jrzycrim

Taskkill or pskill won't work in this case. You would have to kill explorer which I don't think you want to do. cmdow "Total Commander" /cls should work.

You can use cmdow to close a window. cmdow [window caption] /cls If the window caption has spaces you need to enclose it in quotes.

I'm going to put in an order. I got SP1 the same way. Heh, must be a lot of people putting in orders... Looks like they just removed XP SP2 English from the CD Language box on the Order Page. It was there just a moment ago but now nothing is avaliable. Never mind, must have been a glitch.

I've discovered that PSkill is a bit easier to use then Taskkill.

Hmm, Your vmware tools should install. I think I had the same problem once and had to reboot the vm to get it to install, anyway... Here, try these. VMware Video Drivers I modified the inf for a resolution of 1024x768x32. VMware tells you that in order to have a display res higer than 640x480, you have to install the drivers but then it defaults to 640x480 anyway. [vmx_svga_SoftwareDeviceSettings] HKR, , InstalledDisplayDrivers, %REG_MULTI_SZ%, vmx_fb HKR, , VgaCompatible, %REG_DWORD%, 0 HKR, , DefaultSettings.XResolution, %REG_DWORD%, 1024 HKR, , DefaultSettings.YResolution, %REG_DWORD%, 768 HKR, , DefaultSettings.BitsPerPel, %REG_DWORD%, 32 That's what I changed...

You need to have your OS installed on vmware first. Then bootup your VM and then install.

ntkrnlmp will not work on single processor systems. That's why you would need to use a script like Alanoll's. Setup will determine whether you have a single or dual(or ht) processors and use the appropriate kernel. I think it even renames ntkrnlmp to ntoskrnl for use on multi-processor systems. ntkrnlmp.exe is in the i386 folder of the XP CD. Also in the Driver.cab.

If Kernel1.exe is a modified ntoskrnl.exe, it will not work for hyperthreading. You will need a modified ntkrnlmp.exe. I'm pretty sure that's where your problem lies since it happens only on HT systems. Is there a place I can download that bootscreen from? If so, I can try to make a modified ntkrnlmp.exe for you to use...

In $OEM$\$1\Drivers\VMware I placed the vmware video drivers. In my Winnt.sif, I added: DriverSigningPolicy = Ignore OemPnPDriversPath = Drivers\vmware Add that to the [unattended] section of your Winnt.sif Also, you need to install vmware tools in a running Virtual machine and then get the drivers from Program files\Vmware\Drivers\Video or something similar (insided the VM).

Yes i am using custom bootscreen. How exactly are you using your custom boot screen? Are you using a modified ntoskrnl and renaming it to oemkrnl or something else? If so, I beleive you need to use a modified NTKRNLMP.EXE for hyperthreading. That's the multiprocessor kernel. Alanoll has a nice script that will chooses the correct kernel for single or dual processor. http://www.msfn.org/board/index.php?showto...=0entry108366

You can include the video drivers for vmare in your OEM drivers on your install disk. they are only 45Kb or so. From within vmware, after you install vmware tools and drivers, you can find them in the program files\vmware\drivers, I believe. I had that same problem when testing but after adding the vmare video drivers to my installation CD, it worked fine.

Are you using any custom bootscreens?

RunOnce/RunOnceEx doesn't happen at the 13 minute mark. That will happen at first logon. Most people execute there RunOnceEx.cmd from cmdlines.txt but that doesn't mean that the applications will be installed at this time; that just writes the information into the registry for execution at first logon. If you wanted to execute a setup at T-13, you would add the appropriate command to cmdlines.txt in the $OEM$ folder. I think cmdlines.txt executes at T-12 however. cmdlines.txt [COMMANDS] "%systemdrive%\Install\Applications\7zip\7z313.exe -y /q /r:n" That's just an example for installing 7zip. My 7zip setup file is in $OEM$\$1\Install\Applications\7zip\ I use RunOnceEx to install my applications however. If you want to use RunOnceEX to install your applications, a search of the forum should yield many results. Refer to this: http://unattended.msfn.org/xp/runonceex.htm GUIRunOnce is another option you might consider.

