PVU

TC, I've noticed that your dynamic (Win2K) page no longer includes the User Profile Hive Cleanup option, but that it's still on your recommended list. The Fix 127GB barrier of Windows setup is a fairly new option - adding reg.exe in HFTOOLS (described as [load hives]). Was UPHClean replaced with something? BUMP: Tomcat76, are you now placing the Hive Cleanup msi in the HFSVCPACK_SW folder? I think you used to include it in HF, but that might have changed with newer (post 1.2.2) versions. TommyP's basic how to indicates: most MSI files are to be placed in HFSVCPACK_SW. Thanks

TC, I've noticed that your dynamic (Win2K) page no longer includes the User Profile Hive Cleanup option, but that it's still on your recommended list. The Fix 127GB barrier of Windows setup is a fairly new option - adding reg.exe in HFTOOLS (described as [load hives]). Was UPHClean replaced with something? I have seen Microsoft recycle stuff before. I wonder if this is just their way of pushing packages/updates that they want folks to install for problem solving issues - it might keep this in front of people.

nmX.Memnoch is correct, officially. But the 7.2 driver does work with Win2K. There is a "C2" inf. I don't know about the larger Catalyst program, but the driver works, if not supported.

TC, thanks. There's nothing wrong with HFSLIP and KB927779. I downloaded the hotfix for MDAC 2.8 without SP1 - MDAC28-KB927779-x86-ENU.exe, not with SP1 - MDAC281-KB927779-x86-ENU.exe. A little too hyper to get a new disk/install with 1.30 and a new MS security release batch all coming at the same time. After I ran HFSLIP, I used a program (Windows Unattended CD Creator) to establish TEXTmode (OEM) chipset and HDD drivers - a post setup. It's worked like a charm in the past. The time stamps in I386 for TXTSETUP.SIF, DOSNET.INF, SVCPACK.INF, and winnt.sif are all different than what was created by HFSLIP - all modified. It looks like that's my problem. I'll either have to start doing the TEXTMODE setup manually, or mess around with OlegII's solution. Human Error. No problem with HFSLIP. Thanks again. Addition: As far as running the CD Creator program to do a $OEM$ setup is concerned, I may try running the CD Creator program prior to running HFSLIP - it would create the $OEM$ stuff in SOURCE folder prior to running HFSLIP, not in SOURCESS after.

I haven't used HFSLIP for a while, but just did so with 1.3. All went pretty well except the install choked on/didn't install the latest MDAC 2.8 update, Security Update for Microsoft Data Access Components 2.8 Service Pack 1 (KB927779). This was placed in HF. All other hotfixes installed without issue - WU confirmed. I forget when the install of Win2K showed that it choked on KB927779, but it did (a black CMD box came up). With 1.3, HFGUIRUNONCE has been introduced. With that in mind (and I stayed away from HFGUIRUNONCE), all of the switchless programs I usually place in HFSVCPACK failed to install - TweakUI 1.33, vbrun60sp6.exe, and RyanVM's .NET1. All in all, a success. I may be missing something with HFGUIRUNONCE, but the MDAC 2.8 update KB927779 failure might be of interest. See the attached log. HFSLIP_log.txt

TC, I've been able to update/slipstream SP2 into a stand-alone Outlook 2003 Admin Install. The concept was explained here for FrontPage. Without a full Office 2003 disk, can I use your program? I'm assuming so, but I guess your answer to TAiN could also mean that you need a full Office 2003 disk in order to slip just one component (and the more I think about it, the more I'm afraid that this is the case). Also, your first line indicates that Office Patcher can silently update admin installs of the mainstream Office CDs with the latest service pack and hotfixes. Would a standard (not OEM), stand-alone, Outlook 2003 disk qualify as a mainstream office CD? Thanks

Follow-up: Outlook 2003 Updates are right here. SP2 is not indicated for Outlook, but that doesn't seem to be an issue - looks like you can slip. SP2. Same concept as outlined here for FrontPage. Or right here. msiexec /p C:\SP2\MAINSP2ff.msp /a C:\Outlook\OUTLS11.MSI shortfilenames=true /qb You can slipstream and individual Office 2003 Component (if it's not an OEM disk).

I've recently run into Outlook Express e-mail hell where compacting killed my inbox e-mails from June - Jan. So I'm moving to Outlook 2003. I have a stand-alone Outlook 2003 disk. When I load it, it reads OFFICE11. When I start the slipstreaming process and create an Administrative Installation Point, it offers: C:\Outlook. I guess the very simplified question is, can you slip Office 2003 SP1 into just one component without a full Office disk? I would then like to use TC's Office Patcher program to finish the job with additional hotfixes. I also have a stand-alone FrontPage 2003 disk, so the same issues probably apply - looking to create fully patched FrontPage 2003 and Outlook 2003 disks. Thanks. Addition: It doesn't look like SP2 applies to Either Outlook 2003 or Frontpage 2003, so I'm changing the title to deal with SP1.

