Electrician

@Gurgelmeyer For my two cents - could you could put something in the option pack to PREVENT messenger from installing? So what is supposed to be so evil about BITS 2? I have "dutifully" upgraded all the machines at work (over 70) and have not seen anything that made me think it was fouling the works. BTW When all is said and done, perhaps a more detailed explanation of the process (blog?) you went through to do this astounding piece of work, would be helpful to those who may wish to pursue a similar endeavor. At least it would make for interesting reading!! Your skill-set must be killer!! or, in the common vernacular, YOU RULE! @slippykillsticks BITS 2.0 is already available seperately - from good ol' MSoft.

Tommy, noticed the INF files are missing from the Apr 23 zip file. Is that a faux pau, or did you find some other way? Now that I have gotten 'work' out of the way, I can play with this project again. yay.

From that very article is this line: So take out the Language= line...? Me, I barely speak proper english - and I grew up here! Engrish ok by me. So waddah I know?

Although I have been having another problem making the disk, I noticed that as well. When I ran the patch manually it would error out and tell me that I had to have OE 6 sp1 installed to use the patch. The OE 6 sp1 patch that can be dwnld'd from M$ also errors out and says you must be running XP. Since the files are slipstreamed, just do Like TommyP suggests and apply the reg hack.

I vote yes for NET 1.1, and XML, and MDAC, etc. As for uninstalling, I was thinking of those who detest media player and IE, etc etc. and having everything in one do-or-die pack would prevent some from using it. Personally, I don't use/want any kind of IM service (for example). And have specific req for using MediaPlayer 9 - but not 10, and tho I tend to use the latest DirectX, I am never an early adopter when M$ updates, due the track record. @Gurgelmeyer by "Seperate modules" I take it you mean for you, not for the end user? Or will this have an installation chk list?

@tommyp Sorry, but already have said dll. Just left it out of original msg (brevity). Do not have XP sp1 DO have XP sp1a CD and used it the first three go-rounds. My XP sp1a disk is a Dell oem. My vol lic XP CD is RTM version, and my vol lic 2K CD is SP2 (i think). Thinking there might be something odd with the oem files, or you really are using sp1 files, I tried the ones from the service pack. My reason for doing the updates in the svcpack is because I have had this problem from the start and wanted to reduce other factors (relating to the slipstream). One more test I haven't tried.... I will build a disk with NOTHING but but IE6 slipstreamed, and test it - will report back shortly. edit -Same problem with file not signed. (no patches, but no bad chksums) Will build from non integrated source to verify that it works and assuming it does will run your batch without even the ie integration. btw, i always get this (i ASSumed it was not a real problem): Could Not Find E:\w2ksp4IE6\HFFILES.TXT Could Not Find E:\w2ksp4IE6\HFFLDRFEXP.TXT 'FILECASE' is not recognized as an internal or external command Did I assume wrong?

@tommyp and Bilou_Gateux I am still having the same problem as from the first attempt made. The install goes wonderfully, except that during the "final tasks" stage, I get an error message that a file is not digitaly signed. The more info button says the file is IEINFO5.OC_ and I have to click on continue . I backed tracked from my original file set untill I have the following sequence Win2k pro vol lic Cd Slipstream SP4 IE6 sp1 as downloaded from M$ site (not using my IEAK'd setup) Applying ONLY DX9c and IE6 extracted IE.in_, msoe50.in_, etc from a download of XP xp1a. Only use the setupapi.dl_ and sfc.dl_ from FDV's site. None of his other stuff. (I don't like turning off SFC but hoped it would kill that D*** msg) This is a s clean as it gets - ain't it? I also apply all sec updates by using the svcpack. Also, in testing this I have run hfNEtchk on the resulting build. It tells me that five of the files have invalid checksums (but expected version). WU and qfechk are happy. the 5 files (even after re-applying updates) are cryptdlg.dll, ntvdm.exe, user32.dll, ole32.dll, msadce.dll Any ideas what the heck I am doing wrong? Bilou_Gateux I am not clear on your procedure but I need to re-read this thread when I still have a couple of working brain cells. (been a long day). cao

@Gurgelmeyer WOW! Bless you a thousand fold. I do have one conceptual problem with what you are doing. If you put everything in one super-pack, then the only way to uninstall any component is to blow them all out. May I suggest keeping IE, MDAC, etc in a functionality pack separate from the security "rollup"? btw Remote desktop uses the same underlying tech as the Terminal Services Client. However, the terminal server portion that is in XP pro is gratis ONLY for XP pro. To use it's components in windows 2k will violate the law. Terminal server requires a lic from ol M$. Tread carefully. I would hate for the M$ vampires to swoop down and kill this thing. The client side of Terminal server is free and could be included (in functionality pack?). Again, thanks for your work, eagerly awaiting the rtw.

GDR versus QFE I tried to find out what they stand for. Golly, searching the web-at-large, all led back to various MSoft update notices! Did find a nice article about update exe here; http://www.microsoft.com/technet/prodtechn...t/winupdte.mspx As near as I can get, it seems that if a rollup finds fixes that were applied since the previous rollup, it deletes them and replaces files with the ones in the new rollup, unless the key is set. If the ket IS set, then it (RE) applies hot fix files that were released between the previous rollup and the new rollup. Why the new rollup doesn't BY DEFAULT replace with all newer files is confusing as H***! Gotta leave for a Sarbanes-Oxley 3-day (kill me now) so no time to delve deeper. (Unless this is about NOT replacing with newer files when an older ver of a program is installed like IE6 v/s IE6 sp1)

@msfn11 The IEAK displays the default language of the system it is running on. Change the computers language and restart the IEAK wizard.

(Just started down this path...) So you guys are saying this CMD file can integrate DirectX 9C without requiring user interaction? I would swear I had tried the switches (QA & RN) before - and it didn't work. Though I do have the dx9ntopk (aka 9B) now. <EDIT> Ok. Repack files with a modified setup.exe. Done! <TX Hirudin> Also, MDAc ver 2.53 ?? Why not 2.8? @tommyp You saidIf you want to run windows2000, you need FDV's sfc and setupapi files Where would this be? - ah geez, am I lame? fred (www.)vorck.com - didn't make the connection before. Sorry.