Black screen when loading blue.sys in setup(ReactOS 0.31)
Moderator: Moderator Team
Black screen when loading blue.sys in setup(ReactOS 0.31)
Hello
I had installed ReactOS 0.30 on a harddisk using the boot cd . it ran fine.
But with ReactOS 0.31 it's much more difficult. Setup starts, begins to load drivers, but when Blue.sys has just been loaded, I get a black screen. To be sure it was not my CD Burner, or my CDrom drive, I used winimage to extract files and folders from the iso file and copy them on the harddiisk.without burning any cd rom.
Since I have already installed ReactOS, the boot sector calls Freeldr.ini and Freeldr.sys.
I copied Setupldr.sys to the root directory (c:\) and renamed this file Freeldr.sys. So at the reboot, ReactOS setup started from the harddisk, but was stopped immediatly after loading blue.sys. it seemed to be a display problem.
Then I searched other ways to make it work.
Finally, I got a success with the following way.
I copied the folders from live cd to the harddisk
I copied the folders from dbg-kdbg boot cd the harddisk(overwriting live cd files)
I copied Freeldr.sys from the loader folder to the root folder(c:\)
I edited Freeloader.ini(I had kept this file from ReactOS 0.30) , Default : ReactOS_Debug, path : \"drive*\Reactos.
At the reboot setup starts(with Freelodr.sy, instead of Setuplldr.sys), but desn't stop any more when Blue.sys is loaded.(I don't undertand why)
I had to choose a other folder to install ReactOS (Not the folder where I had put installations files)
There was an error : setup couldn't create system hive. So I copied the config folder from the live cd to the folder where I had installed ReactOS.
I edited again Freeldr.ini, Default : ReactOS, path:\drive\directory where ReactOS was installed.
After the reboot, I got ReactOS 0.31
Many program works (cmd, notepad, workpad, control ... for instance), I can change the display, install 7zip, or Mozilla Activex controls, but this installation is not correct . The registry is only a copy of the registry of the live cd . Most drivers are not installed. Network and shutdown don' t work . Every timeI reboot, i have to restore the registry.
Thank you for your help
I had installed ReactOS 0.30 on a harddisk using the boot cd . it ran fine.
But with ReactOS 0.31 it's much more difficult. Setup starts, begins to load drivers, but when Blue.sys has just been loaded, I get a black screen. To be sure it was not my CD Burner, or my CDrom drive, I used winimage to extract files and folders from the iso file and copy them on the harddiisk.without burning any cd rom.
Since I have already installed ReactOS, the boot sector calls Freeldr.ini and Freeldr.sys.
I copied Setupldr.sys to the root directory (c:\) and renamed this file Freeldr.sys. So at the reboot, ReactOS setup started from the harddisk, but was stopped immediatly after loading blue.sys. it seemed to be a display problem.
Then I searched other ways to make it work.
Finally, I got a success with the following way.
I copied the folders from live cd to the harddisk
I copied the folders from dbg-kdbg boot cd the harddisk(overwriting live cd files)
I copied Freeldr.sys from the loader folder to the root folder(c:\)
I edited Freeloader.ini(I had kept this file from ReactOS 0.30) , Default : ReactOS_Debug, path : \"drive*\Reactos.
At the reboot setup starts(with Freelodr.sy, instead of Setuplldr.sys), but desn't stop any more when Blue.sys is loaded.(I don't undertand why)
I had to choose a other folder to install ReactOS (Not the folder where I had put installations files)
There was an error : setup couldn't create system hive. So I copied the config folder from the live cd to the folder where I had installed ReactOS.
I edited again Freeldr.ini, Default : ReactOS, path:\drive\directory where ReactOS was installed.
After the reboot, I got ReactOS 0.31
Many program works (cmd, notepad, workpad, control ... for instance), I can change the display, install 7zip, or Mozilla Activex controls, but this installation is not correct . The registry is only a copy of the registry of the live cd . Most drivers are not installed. Network and shutdown don' t work . Every timeI reboot, i have to restore the registry.
Thank you for your help
hello
Thank you for these explanations.
Is this uncompatibility issue with AMD xp/mp/64 in Setupldr.sys or in Ntoskrnl.exe ?
With my AMD K8 cpu I never completed an installation with Setupldr.sys,( new release provided with ReactOS 0.31), but Ntoskrnl.exe seems to work with this kind of "dirty" installation I've made using Freeldr.sys instead of Setupldr.sys.
Thank you for these explanations.
Is this uncompatibility issue with AMD xp/mp/64 in Setupldr.sys or in Ntoskrnl.exe ?
With my AMD K8 cpu I never completed an installation with Setupldr.sys,( new release provided with ReactOS 0.31), but Ntoskrnl.exe seems to work with this kind of "dirty" installation I've made using Freeldr.sys instead of Setupldr.sys.
There are actually two problems -- one with wrong boot device name, another with display driver, which cannot show BSOD because of wrong video mode, so the screen remains black.So at the reboot, ReactOS setup started from the harddisk, but was stopped immediatly after loading blue.sys. it seemed to be a display problem.
Helllo
I can give you more details about what happens.
Setupldr.sys has been designed to load files from the CD ROM, not from the harddisk, it's true.
But when I use Setupldr.sys(Renamed Freeldr.sys) on the harddisk, setup loads the following files : Ntoskrnl.exe, Hall.dll, Kdcom.dll, C_1252.nls, C_437.nls, L_intl.nls, Scsiport.sys, Atapi.sys, Buslogic.sys, Class2.sys, Cdrom.sys, Cdfs.sys, Disk.sys, Floppy.sys, Vfat.sys, I8042prt.sys, Kbdclass.sys and Blue.sys.
I have tested. Every time I remove one of these files , Setup stops and tells it couldn't load the file I have removed , but goes on when this file has been restored.
The display disappears when Blue.sys is loaded, but I can't say Blue.sys is not supported by my system.
When I use Freeldr.sys in debug mode to get the setup, Blue.sys is loaded, but I have no display trouble. I can select the display mode, the keyboard layout, the partition, format or not format, change he name of the ReactOS folder. But in the end I have an error message "Setup failed to create system hive".
But this is not at all a display issue.
I don't understand.
Maybe I have no display problem because Freeldr.sys claims for system hive. I have to copy the config folder from the live cd to the harddisk. Maybe Freeldr.sys looks at the registry to know what display mode must be used . Maybe the diplay mode specified in the registry is supported by my system.
Setupldr.sys desn't look at the registry, because when you use Setupldr.sys, the registry is supposed not to have already been built.. Maybe Setupldr.sys use a default display mode not supported by my system.
And if I use Freeldr.sys instead of the Setupldr.sys, the system hive can't be created maybe because there is already a registry i've copied from the live cd to allow Freeldr.sys to start up.
But I'm not sure at all about what I say.
I hope developers will make a patch to allow users to select display mode used while the setup.
I can give you more details about what happens.
Setupldr.sys has been designed to load files from the CD ROM, not from the harddisk, it's true.
But when I use Setupldr.sys(Renamed Freeldr.sys) on the harddisk, setup loads the following files : Ntoskrnl.exe, Hall.dll, Kdcom.dll, C_1252.nls, C_437.nls, L_intl.nls, Scsiport.sys, Atapi.sys, Buslogic.sys, Class2.sys, Cdrom.sys, Cdfs.sys, Disk.sys, Floppy.sys, Vfat.sys, I8042prt.sys, Kbdclass.sys and Blue.sys.
I have tested. Every time I remove one of these files , Setup stops and tells it couldn't load the file I have removed , but goes on when this file has been restored.
The display disappears when Blue.sys is loaded, but I can't say Blue.sys is not supported by my system.
When I use Freeldr.sys in debug mode to get the setup, Blue.sys is loaded, but I have no display trouble. I can select the display mode, the keyboard layout, the partition, format or not format, change he name of the ReactOS folder. But in the end I have an error message "Setup failed to create system hive".
But this is not at all a display issue.
I don't understand.
Maybe I have no display problem because Freeldr.sys claims for system hive. I have to copy the config folder from the live cd to the harddisk. Maybe Freeldr.sys looks at the registry to know what display mode must be used . Maybe the diplay mode specified in the registry is supported by my system.
Setupldr.sys desn't look at the registry, because when you use Setupldr.sys, the registry is supposed not to have already been built.. Maybe Setupldr.sys use a default display mode not supported by my system.
And if I use Freeldr.sys instead of the Setupldr.sys, the system hive can't be created maybe because there is already a registry i've copied from the live cd to allow Freeldr.sys to start up.
But I'm not sure at all about what I say.
I hope developers will make a patch to allow users to select display mode used while the setup.
Last edited by fm on Sat Mar 31, 2007 11:32 am, edited 1 time in total.
After loading Blue.sys, Setupldr.sys clears the screen and starts Ntoskrnl.exe. Then Ntoskrnl.exe thinks it was loaded from CDROM and tries to access it. If there is no CD in the drive, the kernel tries to show BSOD but can't, because of video mode which Setupldr.sys sets. So the screen remains black.The display disappears when Blue.sys is loaded, but I can't say Blue.sys is not supported by my system.
Setup uses standard display mode. There is currently some incompatibility between Setupldr.sys and Bootvid.dll.I hope developers will make a patch to allow users to select display mode used while the setup.
Could you please try my Setupldr.sys from http://www.5748.nm.ru/setupldr/ , it sets different video mode. If there is some problem in the kernel, it will show BSOD with error code.
Who is online
Users browsing this forum: No registered users and 15 guests