johnhc

pokeseeker, Why are you not using SP3? I use nLite to integrate the SP and exit. Then I use WMP11 Slipstreamer to integrate WMP11 and its hotfixes. Then do all the rest in one nLite run. I save the SP integrated files (original source+SPx) in case I have to slipstream again. Then I just start from the saved files. Good luck, John

Zoom7000, The Universal Silent Switch Finder (USSF) finds the following: "nLite-1.4.7.installer.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP- I have not tried it, so don't really know if it works - perhaps give it a try. Have fun, John.

kingsc, I don't have an answer for you, but it is obvious that most people looking at your post are going to want more information. Please post your particulars such as OS using, OS nLiteing, Preset data, nLite version, SPx, hotfixes/packs, etc. I will comment that I have found nLite very solid, not glitchy at all. I have built many ISOs and not seen any install errors such as you describe. I install one additional user and add a password to the Administrator and don't have to do anything else after install. One seemingly common error is to nLite the same source more that once. Basically, you should always start with a fresh source (copy of your install CD). Good luck, John.

hapecat®, I have used a DVD+RW many times with no problems. Just erase it before writing a new ISO. Have fun, John.

BikinDutchman, Thanks for your reply. I ran across a driver folder containing two files: *.inf_64 and *.sys_64. I found a number of references to inf_64 drivers via Google and wondered if this was a special extension for 64 bit OSs. I just DLed one of the Google found drivers (inf_64.zip) and extracted it and there were no *.inf_64 or sys_64 files. Don't know where this crazy one I ran across came from. Thanks again, John.

Will nLite integrate a driver with an extension of inf_64? Thanks, John

krwilson, The keyboard short cuts do work: ctrl-x cut ctrl-c copy ctrl-v paste. Enjoy, John.

