I can confirm this behaviour. This happened after (I think it was)
GvG's changes that broke the bootcd/livecd the first time were
recommitted. After it hangs, I can't even break into KDB, so I have
no idea what is going on..
On 4/26/05, Hartmut Birr <hartmut.birr(a)gmx.de> wrote:
Hi,
since some time, I'm not able to install ros from the bootcd over an
existing ros. The first stage setup works perfect. The second boot hangs
after loading most of the drivers. The last line on the debug port comes
from framebuf.dll:
...
DriverBase for \??\E:\ReactOS\system32\win32k.sys: 9d62b000
DriverBase for \??\E:\ReactOS\system32\freetype.dll: 9d803000
DriverBase for \SystemRoot\System32\kbdgr.dll: 9d78f000
(ntuser/desktop.c:574) IntShellHookNotify: No desktop!
(ntuser/desktop.c:574) IntShellHookNotify: No desktop!
(ntuser/desktop.c:574) IntShellHookNotify: No desktop!
DriverBase for \SystemRoot\System32\framebuf.DLL: 9dfab000
Has anyone the same problem? The install works again, if I delete all
registry files from the existing installation. Usually I use the 'make
install' command to install ros over the network on my test machines.
- Hartmut
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev
--
"<tinus_> and also win32k should be fixed up a bit"