Jump to content

problem with INF's in HFSVCPACK


Recommended Posts

Posted

I am new to posting - have used HFSLIP for over a year now

having a problem with 1.3.0 - does not want to install my INF's in the HFSVCPACK folder

I get a dialog box 6 times during the Win2k install that says "Installation Failed" - I have 6 INF's in the HFSVCPACK folder and none of them get installed

I am using an exact copy of my HFSLIP 1.2.2 folder for testing (except of couse for the 1.3.0 CMD file)

am I missing something between 1.2.2 and 1.3.0?

Thanks!


Posted

hi z80! those infs are supposed to executed at T-13 when placed in HFSVCPACK directory ... i'm not so sure if TC modified something in the code but it may help if you post your HFSLIP.log at least ... ;)

Posted

here is my log file... thanks!

This file is automatically generated by HFSLIP

HFSLIP is for personal use only

Copyright© TommyP 2005-2007

============================HOW TO REPORT A PROBLEM============================

If running into problems, refer to http://hfslip.org/support.html

HFSLIP support forum: http://msfn.org/board/index.php?showforum=129

===============================================================================

HFSLIP Version - 70216

HFSLIP Path - E:\hfslip\

OS in SOURCESS - 2000 SP4 English

MSIE Version - 2KIE6

DirectX Slipstreamed

Drivers - SPX.CAB Added

CD Install Path - Default

CDTAG - CDROM_NT.5

===============================================================================

Files in your FIX folder:

WINNT.SIF

Files in your HF folder:

IE6.0sp1-KB833989-x86-ENU.exe

IE6.0sp1-KB887797-Windows-2000-XP-x86-ENU.exe

IE6.0sp1-KB905495-Windows2000-x86-ENU.exe

IE6.0sp1-KB929969-Windows2000-x86-ENU.exe

OE6.0sp1-KB923694-Windows2000-x86-ENU.exe

Windows2000-KB891861-v2-x86-ENU.EXE

Windows2000-KB893756-x86-ENU.EXE

Windows2000-KB896358-x86-ENU.EXE

Windows2000-KB896423-x86-ENU.EXE

Windows2000-KB896424-x86-ENU.EXE

Windows2000-KB899587-x86-ENU.EXE

Windows2000-KB899589-x86-ENU.EXE

Windows2000-KB900725-x86-ENU.EXE

Windows2000-KB901017-x86-ENU.EXE

Windows2000-KB901214-x86-ENU.EXE

Windows2000-KB902400-x86-ENU.EXE

Windows2000-KB904706-DX9-x86-ENU.exe

Windows2000-KB905414-x86-ENU.EXE

Windows2000-KB905749-x86-ENU.EXE

Windows2000-KB908519-x86-ENU.EXE

Windows2000-KB908531-v2-x86-ENU.EXE

Windows2000-KB911280-v2-x86-ENU.EXE

Windows2000-KB912919-x86-ENU.EXE

Windows2000-KB913580-x86-ENU.EXE

Windows2000-KB914388-x86-ENU.EXE

Windows2000-KB914389-x86-ENU.EXE

Windows2000-KB917008-x86-ENU.EXE

Windows2000-KB917344-56-x86-enu.Exe

Windows2000-KB917422-x86-ENU.EXE

Windows2000-KB917537-x86-ENU.EXE

Windows2000-KB917736-x86-ENU.EXE

Windows2000-KB917953-x86-ENU.EXE

Windows2000-KB920213-x86-ENU.EXE

Windows2000-KB920670-x86-ENU.EXE

Windows2000-KB920683-x86-ENU.EXE

Windows2000-KB920685-x86-ENU.EXE

Windows2000-KB920958-v2-x86-ENU.EXE

Windows2000-KB921398-x86-ENU.EXE

Windows2000-KB922582-x86-ENU.EXE

Windows2000-KB923191-x86-ENU.EXE

Windows2000-KB923414-x86-ENU.EXE

Windows2000-KB923689-x86-ENU.EXE

Windows2000-KB923980-x86-ENU.EXE

Windows2000-KB924191-v2-x86-ENU.EXE

Windows2000-KB924270-x86-ENU.EXE

Windows2000-KB926121-x86-ENU.EXE

Windows2000-KB926247-x86-ENU.EXE

WindowsMedia-KB911564-x86-ENU.exe

WindowsMedia6-KB925398-x86-ENU.exe

WindowsXP-KB928388-x86-ENU.exe

Windows2000-KB924667-x86-ENU.EXE

MDAC253-KB927779-x86-ENU.exe

Windows2000-KB918118-x86-ENU.EXE

IE6.0sp1-KB928090-Windows2000-x86-ENU.exe

Windows2000-KB926436-x86-ENU.EXE

Windows2000-KB928843-x86-ENU.EXE

Files in your HFCABS folder:

BDANT.cab

BRANDING.CAB

dxnt.cab

IEW2K_1.CAB

IEW2K_2.CAB

IEW2K_3.CAB

IEW2K_4.CAB

mailnews.cab

OEEXCEP.CAB

scripten.cab

wab.cab

Files in your HFSVCPACK folder:

boot.inf

DOSHERE.INF

drives.inf

drives.lnk

EXPLORE.INF

icw.reg

intl.reg

LockWork.inf

LockWork.lnk

PATHC300.DLL

PATHC300.HLP

PATHC300.INF

Files in your HFSVCPACK_SW folder:

Files in your HFGUIRUNONCE folder:

Files in your HFTOOLS folder:

boot.bin

cygwin1.dll

EXTRACT.EXE

HFANSWER.INI

mkisofs.exe

Files in your HFAAO folder:

dtool347.cab

===============================================================================

Posted (edited)

Are all your HFSVCPACK files present in SOURCESS\I386\SVCPACK?

If so, can you ZIP HFSLIP.CMD from the same folder and attach it here?

Edited by Tomcat76
Posted

The only difference between 1.2.2 and 1.3.0 is that the INF file names including their path are quoted in the installation command. If you know how to rebuild the ISO manually, then edit HFSLIP.CMD to remove the quotes in the lines that install your INF files. I hope the quotes are not the problem...

Posted

no joy...

still get 6 "installation Failed" messages

difference this time was that a large black dos box was on the screen behind each error dialog box

attached find the modified CMD file used in the iso

HFSLIP.CMD

Posted

The changes you have made resemble what HFSLIP 1.2.2 would've done so if it worked before it should've worked now too. Are you sure you didn't change anything in the INF files?

I can see two other potential reasons but they would've caused INF installations to have failed ever since that feature was introduced...

Posted

no changes made - I even rebuilt the 1.2.2 iso again and tested it earlier today and it works perfectly

then I copied the entire 1.2.2 folder and replaced ONLY the 1.3.0 CMD file - reran it again and the problem shows up

I can try using the 1.2.2 HFSLIP.CMD file from the 1.2.2 iso SVCPAK inserted into the 1.3.0 iso if you like - I noticed there are a few other differences besides the quote marks

I can also start comparing the 1.2.2 iso to the 1.3.0 iso and see what other differences I can find but that would take some time and I wouldn't be able to get that done tonight

are there any other reports of this problem?

am I trying to do something unconventional here?

thanks for your attention - I've spent most of the weekend trying to figure out what I messed up - it's always worked so well before for me

Posted

FYI... tried using the HFSLIP.CMD from SVCPACK in the 1.2.2 iso wilth the same negative result

done testing for now

Posted

test version FIXED the problem!

guess I should have just waited for the next release

thanks very much for your attention and for a great product!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...