IcemanND

Try changing the red highlighted text to be the same variable name.

My tutorial is written to deploy an image. But you can start the xp install instead of deploying an image. So instead of running imagex to put the image down kick off the windows installation with WINNT32

This will show you how to create you PE cd, http://www.msfn.org/board/GUIDE-Creating-W...st&p=674778. You don't put the XP cd ISO on the PE cd you put the contents of that cd on the PE CD, and all you really need to copy over is the i386 folder structure. If you have an $OEM$ folder structure you need to pull it out of the i386 folder and place it in the same location as the i386 folder. Then run WINNT32.exe with the appropriate switched to kick off the installation.

check out the REG.EXE command. You will need to LOAD the offline registry, make your changes and then UNLOAD the registry hive. Same as using LOAD/UNLOAD HIVE from within regedit.

Sounds like you need some chipset drivers and the High Definition Audio patch, but that is a guess.

Do you want to do it silently or could it be a manual step?

sounds like you have something else out there publishing the printer to the machine. How was it originally installed on these machines?

[MOVED] While we are at it I believe you are looking for this: http://unattended.msfn.org/unattended.xp/view/web/77/

Here is the beginning of a script I use to replace printers on machines, it deletes all of the installed printers and their associated ports except for the Microsoft Office Document Image Writer and the Adobe blah, blah, blah printer, then deletes the ports. Then I add the desired drivers. This runs as a gpo startup script, it can run as a logon script if the user has admin rights. strComputer = "." Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") set objNewPort = objWMIService.get("Win32_TCPIPPrinterPort").SpawnInstance_ Set objPrinter = objWMIService.Get("Win32_Printer").SpawnInstance_ objWMIService.Security_.Privileges.AddAsString "SeLoadDriverPrivilege", True Set objDriver = objWMIService.Get("Win32_PrinterDriver") set colInstalledPrinters = objWMIService.ExecQuery ("Select * from Win32_Printer") set objDictionary = CreateObject("Scripting.Dictionary") 'get list of installed printers and delete everything that does not have adobe or microsoft office in the displayed name for each instPrinter in colInstalledPrinters if (instr(instPrinter.Name, "Adobe")=0) and (instr(instPrinter.Name, "Microsoft Office")=0) then instPrinter.Delete_ end if next 'get new list of installed printers, should only be microsot and adobe add to dictionary for easier search and compare set colInstalledPrinters = objWMIService.ExecQuery ("Select * from Win32_Printer") For Each instPrinter in colInstalledPrinters objDictionary.Add instPrinter.PortName, instPrinter.PortName Next 'check for installed ports against those listed in dictionary if they don't exist delete them. Set colPorts = objWMIService.ExecQuery ("Select * from Win32_TCPIPPrinterPort") For Each objPort in colPorts If objDictionary.Exists(objPort.Name) Then 'used to do something here but don't anymore just left it for future use. Else ObjPort.Delete_ End If Next

Here is what I did with mine: http://www.msfn.org/board/Utility-Driver-B...st&p=568879 Query WMI for Win32_PnPEntity, use this information to get some info about the device from the registry, like Driver Class, driver inf name, Driver provider name, amongst others. Then I dig through the associated INF file to get the CAT file and the system files and copy them from the system to a folder structure to match the original install folder structure.

Dell repackages all of the drivers for their systems. And rarely update them to the newer drivers released by the chip manufacturers.

In PE you need IN.COM to be written to the RAM drive usually X: not D:

in what line do you get the error message from? I would guess the net use line. But it works as is for me

to my knowledge there are no new drivers added to XP via SP3.

actually they are not from the disk manufacturer but rather the disk controller manufacturer. Check your vista device manager and see what device the hard drives are connected to then find the drivers from the manufacturer for your device. Then if you have a floppy (not likely since the machine came with vista and it being a laptop) you can put them on the floppy and press F6 when you boot from floppy. Or you could slipstream the drivers into the XP source as textmode drivers. The third option is to check the systems bios and see if there is a compatibility setting for the SATA controller and change it from native to compatibility mode and see if the drive is seen then.

The screensaver is force on me, but I normally lock or hibernate my machine when I walk away depending upon how long I am gone and where I'm going next. I have a laptop and 4 offices.

MOVED. You are missing a section in your sysprep file to have it process the mass storage controllers. Put this before [sysprepmassstorage]: [sysprep] BuildMassStorageSection = Yes

Sigh, search, search, search. See for numerous different examples, may need some slight modification: http://www.msfn.org/board/index.php?showtopic=74352

Not without getting physical access to his machine.

"generally inexpensive part!" since when? The laptop LCD is the first or second most expensive part in a laptop depending upon model. It fights with the laptop motherboard for position. Expect anywhere from $150 to $500(US) depending upon size and age. Possibly more, quite often you are better off buying a new laptop, this is reason I always tell people to get accidental damage protection warranties on laptops, especially for students.

Not sure exactly what your error is, but did you create the database with the table and then create a DSN to it? If not see (last half): http://www.microsoft.com/technet/scriptcen...k.mspx?mfr=true Wasn't sure if you got the scrit from there or the scriptcenter.

How did you do this? Did you put them in the SysprepMassStorage section and add BuildMassStorageSection?

You mean something like this: http://www.msfn.org/board/index.php?showto...st&p=674778 you need to be sure to account for changes in the HAL between the VM and your physical machine.

http://www.myitforum.com/articles/15/view.asp?id=8997 http://jimtsay.googlepages.com/mysysprep http://www.altirigos.com/vbulletin/imaging...3.html#post5960

technically XP will not support raid unless you replace some files in it with files from server 2003. I wouldn't exactly call the "striped volume" raid. You would really be better off with a hardware raid.