Kelsenellenelvian

I nLite XP, 2003 and 2000 on my Vista PC all the time...

They're will never be a new version the author disappeared a LOOOOOONG time ago.

Its gotta be the widescreen stretching.

Fasle postive. Use the Post_$0em$ file then...

Here is a quick start package that will set your windows disk up to use WPI with runonceex. This is for use with all versions of Windows 2000, XP and 2003! To make use of this archive all you need to do is unRAR it and place the %oem% folder beside the I386 and WPI folders. http://www.wpiw.net/downloads/$OEM$.rar cmdlines.txt RunWPI.exe (Sets the runonceex and MCE themeing entries used for WPI)

Are you sure it is a still legal CD-Key? Remember they blacklist hundreds of pirated keys with each service pack. So SP3 has many hundreds of keys that will not work with it now. Easy test: install with no SP and try to activate. If it doesn't activate then you key has been blacklisted and will not be accepted during install anymore...

WOW from reading (and trying to decifer your paragraph) you seem to have little knowledge of all of the crud you are using. 45 Known and unknown??? Alot of those "Anti-SPyware" apps are just the opposite. How to fix? #1 make yourself an Ultimate boot cd for Windows ON A DIFFERENT PC. Yes it is legal and free! #2 take your system offline and QUIT FEEDING the leeches! #3 run you UBCD4win and scan EVERYTHING! #4 reinstall windows ONLY (Leave the other danged OS'es alone untill you are secure) #5 install 1 anti-virus. Like ESET smart security (NOD32) or Kaspersky whatever, just not Nortons for the sake of the gods that be. #6 get a really good firewall! #7 Rescan everything from within windows. Now for gods sake after you get Windows reinstalled reorganize everything and surf safer!

You just can't have an automatically activated system unless you have the OEM disk(s) that where made for your PC. (Which you assure us you have.) The major problem here though is that the damned OEM's add all sorts of crap on those cd's and make several modifications. Thus making it un-nLite-able. The disk can be mostly cleaned and nLited but it takes a lot of manual work... Leeme see. #1 copy the i386 folder and the ident files from your CD. (win51*** There will be 3 or 4 of them) #2 delete the svcpack.in_ and svcpack folder. (Inside the I386 folder) #3 Grab one of the COA keys off of your machine (I can't remember which one to use during install I would use the one in the unattended.txt file) #4 Slipstream SP3 and enter your unattended info with nLite. #5 Test with VMWare, Virtualbox, parralells, VirtualPC - hell ANY virtual machine. #6 If it works BURN THE ISO to a disk and keep it as your new SOURCE #7 Now nLite to your little hearts desire... Remember this may take some more work!

OEM disable or enabled matters not. You have a RETAIL copy of windows which needs to be activated every install. Normally this is not an issue as they (MS) keep records of your systems UID and will auto-activate when you press the little activate button. Every 4-6 months they flush those servers so either you are switching hardware or PC's too much. Remember a XP license is for ONE computer! Also with every service pack they blacklist HUNDREDS of keys that have been released on the internet or otherwise pirated. P.S. SP3 is out! (Probably the last SP for XP too )...

Site has been updated now...

Yup its all pretty much the same....

As soon as you donate a lot of money to nuhi. Seriously though this question gets asked ALL the time and please remember we develop these apps for free and are not paid on a regular basis. For as far as I know he got tired of all of the problems and people asking and demading a newer version. His profile says he is "On vacation"

You never said what drivers you where installing you just said the keyboard and mouse wouldn't respond. I have spent the last 30 minutes searching online and CANNOT find a way to disable the driver signing check pre-install... Maybe write your CHIPSET manufacturer and ask when they plan on releasing 64bit drivers.

You are assumming very correct! WPI has built in commandlines so you can call it 30 ways from sunday. And the latest WPI works fine on win2000 and upwards.

WPI http://www.msfn.org/board/index.php?showtopic=129222 (Also see link in my sig but it is not updated to latest version right now. Doing that now!) This will allow you to call those regtweaks as 64bit when you select them as 64bit.

Getting drivers signed is a very expensive process that some manufacturers just can't afford or won't pay for. Personally I would skip the keyboard and mouse drivers and do them post install. Yes it is normal for devices to stop working during setup as windows checks the devices and install drivers for them or configures them. Hope this makes sense to you. What keyboard and mouse set do you have?

JantinBeniwal = You need to stop yelling in every post you make...

