IcemanND

Quite frequently I saw this with bad power supplies. Or an incorrectly connected one. Usually the additional 4 pin power connector wasn't connected or did not supply power.

Actually it does not have to be identical, but as HP found out don't go from Intel to AMD or vice versa. As long as you have the appropriate drivers available you can image machines across many different makes and models without issue. The biggest hang up is the HAL, but as long as you are not trying to throw in old machine that is usually not an issue any more either.

It depends upon how you want your partitions to be organized. This will probably not be entirely accurate but it should be close, can't fin the link at the moment. Starting with disk 0, each Primary partition will recieve a drive letter in order, then each the next disk and it's primary partitions, until the last disk is lettered. The the sam process will occur with the extended partitions. Obviously you can re-arrange the drive letters to your preference afterwards.

you can check the local group policies: start -> run -> gpedit.msc check under Local computer policy\Computer Configuration\Administrative Templates\Network\Network Connections\Windows Firewall Will have both domain and standard profile settings there, windows updates are under Local computer policy\Computer Configuration\Administrative Templates\Windows Components\Windows Update By default the majority of the settings default to Not configured. If the machine was is on the domain still for some reason it may have domain policies being set to do that in which case the option to change these settings will be grayed out.

I've seen a few things cause this, malware, third party security software, or a local group policy set, or the associated services being disabled or missing.

create a VM and run them under you chosen OS in the WM

See the Timeline reference for T-13: http://unattended.msfn.org/unattended.xp/view/web/13/ Windows PE is the Windows Pre-Installation environment, a CD bootable limited Windows 32-bit environment. See the Windows PE forum here for more.

http://www.msfn.org/board/index.php?showto...st&p=674778 = create a WIM image of the system that can be burned to bootable DVD or put on a bootable thumbdrive and then can be used to restore the system.

During Windows XP setup you can create as many partitions as the os will allow, but you can only format the partition you are installing the OS on. If you want to format the other partitions you can do it during the t-13 phase of setup witha command script, or use Windows PE to create and format all of your partitions before beginning any other portion of setup.

Who is the monitor manufactured by, and model? They may have a specific driver you have to use.

app is called GDISK, may not be in the home version, might only be in the enterprise versions of ghost.

Ghost comes with its own partitioning utility.

Not for XP that I know of.

Need I say why? CLOSED

1. open the WAIK Command window. 2. mountrw your boot WIM file 3. Run the PEIMG command to adjust the scratch size in the mounted image using /SCRATCHSPACE flag to set the size of the drive you want (in this case 128Mb) - peimg.exe /SCRATCHSPACE=128 c:\temp\mount\windows replace c:\temp\mount\windows with the folder your image is mounted to. 4. unmount and commit changes

does your script return anything? will it return info if you query for only one item, instead of both samAccountName and distinguishedName?

ghost will allow you to image a machine to a cd/dvd but not the same one you booted from.

everything that is in the BOOT.WIM file gets loaded into memory. The error you are getting usually references a memory error in that you have run out. If you have a 400-500mb WIM compressed it has to decompress 500+mb into the system memory. If you are using a USB device put the large files (i.e. disk images) at the root of the device, if you are making cd's put them in the ISO folder before creating your ISO.

with an image that big I would lean towards a memory issue. By default everything in the WIM is loaded into memory and that is where PE 2 runs from if you are leaving the CD/usb drive in the machine while using PE, put the large files in the iso folder instead of into the WIM structure, then they are available but not loaded into memory.

if "%username%"=="user1" goto :user1 if "%username%"=="user2" goto :user2 rem repeat as needed for each user goto EOF :user1 rem do what you need goto EOF :user2 rem do what you need goto eof

Go back to the molex connector and follow the 4 fatter wires out, do they go directly into the PSU without a connector in between?

Usually when they hook something up like that it is an adapter if you follow the four wires (red, black x2 and yellow out of that molex it goes straight into the PSU?

Should work just fine, as long as you have all of the hardware drivers for it.

That's a standard ATX power supply, the power supply should slide forward in case once the screws are removed. There may also be a clip holding it in place, I'm not familiar with that particular case. And the video doesn't help too much, too blurry. if you follow the wires to the from they are likely going to a fan and should have a connector on them somewhere you can disconnect.

taking a guess, is the HD a SATA drive? If so you either need to change the controller type in the BIOS from AHCI to Compatibility (or equivalent) or integrate the SATA controller drivers into your XP CD.