lth@uoregon.uoregon.edu (Lars Thomas Hansen) (06/25/89)
>I thoroughly love DESQview and often wonder how people can be really >productive without. IMHO, anybody wishing to speak the word "productivity" should *first* read Ed Yourdon's "Productivity: A personal choice" (Computer Language May '89, the "eof" column), *then* do some serious thinking, and *finally* (maybe) say what needs to be said. Just a gentle reminder that a word like "productivity" should be used with some care. It is not A&O. --lars ---------------------------------------------------------------------------- On a blank disk you can seek forever
davidr@hplsla.HP.COM (David M. Reed) (06/29/89)
# My choice for a DOS multitasker requires a 386 machine and is known # as VM/386. My preference is based primarily in that each virtual # machine is constructed with its own individualized config.sys and # autoexec.bat files, contrary to the WINDOWS-386 and DesqView. If you have a 386 system, then you can really benefit from the new version of DESQview-386 with its highly acclaimed QEMM. I just received a copy of this last week, and did not realize that it had a program (called LOADHI) that will allow you to load device drivers and TSR programs in Extended memory, thus saving most of base memory for application needs. # (Also, I'm not overly sold on multiple windows (yet) and find that # multiple screens (each application/machine has its own full-sized # "window") is adequate for most my needs.) I actually prefer to run applications in full-size windows under DESQview (I like to see a lot of information when I am editing or working in the file system, etc.), and so primarily use windows when I have a background task I want to monitor progress on while I work on something else (such as to know when a file has finished downloading so I can switch back to that window to request another file download). DESQview if VERY flexible. It is a great environment to work in.