Well, I look a bit at the code, and try to figure out a bit more how things... boot. First you need a bootsect, and there are many depending of where it is put: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/bootsect/ I believe the role of bootsect is to load freeldr.sys. FreeLoader r...

Thanks, but at first glance this is not it. I means I commented out usb stuff in reactos/media/inf/CMakeLists.txt and after that "ninja all" said nothing to do. Then bootcd with "ninja bootcd" did the same as before. edit1:I think this is linked to http://svn.reactos.org/svn/reac...

ah! Maybe that: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/bootdata/txtsetup.sif?revision=59649&view=markup Googling about it returned among others: http://gosh.msfn.org/txtsetup.htm It works... more or less... commenting out with a semicolon at the begining... Now stage 1 is fine... ...

I have built a bootcd with: #add_subdirectory(usbohci) in drivers/usb/CMakeLists.txt file. It build fined, but when I try to run it: (../../boot/freeldr/freeldr/windows/winldr.c:328) err: Can't load boot driver 'system32\drivers\usbohci.sys'! It will also stop because it cannot initialize boot drive...

Everything in second post was tested and worked for me.

The best option is already documented in https://www.reactos.org/wiki/VirtualBox minicom with serial port set to unix#/tmp/ReactOS-Debug.pipe Then you can use Ctrl-A Z to get list of commands. Most usefull Ctrl-A L to log to a file. When finished, redo Ctrl-A L to close the file. Ok I found somethin...

Once at the kbd> prompt, I cannot send my keystroke to the VM while using socat to show the log. Even if I boot ReactOS (RosDbg)... ReactOS (Debug) should have this problem I think. I use: paul@chibouli:~$ socat unix-client:/tmp/ReactOS-Debug.pipe stdin [Tab K to force the debugger] fixme:shell:OnNo...

I just found exactly? the same stack trace in my bug report five hours ago! https://jira.reactos.org/browse/CORE-8020 Just stop trying F8, Enable VGA mode should fix it! :) But if you used it, probably you was having an other bug when not trying to boot in VGA mode? Just worth to mention my computer...

Well, without reinstalling... I connected my null-modem cable... and rebooted in debug mode.
This time I accepted default value in Setup Wizard.
Somehow... sadly... it finished without problems this time.
So that now I reboot, and the system inform me that it found a new audio-device.

Ok, having gone through the problem of needing to grow my video memory in BIOS, I was happy to go to setup wizard. Was mostly ok... except maybe setting my country to Canada, it was coming back by itself to United States. Setting default keyboard layout... I had no feedback telling me I succeeded to...

I did read the other post about problems about i845 chipset having problems (not enough video memory). So I did go in my BIOS to see that actual memory set was 1024k ... I changed it to 8096k... then reboot. Did not have to try VGA (which I had try before with F8, VGA) and did not seen any major cha...

On this computer, ReactOS does not seems to work. With ACPI, I got: http://jira.reactos.org/browse/CORE-7501 So, I reinstalled, but without ACPI (uniprocessor standard... or something like this). I used my Null-Modem cable to get the following: ../../ntoskrnl/kd/kdio.c:376) -------------------------...

Hi! I just received this email: Dear ReactOS Community Member, We contact you today, because you have signed up for a myReactOS account some time ago. And we need your help! A German bank is currently running a sponsoring campaign for all kinds of foundations. The 1000 foundations with the most vote...

Hi, I tested TRUNK (some days ago), more precisely livecd-48891-dbg.iso. On Pentium III with a Voodoo 3 AGP video card, it looks like all the drivers were loaded on the black screen (after FreeLoader). But it seems hang at the end. Maybe Voodoo 3 is not a VESA card? On the Asus P5GZ-MX (integrated I...

Well, It is still quite a bit confused in my head. But Gallium3D was integrated in Mesa main line, in version 7.5 (July 2009). I THINK that it is still not used much, and that it is optional for now. And that even if eventually, it would be compilable on Windows and then allows to use the new driver...