thanks-loving it: suggestion for hfslip.org v.1.6.4

[michaeljeshurun]

I found one or two quirks in the directions on the howto.html page. For one, I found that to use bbie.exe I needed to go to command prompt and specify the source drive. Probably a little more explanation on the HowTo page would 've helped me. Just typing bbie.exe at a prompt gives clear directions.

Also, when I ran hfslip*.exe, a scruffy incomplete screwy FILE was created, not a folder. I needed to create my SOURCESS folder by hand. I just deleted that weird half-bred file, and everything went fairly smoothly. It never came back. I think the forum said I need to empty the hand-made SOURCESS folder every time I add Updates for slipstream.

Finally, I did need to fish around the forum for an error with the compiler not finding modiFYPE.exe. I shouldn't have needed it according to what I found there, but I put it in, and that error was resolved.

I guessing these three problems might have been fixed in more recent releases.

I'm messing around with multi-boot linux systems, and I tend to screw up my OS setups quite often. The computer I do the experimentation on is XP Home (Gold?) with no service pack whatsoever included. But I do need the computer for watching a broadcast on Media Player daily, and to quality control my occasional web designs on it's oversize monitor. The HFSLIP disk I created with this system and programs have made my life easier. I'm back up and running in an hour, instead of worrying about network security, and repeating Windows Updates for hours everytime.

Many thanks.

Edited November 16, 2007 by michaeljeshurun

[Tomcat76]

Version 1.6.4 was released on October 14, version 1.6.5 on October 25, and version 1.7.0 was released just the other day... No biggie, though...

I found one or two quirks in the directions on the howto.html page. For one, I found that to use bbie.exe I needed to go to command prompt and specify the source drive. Probably a little more explanation on the HowTo page would 've helped me. Just typing bbie.exe at a prompt gives clear directions.

You are supposed to put it in the HFTOOLS folder, so HFSLIP can automatically create the ISO when it's done. That's what Step 6 in the Basic How-to is all about. If you want to do things manually, that's your call...

Also, when I ran hfslip*.exe, a scruffy incomplete screwy FILE was created, not a folder. I needed to create my SOURCESS folder by hand. I just deleted that weird half-bred file, and everything went fairly smoothly. It never came back. I think the forum said I need to empty the hand-made SOURCESS folder every time I add Updates for slipstream.

HFSLIP automatically deletes an existing SOURCESS folder when it's started. I believe the comment you're referring to is that you shouldn't copy the content of the SOURCESS folder into the SOURCE folder next time as HFSLIP is only made to work with a clean source. Do you get the same problem when you start from scratch again?

Finally, I did need to fish around the forum for an error with the compiler not finding modiFYPE.exe. I shouldn't have needed it according to what I found there, but I put it in, and that error was resolved.

If you show me your HFSLIP.LOG file (please ZIP it), I can tell you if you need it or not.

[michaeljeshurun]

I'm feeling silly that I didn't realize bbie.exe in HFTOOLS worked automatically! Some forum answers mentioned after the boot.bin is created you can delete bbie, so that was partly to blame for the confusion.

My first run of HFSLIP didn't create a SOURCESS folder at all. I definately didn't copy anything into it myself. I'll let you know how the next run works starting from scratch like you suggested, and I was going to. I think I got lucky I figured out creating one and leaving it empty worked out.

As to your offer to check my HFSLIP.log, I did the first run with just SP2 and a few downloads from Microsoft, just as a test. I have another two hours of work I need to find to get all the ones I want. I'll definately need modiFYPE in the next run. Can I take a rain-check in case I mess something next time?

TYVM

[Arie]

My first run of HFSLIP didn't create a SOURCESS folder at all.

Indeed and it shouldn't either. The first time you run HFSLIP, it only creates all the default folders which HFSLIP requires. You then copy the files which you would like to add to the appropriate folders, such as your complete source to the SOURCE folder, hotfixes to the HF folder, et cetera. Once you're all done, you run HFSLIP again. HFSLIP then creates your updated source files and places those in the SOURCESS folder. You don't create this folder yourself, HFSLIP does this. Once HFSLIP has built an updated source in your SOURCESS folder, but you decide to add for example more hotfixes to your HF folder and run HFSLIP again, the SOURCESS folder will be deleted and recreated with the new, updated source. If you let HFSLIP create an ISO automatically, you can delete the SOURCESS folder yourself every time as well. Hope this makes things more clear.