tap52384

I would also like to make known my thanks. Ever since 2004 and the impending release of Windows XP Service Pack 2, nuhi has been working diligently to provide a quality piece of software whose purpose was to provide modularity to Windows XP. I have followed along and saw this software blossom, being very receptive to user feedback and in the end, provided us with not only customization for XP, but the possibility of bloat removal for Vista with Vlite. Thanks for your years of hard work!

If you are using an Autoattend.xml file, it may have an error in it. Use the WSIM in the WAIK installation to validate Autoattend.xml. If you have a functioning one that you used with Vista, that one should work fine with Windows 7. Additionally, last I heard, build 6956 was only in VHD format; your ISO may not be authentic.

Ditto; I am also experiencing this problem with Windows Vista Ultimate.

Does this setting fail if you are installing Vista from a USB drive? It doesn't seem to work for me.

This is awesome! This is always something that I wanted to do, especially since I assume that installation from USB is not only more convenient, but faster than installing from DVD, or am I wrong? In any case, an nLite collaboration would be cool as well, to be able to nLite XP and then install it from USB!

http://unattended.msfn.org will explain the heirarchy of the $OEM$ folders best. That's how I learned.

This is the wrong preset; there should be one more file called Last Session.ini.

nLite is designed to only keep the newest files, so I suppose in theory, integrating RyanVM's updates wouldn't hurt SP3, but it would be interesting what you report after you try it...RyanVM has updates that are not necessarily Windows Updates, but other necessary updates from Microsoft that are needed for programming and other little known but important features available to Windows XP.

I care, but I do not know if i can answer the question to if the MSDN version is better or not. Do you slipstream manually or with nLite? Perhaps there may be a difference if you slipstream manually and with nLite.

Yes, Media Center is one of the Compatibility options that can be protected from removal during the nLite process, so yes, it can be removed. I also can confirm that Media Center is Professional without Active Directory functionality. Perhaps that registry key that XP Professional users change to make XP think it is MCE could help in your quest...

Even though such a check would be fairly simple to implement, it is not fair to suggest that checking to make sure that the system folder is not selected due to user error. Additionally, nLite does not select a folder by default, the folder path dropbox is blank. Furthermore, I just selected my C:\windows and I received this message: --------------------------- Warning! --------------------------- CD Ident file not detected! Make sure you copied it from the original CD (and all root files). You can copy it now without restarting nLite. Copy win51ip to c:\windows\ --------------------------- OK --------------------------- This is an error message that basically says, "the currently selected folder does not have the files that a normal installation cd have." A form of check was implemented after all.

This is probably what you are looking for: http://blogs.msdn.com/winpe/archive/2007/0...mple-steps.aspx This is an article that explains how you can removed the unused packages from WinPE. The files are marked to be deleted and then are actually deleted when you export that WIM, resulting in a much smaller size. You can reduce it down to ~100 MB, which loads a lot faster than its normal size.

That's not a bad feature, but this can be done with a single CMD script (I use a separated registry file, however). The way I currently do it is set a command in cmdlines.txt that points a .reg file and the cmd script to copy the files: CMDLINES.TXT: [COMMANDS] "REGEDIT /S i386copy.reg" "i386copy.cmd" EXIT i386copy.reg: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup] "SourcePath"="%systemroot%\\i386\\" "ServicePackSourcePath"="%systemroot%\\i386\\" i386copy.cmd: @ECHO OFF for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\WIN51IP set CDROM=%%i: ECHO Please wait, Recovery Console is being installed locally. %CDROM%\i386\winnt32.exe /dudisable /cmdcons /unattend mkdir %systemroot%\i386 ECHO Please wait, source files are being copied. This may take several minutes. xcopy /e/h/f/v/c/y/z %CDROM%\i386\*.* %systemroot%\i386\ ECHO Adding registry entries. regedit.exe /s %CDROM%\$OEM$\i386copy.reg ECHO Done. EXIT Note: My i386copy.cmd also installs the Recovery Console.

Well, duh... If you would've looked at the left, you would've seen that I'm running XP 64, so I obviously installed the x64 version. Answered your PM already. Just send the test version over. Try using Unlocker 1.8.6 on the file you are receiving an error about. Since you rebooted and the same error occurred, it's possible that it is a program that launches at boot. Additionally, your responses to assistance could be fine-tuned. People genuinely trying to help do not deserve attitude.

Start with http://support.toshiba.com.

You can now officially download SP3 RC2 from the Microsoft website: http://www.microsoft.com/downloads/details...ang=en#filelist Perhaps this much newer build will resolve any issues you are running into.

The progress bar is blue; I thought the RTM was green...

Could someone tell me what components are required for Vista activation via KMS server? I am using Vista SP1 and I cannot activate and receive the following error message: The following information was found for this error: Code: 0x8007232B Description: DNS name does not exist. I am able to get on the Internet, so i'm not sure what I did wrong...

Sweet. Thanks! I have the real thing!

Does anyone know the MD5 for the official Vista SP1?

The latest build of Windows XP SP3 is 3264, which is freely available for download from Microsoft. Perhaps using that version could correct whatever issues you are having.

post your last session.ini to get a more definitive answer.

Cyclic redundancy? I would backup that drive now. Every time I ever saw this message, it was a gentle warning for a complete hard drive failure.

Visual Studio 2005 is supposed to only create a single folder called "Visual Studio 2005" within your My Documents folder; by default, all projects should be created within that folder unless otherwise specified. Look at your general options to see if that location has been changed.

OEM Preinstallation Kits (OPKs) I must admit I didn't know what OPK was. Essentially, you are trying to create addons for the softwares which would be added during the "Hotfixes" section of the nLite process. There are a lot of addons here: http://www.winaddons.com There should be a topic on MSFN somewhere that explains how to make addons.