Jump to content

Unable to copy SP4.CAB


Recommended Posts

Posted (edited)

OK, here I am at work, trying to cobble together a slim Win2k with IE6 for compatibility purposes with PC Anywhere. I had something working fine. I am using 1.7.0. I always select Option C. During the blue stage of setup, it says "unable to copy sp4.cab" and I choose continue anyway. Setup proceeds as normal, of course.

I am posting because:

1. I wanted to say "hi, all!"

2. I wanted to see if it's something someone else has had before I go diving into troubleshooting it.

3. I know it's no big deal, trust me. I'm just racking my brain since I didn't really "do" anything that would have triggered this!

I can certainly choose not to combine cabs, and I can probably figure this out... In the ultimate irony, way back I stumbled upon the driver.cab and sp4.cab entries in the INF files and suggested to tommyp that we try having HFSLIP combine them. That was on a Friday; by the following Monday he had it working... so I really ought to know what the problem is.

Just frustrated since I have to set up some PCs and I wanna go home for the weekend! :realmad:

Awesome work as always, Tomcat and Tommyp!

EDIT:

I had a customized IE.IN_ in my FIX folder. For some reason a little voice is telling me to include that.

Edited by fdv

Posted

That copy command must come from somewhere. Do you still have an entry for SP4.CAB in TXTSETUP.SIF or in DOSNET.INF?

Have you tried removing the Read Only attribute for each file after copying them from CD?

Wait... That didn't come out too well...

Have you tried selecting all files in the SOURCE folder, right-clicking somewhere inside the selection, choosing Properties, unchecking the Read-only checkbox, clicking Apply, marking the radio button to "apply the changes to the selected items, subfolders and files", clicking OK, and clicking OK again?

Whatever... You know what I mean... :)

Posted

It was still in TXTSETUP. I had a modified TXTSETUP in FIX. From this I take it that if the FDV fileset is not being used, then HFSLIP modifies files like TXTSETUP first and then copies the FIX files over... and in so doing put my TXTSETUP that still had a SP4 entry in it. This isn't the first time that having certain files in FIX has messed me up... I gotta watch that.

Posted

In Easter Egg mode, TXTSETUP.SIF from SOURCESS\I386 is appended to.

If FDVFILES\IE.IN_ exists, TXTSETUP.SIF from FDVFILES is used as a base.

Otherwise, HFSLIP takes it from SOURCE\I386.

The content of your FIX folder is copied over near the end of the HFSLIP run, regardless of your setup.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...