Thank you Bernd for steering this good effort by Tom away from semantics and back on track.
@Tom I will send you any info on non-working hardware I get from my NwDsk end-users. Since I provide an escape-option in config.sys to choose when experiencing errors like this, the response might be low due to end-users successfully using this workaround. @Bernd On VMware 4.5.2 without harddisks defined I do not duplicate your problem. I get a proper message by UDMA2 (/L /S) that there are no harddisks so it got nothing to do and won't load. Erwin > > Hi! > > Where? > > in a previous message. Tom wants to collect results about UDMA2.SYS > compatibility. It's a driver to set IDE devices (not ATAPI, only IDE) > from PIO into UDMA mode. > Result will be usefull for his own software (partition imaging product), > but also for FreeDOS community. > > > te> one VERY important thing: what information to provide. > > > > For what? > > Testing report about compatibility between UDMA2.SYS and the physical > system that the user tests this driver on. > > > > "UDMA" - as some driver? From which URL I may get this driver? > > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/udma/devel/udma2_20.zip > (93KB) > > > te> AMD/Intel CPU > > te> approximate age > > > > Age of who/what? Mine? Shiping date of case, CPU, mboard? Date of their > > manufacturing? Date of "releasing" press-release? > > age of complete computersystem I think. Incompatibility with new system > should indicate that you ask your BIOS manufacturer for a new BIOS which > fixes things. Incompatibility with an ancient computer shows that > UDMA2.SYS driver might need more workarounds. > > > te> and - of course - GOOD, BAD, HARMLESS > > > > May you explain, what you poll? > > poll about how compatible UDMA2.SYS driver is with the system. > GOOD : loads correctly > BAD : crashes system or makes it unstable > HARMLESS: aborts safely on error > > My example: using UDMA2.SYS in VMware emulator, with no harddisk in that > emulated environment, causes "Bus-Master setup BAD; driver NOT loaded!" > message, instead of "No disks to use; driver NOT loaded!" > > That's an emulation error, probably. > I've also noted that UDMA2 might help with the VDS feature of EMM386 > driver, but I probably should check that again. > > Bernd Erwin Veermans [EMAIL PROTECTED] Department of Social Psychiatry, University of Groningen P.O. Box 30001, 9700 RB Groningen, The Netherlands Fax: +31 50 3619722, Tel: +31 50 3612079 ------------------------------------------------------- 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
