That's right. HFSLIP registers the Windows Update files (among other things) AFTER the SYSOC addons are installed. If something goes wrong with an addon, things are likely to go bad with subsequent addons, WU, and registration of other files.

I noticed you made quite a few cosmetic changes in the latest test release (60428a), especially to the titles .

Can you possibly implement the following changes, too?

1. Call up CMDOW (if it exists) to hide the extra command prompt window when extracting MP10Setup.exe, scripten.exe, wmfdist95.exe, etc.

2. When HFSLIP extracts the extra DX9 updates, the title bar still says "Processing MSXML," which it does before running through the D3DX9 files.

-- Super-Magician

Thanks for adding in the changes, Tomcat . You rule!

If you have the time, please see if you can do anything with this:

dziubek requested earlier this month (see his posts in this topic from Apr 15 and Apr 22) to have added to HFSLIP.LOG the time it takes for HFSLIP to run. I know that this is not possible with DOS, but it is possible to record the time HFSLIP starts running and the time HFSLIP finishes slipstreaming/repacking/etc. I think this is a great idea.

Maybe you could make the following changes to the script.


(Of course, if you decide to introduce them, you may improve/modify these changes)


Edit: Added more possible changes

Do we need the second variable? Why not this:
..and obviously I second the nomination to add this feature

There's still a variable too much...

I'll see what I can do...

TAiN - You are absolutely right about that second variable . Thanks.

Be careful what you ask for 'cause you just might get it...

Hint: It's *NOT* displayed in HFSLIP.LOG....

I will maybe make an integrator by myself (with AHK).
I just installed MilkE bricopack. Hopefully it uses ResHacker and hopefully it does not delete the log file.


I think the installer proceeds like this:
1- the installer you downloaded extracts some files to Packs\ThemeName and runs Setup.exe
2- you select the files you want to be modified, setup.exe finds them, copy them Packs\ThemeName\PackFiles
3- *.res files are generated from Rs??.txt files in Packs\ThemeName\ResFiles (those Rs??.txt files have an half-inf structure)
4- reshacker is called with the parameters shown in the log
5- files are replaced


Bad surprise : my shell32.dll is now 35MB.
My comp seems slower now, especially when opening apps. I should reboot twice and check but I don't think it will change anything.
Some icons are 128x128, sometimes they seem to be duplicated inside shell32.dll. weird.
(I exported one 128x128 icon, it was 66KB. )

edit: rs ??.txt files look like :

There are half-inf, half not.
Also, I just understood something else : in the pack, all icons are 128x128 32bits. They are then resized but I have absolutely no idea on when it is done.
I think I will make an AHK app that will be named "reshacker.exe", that would accept the same parameters as genuine reshacker.exe and that would then call it with slightly different parameters (of course, it will have expanded installation files)
If you have a better idea....

Tomcat: Thanks for implementing the run time indicator! So it is possible with DOS? Great job on the coding there !!

Now, I hope I'm not asking for too much, but how about dziubek's other suggestion on the difference in size between SOURCE and SOURCESS?


Oh, and personally, I liked the old format for the hotfix extraction section (at least 60428a-60429a). Because HFSLIP showed the names of the files that were being copied, the script *appeared* to move faster. IMHO, the current test release (60429d) has too little information in that section .

Actually, it isn't possible the way I imagined it back when dziubek asked for it. All HFSLIP does now is record the start time, record the end time, then calculate the difference. Pretty "basic", hehe...

I'll try to figure out the most sensible way to do this. But the main thing is that all other changes implemented in the recent test releases should work fine as I'd like to release a new final. After that, I may give x64 a shot and maybe even .NET 2.0.

Personally, I don't care which way it is represented. What do other people think?

!! Unfortunately, the run time indicator has a bug !!




Suggestion once you figure out the bug: have HFSLIP record the time when it actually starts running, not immediately after you start the script (the time will depend on how long it takes you to go through the initial screens and type the "I have read...").

I saw that once but it should've been fixed.

I did some changes. See if you still get the error...

I managed to integrate SnowE bricopack into XP.
Ok, in fact, the files still have to be cabbed.

Two files did not get updated : uxtheme.dll and shellstyle.dll.
I'm sure it is because they are updated with a patcher written inside the bricopack installer (whereas other files are updated with reshacker.exe). I don't care about uxtheme.dll but I wonder what role shellstyle.dll plays.
(seems it is not so important, only useful with some themes)

The method I used is not the easiest since you have to put my files, deny Write permissions to everybody (NTFS rights), install your bricopack. The bricopack will complain about reshacker.exe not being writeable which is normal.
If I don't deny Write to everybody, the installer will overwrite my reshacker.exe with the normal one.

:sotired:

If it's this complicated I don't even feel like trying it. The best would be if the author provided advanced switches for silent installation just like for XPize...

I totally agree with you.
Now, the work has been done, but it's too complicated. I mean bricopack creators could do it in a few seconds or minutes whereas it took me hours (with less coding errors it would have been faster. ).

