killerb255

See this topic: http://www.msfn.org/board/index.php?showtopic=44048 In particular, the issue is not fully resolved. You can slipstream just about any update and avoid WFP popups EXCEPT for IE7 and MP11.

The e-mail SSL port is 995. You need to change this in your POP settings.

Using a PE disc with submix8c's suggestion (like BartPE or WinPE 2.0) might not be a bad idea... Even better would be an updated virus scanner loaded on the PE disc (or a browser that can store an online virus scanner's cookies on the RAM drive).

Shelax: Nobody's calling you a liar. The only hint of negativity in this entire topic is the Windows XP "Service Pack 3." I can see that there's a language barrier here (I don't think English is your first language--please don't take offense to this assumption). That's not a bad thing in itself--it just causes certain words to be misinterpreted... Anyway, there is no real SP3 yet. The SP3 you downloaded was, as you said, SP2 with a bunch of updates on it. SP2 with a bunch of updates on it is not SP3. SP2 with a bunch of updates on it is SP2 with a bunch of updates on it. I have heard that there was something called "SP3" among various pirate distribution channels (illegal, meaning we don't talk about that on this forum). Here's my question to you: Do you either: a) have swappable hard drives? Each hard drive has an operating system on it. For example, if you are running Fedora now and you want to run OSX later, you would turn your computer off, remove the Fedora drive, put the OSX drive in, and turn your computer back on. or b) choose between your operating systems with a bootloader? On the bootloader, you select which operating system you want and press Enter. If your answer is A, then you might have a bad Windows XP SP2 hard drive. If your answer is B, then either your bootloader didn't like having so many operating systems to deal with at one time or SP2 doesn't like your bootloader. The "SP3" you referred to (again, this is NOT SP3...just SP2 with a bunch of updates) probably has an update that fixed this particular problem and a raw SP2 (meaning SP2 with NO updates) may have caused a problem at the time it was released.

Your best bet would probably be to create a scheduled task that edits the autochk registry key to automatically check all drives on reboot, then resets the key (otherwise, autochk will run on every reboot). Or...you can create a batch file that runs off of your Scheduled Task with a series of questions asking you if you want to check certain drives. If yes, then it gets entered into the The reg key is: HKLM\System\CurrentControlSet\Control\Session Manager Under that is a string value. The default is: BootExecute = autocheck autochk * The asterisk means that no drives are being checked on startup. I'd give this a read before doing anything: http://www2.isye.gatech.edu/~mgoetsch/cali...nofCHKDSK_F.htm

WINNT.SIF is the unattended answer file. If you remove that, the installer will *try* to run as a standard installer. The reason I emphasize *try* is that, like Iceman said, it depends on what you did with the installer files using nLite.

Well...here's the deal. Vista uses an entirely different bootloader than previous versions of Windows. This means that either a) Vista MUST be installed LAST in order to use its bootloader. or b) You'll have to use a third-party bootloader.

That would be your best call.i tried it and it works. The company I work for does this religiously. Use BartPE, WinPE (any version), or an Ultimate Boot CD (DOS or Windows). Ghost 8 is perfect for this, as there are 16 and 32-bit executables that can be used on DOS or Win-based boot disk©s respectively.

http://www.byremote.com.au/Hip/mce_remote_faq.htm

Can you give us a specific example of when this issue comes up? Are you recording TV from satellite? Cable? What tuner are you using? System specs? Driver date(s)?

...and here's Step 9, just in case. step9.7z

If you have XP Pro, just use the ntbackup command...

Not even close, NaDer (although I can understand why you were confused--bobbintb wasn't exactly clear): What he's wanting is to be able to put a second WINS (Windows Internet Naming Services) server IP in Network Settings. From what I see, there is no way to add a second WINS server IP address in, nor is there a way to add more than two DNS servers.

Perhaps autologon bypasses various User and Computer Configurations in "Local Security Policy" on first boot? Try rebooting after your OS install.

Typically, System Restore only allows you to roll back to various driver/registry (and some program) settings. I would try using Vista's built-in backup utility (Home Basic doesn't come with a backup utility and Home Premium comes with a stripped-down version of it). If you type "Backup" in the search box, one of the options that comes up is the "Backup and Restore Center." Use that.

