Thread View: comp.sys.powerpc
3 messages
3 total messages
Started by Douglas B Clayton
Wed, 23 Aug 1995 18:18
Re: Ask yourself these before you choosing a 32bit OS...
Author: Douglas B Clayton
Date: Wed, 23 Aug 1995 18:18
Date: Wed, 23 Aug 1995 18:18
25 lines
1692 bytes
1692 bytes
Excerpts from netnews.comp.sys.intel: 23-Aug-95 Re: Ask yourself these befo.. by Jim Williams@tiac.net >>And Windows does do that with DOS sessions. Make a simple batch file that >>does a directory listing, then calls itself. Open two DOS sessions, watch >>them both scroll by simultaneously. >> > >mmm... Not quite the same thing, and maybe I should perform the following >experiment -- but I'll just leave it to someone else. > >What happens if you write a small program which doesn't do any I/O (e.g. >a tight loop) and put that in two DOS windows? It multitasks it. (Obviously, because otherwise it would hang.) Someone posted a several-byte program that looped back to itself. It was one instruction long and could be compiled with DEBUG. No i/o, no DOS calls. Windows multitasks it fine (note: "fine" here means it's pre-emptive; its efficiency is another matter). In fact, you can open up several boxes and run that program and it still multitasks it. Of course, you have to set "Background execution" or something like that in its PIF or in the Settings dialog box. DOS apps it multitasks pretty well--it's the Windows apps that are cooperative. Douglas Clayton
Re: Ask yourself these before you choosing a 32bit OS...
Author: Linh Dang
Date: Wed, 23 Aug 1995 19:33
Date: Wed, 23 Aug 1995 19:33
36 lines
2287 bytes
2287 bytes
Douglas B Clayton (dc6f+@andrew.cmu.edu) wrote: : Excerpts from netnews.comp.sys.intel: 23-Aug-95 Re: Ask yourself these : befo.. by Jim Williams@tiac.net : >>And Windows does do that with DOS sessions. Make a simple batch file that : >>does a directory listing, then calls itself. Open two DOS sessions, watch : >>them both scroll by simultaneously. : >> : > : >mmm... Not quite the same thing, and maybe I should perform the following : >experiment -- but I'll just leave it to someone else. : > : >What happens if you write a small program which doesn't do any I/O (e.g. : >a tight loop) and put that in two DOS windows? : It's not really Wind*ws that multitask those dos apps, it's the i386 cpu. Wind*ws just creates the VMs and put load the dos apps. I may be wrong but I think that the scheduler (the i386) doesn't even know whether the dos apps is doing I/O or not. --------------- L.D. : It multitasks it. (Obviously, because otherwise it would hang.) Someone : posted a several-byte program that looped back to itself. It was one : instruction long and could be compiled with DEBUG. No i/o, no DOS calls. : Windows multitasks it fine (note: "fine" here means it's pre-emptive; : its efficiency is another matter). In fact, you can open up several : boxes and run that program and it still multitasks it. Of course, you : have to set "Background execution" or something like that in its PIF or : in the Settings dialog box. : : DOS apps it multitasks pretty well--it's the Windows apps that are cooperative. : : Douglas Clayton
Re: Ask yourself these before you choosing a 32bit OS...
Author: scott goehring
Date: Thu, 24 Aug 1995 06:37
Date: Thu, 24 Aug 1995 06:37
21 lines
1340 bytes
1340 bytes
-----BEGIN PGP SIGNED MESSAGE----- In article <41fvqq$efj@bmtlh10.bnr.ca>, Linh Dang <linhd@bnr.ca> wrote: >It's not really Wind*ws that multitask those dos apps, it's the i386 >cpu. Wind*ws just creates the VMs and put load the dos apps. I may be >wrong but I think that the scheduler (the i386) doesn't even know >whether the dos apps is doing I/O or not. no CPU i've ever heard of has a process scheduler. the operating system does that; in this case, it's Windows. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMDweGxbgfSHT/piVAQGxxgP/abYp97OsoMGXKsaLMfCPrf7ya+w4eZjc Sl18BUwyKWwYq7xwKpzFc4+U/lk7Qcr7rxLKsLLNVk4+GJk3gYnOVKobLbo8JwI5 7DQJ1Mfz4SDBof2G+fvVXfhxNo93kPtDvEYuD+/yGOASXYwyASiKDktvfRgpqqtU X5QPPAEB8E8= =NoB9 -----END PGP SIGNATURE-----
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads