newsposter

You guys are dancing around the edge of how to subvert or bypass windows licensing and activation...... First Clue: If you need to manipulate pidgen.dll, you're probably not legal.

www.driverpacks.net

It's my understanding that for pre-fetch to do any real good, the files need to be kept on a device (small SSD, UDMA CF card on an PCI adapter, etc) that is 'faster' than the main HDD things would normally load from. This is the theory behind Intels TurboBoost anyway. Pre-fetch on XP is 'almost' the same as Vista TurboBoost but they both depend on the user spending the $$ necessary for a really fast secondary storage device.

No 'numbers' but removing scheduled tasks and setting as many services as possible to manual/disabled does the trick for me. Actually removing services/files doesn't do a thing for startup times. Laving everything in lets you adjust things as needed. The idea of boot profiles helps a lot here too. A quick booting minimal profile for when you need it and othe rprofiles of various functionalities for other things. If you really want a fast startup, invest in hardware that works quickly on startup. You need a mobo with a bios and disk controller that gets to work quickly instead of pausing ever second or three. At a minimum this means an EFI 1.10 (UEFI draft) BIOS. And don't forget a fast/fat hard drive that (at least on paper) can actually saturate the sata channels.

Instead of a USB stick and all of the config and formatting hassels that brings, consider using an IDE flash module. Cheap and fast and wholly internal to your system.

If a service is disabled, the code 'left behind' does nothing more than take up space on the hard drive. On the other hand, if a service is removed, it's difficult to impossible to manually re-add it. So do some searching on the forum here. Weekly and daily posts can be found from noobs asking how to replace things that shouldn't have been removed in the first place. There are practically NO posts from people who say that they regret not removing something. Once services are disabled via nlite, a tool such as Sysinternals Autoruns is used to look at all of the device/service startups and further shut off (again DO NOT DELETE) things that appear to be unneeded. Autoruns has the abinity to take snapshots of before and after setups which maked reverting changes very easy. If an error is made, or a service/driver is in fact needed, it is a simple matter to reset the services/drivers to start on boot.

well, try installing that .exe on your own. No other way to tell what will happen.

nlite is not designed to be run multiple times on a modified source. Your results will range from unpredictable to bad and unuseable.

Nuhi, how about it? The last line that sets "2048" just set up the default after establishing 4 default levels. The default out-of-the-box cache for XP is 500 icons. thanks! REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Advanced\IconCache] "Text"="Icon Cache Size" "Type"="group" "Bitmap"="SHDOC401.DLL,6" "HelpID"="update.hlp#51140" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Advanced\IconCache\Small] "RegPath"="Software\\Microsoft\\Windows\\CurrentVersion\\Explorer" "Text"="1024 Icons" "Type"="radio" "CheckedValue"="1024" "ValueName"="Max Cached Icons" "DefaultValue"="2048" "HKeyRoot"=dword:80000002 "HelpID"="update.hlp#51140" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Advanced\IconCache\Medium] "RegPath"="Software\\Microsoft\\Windows\\CurrentVersion\\Explorer" "Text"="2048 Icons" "Type"="radio" "CheckedValue"="2048" "ValueName"="Max Cached Icons" "DefaultValue"="2048" "HKeyRoot"=dword:80000002 "HelpID"="update.hlp#51140" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Advanced\IconCache\Large] "RegPath"="Software\\Microsoft\\Windows\\CurrentVersion\\Explorer" "Text"="4096 Icons" "Type"="radio" "CheckedValue"="4096" "ValueName"="Max Cached Icons" "DefaultValue"="2048" "HKeyRoot"=dword:80000002 "HelpID"="update.hlp#51140"

just shut off services.....

Bruce, go do some google-ing on windows system variables.

Eight Cds from HP?? Sounds like you are trying to use restore discs which is NOT supported in any way by nlite.

It is not possible to use an OEM-supplied 'recovery discs' as a source for nlite to work on. This is known to fail. You MUST use an 'official' MSFT distribution that you are personally and legally licensed for.

If anyone has successfully downloaded the ISOs from Microsoft (not from the bit torrents) could you post the MD5s for both 32 and 64 bit. thanks

Epic Fail, attitude related.................

nlite is intended to be used as a SINGLE PASS utility. If you fubar an ISO, you MUST start over with a fresh, unmodified XP source. If you need to update an existing ISO, you MUST start over with a fresh, unmodified XP source.

The same advice goes for driver and driver support if you are going to integrate driverpacks.

I would say that due to the newness of your hardware, you are going to have to find a way to get XP compatible CPU, chipset/mobo and SATA drivers into your XP image. No way around it. The hardware you are trying to use is newer than XP by what, 5+ years?

Considering that the AMD drivers are what, 10kb, it might be worth a try to rework your image and NOT remove that particular driver. You should also leave support for apic and things like that.

Nuhi, next time you're working on nlite code, can you add another MSIE tweak? Add the following four sites to the 'trusted sites' list: http://update.microsoft.com http://windowsupdate.microsoft.com https://update.microsoft.com https://windowsupdate.microsoft.com (in Tools | Internet Options | Security | Trusted Sites) These are recommended by MSFT to avoid an occasional/temporary condition wherein Microsoft Update cannot connect. http://support.microsoft.com/kb/836941 (look for Method E in the write-up) Many thanks!

No offense intended, but I don't thank that anyone here is going to risk downloading modified and otherwise unknown drivers from a third party site on the say-so of someone with less than 10 posts.

microXP is indeed warez so no support for that or any mods here...... Doesn't matter if you own a legit key, the distro of microXP itself is warez.

yawn.......

you probably removed the default amd and/or intel cpu and chipset drivers. LEAVE THEM IN.

Virtualbox also runs on most Linux and Solaris hosts for Windows guests...