Hi mate, I've checked the sfcfiles.dlls that you posted (thanks again!) and have noted that the only one that is getting modified is the one in Step 7. The others remain unmodified compared to a vanilla install. This is useful to know as it means that none of the other tools you used are modifying it in any way, which is good for debugging purposes as we can rule out possible interference from them. That's definitely good to know. So basically, nLite's procedure for slipstreaming IE7 and/or Media Player 11 Slipstreamer's procedure for slipstreaming MP11 is/are modifying sfcfiles.dll, breaking WFP. In any case, I'll go ahead and repeat Step 9 as well to see if any updates to IE7/MP11 modify it further.

Thanks for your hard work testing this out, killerb255. Can you please do one last test, and compare the sfcfiles.dll file from a build you have that does not have WFP popups, with a build that you *do* get the popups in? If I'm reading it right, something must be happening between steps 7 and 8 above, which from your description points to something to do with IE7 or WMP11. I don't use IE7, but apparently it's a big update so maybe it does something to sfcfiles.dll. So If you can save a copy of sfcfiles.dll from step 7, then compare it to an sfcfiles.dll in step 9. sfcfiles.dll is in %systemroot%\system32\sfcfiles.dll Basically I just need to know if the file is identical from both your steps 7 & 9 or if it changes at all. Okay, I have the sfcfiles.dll from Steps, 3, 5, and 7 attached. I made a mistake during Step 7 before and left the slipstreamed XP ISO mounted. Therefore, the WFP popups wouldn't show up. I repeated Steps 3, 5, and 7 to get these files, and I got a WFP popup on Step 7. I didn't bother repeating Step 9 for that reason... step3.7z step5.7z step7.7z

That will happen if IE6 or Media Player 11 updates are integrated or nLite'd into the install.

Thanks for your hard work testing this out, killerb255. Can you please do one last test, and compare the sfcfiles.dll file from a build you have that does not have WFP popups, with a build that you *do* get the popups in? If I'm reading it right, something must be happening between steps 7 and 8 above, which from your description points to something to do with IE7 or WMP11. I don't use IE7, but apparently it's a big update so maybe it does something to sfcfiles.dll. So If you can save a copy of sfcfiles.dll from step 7, then compare it to an sfcfiles.dll in step 9. sfcfiles.dll is in %systemroot%\system32\sfcfiles.dll Basically I just need to know if the file is identical from both your steps 7 & 9 or if it changes at all. Sure thing, bub. I'll probably have the test results sometime by the end of the week.

I just tried it out doing the following: 1) Copied a virgin Windows XP Professional Corporate CD's source files to my test box. 2) Slipstreamed SP2 using the /integrate switch 3) Test using VPC2007. Works fine. 4) Slipstream a bunch of updates using the following: http://smithii.com/slipstream_xpsp2. 5) Test using VPC2007. Works fine. 6) nLite 1.4 beta Internet Explorer 7 and Windows Media Player 11 (using the WMP11 Slipstreamer) 7) Test using VPC2007. No Windows File Protection popups! (1.3.5 had the WFP popups) 8) Slipstream remaining updates using nLite 1.4 beta (including updates for IE7 and WMP11). 9) Test using VPC2007. Windows File Protection problem is back... Just FYI.

Never mind--I solved the problem. wkst32 edits: Omissions in bold. Additions in italics t:\i386\winnt32 /m:t:\i386\ /syspart:c: /tempdrive:c: /makelocalsource /unattend:t:\wkst\%TRACK%.txt In any case, slipstreaming the hotfix for the Vista diskpart craziness combined with this worked like a charm!

In your answer file, put the following line in: [unattended] FileSystem=ConvertNTFS

Is there anyway to slipstream IE7 and have its files saved in 8.3 format? The .DLL.MUI folders especially cause DOS-based unattended installs to crap.

I dunno about Roxio 8, but here's what I used for Roxio 9: setup.exe /qn RX_EULA_ACCEPTED=1 Reboot=ReallySuppress ROX_KEYTEXT="XX-XXXXX-XXXXX-XXXXX" ADDLOCAL=ALL REMOVE=GoogleToolbar,SightSpeed,MediaManager,MediaCapture,DivXCreator,PhotoSuite,VideoWave,VirtualDr ive,RoxioCentral

nLite will currently slipstream IE7 into XPSP2. However, it tends to put long file names (not 8.3) in your i386 folder. If you're using a DOS-based unattended install, this can be a bad bad thing without $$rename.txt...