> I had contact with Jack Ellis, and he claims that there are NO systems > (that he knows about), where UDMA leaves it in a unusable state. maybe > it won't work(accelerate), but at least it doesn't break the system. > So UDMA could be used as default driver on ANY system. > > are there ANY reports, that a fairly recent version of UDMA(2) leaves > the system in an unusable state? Erwin ?
Nope. I must say I am impressed with the whole line of recent updates. The only problem I experienced and reported was the "FOOLISH disk-select bug" from 1.7 as Jack calls it. All later versions, even the 2.0-early-betas that Jack questioned himself, ran fine on my (multi-HD) systems. Also I could not duplicate Bernd's VMware no-harddisk-bug. Looks like a VMware 5beta issue and not UDMA's. Did not hear anything on UDMA from my end-users yet. Some solid piece of programming. Kudos to Jack! Erwin P.S. Using 2.0 "UDMA2.SYS /L /S" with UMBPCI.SYS 2.63 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