Moreover it's not easy to make it unattended and I doubt batch scripting will appreciate.
Anyway, it will maybe make the things evolve : I know lots of people think customizing an XP CD is incredibly harsh, I'm prooving bricopack integration can be done quite quickly.
Now I just hope the installers will give more control soon.


btw, the /S switch can be used; advanced customization.

Is this VBS or something?

I found it. It looks like DOS freaks out with some (not all) numbers that have a leading zero. It's worked around in 60430c.

OK. Haven't had time to test, but will report back by tomorrow, if not sooner.

Pure AHK : http://www.autohotkey.com
AHK and AutoItv2 are like two peas in a pod (my english teacher would be proud of me for this expression ). But AHK is opensource-licensed whereas AutoIt is closesource.
Annoying with variables but powerful with windows (resizing, sending keystrokes, mousemoves...), key remapping (remap a to q needs only : "a::q"), inireading/writing, regreading/writing and string manipulation.

I use ahk2exe to get an executable (btw, ahk2exe's logo is that of AutoIt)

Tomcat: Is there anything in the script that is processed before :GETBOOTBIN but is needed to parse :GETBOOTBIN properly?

You modified the :GETBOOTBIN section of the script after Kramy suggested something to get rid of the error message that pops up. For some reason, I think the message still pops up. I haven't observed this, however, because I have boot.bin in HFTOOLS, and therefore the script skips that section when I run it. Nevertheless, when I copied that section into a separate batch file and ran it, the error message popped up.

I will run HFSLIP without boot.bin and see if I get the message.

Edit: Actually, I think I may have a special case. I have a drive, D:, that is a ZIP drive and normally does not have anything in it. If I run the test script (that has only :GETBOOTBIN) and leave echo on, the error pops up after it processes drive D.

(The following has nothing to do with the above problem)

On a side note, I think you should insert the following line into :GETBOOTBIN so that HFSLIP does not try to run BBIE if no disc is detected.

Time bug fixed! Thanks, Tomcat

I did not see the error box saying "There is no disc in the drive," but that's because I didn't have bbie.exe in HFTOOLS so the script didn't process that section. (See my previous post if you don't know what I'm talking about.)

If I run the following script, that error box pops up (note: this is an exact copy of the :GETBOOTBIN section with a few things at the top).

I added the GOTO EOF to the GETBOOTBIN section in 60501a. Thanks.

As far as the other problem is concerned... This can't be fixed. It's the same as when you double-click on a CDROM/ZIP/USB drive icon when there's nothing loaded in it.

That's what I figured after I thought about it for a while. Thanks.

It sounds logical... HFSLIP needs to check for the existence of an I386 folder before it determines that it's a drive containing the Windows CD. For that, the drive needs to be accessed...

But - the modification provided by Kramy - wasn't that to get rid of such error message?

Hey, I was just thinking - I don't see any ( ) brackets in the above function. What happens if multiple drives have an i386 in their root? Will it only attempt to copy from the last one?

Yes, that's true. I don't think there's an easy way to fix that.

Tomcat - minor prob with writing the run time into HFSLIP.LOG. Obviously it won't get written into the ISO as that's created before the time is generated. Just a head's up .

It at least gets rid of an error message appearing when a drive letter doesn't exist.

As far as I know... yes.

i made a lot of tests but unfortunately i couldn't find out which addons causes the problem.


Could You write me a meaning of that warning: Rock Ridge




dziubek

I don't know what Rock Ridge is. Someone else should be able to answer that. What worries me more is the renaming of General_Settings.reg. What are the switches in your ISOconf.txt file?

I see nothing wrong in TXTSETUP.SIF and SYSOC.INF, but if you're using switches that change files to 8:3 format you might get in trouble with UserPass2.inf. Also, note that HFSLIP adds file names into SVCPACK.INF representing the files in the HFSVCPACK and HFSVCPACK_SW folders the way they are called in there. If General_Settings.reg is renamed to GENER000.REG it won't be installed/executed.

Can you delete ISOconf.txt and test again?

I deleted Kels_UserPass2_addon_v1.CAB and ISOconf.txt and I will test it again

hi all!

been away for quite a while ... ;(

just wanted to share that all seems fine with those that i have slipstreamed ...

only a few things to share though:

888111 doesn't seem to recognized when ITs presence is validated via qfecheck ... it does not show in the report

a particular theme addon (VistaCGI if i recall it right) from rynavm prevent the OS from installing ... it shows that line 1 of textsetup.sif is not valid ...

there seems to many directories (usually the very 1st folders) added to my i386 directory (i.e., 041, 043, & the like) ... where did these come from?

btw, XPIZESW=/S /notask still didn't work for me. XPize installation still showed up at T-13 & i still followed the prompts.
may i just ask what the SW is for?

thanks!

@dziubek - What you are seeing is some LFN in your svcpack directory. It either got there from your HFSVCPACK directory or a non-compliant ryanvm addon. If you are running installation via CD, there is NO NEED to worry about this error message. The only way you will get errors is if you are running a dos prompt install (e.g. winnt.exe).

@kiki - Do you get the same folder problem if you are not using application add-ons?

Kiki - the SW in XPIZESW just means "switches", like in CDIMGSW and MKISSW (isoconf.txt).

It doesn't matter for Windows - it's for UNIX purposes only.
excerpt from Wikipedia

Is qfecheck capable of detecting it? As far as I know, it is only installed if Windows setup thinks it's necessary. It's just a driver update. Are you having audio problems?

Really strange. SVCPACK.INF doesn't contain the switches even though they are specified in XPize.txt. Can I have a look at your xpize.txt file?

Tomcat, would you mind keeping this post/thread up to date? You do a really great job of breaking this stuff down to my level

@Kiki: Themes_rytukz_VistaCG_addon_v1.0.cab (and other addons of that type) should be supported with 60503a...

@TAiN: You mean that one reference to the HFSVPK folder? Updated.

Hah... Well... Should I let HFSLIP extract the ISO, update HFSLIP.LOG and remake the ISO?

@dziubek

You have a couple of addons with spaces in their name. Are those the original names or did you change (or make) them yourself?

I have not added much add-ons except for the ff: VistaCG Theme [v0.98], Microsoft MakeCab v1.00.0601, XnView Complete v1.82.4, Reboot Into Safe Mode v1.0 ... please see the pic attachment for the extra folders



thanks for the clarification Super-Magician … I was just thinking that replacing it probably with .exe would make it work



pls see attachments sir … I’ve included both the SVCPAK & SYSOC.infs … please know I am not having problems w/ the installation … it’s just that I hope I wouldn’t have to answer follow the prompts anymore at T-13



got the latest already … let me try this ver J
just the same pls see the pic attachment for the error

thanks guys!

this is nothing much ... but may be worth a look ...
"Founding"

@Kiki

60503b fixes the XPize problem. I also added something that alerts you which hotfix adds those extra folders. Please let me know which one it is.

When you install KB888111 by hand, Windows assumes that you need it. I'll search around to see if it's really better to have Windows force-install it from SVCPACK.

Everything should be fine with VistaCG (only checked version 1.0). I'll check the other addons you mentioned.

Yeah... That's why CounterStrike isn't made for DOS...

@Kiki

I had a look at the other addons you mentioned (except Microsoft MakeCab v1.00.0601 which doesn't seem to be available anymore) and don't see a problem. Please use the latest test release (60503c at the moment). If you still get an error referring to "line 1" of TXTSETUP.SIF, I'll have to take a look at your TXTSETUP.SIF file.

@all
Thanks for explanation about The Rock Ridge...


@Tomcat76
I used only addons from RYAN's forum.
I will tidy up addons (upgrade too) from HFAAO and HFSVCPACK and I write raport about that today.

dziubek

thanks TC!
as always, i have downloaded the latest!

sir, do you mind looking into this: http://users.atw.hu/mp-soft/CabSDKAddons_1.0.cab?

i've taken the liberty of attaching a zipped sif files (1 without the error & 1 with the error) for your reference

just wondering, for XPize to be silently install would i not need an edited modified SFC_OS.DLL which i got from http://www3.sympatico.ca/lazimute/xpcr_en/SFC_OS.DL_?

thanks again!

HFSLIP doesn't handle it?

You get the "bad" TXTSETUP.SIF after including VistaCG? If so, please download the latest version of the VistaCG addon (it's now at version 1.0 but you're still using 0.98) and run HFSLIP again. After that, see if TXTSETUP.SIF still is 3.13KB large.

I don't know this personally (I never used XPize) but other people say it's needed.

i think HFSLIP does sir ... since Microsoft MakeCab v1.00.0601 isn't avail anymore, would http://users.atw.hu/mp-soft/CabSDKAddons_1.0.cab more or less have the same function?


already got the 1.1 ver ... will try it


oops sorry for the confusion ... i meant would there be anything else that needs to be edited in this already modified SFC_OS.DL_?

BTW, how do i get to edit some text files (.dl_, .sif, etc.) when they appear to be with non-eng, non alpha-numeric chars? ;o

thanks again!

I don't know... I never used another version than the one that comes with Windows...

Whoops... I better check if it's still compatible then...

I don't think so. Windows should just not check if a file is original so I guess the SFC_OS.DLL file you have is good.

I never messed with SFC* files myself. Does anyone know this?

Kiki, Typically if a file has a _ at the end, it's a compressed file. The only files that you really look at with a text editor are inf's and sif's. As far as replacing system protected files and other files, you're best bet would be to familiarize yourself with this. If you are only slipstreaming the hotfixes listed on Tomcat76's hotfix webpage, you do not need to alter any files (like sfc_os.dl_). However, if you want to add in the tweaks such as xpize or certain AAO's, then you are more than likely going to need a modified sfc_os.dl_. FYI, xpize modifed a boatload of dlls.

@Kiki

Version 60505a no longer checks for duplicate entries in TXTSETUP.SIF. There's no real need for doing that and it may have been responsible for your TXTSETUP.SIF problem. Please try this release and tell me two things before you install it:

- the file size of TXTSETUP.SIF in SOURCESS\I386
- the name of the hotfix that adds the "04" folders to SOURCESS\I386