pcb@gator.usl.edu (Peter C. Bahrs) (01/06/90)
ash@mlacus.oz (Ash Nallawalla) writes: >> >> I obtained my copy of HIMEM.SYS version 2.06 and some supporting doc files >> through a now-defunct local BBS about six months ago. It is timestamped >> 7 Feb 89. I upgraded mycopy of Windows/386 after I received that copy but it >> contained an older HIMEM.SYS. A couple of months ago Windows was still >> shipping with an older HIMEM.SYS. Could someone please explain >> -- >> ============================================================================= >> Ash Nallawalla Tel: +61 3 823-1959 Fax: +61 3 820-1434 >> ZL4LM/VK3CIT Postal: P.O. Box 539, Werribee VIC 3030, Australia. >> >> I am not going to explain what to do with HIMEM.SYS but I will comment on a similar frustrating situation. First, I have numerous applications that run under windows 386, and hence, numerous drivers supported with each. For example, I have 4 different HP Plotter 7475 drivers. One of them never works with the application we developed. Why in the heck are there 3 drivers (win386's is the oldest) and which one do I use, the newest? Second, I have MS 5.0 and the new QuickC (version 2.?). Which libs do I use with windows SDK? Should I erase all of the MS 5.0 libs and just use QC libs? I think this is a general problem in the software industry, especially when a mfr. creates a product such as windows, or and OS and other vendors create programs that 'run' in this environment. I think that some sort of standard distribution of software supplements (driver, fonts, ...) should be initiated regardless of the cost. I am tired of hearing... "...well we can only guarantee that it will work on our version..." /*------------Thanks in advance...---------------------------------------+ | Peter C. Bahrs pcb@gator.cacs.usl.edu | | USL-NASA Project | | The Center For Advanced Computer Studies | | University of Southwestern Louisiana | | Lafayette, LA 70504 | +-----------------------------------------------------------------------*/