The ReactOS team is proud to announce the release of ReactOS 0.3.12.
This is a huge release for the team, not just with regards to the
number of improvements which this release holds but in terms of the
leap forward architecturally, stability wise and in bringing some of
the more modern aspects of the NT kernel into ReactOS.
It's been almost a year since the last release and whilst this is
understandably excessive, it was required to stabilize the OS due to
the nature of the work which was undertaken. Focus at the start of
this release was on a single area, the trap handler mechanism, which
resulted in a complete rewrite of this area. This brought with it the
need for more changes which escalated into many areas getting an
overhaul and many new technologies being developed and brought into
the core. What resulted from this was a vastly more modern kernel
containing code which had been exercised significantly less than the
code it replaced. This triggered a large testing phase to bring the
stability and compatibility to levels above that of the previous code.
During the preparation of this release, 259 bugs were fixed,
including 61 regressions some of which originated from ReactOS 0.3.7.
Ten of those bugs are more than 3 years old, with the oldest fixed
bug being #969 (5 years old).
A heavily cut down list of some of the more major changes which have
been going on in the past year is as follows:
• Memory Manager - The memory manager continued to see much work as
the ARM team replaced each component piece by piece whilst also
maintaining the functionality of the old manager. Although 0.3.12
does not completely switch over to the new manager, what is obvious
are the speed, stability and compatibility improvements of this new
model.
• NMI support - ReactOS can now handle NMIs with a Red Screen of
Death, useful for capturing hardware errors detected by the CPU or
Bus. Additionally, support for 3rd party NMI callbacks has been
implemented, which is useful for certain server systems. Finally,
support for generating a crash dump during an NMI is partly
implemented, which can help when a machine is frozen or hung and an
external NMI dump switch is used.
• Trap Handler Rewrite - Almost all CPU faults, trap, exception, and
system call code is now written in C instead of Assembly. Many legacy
and/or deprecated code paths have been disabled and performance-heavy
debugging paths disabled by default. Additionally, the x64 and ARM
ports now share much more of this code. Finally, the code is much
cleaner and can take advantage of compiler optimizations to generate
the best possible code for the CPU instead of writing hand-crafted
assembly that was specific only to certain CPU models. Work is
ongoing to remove even more of the last remaining Assembly routines.
• EMS - Support for Emergency Management System (or Headless) has
been partially implemented. The boot flags documented by Microsoft
are supported, and certain debug output is sent to the serial port as
expected. Work is ongoing to provide the EMS logging capabilities and
to move the existing legacy KDBG debugger over EMS. SAC (Special
Administration Console) driver work is also in progress to compliment
this.
• PnP Compatibility - Various improvements have been done to increase
hardware support and support for loading 3rd party drivers.
• ACPI Improvements - The ARM team has implemented the basic drivers
required for supporting batteries and 3rd party UPS/battery drivers,
including support for the ACPI Composite Battery specification. This
support is not currently enabled in this release because ACPI is
still undergoing work.
• New PCI-X driver - The ARM team has been slowly working on the new
PCI bus driver. Previously, ReactOS was using a very simple and
mostly stubbed PCI bus driver which lacked support for many real-
world PCI bus features, PCI-to-PCI bridges etc. With this new
driver, compatibility on real hardware, not just virtual machines,
should improve significantly, along with performance.
• SxS support – Side-by-side code was added, along with loading and
finding manifest files. It’s an important step forward to be
compatible with modern applications which use this technology.
• Pool Corruption Fixes - Perhaps the most serious of these suspected
leaks were fixed thanks to combined efforts of key ReactOS developers
utilising advanced methods including a customized version of QEMU
virtual machine.
• Timer and message handling rewrite - Incorrect handling of non-
queued messages led to deadlocks in some applications which the
message handling rewrite resolved. The timer implementation rewrite
is also completed by this release which fixes many timer-related
problems, most known is the “need to move mouse in order to download
in FireFox”.
• x64 build - While the x64 port is still in an early stage regarding
the functioning of the kernel, most of the generic compilation issues
are resolved and necessary core functionality implemented. These
efforts have been merged back into trunk, so that trunk can be
compiled for x64 target. With the help of automatic builds, possible
breakages can now quickly be detected and resolved. Don't expect it
to boot to GUI though!
The changelog <http://www.reactos.org/wiki/index.php/
ChangeLog-0.3.12> for 0.3.12 is also markedly different from previous
releases, with an emphasis on conveying an understandable and concise
summary of major changes in the release. Thus instead of duplicating
that summary here, we invite you to peruse its contents and see what
has been accomplished.
Whilst the ReactOS team has still been attending many public events
and conferences in various different countries, we’ve been out of the
news due to what may appear as a quiet patch or a lull in activity.
We hope this release will go some way to show that we’ve been busier
than ever behind the scenes.
_______________________________________________
Ros-announce mailing list
Ros-announce(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-announce
Hola,
ayer me pegué el santo día intentando instalar el Reactos en mi
portatil Fujitsu Amilo LI1705. Ni flores, no hubo forma. Se quedaba
pillao poco después de seleccionar la partición de mi disco duro.
Todo eso desde el cd de instalación. Luego me volví loco buscando por
internet si había alguna forma de crear un pendrive de instalación de
Reactos. No encontré nada, e igualmente ni flores. Alguien sabría la
forma de crear un pendrive que contuviese la instalación de Reactos???
Un saludo y gracias de antemano.
Pepe
Hi folks,
does ROS run under lguest ?
I'm currently building an lguest-based VM (mass-)hosting service,
and it would be a cool thing if ROS (as win32 alternative) could
be easily run there.
My business model includes free VMs on spare resources, which
can be quickly deployed (within a minute), for testing and fun.
I'd like to provide ROS as one of the preinstalled images, so
it will get a bit more audience :)
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
Hallo,
I get a BSOD, if install ethernetdriver el90xnd5.sys.
HW seen to be ok. (tested on knoppix)
Whats going wrong?
Heiko
details:
- ReactOS 0.4-SVN (Build 20100711-r47998)
- install driver [1] [2]
wget ftp://ftp.3com.com/pub/nic/3c90x/3c90x1.exe
dosbox> 3c90x1.exe
knoppix # scp $src/EL90XND5.SY_ $rosdir/TEMP
ros> cd \TEMP
ros> expand EL90XND5.SY_ el90xnd5.sys
ros> copy el90xnd5.sys %windir%\system32
## hardwareinstaller will this use as TODO.
- ros: hardwareinstallation detected a new device:
hardwareinstallation
Ethenet controller
[x] treiber von einer bestimmten Pos. installieren:
[x] diesen Pfad ebenfalls durchsuchen: c:\temp
Card seen recognized (print "3com 100Mbit" for 0.01s)
-> bluescreen:
A problem has been detected...
Stop: 0x000001E (0cc0000005,0xf93c2f01,0xf93e9658,0x000000)
el90xnd5.sys - Address F93c2f01 base at f93b000. dtaStamp 3b535836
- debug.log: IRQ11 fail
I cannot get debuginfo over serial interface.
Therefore i attached debug.log (part) only.
$ egrep -i "^00|hal|err|ether|irq|3c" /var/tmp/debug.log > ros.deb.log-100723.3com.part
Does exist another way to install network-driver?
Howto add timestamp to debug.log?
[1] http://www.reactos.org/wiki/Supported_Hardware/Network_cards
- supported HW
[2] http://www.reactos.org/archives/public/ros-general/2010-June/002586.html
- minihowto (concept)
Please open a bug report in bugzilla, tag the title with [PATCH], attach the
patch and provide your name and email.
Thanks in advance
2010/7/25 <ros-general-request(a)reactos.org>
> Send Ros-general mailing list submissions to
> ros-general(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-general
> or, via email, send a message with subject or body 'help' to
> ros-general-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-general-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-general digest..."
>
>
> Today's Topics:
>
> 1. patch more.c ros-0.4 (Heiko L.)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 25 Jul 2010 13:39:02 +0200 (CEST)
> From: "Heiko L." <hlehmann(a)fh-lausitz.de>
> Subject: [ros-general] patch more.c ros-0.4
> To: ros-general(a)reactos.org
> Message-ID:
> <49634.217.93.93.92.1280057942.squirrel(a)webmail.fh-lausitz.de>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
>
> >>> prob 5: cmd "more" keybind "next page"
> >>> - descr: "EACH" key binded to "next page", so "^C" "q" does not working
>
> solution:
> - check if (wVirtualKeyCode=="q")
> - s. patch ros-0.4.patch-100724.more_quit
>
> regards heiko
>
>
> [1]
> http://www2.fh-lausitz.de/launic/comp/ros/100724.ros.compile.rosbe.howto.txt
> [3]
> http://www.tutorials.de/c-c/279010-wie-mit-readconsole-strings-einlesen.html
>
Hello good Day,
my name is Faustina Essing and i visitthe linux-user-group at Cologne (Köln, Germany).
Linux Workshop Kölnhttp://www.uni-koeln.de/themen/linux
We are enthousiast to all free and opensource software and at Software Freedom Day at 18. september 2010 weare going to organize an interesting event and celebrate this day atCologne (Köln).
For this event we would like to producean exciting agenda (Tagesprogramm) and we would like to invitesomeone of ReactOS and ask politely if someone of you would like tospeech about the interesting ReactOS-Project on our Software FreedomDay Event.
Software Freedom Day Köln http://www.koelnerlinuxtreffen.de
Kind regards from Cologne
Faustina Essing
Hallo,
I trial to install network-driver.
Problem: hardware-assistent seen does not work. (see 3.)
(i have tried translate to en, org: ger)
Whats going wrong?
Does exist another way? (Link)
regards Heiko
3.11, bootcd-47788
----------------------------------------------
1. command seen cannot execute dos-exec
ros: C:\TEMP> 3c90x1.exe
The instruction at "0x7800202" referenced memory at "0x00000000". The memory c
ould not be "read".
-> workaround: debian>dosbox
----------------------------------------------
2. my minihowto install network-driver (part)
debi # cd dos
debi # wget ftp://ftp.3com.com/pub/nic/3c90x/3c90x1.exe
dosbox> 3c90x1.exe
knoppix # scp $src/EL90XND5.SY_ $rosdir/TEMP
ros> expand EL90XND5.SY_ el90xnd5.sys
ros> copy el90xnd5.sys %windir%\system32\drivers
ros> control -> system -> hardware
[1] http://www.reactos.org/wiki/Supported_Hardware/Network_cards
----------------------------------------------
3. ros install driver
ger:
----
control -> system -> hardware
|
v
...
HW-Assistent
Installierte HW:
Ein neues Geraet hinzufuegen , ....
|
v
Wie wollen Sie den Assistenten fortsetzen?
( ) Automatisch nach neuer HW suchen ... (empfohlen)
( ) Manuell aus der Liste....(erwitert)
- test 1 auto
Die Suche ist nach 10 Min. noch nicht weiter...
fortschrittsbalken: 0%
- test 2 man
egal was man auswaehlt:
button <weiter> bleibt inaktiv
----------------------------------------------
eng:
---
HW-Assistent
What you want....?
( ) automaticly...(recommended)
( ) manually...
-> test 1 auto
nothing to do...progressbar: 0%
-> test 2 man
click one of these entries
result: button <next> inactive anymore
----------------------------------------------
Hello, everyone.
I am testing ReactOS for a few months and I am of the opinion that
it is a really interesting Project.
I am also here to anounce something.
I saw on the homepage thay the ReactOS Team was present at CLD.
Since I am Member of upLUG (Potsdam Linux User Group), I would like
to forward a request.
The 7. BLIT (BLID - Brandenburg Linux Info Day) will take place at
Griebnitzsee (Potsdam/Berlin) on 6. of November and there is a
possibility to present ReactOS on the BLID.
If you are interested to come, you can find information on www.*blit*.org.
But I have to warnyou , the website is german and I didn't find a button
for changing the language.
sincerly, Eladrion