Dos drivers under Windows

Thread View: comp.windows.ms.programmer

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Mark Narduzzi Wed, 15 Apr 1992 06:33

#390

Author: Mark Narduzzi
Date: Wed, 15 Apr 1992 06:33

14 lines
923 bytes

I hope this is the right group for this question.

Is it possible for a DOS device driver, loaded in a DOS box,
to communicate with a Windows app (with Windows running in enhanced mode)?

The company we're consulting for insists on maintaining a single DOS
device driver to simplify support for their projects, so writing a
Windows driver is not an alternative at this time.

Please post or e-mail.
Microsoft? anyone?

Mark N.
nar@mathsun.math.wayne.edu

Re: Dos drivers under Windows

#433

Author: Richard Hancock
Date: Thu, 16 Apr 1992 10:23

18 lines
1176 bytes

/ hpopd:comp.windows.ms.programmer / axb@cse.nd.edu (Arindam Banerji) / 11:46 am  Apr 15, 1992 /

>[stuff deleted] This is not as bad as it
>seems, since in enhanced mode the Windows vitual 
>machine is non-premptable, although the DOS boxes are.

I think I know what you mean, but just in case anyone else
is confused, what I think you mean (to say) is that
pre-emption occurs at the virtual machine level but not at
the Windows app level.

In other words, virtual machines are
pre-emptively multitasked (by default) but Windows apps are
only ever non-pre-emptively multitasked (ie. a Windows app
must yield the processor for another Windows app to run).

While DOS apps each run in their own virtual machine, all
Windows apps run in the same virtual machine.

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