Page 1 of 7

ReactOS does not run on older computers

Posted: Mon Jan 01, 2007 1:31 pm
by PeterK
Hello,

I have tried to boot from LiveCD on four older computers (between 200 and 400 MHz) but none of them boots up well.

Two of them do not boot at all - not even "A problem has been detected and ReactOS has been shut down to prevent damage to your computer. ...", just only a blue screen. One of them does hang with ""The bug code is undefined ..."

I added the last one - with error "Can't boot LiveCD, error 0x00000000" - to Bugzilla (1742). But it seems the problems inside ReactOS are not fixable at the moment as there does happen nothing since 2006-08-08.


Does anybody know if (or when) the bootup problems on older mainboards are going to be fixed - or is it not a thing of interest ?

Posted: Mon Jan 01, 2007 3:07 pm
by GreyGhost
Welcome to ReactOS !!
Can u please give us a bit more details?
1- Which version of ReactOS was it 0.3 ? or was it trunk ?( last i heard ....trunk LiveCD is broken...)
2-Were there any USB peripherals connected? (ReactOS has an unstable USB stack atm...)

Posted: Mon Jan 01, 2007 5:33 pm
by PeterK
GreyGhost wrote:Welcome to ReactOS !!
Can u please give us a bit more details?
>Which version of ReactOS was it 0.3 ?
I tried every release from 0.2.9 up to 0.3.0 rel (also the 0.3.0 RC1,2,3 ..)
Every version with the same result.

>Where there any USB peripherals connected?
No device connected.

Hardware: Pentium II / 400 MHZ on special mainboard with riser card, built in a 19" 2HE case / housing


Details - while booting LiveCD 0.3.0 RC1 :

"The bug code is undefined"
0x00000000

.. following ...:

Frames:
<ntoskrnl.exe 1676>
<ntoskrnl.exe 168d>
<ntoskrnl.exe 72d05>
<ntoskrnl.exe 73026>
<ntoskrnl.exe 70fd8>
<ntoskrnl.exe 45fa>
<ntoskrnl.exe 6f529>
<0>


You can have more hardware details when I'm back home from work ..

Posted: Mon Jan 01, 2007 6:35 pm
by Dr. Fred
If possible for you please try our debug release, but's a install cd.

http://sourceforge.net/project/download ... EL-DBG.zip

Posted: Mon Jan 01, 2007 6:58 pm
by PeterK
Dr. Fred wrote:If possible for you please try our debug release, but's a install cd.

http://sourceforge.net/project/download ... EL-DBG.zip
I will do this asap.


***************
Further information:
Under build 23566-dbg (2006-08-13) the bug looked as follows:

A problem has been detected and ReactOS has been shut down to prevent damage to your computer.

The bugcode is unidentified. Please use an existing code instead.

Frames:
<ntoskrnl.exe:1d5a (ntoskrnl/ke/bug.c:499 (KeBugCheckEx))>
<ntoskrnl.exe:1d71 (ntoskrnl/ke/bug.c:515 (KeBugCheck))>
<ntoskrnl.exe:9702c (ntoskrnl/io/iomgr/arcname.c:303 (IoCreateArcNames))>
<ntoskrnl.exe:98655 (ntoskrnl/io/iomgr/iomgr.c:477 (IoInit3))>
<ntoskrnl.exe:95c09 (ntoskrnl/ex/init.c:654 (ExpInitializeExecutive))>
<ntoskrnl.exe:5015 (ntoskrnl/ke/main.c:108 (KiSystemStartup))>
<ntoskrnl.exe:94531 (ntoskrnl/ke/main.c:291 (_main))>
<0>

Posted: Mon Jan 01, 2007 7:14 pm
by hto
Is it only happens with LiveCDs or with BootCDs too?

