Jump to content

Error copying SP2.cab


DmitryKo

Recommended Posts

WINNT32 tells me that SP2.CAB is missing when preparing upgrade from Windows 2000 SP4 using HFSLIPped version of the installation folder. What's more, it's happening with two differnet language versions! Setup goes on as usual right after a restart.

WXP_EN.zip

Link to comment
Share on other sites


If I wanted to make a clean install I would do it, but this time I just needed an upgrade (I have clean-installed WXP Pro X64 on another partition). No, I didn't specify any switches, I just ran Setup.exe right from Windows 2000 and chose Install Windows (it doesn't matter if I burn a CD or run it from the SOURCESS folder, the error is still there) and it starts Winnt32.exe unattended mode - that is precopies setup files to a temporary folder and creates WINNT.SIF which contains my current system setting with a number of "interesting" options.

BTW, it's supposed to be a "quiet" mode but actually Windows Media Players 10 asks me if I want it installed because Windows System Protection is turned off. There was also another dialog box but I don't remember the details..

Edited by DmitryKo
Link to comment
Share on other sites

Sorry, I thought you were doing a 2k cd. Can you re-read the first line of step 3 of this: http://www.vorck.com/hfslip.html. Don't use punctuation marks (rename your folder to hfslipWXPEN). If there is a problem with WMP10, let me know and I'll see what I can do. In the (remote) event I need the windows bloat player 10, I throw the installer into the HF folder. Remember, HFSLIP is geared toward installing via a CD. If you don't run a cd installation, it doesn't work and you will get copy errors and files not found errors.

Link to comment
Share on other sites

Don't use punctuation marks (rename your folder to hfslipWXPEN).

HFSLIP is geared toward installing via a CD. If you don't run a cd installation, it doesn't work and you will get copy errors and files not found errors.

Do you mean text mode setup invoked by booting from the CD?!! I was upgrading Russian localized version of Windows 2000 from the CD (not from text mode setup) but English version of Windows 2000 was upgraded the local folder, and it went just fine except for several non-critical error messages...

Well, the saga contunues. I tried to do yet another "upgrade" for the Windows XP installation I just upgraded from Windows 2000. I removed the punctuation marks from the folder name (not that it made any difference), reran HFSLIP and then burned a CD and started winnt32.exe from it. There were no precopying errors regarding SP2.CAB this time, but instead it told me "amss" (all-lowercase) is not found in "GLOBALROOT\DEVICE\CDROM0\I386" (?!!), even though "AMSS" folder (in all-uppercase) was actually there. Pressing Cancel threw a critical failure and setup was permanently interrupted. Restarting from the CD didn't help either, so I had to manually type the path to my C:\HFSLIPWXPENG\SOURCESS folder, and then the setup went on. I had to type it some two dozen times more during the rest of the setup (mostly for some INF or CAT files), including Detecting Devices and Adding Start Menu phases. There were no messages from Media Player regarding System File Protection (I left it in HFSVPKSW for now), but there was "Unable to access configuration for Personal Web Server" (and I recall the same error appeared when I was upgrading from Windows 2000).

I really hope Microsoft gets this whole setup and slipstreaming act right for the Windows Vista, I'm just tired of 15-year old floppy-based setup routines...

Edited by DmitryKo
Link to comment
Share on other sites

The HFSLIP slipstream is to be used for a clean installation of windows. It will not work properly with running a winnt.exe command. You must use the HFSLIP install CD to boot the machine, delete your windows partition, and install windows on the "raw" partition of the drive. No winnt.exe commands are needed. The windows setup takes care of all of it.

Edited by tommyp
Link to comment
Share on other sites

But I've also made several Windows 2000 install CDs and upgrades were totally flawless (I started the bootable textmode setup to copy the GUI portion this time, not the WINNT32.exe)

Windows XP is currently working fine as well, despite all the installation troubles.