I see what you are talking about. But his guide says to use the /audit switch in the commandline also.

7.3.0 released here...

7.3.0 released here.

Windows Post-Install Wizard (WPI for short) is a hypertext application designed for giving users choice. While Windows XP offers many ways of customizing the setup process out of the box, its major drawback is the lack of being able to select which applications an end user may install. In the past, end users and administrators needed to either download the files manually, or create overly complex scripts that could only be used once. WPI allows you to create one image, which can then be custom configured, and optionally, automated, so that end users can install any applications. WPI is a simple to use automation program for the choice and installation of multiple programs, tweaks and scripts. No longer will you need a dozen CD's or more when doing a fresh Installation. No longer will you need multiple files when you are servicing another PC. With Windows Post-Install Wizard all that you will need is 1 or 2 CD\DVD's to fully install your PC with all of your apps, scripts, registry files or tweaks. Instead of having to re-download those apps like adobe reader, flash or updates to programs you can have them all on one disk. With WPI you can have all of them all on one disk and then have a nice interface for selecting which apps to install and after configured properly WPI will install all of them without any needed input from you. WPI also and is commonly used added to your windows installation disks. This way you can automate the complete process of Windows and program installations. With your typical setup of WPI you have your OS and all of the apps, tweaks and such on one disk. After windows installs, WPI kicks in and you are given a selection of everything you have configured WPI with, then you can select the ones you want or simply let the timer run out and your default apps will install. Highlights of the newest version! v7.3.0 Updates - Released January 27th, 2009 ======================================================================== * If you wish to add your own custom functions, if it doesn't already exist, create a file called userfunctions.js in the WPIScripts folder, and place your code in it. Then use JSCRIPT={MyFunction()} to call it. * Added more information to the log file. * Fixed bug with quotes not being placed around paths from network share. * Added function getPointingDeviceID() Usage: getPointingDeviceID()=="ACPI\PNP.........." or Usage: getPointingDeviceID()=="HID\VID_.........." Returns: PnP Device ID. See Alt+G Hardware tab. Why: For wireless mice, multi-button mice. * Added function getKeyboardID() Usage: getKeyboardID()=="ACPI\PNP.........." or Usage: getKeyboardID()=="HID\VID_.........." Returns: PnP Device ID. See Alt+G Hardware tab. Why: For wireless keyboards, hot keys. * Added function getHDDControllerID() Usage: getHDDControllerID("PCI\VEN_..........") Returns: true or false. See Alt+G Hardware tab. * Added function getCDBurnerID() Usage: getCDBurnerID()=="IDE\CDROM.........." Returns: PnP Device ID. See Alt+G Hardware tab. Why: Determine if install burning software, Light Scribe software, etc. Note: Could be a CD or DVD burner. See hasDVDBurner(). Note: Combination drives like CDRWDVD drives do not always return reliable information. Same for USB drives. * Added function getCDBurnerName() Usage: getCDBurnerName()=="PLEXTOR DVDR PX-800A ATA Device" Returns: Name of burner. See Alt+G Hardware tab. Why: Determine if install Light Scribe software or not Advanced Usage: getCDBurnerName().toUpperCase().indexOf("SCRIBE") != -1 Result: if == -1, then SCRIBE doesn't exist, not Light Scribe. if != -1 (does not equal), then SCRIBE does exists. This is a simple check of the name for Light Scribe. Can also check for DVD or something else in the name. Note: Could be a CD or DVD burner. See hasDVDBurner(). * Added function getCDROMID() Usage: getCDROMID()=="IDE\CDROM.........." Returns: PnP Device ID. See Alt+G Hardware tab. Why: Determines hasDVDROM(). May have other use. Completeness. Note: Could be a CD-ROM or DVD-ROM. See hasDVDROM(). * Added function hasDVDROM() Usage: hasDVDROM() Returns: true or false Why: Determine if install DVD movie playing software or not. Older computers may only have a CD-ROM. * Added function hasDVDBurner() Usage: hasDVDBurner() Returns: true or false Why: Determine if install DVD only burning software, ie, for movies. Advanced Usage: hasDVDBurner() Result: There is a burner and it is a DVD burner. Short cut method. Advanced Usage: getCDBurnerName() != "n/a" && !hasDVDBurner() Result: There is a burner but it's not a DVD burner, so it's just a CD burner. * Added function hasDVDDrive() Usage: hasDVDDrive() Returns: true or false Why: Shortcut to determine if there is a DVD ROM or burner, but doesn't say what kind of drive. Same as: hasDVDROM() || hasDVDBurner * Added function getHDDControllerID() Usage: getHDDControllerID("PCI\VEN_..........") Returns: true or false. See Alt+G Hardware tab. Note: There could be multiple controllers, so you have to know the ID of the one you are checking if exists or not. Note: This is only useful for installing support software, not the driver itself. * Items with very long names will not be cut off and will see an ellipsis, ... , so all the columns stay the same width and no horizontal scroll bar. If text gets cut off when doesn't need to be, reduce the number of columns in Options -> General -> Number of columns. * Updated all installer.css files. * Created LIVESTRONG and PinkRibbon themes. * Created Accordion theme. The navigation system may be used later in the main program. * Created Da Vinci theme to show customization of themes. * Updated {EXTRACT} to handle wildcards better. * All reg keys are now deleted to prevent any cross-contamination. * The reg keys that store the paths for options and config files are now deleted when quit and after install is complete. * Updated getOSver() and getOSeditionID(). Usage: getOSeditionID()=="Home Basic Premium Edition" ***** NOTE: getOSeditionID() now has Edition in all returned values. You will need to update your conditions. ***** If on XP, getOSeditionID() will return "Home Edition" or "Professional Edition". If on Server 2003, getOSeditionID() will return "Standard Edition", "Enterprise Edition", "Web Edition", "Datacenter Edition", or "Itanium Edition". If on 2K, getOSeditionID() will return "Professional Edition", "Server Edition", "Advanced Server Edition", or "Datacenter Edition". * Updated the command line args parser. Wasn't accepting quotes in path names. * The font installer now checks if the font already exists so don't get any verification alerts to overwrite it. * Installer can not be started if a wizard is open. * Updated some of the audio player function calls. * Added option to Audio Player to copy the Audio folder to your harddrive when installation starts. This should prevent any skipping or slowing of reads from DVD. Notes and Extras Suggested disk folder layout: With the above folder layout all your config entries should read like: ["%wpipath%\Install\Blah.exe" /switch] Here is a small tutorial on how to add an app to WPI! Ok this is a sample (Very simple) configuration for CCleaner (A.K.A Crap Cleaner) This assumes you have all of the WPI files either in the WPI folder at the root of your Windows cd or all of the WPI folders (Common, Graphics, WPIScripts, Tools, Install and Themes) and the file WPI.hta at the root of your cd. Remember this is just the most basic and required entries for a program! 1. Download the app and place it in the WPI\Install Folder. (CCleaner.exe in this example) 2. Run WPI.hta and click on the “Config” button\Icon area. 3. Go to the very top area above the config section and click on the button that says “Add” 4. Enter in the name section “CCleaner” No quotes! Then click on any other section of the config area to activate the rest of the wizard. 5. You will notice the Unique ID (UID) section gets automatically filled in for you. 6. All apps are selected to be installed by default right from the start so if you don’t want it selected by default you must uncheck this box. 7. Choose a category for your app to be displayed in. If you want the app to be displayed in a category you don’t see simply chose other and a box will appear that will allow the entry of you choice. 8. In the commands tab click on "Add" at the controls area just right of the command line pane and then the the little folder icon and browse to your folder that contains the app, preferably the .\WPI\Install folder then select the CCleaner installer, this will place the appropriate path in the command line. 9. Add the necessary switch(s) for the program to run silently. For CCleaner the switch is /S so you would have your command line looks like so = "%wpipath%\Install\CCleaner.exe" /S (This can be easily done for most standard apps by simply clicking on the USSF button on the far right of the command line.) Other switches for apps that USSF cannot identify you can try looking at the forum section here = MSFN Application Installs section, 10. Select the Save and then the Exit buttons and you have now configured your first app! Afterwards you configure WPI to run with your CD using whichever method you choose. We suggest using one of the pre compiled and nicely provided $oem$ (Source folder if your are using Vista or Server 2008) folders that can be found in the downloads section. Then you can use an app like nLite, vLite, CDImageGUI or the Makeiso* program included in the tools folder to make your CD w\WPI bootable again. * MakeIso.exe = Adds make bootable .iso to the right click menu of folders. It is a silent installer so DO NOT click on it 50x a simple double click is all that is need to install it. It can be uninstalled from the add\remove programs menu! Just go to the source folder (The one that contains I386 and WPI) and right click then select Make Bootable ISO... _____________________________________________________________________ I have seperated the tools out from the main archive. You can download the tools here: Tools archive. Contents of the tools archive: WPI Config Lister CDSwitch <-- 3 Custom themes for CDSwitch MakeISO.exe autorun.inf <-- Updated and fixed WPI.ico New icon thanks to WolfX2 TaskKillS.exe from sadicq <-- TaskKillS Instructions Cleanup.exe (Deletes ALL icons from the desktop) Reboot.exe (Dialog box that will reboot in 60 sec unless cancel is pressed) _____________________________________________________________________ Here is a quick start package that will set your windows disk up to use WPI after the desktop loads. This is for use with all versions of Windows 2000, XP and 2003! To make use of this archive all you need to do is unRAR it and place the %oem% folder beside the I386 and WPI folders. http://www.wpiw.net/downloads/Post_$OEM$.rar Contents of the Post %OEM% archive: cmdlines.txt RunWPI.inf _______________________________________________________________________ Here is a quick start package that will set your windows disk up to use WPI with runonceex. This is for use with all versions of Windows 2000, XP and 2003! To make use of this archive all you need to do is unRAR it and place the %oem% folder beside the I386 and WPI folders. http://www.wpiw.net/downloads/$OEM$.rar cmdlines.txt RunWPI.exe (Sets the runonceex and MCE themeing entries used for WPI) _______________________________________________________________________ An $OEM%\WPI folder that sets up your WPI for RunOnceEx with the official Zune Microsoft Theme! http://www.wpiw.net/downloads/$OEM$-Zune.rar Contents of the %OEM%-Zune archive: cmdlines.txt RunWPI_Zune.exe _______________________________________________________________________ An $OEM%\WPI folder that sets up your WPI for RunOnceEx with the official Embedded Microsoft Theme! http://www.wpiw.net/downloads/$OEM$-Embedded.rar Contents of the %OEM%-Embedded archive: cmdlines.txt RunWPI_Embedded.exe _______________________________________________________________________ Here is mritters RUN_ WPI solution! http://www.wpiw.net/downloads/$OEM$_RunWPI.cmd.rar CleanUpWPI.cmd cmdlines.txt RunOnceEx.cmd RunWPI.cmd Use is as the same as the one above... _______________________________________________________________________ This is for use with all versions of Windows Vista and Server 2008! To make use of this archive all you need to do is unRAR it and place the Sources folder at the root of your CD. Sources Folder. Contents of the Sources archive: setupcomplete.cmd (This needs to be several folders deep so I preset the folders for you) ________________________________________________________ Over 2000 .png images for your pleasure to use in your tooltips or whatever! PNG Collection. ________________________________________________________ Themes are now hosted on WPI.net!!! Theme page! Please remember and donate!