Who here thinks it might just be best (for the long run - if you want to use the disk more than once) to not include LegitCheck, and the Malicious Software Removal Tool? Let's face it; you're gonna update that system.

OT: Maybe most folks knew this, but, like IE7, .NET 3 won't work/install on Windows 2000. (Not so) Slowly but surely, Mr. Softie is killing Win2K. Besides the other neat little programs that are being developed with the latest .NETs, my proprietary office program is now written in .NET (1 for now). Sooner or later, a forced upgrade is in the works. It might be well before MS stops "updating" 2000 in 2010. Too bad. I STILL prefer 2000.

Issue 1: Thanks. Is it stand-alone, or does it replace something. Without reading the bulletin, I'm guessing 925568 is a stand-alone update. Issue 2: So is KB925308 obsolete for Win2K? MS06-049 V2

Thanks for the link. The attached is the_guy's inf file. Addition: guy, the code in your inf is slighlty different than what MS and Gurgelmeyer are posting - Yours: HKLM,"System\CurrentControlSet\HAL","14140000FFFFFFFF",," 00000010" vs. HKLM,"SYSTEM\CurrentControlSet\Control\HAL","14140000FFFFFFFF",0x00010001,0x00000010 Does it matter for a post install? Addition 2: Tomcat76's inf: [Version] Signature = $Windows NT$ AdvancedINF = 2.0 [DefaultInstall] AddReg = AddReg.Halt [AddReg.Halt] ; 239887 HKLM,"System\CurrentControlSet\Control\HAL","14140000FFFFFFFF",0x00010001,16 HALT.INF

Thanks, guys (and the_guy). It was a worthwhile post for my machines that weren't created with HFSLIP or the G-Man's SP5. guy, I have a few machines here at the office. If you would attach your inf file, that would be great. Thanks again

I'm in. HFSLIP is a killer program.

Crow, I'm just getting into this $OEM$ integration also. I was interested in getting this done because I'm also using HFSLIP. Then I ran into Fernando1's various conversations about force-fitting difficult NVidia RAID drivers, and he mentioned a program called Windows Unattended CD Creator. It was developed by his friend, Vitali Graf. Go to: [url="http://www.vitaligraf.de/en/index.htm"]http://www.vitaligraf.de/en/index.htm[/url] I haven't used all of the features of the CD Creator, but I can tell you that it worked great integrating those Intel iaStor drivers. It also integrated (in PnP mode) the IntelINF drivers perfectly. The nice thing about this program as it will interest you is that it applies TEXTMODE drivers in the traditional $OEM$ manner. You may want to give it a shot. Vitaly is German, but you can setup the program for English, and he has an English forum. If you give it a go, let me know how it works out for you.

Al, would this also be true for integration in any pre-install/unattended setup? I had a problem with this just recently, although "human error" (mine) could have been at work. In other words, even if you are going to do a post install, will the INF look for the prounstl.exe? When I did a post install, I don't remember the update driver process going into executable mode. If I remember it correctly, I think it just picked up the driver via INF. Thanks

nuhi, this (RC8i) must have done it, because on the initial install it picked up the Intel® 82801FR SATA AHCI Controller (Desktop ICH6R). I will load it on the Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH) machine when I go to work. I'm assuming it will work. If I run into a problem I'll let you know. But no news will be good news. I don't need to do a full install right now, so I can't tell you about the Intel NIC drivers. But, if they had the same multi-selection issue, you should be in good shape there also. If it is still an issue, we'll see folks discuss it, I'm sure. I almost feel like formating this machine to see how it would all go - interested to see how the integration worked out for the NICs, and SigmaTel and SoundMAX audio drivers. For the Sigmatel drivers, I deleted the STHDA64.INF (64 bit files) before integration. Many thanks for your work on this specific issue. It may not have made it easier to deal with the NVidia drivers, but it looks like it took care on the Intel storage drivers. You might be done with RC8.

