#ReactOS in OpenExpo'15 (Madrid) and other PR stuff

[victor martinez]

Hi guys!I'm proud to confirm that ReactOS project will be shown in OpenExpo'15 in
Madrid, 16th June.OpenExpo is one of the greatest open source events in Spain:
http://www.openexpo.esWe'll have the opportunity to give a Talk plus some Hacking lab
(wish me good luck!). If anyone wants to come, I've one additional free pass.
On the other hand, the open source 2/OS project is pushing forward through some Latam
guys:https://plus.google.com/112666045931562995118/posts/6k1Xw2yXB7MSeems they're
using ReactOS code in their project according with their
tweets:https://twitter.com/2osproject/status/578135968219267072(Translation: We're
using code of reactos.org and winehq.org, we have had to interact with networking stack
with ROS using JAVA)Using Java???
And they seemed to have some issues with ReactOS
code:http://twitter.com/2osproject/status/592291632004882433
Keep rockin'!

[Aleksey Bragin]

Awesome news, man!

On 07.05.2015 15:17, victor martinez wrote:
>   Hi guys!
>  I'm proud to confirm that ReactOS project will be shown in OpenExpo'15 
>  in Madrid, 16th June.
>  OpenExpo is one of the greatest open source events in Spain: 
>  http://www.openexpo.es
>  We'll have the opportunity to give a Talk plus some Hacking lab (wish 
>  me good luck!).
>  If anyone wants to come, I've one additional free pass.
>
>  On the other hand, the open source 2/OS project is pushing forward 
>  through some Latam guys:
>  https://plus.google.com/112666045931562995118/posts/6k1Xw2yXB7M
>  Seems they're using ReactOS code in their project according with their 
>  tweets:
>  https://twitter.com/2osproject/status/578135968219267072
>  (Translation: We're using code of reactos.org and winehq.org, we have 
>  had to interact with networking stack with ROS using JAVA)
>  Using Java???
>
>  And they seemed to have some issues with ReactOS code:
>  http://twitter.com/2osproject/status/592291632004882433
>
>  Keep rockin'!
>

[Андрей Кудравец]

Hello everyone. In your community I am a newbie. 
Tell me, how can I tell the developers about bugs in ReactOS, not having write permissions
in the repository. 
I added an issue in jira "core_9895", and as developers learn?

[David Quintana (gigaherz)]

Write access to the repository is not needed to "tell" anyone
anything, that's what JIRA and the IRC channels are for.
If you find a bug, you can just create a new JIRA issue. If you have a
solution for it, then attach the PATCH/DIFF file, and give the issue a
"PATCH" label.
Write access is only given to people the team trusts not to make too
many mistakes too often.

On 3 July 2015 at 18:33, Андрей Кудравец <andrey220822(a)mail.ru> wrote:
>   Hello everyone. In your community I am a newbie.
>  Tell me, how can I tell the developers about bugs in ReactOS, not having
>  write permissions in the repository.
>  I added an issue in jira "core_9895", and as developers learn?
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev

[Андрей Кудравец]

Hi all.
I have added full implementation of the scatter-gather functions.
Also, improvement of the checking is EISA DMA available.
Added detect machine type (ISA / EISA) in the freeldr.
Resolve CORE:9895

https://jira.reactos.org/browse/CORE-9976

I check working of s/g functions on network ndis driver, which using scatter-gather
functions for bus-master adapter.
ASUS P5B->Realtek PCIe GBE Family controller.
All works.

[Андрей Кудравец]

Hello.

I propose to change the structure of the HAL. 
i.e. to build different hal's (hal.dll, halacpi.dll etc not from different libs
(generic, acpi, apic, up, legacy etc.), 
and using constructs like #ifdef _ACPI_HAL_. 
For example, generic/dma.c in the acpi version need when entering sleep mode and exit from
it, you need to save the state of the dma controller, and in non acpi hal - this is not
necessary.
this is for the future.


p. S. sorry for my English if anything.
p. p. S. who speaks Russian, if not difficult, can I write in Russian

[Timo Kreuzer]

