redxii

Yeah. You can also remove that "win51ip.SP1" file.

I see this question a lot. In Win 7, 7.9 is the highest score. (5.9 in Vista) Comparing Vista to Win 7 scores is comparing apples and oranges and fig newtons. You can run the WEI test in the command prompt by running the following command: winsat disk http://technet.microsoft.com/en-us/library/cc742157.aspx Compare in Vista and 7, if they are close then you didn't lose any performance. Since Win 7 has a higher max score, your score is going to be lower in Win 7.

It shouldn't be hard to add Win 7 compatibility to vLite, is it? Instead of building an entirely new program. nuhi couldn't add Vista support to nLite because 2000/XP/2003 have completely different installation routines as well as just plain being too different. I am shifting to removing nothing except Manual Install and tweaking services to disabled to avoid compatibility problems and broken stuff, but until '7lite' is released or vLite adds 7 support, I wouldn't trust it to just tweak services.

I had no problems vLiting a Vista 64-bit source on XP 32-bit or Vista 32-bit. I'm unsure why you couldn't.

Adblock Plus Firesizer Flashblock Text Area Resizer and Mover

You should be able to do this via autounattend.xml as well. Add oemlogo.bmp to \Sources\$OEM$\$$\System32\oemlogo.bmp on your DVD. <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OEMInformation> <HelpCustomized>false</HelpCustomized> <Manufacturer>Hewlett-Packard</Manufacturer> <Model>Compaq Presario SR1610IL</Model> <Logo>C:\Windows\Sytem32\oemlogo.bmp</Logo> <SupportHours>9 AM to 9 PM (Mon-Sat)</SupportHours> <SupportPhone>1-600-114772 (Toll free), 0124-2346992 (Toll Number)</SupportPhone> <SupportURL>http://www.hp.com/in/support</SupportURL> </OEMInformation> </component> </settings> </unattend> processorArchitecture="amd64" for 64-bit Vista.

Yes you can, but if you have an internet connection like cable modem or DSL or other that connects to your PC with RJ-45 (8-pin connector resembling a big phone connector), you should instead get a router.

Those compressed files aren't referenced in dosnet.inf or txtsetup.sif. There are newer remote desktop files on the disk that are used. Example, mstscax.dl_ was replaced with lhmstscax.dl_, but lhmstscax.dl_ is still extracted as mstscax.dll. mstscax.dl_ is obsolete. Plugin.ocx was made obsolete in a security update released for SP2 (KB912945). mmc.chm is extracted from mmcS.ch_.

You don't need one from someone else, you can go through it and decide what removals or tweaks work for you & your system.

The keys students (usually technology department students) receive are through MSDNAA, they are retail keys w/ a different EULA and require activation. nuhi doesn't even allow nLite for commercial purpose, does he? And VLK isn't licensed to individuals buying for just one or couple of computers.IMHO, bad idea anyway for company desktops.. just don't do it.

Vista SP2 requires SP1, whether you integrate or install after Vista is set up.

There shouldn't be any ramifications, it just tends not to clean out obsolete files, like SPx.cat/SPx.cab. Even Microsoft's image contains obsolete files, but they aren't referenced anywhere in the INFs so they are ignored by setup and take up space: mmc.ch_ mstsc.ch_ mstsc.ex_ mstscax.dl_ plugin.oc_ rdsktpw.ch_

Maybe, if it's identical to a retail cd. If you're intending to remove the stuff the OEMs, not Microsoft, include, then you're outta luck since vLite doesn't remove OEM bundled software.

Still every time you install a hotfix, it has to install a zillion other copies of the same file? If files are being counted more than once, you still lose that space since it appears none of the utilities can handle links correctly/not include them.

Well, it doesn't do anything by itself, it's a registry hive. Open the Services snap-in, and see if in the "Log On As" column there are any services set to run with the account. Additionally, see if maybe the user is logged in remotely (may see this in Task Manager).

The ntuser.dat is the profile's HKEY_CURRENT_USER registry hive, cuz you know, each account has their own HKEY_CURRENT_USER. If a user is logged in, the file is loaded, and when you load a file in Windows, it becomes locked and you can't delete it while it's in use. So to delete a profile folder, you have to be logged off of that account. The folder will be recreated when the user logs in again. It will not delete the account, you have to use Local Users and Groups snap-in (locally) or Active Directory snap-in (domain account).

Maybe not unless you want to screw up your profile..

You have to log out of the Administrator (Administrador) account and use another account to delete that file in the Administrator's profile folder.

Also you might be confused about the path to the file. In XP it's: C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG But still, if the account is logged in you can't delete it.

You should be able to delete it as long as the account it belongs to isn't logged on, so you have to have another administrator account to delete it from.

Probably because it's a system file. Are you experiencing any errors relating to this file or did it look at you funny?

I tested on my configuration and it installed and ran fine on mine, I remove mostly non-essential stuff, maybe it won't on yours. Load it up on a virtual machine with the same settings and try it out.

You need this: http://www.microsoft.com/downloads/details...;displaylang=en

You only need to integrate SP3 if you want SP3.

VirtualBox doesn't enable sound by default.. you have to go into the virtual machine's properties and turn it on. XP already has the driver for the sound card VBox emulates, so if it don't work then you probably removed it.