Can you try to boot latest revision of live/boot CD? ( http://svn.reactos.org/iso/ )

> Does anybody know if (or when) the bootup problems
> on older mainboards are going to be fixed - or is it
> not a thing of interest ?

I think it will be fixed, but nobody knows when.

Posted: Tue Jan 02, 2007 12:13 am
by PeterK
hto wrote:Is it only happens with LiveCDs or with BootCDs too?
Both.
hto wrote:Can you try to boot latest revision of live/boot CD? ( http://svn.reactos.org/iso/ )
As asked I tried 0.3 release.


Now, tested with 0.3 release dbg I get the same result as since 0.2.9 (but for sure with different entry points in the source code as developement goes on .. ):

------------------------------------------------------------
A problem has been detected and ReactOS has been shut down to prevent damage to your computer.

The bugcode is undefined. Please use an existing code instead.

Technical information:

*** Stop: 0x00000000 (0x00000000, 0x00000000, 0x00000000, 0x00000000)

Frames:
<ntoskrnl.exe:1676 (ntoskrnl/ke/bug.c:489 (KeBugCheckEx))>
<ntoskrnl.exe:168d (ntoskrnl/ke/bug.c:505 (KeBugCheck))>
<ntoskrnl.exe:832e4 (ntoskrnl/io/iomgr/arcname.c:303 (IoCreateArcNames))>
<ntoskrnl.exe:83678 (ntoskrnl/io/iomgr/iomgr.c:417 (IoInit3))>
<ntoskrnl.exe:8128d (ntoskrnl/ex/init.c:668 (ExpInitializeExecutive))>
<ntoskrnl.exe:4e71 (ntoskrnl/ke/main.c:108 (KiSystemStartup))>
<ntoskrnl.exe:7f53d (ntoskrnl/ke/main.c:255 (_main))>
<0>


So I think that nothing happened since 0.2.9. in the case of the error that occurs on my
P II 400 MHz
128 MB RAM
VGA Elsa Winner 2000 / Office
Mainboard I440BX-SMC93X-2A69KN0AC

My question is if I can do anything with the hardware configuration to avoid the error ?

Thanks,
Peter

Toshiba Tecra 510 Laptop no GO SVN 25331

Posted: Tue Jan 02, 2007 1:22 am
by madmax69
Have had several attmepts to boot a Toshiba Tecra. 510 - approx 140mb memory, 2GB hard drive. Win2k installed and working - multi boot with Win98. FAT32. Smart Boot Manager to enable CDROM boot as BIOS does not support it. SBM is quite good for booting older PCs from CDROM and is free.

e.g. SVN 25331 REL ISO Live CD

Boot sequence starts okay. Black Screen. Bootstrap loader initiates, lots of CD activity after about 10 secs ROS atom logo is displayed on a black background briefly. Looks good so far but a few milliseconds later a solid block of "BSOD blue" colour wipes from Left to right over the logo and erases it and the boot process halts with no information. No HDD activity, no CDROM activity. No response to any keypresses other than to toggle NumLock LED for a while but eventually that stops responding. No CTRL_ALT_DEL available. Screen is left solid mid blue with zero writing or cursor. Power off reboot several times to confirm this is repeatable.

Deadsky!

Addendum ----------

Just booted 0.3.0 REL live CD on same machine got the following error which appears typical of that version. Heres the output in case it is of any use for debugging with older H/W or SBM.

--------------
Press any key to boot from CD
Disk Read Failed
Error Code: 0x1
Error: bad command passed to driver
Press any key
Failed to read the PVD.
Press any key
---------------

Posted: Tue Jan 02, 2007 2:13 am
by GreatLord
trunk livecd does not working yet. it have regress thanks to redesign of ntoskrnl, it will be back when then new mounting of drivers are in ntoskrnl, mean time we are using a hack getting bootcd.iso working

Posted: Tue Jan 02, 2007 2:23 am
by madmax69
Thanks GreatLord - that answers my question! :)

Posted: Tue Jan 02, 2007 4:18 am
by hto
Can you try to boot latest revision of live/boot CD? ( http://svn.reactos.org/iso/ )
As asked I tried 0.3 release.
I mean can you try to download latest iso image from that address, boot machine from it and say is it works or not.

Posted: Tue Jan 02, 2007 7:57 am
by PeterK
hto wrote:
Can you try to boot latest revision of live/boot CD? ( http://svn.reactos.org/iso/ )
As asked I tried 0.3 release.
I mean can you try to download latest iso image from that address, boot machine from it and say is it works or not.
As far as I remember it was
bootcd-25263-rel.7z

It was not the liveCD.

Posted: Tue Jan 02, 2007 10:32 am
by hto
PeterK wrote: As far as I remember it was
bootcd-25263-rel.7z
PeterK wrote: Frames:
<ntoskrnl.exe:1676 (ntoskrnl/ke/bug.c:489 (KeBugCheckEx))>
<ntoskrnl.exe:168d (ntoskrnl/ke/bug.c:505 (KeBugCheck))>
<ntoskrnl.exe:832e4 (ntoskrnl/io/iomgr/arcname.c:303 (IoCreateArcNames))>
<ntoskrnl.exe:83678 (ntoskrnl/io/iomgr/iomgr.c:417 (IoInit3))>
<ntoskrnl.exe:8128d (ntoskrnl/ex/init.c:668 (ExpInitializeExecutive))>
<ntoskrnl.exe:4e71 (ntoskrnl/ke/main.c:108 (KiSystemStartup))>
<ntoskrnl.exe:7f53d (ntoskrnl/ke/main.c:255 (_main))>
Looks like this trace was not from 25263.

Posted: Tue Jan 02, 2007 10:57 am
by hto
VGA Elsa Winner 2000 / Office
Maybe VBE is not supported and error related to it. Try to use Display: VGA Display (640x480x8) when installing.

Posted: Tue Jan 02, 2007 11:10 am
by PeterK
PeterK wrote: Frames:
<ntoskrnl.exe:1676 (ntoskrnl/ke/bug.c:489 (KeBugCheckEx))>
...
hto wrote: Looks like this trace was not from 25263.
Possible. Maybe it was the release dbg (I'll ckeck this tonight ..)

But I get the same return messages from subfunctions / units in the same order (since 0.2.9):
- KeBugCheckEx
- KeBugCheck
- IoCreateArcNames
- IoInit3
- ExpInitializeExecutive
- KiSystemStartup
- _main

.. only with different .exe adress / source code line numbers, since 0.2.9 ..

hto wrote:
VGA Elsa Winner 2000 / Office
Maybe VBE is not supported and error related to it. Try to use Display: VGA Display (640x480x8) when installing.
As far as I remember I tried another VGA card last year and I got the same result. (I don't know how to change resolution, and the error happens before the ReactOS start screen appears, in text mode)