After some strike related problems we lost one of our supporters @
Chemnitzer Linux Tage (https://chemnitzer.linux-tage.de/2017/de)
SO if someone wants to join. Here we are, waiting for ya. Start is on
THIS saturday and ending is THIS sunday evening.
Yes, quite a bit early I ask here, but... sadly the problems showed up
today. We might even have a hotel room left if our hotel does not cancel
it that close to booking date. Otherwise we find a way, too.
So, first come first served. Sell your soul/come to us ^^
Hello,
I've just found some new methods to solve the problem you're facing, read more here <http://slyngythyky.httplabs.com/aefaxvsc>
Thanks for your consideration, newsadress(a)gmx.de
Hi Gang,
I was really hopeful when I saw the announcement, and downloaded the latest
ISO, and tried it on both a Dell Optiplex GX270 (basic P4 machine), as well as
a Dell Optiplex 755 (Core 2 duo).
The install went fine on both machines, but neither one will boot up. Locks
up at the first page of loading. If I did a debug boot, the 755 would try to
start, and I could get into the desktop, but then it flaked out.
I would think these boxes are fairly mature technology, and should be no
issue, but apparently not. Is there a way I can help to debug and get this
working?
Thanks,
Bob
I hope this doesn't come across as a rant, but at times ReactOS seems
to be the perfect cure for low blood pressure...
1) Does it have a working partition/format program once installed? I'm
running it as a QEMU VM. *THE INSTALL PROCESS* can take a raw virtual
drive, and create a primary partition and format it. I can't seem to
find that functionality inside the installed ReactOS. The only way I
could figure out to partition and format virtual "drive D:" was to
attach it to a linux VM boot, and run fdisk and mkfs.fat from linux
to prepare it, and exit. Then boot under ReactOS, which now sees a
partitioned and FAT-formatted drive.
2) *WHERE* is the Wine IE executable located? This is as a last resort,
but it's nice to know.
3) *WHERE* does Wine IE stash files that it downloads? There is no
indication anywhere on its menus. I can't find anything resembling
"Edit->Preferences". And while we're at it, could the people who do
ReactOS docs *PLEASE* specify that "debug.log" default directory is
C:\ReactOS. It took me a while to find it. Merely saying that there's
a "debug.log" file somewhere, in some directory on the system, is *NOT*
good enough.
4) I finally managed to turn off nagging at bootup for, "New Hardware
Wizard" has found a Bus Controller. It can't find the driver locally,
and, no I don't have a driver for it. I had to click "Cancel" on the
dialogue 3 times, because it came back after the first 2 cancels...
*EVERY TIME I BOOTED UP***.
Out of sheer desparation...
* I told it to install
* It failed and came back with the same dialogue, but with a "Don't ask
me again" checkbox, which I eagerly checked off.
* I had to repeat this 3 times. Now no more nagging from the "New
Hardware Wizard about the Bus Controller driver.
--
Walter Dnes <waltdnes(a)waltdnes.org>
Nearly ten years ago the ReactOS Project released version 0.3.0. Today we are proud to announce the formal release of version 0.4.0!
A great deal of work has gone into making this release happen and as we look back it is remarkable to consider how far the project has come since that release a decade ago. This release is both a celebration of and a testament to everything that the ReactOS team and community has achieved together.
Here we document some of the highlights that separate 0.4.0 from not just the 0.3.17 release but also the cumulative achievements that the 0.3.x series achieved: https://reactos.org/project-news/reactos-040-released
A changelog is available at: https://reactos.org/wiki/ChangeLog-0.4.0
Thank you to all of you for having stood by the project for this long and we hope rewarding journey.
For those of you chomping at the bit to check out the release, please go to the download page to get it now: https://reactos.org/download
