akcs.gregc@ddsw1.MCS.COM (*Greg*) (07/17/90)
Try the VM/386 first and then stay with DESQview because of the (technical)
side of things.
- Greg
p.s. VM/386 has to have Command.com in everywindow and it takes up memory.
But, a easy multitasking system. You have memory? You get VM/386.keithe@tekgvs.LABS.TEK.COM (Keith Ericson) (07/24/90)
In article <26a28878-3181.1comp.ibmpc-1@ddsw1.MCS.COM> akcs.gregc@ddsw1.MCS.COM (*Greg*) writes: >Try the VM/386 first and then stay with DESQview because of the (technical) >side of things. > >- Greg > >p.s. VM/386 has to have Command.com in everywindow and it takes up memory. > But, a easy multitasking system. You have memory? You get VM/386. First of all, VM/386 doesn't "do" windows - its a command-line oriented (for _real_ computer users :-) ) interface. Secondly, VM/386 may run a copy of command.com in each virtual machine, but 1) this could also be viewed as an advantage: a _different_ command processor in each virtual machine - command.com in one (why?), 4dos in another, mks shell in another, ms_sh, ..., ... 2) each virtual machine starts up with its own copy of a config.sys and autoexec.bat (or not, depending on command processor), meaning, for example, that if you're running memory-hogging networking programs in one virtual machine you won't _have_ to have those same programs running in every machine. kEITHe