jrzycrim

Try removing start from the last line. That's not necessary and I don't think you can use that in cmdlines.txt anyway. Start is an internal command in cmd.exe and can't be called from cmdlines.txt like external programs and commands.

Welcome It depends on the application in question. Typically, a program will install to the default path as it would during a normal installation. Some installers will let you define the install path with a command line switch. Those are command line switches to install a program silently; without user intervention. Those particular switches are only for a particular type of installer. See this forum for the unattended installation of different programs:http://www.msfn.org/board/index.php?showforum=80 Searh this forum and the web for "Virtual PC" and "Vmware". These programs will create a 'Virtual Machine' on your system and allow you to test your installation. No. The process is the same. A DVD is useful as it will accommodate more programs that you may want to include in your installation.

As far as I know, the corporate edition is a version of Windows XP professional that doesn't require activation. The boot screen displays professional just like the retail version; except for SP2 versions which doesn't display the version.

Well, personally, I've never disabled the admin account. Can't be 100% sure how things will go down. I'm to chicken to test it out myself, lol. I do have a second administrator account so I could probably test it without problem. It is a good idea to have an admin account other then the built-in one. ------------ Just to satisfy my own curiosity, I disabled the built-in Admin account. Booting into safe mode, I was able to log on to that account. Go to Start > Run, Enter: lusrmgr.msc Select 'User' Right click on Administrator and select Properties. Uncheck 'Account is disabled'. Click Ok.

If you're still not able to enable the account via safe mode, this utility can be used to enable accounts: http://home.eunet.no/~pnordahl/ntpasswd/ Good Luck.

Under safe mode, the administrator account is always enabled. He should be able to boot into safe mode and renable the account.

See if this info helps: http://www.dougknox.com/xp/scripts_desc/xp_admin_ok.htm

Correction. While the /q switch can be used to install the screen saver, the Display Properties launches after the install. You can use winzip to extract the .scr file from the installer or just grab the screen saver from your system32 directory. Just place that in $OEM$\$$\system32 on your CD. You can compress it if you like but uncompressed, it only requires 1.55MB of space. It doesn't really need to be installed, just copied over during setup.

You can use this to install it unattended: 3DwindowsXP.exe /q

For the CD to operate in unattended mode, unattend.txt needs to be renamed to winnt.sif. See http://unattended.msfn.org/xp/winnt_sif.htm

You forgot to escape the extra quotes in your commands. Try this: REG ADD %KEY%\020 /V 1 /D "%CDROM%\Software\WMP10\MP10setup.exe /q:A /c:\"setup_wm.exe /Q /R:N /DisallowSystemRestore\"" /f REG ADD %KEY%\002 /V 1 /D "%CDROM%\Software\AdobeReader\AdbeRdr602_distrib_enu.exe /s /a /s /v\"TRANSFORMS=Rdr602.mst /qb\"" /f Any extra quotation marks inside the original quotes need to be preceded with a back slash. Those should work assuming the original syntax is correct.

If you have "Text Documents (*.txt)" selected for the Save as type, then you need to use quotes around the filename or it will be saved as a .txt file. If you select "All Files" then the quotation marks are not necessary.

You should never install a program that is offered via a pop up. Chances are the program you installed is itself adware/spyware infected. No legitimate spyware removal program will offer itself in this way.

That setting seems to be stored in this key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StartPage Probably the value, Favorites.

Not sure about that one...

You're welcome. I hope it works.

Sounds like that program uses the Installshield installer. First, you need to do a manual installation using the -r switch: setup.exe -r That will create an answer file saved as c:\windows\setup.iss Each response to a prompt during the installation will be recorded in that file, including the answer given for the prompt asking to reboot. Obviously you want to choose No. Grab the setup.iss file and place it in the same directory as your setup.exe. That should take care of the reboot problem. Use setup.exe -s -SMS to install. The -SMS switch should keep the installer in memory until the installation is complete. Hopefully that will solve the other problem.

See this thread if you are using the tweak that disables the recycle bin delete confirmation: http://www.msfn.org/board/index.php?showto...=0entry181041

You need to add a leading zero to the key names: 70, 80, 85, 90 and 95. The keys are arranged alphabetically in the registry so the values present in key 100, for example, will be executed before the ones in 70 or 80...

At first I didn't like the new zip format but like alanoll said, you can just grab the test kernel from system32 (NewBoot.exe) after testing. The zip format is very convenient. Cuts down a lot on file size. Plus, boot editor is a great program.

I also tried Changing FC FC FC to 00 00 00 as well. The text came out black as it should but there was also an ugly black border around the windows logo.

I must of caught them in time if the server they are hosted on is having trouble. Anyway, I tried fiddling with changing the colors around in the default palette. Didn't really work so well. I copied your first image and saved it as a bmp. I used that image in ntoskrnl.exe with the following palette: FF FF FF 00 00 00 00 00 BC BC BC 00 D2 3E 20 00 01 65 53 00 05 35 B2 00 81 81 81 00 00 92 89 00 FC 7F 5E 00 20 6B F7 00 FF A6 8D 00 04 DC 8E 00 1B BC F3 00 43 43 43 00 03 03 03 00 E8 E8 E8 00 That seemed to work pretty good. I think that's going to be your best bet. Also, before you import that image into your kernel, you should change the image palette, not the palette in ntoskrnl mind you, to all black to avoid that initial image flash that comes up just before the image fade-in.

Why is the background grey? Anyway, simply replacing the background color won't work. Other colors in the palette need to be changed. FF FF FF to 00 00 00 for example. I'll do a quick test here and see if I missed any other issues that may be screwing things up.

Try adding this to your winnt.sif under [Display]: [Display] AutoConfirm=1 ConfigureAtLogon=1

Another alternative is to create an all black palette in PSP and load that into your images before saving and placing them in the kernel.