tguy

This link might help too. http://www.microsoft.com/office/ork/xp/journ/ohotfix.htm Basically you will need to extract Ohotfix to a temp directory and then extract each hotfix patch to that same directory. Then create a batch file that will copy the files into your installation replacing the originals. It is a fairly manual task but with batch files you should be able to accomplish it successfully.

Try going to a command prompt and typing runas /? >c:\runoptions.txt This will create a sort of help file for you to use when incorporating this into your build. Don't know if it will work if being run from an XML file or if you can encrypt the password. You can however, use it with smartcards for authentication, then passwords are probably not an issue.

Remote Installation Services on Windows 2000 would work or you could try a hardware based imaging solution Automated Deployment Services for Windows 2003, both are from MS.

I have done this sort of thing in the past without any problems. Try del /s %systemroot%\*.tmp in your cleanup batch file.

Is the regtweaks.reg file in the same directory as regedit.exe or in a directory typically specified the PATH statement of a Windows installation? If not, specify the direct path to the regtweaks.reg file in your cmdlines.txt file. Keep it in quotes to allow for spaces in the path statement to the file.

Hi, first of all make sure you get the right version of the download for your install. There are usually two separate files for client and administrative installations. Reference this MS KB article to get the syntax for the command line switches. http://support.microsoft.com/?kbid=197147 tguy

Try /qn. I believe it represents quiet mode, no display of dialogs.

Try switching the IE 6 install to run from cmdlines.txt with the same syntax. I run it from there without an immediate reboot and have been successful. Good luck.

You could try these two sites for additional help and information. http://unattended.sourceforge.net/installers.html http://www.appdeploy.com

Runonceex.cmd runs before the desktop and explorer.exe are fully loaded and running. Therefore some of your commands may not be interpreted correctly because the shell is not yet fully operational. Try using Sleep.exe to have runonceex wait until the Shell is loaded before trying to run your script. Another option would be to move the script execution to the end of the runonceex commands right before cleanup runs. Good luck.

From the looks of your registry file, it appears you may have a blank line at the top of the file. Try removing that so Windows Registry Editor 5.00 is on the top line.

Diskeeper 8 is good, 9 is better. Definitely gets my vote.

You could try running WINPE. Then loading the Security Configuration & Analysis tool. Open the template compatws.inf from %WINDIR%\Security\Templates. Apply the template to your machine. Reboot and see what happens.

Try this: Make sure OEMPreinstall=Yes Make sure $OEM$ is in the root of the directory structure. To logon as Administrator, press CTRL + ALT + DELETE twice.

Check your file system permissions. Try making sure the group Users or the Guest account have Read & Execute and List Folder Contents permissions to your FTPROOT or Virtual Directory.

A forced demotion may cause you to lose changes that were implemented from the DC that is having replication issues. Those changes may only be stored in the local database. On a side note, just forcibly removing this DC from AD may not solve your problems. Replication happens between all domain controllers. If it is not replicating between the problem server and the first server you mentioned, how would you know if it is replicating to another DC? Check your event logs for DNS, Directory Service, FRS errors and try and resolve. You could, should probably open a support case with MS as well. There are some sharp folks out there who work solving these problems all the time.

Though it is installed and may run, the program .REG entries or .DLL's may not have registered yet until you reboot. If you can isolate what PowerDVD is looking for when it checks the DirectX version then you can take steps to register whatever is necessary for PowerDVD to install. Try installing PowerDVD with the installer set in debug mode so it will create a verbose log file of the installation process. You can then parse the installer log file to see if the process for version checking is in there and take measures to start mitigating your problem.

Here is a copy of the script I use to add a user and add them to the administrator's group. '**************************************************************** Option Explicit ' On Error Resume Next Const UF_SCRIPT = &H1 Const UF_ACCOUNTDISABLE = &H2 Const UF_HOMEDIR_REQUIRED = &H8 Const UF_LOCKOUT = &H10 Const UF_PASSWD_NOTREQD = &H20 Const UF_PASSWD_CANT_CHANGE = &H40 Const UF_TEMP_DUPLICATE_ACCOUNT = &H100 Const UF_NORMAL_ACCOUNT = &H200 Const UF_INTERDOMAIN_TRUST_ACCOUNT = &H800 Const UF_WORKSTATION_TRUST_ACCOUNT = &H1000 Const UF_SERVER_TRUST_ACCOUNT = &H2000 Const UF_DONT_EXPIRE_PASSWD = &H10000 Const UF_MNS_LOGON_ACCOUNT = &H20000 Dim objComputer, objGroup, objUser, objWSHNetwork, ObjPwdExpires, strComputerName, strFullName, strPassword, strUserName Set objWSHNetwork = WScript.CreateObject("WScript.Network") strComputerName = objWSHNetwork.ComputerName Set objComputer = GetObject("WinNT://" & strComputerName) Set objGroup = GetObject("WinNT://" & strComputerName & "/Administrators") strUserName = "Admin2" strFullName = "Emergency User" strPassword = "********" Set objUser = objComputer.Create("User", strUserName) objUser.SetPassword strPassword objUser.FullName = strFullName objUser.Put "description", "Local User Account for Emergencies" objUser.Put "UserFlags", objUser.UserFlags Or UF_PASSWD_CANT_CHANGE objUser.Put "UserFlags", objUser.UserFlags Or UF_DONT_EXPIRE_PASSWD objUser.SetInfo '*** Add user to Administrators Group *** objGroup.Add "WinNT://" & strComputerName & "/" & strUserName objUser.SetInfo ' MsgBox "Completed adding user " & strUserName & ".", vbInformation, "Execution completed" Obviously substitute real password for asterisks.

Prathapml Review these articles, they will tell you what you need to know to automate your partitioning, formatting, and reloading a ghost image by cd. http://www.tech-forums.net/computer_articl...estore-disk.php http://service1.symantec.com/SUPPORT/ghost...dSection=1&Src= As for the reboot utility, Tsunami is right, reboot.com works well. Google it, I'm sure you will find it.

If you have an original MS Windows XP or Windows XP SP1 source cd, copy it to your hard drive, extract the SP2 files to your hard drive as well then slipstream them and re-create your .ISO. This has worked for me. The article may be referencing a build of XP that has had hotfixes copied into it.

To install Adobe, try the method discussed here: http://www.sanx.org/tipShow.asp?articleRef=86 http://www.sanx.org/tipShow.asp?articleRef=254 These have worked extremely well for me on XP, 2K, 2K3.

I believe the 128 bit WEP encryption relates to the wireless card connection only. One thing to check, in case you overlooked it, is to make sure the MAC address of the Win 98 computer is included in the MAC filtering allow list. Another thing to try would be to use the software from the manufacturer to configure and connect your wireless card, as opposed to letting Windows do it for you.

Winzip has a command line add-on to their software. Check it out. http://www.winzip.com

Here is a sample of my cmdlines.txt [commands] "RunOnceEx.cmd" "C:\WINAPPS\IE6\IE6SETUP.EXE /Q /R:N" "REGEDIT /S C:\WINAPPS\IE6\IE6.REG" should give you an idea of what you can do. These all install at the T-12 stage of setup.

Why don't you try using a freeware packaging utility like InstallRite or WinInstallLE? Create a vanilla install of XP or whatever OS on a PC. Install one of the above applications. Run the application to do a 'Discover' for the baseline settings. Install your application to a custom location. Run the installer application to do a 'Post Discover' to capture the deltas and create the install package. Include the new install package with your build. You will just need to run the .EXE created when your package is bundled to install it. Repeat the process in it's entirety for each app. you wish to package.