chrisf826

This is the first time i have ever posted here after lurking for a couple years as a guest I really enjoyed this guide and the rest of the msfn site, has given me a lot of great ideas on customizing my xp and 2003!. I have been trying to sort out where the failure is for low memory systems on windows home server. Apparently, the WPE 2.0 environment WILL function without errors on 256 mb of ram, if you access a command prompt and create a pagefile on the hard drive, via wpeutil CreatePageFile <pagefile_name>, i had to edit winpeshl.ini and remove qs.exe and add cmd.exe in this file. This remaining stuff i did was in Normal boot mode. did the rest in a full windows windows sbs install. I unhid the whs optional components INF after i installed the whs component exe's and right click installed the whsoc.inf file. Then accessed cmd.exe again, then entered install.cmd from \files\install on the whs media then rebooted. It appears qs.exe then exhibits strange behavior and bypasses the RAM check on the next reboot, the strange behavior is exhibited by using the bogus registry keys install.cmd entered, install.cmd made the assumption the media is on the drive you are booting from. The weird thing as well, that the media you called qs.exe from is now drive X: on reboot and your not even on PE!! and the install is hosed when i didnt do the previous steps before. i could NOT even logon. I have a suspicion that whs is convertable if it can be figured out how to do this procedure without locking yourself out. or having strange drive assignments. i would like to have otheres test this out on a non important installation. It seems you need a good portion of the dvd directory structure and files in the root of the drive your attempting this on. 1). Unhide the windows components hidden in sysoc.inf, from your hard drive 2). install the inf from \windows\inf\whsoc.inf. from your hard drive. 3). Installed the whs components in \whs on your install media. 4). enter install.cmd from \files\install from your install media while in a normal windows session. 5). either reboot and allow the system to run qs.exe on next logon.