IcemanND

[data] autopartition=1 and [unattended] Repartition=yes Your install is detecting an existing install on the first hard disk so it is installing on the next available disk/partition that does not contain an install of windows. Add the above to your answer file and it will delete the existing partition on the first disk, repartition to the full disk size and install.

stop7b refers to not being able to find the correct driver for the hard disk controller. What is the reason you are using the -ib switch with ghost? Or is that what fixed the xp problems with ghost 7? Been awhile since I used 7. Been using 8, 8.5 for some time now.

Cmdow is a Win32 commandline utility for NT4/2000/XP/2003 that allows windows to be listed, moved, resized, renamed, hidden/unhidden, disabled/enabled, minimized, maximized, restored, activated/inactivated, closed, killed and more. http://www.commandline.co.uk/cmdow/

my guess would be you named your batch file netstat.bat, so the batch file is calling itself instead of running netstat.

Missing the Poll, it may not be totally dead yet but it's life expectancy is extremely short. I'm part of the support for over 4000 systems and I think I have pulled out a floppy 4 times in the last year.

your runonceex.cmd only populates the registry keys, it doesn't do the software installation. That happens at the firt login and windows takes over and runs the commands in the runonceex registry keys and displays that window listing the titles from the registry.

That is part of the runonceex process. it is created by windows when the runonceex keys are populated.

run it for a day, you should know by the end of 24 hours how it would go over 2 weeks unless a fan fails. Just be sure the fan and heat sinks are clean and it should be fine.

Are you using a physical CD to do the install in the VM or are you using the ISO for the CD int eh VM?

Ignore em both, let windows updates do them, KB890830 is the Malicious software removal tool so it changes monthly. Th GDI tool checks to see if you have the appropriate updates installed when office is installed.

this is the way I do it. http://unattended.msfn.org/unattended.xp/view/web/23/ for my purposes I wrote a short CMD script to integrate the updates.

What Cluberti said. At least that is how mine is.

winLIRC

change: AutoPartition = 1 to AutoPartition = 0 change: Repartition=1 to Repartition=NO remove: FileSystem = ConvertNTFS

in your winnt.sif file in your first attempt using GuiRunOnce, you don't have the [GuiRunOnce] section. Which should contain a line to run START.CMD, see http://unattended.msfn.org/unattended.xp/view/web/81/ in the RunOnceEx file you createdyou either need to add a \ to the end of the set key=....... line, or put a \ between the %key%and the following number on the REG ADD lines. See http://unattended.msfn.org/unattended.xp/view/web/31/ And I'm not sure what %PP% is supposed to refer to.

Welcome to the forum. First you have to create the $OEM$ folder yourself it does not exist on the the media from Microsoft. Also it looks like you were using nLite if you were removing things with nLite try making a cd with just adding the updates first and make sure it works. Also make sure you have the latest version of nLite. Or make it manually instead of using nLite. If you continue using nLite and stillare having problems, try posting in the nLite forum and you may get more specific help towards nLite issues.

"C:\WINDOWS\system32\rundll32.exe" shell32.dll,Control_RunDLL hotplug.dll

or possibly a drive with bad sector where the files reside. try running a full scandisk with repair and look at the report to see if there are bad sectors. If that returns with no bad sectors try reinstalling your SATA controller drivers.

ActiveWorkbook.Save ActiveWindow.Close

just a guess, not seeing the page you are reformatting, but you start with selection.tables(1) then later move down 6 lines and reference the same object. But that object is a member of the cell 6 lines up. If you are trying to format another table then the (1) should be something else.

some USB drives can be set up to be bootable, but the BIOS of the machine you hook them up too must support booting from USB. If you need access to one from a DOS boot disk you may be out of luck.

You will lose anything that was not on the machine at the time you first took it out of the box. So back up anything that you want to pu back, except applicaitons of course those you will need to reinstall after you receive the machine back. Along with all of those lovely updates from Microsoft. As long as you have a valid subscription to Norton that should not be a problem. And everything else should reinstall without a problem also.

if you want to try a repair create an xp c with just updates, not answer file and nothing else then use the F6 option at boot to load the raid driver. A better place to start would be to scan for viruses and malware preferably from a boot cd like BartPe or something similar.

if you used the KTD method al you need to do is run sysprep. As I recall KTD adds the driver paths to the registry so that they can be found later so this will still work on the first boot after sysprep as long as you don't add more with the sysprep.inf file.

I think I'm detecting a guilty conscience here. In the past you were just blocked from getting or installing future updates. And recently would get annoying popup windows that you were running unauthorized copies of windows and I think they gave you 30 or 60 days after that to be legit. What they will do in the future is not known. They have probably use this information in the past to crack down on companies selling the illegal licenses also.