HFSLIP doc says you can use Winnt.exe (step twelve, http://www.vorck.com/hfslip.html):

Windows is fully slipstreamed in SOURCESS.

Now, you can:

• Set everything to read-only and use it as a distribution share (WINNT.EXE)

As I understant, HFSLIP basically follows the hotfix slipstreaming procedure recommended by Microsoft ( KB316037 and KB828930), with the exception that instead of integrating aka slipstreaming hotfix packages using /integrage switch (which BTW can be hacked to work with WXP updates under W2000, as described by KB889719), the packages are are expanded, contents (GDR branch) are copied over to i386 folder , then compressed as necessary and finally custom INF files are created for each hotifx.

If so, I just don't understand why there are copy errors when I'm not adding anything past some XP hotfixes and WMP10... why there were no errors in W2K? Could you please explain this with a little bit more detail?

Edited by DmitryKo
Link to comment
Share on other sites

Is your SP2.cab corrupted? Can you expand it with winrar? As I mentioned before, installing via CD will give no troubles. Perhaps I sould ask FDV to remove that line from the instructions.

What exactly do you mean when you say"

But I've also made several Windows 2000 install CDs and upgrades were totally flawless (I started the bootable textmode setup to copy the GUI portion this time, not the WINNT32.exe)

Windows XP is currently working fine as well, despite all the installation troubles."

Do you mean that you had errors when it installed via a CD? What errors are you seeing when installing by cd? Why so many questions about installing by winnt.exe when the 2nd page of HFSLIP says that it is to be installed by a cd?

Link to comment
Share on other sites

Is your SP2.cab corrupted? Can you expand it with winrar?

No, it's not corrupt in either of my sources (English and Russian), I can open and extract them witn both Explorer (in XP) and WinRAR.

I could have integrated one of the installations under Windows 2000, which is not the right way according to KB889719. But I'm not sure because I could have done it under Windows XP Pro x64 as well.

As I mentioned before, installing via CD will give no troubles.
OK. But what's the technical reasons for this behaviour, if all the necessary setup files are updated according to the procedure defined by Microsoft?
Why so many questions about installing by winnt.exe when the 2nd page of HFSLIP says that it is to be installed by a cd?
Well, it seems like a confusion on my part... maybe phrases like "use CD to install", "install by CD" etc. are not technical enough of a description for me :P - all in all, running setup.exe or winnt32.exe from the CD could be also qualified as "installing via CD", don't you think? ;) (not to mention some "clever" programs that won't even install from a local or network folder unless it's mapped to a drive letter).

Non-GUI precopying phase on NT installers has always been referred to by Microsoft as "text-mode setup", whenever it's invoked by booting to Windows kernel from the CD/floppy or by running winnt.exe from MS-DOS propmt, so maybe there should be an excplicit clarification somewhere in the docs, something like "Do not use winnnt.exe and setup.exe/winnt32.exe! The only supported installation method is CD-bootable (or floppy-bootable) text mode setup".

What exactly do you mean when you say...

Do you mean that you had errors when it installed via a CD? What errors are you seeing when installing by cd?

I guess it doesn't matter anymore, but nevertheless... here's what I did.

1) I've HFSLIPped two Windows 2000 CDs, English and Russian, in order to upgrade two different PCs to the latest hotfixes. I then run the textmode setup by booting from the CD in either cases and performed in-place installation, and there were no errors or warnings. (I could just apply the latest hotfixes I guess, but some of the Windows' components were behaving strange so I thought a "repair" install would help, but it didn't :(

2) Then I've HFSLIPpped two extra Windows XP CDs, also English and Russian, as I wanted to upgrade two more PCs from Winfows 2000 to Windows XP level (some programs wouldn't install on W2K). This time I didn't use bootable textmode setup, I just ran Setup.exe from within the Windows Explorer (one time from the CD and another from the SOURCESS folder). This way, I've got SP2.CAB not found warning, but I was able to Skip it over, and then Windows Media player setup found no System Files Protection and configuration for Personal Web Server was not accessible.

3) Finally, I've tried to upgrade newly-installed English XP one more time, again by running Setup.exe, and I've got stuck at Installing Windows, being told that "GLOBALROOT\DEVICE\CDROM0\I386" contains no "amss". I just had to specify the SOURCESS folder so the install would go on. There were no SP2.cab errors this time, but Windows Media Player and Personal Web Server warnings were still there.

Link to comment
Share on other sites

TommyP

Just a thought: not sure if it is so but could it be possible that if one doesn't use modified SETUPAPI.DLL he will get a missing SP* file error during installation or even corrupted installation? When HFSLIP merges DRIVER.CAB and *.CAB it also alters (or not?) LAYOUT.INF and TXTSETUP.SIF. Does Windows let it without modified DLLs?

Link to comment
Share on other sites

Just a thought: not sure if it is so but could it be possible that if one doesn't use modified SETUPAPI.DLL he will get a missing SP* file error during installation or even corrupted installation? When HFSLIP merges DRIVER.CAB and *.CAB it also alters (or not?) LAYOUT.INF and TXTSETUP.SIF. Does Windows let it without modified DLLs?
I don't use a modified setupapi.dll and never had Win2K SP4 nor WinXP SP2 complain about a missing SPx.cab (WinXP SP1 doesn't complain about SP1.cab either). Edited by Tomcat76
Link to comment
Share on other sites

Layout.inf isn't touched by hfslip. It's a protected file and will cause problems in you want to retain SFC and not use modified setup dlls.

@DmitryKo - When you ran HFSLIP it told you that it's geared for CD installations. Why is this a problem when you were already informed about this?

Oh, there are no published methods for slipstreaming IE6 in a W2K source. HFSLIP started it over a year ago. For technical details of the setup process, microsoft has some info. Check out their site.

Edited by tommyp
Link to comment
Share on other sites

@DmitryKo - When you ran HFSLIP it told you that it's geared for CD installations. Why is this a problem when you were already informed about this?
As I said above, it wasn't clear enough of a warning to me. "Geared for CD installation" is not equal to "geared for CD-bootable text mode installation", a term used by Microsoft's Knowledge Base (I can run setup.exe or winnt32.exe right from the CD and, in general sense, it's still a "CD installation"), and I read it in the HFSLIP doc that one can actually install from a distribution share using winnt32.exe Edited by DmitryKo
Link to comment
Share on other sites

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