CMS - NT and DOS Apps

Top  Previous  Next

bsscnav4bsscnav5

Condition

 

Errors when running under NT

Most common error is DOS Error 4 - running out of file handles...

 

Action

 

The following info may be helpful in getting your CMS application to run under NT...

 

The most important point to remember when configuring NT is: NT DOES NOT READ CONFIG.SYS AND/OR AUTOEXEC.BAT !!! NT looks for, and reads AUTOEXEC.NT and CONFIG.NT (by default - or whatever files it is told to read...)

 

 

The following are heavily commented AUTOEXEC.NT and CONFIG.NT files.

AUTOEXEC.NT

 

@echo off

 

REM AUTOEXEC.BAT is not used to initialize the MS-DOS environment.

REM AUTOEXEC.NT is used to initialize the MS-DOS environment unless a

REM different startup file is specified in an application's PIF.

 

REM Install CD ROM extensions

lh %SystemRoot%\system32\mscdexnt.exe

 

REM Install network redirector (load before dosx.exe)

lh %SystemRoot%\system32\redir

 

REM Install DPMI support

lh %SystemRoot%\system32\dosx

 

SET CLIPPER=F71

 

REM End-of-file

 

CONFIG.NT

 

REM Windows NT MS-DOS Startup File

REM

REM CONFIG.SYS vs CONFIG.NT

REM CONFIG.SYS is not used to initialize the MS-DOS environment.

REM CONFIG.NT is used to initialize the MS-DOS environment unless a

REM different startup file is specified in an application's PIF.

REM

REM ECHOCONFIG

REM By default, no information is displayed when the MS-DOS environment

REM is initialized. To display CONFIG.NT/AUTOEXEC.NT information, add

REM the command echoconfig to CONFIG.NT or other startup file.

REM

REM NTCMDPROMPT

REM When you return to the command prompt from a TSR or while running an

REM MS-DOS-based application, Windows NT runs COMMAND.COM. This allows the

REM TSR to remain active. To run CMD.EXE, the Windows NT command prompt,

REM rather than COMMAND.COM, add the command ntcmdprompt to CONFIG.NT or

REM other startup file.

REM

REM DOSONLY

REM By default, you can start any type of application when running

REM COMMAND.COM. If you start an application other than an MS-DOS-based

REM application, any running TSR may be disrupted. To ensure that only

REM MS-DOS-based applications can be started, add the command dosonly to

REM CONFIG.NT or other startup file.

REM

REM EMM

REM You can use EMM command line to configure EMM(Expanded Memory Manager).

REM The syntax is:

REM

REM EMM = [A=AltRegSets] [B=BaseSegment] [RAM]

REM

REM AltRegSets

REM specifies the total Alternative Mapping Register Sets you

REM want the system to support. 1 <= AltRegSets <= 255. The

REM default value is 8.

REM BaseSegment

REM specifies the starting segment address in the Dos conventional

REM memory you want the system to allocate for EMM page frames.

REM The value must be given in Hexdecimal.

REM 0x1000 <= BaseSegment <= 0x4000. The value is rounded down to

REM 16KB boundary. The default value is 0x4000

REM RAM

REM specifies that the system should only allocate 64Kb address

REM space from the Upper Memory Block(UMB) area for EMM page frames

REM and leave the rests(if available) to be used by DOS to support

REM loadhigh and devicehigh commands. The system, by default, would

REM allocate all possible and available UMB for page frames.

REM

REM The EMM size is determined by pif file(either the one associated

REM with your application or _default.pif). If the size from PIF file

REM is zero, EMM will be disabled and the EMM line will be ignored.

REM

dos=high, umb

device=%SystemRoot%\system32\himem.sys

FILES=150

 

You may also create the following files: These files are the AUTOEXEC.NT and CONFIG.NT files with most of the comments removed...

 

AUTOEXEC.ST (for Stockroom...)

 

REM Install network redirector (load before dosx.exe)

lh %SystemRoot%\system32\redir

 

REM Install DPMI support

lh %SystemRoot%\system32\dosx

 

SET CLIPPER=F71

 

CONFIG.ST

 

dos=high, umb

device=%SystemRoot%\system32\himem.sys

FILES=150

 

 

Screen shot of Shortcut below....

 

 

This is a shot of the shortcut for a CMS Application. Click on the Windows NT button...

 

Create these files (CONFIG.NT and AUTOEXEC.NT) in the SYSTEM32 directory. Then in the shortcut properties, select the Program tab, the click on the Windows NT button. The "Custom MS-DOS Initialization Files" dialog appears. Change the names of these files from AUTOEXEC.NT and CONFIG.ST to AUTOEXEC.ST AND CONFIG.ST

 

Rebooting is not necessary after making these changes. If you continue to get DOS ERROR 4 errors, change the FILES statement to FILES=255. The software typically works with FILES=100. It may be possible that there are too many open applications on the system. Close all applications and then run Stockroom Inventory Manager. No errors now? Errors are due to running out of system resources with the existing configuration/open applications.

 

Go to CMS Support Page Go to the CMS Home Page   Return to CONTENTS Page