On Tuesday 24 January 2006 01:11 am, Jan Knutar wrote:
> On Tuesday 24 January 2006 08:37, dene maxwell wrote:
> > Hi,
> > I think you might be mistaken, 95,98,98se & 98SP5 known as ME, all had
> > cooperative multitasking. This has been well documented in the MSDN
> > developers mailing lists and numerous developers literature.
>
> Can you give me an URL to the relevant MSDN articles?
>
> > The first
> > windows that was cooperative was NT 3.51...this went on to variouys
> > iterations to become Win 2K and laterly XP.
>
> Although I haven't used it, surely NT 3.51 would have been preemptive
> and not cooperative. I can't believe Microsoft started on NT (New
> Technology) and tried cooperative.
This is exactly the case NT, 2000 and XP are all OS/2 derivatives and have no
real relationship to 3.x, 95, 89... other than sharing some of the same high
level API's. The kernel architecture and all of the underlaying hardware
support layers are totally different and NT, 2000 and XP like OS/2 were
preemptive and protected from the beginning. None of the 3.x derived
versions of Windows (95, 98...) were either preemptive or protected.
>
> > By the very definition of cooperative multitasking you only need to look
> > at the messages in the "Blue Screen of Death" This is primarily a 95, 98,
> > 98SE and ME phenomenon...
>
> And a W2K, and XP phenomenon.
>
> Usually the bluescreen seems to happen when the OS hits a condition from
> which it does not how to recover. This happened more often in Windows 9x&ME
> because software and drivers needed less priviledges to access hardware
> directly, and when they faulted, the operating system had all the time been
> unaware of what these drivers had been doing, and thus unable to recover.
>
> In NT based Operating Systems, drivers are not allowed direct access as
> easily as during 9x. The Driver Certification (or whatever it is called)
> certainly helps with this too, since drivers will not get certified if they
> do strange things behind the back of windows.
>
> Blue Screens have actually nothing to do with multitasking whatsoever.
> Bluescreens occur when the system has encountered an unexpected situation,
> and does not know how to recover from it. The basic facilities of the
> system (like multitasking, paging) have been compromised, and attempting to
> continue from there would most certainly result in extremely unpredictable
> behaviour from the driver that violated system protections in the first
> place. You CAN try to continue, but most likely, this would result in
> massive corruption, and if you were lucky, none of this corruption would
> hit the harddrive and mess up your data forever, but the risk of that
> happening is too high. The only sensible thing is to halt the system.
>
> > I refer you to Dan Appleman - Visual Basic Programmers Guide to the Win32
> > API IBSN 1-56276-466-2 for the definitive word.
>
> I would rather refer to MSDN documentation. I have not programmed visual
> basic extensively.
>
> The fact that I can run the following program and still the other programs
> running are able to respond, to me, proves that the system does not use
> cooperative scheduling:
>
> int main(){while(1);}
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Flightgear-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flightgear-users
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Flightgear-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-users
