danod

Walked away from this for a while then started from scratch. Not a hitch this time through. Nor a clue as to what was wrong before. I want to thank you guys for your help and for a great job on HFSLIP

Well, I've run with the serice pack in HFSPACK and having been removed altogether ( except for having been expanded into the original source). No variation seems to have affected the result - reboots after registration into Windows splash screen and then ... windows is restarting set up. I'll start this process from scratch. I must have poisoned it somehow. This time I'll let HFSLIP do the service pack in the first place.

Tomcat67, Done. Wasn't sure that was aimed at me and got confused by the fact there's already a folder, HFSVPK - compounded by the fact I see neither referred to in the page (http://www.vorck.com/hfslip.html ) that kicked me off on HFSLIP. But HFSLIP is running on it now with the service pack pulled from HF and placed in newly created directory, HFSPACK. Thanks, --danod Edit: duh! I'd already extracted the service pack into the I386 directory. So it was redundant in the HF directory - and then in the HFSPACK directory. I suspect the latter is merely redundant - as in no side effects. But if it doesn't fly this time, I'll yank it altogether. Thanks!

Tomcat67, Tommyp: Use of the command prompt was revealing. The HSLIP directory exists during installation with all the .INF files in it. It persists through much of "Registering Components" and then is cleared - which seems reasonable. Progress is made through "Finalizing - saving settings" seems to about complete that and reboots. Coming back from reboot, it restarts setup back to "Preparing Installation" and runs through the "Personalize Your Software", collects product key, machine name and so on. But ... HFSLIP is long gone. Don't think the reboot is error - says it's going to do it. But it's as though it leaves a sticky set up flag or bread crumb. This is all on a VM, by the way. And I'm wondering if that's a factor. Thanks, --danod Edit: Another point of confusion: I tried building an ISO with the Sources content using Nero(7). If I build a data CD ROM ISO, I get no boot record. If I build a bootable CD ROM ISO I get a CODE 4 (whatever that means). I've tried using the same boot.bin I provided to HFSLIP and another I've successfully slipstreamed XP SP2 with some time ago with no good result in any case.

Sheesh - I glanced away at email and, with about ten minutes to go - rebooted into setup running again into installing windows with 39 minutes to go ... again. The files from the latest HFSLIP run are at: http://www.yaod.com/HFSLIP/ Into 12th hour of mucking with this but for a trip to the store and lunch. So ... tomorrow. Thanks, --danod Edit: Had to watch one more time. Forty percent into "Registering Components" with 13 minutes left - same problem; cannot find C:\WINNT\HFSLIP\HFSLP200.INF ..., etc. No Eureka, after all.

Tomcat67, you nailed it. Installation not yet completed but into registering components and well beyond the "files not found" and reboot scenarios of prior attempts. Thanks again. --danod

Ok, Tomcat67, if you're interested, the ERROR_REPORT.TXT and TXTSETUP.SIF from the run of HFSLIP sans dotNet. As you expected, the: install.res.xxxx.dll = 1,,,,,,,2,0,0 are gone. About to stick in a VM and see if I got a sane platform for SQL Server. Thanks, mon. HFSLIP and this forum rock!

Absolutely. Removing dotnet and re-running HFSLIP re-run underway with: dotnetfx_18f7bece34e729581e6b5b7b9afae1b.exe removed Got it: dotnet unsupported by HFSLIP Thanks so much Tomcat67. I'll expect a clean install! or I'll be back. --danod

Tomcat76-- Am running 2nd shot of HFSLIP but ERROR_REPORT.TXT still looks like first run. It's at the typo (story of my life) spot. Thanks, --danod

Hey Tomcat76, thought I'd posted TXTSETUP.SIF in a reply. Perhaps it's too large to put on forum? Anyway, it's here: http://www.yaod.com/HFSLIP/TSTSETUP.SIF Thanks, danod b.t.w., since you're interested in it, I infer I should be. And the HFSLPXXX.INF entries are curious. This is typical: HFSLP200.INF = 1,,,,,,,999,0,0 - and I suspect 999 is meaningful. Trying to discern from HFSLIP_60310.CMD.

I have a similar problem and, possibly, more info that may help. The unfound files in my install are: C:\WINNT\HFSLIP\HFSLPnnn.INF Note the spelling delta of the file name - makes one suspect a typo. But is it the original poster, my self somewhere along the way or HFSLIP_60310.CMD? For what it's worth, the files do exist, as HFSLPXXX.INF, in the HFSLIP\SOURCES\I386 after running HFSLIP_60310.CMD. As I'm running HFSLIP_60310.CMD again and it stops to display file and folder formats, I see that INF files to be processed at T13 should be in HFSVPK - which is empty. Checking step 5 at http://www.vorck.com/hfslip.html, that's 'optional' and I put nothing in HFSVPK. To try to experiment my way around the reboot cycles, I'm putting the unfound INF files in HFSVPK ... to see what happens. danod