[tain]

A couple of issues with 17b:

1)
*.cpl/*.cpi seems to still be an issue. My task scheduler control panel entry has an odd name (bad ascii?) and doesn't run (17b w/HFCLEANUP but not HFEXPERT). I have also been having an odd problem with HFEXPERT/WIN/SYSTEM32...I have a 5k .cpi in there that consistently ends up as a 128kb .cpi with the original filename. Not sure how the transformation takes place. I have been fighting that particular issue for several days using different versions (expert and normal) and different configs.

2)
60317b-expert + HFCLEANUP: Good to Go (GTG)
60317b-expert + HFEXPERT:

Quote

"Line 1 of the INF file is invalid"

about 10secs into setup. That run had a really jacked up txtsetup.sif. I will run HFSLIP with HFEXPERT again so that I can post the txtsetup.

This post has been edited by TAiN: 17 March 2006 - 08:57 PM

[tain]

Zip w/errors and funky TXTSETUP.SIF is attached...along with the DOSNET file detailed below:

In reference to my cpi/cpl problem:
I have three files named myuninst.* in HFEXPERT/WIN/SYSTEM32. They are .CPL, .CPI, and .EXE.
In my SOURCESS I get myuninst.CP_ (containing the CPL) and myuninst.EX_....the .CPI doesn't seem to get integrated although it is listed in SOURCESS's DOSNET and the funky TXTSETUP. Not sure if the errors are connected, but my previous post mentioned a 128k version of the .CPI. You guessed it...the proper CPL is 128k so it seems that the proper CPL is getting installed as the right CPL as well as the wrong CPI. The proper 5k CPI isn't in SOURCESS.

Attached File(s)

•  error17be.zip (33.82K)
  Number of downloads: 30

This post has been edited by TAiN: 17 March 2006 - 09:31 PM

[Tomcat76]

There was a path issue in the HFEXPERT section of the test releases. After I got rid of it, things seemed to go fine. I have a "normal" txtsetup.sif and dosnet.inf after letting HFSLIP run till the end.

I'll take a look at the CPI issue now.


Edit...
The missing CPI issue should be fixed. I forgot to separate the wheat from the chaff. I also let CAB files pass though I don't know if that's useful.

This post has been edited by Tomcat76: 17 March 2006 - 10:36 PM

[tain]

Cool, thanks for the quick fixes. I'll get this started tonight and report back in the morning.
I have a big test next week so I will be studying all weekend and taking breaks to work on HFSLIP for fun. Isn't that sick?

[Tomcat76]

It's 6:40am here. How's that for sick?

[Tomcat76]

And another new one. Tommy noticed a problem with HFCLEANUP+hfslipwu.inf. There was also a problem with HFCLEANUP+sysoc.inf.

I believe that's everything...

Nighty night...

[tain]

Tomcat, in his sleepy state, made a slight typo on the first post link...here is the correct link for 60318a:
http://users.telenet.be/tc76/hfslip/60318/...0318a-expert.7z

Testing now!

[tommyp]

Thumbs down on HFSLIP_60318a-expert.CMD with HFCLEANUP. TC, I sent you some details on what parts you can mod and what parts you cant. The part that I explicitly said not to mod was modded.... this made the hfcleanup break.

[tain]

I'm having trouble with 18a as well
Nothing has changed for me...I am having the same two problems that I've been having for the past several days. Not sure what I can do to help diagnose...

[Tomcat76]

TXTSETUP.SIF + missing CPI?

[tain]

Yes.
Post #71 applies to version 18a.
My results haven't changed for the last couple of versions now...

This post has been edited by TAiN: 18 March 2006 - 07:26 AM

[Tomcat76]

I focused on the CPI problem you mentioned in post #72. Do you have the three required myuninst files in SOURCESS\I386 now?

As far as post #71 goes...
What's the name of this "task scheduler control panel entry"?


@TommyP:
I noticed modifype is run on files in WIN\ but not on files in WIN\SYSTEM32. Is that intentional?

[tain]

Tomcat76, on Mar 18 2006, 07:38 AM, said:

I focused on the CPI problem you mentioned in post #72. Do you have the three required myuninst files in SOURCESS\I386 now?

Yes, but the dorked txtsetup prevents me from seeing if they all get installed in the final product properly.

Quote

As far as post #71 goes...
What's the name of this "task scheduler control panel entry"?

Gibberish...it looks like bad ascii codes or something...just a few tall rectangles similar to [] but as one-character, completed boxen.

[Tomcat76]

I meant the original file name. I couldn't find it in your ERROR_REPORT.TXT. I would like to test it to see if I can figure out the problem.

The current version is 60318c-expert. There was an issue with a fix introduced in 60318b-expert.

I don't know how you are testing now, but I'd advise to take a look at txtsetup.sif and hfslipwu.inf before doing a test install. This could save you some time...

[tain]

Tomcat76, on Mar 18 2006, 08:07 AM, said:

I meant the original file name. I couldn't find it in your ERROR_REPORT.TXT. I would like to test it to see if I can figure out the problem.

Isn't task scheduler a standard control panel entry? The only other thing it could be on my end is a bad CPL entry in an addon...I will check that next. Either way, there are no other *.CP* in HFEXPERT.

Just tested again with 18ce. Same TXTSETUP problem as before. I would attach the file and an error report, but there doesn't seem to be any change from the last time I posted them.

EDIT: I see that 18d is posted...will test now.

This post has been edited by TAiN: 18 March 2006 - 08:35 AM

[Tomcat76]

I doubt 18d will fix the txtsetup.sif issue for you. I really wonder what's causing it...

[tain]

You're right; 18d didn't help

I can try selectively removing things from HFEXPERT/WIN if you think that may narrow it down.

This post has been edited by TAiN: 18 March 2006 - 08:50 AM

[Tomcat76]

Do it by folders. Remove the WIN\SYSTEM32 folder. Then remove all subfolders in WIN. Two tests...

[tommyp]

If you're using the full blown hfcleanup, there is no task scheduler at all. My txtsetup doesn't have strange characters. It will work, but it won't be able to do the full cleaning that hfcleanup can do.

[tain]

@Tomcat: I'll start selectively reducing my HFEXPERT and report back.

@tommyp: The odd characters were in the *intalled and running* OS...I can check what the TXTSETUP says but I'll have to generate that config again.

Low disk space != good records

This post has been edited by TAiN: 18 March 2006 - 09:02 AM