[Fudeba]

I'm a king of newbie question!

Well... in the actual compilation i have moved files from $OEM$ folder to equivalent folder in a HFEXPERT.

My folders in HFEXPERT is:

APPREPLACEMENT: This contain patched version of explorer.exe to show icons in notification area with 256 colors (dr. hoiby patch)

WIN: Contain a some files to placed in a winnt dir and subfolders. This a content of my HFEXPERT\WIN:

 hfexpert_win.rar (2.31K)
Number of downloads: 5

After run HFSLIP and no aparently errors, get this error on install:



Live translation to english:

"Line 10946 of the information archive is not valid. It is not possible to continue the installation. It press any key to exit."

I removed temporaly HFEXPERT folder and problem disaper. I tried with HFSlip 1.5.0 and beta release (70627a) and problem persist.

My HFSlip LOG:

 HFSLIP.rar (3.93K)
Number of downloads: 2

[Tomcat76]

A bit obvious. You have file names with special characters.

But I see you are also using file names which already exist in the source. Also, HFSLIP copies all files together into the I386 folder; this means that if you want cmdialog.vbx in both system32 and system32\dllcache it will not work.

You should definitely delete these files (and don't use them in $OEM$ either):
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\dllcache\drmclien.dll
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\dllcache\gdiplus.dll
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\dllcache\wmasf.dll
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\dllcache\wmidx.dll
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\dllcache\wmvcore.dll

The following can remain in HFEXPERT:
D:\Win2K\HFSlip\HFEXPERT\WIN\deltree.exe
D:\Win2K\HFSlip\HFEXPERT\WIN\lista.txt
D:\Win2K\HFSlip\HFEXPERT\WIN\Notepad2.exe
D:\Win2K\HFSlip\HFEXPERT\WIN\Notepad2.ini
D:\Win2K\HFSlip\HFEXPERT\WIN\Notepad2.txt
D:\Win2K\HFSlip\HFEXPERT\WIN\procexp.chm
D:\Win2K\HFSlip\HFEXPERT\WIN\procexp.exe
D:\Win2K\HFSlip\HFEXPERT\WIN\System\winaspi.dll
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\cmdialog.vbx
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\cmdow.exe
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\directx.cpl
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msconfig.chm
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msconfig.cpi
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msconfig.cpl
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msconfig.exe
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msinet.ocx
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msvcp71.dll
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\msvcr71.dll
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\regedit.cpi
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\regedit.cpl
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\themes.cpl
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\vbrun300.dll
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\wnaspi32.dll
D:\Win2K\HFSlip\HFEXPERT\WIN\System32\drivers\aspi32.sys

For everything else I advise you keep using $OEM$. There are several more files which you can embed through FIX but they will have to be renamed so they match the name of existing files in the source and be compressed. This is beyond my time and has nothing to do with HFSLIP.