Flame12121

Reordering my path does seem to have fixed the problem. Thanks for your help everyone

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. Hmm, I'm rather confused on that one too, the file doesn't exist anywhere in the SOURCE directory tree. I 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. Not to my knowledge As 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?

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 SOURCESS I386\DRIVER.CAB I386\SP1.CAB I386\sp2.cab Each of the following files changed (differences using TextPad's compare files, approximate diff format): I386\DOSNET.INF 10944a10945,10950 > > [OptionalSrcDirs] > svcpack > > [Files] > d1,HFSLIPWU.INF ;UPDATE I386\DRVINDEX.INF See attached I386\SVCPACK.IN_ -> SVCPACK.INI Note: 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.INI This 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,7 I386\TXTSETUP.SIF Compare: (<)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,0 16351d16350 < DriverCabName=driver.cab,sp2.cab 17023d17021 < hscxpsp1.cab , 139 19490d19487 < sp2.cab = 16 21832c21828,21833 < --- > [WinntDirectories] > 999 = HFSLIP > [SourceDisksFiles] > HFSLIPWU.INF = 1,,,,,,,20,0,0 ;UPDATE > [SetupData] > DriverCabName=driver.cab The following files appeared in SOURCESS and were not originally in SOURCE I386\HFSLIPWU.INF I386\SVCPACK\HFSLIP.CMD Both of these files are also attached in case their contents are important. attach.zip

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. 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?

tommyp: Yes, I intend on making a SP2 disk, but since I've been having problems, I took the same approach I usually take to programming, reduce the problem to the simplest case that still demonstrates the error. I currently have an XP-SP1 disk. As the source is unchanged and the only other directory with any contents is HFTOOLS, it was my understanding that running HFSLIP on it would do nothing, and the SOURCESS directory would contain effectively the exact same copy of the XP-SP1. While the ISO made from the SOURCE directory does work however, the ISO from the SOURCESS directory does not, which leads me to believe something changed, I just don't know/understand what or why.

Can you open these files? Are they all readable? They all appear to contain valid INI formatted INF commands, starting with the normal [Version] section. I have 11 GB free, and while I have yet to run a recent scandisk, the last one was only 6 months ago and showed no problems. I will do another and post an update. Update: Well I ran it, and to my knowledge it didn't find anything, I wasn't watching it as it worked and I can't find the log it usually makes if it found a problem. Yes, I've been trying to emphasise that this is SP1 in case it mattered. SP1 is currently in the source folder, as I wanted to be sure it was OK before I made any changes to it. I'm running HFSLIP on a machine running XPSP2 - fully patched.

Yes, I've doublechecked, it's a complete disc copy. The HFSLIP directory contains: FDVFILES (empty) FIX (empty) HF (empty) HFCABS (empty) HFSLIP_51218.CMD HFSVPK (empty) HFSVPK_SW (empty) HFTOOLSboot.bin cygwin1.dll mkisofs.exe modifyPE.exe MSICabExtract.exe MSICabExtract.txt [*]SOURCE [*]SP1.iso - this is the ISO created directly from the SOURCE directory, it does function. LAYOUT.inf is present and has contents SYSOC.IN_ exists, and contains SYSOC.INF SYSSETUP.IN_ exists and contains SYSSETUP.INF TXTSETUP.SIF is present and has a filesize of 444kb

tommyp: Following your directions, I was able to turn my unaltered direct copy from CD to SOURCE XP-SP1 cd into a functioning iso, and have done a complete install on the virtual machine using that ISO, so the SOURCE directory, unpatched, seems to be fine. I ran HFSLIP on it (still with nothing in any of the other directories other than HFTOOLS,) and it gives me the "Setup cannot access the CD containing the Windows XP installation file" error again. ~ Flame12121 ERROR_REPORT.TXT

In regards to 1, already done, I just haven't posted a new file list (wasn't aware anyone had looked at it recently, if you desire, I'll post another). The iso is being created, it just suffers the same problem that Nero had. 2-5 Sorry, I seem to have miscommunicated. Before every trial I have been copying the files off the original CD once more. In this case, I meant removing the files in HF, HFEXPERT, HFSVPK etc leaving them empty. The only directory with any contents at this point is the completely untouched XP disc copy in SOURCE, and the HFTOOLS directory, containing everything it contained before, and the mkisofs program. Hope that explains the current situation a little better, and on a somewhat related note, I'm begining to wonder if there is something wrong with the CD drive I was using to copy the CD, it's a Plextor PX712SA, and they seem to have a reputation for bad reads, I'm repeating the previously mentioned experement with another drive now. ~ Flame12121 *Followup: The other drive didn't seem to improve matters*

Unfortunately the auto-iso generation doesn't seem to work either, I've systematically started removing elements until I'm now working with the original CD copy, unpatched, and all the other directories that HFSLIP creates have been emptied, at this point, the files going in should be identical to the files going out, correct? If they should, then I think I have a problem, I have a directory comparison program that I used on both sets, and the following files had changed: I386\DOSNET.INF I386\DRVINDEX.INF I386\SVCPACK.IN_ I386\SYSOC.IN_ I386\TXTSETUP.SIF I don't know if this is significant, but the iso built with this run gives the same problem that I had the first time: "Setup cannot access the CD containing the Windows XP installation file".

A valid point that I had overlooked. I'll fix it next attempt. On a more positive note: I think I've figured out the source of my problem. After sucessfully getting Alcohol to rip an iso from the cd directly, and noticing the link to http://www.tacktech.com/display.cfm?ttid=297 in the HFSLIP tutorial, I changed some of the Nero settings... specifically I changed the "Load segment of Sectors" from the default 07C0 to 0000 and I changed the ISO settings to ISO 9660 + Joliet, Max of 31 characters, and enabled all of the "do you want to break _____ rule" checks. I've managed to sucessfully install from an iso built from my SOURCE directory, now I'm off to patch it to SP2, and see if I can get the rest of the thing working ~ Flame12121

Unfortunately that's what makes the error cryptic, it isn't specifying what it's trying to do with the disk, only that it can't read it. It then suggests that I either hit Well, I can install directly from the CD without any problems, if I do as you suggest here and copy the files off the disk and make a second iso, that too has problems, but not the same as the first. This one starts complaining with actual file names, the first of which was cyclad-z.inf, which it complained "Setup cannot copy the file" and offered to let me retry (which didn't help), skip the file or abort the install. I've checked it each time, the ISO is still captured.

I have: WIN51 WIN51IP WIN51IP.sp2 In the root of the SOURCESS directory. I think those are the XP equivilants.

First, a confession: I know less than nothing about what I'm trying to do. I started by following the directions at http://www.vorck.com/hfslip.html In an effort to test my progress toward a slipstreamed XP Pro disk, I've installed a trial of MS Virtual PC 2004, but in the process of testing the disk, I keep running into a rather cryptic error immediately after it finishes formmatting the destination drive: "Setup cannot access the CD containing the Windows XP installation files." This is working from an ISO built with Nero Burning ROM. Unfortunately, since I don't really understand the error, I'm not sure what information may be useful. It sounds like it's complaining about a missing file, but I can't be certain what it means. Thinking it might be a missing file, i've tried copying the complete XP source disk into the SOURCE directory and repatching, I've tried changing the ISO format, and mounting it on an emulated cd drive with Alcohol, nothing seems to work. I'm not getting any errors from HFSLIP while it runs... but I'll admit, I'm not sure I'd recognize an error if I saw one. Thank you for your time and this fascinating tool, and I hope you can shed some light on my problem. Any further information you feel may be of use, name it and I will attempt to provide it. I've attached a list of all the files in SOURCE and the ERROR_REPORT.TXT file. ~ Flame12121 lists.zip