Flame12121 Posted December 29, 2005 Author Posted December 29, 2005 Manually slipstream SP2 into the source folder, create an iso and see if it works. If it works, then proceed to filling the HF folders and running HFSLIP.I've slipstreamed SP2 in, and sucessfully created an ISO from the SOURCE directory which does work, however, even with all the other directories empty (other than HFTOOLS), it still seems to be changing something that doesn't want to be changed, as the HFSLIP iso still fails.Well, I can't think of anything else that could influence HFSLIP running Having an active Internet connection might...If it does influence it, that would probably be the problem, why would having an internet connection matter though?
Tomcat76 Posted December 30, 2005 Posted December 30, 2005 If it does influence it, that would probably be the problem, why would having an internet connection matter though?It used to be in the instructions but I can't find it anymore. It was something about hotfixes updating themselves during execution when having a live Internet connection.
Flame12121 Posted December 30, 2005 Author Posted December 30, 2005 I've tried running HFSLIP while disconnected from the internet with no further progress, so, I'm going to highlight the differences that appear between the SOURCE and the SOURCESS directories.The following files are missing, they were in SOURCE but didn't make it to SOURCESSI386\DRIVER.CABI386\SP1.CABI386\sp2.cabEach of the following files changed (differences using TextPad's compare files, approximate diff format):I386\DOSNET.INF10944a10945,10950> > [OptionalSrcDirs] > svcpack > > [Files]> d1,HFSLIPWU.INF ;UPDATEI386\DRVINDEX.INFSee attachedI386\SVCPACK.IN_ -> SVCPACK.ININote: The filenames are capitalized differently in the two archives, don't know if that's significant.Compare: (<)C:\xp\SOURCE-svcpack.inf (137 bytes) with: (>)C:\xp\SS-SVCPACK.INF (208 bytes)1,9c1,13< [Version]< Signature="$Windows NT$"< < [SetupData]< CatalogSubDir="i386\hotfixes"< < [ProductCatalogsToInstall]< < [SetupHotfixesToRun]---> [Version] > Signature="$Windows NT$" > MajorVersion=5 > MinorVersion=1 > BuildNumber=2600 > > [SetupData]> CatalogSubDir="i386\SVCPACK"> > [SetupHotfixesToRun]> HFSLIP.CMD> > [ProductCatalogsToInstall]I386\SYSOC.IN_ -> SYSOC.INIThis one seems important to me, I thought all INF's MUST have a VERSION section, but this one has none in the SS version. Also, the filenames were capitalized differently here as well.Compare: (<)C:\xp\SOURCE-sysoc.inf (1849 bytes) with: (>)C:\xp\SS-SYSOC.INF (134 bytes)1,110d1< < [Version]< Signature = "$Windows NT$"< DriverVer=07/01/2001,5.1.2600.2180< < [Components]< NtComponents=ntoc.dll,NtOcSetupProc,,4< WBEM=ocgen.dll,OcEntry,wbemoc.inf,hide,7< Display=desk.cpl,DisplayOcSetupProc,,7< Fax=fxsocm.dll,FaxOcmSetupProc,fxsocm.inf,,7< NetOC=netoc.dll,NetOcSetupProc,netoc.inf,,7< iis=iis.dll,OcEntry,iis.inf,,7< com=comsetup.dll,OcEntry,comnt5.inf,hide,7< dtc=msdtcstp.dll,OcEntry,dtcnt5.inf,hide,7< IndexSrv_System = setupqry.dll,IndexSrv,setupqry.inf,,7< TerminalServer=TsOc.dll, HydraOc, TsOc.inf,hide,2< msmq=msmqocm.dll,MsmqOcm,msmqocm.inf,,6< ims=imsinsnt.dll,OcEntry,ims.inf,,7< fp_extensions=fp40ext.dll,FrontPage4Extensions,fp40ext.inf,,7 < msmsgs=msgrocm.dll,OcEntry,msmsgs.inf,hide,7< WMAccess=ocgen.dll,OcEntry,wmaccess.inf,,7< RootAutoUpdate=ocgen.dll,OcEntry,rootau.inf,,7< IEAccess=ocgen.dll,OcEntry,ieaccess.inf,,7< OEAccess=ocgen.dll,OcEntry,oeaccess.inf,,7< < WMPOCM=ocgen.dll,OcEntry,wmpocm.inf,,7< < < < Games=ocgen.dll,OcEntry,games.inf,,7< AccessUtil=ocgen.dll,OcEntry,accessor.inf,,7< CommApps=ocgen.dll,OcEntry,communic.inf,HIDE,7< MultiM=ocgen.dll,OcEntry,multimed.inf,HIDE,7< AccessOpt=ocgen.dll,OcEntry,optional.inf,HIDE,7< Pinball=ocgen.dll,OcEntry,pinball.inf,HIDE,7< MSWordPad=ocgen.dll,OcEntry,wordpad.inf,HIDE,7< ZoneGames=zoneoc.dll,ZoneSetupProc,igames.inf,,7< < < < TabletPC=tabletoc.dll,TabletSetupProc,Tabletpc.inf,HIDE,7< < < < Freestyle=medctroc.dll,MedCtrOCISetupProc,medctroc.inf,HIDE,7< < < < netfx=netfxocm.dll,UrtOcmProc,netfxocm.inf,hide,7< < < < [Global]< WindowTitle=%WindowTitle%< WindowTitle.StandAlone="*"< < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < [Components]< msnexplr=ocmsn.dll,OcEntry,msnmsn.inf,,7< < < < [Strings]< WindowTitle="Windows Professional Setup"< WindowTitle_Standalone="Windows Components Wizard"111a2,3> [Components] > WinUpdate=Ocgen.dll,OcEntry,HFSLIPWU.INF,HIDE,7I386\TXTSETUP.SIFCompare: (<)C:\xp\HFSLIP\SOURCE\I386\TXTSETUP.SIF (472007 bytes) with: (>)C:\xp\HFSLIP\SOURCESS\I386\TXTSETUP.SIF (472044 bytes)7296d7296< sp2.cab = 100,,,,,,_x,39,0,016351d16350< DriverCabName=driver.cab,sp2.cab17023d17021< hscxpsp1.cab , 13919490d19487< sp2.cab = 1621832c21828,21833< ---> [WinntDirectories] > 999 = HFSLIP > [SourceDisksFiles]> HFSLIPWU.INF = 1,,,,,,,20,0,0 ;UPDATE > [SetupData] > DriverCabName=driver.cabThe following files appeared in SOURCESS and were not originally in SOURCEI386\HFSLIPWU.INFI386\SVCPACK\HFSLIP.CMDBoth of these files are also attached in case their contents are important.attach.zip
tommyp Posted December 30, 2005 Posted December 30, 2005 (edited) HFSLIP merges SPx.cab and the driver.cab to make a new driver.cab. There should be a file called driver.cab in the i386 folder. Are you sure it's not there? What happens when you expand the driver.cab file in the non-hfslipped-slipstreamed sp2 in your source folder? What is the hscxpsp1.cab file in the source\i386 folder? That filename is new to me. I'll bet that you have something wrong with your driver.cab file. The reason I say this is because HFSLIP expands that file, and after slipstreaming makes a directory listing of the extracted driver.cab file and puts it into the driver.inf file. But your driver.inf file is pretty much empty. So either you are missing expand.exe from your system32 or your driver.cab file is f'd up. Try this to test out your source\i386\driver.cab file. Open a command box and change the working directory to your HFSLIP directory (like I mentioned in a previous post). Type this in and see if there are errors in the sourcess\i386\driver folder:MD SOURCESS\I386\DRIVEREXPAND SOURCE\I386\DRIVER.CAB -F:* SOURCESS\I386\DRIVERBTW, have you tweaked your memory via regedits or anything like that? Edited December 30, 2005 by tommyp
Flame12121 Posted December 30, 2005 Author Posted December 30, 2005 HFSLIP merges SPx.cab and the driver.cab to make a new driver.cab. There should be a file called driver.cab in the i386 folder. Are you sure it's not there? What happens when you expand the driver.cab file in the non-hfslipped-slipstreamed sp2 in your source folder?DRIVER.CAB really isn't in the SOURCESS\I386 directory. I'm able to open the file in SOURCE using 7zip and it's got a rather long file list.What is the hscxpsp1.cab file in the source\i386 folder? That filename is new to me.Hmm, I'm rather confused on that one too, the file doesn't exist anywhere in the SOURCE directory tree.I'll bet that you have something wrong with your driver.cab file. The reason I say this is because HFSLIP expands that file, and after slipstreaming makes a directory listing of the extracted driver.cab file and puts it into the driver.inf file. But your driver.inf file is pretty much empty. So either you are missing expand.exe from your system32 or your driver.cab file is f'd up. Try this to test out your source\i386\driver.cab file. Open a command box and change the working directory to your HFSLIP directory (like I mentioned in a previous post). Type this in and see if there are errors in the sourcess\i386\driver folder:MD SOURCESS\I386\DRIVEREXPAND SOURCE\I386\DRIVER.CAB -F:* SOURCESS\I386\DRIVERI tested the cab's integrity using 7zip's test function, and it's a valid cab file, BUT I did just realize something... I have the Unix Utilities package at the front of my path variable, and in it is a command called expand, which has nothing whatsoever to do with cab files. I'm going to reorder my path now and see if things improve. I'll post a followup.BTW, have you tweaked your memory via regedits or anything like that?Not to my knowledgeAs a general suggestion, perhaps the EXPAND.exe in the I386 directory should be specifically used instead, in case someone else has badly named programs in their path?
Flame12121 Posted December 30, 2005 Author Posted December 30, 2005 Reordering my path does seem to have fixed the problem. Thanks for your help everyone
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now