[PVU]

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.

Attached File(s)

•  HFSLIP_log.txt (4.07K)
  Number of downloads: 7

This post has been edited by PVU: 18 February 2007 - 11:29 PM

[Tomcat76]

I can't confirm any of this. I just did a test with all hotfixes (including MDAC 2.8 SP1 and KB927779 for MDAC 2.8 SP1) and with the following in HFSVCPACK:
2K.REG
AR800.exe (Adobe Reader 8.0)
DNF11.exe (.NET 1.1)
DNF20.exe (.NET 2.0)
jre600.exe (Sun Java Runtime 1.6.0)

Everything installed as intended and Windows Update shows 0 updates.

I also did a test with some INF files in HFSVCPACK. There are problems with those, but they didn't break the installation of other components.

Make sure the KB927779 hotfix you have is not corrupted. It should have a size of 1,872,168 bytes.

[PVU]

Tomcat76, on Feb 19 2007, 05:37 AM, said:

Make sure the KB927779 hotfix you have is not corrupted. It should have a size of 1,872,168 bytes.

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.

This post has been edited by PVU: 19 February 2007 - 11:25 AM