Prosoft-technology MVI69-ADMNET Instrukcja Użytkownika Pobierz pdf (Strona 35)

MVI-ADMNET ♦ 'C' Programmable Setting Up Your Development Environment

'C' Programmable Application Development Module with Ethernet Developer's Guide

ProSoft Technology, Inc. Page 35 of 122

February 20, 2013

If a command interpreter is needed, a line like the following should be included in

CONFIG.SYS:

SHELL=A:\TINYCMD.COM /s /p

If a command interpreter is not needed, the user application may be executed

directly from the CONFIG.SYS file as shown (where USERAPP.EXE is the user

application executable file name):

SHELL=A:\USERAPP.EXE

The user application may also be executed automatically from an

AUTOEXEC.BAT file, or manually from the console command line. In either

case, a command interpreter (page 35) must be loaded.

MVI56

IRQPRIORITY=1

INSTALL=A:\MVI56bp.exe

INSTALL=A:\MVI56dd.exe

MVI69

IRQPRIORITY=1

SYSTEMPOOL=16384

STACKS=5

SHELL=A:\TINYCMD.COM /s /p

INSTALL=A:\MVI69bp.exe

Note: At this time, messaging is not supported on the MVI69.

MVI71

IRQPRIORITY=1

INSTALL=A:\MVI71bp.exe

MVI94

IRQPRIORITY=1

INSTALL=A:\MVI94bp.exe

3.2.2 Command Interpreter

A command interpreter is needed if you want the module to boot to a command

prompt, or if you want to execute an AUTOEXEC.BAT file. Two command

interpreters are included, a full-featured COMMAND.COM, and the smaller, more

limited TINYCMD.COM. Refer to the General Software Embedded DOS 6-XL

Developer's Guide located on the MVI CD-ROM for more information.

3.2.3 Sample ROM Disk Image

The sample ROM disk image that is included with the MVI-ADMNET module

contains the following files:

1 2 ... 30 31 32 33 34 35 36 37 38 39 40 ... 121 122

Brak uwag

Prosoft-technology MVI69-ADMNET Instrukcja Użytkownika Strona 35