[Super-Magician]

Sure, I will get on that and get back to you tomorrow (my time).

Edit: Actually, I will report back in half an hour .

This post has been edited by Super-Magician: 27 April 2006 - 06:55 PM

[Super-Magician]

It works without that line!

[Tomcat76]

Thanks. There's a new version again...

[Kiki Burgh]

thanks Tomcat for the inclusion of KB888111!
have already downloaded the new ver ...

you really are so proactive in putting in all those changes ...
rest assured, we all will do our parts & contribute to HFSLIP's evolution

allow me to go back to the ff:

Tomcat76, on Apr 26 2006, 11:45 AM, said:

This is a new file that comes with one or more of the hotfixes you add on top. Can you tell me where that file ends up on the system? Is it the SYSTEM32 directory?

nothing ends up in the i386 dir nor in the system32 dir ... i even tried searching the entire source for it ...

Tomcat76, on Apr 26 2006, 12:12 PM, said:

I searched around a bit and KB897338 contains this file. HFSLIP needs to be updated for it. Is this a hotfix you're including?

yes sir, it is a hotfix from this link: http://support.micro...om/?kbid=897338

Tomcat76, on Apr 27 2006, 07:16 AM, said:

Kiki Burgh, on Apr 26 2006, 03:24 AM, said:

also, XPize does not silently install despite the xpize.txt in HFTOOLS dir ...

If SVCPACK.INF in SOURCESS\I386 contains at least "XPIZE.EXE /S", then it can only mean two things:
- there's a general problem with the XPize executable (which version are you using?)
- XPize cannot be installed at T-13

pls find the attached SVCPACK.INF handy (& SYSOC in case needed)
thanks again!

BTW, have already downloaded the most recent hfslip … just now ...

Attached File(s)

•  infs.7z (2.02K)
  Number of downloads: 24

This post has been edited by Kiki Burgh: 27 April 2006 - 08:15 PM

[Tomcat76]

Kiki Burgh, on Apr 28 2006, 04:11 AM, said:

yes sir, it is a hotfix from this link: http://support.micro...om/?kbid=897338

Then I guessed right. Support for it was added yesterday...

[Tomcat76]

It looks like the switches aren't recognized (they aren't there in SVCPACK.INF). Can you copy & paste the following into HFTOOLS\XPIZE.TXT?

XPIZESW=/S /notask

It works for me...

[Kiki Burgh]

thanks for the confirmation sir ...

will do ...
although, i tried different approaches in the xpize.txt in HFTOOLS dir ...

xpize.exe /S /notask

& one with

XPIZESW=/S /notask

yet prompts still come up ... well, not that it is difficult to follow the prompts ... though it would have been much better if no prompt anymore would present itself

This post has been edited by Kiki Burgh: 27 April 2006 - 09:42 PM

[dziubek]

1) All is Ok If I don't use folder HFAAO .
WU is satisfied, all Hotfixes doesn't miss

2) However I have again problem from WU (ActiveX control) when I use folder HFAAO
dziubek

Attached File(s)

•  HFSLIP.zip (3.67K)
  Number of downloads: 24

[Tomcat76]

@dziubek...

I need the TXTSETUP.SIF and SYSOC.INF from the "bad" install. If everything is fine in those files, the only solution is that you try to find out which addon is causing the issue because the only thing HFSLIP can do is obey what's defined in the addons configuration file (just like nLite). If the problem addon is localized I can maybe try to find a workaround (just like for the one for CDImage).

This post has been edited by Tomcat76: 28 April 2006 - 10:04 AM

[Axed]

dziubek - Have you tried running these addon packs thru a different program such as nLite or the RyanVM slipstreamer to see if its the update packs?

A way you could test them is to extract all the cabs into a single directory, remove the .ini files, then extract all the .in_ files. You will then have *namehere*.inf files. To test the addons, right click each addon .inf and select Install. If it does not work (doesnt do anything) just delete the pack because it wasnt tested, or the creater is lazy which means its liable to have errors. This isnt for system update packs like WMP10 or RyanVM Update Pack only application addon packs. Otherwise, they should all install properly and you'll know pretty fast which ones are worth keeping because they work and which ones arent.

Do this on a virtual machine. These addonpacks can cause havoc on your computer. And ill say it again, these addonpacks can cause problems when installing XP unless they are perfectly working.

Mind you, im not against all application addon packs. The "nLite Application Add-Ons" tend to be quite good because they dont modify the sysoc which is what causes incomplete system installs when the sysoc errors from a bad inf. At least if theres an error in the "nLite Application Add-Ons" packs, the system install keeps going properly...

This post has been edited by Axed: 28 April 2006 - 05:42 PM

[Tomcat76]

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.

[Super-Magician]

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

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

Quote

