The architecture of a virtual video device driver conforms to the architecture defined for all virtual device drivers. However, some parts of the multiple DOS session's architecture have been designed primarily for virtual video device drivers, as follows:

• Foreground and background notification hooks
  
• Freeze and thaw services
  
• Title change and code-page change notification hooks

A significant amount of the primary virtual video device driver code involves communication with the DOS Session Window Manager. A Remote Procedure Call (RPC) mechanism must be used to communicate between the DOS Session Window Manager and a virtual video device driver under the following conditions:

• The DOS Session Window Manager is a Ring 3 component (lowest privilege level); 
  Virtual device drivers run at Ring 0 (highest privilege level);
  
  DOS sessions have no Local Descriptor Table (LDT) and therefore cannot attach to Dynamic Link Libraries (DLLs).

  For this purpose the DOS Session Window Manager creates a thread that calls the virtual video device driver to wait for a video event from any of the currently windowed DOS sessions.

  ---

  [Back: Overview]
  [Next: Design of Installable Virtual Video Device Drivers]