I believe the only thing you can change is the Processor Name from here: [HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0] "ProcessorNameString"="Processor Name" Not sure why you want to change that since this depends on the actual hardware in your system. You are probably out of luck if you want to change the other values. I wouldn't recommend modifying other values in that key. Backup your registry in any case.

I'd do another test ensuring that you have enough hard drive space. If you run out of space during installation then that certainly would cause some problems. I can't answer specifically not knowing the exact details. Good Luck

You should have OemPreinstall = Yes, not OemPreinstaller.

$OEM$\Installs isn't a folder that will be copied over. You probably meant $OEM$\$1\Installs. That will be copied to %systemdrive%\Installs See http://unattended.msfn.org/xp/oemfolders.htm

I hope it isn't true for the sake of everyone that's waiting. It doesn't look very promising though.

Heh, a lot of people aren't going to like that. They're counting down the minutes until the 5th, the alleged date of the release.

I've never usd SP2 in any form so I don't know what to expect. Of course I've read articles about SP2 but it's not the same as actually experiencing it.

Yep, Setup adds %systemdrive% to the beginning of all directories listed in the OemPnPDriversPath. If you have OemPnPDriversPath=".\MYNAME\DVRS\MODEM" It would look in %systemdrive%\.\MYNAME\DVRS\MODEM.

[Data] AutoPartition = 0 MsDosInitiated = 0 UnattendedInstall = Yes [Unattended] UnattendMode = FullUnattended OemSkipEula = Yes OemPreinstall = Yes TargetPath = \Windows UnattendSwitch = yes Hibernation = no FileSystem = * WaitForReboot = No DriverSigningPolicy = Ignore nondriversigningpolicy = Ignore OemPnPDriversPath = Drivers\001_Sound;Drivers\002_Modem [GuiUnattended] AdminPassword = XXXXXX EncryptedAdminPassword = No OEMSkipRegional = 1 TimeZone = 35 OemSkipWelcome = 1 [UserData] ProductKey = "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" FullName = "Jim Roberts" OrgName = "Earth" ComputerName = IgorXI [Display] BitsPerPel = 32 Xresolution = 1024 YResolution = 768 Vrefresh = 75 ConfigureAtLogon = 1 AutoConfirm = 1 [TapiLocation] CountryCode = 1 Dialing = Tone AreaCode = 502 [Identification] JoinWorkgroup = WORKGROUP [Networking] InstallDefaultComponents = Yes I only put quotes around values that the ref.chm examples did. In the past, I've had quotes around some values like UnattendSwitch = "yes". But the above winnt.sif works fine. For the drivers path, you would need quotes if there are spaces in the paths to your drivers. It's UnattendSwitch not UnattendedSwitch. I've never used that in my Winnt.sif so I really don't know. Here's what ref.chm has to say about it: It may or may not work for a unattended CD. *shrug*

I've been testing the permissions on some of my default icons. Setting Deny on Full control created some problems since it denys read access as well. If you still have problems with your icons changing, try this: (I tested this and it worked for me) Right click on the DefaultIcon Key, select permissions, click advanced. Select Administrator, click edit, Check 'Set Value' under Deny. Do this for Administrators, System, and any other administrative accounts. This will still allow the values for a key to be read but will keep the system and proggies from changing things. I tested this with winzip. I never changed my default icons for zip files but for testing purposes I did. When I ran winzip, it would change the icon back to the default. After denying 'Set Value' on the key, it prevented the icon from changing back. Good luck with you endeavors.

For the icons that keep switching back, try setting the permissions on that particular Default Icon key. Righ click on DefaulIcon, select permissions, Check Full Control under Deny for Administrator(s) and System. That might keep things from resetting what you change. <snip>

Which Icons are you having trouble with?