• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Tsaukpaetra

  1. I've got my Linux-based RIS running, and booting Windows 7 setup. After attempting to add Windows XP (for backwards compatibility), I find myself rather stuck trying to get to Stage 2 of the setup process. I get to the point where "Setup is starting Windows" and I see the bootvid, but moments later I get a BSOD with the following information: PROCESS1_INITIALIZATION_FAILED STOP: 0x6b (0xC...3B, 0x2, 0x0, 0x0) (Shortened for your viewing pleasure ) The code 3B indicates that STATUS_OBJECT_PATH_SYNTAX_BAD [0xC000003B] :: The object path component was not a directory object. Running Wireshark, I captured data that indicates that Windows Setup is in fact querying my Samba server and logging in (with no password, something that was explicitly allowed) but stops there. Attached are the details in text format. Packets.txt Problem is, that even though the request does seem valid (mostly), Windows Setup chokes for no apparent reason. Any ideas on how to fix this? I'm quite lost on anything else I can do for this...
  2. Greetings all! I was searching for a slightly nicer looking bootup application for Windows PE to replace most of the GUI of xpeinit.exe. Specifically, its' GUI. I am using the ReaToGo version of XPE fyi. I can go through the process of adding all of the commands that will be launched, however I have found that since the sound-card is not initialized yet (happens in the second stage of setup) so when the program tries to play the "ticking" sound for the timer timeout it will semi-crash trying. (Also the actual "wizard" window fails to load or do anything of consequence) Unfortunately no errors popup usually (and if they do I can't trace where the error in the code is since it doesn't tell me any useful information about included code...), so I'm lost in figuring out how to get this to work properly. This far I have hacked down the code to remove the "Abort" features (Since aborting the system's startup is usually disastrous! ) However I can do nothing to prevent the user from just pressing Alt-F4 (on accident I suppose) Anyone have suggestions for this?