JoeMSFN

Try Windows Memory Diagnostic to rule out bad RAM. It will create a floppy or extract an bootable ISO suitable for burning to CD. Since bad RAM is a big problem for Windows and probably MS tech support calls, I assume they made this one good. (see below for my personal encounters with it). @Jito463 Yes those are very good suggestions. To relate a story of mine. Before I had slipstreamed SP2 into the install CD, I installed it from the IT professional massive download. (My download was good however.) I knew it was a good file since I used the same file from previous CDRs on many computers. One day I tried it on a computer that INSTALLED JUST FINE from my XPCREATed disc. Then I took a freshly made CDR of the SP2 file I mentioned above and it kept failing to get past the extraction or decompression or whatever stage is when it creates that really long ZGD123432FDDF randomly named folder. Never got to next, continue etc. It kept saying the SP2 file was corrupt. Since it was a recent SP2 burn (disc never tried, but knew the file was good), I though it was the drive in the new computer, the drive int the computer I was using for creating unattended install discs, the media, etc. It drove me nuts trying different combinations trying to troubleshoot the problem. I even copied it through a network connection. Well that was the long of it. The short of it was BAD RAM. With Windows Memory Diagnostic I've never (yet) had bad RAM slip by. A friend of mine had problems with a laptop and tracked it down to a recent memory upgrade. And this computer had bad memory also which (oddly enough seemed to behave properly) I wouldn't have noticed if it weren't for the redundencies and checks built into the extraction process of SP2. Try running Windows Memory Diagnostic on quick first. I've never HAD to use it in extended mode, (eventhough sometimes I do) basic or quick mode has worked just fine (which is it's default).

I battled with that too. With Windows XP it seems to only take you to a website that tells you to run Windows & Office Updates. The long and the short of it is, it's a registry entry. You don't need to install or "slipstream" this file. Somewhere in your Registry Tweaks .reg file, you need to put... ;----- tell windows I've already run the GDI+ detection tool (gdidettool.exe) ;----- in references to http://support.microsoft.com/?kbid=873374 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\GdiDetectionTool] "GDITool"=dword:00000001Of course add "Windows Registry Editor Version 5.00" to the top if this is your first registry tweaking durring unattended install. I discovered this using a registry compare program. (there are several referenced in the forums). Well The above tweak is probably also, but I felt like answering. Also I included as a default bookmark in my winnt.sif file: [FavoritesEx] Title1 = "Microsoft GDI+ Detection Tool - September 14, 2004 - KB873374.url" URL1 = "http://support.microsoft.com/?kbid=873374"To help reference the file since it doesn't install and the first time it's run it won't showup as a critical update again. note: (I found the quotes necessary or my winnt.sif file would bomb.)

Searching in "ref.chm" under FileSystem = ConvertNTFS I found this link . It states Also I know I read earlier in this thread about "WinPE". If you check out BartPE builder. It only requires Also doing a search for cygwin, it turns out PE Builder uses cygwin1.dll I've installed that once (lots of the package, not just the dll), and I know it has UNIX commands, perhaps even the ones you require/desire. I'm not familiar with either of the above techniques, but I have made a BartPE disk, and it worked. I also remember reading about the optimizations for FAT32->NTFS conversions. Thought I'd add this to help give a searching point. Looks like MFT optimization is what you have to worry about. But maybe BartPE with some cygwin stuff might help.

Hi, Ok, I found out what I wanted to know. It was or is a vulnerablitity in MSIE which has been fixed if you upgraded your computer. However, in spybot it continues to report it and should not. I see that in spybots next issues that will not appear any longer. It is nothing to worry about if your computer it updated as spybot is updating thier software also. Thank you DakotaSunRunner for pointing that out. I'm a big Spybot S&D user (even bill my clients the donation to support them) and was wondering how long MS would take to fix that.

Well I used to have that problem 'till in the task manager (CTRL-ALT-DEL) and right clicked on the "Applications" tab and selected "Go To Process" Task Manager will switch to the "Processes" tab with the offending program pre-highlighted. Right click on the highlighted process (sometimes have to sort by "Image Name" to avoid a moving target ), then select "End Process Tree" See Attached image for help. (Note: I've never had to kill firefox, it's just an example.)

Might I suggest Greenmachine's XPCREATE?!? have a look at this deep link... XPCREATE: The XP Distribution CD Creator with Hotfix Slipstreaming I've used his app/script? since pre SP1 and it's worked great. As you can see from the contents on the page linked above, he shows where to place both dotNet 1.1 and the service pack for it as well! Actually he also "slipstreams" WMP 10!!!