Hi,
Eric Auer escribió:
Hi Aitor,
Eric Auer escribió:
PS: If MS DOS allows you to access a drive which is bigger than
the reachable range of your BIOS then MS DOS has a bug. It should
ONLY allow you to access drive letters (partitions) on your harddisk
which are ENTIRELY inside the reachable-by-BIOS range (usually at
least 504 MB even for old BIOSes).
Why? If it behaves nicely with data stored beyond BIOS range then it
seems it's doing well...
I once (ages ago when I was using MS DOS) lost a FAT because
the access did just wrap around from the last to the first
cylinder. So access beyond the officially available range
must ONLY be activated if the user KNOWS that the BIOS has a
bug in REPORTING the size but supports ACCESSING data even
beyond the supported size...
My point is: There ARE BIOSes which actually support access to
1024 cylinders or to 2^28 LBA sectors or even 2^32 LBA sectors
but which have a BUG which prevents them from reporting that.
For SUCH BIOSes it would be very nice to have a SYS CONFIG option
which allows bypassing of the limits!
Understood, sounds sensible to me too! If no-one has time for this at
the moment (unfortunately I don't, even if I would like to), perhaps it
could be annotated as a wish in Bugzilla.
There might be a problem if a driver to be accessed at boot-up lives
beyond int24h and is loaded BEFORE UDMA2.
I have rarely accessed UDMA2, can it be loaded as a device driver? In
such case it could be adviced to load it first, with HIMEM and EMM386,
in the order that is best for the three of them.
Aitor
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
