Hello,
By accident I bumped onto a video about ReactOS by PXE booting so I checked the project once again after a while (was very primitive the last time I checked this OS).
For some reason the latest builds don't show anything after selecting what to boot so it looked like it crashed.
When I was just about to leave work I noticed that pressing a key suddenly brings up the GUI or text logging.
Unfortunately the text logging one displayed some error that prevent booting into the "eplorer".
I don't know if it's driver related as it happends in the (pre)boot.
As I wrote earlier I left work and my forum activation mail still didn't arrive so I will post the error tomorrow.
Besides that... does anyone have any experience with ReactOS booting from PXE and acting as a thin client (only allow RDP connections) ?
Can I just tweak the ISO file to wipe everything that's not needed (reading 140Mb via PXE TFTP still takes time so this should be reduced to the minimum)
pxe booting
Moderator: Moderator Team
Re: pxe booting
I installed it on my home laptop in VirtualBox, boots quite fast.
I only noticed 1 issue so far.
When I enter a dosbox I can't type. only the enter key seems to respond?
I only noticed 1 issue so far.
When I enter a dosbox I can't type. only the enter key seems to respond?
Re: pxe booting
A "dosbox"? What do you mean? (there is no DOS in reactos, unless you start a 16-bit DOS app, in which case a NT virtual DOS machine is started)
Re: pxe booting
command prompt console thingy is what I meant.
Re: pxe booting
hmm... now my typed chars appears. weird 

Re: pxe booting
I assume you refer to this video by Jedi-to-be, ReactOS PXE boot with 3rd party ethernet driver and RDP connection to Windows 7.gvb wrote:By accident I bumped onto a video about ReactOS by PXE booting...
This ReactOS Wiki page, Building PXE-ready ReactOS, is interesting.
Re: pxe booting
Hello,
It was already booting from PXE/TFTP to some degree.
Here's what I get in the text logs, well what I can still see on the screen.
(ntoskrnl/io/pnpmanager/pnpmgr.c:4059) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xC0000bb
(ntoskrnl/io/pnpmanager/pnpinit.c:321) IopOpenRegisteryKeyEx() failed with status C0000034
(ntoskrnl/io/iomgr/driver.c:734) ZwOpenKey() failed with status c0000034
(ntoskrnl/io/iomgr/driver.c:734) ZwOpenKey() failed with status c0000034
(ntoskrnl/io/pnpmanager/pnpmgr.c:4059) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xC0000bb
(ntoskrnl/io/pnpmanager/pnpinit.c:321) IopOpenRegisteryKeyEx() failed with status C0000034
(ntoskrnl/io/iomgr/driver.c:734) ZwOpenKey() failed with status c0000034
(ntoskrnl/io/iomgr/driver.c:734) ZwOpenKey() failed with status c0000034
(ntoskrnl/io/pnpmanager/pnpmgr.c:4059) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xC0000bb
(ntoskrnl/mm/ARM3/sysldr.c:3024) ZwOpenKey() failed for '\Systemroot\system32\drivers\vbemp.sys' with status 0xc000003a
(drivers/usb/usbehci/hardware.cpp:1051) waiting 50 miliseconds for port to recover after reset
(ntoskrnl/io/iomgr/iomgr.c:566) IopCreateArcNames failed: c0000034
fatal system error: 0x00000069 (0x00000000,0x00000000,0x00000000,0x00000000)
Entere debugger on embedded INT3 at 0x0008:0x8093f178
It was already booting from PXE/TFTP to some degree.
Here's what I get in the text logs, well what I can still see on the screen.
(ntoskrnl/io/pnpmanager/pnpmgr.c:4059) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xC0000bb
(ntoskrnl/io/pnpmanager/pnpinit.c:321) IopOpenRegisteryKeyEx() failed with status C0000034
(ntoskrnl/io/iomgr/driver.c:734) ZwOpenKey() failed with status c0000034
(ntoskrnl/io/iomgr/driver.c:734) ZwOpenKey() failed with status c0000034
(ntoskrnl/io/pnpmanager/pnpmgr.c:4059) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xC0000bb
(ntoskrnl/io/pnpmanager/pnpinit.c:321) IopOpenRegisteryKeyEx() failed with status C0000034
(ntoskrnl/io/iomgr/driver.c:734) ZwOpenKey() failed with status c0000034
(ntoskrnl/io/iomgr/driver.c:734) ZwOpenKey() failed with status c0000034
(ntoskrnl/io/pnpmanager/pnpmgr.c:4059) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xC0000bb
(ntoskrnl/mm/ARM3/sysldr.c:3024) ZwOpenKey() failed for '\Systemroot\system32\drivers\vbemp.sys' with status 0xc000003a
(drivers/usb/usbehci/hardware.cpp:1051) waiting 50 miliseconds for port to recover after reset
(ntoskrnl/io/iomgr/iomgr.c:566) IopCreateArcNames failed: c0000034
fatal system error: 0x00000069 (0x00000000,0x00000000,0x00000000,0x00000000)
Entere debugger on embedded INT3 at 0x0008:0x8093f178
Re: pxe booting
for some reason the builds after livecd-70313-dbg.7z are not booting to the selector at all.
Who is online
Users browsing this forum: No registered users and 1 guest