Problem booting ReactOS from Dos

[Julius Schwartzenberg]

Hi,
When I try to boot ReactOS on one of my comps, I get the following error 
after running boot.bat:
Bug detected (code 7b param 0 0 0 0)
INACCESSIBLE_BOOT_DEVICE

Frames: <ntoskrnl.exe: 969a> <ntoskrnl.exe: 96ba> <C007B16A> 
<ntoskrnl.exe:a9ed> <C007B96B> <ntoskrnl.exe: 127e>

I'm using the binaries package, because I have more than one primary 
partition. I tried running boot.bat from PC DOS 7 and FreeDOS (ReactOS 
boots without problems with PC DOS 7 on another comp).
The specs of the computer:
Intel Pentiun 3 700MHz
Intel 440BX chipset
Creative 3D Blaster Banshee (Voodoo Banshee)
Creative Sound Blaster 16
3COM 3C905C-TX ethernet
I'm using ReactOS version 0.2.2.
Any idea what to do?
Thanks in advance,
Julius

[Sukotto]

I've got a 440BX Based board too! Same problem! My
board is a MSI 6163 BX Master. I've had problems like
that with Low level format tools, & with Windows 98
(on after first boot, I then have to boot in safe mode
and install the driver from a floppy) since it doesn't
know what the onboard promise ata66 controller is. You
could try loading the NT4 version of the promise ata66
controller & hopefully it works. Sorry I can't test
it, I just made mine into a FreeBSD box.

--- Julius Schwartzenberg <julius(a)zgod.cjb.net> wrote:
>   Hi,
>  When I try to boot ReactOS on one of my comps, I get
>  the following error 
>  after running boot.bat:
>  Bug detected (code 7b param 0 0 0 0)
>  INACCESSIBLE_BOOT_DEVICE
>  
>  Frames: <ntoskrnl.exe: 969a> <ntoskrnl.exe: 96ba>
>  <C007B16A> 
>  <ntoskrnl.exe:a9ed> <C007B96B> <ntoskrnl.exe: 127e>
>  
>  I'm using the binaries package, because I have more
>  than one primary 
>  partition. I tried running boot.bat from PC DOS 7
>  and FreeDOS (ReactOS 
>  boots without problems with PC DOS 7 on another
>  comp).
>  The specs of the computer:
>  Intel Pentiun 3 700MHz
>  Intel 440BX chipset
>  Creative 3D Blaster Banshee (Voodoo Banshee)
>  Creative Sound Blaster 16
>  3COM 3C905C-TX ethernet
>  I'm using ReactOS version 0.2.2.
>  Any idea what to do?
>  Thanks in advance,
>  Julius
>  _______________________________________________
>  ros-general mailing list
>  ros-general(a)reactos.com
>  http://reactos.com/mailman/listinfo/ros-general 


	
		
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover

[Hartmut Birr]

>   -----Original Message-----
>  From: ros-general-bounces(a)reactos.com 
>  [mailto:[e-mail]] On Behalf Of Sukotto
>  Sent: Saturday, May 01, 2004 2:31 AM
>  To: ReactOS General List
>  Subject: Re: [ros-general] Problem booting ReactOS from Dos
>  
>  
>  I've got a 440BX Based board too! Same problem! My
>  board is a MSI 6163 BX Master. I've had problems like
>  that with Low level format tools, & with Windows 98
>  (on after first boot, I then have to boot in safe mode
>  and install the driver from a floppy) since it doesn't
>  know what the onboard promise ata66 controller is.  
If the problem is the promise ata66 controller, it's possible to add support
for this controller. Currently, atapi can use promise ultra100 and
ultra100tx controllers. If you know the pci device id of the ata66
controller, you can add it to PciNativeController. If you cannot compile
ros, I can build the atapi driver for you, if I know the pci device id or
the chip description (PDC20???). The only risk is that nobody has tested
this conntroller and in the worst case, atapi can mix your disk.      

- Hartmut