hma6879, I am curious if your ISOs install and run properly? All that I have read here indicates that one should always start with an untouched original source. I have built a folder with the original CD files and integrated my SP. I then build from there. Right now I am mostly testing post install items (WPI and Kurt_Aust's procedure), so I am just changing files not really associated with Windows. I have tried a few tweaks or other small changes to Windows via nLite and it installs OK (VMware Server) but it looks a little funny and has some strange problems such as missing labels on some buttons. I suggest you start over with a fresh copy if you are going to change thinks like components or tweaks. Enjoy, John.

knifesk, Perhaps you are talking about the TCP connection-count Tweak in nLite? If so, I cannot comment on it since I have not used it. I use TCP Optimizer because I also need to increase my Receive Window (RWIN) to get up to my paid for speed. Enjoy, John

knifesk, Eh?????????????????????????????????? I don't have any idea what you are asking. Enjoy, John.

Kurt, If you want sound, you should have the following code in your .vmx file: sound.present = "TRUE" sound.fileName = "-1" sound.autodetect = "TRUE" sound.virtualDev = "es1371" You should also have the audio adapter enabled in your VM configuration. Perhaps the code is not present if not enabled. I had all these lines in versions 1.0.x, it is not a function of RC1. Enjoy, John.

Kurt, I am now listening to Internet radio on my 64 bit guest and I think you can also! Look in your .vmx file (VM not running) and change your virtual device as follows: sound.virtualDev = "es1371" Mine originally said sb16 instead of es1371. That should cause you to show a sound adapter (enable it in guest configuration) in Device Manager. Install one of the drivers I posted and see what happens - good luck! I am running 2.0.0RC1 and VMware Tools contain the driver for me. Thanks for the July update. I guess you know nuhi fixed the KB951376 integration problem in nLite 1.4.7. I tried it last week and it seems to work fine. I have not looked through all you updates and will soon. Good idea on the VMware Tools not needing extracting. I noticed for RC1, they have separated 32 and 64 bit items (e.g. VMware Tools64.msi) in the .iso. I extracted it and deleted all that I could identify that I thought I did not need, then 7-ZIPped it to about 16 MB. The ADDLOCAL=ALL switch causes a problem (failure to register DLL) so I use only '/i <file name> /qn /norestart' which seems to work fine. Have fun with your sound, but please let me know if it doesn't work. John

GamingX, It has been a while but I think these are the switches I used with Nero 6 in WPI: /SILENT /NOREBOOT /SN=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx /WRITE_SN Enjoy, John.

Kurt, You may know about this, but I have found an audio driver that is suppose to work for 64 bit Guests. I attach one I found on the VMware web site and a signed one I found via Google. I have been trying to run VMware Server 2.0RC1. It should have an audio(VMaudio) driver as part of VMware Tools64, but the audio fails to install when the tools install. I tried these drivers on my VM and have no luck so far - still 'no audio device'. I have an open thread on the VMware forum and if I don't learn something soon, I will try integrating the signed VMaudio driver and see if that works. This driver is listed to work on versions 1.0.4, 1.0.5 and 1.0.6. If you give it a try and are able to get audio to work, please let me know how you do it. Enjoy, John

Lrchr, Right click on My Computer and then click on Properties. Enjoy, John.

mitsukai, I'm not sure if you are asking a question or making a comment but you might want to see this post: show QL Kel's Addon seems like the easiest. Enjoy, John.

leoliver, I think the secret is, your Dell CD is an OEM copy of XP. If you'll look at My Computer properties you should see OEM under the Registered to: field. If you will read your EULA, you'll see mitsukai is correct. You cannot put this copy of XP on another computer. MS cannot prevent you from installing, but they can prevent you from Activating it on the new machine. When it was originally activated, information about your hardware was sent to MS and is associated with your key. This information is serial numbers and type info on various pieces of your hardware. If you change too many of these at once you have trouble from MS. You can probably still buy XP for a while even though MS has ceased shipping. I saw an OEM copy on Newegg the other day for $140. A retail copy will be more expensive but you can install it on multiple machines, one at a time. The main message is to read your EULA. Enjoy, John.

gkar, I DLed the self-extracting from mirror '02' and used 7-ZIP to extract with no problems (17 files+folders). The only reason I used '02' is because it was considerable faster than the one labeled 'download'. Enjoy, John.

GamingX, Perhaps this is a computer manufacturer's CD - right? The OEM and $OEM$ should coexist OK. Perhaps the manufacturer (if so) is using the folder in some sort of post install process of its own. I think you can place almost any folder (with no conflict with Windows) on the CD you want. It will just sit on the disk unless copied onto a hard drive. I have never looked at the content of a manufacturer CD, so am only guessing here. Enjoy, John.

Lrchr, I think you can get by with just SP3 plus a few fixes. I know of no way to recover installed hotfixes from your system. Enjoy, John.

Great, nuhi, thanks! Enjoy, John

Does 1.4.6 correct the KB951376 integration problem? Thanks, John.

Skunky, I'm no expert but perhaps I can give you a few pointers. Not sure what you mean here. Windows opens .hta files with mshta.exe and all you need to do is double click the WPI.hta file. WPI does nothing about parameters for your installs. The built-in USSF (Universal Silent Switch Finder) can help but will not cover all parameters. In Configuration, click the icon on the command line next to the folder option and USSF will run to give you some switches for some installers. There is also a free program called AutoIt that can be used to automate installs among other things. There are several topics including Addons which make installing applications easier - search these forums. There are many people in these forums installing Office and I think I have seen talk about unattended installs for it - again search these forums. I use Open Office myself. Be sure to read the manual at Kelsenellenelvian's web site. Enjoy, John.

Kurt, I've never had any conflict with your procedure and WPI. Before I removed the shutdown in your process, WPI always ran after your reboot and worked fine. Since I removed your reboot, after your process finishes, the 'Personalizations..' run, then WPI comes up and runs fine. The reboot I have at the end of my WPI installs waits for the last one to finish, then starts the reboot. There are no terminated processes and I have not seen the missing Quick Launch folder. If I haven't mentioned before, I am creating a user account (with Administrator privileges) with nLite and that account is what is running for your process and WPI. BTW, I am glad you did create this procedure. I especially like that I can install VMware Tools early but also like the flexibility that comes with your hotfix procedure. I really am not too crazy about turning this over to someone else to make the decisions. Thanks again for creating it and your continued support. Enjoy, John.

mshaw, I am curious what language DNU is (ENU perhaps)? Have you had any CD read problems? Cleaned the disk? Cleaned the CD drive? I have not run nLite 1.4.6. You might try 1.4.5 Beta 2 (what I run with no problems). I assume you have .NET Framework 2.0 or higher installed? If all else fails, please post a screen shot of your error window. Here's the info on SP2 (ENU): [367,964,016] MD5: 46D05CE174437A224C8A77047D010AE9 SHA1: 7F8E909C52D23AC8B5DBFD73F1F12D3EE0FE794C You might have fun with this post about XP x64. Enjoy, John.