The sysprep is used for manufacturers and PC makers. When you use that command it cleans out the serial and sets it to a "Factory" state. This is so the end-user\consumer starts the PC up then it asks for the serial and the user names, all of that info.

• Manufacturer Warranty 2 years warranty Granted you already voided the warranty by disassembling it. But I am very sorry to say your drive is dead... (It's like trying to walk on two-very broken legs) Unless you have a clean-room and the proper set of tools, plus the exact same type of drive then there is no way to get any data off of it without spending thousands of dollars. I have attempted drive swaps like that before and the only one I was ever successfully with was just when I switched the boards out. Any further into the drive and recovery became WAAAAY beyond my league. (I have been at PC's since the days of commodore 64 and windows 3. All the case is is a box of wires with a plastic housing for the drive itself. by itself it will not make any noise when the drive comes on. The noise you hear, like others have said is coming from inside the drive itself and means that you have irrevocably damaged the drive. I know 500 gigs is allot but when you have the means you should always keep redundant backups. Thats a lesson I have learned several times....

It's because it is an OEM cd... They modify the hell out of those things. I am sorry to tell you but those disks just will not work with vLite...

You don't really need to reformatt everytime. As long as you have made sure it starts and runs at the proper time do all your modifications and test each program seperatly (One at a time) inside your virtual machine. Or do them all and then run it in a virtual enviroment and grab the wpi log from your c:\ drive and read it. This will tell you which commands failed. Personally I test each command in my live machine. If the program is installed I uninstall it and run WPI to re-install it. Then if I have added several I run a test in VMware. There is 3 options for you I hope 1 of them helps.