Mt.Dew

BTW, hello to you in Pocatello from Twin Falls

And so am I. See the above posted script

Nlite will "integrate" it properly, but will not clean up the duplicate files. If you have a SP2 disk this is the way to clean it up. Doing this is also very useful if you wish to make custom modified images. -edit: Forgot to mention this: Copy/extract your sp2 image to a folder named "finished" on your HD, then copy sp3 installer to a folder called "sp3" and rename the intaller to "sp3.exe" To make this method much faster, create a new text file and name it cleanup.txt and add the following in quotes. Then rename it to cleanup.bat and launch. (note, you must edit the directories to point to your actual drive/folder directories. This script will also integrate so you won't need nlite) Next, use what ever program you like to make a cd and don't forget to add the bootable information.

Actually, if you do it right, the SP2 with SP3 integrated, makes for a smaller image than integrating to a XP Gold source. SP0 with SP3 is 561mb SP2 with SP3 cleaned up and dotnetfx folder removed (to show comparision against SP0 since SP0 does not have DOTNETFX folder) Is 548mb If you choose to leave DOTNETFX folder (and copy DOTNETFX to the SP0 integrated image) Then the file sizes will be: SP0 source: 600mb SP2 source: 587mb

Do keep in mind that MS may not even release SP3 final. It has been stated by Microsoft and in the SP3 TechNet forum that it may not even be released. If that is indeed the case, then we shall see whether or not after June 30th 2008, the newest beta builds still function fully and without nag-ware.

Regardless to what cluberti claims are the "real" expiration dates, the fact remains that cluberti is not on the team that is creating service pack 3, and the fact remains that a member of that team creating service pack 3 confirms that ALL beta's will no longer function completely after June 30th 2008, or when SP3 final is released, which ever happens first. Facts are facts. No need to adjust the EULA.TXT based on the views of someone who is not part of the SP3 development team. If you wish to dispute this, by all means, head on over to the technet SP3 forum and make your dispute there.

people actually READ those ??? For those who like to know just exactly what is permissable and what is not, they do. However, everyone SHOULD read them. Otherwise they would not realize they don't actually own a copy of XP, they are just licensed to USE it. Plus, if more people actually read the EULA.TXT when it comes to these beta's, a lot of unneeded posts in forums could be staved off.

When it comes to windows XP, it gives priority to IDE HD's over SATA drives. I do not think you can simply move those files to the SATA drive effectively. Basically it comes down to this.. Install windows onto the 10GB drive and then, ANYTHING else you install should go onto the SATA drive, both to save space on the IDE and to make anything on SATA drive load a bit faster due to the bandwidth of SATA. Your other option is, use the SATA only. I have tried many times on friends pc's that have one IDE HD and one SATA HD. The end result is as stated above: either install windows to the IDE and then any other programs to the SATA, or just run the SATA only.

Microsoft: XP SP3 RTM Build 5511 anyone see it anywhere believe its rtm its all over torrents and i cannot believe in torrents I just googled various 5511 searches, not one torrent site has that listed.

Read the EULA.TXT that comes with every SP3 beta. It very clearly and very specifically states: until June 30th 2008, or until SP3 Final is released, which ever happens first. Also, you can refer to this thread from the SP3 forum: SP3 TimeBomb

RYU81: The program you might want to try is "useful file utilities" with the "change attributes" plug-in added. Useful File Utilites and plug-ins change attributes page

All SP3 beta builds expire on June 30th, 2008 OR when SP3 final is released, which ever happens first. After June 30th, or when SP3 final is released, ALL beta SP3 machines will no longer receive updates and will receive pop-up's (nagware) urging you to upgrade to SP3 final.

SP3 release candidates as far as I know, are for XP Professional only, not XP home as well. I could be mistaken, but I am fairly certain SP3 RC's are for Professional editions. A former co-worker uses torrents and he has downloaded a few SP3 integrated images, and just yesterday downloaded one that was listed as XPSP3_RM.0_PRO_RTL_EN (the description on site did state it was a "what if 5503 was RTM, it would look almost exactly like this" ). I examined the image compared to my own personal integrated images, because I prefer to do my own work. The creator of the image did an amazing job, even removing all the duplicate files that are no longer needed after integration, including ones that I myself had missed. Tested the image in VM: perfect install. Then came the real test, integrating my RAID drivers. Worked perfectly. Now, I am not telling you to go out and download other people's integrated images because there is no excuse these days to learn to do it yourself, but, that XPSP3_RM.0_PRO_RTL_EN was the cleanest integrated only image I have seen.

No IE7 or WMP11 in service pack three due to Anti-Trust lawsuits. And thank god for that too. IE7 is the biggest piece of crap ever and my god WMP11 designer needs to be shot. Both are such garbage.

I am unsure of any programs. What I was doing back in 2003/2004, was create a bat file. This bat file did many things for me at once, ranging from clearing out my most recently viewed documents, document history for various applications, as well as run registry commands and copying files from a stored location to overwrite main files to "clear" the system. As you can imagine, it took some time to develop the bat file to perfection, but once it was done, it was just a simple click from the quick launch and everything was the way I wanted it. The good thing about using the bat file was at any given time I could edit the bat file to exclude or include different programs. Also, having a pre-config'd bat file backed up made for a much faster tuning if a fresh install was called for. A lot easier to get to your desktop the first time and running that bat file to clear that file extension list with out having to do it manually on every format/install.

GrofLuigi, thank you for the information. I attempted cleaning this list some years ago and became frustrated when I encountered extension refusing to change. I look forward to the future posting. Knowing now that in fact the entire pool is scanned before a decision is made has invigorated me to take this endeavor on once again. How can you ignore such obvious gains in time saved? Your future post will be most helpful when I build my master list of extensions to keep.

Try a program called sandboxie: http://www.sandboxie.com/

IPCONFIG: Hehe. How interesting. You can run it, see the dos box for a 1/4 of a second then it closes. going to a command prompt and running ipconfig will list DNS suffix, the IP Address, the Subnet Mask, and the Default Gateway. But, no configuration can be done unless you know what you are doing at a command prompt. As far as sysinfo goes, sysinfo.exe does not exist and you must run msinfo32.exe to get to what you would normal see when you run sysinfo. (I am probably wrong about sysinfo.exe no longer exsisting, as I did not have all files and folders set to be displayed, including hidden system files/folders) -edit: Oh, and to hack to make it appear a different version really isn't that hard if you know what files to manipulate. Trouble is, on recompiling, the Digital Signature would be invalid. (However, there are some really crafty Russians and Chinese and people from India that have the know how and the means to make a Digital Signature appear legit. But, as nuhi stated, I doubt anyone is that bored.

Greetings my fellow SP3 beta testers. I must admit, this new build version is a mysterious one. Slipstreaming to SP0 or SP2 still suffers from some files not being updated during integration. Nothing new about that since there is a thread about it. Again, SP1 image still remains the only source image to integrate into properly. Integrating into SP0 or SP2 still works, but like stated before, a few files do not update properly and the result of that could be nothing, or it could mean at some point, something might throw a fit in bizarre situations. Also, this mysterious 5503 build includes some 15 or so new files, and also has "spcompat.dll" instead of "spcompat.exe" in the \i386\update folder. The prior SP3 builds had spcompat.exe files. Taking 5503 to windows updates netted 2 updates for my equipment that none of the prior SP3 would pick up. Also, IE6 still has the crash bug, so the registry entry fix is still needed. This issues has been stated will be fixed when SP3 is final. 5503 will sometimes list the build number in system properties after install, sometimes it will not. In VM install, it will almost always not show the SP3 build version, but a real install will. This is because the registry key CSDReleaseType is failing to update properly, leaving it at default value of 0 (which does not list build version), changing it to a value of 1 will properly display the build version. Lots of stuff for people to mull over. Among them being the huge jump in build number. Last I heard, 3380 would be final build.

I have had errors like that before. Two things for you to do: 1: make sure you do a FULL format of the HD when asked which method of format to use. 2: if your SATA optical drive has a jumper to select master or slave, set it to slave. Windows XP can be one picky bugger when installing.

One thing all of you are forgetting about is: SP0 does not include the DOTNETFX folder, which is on all XP discs Since SP1, but is not part of the seperate service pack installers. This folder is also different sizes. 33.2MB on SP1a, and 39.5MB on SP2 (referring to untouched images, not user created slipstreams). Adding the DOTNETFX folder from SP2 source image onto your SP0+SP3 slipstream (and all other user created slipstreams will increase by the 40mb DOTNETFX folder) will bring the file size up to 637MB. So, re-calculate your image sizes. Me personally, I use SP0 to integrate the newest SP, then add the DOTNETFX folder. The reasons are pretty simple. 1: often times .NET needs to be installed, and thus why MS added the folder to their images for XP. 2: SP3 final iso from MS will almost assuredly contain the DOTNETFX folder.

Here are some links for ALL windows XP discs: SP0: http://www.tacktech.com/display.cfm?ttid=226 SP1: http://www.tacktech.com/display.cfm?ttid=283 SP1a: http://www.tacktech.com/display.cfm?ttid=312 SP2: http://www.tacktech.com/display.cfm?ttid=342 Another great page is: http://wiki.djlizard.net/Product_IDs

Maybe you should re-read the original post. I explicitly says "how can i detect that what kind of CPU is used in the current pc or notebook?", not what you perceived as "which version of an update do I install when I can find x86, x64, and ia64 editions of an update", because that phrase was not used at all. As for the OP's issues of his/her disk being used on various computers, his/her image should work on any cpu (including amd64 cpu) that is not an ie64. So, the issue the OP is having is rather odd.

Actually, msinfo32 will not accurately tell you what kind of cpu you have. It will tell you in what "mode" your cpu is running, based off the OS. For example: msinfo32 reports "Processor x86 Family 15 Model 35 Stepping 2 AuthenticAMD ~2611 Mhz" I have an AMD Athlon64 FX-60. Everest Ultimate edition on the other hand will tell you EXACTLY what the cpu is. For example: Everest reports "CPU Type DualCore AMD Athlon 64 FX-60, 2612 MHz (13 x 200.9)" Instruction Set x86, x86-64, MMX, 3DNow!, SSE, SSE2, SSE3 Plus, Everest will give you more details about your processor than you may even understand. If you want a quick way to find out exactly what you have in your system, or any system at all, download everest ultimate edition from http://www.lavalys.com. Extract the zip file or run the installer, then copy the everest folder onto a usb stick. Now you can just simply plug in the usb stick, launch everest and get any information you need.

If the definition of stutter in this case is: sound plays then stops then continues to play at the point the sound stopped prior. Could be a shoddy driver or the signs of a failing sound card. Try uninstalling the drivers then cleaning up the registry (if you are comfortable doing so), downloading the drivers again (just in case) and re-install. Another option could simply be physically removing the sound card and re-inserting into the motherboard. Sometimes the last step is the magic trick. If the definition of stutter in this case is: sound plays then stops, then continues to play, but not from the point the sound stopped prior. Most likely failing hardware. Try installing a different sound card. Is there any system monitoring software running on the pc that might be accessing SMART functions, even at low-level? If so, that may be a cause for stuttering of audio. An example of such an application is Everest Ultimate Edition. There is a thread regarding winamp and stuttering, but this is not limited to just winamp in conjunction with Everest running.