So what did I forget...

[fdv]

Even Microsoft says it's probably what's been suggested.

dotnet does not need IE, BTW. I use dotnet fine.

Are you using an OEM CD? you said "retail" but I want to make sure.

Also, be sure to use a Virtual Machine to test in. You can download VM free for 45 days.

Also it sounds like you tested with a slipstreamed 2000 with SP4 but this was from what... your SOURCE folder, right?

Finally try a version using my files but delete SETUPP.INI from the FDVFILES folder. That's the product specification file.

[Aluminum]

The machine I am typing on, right now, was made from a CD, which was burned from the Sourcess folder.

It also worked fine burning nothing but the source folder (w2k + SP4, nothing else, my old i386 really did come from a retail hologram cd ages ago - I dont buy prebuilts) as in worked fine from a CD from start to finish.

(I'm lazy and screw learning yet another partition tool, I use the windows format tool from the long version of the setup - I really do install 100% from a CD)

I will try a VM machine but to me thats just another layer of obfuscation + potential bugs to figure things out, the cds w/o fdv files all worked 100% through the setup (about 10 by now)

Heres the error report for my current setup (in other words, my source works fine for a slipstream of all this stuff, just not FDV files):

=========================DO NOT ALTER THE SECTION BELOW========================

HFSLIP Version -

HFSLIP_60107.CMD

Your path - D:\HFSLIP\

OS you are slipstreaming - 2000

Language you are working with - English

IE6 Version - 2KIE6

FDV Fileset - Not Used.

DX9C - Integrated

==============================================================================

The files in your FIX folder -

hosts

NTDETECT.COM

NTLDR

Names of the files in your HF folder:

IE6.0sp1-KB823353-x86-ENU.exe

IE6.0sp1-KB833989-x86-ENU.exe

IE6.0sp1-KB887797-Windows-2000-XP-x86-ENU.exe

IE6.0sp1-KB905495-Windows2000-x86-ENU.exe

IE6.0sp1-KB905915-Windows-2000-XP-x86-ENU.exe

msxmlcab.exe

oe6.0sp1-KB897715-Windows-2000-XP-x86-ENU.exe

rootsupd.exe

scripten.exe

Windows2000-KB842773-x86-ENU.EXE

Windows2000-KB890046-x86-ENU.EXE

Windows2000-KB891861-v2-x86-ENU.EXE

Windows2000-KB893756-x86-ENU.EXE

Windows2000-KB896358-x86-ENU.EXE

Windows2000-KB896422-x86-ENU.EXE

Windows2000-KB896423-x86-ENU.EXE

Windows2000-KB896424-x86-ENU.EXE

Windows2000-KB899587-x86-ENU.EXE

Windows2000-KB899589-x86-ENU.EXE

Windows2000-KB900725-x86-ENU.EXE

Windows2000-KB901017-x86-ENU.EXE

Windows2000-KB901214-x86-ENU.EXE

Windows2000-KB902400-x86-ENU.EXE

Windows2000-KB904706-DX9-x86-ENU.exe

Windows2000-KB905414-x86-ENU.EXE

Windows2000-KB905749-x86-ENU.EXE

Windows2000-KB908506-x86-ENU.EXE

Windows2000-KB908519-x86-ENU.EXE

Windows2000-KB908523-x86-ENU.EXE

Windows2000-KB912919-x86-ENU.EXE

WindowsInstaller-KB893803-v2-x86.exe

Windows-KB890830-V1.11-ENU.exe

Windows-KB909520-v1.000-x86-ENU.exe

WindowsMedia9-KB885492-x86-ENU.exe

WindowsUpdateAgent20-x86.exe

wmfdist.exe

Names of the files in your HFCABS folder:

Apr2005_d3dx9_25_x86.cab

Aug2005_d3dx9_27_x86.cab

BDANT.cab

BRANDING.CAB

Dec2005_d3dx9_28_x86.cab

dxnt.cab

Feb2005_d3dx9_24_x86.cab

IEW2K_1.CAB

IEW2K_2.CAB

IEW2K_3.CAB

IEW2K_4.CAB

Jun2005_d3dx9_26_x86.cab

LegitCheckControl.cab

MAILNEWS.CAB

Oct2005_xinput_x86.cab

OEEXCEP.CAB

SCRIPTEN.CAB

WAB.CAB

Names of the files in your HFSVPK folder:

dotnetfx.exe

tweakui.exe

Names of the files in your HFSVPK_SW folder:

50comupd.exe

Names of the files in your HFTOOLS folder:

boot.bin

==============================================================================

[Aluminum]

I tried out VMware and removing the SETUPP.INI from FDV files works. Your # is slightly different than mine, whatever that might mean?

Next to make a slipstream with patches and such, but at least now I know the base works great: 12 processes and <35000k commit looks pretty slick

[tommyp]

Glad you're up and running. Keep us posted on how you make out.

[Aluminum]

Working great now, I built a completely up to date iso with everything including dotnet. 5 minutes worth of services.msc and regedit later is one lean, mean, almost invisible machine on the network

Now I'm going to waste a bunch of time making custom reg files to turn even more stuff off automatically during install

[RJARRRPCGP]

I deleted everything in FDV files and it worked flawlessly. #$%@#$% IE

So something about my files doesn't mesh with FDV fileset...would scripten alone do it?

What about dotnetfx, looking at that now I'm wondering if it demands IE or even IE6 I need .net for a few stupid stubborn programs unfortunately.

I see what you did wrong. The following packages:

IE5.01sp4-KB905915-Windows2000sp4-x86-ENU.exe

msxmlcab.exe

rootsupd.exe

scripten.exe

Don't use those packages with the FDV fileset!!

Also ONLY include the following files for DirectX 9.0c:

BDANT.cab

dxnt.cab

Also, unfortunately the Net Framework installer will demand Internet Explorer!! Unless there's a special hack that can be done, Internet Explorer is required!!

Edited February 6, 2006 by RJARRRPCGP

[Tomcat76]

The *d3dx9* files can stay. Those contain the new dlls and they are processed by HFSLIP. You can leave Oct2005_xinput_x86.cab in if you want, but that one IS ignored...

[the_guy]

The IE cumulative update maybe used if using FDV's fileset, but it is user's choice. Some files updated by it are not removed with the fileset.

the_guy

[Aluminum]

I see what you did wrong...

I see you didn't read the whole thread

We finally determined it was the product id (setupp.ini) FDV includes not matching mine.

I've used all those files except scripten, and the other DX files are needed by many newer games.

Dotnet 2.0 installs and is working fine without IE, I use several utilities that require it, and one stupid driver control panel (ATI) that I just uninstalled for a homebrew tweak.

[Tomcat76]

setupp.ini basically determines whether it's an OEM or a retail CD (or "corporate" if applicable). These require different keys.