DriverPacks.net Forum - [SOLVED] OS No Value Error Win2K with HFSlip

Re: [SOLVED] OS No Value Error Win2K with HFSlip

2009-04-09T20:25:08Z

They were editing part of a file they should not have been I am sure it was unintentional.

Marked Solved...

Thanks again for reporting it... I am sure you will save (or have saved) people time and effort!

Have an Awesome day!

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

Re: [SOLVED] OS No Value Error Win2K with HFSlip

2009-04-09T19:49:24Z

FDV wrote:

[Issue solved]

Thanks... but how?

Re: [SOLVED] OS No Value Error Win2K with HFSlip

2009-04-09T18:47:14Z

[Issue solved]

Re: [SOLVED] OS No Value Error Win2K with HFSlip

2009-04-08T04:05:00Z

Hfslip without fdvfiles works. Using hfslip with fdvfiles fails. hfslip with fdvfiles generates a CD that works well. The issue is almost certainly an incompatibility between hfslip/fdvfiles and driverpacks. Specifically, it is fdvfiles.

Given the dated nature of Windows 2000 and the security holes in the older Internet Explorer and the increasing number of files that the older MediaPlayer can not run, it is not unreasonable to remove this functionality especially since Windows 2000 is much less resource hungry than XP.

Since I have access to the source code of fdvfiles. Playing around with combinations of wks_id and wks_id_vga failed to generate the desired results. FDV has been very helpful in suggestions on figuring out the problem.

If you could provide the filenames and the strings examined, I can correlate the results of hfslip/fdvfiles to see where the discrepancy lies. I suspect that there is a edge case that the algorithm fails to detect. If you are unable to provide access to either the algorithm used or the source code, could you check the results of hfslip with fdvfiles against the Windows 2000 cd to work out the problem?

Once the problem is narrowed down further, I suspect that FDV would be more than willing to make the necessary compatibility changes.

Re: [SOLVED] OS No Value Error Win2K with HFSlip

2009-04-08T03:05:29Z

this problem ONLY occurs when useing HFSlip...

So we know where the problem lies... Awsome!

Thanks for reporting

PS. I am not going to publish in public what the routine is...
I don't want to allow cheating.
If your filesystem is valid it will be detected.
If it is corrupt it will not be used... This is a GOOD thing.

This routine has gone unchanged for three or more years...
HFSlip is corrupting something

perhaps you could narrow it down to a specific hotfix / package and we can work from there??

Re: [SOLVED] OS No Value Error Win2K with HFSlip

2009-04-07T23:49:38Z

Since two people have independently have run into the same problem, it is less likely that human error on either of our parts is the cause.

I too have successfully applied hfslip and the driverpacks to windows XP.
I have failed to use the driverpacks in conjunction with fdvfiles.

Similarly, when standalone drivers are generated, the process is successful but applying the results to an installation of Windows 2000 with fdvfiles generates an error about not finding sndrec32.

FDV added the following three lines as an attempted compatibility fix without success:
; this is for compatibility with driverpacks
wks_id = "Microsoft Windows 2000 Professional"
wks_id_vga = "Microsoft Windows 2000 Professional [VGA mode]"

FDV suggests using MajorVersion under [SetupData] to determine the OS version. Since I do not have access to the source DriverPack source code, I can not hope to determine how the DriverPacks determine the OS version.

Since I have access to the source code of the fdvfiles. Playing around with combinations of wks_id and wks_id_vga failed to generate the desired results.

Can you provide some idea of the algorithm used by driverpacks to determine the OS version? If you could provide me the filenames and the strings examined, I can correlate the results of hfslip/fdvfiles to see where the discrepancy lies. I suspect that there is a edge case that the algorithm fails to detect.

In summary, the issue is likely an interaction between FDVfiles and DriverPacks but the exact nature of the incompatibility has yet to be found.

Re: [SOLVED] OS No Value Error Win2K with HFSlip

2009-04-07T14:32:22Z

Thanks for the replies. I see now that Yee posted about the same problem here: http://forum.driverpacks.net/viewtopic.php?id=3634 he never recieved a reply. I know its has something do do with fdv's streamlining process and not with DP Base. I will continue and if I find a workaround I'll post it here. Thanks again. Great program.

Re: [SOLVED] OS No Value Error Win2K with HFSlip

2009-04-07T06:22:26Z

no there is not a simple fix...
the detection program (code/module) was written by signet.
the code is quite involved and multi-tiered.
it checks different files based on OS an SP levels ect...
It is likely that it is unable to determint the SP level becuase the slipstream was in some way corrupted.
the detection algorithim Siginet wrote is rock solid...
if your OS is reported as "why does this not have a value"
My guess would be you have a corrupt copy of the OS -
Start over with a clean copy and try again... this time dont corrupt it.

Re: [SOLVED] OS No Value Error Win2K with HFSlip

2009-04-07T02:12:23Z

Not sure. I'm not very knowlegable as far as the alphabet soup or programing. I know enough to get into trouble. I am more of an automated type. I followed this http://www.vorck.com/windows/2ksp5.html through the beginners section. Removed IE. fdv talks about the problem here http://www.msfn.org/board/index.php?showtopic=131008 however I dont think that is the problem because that "string" is in my txtxetup. DP Base did see my source and a nlited Xp, In fact my XP worked fine.

Re: [SOLVED] OS No Value Error Win2K with HFSlip

2009-04-07T00:35:29Z

Did you take WMI/WSH/VBS capabilities away when you trimmed your OS install?

[SOLVED] OS No Value Error Win2K with HFSlip

2009-04-06T22:24:34Z

I'll apologize up front if this is in the wrong place. Have searched and can't seem to find the right answer. Working on W2K slipstreamed and trimmed with HFSlip using dvp's fileset. DP's base reports "OS - Why does this not have a value" I guess the question is: what "string' is your program looking for to verify the OS. Is there a simple fix I can apply. I like Hf Slip and your driver packs but I cannot seem to get them to work together. If there is a simple fix a sticky on the subject may be good. Thanks in advance.