🚀 go-pugleaf

In article <3n9nl1$n...@dunx1.ocs.drexel.edu>,
st93...@dunx1.ocs.drexel.edu (Hon Chong Chang) says:

>First, Does this means that Win95 can MULTITASK DOS VDM? Because I'm foremost looking
>for a *TRUE PRE-EMPTIVE MULTITASKING OS* and I really would like to multitask in
>DOS. The easiest way to test this I think, will be to load up DOS VDM under win95,
>play a MOD file (i.e. I think DMP or most popular modplayers should do) and then
>switch back to win95's equivalent of program manager. Is the music still there?
>(this test should also be able to test the stability of win95, because mod playing,
>especially using a SoundBlaster XX crunches up tons of resources and generates tons
>of system interrupts and DMAs). Does the music die down if I start another DOS VDM?
>(try playing the DOS QBASIC's NIBBLES or any other games that do not use soundcards)
>Also, can someone tell me how well windows handles DOS communication softwares? I
>know win95 native comm program would exist, but I just like to test the stability
>and comm port handling ability of win95 DOS VDM. What happens when you try to use
>the same comm port? (i.e. load up another comm program that uses the same comm port)

Even Windows 3.1 preemptively multitasks dos sessions (provided you configure the
PIF file settings correctly), so I doubt that there's any problem under
Win95.  Windows is a stange creature: a very nice premptive mutltasking OS, 
and a very nice GUI API, but you can't use them both at the same time.
Win16 apps are always cooperatively multitasked under Windows 3.1 and Win95.


Stephen C. Steel       <rev...@qv3pluto.LeidenUniv.nl>
Maintainer of Childrens Software Reviews WWW site:
http://qv3pluto.LeidenUniv.nl/steve/reviews/welcome.htm
==========================================================