problems with HFSLIP 1.70

[Saibaschbeis]

Hi,

just tried to use the newest HFSLIP 1.70, but got errors.

First of all it tried to expand the sysoc.inf file from my source but cpould not (expand returns "error extracting..." blabla).

I worked around this by extracting sysoc.inf manually using 7zip and preventing HFSLIP from deleting the WORK directory, so I can put the sysoc.inf file there in advance.

But in the HFSLIP CMD there is the following command:

FINDSTR/L "[Version]" work\i386\sysoc.inf

This command always fails, although there is a section called [Version] present in the file! I even checked for blanks in the same line, but there are none...

Additionally I get an error on the new GETLANG section.

This one:

FOR /F %%I IN ('DIR/B SOURCE\I386\FP*0EXT.IN*') DO (
		COPY SOURCE\I386\%%~nI.INF WORK >NUL 2>&1||EXPAND SOURCE\I386\%%~nI.IN_ -R WORK >NUL
		TYPE WORK\%%~nI.INF>WORK\GETLCIDD.TXT
	)
	FOR /F "TOKENS=3 DELIMS= " %%I IN ('FINDSTR/BI "FrontPageLangID" WORK\GETLCIDD.TXT') DO SET LCIDD=%%~I

always returns "the system cannot find the file specified"

cheers,

Saiba

[Tomcat76]

First of all it tried to expand the sysoc.inf file from my source but cpould not (expand returns "error extracting..." blabla).

I worked around this by extracting sysoc.inf manually using 7zip and preventing HFSLIP from deleting the WORK directory, so I can put the sysoc.inf file there in advance.

If you had to do this manually then there's either something wrong with the file in your source, or your host system does not support extracting of Windows-compressed files from the command line (though I wouldn't know how to break that myself).

But in the HFSLIP CMD there is the following command:

FINDSTR/L "[Version]" work\i386\sysoc.inf

This command always fails, although there is a section called [Version] present in the file! I even checked for blanks in the same line, but there are none...

That command only checks whether your sysoc.inf is in Unicode or not. If it's Unicode (as is the case for non-English systems), a silent error occurs which is intercepted by the "IF ERRORLEVEL 1" command and then sysoc.inf is treated differently. If the error is not silent for you, there must be something strange with your system configuration.

Additionally I get an error on the new GETLANG section.

This one:

FOR /F %%I IN ('DIR/B SOURCE\I386\FP*0EXT.IN*') DO (
		COPY SOURCE\I386\%%~nI.INF WORK >NUL 2>&1||EXPAND SOURCE\I386\%%~nI.IN_ -R WORK >NUL
		TYPE WORK\%%~nI.INF>WORK\GETLCIDD.TXT
	)
	FOR /F "TOKENS=3 DELIMS= " %%I IN ('FINDSTR/BI "FrontPageLangID" WORK\GETLCIDD.TXT') DO SET LCIDD=%%~I

always returns "the system cannot find the file specified"

I'll have HFSLIP check if that file exists before handling it in the next version, but I won't make it a quick-fix release because that file is there by default on all sources. HFSLIP is made to work with original/clean sources only.

It would help if you ZIPped your HFSLIP.LOG file and attached it here...

[Saibaschbeis]

Hi Tomcat,

regarding my sources: maybe there is something wrong. They are slipstreamed with SP2 already, but not by myself...

I will get clean XP SP2 sources from work from a original MS CD today and we'll see if this helps.

regarding GETLANG section:

the file is present in my sources! I have a file called FP40EXT.IN_ in my sources. But nonetheless HFSLIP causes the file-not-found error.

As I deleted everything yesterday to start from scratch again, I will attach any logfile in future if I get the same errors again.

Thanks for now

cheers

Saiba

[Tomcat76]

Now I'm beginning to wonder... Do you actually have the original Microsoft EXPAND.EXE in your system32 folder? If it is not the original MS version, or if you have another version of EXPAND.EXE in a different folder for which a system path is configured, extraction by HFSLIP will fail if it uses different switches. Make sure that the first system path which contains EXPAND.EXE contains the original EXPAND.EXE from Microsoft, or place it in the main HFSLIP working folder.

[Saibaschbeis]

hi again,

I think I found the problem:

I had an EXPAND.EXE with a date of 2002 in my SYSTEM32 folder. I got the new sources I was talking of and replaced the EXPAND.EXE from these new sources.

Now everything seems to work fine.

cheers,

Saiba