We're slowly heading for a new release. I don't intend to add any more to it in this round, so... let us know if something broke. Comments on the new HFEXPERT\PROGRAMFILES feature would be nice too...

I'll test these test release asap, I was busy.

I had to use hfslip this morning to make an XP SP2 CD. My first iso was bad because I used a CD with SP2 sent by Microsoft and the name of the pack was "XPSP2.EXE".
I then renamed it but I think it would be better if HFSlip recognized this too.

Thanks.

I'm going to agree.

Maybe modify the code for XPSP2 to

just an idea. It might be sending it to the wrong part though.

the_guy

The XPSP2 installer can be named xpsp2*.exe from now on if MS ships it like that. The old *835935* from the MS Download Center still works, of course.

Woooooow ....... alot of changes and new features. So, i´ll have to spend some time in the next future to see and to learn.
One Question i have before i start. Theres the need for me to copy one file during syssetup or during first logon in to %windir%. Please, how is the best way to do that??? Could hfslip help???
Thx for your answer.

wela - please refer to the HFEXPERT page for fine details. Short answer, create a folder structure alongside your hfslip cmd file: HFEXPERT\WIN. Place your file in that folder.

@tommyp. THX for the short answer. It helped.

Made a first test install with german Xpsp2 and the new feature Progfiles.
Works great.
Very good work guys!!!

Made a final install with new features. My son is happy, WU is happy, i am happy.

This post has been edited by wela: Jul 30 2006, 01:10 PM

test release has been kinda quiet recently ... ... looks like all's fine

When you the least expect it...


I'm waiting for TommyP's results. Then we can release a new one.

What was wrong with fetching the boot image?

I forgot to report back. I had no issues with that last file you sent me. Sorry dudes.

It didn't work for me -- neither in HFSLIP, nor in another program I'm currently working on. I actually never noticed this because I don't use HFSLIP to make an ISO. When I noticed the problem in that other program, I tested it in HFSLIP and it didn't work there either.

I see. I wonder why no one reported that problem. Maybe not many people actually use the feature?

Or they did it once a couple of months ago. There's no need to create it again if you already have it.

ey ... kinda got lost there ... i'll second what Super-Magician didn't notice this all along ... i always create an ISO via HFSLIP to test it with other ISO created by another app ... maybe because i don't touch anymore my HFTOOLS folder which has it there (actually there's a .bin & .img there ... probably because i used to have mkisofs & cdimage both in the folder) ...

ah ... just the same ... i was right ... a new final!

This post has been edited by Kiki Burgh: Aug 4 2006, 08:34 AM

No wonder you never noticed... You already have a boot.bin file.
Move boot.bin out of the HFTOOLS folder and then use an older version of HFSLIP. It won't make a new boot.bin.

hi TC!
i actually exprimented on boot.bin & boot.img over the weekend ... with these files (and/or) in HFTOOLS folder ... no ISO was created ... no wonder the cmd file finished faster ... but when i took those 2 out with bbie & mkisofs still in HFTOOLS & leaving the original source CD in the drive, boot.bin was recreated & ISO was created as well ...

as for the presence of the boot.bin there, i have never removed since i 1st used HFSLIP ... i got curious because of the posts i read prior to taking my days-off from work

oh btw, this was using 60803 ... i'll ask related questions in the appropriate thread: ISO creation fails with 60803

This post has been edited by Kiki Burgh: Aug 7 2006, 07:20 AM

*silent bump*

Suggestion for 917008: Remove the MUI files and just treat the rest like a normal hotfix. Is this possible, or not?

the_guy

I like that better.

Done.