Re[2]: [ros-general] Booting problem: ROS hangs up after disks check

[Kyryll A Mirnenko]

j> You must start ros from protected mode if you are running windows.
j> I run win95 and just before windows starts (as soon as I see ' starting win95 ' ) I have to press the F8 key and then select safe mode with command prompt (7). I think it is the ctrl key and not
j> the F8 key in win98.

I've started it from CLEAN DOS (WinME boot floppy), that was real mode
under real DOS.

j> Running ros for the first time is like running windows for the first time, you have to reboot again before you can use it.

Was that normal it hung up in a blue sceen after D: drive check? There
were no messages, after hardware reboot everything was the same -
hanging up after last FAT32 drive check.

As I said, I've got UFS (FreeBSD) partition after that last drive it
checks & hangs up, my version is that it's confused by it. Another
version is DMA-less harddisk (although ATAPI v4)

Hope, somebody'll help,

mirya

[Aleksey Bragin]

----- Original Message ----- 
From: "Kyryll A Mirnenko" [e-mail]
To: "jh" [e-mail]; [e-mail]
Sent: Monday, February 23, 2004 11:53 PM
Subject: Re[2]: [ros-general] Booting problem: ROS hangs up after disks
check

-= skip =-
> j> Running ros for the first time is like running windows for the first

time, you have to reboot again before you can use it.
> Was that normal it hung up in a blue sceen after D: drive check? There
> were no messages, after hardware reboot everything was the same -
> hanging up after last FAT32 drive check.

Certainly it isn't. But actually ROS doesn't really check drives,
autochk.exe is just a stub for now. So the problem is further - when loading
drivers probably.
> As I said, I've got UFS (FreeBSD) partition after that last drive it
> checks & hangs up, my version is that it's confused by it. Another
> version is DMA-less harddisk (although ATAPI v4)

ReactOS doesn't use DMA to access HardDisk now at all (correct me if I'm
wrong - I'm not so into harddisk drivers stuff).
> Hope, somebody'll help,
> mirya

You know, you should definately enable debug output (edit your freeldr.ini ,
in [ReactOS] section, in Options=/DEBUG /DEBUGPORT=COM1 /BAUDRATE=115200).
And you can watch debug messages both on the screen and on the COM port.
Then you can tell us more precisely what your problem is, and we can find a
fix for this.

With the best regards,
Aleksey Bragin.