zorphnog

If its an authentication issue i would try using the domain in your username (i.e. server=master username=admin would be username=master\admin). I don't know how you are trying to authenticate to whatever server you are trying to connect to, but I have experienced authentication issues when using the "net use" command within PE and the domain name fixed it. That might work, but as Jazkal said, a better explanation of what exactly you are trying to do would help.

I've found that for some reason you always have to specify the full path of the file for mshta to execute properly. So even if you are in the folder where the .hta file is located, you still have to type the full path. X:\Windows\System32>mshta.exe X:\Windows\System32\wizard.hta

I've had the same problem and found that you always have to specify the domain when entering the username. So try using 192.168.10.30\guest as your username.

Looking at the latest driver files, I notice that megasas.sys is referenced as a source file in the inf. Try adding it to your drivers folder.

You can use the built-in FILEMOVE or FILECOPY command to move/copy files. Both commands are used the same way. If you are trying to move files from a CD to the HDD then you will need to use FILECOPY since you cannot move files from read-only media. Syntax: FILECOPY [source] [destination] Examples: //copy all files in CopyFiles folder to components folder FILECOPY "%WPIPATH%\Install\CopyFiles\*.*" "C:\Program Files\foobar2000\components" //copy lame.exe to components folder FILECOPY "%WPIPATH%\Install\CopyFiles\lame.exe" "C:\Program Files\foobar2000\components" Make sure you use quotations for any paths that contain spaces, and that your destination folder exists (use MAKEDIR command to create a directory).

What kind of processor was used during sysprep and what kind is on the board that doesn't work? I've ran into similar symptoms of stopping at the boot screen that are a result of different HALs. Just a thought.

I'm not sure what your problem is, but I use a KVM switch and PXE boot all the time and have had no problems. I would think that it is either a hardware issue with the computer (not the switch) or a bad WinPE image. You may want to rebuild the WinPE image, but just to eliminate some variables I would try without the switch first.

Your using msiexec incorrectly. You do not have msiexec.exe in your Install\McAfee80 folder. msiexec.exe is in your System32 folder so you can call it from anywhere. You should be calling your install like so: cmd1[pn]=['msiexec.exe /i "%wpipath%\\Install\\McAfee80\\VSE800.msi" /qb'];

I've just tried this out on my 60GB usb hard drive and confirmed that it works. Here are the steps I used. Run diskpart (v6.0.6000): select disk 1 clean create partition primary size=10240 create partition primary select volume 2 //10GB USB partition format fs=fat32 label="VISTA_BOOT" quick active assign select volume 3 //46GB USB partition format fs=ntfs label="USB_DISK" quick assign exit Copy Vista contents to USB drive: xcopy d:\*.* /s /e /f e:\ Just make sure that you mark the VISTA_BOOT partition as active and you should be good to go. *EDIT: I just tried it with NTFS format and it works also.

Are you entering the domain name along with your user name? I've found that on my network I always have to enter the domain name with the username to connect (i.e. /USER:server\admin). I don't really see how that would have anything to do with the clock, but its a problem i've ran in to trying to map drives.

Post your config file so we can have a look at your conditions.

All the documentation that I've read says that it has to be formatted in FAT32 as a single partition spanning the entire drive, although I'm not sure why.

Have you checked user permissions on the files?

So I guess nobody has any ideas on this? Comments?

I'm not quite sure if I understand you correctly. The script I posted queries WMI for all optical drives attached to the system and returns a collection of the optical drives. In this case I am assuming that there is only one optical drive attached to the system (if colItems.Count = 1). The optical drive letter is written to the setOpticalVolume.txt file (txtfile.WriteLine "SELECT VOLUME " & objItem.ID) where objItem.ID is the drive letter of the optical drive. This setOpticalVolume.txt file is written during the execution of the script so it will always correspond to the current drive letter of the optical drive. I would use it as a part of your cmd file. Note: .cmd file, cleanPartitionFormat.txt, and getOpticalVolume.vbs are all in the same directory. @rem Script to clean partition and format HDD diskpart /s cleanPartitionFormat.txt @rem Run the WMI script i posted cscript getOpticalVolume.vbs @rem Assign Z to optical drive letter diskpart /s setOpticalVolume.txt If I understand your situation correclty this should work. Have you even tried it?

