An IMPORTANT note on using UHDD/UIDE, which I felt needed to be posted -- "Protected mode" users (JEMM386, EMM386, etc.) who run UHDD or UIDE should load these drivers with their /F switch. For caches of 80-MB to 1023-MB, /F causes UHDD/UIDE to have 64K cache blocks, not 16K blocks. 64K blocks run MUCH faster for protected-mode, since the drivers need to process only 1/4 as many cache blocks on most files. /F helps to "maintain" the speed of UHDD/UIDE on any "protected mode" DOS system!
"Real mode" users (UMBPCI, etc.) are far less affected and may omit /F for higher cache capacity. In "real mode", the UHDD/UIDE "MvData" subroutine has its own FAST logic to handle XMS memory moves (NO slow Int 15h "traps" needed!), and it is not "bothered" by cache-block sizes! 16K cache blocks are 90% efficient in cache capacity, while 64K blocks are only 70% efficient, due to "wasting" more space in the last cache block of a file, which is seldom filled. If /F is given, users can compensate for the lower "net" cache capacity of UHDD/UIDE by setting a bit larger cache, which most current 1-GB to 4-GB PC systems should easily permit! ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Freedos-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-user
