|
MS-DOS-based applications that cycle on device input
|
| bet | 42/49 | | Sana | 29.03.2021 | | Hajmi | 197,5 Kb. | | #13691 |
MS-DOS-based applications that cycle on device input. MS-DOS-based applications that tightly loop for keyboard input, mouse activity, or other input device operations are often too CPU-bound to run effectively in the Terminal Services environment.
FoxPro® database for MS-DOS-based applications. These applications tend to be CPU interrupt-intensive and drain processor resources away from other user sessions. As in the previous case, these applications often cannot run effectively in the Terminal Services environment.
MS-DOS-based print applications. Many MS-DOS-based applications use print techniques that are not compatible with the Terminal Services environment. However, 16-bit Windows-based applications that use the standard Windows printing APIs function correctly.
MS-DOS and 16-bit Windows-based applications that internally mount NetWare drives. Programmatic NetWare drive-mapping operations do not function under Terminal Services. On the other hand, programmatic uniform naming convention (UNC) mounts work correctly.
16-bit Windows-based applications that directly access .ini files. Older Windows-based applications that directly access .ini files instead of using the standard APIs may not work when multiple users are concurrently running the application. To minimize compatibility issues and to maximize performance under Terminal Services Application, developers are strongly encouraged to port all MS-DOS or 16-bit Windows-based applications to the Win32 environment. Please refer to the MSDN Web site for additional information on porting 16-bit applications to the 32-bit Windows environment.
|
| |