The point of using libs is to avoid recompiling stuff to reduce build time.
Everthing that can be done with #ifdef can usually be done with link 
time solutions as well.
So unless there are very strong reasons to change it, I would prefer to 
keep it as it is.
In the case you described, we just need a function that does that wait 
in the ACPI hal and does nothing in the other hals.

Timo

Am 09.08.2015 um 11:14 schrieb Андрей Кудравец:
>   Hello.
>  I propose to change the structure of the HAL.
>  i.e. to build different hal's (hal.dll, halacpi.dll etc not 
>  from different libs (generic, acpi, apic, up, legacy etc.),
>  and using constructs like #ifdef _ACPI_HAL_.
>  For example, generic/dma.c in the acpi version need when entering 
>  sleep mode and exit from it, you need to save the state of the dma 
>  controller, and in non acpi hal - this is not necessary.
>  this is for the future.
>  p. S. sorry for my English if anything.
>  p. p. S. who speaks Russian, if not difficult, can I write in Russian
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev

[Timo Kreuzer]

That 2/OS project looks like another BS project. When I look at the 
video (intentional that it's so blurry that you can't see anything?) all 
I see is a Windows 8 or 10 booting, with a customized startmenu and some 
reactos apps and icons.


Am 07.05.2015 um 14:17 schrieb victor martinez:
>   Hi guys!
>  I'm proud to confirm that ReactOS project will be shown in OpenExpo'15 
>  in Madrid, 16th June.
>  OpenExpo is one of the greatest open source events in Spain: 
>  http://www.openexpo.es
>  We'll have the opportunity to give a Talk plus some Hacking lab (wish 
>  me good luck!).
>  If anyone wants to come, I've one additional free pass.
>
>  On the other hand, the open source 2/OS project is pushing forward 
>  through some Latam guys:
>  https://plus.google.com/112666045931562995118/posts/6k1Xw2yXB7M
>  Seems they're using ReactOS code in their project according with their 
>  tweets:
>  https://twitter.com/2osproject/status/578135968219267072
>  (Translation: We're using code of reactos.org and winehq.org, we have 
>  had to interact with networking stack with ROS using JAVA)
>  Using Java???
>
>  And they seemed to have some issues with ReactOS code:
>  http://twitter.com/2osproject/status/592291632004882433
>
>  Keep rockin'!
>
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev

[Javier Agustìn Fernàndez Arroyo]

WTF

An event in Madrid and i didnt know it????!!!

Of course i´m going!!!!

what do i have to do?

On Thu, May 7, 2015 at 9:48 PM, Timo Kreuzer <timo.kreuzer(a)web.de> wrote:

>  
>  That 2/OS project looks like another BS project. When I look at the video
>  (intentional that it's so blurry that you can't see anything?) all I see is
>  a Windows 8 or 10 booting, with a customized startmenu and some reactos
>  apps and icons.
>
>
>
>  Am 07.05.2015 um 14:17 schrieb victor martinez:
>
>  Hi guys!
>  I'm proud to confirm that ReactOS project will be shown in OpenExpo'15 in
>  Madrid, 16th June.
>  OpenExpo is one of the greatest open source events in Spain:
>  http://www.openexpo.es
>  We'll have the opportunity to give a Talk plus some Hacking lab (wish me
>  good luck!).
>  If anyone wants to come, I've one additional free pass.
>
>   On the other hand, the open source 2/OS project is pushing forward
>  through some Latam guys:
>  https://plus.google.com/112666045931562995118/posts/6k1Xw2yXB7M
>  Seems they're using ReactOS code in their project according with their
>  tweets:
>  https://twitter.com/2osproject/status/578135968219267072
>  (Translation: We're using code of reactos.org and winehq.org, we have had
>  to interact with networking stack with ROS using JAVA)
>  Using Java???
>
>   And they seemed to have some issues with ReactOS code:
>  http://twitter.com/2osproject/status/592291632004882433
>
>   Keep rockin'!
>
>
>
>  _______________________________________________
>  Ros-dev mailing [e-mail]://www.reactos.org/mailman/listinfo/ros-dev
>
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>