When resolution is set to VESA, ReactOS will fail to boot for the first time.
Usually, on the same machine, ReactOS works well on QEMU.
640x480x16 VGA mode should be working
If the bug persists on your machine, please post your specs as well as comments (if for example, even vga mode isn`t working).
ReactOS 0.3.1 freezes at boot screen
Moderator: Moderator Team
ReactOS 0.3.1 freezes at boot screen
Last edited by Haos on Sun Apr 01, 2007 4:19 pm, edited 1 time in total.
-
Paul Conway
- Posts: 10
- Joined: Sun Nov 05, 2006 9:36 pm
no luck with virtual pc 2004
I tried to run ReactOS 0.3.1 using Virtual PC 2004.
No luck with either the live CD or the install CD.
In both cases it hangs when the logo screen appears.
I am confused by the preceding comments in this thread.
Is there something I can do that would make it work, or not?
Don't know what QEMU is. Never tried that.
I gave Parallels a try-out a while ago but seemed much
the same as Virtual PC 2004 so I went back to that.
Is Parallels worth trying again to make 0.3.1 run?
No luck with either the live CD or the install CD.
In both cases it hangs when the logo screen appears.
I am confused by the preceding comments in this thread.
Is there something I can do that would make it work, or not?
Don't know what QEMU is. Never tried that.
I gave Parallels a try-out a while ago but seemed much
the same as Virtual PC 2004 so I went back to that.
Is Parallels worth trying again to make 0.3.1 run?
-
Paul Conway
- Posts: 10
- Joined: Sun Nov 05, 2006 9:36 pm
non-virtual trials
I burned CDs of ReactOS.ISO and ReactOS-LiveCD.ISO.
I tried each of them out directly on my PC, no emulation.
Both froze at the ReactOS logo screen.
(With ReactOS.ISO I was able to do the install ok,
it was the boot thereafter where it froze.)
My machine is home-built.
It has an Asus motherboard, with a 1.8 GHz 32-bit AMD
processor (equivalent to 2.4 GHz Intel), 1 GB RAM, and
an NVidia video card that has 64 MB RAM and is DirectX
9 capable.
Ordinarily I run Windows 2000, various Linuxes,
Vista Beta 2, etc, and all work fine.
Is there a problem supporting AMD processors?
I tried each of them out directly on my PC, no emulation.
Both froze at the ReactOS logo screen.
(With ReactOS.ISO I was able to do the install ok,
it was the boot thereafter where it froze.)
My machine is home-built.
It has an Asus motherboard, with a 1.8 GHz 32-bit AMD
processor (equivalent to 2.4 GHz Intel), 1 GB RAM, and
an NVidia video card that has 64 MB RAM and is DirectX
9 capable.
Ordinarily I run Windows 2000, various Linuxes,
Vista Beta 2, etc, and all work fine.
Is there a problem supporting AMD processors?
This is other thing. This logo freeze is supposedly fixed in trunk version. I cant confirm this yet, as other bugs were introduced, thus on my HW, trunk is freezing at install (described in thread - freeze after blue.sys).
I`ll try to setup some Celeron 300 machine and test ROS there.
Paul could you please try recent trunk on your hardware?
I`ll try to setup some Celeron 300 machine and test ROS there.
Paul could you please try recent trunk on your hardware?
-
Paul Conway
- Posts: 10
- Joined: Sun Nov 05, 2006 9:36 pm
tried vga - ok
Sorry I was using the Vesa driver shown as a default.
I did not realise I had to select VGA explicitly.
I re-installed, selecting VGA.
Now I get it to boot ok.
Once it boots, it asks me to install audio drivers,
ethernet drivers, and video drivers. It did not get
far with any of those, leaving me in the 640 x 480
mode.
My video card is an NVidia MX440-T8X with 64 MB RAM.
My Asus board is a KT4V-series, and it has an ethernet
controller that is not recognised directly by Windows 2000,
so it has to have its own driver installed. I might try
putting in a bog-standard NIC just out of curiosity,
to give ReactOS an easier time installing a driver for it.
Anyway I am up and running, albeit with big pixels.
Sorry for all the fuss.
I did not realise I had to select VGA explicitly.
I re-installed, selecting VGA.
Now I get it to boot ok.
Once it boots, it asks me to install audio drivers,
ethernet drivers, and video drivers. It did not get
far with any of those, leaving me in the 640 x 480
mode.
My video card is an NVidia MX440-T8X with 64 MB RAM.
My Asus board is a KT4V-series, and it has an ethernet
controller that is not recognised directly by Windows 2000,
so it has to have its own driver installed. I might try
putting in a bog-standard NIC just out of curiosity,
to give ReactOS an easier time installing a driver for it.
Anyway I am up and running, albeit with big pixels.
Sorry for all the fuss.
-
Paul Conway
- Posts: 10
- Joined: Sun Nov 05, 2006 9:36 pm
using the trunk
I presume you mean within the source repository,
so I would need to do my own build etc.
I am not at a stage at which I am able to do that.
I have only used the released ISOs.
When I have more time (if ever!) I would certainly
like to be more involved, but for now I am not able
to do so, much as it intrigues me.
so I would need to do my own build etc.
I am not at a stage at which I am able to do that.
I have only used the released ISOs.
When I have more time (if ever!) I would certainly
like to be more involved, but for now I am not able
to do so, much as it intrigues me.
SVN server builds an ISO every time someone makes a commit.
http://svn.reactos.org/iso/
Just go to the highest numbered bootcd. It can be either debug or release, doesn't really matter which you choose.
http://svn.reactos.org/iso/
Just go to the highest numbered bootcd. It can be either debug or release, doesn't really matter which you choose.
Progammers Duty
A progammer inserts visible milestones. So the exact state of the machine prior to the error is known.
-
mikedep333
- Posts: 167
- Joined: Sat Oct 01, 2005 1:48 am
- Location: United States
Re: Progammers Duty
You can bombard the user with info in your program if you want, but a ReactOS programmer uses debug information. Here is one method of getting it.ubion wrote:A progammer inserts visible milestones. So the exact state of the machine prior to the error is known.
http://www.reactos.org/wiki/index.php/D ... ut_to_file
-
Paul Conway
- Posts: 10
- Joined: Sun Nov 05, 2006 9:36 pm
tried bootcd-26289-rel.iso
As per recent suggestion...
Well I finally found some time so
I went to the iso directory and downloaded
the latest bootable image ie
bootcd-26289-rel.iso which I tried in Virtual PC
but it did not run. No matter...
But then I burned it to a CD and tried to boot from it
to install to a blank hard disk. The blue boot screen came
up and there were a few messages on the bottom line
saying loading ntkernel.exe etc.
Then it hung.
My PC has an AMD processor.
I don't have any Intel-based PCs that I could try out
at the moment.
I do have an old machine with a relatively dumb
graphics card (no acceleration) that I could try,
incase the hang is to do with my NVidia card.
However, let's suppose I do get this latest version to boot,
and install it ok. I have an application program of my own
(a text editor) which would execute under ROS 0.3.0 up to
the point where it actually opened its window on the screen.
So far under ROS 0.3.1 I cannot get it to run at all.
So I am wondering what in general is the state of Win32
functions support. I presume the support for them comes
from WINE? Or does it? How does ROS support Win32 funcs?
On the assumption that WINE sits on top of a Linux/Unix core,
how would WINE work with ROS, given that ROS, as I understand
it, is not really a Linux/Unix, but an implementation of the basic
functionality of a true Windows-like OS? So how then does WINE
work with it? Or is that not what happens?
Is there a list of Win32 functions and their current
implementation state, so I can figure out which ones
I can use, and which ones to avoid?
Obviously my text editor uses file i/o, dir scanning,
and GUI funcs (it uses MDI). It can also make use of
some common controls and COM, but I can suppress
those features if need be.
Well I finally found some time so
I went to the iso directory and downloaded
the latest bootable image ie
bootcd-26289-rel.iso which I tried in Virtual PC
but it did not run. No matter...
But then I burned it to a CD and tried to boot from it
to install to a blank hard disk. The blue boot screen came
up and there were a few messages on the bottom line
saying loading ntkernel.exe etc.
Then it hung.
My PC has an AMD processor.
I don't have any Intel-based PCs that I could try out
at the moment.
I do have an old machine with a relatively dumb
graphics card (no acceleration) that I could try,
incase the hang is to do with my NVidia card.
However, let's suppose I do get this latest version to boot,
and install it ok. I have an application program of my own
(a text editor) which would execute under ROS 0.3.0 up to
the point where it actually opened its window on the screen.
So far under ROS 0.3.1 I cannot get it to run at all.
So I am wondering what in general is the state of Win32
functions support. I presume the support for them comes
from WINE? Or does it? How does ROS support Win32 funcs?
On the assumption that WINE sits on top of a Linux/Unix core,
how would WINE work with ROS, given that ROS, as I understand
it, is not really a Linux/Unix, but an implementation of the basic
functionality of a true Windows-like OS? So how then does WINE
work with it? Or is that not what happens?
Is there a list of Win32 functions and their current
implementation state, so I can figure out which ones
I can use, and which ones to avoid?
Obviously my text editor uses file i/o, dir scanning,
and GUI funcs (it uses MDI). It can also make use of
some common controls and COM, but I can suppress
those features if need be.
Who is online
Users browsing this forum: Yandex [Bot] and 16 guests