Fernando and LG, this may not mean a thing, but until Fernando asked about flagging both TEXTMODE drivers, I was not aware that you could flag more than one. So, I just created a disk by flagging both Intel SATA drivers (in the Intel TXTSETUP.OEM: iaAHCI_ICH7R = "Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)", and iaAHCI_ICH6R = "Intel® 82801FR SATA AHCI Controller (Desktop ICH6R)") which are both contained within the latest Intel Matrix Storage Manager, IATA55.EXE. I thought it was very much like nLite where you could only flag one. My mistake. Fernando, one thing is that when I have used the CD Creator in the past, not only did I not realize that you could flag more than one TEXTMODE driver, I also didn’t realize that you could choose “bad” for more force-fitting of a stubborn driver. Unlike the nVRaid drivers, I don’t think that these Intel drivers require a “bad” selection, because they’ve worked. Since I have only chosen one in the past, it seems to have imbedded just one without issue. I’m at work right now. When I go home, I will try the new 2-driver selected disk on the other computer to see if there’s a problem. My guess is that there won’t be – I should have selected more than one. I’ll post my results no matter what. As far as the CD Creator and PnP drivers are concerned, have you had any issues? nLite also seemed to have a tough time with my Intel NIC driver, so I’ve gotten a little skittish about trying to do too much. Your program installed the Intel chipset INF drivers without a problem. It also installed my ATI video drivers perfectly. If all I had to do is select more than one driver, this is the $OEM$ driver install program I was asking about. It really is a nice program. I like the way it asked me to get rid of the useless folders in my (HFSLIP) Win2K installation. Many thanks

The integration of TEXTMODE and PnP drivers is done in a similar way. The difference is the method to enforce the installation of not or not correctly digitally signed mass storage controller drivers. If you are using the CD Creator, all files of the driver subfolder are copied and usable for Windows setup (as with nLite), but additionally you have the possibility to enhance the installation of a critical textmode driver by flag him as "bad" controller driver. After having done this, the "bad" controller driver is something like "privileged" during the later OS install.Fernando, the Windows Unattended CD Creator funtionally only "embedded" the one TEXTMODE storage driver that I selected, and, based on what you've said, that is probably the intent. Even though the $OEM$ file shows all the drivers, it only picks up the one at install time. To verify, I re-did it selecting the other TEXTMODE driver, and, sure enough, the 2nd disk worked like a charm on my other machine, but wouldn't work on the original. Are you aware of any simple program (besides nLite that's having problems in this area right now) that will TEXTMODE embed all of the storage drivers? If not, I'm assuming the the CD Creator modifies the TXTSETUP.SIF - I can see the one driver. Can I add another line under [sCSI] for the other specific driver? Thanks again

Fernando, this maybe slightly off topic, but when I'm using the Windows Unattended CD Creator to add the Intel iaStor storage driver, the program asks me to pick one. Does it matter? Because the $OEM$ file that is created shows all of them, and the WINNT.SIF just makes reference to the file name. I ask this because I have 2 machines I want the install disk to be good for. Both machines would pull from the same storage file, but one is a ICH6R - 82801FR, and the other is a ICH7R/DH - 82801GR/GH. nLite would pull them all in. You would just have to pick one. Does the Windows Unattended CD Creator work the same way? Thanks again

TC, many thanks. You set me straight on switch issue. I think I need to get with the theme of the project - slipping hotfixes. Until your explanation, I thought HFSVCPACK_SW was there to slip in any program. This will be my first go (I've been itching to do it), so I'll go real simple at first, and then look to get (HFEXPERT) creative on my second try. BTW, your Windows 2000 updates for use with HFSLIP was great. I just replaced the Malicious Software Removal Tool and the KB902400.

I put the RyanMV's switchless programs and Tweak UI in HFSVCPACK, and MPsetup.exe in HFSVCPACK_SW. How do you tell what program is switchless? Is it correct to assume that most exe's go into HFSVCPACK_SW? FDV says that (in HFSVCPACK) "you can only use INF files that have a "DefaultInstall" section". There are a couple of Power Toys I'd like to include that have it. Do you have to include their dll files as well? If you setup a HFSLIP\SOURCE\$OEM$\$$\SYSTEM32 folder, would that take care of the Power toys? Thanks

Tom... I'm about to do my 1st HFSLIP. Generic question: Once the source file has been fully slipped/patched, do you need to get rid of all of the files that have been slipped if you want to slip a new file? Or, will HFSLIP simply recognize what's been done and slip what hasn't? I guess you could do a backup, execute again, and slip as they come on line, but that may be unnecessary.

I setup a workstation with Win2K3, and it works like a charm. However, I have a proprietary business program we run off our Netware server. The program sets up the Windows user as a workstation. I could not set it up. When I called in, the tech said that the program is recognizing me as a server, not a true workstation, and that it can’t be done. I followed the conversion directions to a T, but is there something you have to do in the way of killing a service (or something like it) to be recognized as a workstation, and not a server? Thanks

Tommy, I know you guys are doing it with HFSLIP. If you're not using HFSLIP, can you simply do it manually with a simple /s or /integrate command? No problem, right? I'm a little skittish after my nLite try - and it might have been the issue.