Long filenames with spaces in via HFEXPERT\WIN

[Nuhduhvuh]

HFSLIP version: 1.7.7

Win version: 5.1.2600.5512 (SP3, Professional)

When trying to add extra files through HFEXPERT\WIN I noticed the following:

HFSLIP seemed to complete without errors.

Windows setup stopped almost immediately after it had started (even before the F6/F2 queries) with an invalid TXTSETUP.SIF.

The cause is the following in the [sourceDisksFiles] section of TXTSETUP.SIF:

Filename with spaces.ext = 1,,,,,,,1110,0,0

which should be:

"Filename with spaces.ext" = 1,,,,,,,1110,0,0

Strangely enough, this problem does not occur in the corresponding [WinntDirectories] section above it; here the long names with spaces are surrounded by quotes.

The quotes are also missing in the DOSNET.INF entries.

A solution to this problem is to stick with 8.3 filenames and add the destination name to the TXTSETUP-entry.

Apart from this there is a second potential problem one should be aware of when using HFEXPERT\WIN in HFSLIP. The Windows folder Cursors for instance has subfolders for each theme, and in these folders often the same names are used for different files. When one copies the whole Cursors tree over to HFEXPERT\WIN\Cursors and start HFSLIP, HFSLIP will make an entry for each file found with a different destination directory, but the source folder will always be I386. The net result is that there is only one file in I386 (the last one found and copied), although there was more than one file with the same name in the source folders to begin with.

The third last problem with this approach is that files names with spaces in them in the source folder (HFEXPERT\WIN) are NOT copied over to I386 in the SOURCESS folder, although erroneous entries for them are created in TXTSETUP.SIF and DOSNET.INF.

Conclusion: do not use HFEXPERT\WIN as a replacement for $OEM$\$$, unless you are very sure of what you are doing. The advantage would have been that the HFEXPERT\WIN approach had the possibility of being smaller via Makecab, as the $OEM$ files are copied directly to their destination.

HFSLOPLG.zip

Edited August 4, 2008 by Nuhduhvuh

[Geej]

Looking at your HFSLIP.log, seems like you are putting alot of "standalone" program in HFEXPERT\PROGRAMFILES &

HFEXPERT\WIN folder

I have also learnt that HFEXPERT\WIN need to have 8.3 filenames & no spaces for the filename. If you want to have long filename, basically you need to rename them during T13 with a batch file.

I would suggest you try to put these standalone programs in the form of silent 7zsfx or winrar sfx. They can be compressed with long filenames. And put them in HFSVCPACK folder. It will also shorten the overall run time.

Personally I use the HFEXPERT\WIN for additional command-line tools only (So that it is available for use with any CMD files you want to execute during T13 stage. eg. Shortcut.exe , cWnd.exe etc)