[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

[tommyp]

If you saw strange characters in control panel, then it is because hfcleanup (current fileset only from Mar 11th or so) isn't being parsed correctly. The old hfcleanup fileset left little to be desired. Delete any reduction files that Oleg2 made and use the ones posted on FDV's site.

[tain]

I'll tackle that after I am done stomping HFEXPERT/WIN.

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

[tain]

Well that was fun

I started with this structure:

-HFEXPERT (just subfolders)
--APPREPLACEMENT (empty)
--WIN (just subfolders)
---CURSORS (just cursors)
---FONTS (just fonts)
---SYSTEM32 (misc stuff)

And then took these steps:
1) Deleted S32 and a similarly dorked TXTSETUP as before.
2) Left S32 out and also deleted CURSORS...similar TXTSETUP as before.
3) Left S32 & CURSORS out and also deleted FONTS...similar TXTSETUP as before.

So for #3, I just had this:

-HFEXPERT (just subfolders)
--APPREPLACEMENT (empty)
--WIN (empty)

And I *STILL* got a dorked TXTSETUP. So then I deleted HFEXPERT *entirely*, even though it just had empty folders, and HFSLIP 18d ran like a charm.

WTFO?

I am pretty sure that I have run this before with just an empty HFEXPERT/APPREPLACEMENT and not had issues, but I will test that now. It looks like the mere presence of an empty HFEXPERT/WIN causes HFSLIP to vomit on screen.

This post has been edited by TAiN: 18 March 2006 - 10:16 AM

[tommyp]

Dumb question, but are you sure that you don't have spaces in in any of the foldernames?

[tain]

There is no such thing as a dumb question with me
I am positive that there are no folders with spaces anywhere in HFEXPERT.

I do have the pleasure of reporting that 18d has fixed the oddly-named control panel entry. Whatever that was, it is gone now. 18d w/o HFEXPERT installed like a dream.

Running HFSLIP with empty HFEXPERT/APPREPLACEMENT now...

This post has been edited by TAiN: 18 March 2006 - 10:38 AM

[tain]

Problem confirmed.

HFSLIP18d=OK
HFSLIP18d+HFEXPERT/APPREPLACEMENT(empty)=OK
HFSLIP18d+HFEXPERT/WIN(empty)=dorked TXTSETUP

So on an otherwise OK config, just adding the HFEXPERT/WIN folder causes TXTSETUP to be completely borked. Error Report/TXTSETUP attached.

Attached File(s)

•  txtsetup.zip (1.48K)
  Number of downloads: 29

This post has been edited by TAiN: 18 March 2006 - 11:13 AM

[Tomcat76]

That's a nice find. If you still get a borked up txtsetup.sif with 18e, I'll do something special.

I'm hungry now so I'll be back in 30 or something.

[Tomcat76]

Here it is anyway: HFSLIP_60318e-expertSP.7z

Edit: see 18f

This post has been edited by Tomcat76: 18 March 2006 - 12:49 PM

[tommyp]

Bad txtsetup. Echo a [SourceDisksFiles] into txtsetup.sif in the first line of the hfcleanup. DOSNET needs lots of love too.

[Tomcat76]

tommyp, on Mar 18 2006, 07:26 PM, said:

Bad txtsetup. Echo a [SourceDisksFiles] into txtsetup.sif in the first line of the hfcleanup.

So I basically remove the "diagnostic" part in front of the existing line?

tommyp, on Mar 18 2006, 07:26 PM, said:

DOSNET needs lots of love too.

You talkin' 'bout hfcleanup?