Egbert Eich <[EMAIL PROTECTED]> wrote: > > driver sets modes by using the video bios. That way it does not have to > > have full programming capabilities for 3rd party components. The XFree > > driver is therefore limited to what the vbios can do while the Windows > > driver is not. > > Anyway, the solution in this case however should be much simpler: > the BIOS knows about the other modes as they get listed. It just > refuses to set them them it doesn't see more than 892 kB of video > memory. The BIOS just needs to be convinced of that. We had two > ways of doing that. One was by setting some BIOS flags, the other > was using a VESA BIOS interface. For whatever reason there is at > least one more way. Now it is the BIOS vendors' term to provide us > with the necessary information.
AFAIK for the BIOS'es that vendors have not updated to the latest from Intel, there is no way to force the BIOS to recognise more than the amount of memory that is set during POST. The Windows drivers simply do not use the BIOS, and hence this flag setting is irrelevant to the function of the Windows drivers. The only solution I am afraid is to get the vendors to update their BIOS and make the updated BIOS available to their customers. Regards, --- Kendall Bennett Chief Executive Officer SciTech Software, Inc. Phone: (530) 894 8400 http://www.scitechsoft.com ~ SciTech SNAP - The future of device driver technology! ~ _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
