hfslip and driverpacks

[yee]

I have used hfslip 1.7.8, the latest fdvfiles as well as the windows 2000 patch list from the_guy to generate a working updated CD.

I then attempted to use the driverpacks base 8.12.4 to add all the additional latest drivers. This does not work. I think it the step, Select location of platform. I point to the SOURCESS directory and get the error message:

OS: WHY-DOESNT-THIS-HAVE-A-VALUE

When I point to the original SOURCE directory, I have no error message

OS: Windows 2000 Professional - SP4

What am I missing

[tommyp]

I don't know the workings of the driverpack program, but I guess I can try as good as anyone. I'd suggest to try eliminating FDV's fileset, rerun hfslip and then run the driverpack program on the sourcess folder.

[bfc_xxx]

I don't know the workings of the driverpack program, but I guess I can try as good as anyone. I'd suggest to try eliminating FDV's fileset, rerun hfslip and then run the driverpack program on the sourcess folder.

I use hfslip on clean source, and then driverpack without problem on xp. But you have to keep this order: 1st hfslip then driverpack.

[fdv]

Yeah, Tommy's got the answer -- my fileset is the culprit.

I made a compatability change so try it now after RE downloading my fileset

sorry about that

Edited March 12, 2009 by fdv

[yee]

Thanks for the quick responses.

I did confirm that HFSLIP works without the FDV fileset.

I will try to download the new fileset to see if it helps.

Once again, thanks for the help

[yee]

Thanks. The new fdv fileset seems to have done the trick.

[yee]

Very strange.

I thought the new fdvfiles did the trick. It may very well have.

I worked on other things but when I went back, the same errors occurred. What exactly was changed in the new fdvfile set so that I can try to figure out what happened?

Thanks.

[fdv]

look under 'strings' you will see:

; this is for compatibility with driverpacks

wks_id = "Microsoft Windows 2000 Professional"

wks_id_vga = "Microsoft Windows 2000 Professional [VGA mode]"

these strings are what the pack searches for to find OS and version etc, and why it gave "OS: WHY-DOESNT-THIS-HAVE-A-VALUE"

[pawolf496]

Thanks to all for HFSlip and to fdv on his w2k project. I also am having this issue with driverpacks. I posted on DP Base forum here: http://forum.driverpacks.net/viewtopic.php?pid=30653#p30653, still no resolve if found will post.

Great work to all love HFSlip.

[fdv]

He doesn't want to reveal how the OS detection routine works to prevent "cheating" ??!? What on God's green Earth is he talking about?!

[semilong rant deleted by me]

He doesn't want to tell anyone, fine. That's his right on his board. Here on MSFN, i can give away his secret recipe. The answer's not in TXTSETUP, it's in that and LAYOUT as well.

Important: if you post and tell him -how- I fixed the issue, he might create an incompatibility on purpose, so let's keep mum on this on -his- board. He doesn't need to know what we know here.

Edited April 11, 2009 by fdv

[yee]

Preliminary results of testing. I have not yet had the chance to attempt slipstream. It is too late tonight.

Running on SOURCE, driverpack reports :

OS: Windows 2000 Professional - SP4

Running on SOURCESS, driverpack reports :

OS: Windows 2000 Server - SP4.

The results were derived from replacing the 20 files in the new set from the 41 files in the original set.

Running on SOURCESS, driver pack reports :

OS: Windows 2000 Server - SP4.

The results wre derived from using ONLY the 20 files in the new set.

In summary, the new FDV fileset changes the OS version.

When I have the chance, I will see if the anomaly matters in the slightest although there is some software out there that will not load on Windows 2000 Server but will on Windows 2000 Profesional.

[fdv]

The OS version change only happens for the DriverPacks.

The OS will under all other circumstances show up correctly as Workstation (i.e. "Professional").

It's his detection routine that I tricked, nothing else.

He writes: PS It would be considered polite to tell us (Anyone who trips over this thread) if there will be (or is) an update to the offending patch. Or a thread / post where the "fix" can be found if the update is not yet posted...

The problem is, if I explain on his board the details I'll be revealing how his OS detection routine works which is something he probably doesn't want me to reveal.

Edited April 11, 2009 by fdv

[yee]

I attempted to use the sp5files-srv.zip to generate a ISO.

SOURCESS is recognized by driverpacks as posted above.

The ISO assumes that i386 is from w2k server. Likely, the identification files on the root is incorrect. When booted, I am asked for the W2K Server CD in drive A:

[fdv]

Which makes sense, because sp5files-srv.zip is for Win2k Server.

I linked to the wrong set. SORRY!!

Anyway, I finally tried and it works now in Set 9. Sorry for all the trouble guys.

Download set 9 at http://vorck.com/data/sp5files-set9.zip

Edited April 11, 2009 by fdv