SET /P THACATS=
IF /I "%THACATS%"=="Y" SET DELCATS=1
CLS
:START
SET %START%=%DATE% %TIME%
CALL :FOLDERPREP
IF EXIST HFEXPERT IF NOT EXIST HFTOOLS\MODIFYPE.EXE ECHO YOU DO NOT HAVE MODIFYPE.EXE&PAUSE&EXIT

Quote

IF DEFINED HFCLN ECHO>>HFSLIP.LOG HFCLEANUP Detected&ECHO/>>HFSLIP.LOG
IF EXIST SOURCE\I386\nlite.in_ ECHO>>HFSLIP.LOG nLited Source Detected&ECHO/>>HFSLIP.LOG
IF DEFINED HFSLIPSVPACK ECHO>>HFSLIP.LOG Service Pack Slipstreamed By HFSLIP&ECHO/>>HFSLIP.LOG
ECHO Time HFSLIP started - %START%>>HFSLIP.LOG
SET %END%=%DATE% %TIME%
ECHO Time HFSLIP finished - %END%>>HFSLIP.LOG
ECHO/>>HFSLIP.LOG
ECHO>>HFSLIP.LOG ===============================================================================
ECHO>>HFSLIP.LOG Files in your FIX folder:&DIR/B/A-D/OGN/ON FIX>>HFSLIP.LOG&ECHO/>>HFSLIP.LOG

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


Edit: Added more possible changes

This post has been edited by Super-Magician: 29 April 2006 - 09:39 AM

[tain]

Do we need the second variable? Why not this:

Quote

IF /I "%THACATS%"=="Y" SET DELCATS=1
CLS
:START
SET %START%=%DATE% %TIME%
CALL :FOLDERPREP

Quote

IF DEFINED HFSLIPSVPACK ECHO>>HFSLIP.LOG Service Pack Slipstreamed By HFSLIP&ECHO/>>HFSLIP.LOG
ECHO Time HFSLIP started - %START%>>HFSLIP.LOG
ECHO Time HFSLIP finished - %DATE% %TIME%>>HFSLIP.LOG
ECHO/>>HFSLIP.LOG
ECHO>>HFSLIP.LOG ===============================================================================
ECHO>>HFSLIP.LOG Files in your FIX folder:&DIR/B/A-D/OGN/ON FIX>>HFSLIP.LOG&ECHO/>>HFSLIP.LOG

..and obviously I second the nomination to add this feature

[Tomcat76]

There's still a variable too much...

I'll see what I can do...

[Super-Magician]

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

[Tomcat76]

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

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

This post has been edited by Tomcat76: 29 April 2006 - 04:09 PM

[Camarade_Tux]

Camarade_Tux, on Apr 26 2006, 02:56 PM, said:

But then I would have problems keeping my CD up-to-date.
Moreover, it would takes ages to find which files are needed.
Anyway, I've asked if it could be added.

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.

Quote

[30 avr. 2006, 12:39:13]"D:\XPMG.9\SYSTEM32\Packs\SnowE\ResHack\ResHacker.exe" -modify "D:\XPMG.9\SYSTEM32\Packs\SnowE\PackFiles\29_shell32.dll", "D:\XPMG.9\SYSTEM32\Packs\SnowE\PackFiles\29_shell32.dll.new", "D:\XPMG.9\SYSTEM32\Packs\SnowE\ResFiles\Dialog.res", Dialog, 1089,
Modified: DIALOG,1089,1036

Commands completed

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 :

Quote

[FILENAMES]Exe = "TempFiles\fontext.dll"
SaveAs = "PackFiles\fontext.dll"
Log = "PackFiles\fontext.dll.log"

[COMMANDS]
-addoverwrite "ResFiles\63.ico", ICONGROUP, 1,
-addoverwrite "ResFiles\64.ico", ICONGROUP, 2,
-addoverwrite "ResFiles\65.ico", ICONGROUP, 3,
-addoverwrite "ResFiles\66.ico", ICONGROUP, 4,
-addoverwrite "ResFiles\67.ico", ICONGROUP, 5,
-addoverwrite "ResFiles\68.ico", ICONGROUP, 6,
-addoverwrite "ResFiles\69.ico", ICONGROUP, 7,
-addoverwrite "ResFiles\70.bmp", BITMAP, 15,

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

This post has been edited by Camarade_Tux: 30 April 2006 - 05:35 AM

[Super-Magician]

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 .

This post has been edited by Super-Magician: 30 April 2006 - 08:18 AM

[Tomcat76]

Super-Magician, on Apr 30 2006, 02:11 PM, said:

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

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

Super-Magician, on Apr 30 2006, 02:11 PM, said:

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?

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.

Super-Magician, on Apr 30 2006, 02:11 PM, said:

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 .

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