Search options (Page 3 of 6)

Hi Echo_platoon.
Can you tell us before-hand if this driver presents problems with installing when you do NOT have the hardware?

You are an old timer here and a trusted hand, and I think you have seen that we get some impossible requests.
For instance, when we use driver extraction tools, we sometimes see that nothing the team uses gets a usable driver, and then we either get in a situation where:
1; person with the hardware does not know how to extract the full set of files in usable folder.
2; driver install routine is propriatary to installer and extraction tools cannot extract the main from a non existing main because main deleted temps, and the DL exe wont extract without running that routine.
3:we get no response, and miss only a few files..

MsDosInitiated = "0"

If this setting is on "0" it will inform Setup that you are installing from CD, put a value of 1
if you use only diskettes to boot.

Your close Tmaniac.

OfflineSysprep is run after the image has been deployed to the machine. The deployed image has sysprep applied to it. At least this is from my understanding. You have to pxeboot or cd boot into a PE type environment (LiveXP, UBCD4WIN, Reatago, etc.) to run OfflineSysprep after the image has been layed.

Use:

· For SysPrepping a Windows XP or 2003 32-bit partition that is hardware independent (yes, hardware independent!) while offline (yes, a non-booted Windows partition!)

· For SysPrepping a Windows XP or 2003 32-bit partition that is hardware independent while booted in Windows but with a partition/drive to sysprep attached and assigned a drive letter (ie a non-booted WinXP/2003 partition).

· You can use an unattended solution by locating sysprep.inf in the \userfiles\ directory of the OfflineSysPrep plugin or in the \userfiles\ folder of the Windows version.

Using OfflineSysPrep:

1. From 'Select Drive to SysPrep' options, select the XP/2003 partition/drive you want to sysprep (you are only presented with those that have boot.ini in root to cut down options);
2. From 'Select User Profile from Drive', select a user account;
3. Select a HAL update option from those listed;
4. Optionally select a path to be recursively scanned for inf drivers for pnp to detect. Fixed drive letters will be altered to %SystemDrive% (eg 'z:\sysprep\drivers' will be altered to '%SystemDrive%\sysprep\drivers') so path to be specified must be one which will be located on the offline system's %SystemDrive% or in other words the partition\drive that is undergoing sysprepping. File scanning recursion is performed by either SPDrvScn or SetupCopyOEMInf. SetupCopyOEMInf is used if the 'Advanced' option 'Complete OfflineSysPrep operations without running sysprep.exe' is selected. If sysprep is to run, SPDrvScn will be used. However, if it is desirable to not have sysprep itself perform the pnp (ie, 'PnP/Detect non-plug and play hardware' will not be selected from sysprep's interface), then select 'Use SetupCopyOEMInf (if not selecting sysprep pnp)' from the 'Advanced' options;
5. Optionally specify 'Advanced' options by clicking 'Advanced' and then the desired options from those listed;
6. Click 'Apply';
7. Now use SysPrep as usual, which should automatically start.

PSS it may help if you add me to your IM, so we can expidite the exchange of info that is inevitable.
we can then summarize our findings in the forum for more consise reading by a user.

You are absolutely right! I was just doing this temporarily to get all the kinks out first. I was actually going to do radio boxes instead.

@Helmi - 14 hours, and no sign of a finish. I was watching the sysprep process in RAM, it keeps jumping up between 28352kb and 23368kb of RAM, and doesn't seem to do anything.