1 Reply by yee

(10 replies, posted in Feedback and Support - DriverPacks Base)

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.

Go to forum: Feedback and Support - DriverPacks Base

2 Reply by yee

(10 replies, posted in Feedback and Support - DriverPacks Base)

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.

Go to forum: Feedback and Support - DriverPacks Base

3 Topic by yee

(0 replies, posted in Other)

How does base 8.12.4 detect the windows version?

I am trying to use hfslip with the fdvfileset.  I am slipstreaming Windows 2000 with the hotfixes suggested by the_guy.

Base is complaining that OS:WHY-DOESNT-THIS-HAVE-A-VALUE.

fdv attempted to make a compatibility change which I suspect doesn't work. [I thought it worked when I first
tried it but I can't get it to work now.]

fdv has suggested that the driverpacks determine the windows version using Majorversion udner [SetupData].

I would like to try to understand why.  What is the difference between the virgin sources and the slipstreamed sources (after hfslip and fdvfiles) that the OS version can not be detected?  Would it be possible to allow a manual over-ride?

Thanks.

Go to forum: Other