You could use something like this to create a diskpart script to set the optical drive letter to Z, assuming you only have one optical drive connected. strComputer = "." Set objWMIService = GetObject(_ "winmgmts:\\" & strComputer & "\root\cimv2") Set colItems = objWMIService.ExecQuery( _ "Select * from Win32_CDROMDrive") Set fso = CreateObject("Scripting.FileSystemObject") Set txtfile = fso.CreateTextFile("setOpticalVolume.txt") if colItems.Count = 1 then for each objItem in colItems txtfile.WriteLine "SELECT VOLUME " & objItem.ID txtfile.WriteLine "ASSIGN Z" txtfile.WriteLine "EXIT" next end if txtfile.Close Run the WIM script, which will create setOpticalVolume.txt. Run setOpticalVolume.txt as a diskpart script.

Nope. Just put in a command to wpi.hta in the GUIRunOnce section of your sysprep answer file. sysprep.inf ... [GUIRunOnce] Command0="E:\WPI\wpi.hta" ...

Due to a disconnected environment, I have to deploy all systems via DVD. I am trying to apply a .wim image that is split onto two discs. The image is a little over 5GB and I can only use SL DVD's so I had to split it into two .swm files. I've built a PE DVD boot solution that loads PE, partitions, formats, and begins applying my image. I've been using imagex to try and apply the image: imagex /apply e:\custom.swm 1 c:\ OR imagex /ref e:\custom*.swm /apply e:\custom.swm 1 c:\ In either case, imagex fails when the second .swm file is needed. I'm fairly sure its just a limitation of imagex. However, I've ran accross several articles about the createspannedshares.cmd utility located in the samples folder of the WAIK. This utility allows you to span the vista installation DVD accross several CD's, so I know that it is possible to apply an image spanned accross multiple discs. Although, I'm guessing that the vista installation uses the wimgapi to apply their images instead of imagex. My question is whether anyone knows of a way to apply an image that is spanned accross multiple discs? Any tools that will allow me to do this, or am I completely missing something trivial? I'm trying to avoid having to develop something with wimgapi.

The easiest way to accomplish this is to make a batch file to copy the files an then install the application. This way you can use the %temp% variable. Something like: @echo off echo Copying files to local disk... mkdir "%temp%\something" xcopy * "%temp%\something" /E /Y /F echo Installing application... cd "%temp%\something" start /wait msiexec.exe /i something.msi TRANSFORMS=something.mst /qn cd .. rmdir something /S /Q ...then put that batch file in the same folder as your installation files.

You could use imagex to mount the image and make the appropriate changes. Use /mountrw to mount the image and /unmount when you are done.

You should not be altering the program.js file. All your configuration information for the applications needs to go in your config.js file. I separated the files for you. Just drop them in the WPIScripts folder. config.js program.js

Have you changed any of the settings? If not, I would say you should just download it again. If you have changed some settings, then you need to open your useroptions.js file and change 'ShowExtraButtons' to equal 'true'. This will allow you to edit your options and config file. You probably need to load your config file again through the config editor.

There is not an "Unattended" mode per se, but if you want to be able to start an installation without any user interaction you can use timer=0.

Welcome to WPI. 1. The supported commands are referenced in the FAQ section of the manual. Supported commands include: options= (load an options file), config= (load a config file), check= (check applications in a configuration), timer= (set timer in seconds i.e. 1 or 0 for unattended mode). 2. To re-instate the links, you will need to edit your useroptions.js file located in the WPIScripts directory. In the file, edit the variable 'ShowExtraButtons' to equal 'true'. Good luck.

Hmm...Here's an interesting test. Try running WPI from the network with your config file on your local machine. Download your config file then run "WPI.hta config=C:\config.js". I wonder if that would make any difference. I've tried it on my network share (1Gbit/s network on to a XP client 2.00GHz, 2GB RAM), but I haven't noticed a discernable difference in times. Of course I'm not seeing the same issue either, I have about 40 programs and it loads in about 1.5 seconds either way. I guess its worth a try though.