[teotwawki]

First I'll be up-front and say I was probably trying to run before walking, as I'm trying to build a HFSLIP CD of not just a Win 2000 but all 3. We have an original Win2000 MSDN CD which contains a boot loader that prompts for your choice of Professional, Server or Advanced Server. The CD contains sub-folders with installation sources for all 3. Files which are common to all 3 are hard-linked so the whole original CD is quite a bit less than 650MB.

For each of the 3, I separately copied the I386 structure off the CD onto disc, ran the HFSLIP on it and then moved the patched I386 to a new folder structure. I then copied the other contents of the original MSDN CD into the new structure and re-linked all files which have the same name, size & checksum. I took the BOOT.BIN from the MSDN CD and burnt the ISO using the same mkisofs flags I found in the HFSLIP_60129.CMD file. No extra flags were needed to preserve the hard links.

The resulting CD boots ok and offers the menu of the 3 versions. Upon selecting one (same problem on all 3) the normal Win 2000 installation proceeds until just after starting the GUI phase of setup. Then I get an error dialogue whose text is saved in SETUPERR.LOG

I read through the web site again and the other documentation. The WU.TXT is taken from the host machine I used, not the intended target. The other log files are from the target. I've also included TREE.TXT which shows the folder structure on the CD. Note that when prompted in HFSLIP I told it the I386 was in "ENGLISH/WIN2000/PRO/" for example.

Could anyone take a look at the attached logs and see if I've done anything wrong ?
Many thanks.

Attached File(s)

•  HFS_ERR.ZIP (6.18K)
  Number of downloads: 59

[Super-Magician]

Although I can't really help you with your setup errors (I'm not very good with multiboot CDs), I do want to let you know that some of the DX9 cabs you placed in HFCABS are ignored by HFSLIP. Please consult Tomcat's list of Win2000 updates to see which files you need.

Also, try using the latest version of HFSLIP, 60208.

-- Super-Magician

This post has been edited by Super-Magician: 14 February 2006 - 08:59 AM

[tommyp]

teotwawki - please post back after testing with the current version. Very few of us do the multiboot cd's.

[EmRoD]

Hello

can someone help me, I want to slipstream Microsoft Update (muweb.dll)
i've found a "hack" just copy the dll to the system32 folder and regsvr32 it but i wanted toi know if it can be slipstreamed with hfsilp.

i use my cd made with hfslip it at work (oem pre install) but this muweb thing makes me crazy...

[tommyp]

If that file is an "extra" meaning that there no muweb.dll (or muweb.dl_) in your source\i386 folder, then you can place it in a folder that you need to create alongside your hfslipxxxx.cmd file: HFEXPERT\CODECS. Any files you place here are copied to the system32 folder and registered. Please refer to the HFSLIP info site about codecs (step number 15). You need to download some tools for your HFTOOLS folder when you do this (modifpe). All this info is on FDV's instructional site.

If that file is part of the source\i386, then rename your muweb.dll to muweb.dl_ and place it into the fix folder.

This post has been edited by tommyp: 15 February 2006 - 11:45 AM

[Super-Magician]

Quote

If that file is an "extra" meaning that there no muweb.dll (or muweb.dl_) in your source\i386 folder

Quote

If that file is not part of the source\i386

Don't those two say the same thing?

Quote

rename your muweb.dll to muweb.dl_

Here, I thought you would need to compress it (MAKECAB) first.

This post has been edited by Super-Magician: 15 February 2006 - 07:40 AM

[tommyp]

Sorry I posted some incorrect info. I updated & corrected my post. Thanks super magician.

[Super-Magician]

Where am I supposed to find modifype.exe?

Edit: Never mind, found it on the 2000 page.

This post has been edited by Super-Magician: 15 February 2006 - 08:03 PM

[tommyp]

Update to script... some minor bugfixes as listed in first post. Thanks Tomcat76 for your continued help!

[teotwawki]

tommyp, on Feb 14 2006, 10:34 PM, said:

teotwawki - please post back after testing with the current version. Very few of us do the multiboot cd's.

Just tried with the 60220 version and got the same problem.
I think I'll try a run through with a plain W2K CD to make sure I'm doing everything right.
Will post back soon.

[tommyp]

Can you try testing without a multiboot cd? Are you sure you have your multiboot bootloaders and other modified files on your cd set up correctly? Have you tested a virgin source to verify it's an HFSLIP issue or perhaps you are doing something incorrectly?

[EmRoD]

thanks for the advice, but i just saw on the latest version MU is supported.

gonna try this right now

thanks

[teotwawki]

teotwawki, on Feb 28 2006, 10:27 AM, said:

Just tried with the 60220 version and got the same problem.
I think I'll try a run through with a plain W2K CD to make sure I'm doing everything right.
Will post back soon.

Yea, the plain W2K server CD I just HFSLIP-ed works fine so the problems I'm haveing with the 3-way Pro/Server/Advanced must be more to do with the multi-boot than HFSLIP or anything I'm doing.

I'm curious about the bit in HFSLIP when it asks for the path to the booting version. Is there a bit of detail on that published somewhere ?

Meanwhile I'll try to make a single-boot disc from the 3-way original, keeping it's paths.

[tain]

Thanks for adding the changelog to the first post; quite handy.

Suggestion/Request: add the contents of HFAAO to ERROR_REPORT.txt.
- Sub-suggestion: add contents of FDVFILES to ERROR_REPORT.txt...not sure how useful that would be, though.

DX7 vs. DX9 is still giving me problems. I now revert to DX7 when I use addons even without CODECS (or codec addons). Still trying to get the problem accurately diagnosed...

[tommyp]

Tain, I'm not 100% sure about this, but it's worth a shot. If you are current machine is a FDV installation, you need to re-enable your 16 bit subsystem. See his site for details.

[tain]

Thanks for the idea, but I don't think that is the issue. I built/installed my workstation OS in SEP05 and the patch is supposed to be for OCT-FEB. Just to be sure, I checked the patch INF and saw that its main function is to add a bunch of registry keys. My registry already has those keys so I believe that I'm OK.

Unless you think I should run the patch anyway?

This post has been edited by TAiN: 05 March 2006 - 01:04 PM

[fdv]

TAiN, no need to add that patch. your system pre-dates that odd 16 bit subsystem error, so that probably isn't the culprit. not sure about this.

[tain]

@FDV: Thanks, and welcome back!

I just ran HFLSIP with a lot of variables eliminated and DX9 came out alright...I am adding things back in hopes of discovering the culprit...it seems to be one of the addon packs that I am using but it will take some time to figure out which one(s).

This post has been edited by TAiN: 05 March 2006 - 01:34 PM

[tain]

OK, I think I've got this annoying problem nailed down. Whenever the install process has to stop and ask the user (me) to locate a file that is missing, I consistently get a dorked-up DX9c installation that dxdiag.exe reports as DX7. The point in the process that I am referring to is the "Registers components" phase, I believe. That is where setup/hfslip installs addon packs and registers HFEXPERT/CODECS.

If there is an INF in CODECS or one of the addons that doesn't point to the right file, there is a train wreck behind the scenes and DX9 is derailed. It doesn't seem to matter which addon/codec/file is missing; if the installer has to stop and ask then DX9 won't report be reported by dxdiag properly.

I wonder what else might be going wrong along with DX9...

This post has been edited by TAiN: 05 March 2006 - 02:18 PM

[Tomcat76]

The fix that's included in version 60304 and up only kicks in when DX9 and codecs are involved. It doesn't take into account possible issues between DX9 and addon packs. I'll see if I can remedy this by tomorrow...