Tomcat76

60309c to be exact. I wasn't sure if it was a test release or not so I said 60310...

tacoeater... It's as Super-Magician says... You have to start over again though you can use XPSP2 as the base in the SOURCE folder. It only takes 10 minutes... @TAiN: It's deleted automatically unless you run a special test mode.

If dosnet.inf wasn't an issue then 18f would've worked the same as 18g. I'll base the next tests on 18f then. CPI/CPL... You know... A while ago I changed the code to leave both CPI and CPL files extracted. But then I figured it would be better to compress one of the two again and I picked CPL... for these reasons: 1) There's no point in keeping both uncompressed 2) I believe all MS *.CP_ files are CPL files so it's better to overwrite them instead of creating duplicates (eg whatever.cp_ and whatever.cpl) But apparantly Windows setup is too stupid to see the difference between myuninst.cp_ and myuninst.cpi... I see two options: 1) Extract all *.CP_ files (even those from the source) and leave them like that 2) Try what Tommy suggests with the _x thing in txtsetup.sif (this I can't do in HFAAO)

If the older version came from the HF folder (eg, wmfdist.exe) then it was fixed in 60310. Every build from then on keeps the correct version of msdmo.dll unless it's packaged in a silent installer. (It took me a while to find out because I apparantly forgot to mention it in the changelog) You can try that. It should work. But check in dllcache first.

You're right...

I'm slowly beginning to run out of ideas, hehe. 18g does something (or rather doesn't do something) which I wanted to avoid. But if this fixes the problem with dosnet.inf I don't have a choice...

You are being asked for the second CD if you manually add stuff (or force HFSLIP to add stuff) like "filename.exe = 2,,,,,,,1,0,0" into the txtsetup.sif of a Windows XP source. Most often, the "2" is intended for a Win2K install; the equivalent of that for Windows XP and Windows 2003 is "100" but it's better to use "1" which is compatible with 2K, XP and 2003. Ah, wait... That's most certainly a problem with your custom winnt.sif file...

That *may* have been fixed in 18f. You know... It's strange that you never experienced this problem before, but OK... We're working with Altair Basic here...

Which issues? 18f only adds two lines into txtsetup.sif and two more lines into dosnet.inf so it won't make a difference.

Yeah, those errors are normal. Don't worry about them Donation list? What donation list?

OK... 18f adds the lines into txtsetup.sif and dosnet.inf.

So I basically remove the "diagnostic" part in front of the existing line? You talkin' 'bout hfcleanup?

Here it is anyway: HFSLIP_60318e-expertSP.7z Edit: see 18f

Are you including drivers with the HFDRV method?

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.

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

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

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...

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?

TXTSETUP.SIF + missing CPI?

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...

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

I tried the one from November 29 and wasn't impressed. The hiccups are back, and the picture just freezes from time to time (the latter doesn't happen with the build in the K-Lite Mega codec package). I'll try this ffdshow build (November 3).

I wish they'd provide a little more info. I got an Athlon64 CPU but I'm using Win2K 32-bit and WinXP 32-bit (like the majority of people who own an Athlon64 system). This is what I found:2006-03-16 - mplayer2006.03.16.Athlon-XP.7z 2006-03-16 - mplayer2006.03.16.Athlon-64.7z So what do I use? Is the Athlon64 build intended for all Athlon64 CPUs or only when the user is running a 64-bit OS on it?

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.