home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Share Gallery 1
/
share_gal_1.zip
/
share_gal_1
/
LA
/
LA007.ZIP
/
VMIX.DOC
< prev
next >
Wrap
Text File
|
1990-08-12
|
71KB
|
1,173 lines
_______
____|__ | (tm)
--| | |-------------------
| ____|__ | Association of
tm | | |_| Shareware
VMiX 386 Version 2.50 |__| o | Professionals
----------------------- -----| | |---------------------
|___|___| MEMBER
Copyright (c) 1985-1990
Commercial Software Associates
Post Office Box 5054
Playa del Rey, California 90293
BBS (213) 670-4486 (24 Hrs.)
VOICE (213) 670-3386 (8 - 6pm PST)
_______________________________________________________________
| |
| WHAT IS VMiX? |
| |
| VMiX is a multitasking and multiuser environment for |
| IBM PC's and PS/2's (PC, XT, AT, PS/2) compatibles. |
| |
| Version 2.50 configures itself to your processor. If you |
| have an 8088 or 8086, then your applications must share |
| the up to 566 Kbytes available after VMiX loads in low |
| memory. If you have an 80286, then VMiX can multitask |
| applications in low conventional memory or it can swap |
| applications to extended memory. Swapped tasks will be |
| swapped back regularly for a timeslice of the processing |
| or they can remain suspended until reactivated. |
| |
| If you have an 80386/486, VMiX will multitask in extend- |
| ed memory. It will execute each task in virtual 8086 |
| mode, with protected mode pagging, and virtualized video |
| screens, mapping a new 640 Kbytes to each new task. |
| |
| Multitasking is supported at the console, in windows or |
| full screen. If you do not like windows at your console |
| you can choose to use terminals or PC's attached to the |
| COMM ports. |
| |
| The VMiX environment uses the best from MSDOS and UNIX |
| in its implementation of the user control shell and |
| multitasking. The user has a choice of 2 user interfa- |
| ces: the VMiX shell, which can talk to the MSDOS shell |
| (you get both sets of commands), or the VMiX pull-down |
| menus interface which is a multi-threaded environment. |
| |
| Applications that do not write directly to the video, |
| like DBASE, TURBO PASCAL, PROCOMM, WSTAR, WORDPERFECT, |
| OPUS BBS, or BASIC will display correctly at a terminal. |
| Applications that write directly to the video, can be |
| virtualized at the console. |
| |
| VMiX co-resides with DOS 2.1 through 4.02 |
|_______________________________________________________________|
_______________________________________________________________
| |
| HOW TO INSTALL VMiX? |
| |
| VMiX is easy to install. Simply copy the executable |
| files in the VMiX archive to your directory and execute |
| the boot module VM_BOOT.EXE |
| |
| There are 4 start-up options, if VMiX fails to start |
| correctly on your computer. 'VM_BOOT 8086' will force |
| real mode on 80286/386/486 computers, and 'VM_BOOT ext' |
| will force 80286 VMiX mode on 80386/486 computers. Using |
| 'VM_BOOT low' or VM_BOOT low ext' will inhibit relocation |
| of portions of VMiX to extended memory. Some EGA/VGA's |
| will display no cursor or what appears to be a broken |
| cursor when Shift-Tab is pressed to switch tasks. To |
| correct this, start VMiX with the command line 'VM_BOOT |
| egacur'. Use of these 4 options might allow VMiX to |
| execute in your environment. |
| |
| Later you will learn how to customize your VMiX start-up |
| by including command arguments in the VM_BOOT command |
| line from DOS. |
|_______________________________________________________________|
_______________________________________________________________
| |
| HOW TO INSTALL MY APPLICATIONS? |
| |
| If you can execute your applications from DOS, they |
| are already installed for VMiX. VMiX does not use PIF |
| or other types of application configuration files. |
| |
| Applications that write directly to the screen can |
| coexist with other applications at the console, but |
| will not display properly at a COMM port terminal. |
|_______________________________________________________________|
_______________________________________________________________
| |
| HOW MUCH MEMORY WILL REMAIN AFTER VMiX IS INSTALLED? |
| |
| On a 640Kb memory 8088 PC or 80286 AT with DOS 3.1 and |
| no installed TSR's, there will remain 470Kb to 566Kb of |
| memory for applications. VMiX can be told to fill memory |
| above 640Kb with 96Kb of additional DOS program space in |
| alphanumeric text modes on EGA/VGA equipped systems. |
| On the 80386, each task gets it's own 640Kb from your |
| extended memory pool. |
|_______________________________________________________________|
_______________________________________________________________
| |
| HOW DO I VALIDATE THAT VMIX IS WORKING CORRECTLY ON MY |
| SYSTEM? |
| |
| To test VMiX, we recommend that you perform the two |
| tests below: |
| |
| TEST 1: Validates that VMiX itself is working correctly. |
| |
| invoke VMiX as follows: (from the directory where you |
| copied VM_BOOT.EXE ) |
| |
| vm_boot do /debug set |
| |
| and PRESS <ENTER> |
| This will start 2 tasks: |
| the root shell or main |
| window, where the key- |
| board will remain unless |
| you press <SHIFT><TAB>, |
| |
| a VMiX debugger task |
| displaying information |
| about the 'set' command. |
| If all windows display activity, the TEST PASSED. |
| From the root window type 'quit' and press <ENTER>|
| to exit VMiX. |
| |
| |
| TEST 2: Validates that VMiX, your version of MSDOS, and |
| your system's ROM BIOS, all get along fine. |
| |
| invoke VMiX as follows: (from the directory where you |
| copied VM_BOOT.EXE ) |
| |
| vm_boot do dir c: /type c:\autoexec.bat |
| |
| and PRESS <ENTER> |
| This will start 2 tasks: |
| the root shell or main |
| window, displaying your |
| autoexec.bat file, where |
| the keyboard will remain,|
| |
| and another task doing a |
| directory. |
| If all windows display activity, the TEST PASSED. |
| From the root window type 'quit' and press <ENTER>|
| to exit VMiX. |
|_______________________________________________________________|
_______________________________________________________________
| |
| WHAT IS UNIQUE ABOUT VMiX? |
| |
| VMiX is supported shareware. In the rapidly developing |
| multitasking market, VMiX has undergone over 25 new |
| releases in the last 5 years, each with new and enhanced |
| features. |
| |
| VMiX provides an easy to install and operate environment |
| that can be used to multitask DOS. It can also be used |
| to simply task switch applications to extended memory on |
| an 80286/386/486 AT's. |
| |
| VMiX also provides remote modem access to your multi- |
| tasking PC server. |
| |
| VMiX gives you more than a multitasker, it gives you an |
| operating system which gently introduces you to the new |
| complexities of advanced systems. |
| |
| If you can execute your applications from DOS, they are |
| already installed for VMiX. VMiX does not use PIF or |
| other types of application configuration files. |
| |
| APPLICATION SCREEN HANDLING |
| |
| do do -W 'terminal' |
| -------------------------------------------- |
| 8086 Mode Text Mode Text Mode Text Mode |
| Graphics Mix Txt/Grphcs - |
| BIOS Video BIOS Video BIOS Video |
| - - - |
| |
| 286 Ext Mode Text Mode Text Mode Text Mode |
| Graphics Mix Txt/Grphcs - |
| BIOS Video BIOS Video BIOS Video |
| - - - |
| |
| 386 Mode Text Mode Text Mode Text Mode |
| Graphics Limited Grphcs - |
| BIOS Video BIOS Video BIOS Video |
| - Direct Video - |
| |
| The VMiX command interface is layered, to protect the |
| casual user who just wants to get maximum utility and |
| does not need or wants to learn the full system. |
| For the serious operator or software developer, VMiX |
| provides an internal 'debug' shell which can be coupled |
| with a DOS debugger or tool, as a concurrently executing |
| VMiX task, to examine other live applications. |
|_______________________________________________________________|
_______________________________________________________________
| |
| SAMPLE STARTUP |
| ----- if your printer, mouse, or modem is on COM1, |
| then COM2 is available for user logins: |
| (NOTE the lower case 'L', below) |
| |
| C> vm_boot set remote -l2 |
| |
| ----- if your printer, mouse, or modem is on COM2, |
| then COM1 (VMiX default) is available for logins: |
| |
| C> vm_boot |
| |
| ----- if you are using both COM1 and COM2, |
| then set VMiX to COM3 to avoid interferance: |
| (NOTE the lower case 'L', below) |
| |
| C> vm_boot set remote -l3 |
| |
| ----- if you want to start with the VMiX pull-down |
| menus: |
| |
| C> vm_boot vw |
|_______________________________________________________________|
_______________________________________________________________
| |
| QUICK START TO VMiX MULTITASKING |
| |
| The VMiX manual is big and spread out, but the last |
| 2 chapters describe each VMiX command in detail. |
| |
| Basically these are the commands that you must master |
| FIRST, to start using the multitasking features right- |
| away. |
| |
| |
| ? Pressing '?' will display a list of avail- |
| able VMiX commands. Typing a VMiX command |
| that requires additional parameters, will |
| display usage information. |
| |
| |
| exec This command allows you to partition the |
| use of your PC's memory between tasks. |
| By default, VMiX partitions each new MSDOS |
| task into 224Kb chunks of available memory, |
| on 8088 and 80286 processors. On the 80386 |
| the default partition size is 576Kb. |
| |
| To override the defaults, you might type: |
| exec -m128 |
| |
| this sets the partition size to 128Kb. |
| Any new program, after that, will only see |
| a maximum of 128Kb available, until the next|
| 'exec -m' reduces or expands the current |
| limit. |
| |
| In 80386 processors, selecting a partition |
| size smaller than the 576Kb default, will |
| cause new tasks to use the parent's memory |
| partition and will not be mapped to their |
| own 640Kb, from the extended memory pool. |
| |
| |
| do This command allows you to specify a new |
| MSDOS task. 'do' is short for 'dosjob'. |
| To execute BASIC in a window, you would |
| type: |
| do c:\basic |
| |
| 'do' is the basic VMiX command to start a |
| new and separate process. |
|_______________________________________________________________|
_______________________________________________________________
| |
| do -W To execute BASIC and give it the full |
| screen, you would type: |
| do -W c:\basic |
| |
| On the 386/486 the -W switch virtualizes |
| the video segment of the task, allowing it |
| to be moved to and from the foreground |
| without disturbing the display of other |
| tasks. |
| |
| Shift-TAB Once you have started several windows, or |
| full screen tasks, you will need to move |
| the keyboard and/or video display between |
| them, so that input to each task can be |
| safely directed to only that task. You |
| move the keyboard and foreground display, |
| in round-robin fasion by pressing the |
| <SHIFT> and <TAB> keys simultaneously. |
| Shift-Tab will also clear any defunct |
| windows partitions, when there is only one |
| shell active. |
| |
| do /rshell To clone the VMiX command shell into a 2nd |
| shell, you type: |
| do /rshell |
| |
| The / tells VMiX this is not a command for |
| MSDOS but for VMiX. VMiX will ask you for |
| a login name, type: |
| su |
| |
| This is a reserved name for a VMiX operator |
| with 'kill' process priviledges. |
| |
| do . To clone an MSDOS command shell as the 2nd |
| window, you type: |
| do . |
| |
| To close the window, type from MSDOS: |
| exit |
| |
| NOTE THAT THE VMiX SHELL PROMPT DIFFERS |
| FROM THE MSDOS SHELL PROMPT IN THE SINGLE |
| SPACE THAT FOLLOWS THE PROMPT. |
| From the VMiX Shell |
| a directory request would look like |
| C> dir |
| From MSDOS it would look like |
| C>dir |
|_______________________________________________________________|
_______________________________________________________________
| |
| $$ Particularly in 386 mode, you might find |
| that some programs might crash VMiX or fail |
| to execute correctly. To provide system |
| protection, when executing an ill-behaved |
| program, precede the filename and path |
| with the characters '$$': |
| $$[drive:][path]filename |
| or, |
| do $$[drive:][path]filename |
| |
| |
| NOW THAT YOU KNOW EVERYTHING, YOU CAN CHOOSE TO FORGET |
| ALL ABOUT IT AND INSTEAD, USE THE VMiX PULL-DOWN MENUS |
| BY TYPING, AFTER VMiX STARTS: |
| |
| C> c:\vmix\vw |
| |
| VW requires your PATH to include the directory where |
| the VMiX utilities reside. |
| |
| REMEMBER THAT ANY COMMAND YOU CAN GIVE FROM INSIDE VMiX |
| CAN ALSO BE STATED IN THE VM_BOOT COMMAND LINE, EACH |
| COMMAND SEPARATED BY A / |
| |
| Congratulations, you are now a certified VMiX SysOp. |
|_______________________________________________________________|
_______________________________________________________________
| |
| WHAT IS AHEAD FOR VMiX? |
| |
| Virtual 386 DOS file buffers to avoid DOS file |
| read/write conflicts with multiple file I/O. |
| Compatibility with other extended memory software. |
| A new serial port data link driver. |
| A distributed file system: |
| 'rshell' to allow one VMiX PC to execute as a |
| client of a server VMiX at another PC. |
| This will allow one PC to multi-task on its |
| screen a program executing at a second PC. |
|_______________________________________________________________|
RELEASE NOTES
* See the revision.log file for enhancements and bug fixes to this version.
In Summary Version 2.50 is a new release and provides:
1. Fixed known crashiness bugs in previous version. Improved the
reliability of the VW utility, which we can now recommend for regular
use.
2. Added support for multiple default drives and made each task's default
drive independent from other windows/tasks.
3. Added support for virtual video. Eliminates bleed-through, when in
386 mode, by applications that write directly to the screen in text mode.
Tasks started with the 'dosjob -W' command, and all tasks started at a
dumb terminal will execute with virtualized video segments in 386 mode.
The Shift-Tab hot key will bring a virtualized task's video to the
foreground.
4. Added a better command line parser and changed the syntax of the start-up
configuration options:
The new command syntax is:
VM_BOOT [low] [high] [8086] [extended] [egacursor]
[cgacursor] [ [ command ] /... ]
where (note abbreviated syntax),
the '8086' option forces 8088 (real mode) operation on 286/386/486
computers.
the 'ext' option forces 80286 (real/protected mode) operation on
386/486 cpu's.
the 'lo' option inhibits relocation of VMiX code to extended memory.
the 'hi' option forces relocation of VMiX code to extended memory when
using 8086 mode in a 286/386 or 486.
the 'egacur' option corrects a video BIOS bug that fails to indicate
that CGA cursor emulation is disabled.
the 'cgacur' option corrects a video BIOS bug that fails to indicate
that CGA cursor emulation is enabled.
[ command] / any valid DOS or VMiX shell commands, separated by a '/'
5. Added scroll control to the help display. (for example, type 'set',
for help on the command 'set')
6. For shell usage compatibility, Escape now also clears the command line,
like a Ctrl C. An <ENTER> on a blank line will not clear the previous
command buffer, which you can still repeat using up-arrow.
7. Logins at a comm port can now be enabled/disabled with the 'set remote
-e' command toggle. The default is logins enabled. You can only use
this command from the VMiX shell, it will be ignored when used in the
VM_BOOT command line.
The 'set remote -l' command controls the comm port where logins are
polled for.
The 'set remote -c' commands relocates the VMiX shell to the remote
channel specified.
8. Note, some EGA/VGA's will display what appears to be a broken VMiX
cursor when Shift-Tab is pressed to switch tasks. To correct this,
start VMiX with the command line 'VM_BOOT egacur'.
9. The VW menu shell is NOW COMPLETE and greatly improved.
VW.EXE can now be used to set screen colors from the options menu.
VW is a multiple thread environment (like OS/2), the slight delays
you will sometime experience when returning from a command are due
to process synchronization, this will improve in future versions.
10. On systems with EGA/VGA, an additional 96Kb of DOS program space is
now available (64Kb in monochrome mode). To toggle the additional
program space ON/OFF, use the VMiX command 'set system -v'. The
default is OFF, when VM_BOOT is executed. This option will allow
large programs (566Kb maximum) to be executed with VMiX (the maximum
without this option is about 470Kb). Eventhough VMiX uses extended
memory in 286/386 ATs/PS2s, the user partition size is limited by the
address space of DOS, which is now expandable to 736Kb.
11. I/O redirection is now fully implemented. Basically, if you start
a process (with 'dosjob'), you can then use the utility DSTAT.EXE
(use 'dstat -a' to see assigned channels only) and determine what
channels are available to relocate your process to. Note that
available channels are shown as belonging to the scheduler. You can
also use 'assign' to create a new channel to a serial port (SRCSINK)
or to a printer port (CHRSINK). Lastly, you use the new 'assign'
syntax to assign a new channel to your executing process. The original
channel of the process will remain available for restoring the process
back to its original state. You must repeat the 'assign', and give
the process its the old channel id.
The VMiX debugger 'assign' command now accepts the PROCESS object type.
The general syntax for the 'assign' command is:
assign [client process id] [object type]
[port id or channel id]
If client process id is omitted, it defaults to the current process.
If object type is SCRSINK, then the third argument is a COMM port (0-4),
where 0 refers to the console and 1-4 are serial ports.
If object type is CHRSINK, then the third argument is an LPT port (1-2).
If object type is PROCESS, then the third argument is a previously
assigned channel id.
The purpose of the PROCESS assign is to redirect the STDIO (screen and
keyboard) of a process to a new channel. You can move a process using
the console to a COMM port terminal or to a printer CHRSINK type of
channel.
Again, VMiX will prompt you for any arguments missing after the 'assign'
command, except for the first argument.
12. VMiX is now one of the fastest MSDOS multitaskers. The preemptive
scheduler is now fully sensitive to I/O. The following devices affect
the executing priority of a task: keyboard, disk drives, COMM ports.
13. The VMiX start-up program 'VM_BOOT' accepts several command line
arguments that control the mode the program runs. Using 'VM_BOOT 8086',
will force VMiX into real (8086) mode and using 'VM_BOOT ext', will
force VMiX into extended (80286) mode. These 2 command line switches,
disable 80386 protected mode operations. (Useful for getting around
compatibility problems, on certain computers.) Using 'VM_BOOT low' or
'VM_BOOT low ext' inhibits relocation of portions of VMiX to extended
memory.
14. IMPORTANT NOTICE: We have found that the following reasons are the
most frequent causes of VMiX 386 failure:
a) Cable connected to COM1 port which causes VMiX port
test to hang. Recommend to test VMiX with serial
cable disconnected during vm_boot process. Make
a new cable as described in the VMiX manual.
b) The contents of your CONFIG.SYS specify a device
driver that uses extended memory in conflict
with VMiX. (for example, SMARTDRV.SYS, HIMEM.SYS)
c) Failure to reassign VMiX's default port for user
logins, COM1, to another port number when COM1 is
already in use (modem, mouse, etc.). Recommend to
start VMiX with a non-existent port for logins:
(NOTE the lower case 'L', below)
vm_boot set remote -l4 (ie., COM4)
d) Using 'swap' with an extended memory cache program
installed, when VMiX has not been told to reserve
in-use extended memory with the debugger shell
command:
'assign memory ????'
where ???? is number of bytes to reserve above
1 Megabyte (ie., 500000 bytes will be rounded
up to the nearest multiple of 4Kbytes).
e) Using an ANSI.SYS driver that does not support
discreet window scrolling, but instead, always
scrolls the entire screen. Quarterdeck Office
System supplied DVANSI.COM (for DESQview) works
correctly with VMiX 386.
f) Using VMiX with DOS 4.01 on some 386 computers
will boot OK, but multitasking will be erratic
or lock the system.
g) The following vendor's 386 computers are known
to crash (incompatible) or not crash (compatible)
VMiX during 386 protected mode start-up:
(Some 386 BIOSes like Compaq's are currently having
a problem with VMiX + DOS 4.01)
Incompatible Compatible
--------------- -------------------
CompuAdd 386 AST Premium 386
HP Vectra 386 AT&T 386
Zenith 386 Cheetah cAT 386-20
COMPAQ 386-25
COMPAQ 386-SX
COMPAQ Deskpro
Dell 310
Everex 386-16
Everex Step 386-25
Gateway 2000 386-20
IBM PS/2 70-80
Micronics 386
Monolithic 386-16
Northgate 386
Olivetti 386-20
Tandy 5000
ZEOS 386
IMPORTANT IMPORTANT IMPORTANT
--------- --------- ---------
N O T I C E
The manual included in the non-registered distribution diskette is the
last ASCII version of the VMiX manual. This manual, describes the use of
VMiX Versions 1.4X. It should be sufficient to allow you to fully test
VMiX. All changes to VMiX, since its introduction April 1987, are logged
in the REVISION.LOG file, including the new features in Version 2.50.
The VMiX COMMAND LOOK-UP - QUICK REFERENCE, shown below, is the current
list of all VMiX Version 2.50 commands and syntax. VMiX provides built-
in help, as described in the 1.4X manual.
If you decide that VMiX is the way to go, please register, and we will
ship to you the new printed manual for version 2.XX, and the source code
to the VMiX utilities and Application Programmer's Interface to VMiX.
Additionally, you will receive the eight user version and a version
optimized for the 80386 instruction set.
We appreciate the comments and help of all the users, who through
various BBS's helped debug VMiX. Thanks!
QUICK OVERVIEW
* VMiX is not presently a full operating system. It provides the services
of a multiuser operating system supervisor. The VMiX kernel ties tightly
between the host operating system I/O services and the user applications.
The eventual goal of the VMiX kernel is to arbitrate the use of system
resources by individual tasks with either or both UNIX I/O or DOS I/O,
in an environment providing up to 16 megabytes of physical memory.
* The console screen can be automatically partitioned into up to four
windows, for a total of 4 tasks executing from the console. The active
task controls and responds to the console keyboard. The active task
can be switched, at any time, by pressing the hot key, Shift-Tab.
* VMiX does not need to operate in protected mode to multitask. Hence, it
can be used in 8088 PCs. In 80286 mode, VMiX ocassionally needs to use
protected mode for swapping. In 80386 mode, VMiX operates in protected
mode at all times. System services are provided in SYSGATE.ASM to execute
your own functions in protected mode. The debugger "assign gdt" method
allows entries to the VMiX GDT. This can also be done with the memory
manager system service.
* REMOTE permits a user to call a remote PC running VMiX, and teleoperate,
as if he were at the console of the remote PC. Useful for remote customer
support of application programs, offsite login and operations. VMiX
terminal drivers provide full CGA text mode emulation at a COMM port.
* With VMiX you can run programs like WINDOWS, LOTUS 123, XTALK, BASIC,
DBASE, or WORD at the console and BASIC, DEBUG, TURBO PASCAL, WORDSTAR 3.2,
WORDSTAR 4.0, WordPerfect 4/5, PROCOMM 2.4, or DBASE II/III at a COMM
terminal. Multiple BASIC or GWBASIC interpreter sessions are supported.
* Supports a maximum of five users (only because of COMM port limitations),
each with multiple processes up to a maximum of 8 total.
* SPAWN or '&' permits a script of VMiX shell commands to be submitted to a
background process executing the VMiX shell. This allows for background
jobs like compiling or printing by a concurrent child process.
* DOSJOB permits keyboard interactive applications to be partitioned and
managed as concurrent video display tasks. The -W option allows task
to use virtualized video memory for their own separate display screen.
Their display screens can be toggled to and from the foreground display.
* Loadable character fonts, 33 line CGA display and 43 line EGA/VGA display.
Version 2.50 provides support for EGA/VGA video modes and up-to 58 line
display, with VMiX font type 1.
* As explained in the manual, there are (4) four ways to execute a .BAT,
.COM, or .EXE program:
with 'exec' (now optional),
with a command line trailling '&',
with 'spawn',
or (the easiest way) with the 'dosjob' command.
When VMiX starts, unless you issued an 'exec -m<size in Kbytes>' at the
command line, VMiX will use memory partitions of 224Kb for (8088/80286)
programs or partitions of 576Kb in 80386 processors.
The 'exec -m ????', memory partitioning command, is intended for use
mainly on 8086 and 80286 computers, which can not use the VMiX 386 virtual
memory manager. This command guarantees that a second or third program
will find some memory available. The user can select, from the shell,
the partition size for any single program. If your system has 640Kb
memory, then the command 'exec -m192' will only let programs grab memory
to a maximum of 192Kb each. If you need to execute DOS commands like
'exec type <filename>' or 'exec dir', then setting 'exec -m128' should
provide enough memory for about 4 DOS shells in non-80386 systems.
* To use 'dosjob' to execute a VMiX shell command(s) in a separate console
window, precede the command with a / (ie., 'dosjob /debug' or 'dosjob
/rshell'). The / must not be used if the command is for DOS, for example
'do basica' or 'do dir'.
To use 'dosjob' to run a program that requires access to the full screen,
use the '-W' option (ie., 'dosjob -W [drive:][path]filename').
* The VMiX scheduler can provide interrupt corruption protection to multiple
executing tasks. This prevents, to some degree, changes effected by one
task to the system interrupt table from interferring with the interrupts
handlers expected by a second task. To request protection for an ill-
behaved program, precede the filename and path with the characters '$$'.
Programs using protection will execute slower. Some programs like
BASIC/BASICA and WINDOWS, automatically receive protection without '$$'.
The command syntax is:
exec $$[drive:][path]filename
or,
dosjob [-W] $$[drive:][path]filename
* VMiX can be started with the command line arguments: 8086, extended, low,
high, egacursor, or cgacursor. These switches affect the mode that VMiX
executes in and overrides internal configuration defaults. This option
allows VMiX to be downgraded and used with some compatibles, which can not
run VMiX protected mode functions.
The command syntax is:
VM_BOOT [low] [high] [8086] [extended] [egacursor]
[cgacursor] [ [ command ] /... ]
where (note abbreviated syntax),
the '8086' option forces 8088 (real mode) operation on 286/386/486
computers.
the 'ext' option forces 80286 (real/protected mode) operation on
386/486 cpu's.
the 'lo' option inhibits relocation of VMiX code to extended memory.
the 'hi' option forces relocation of VMiX code to extended memory when
using 8086 mode in a 286/386 or 486.
the 'egacur' option corrects a video BIOS bug that fails to indicate
that CGA cursor emulation is disabled.
the 'cgacur' option corrects a video BIOS bug that fails to indicate
that CGA cursor emulation is enabled.
[ command] / any valid DOS or VMiX shell commands, separated by a '/'
* Console operator status line 'set video -s'
* Built-in debugger 'debug' 'monitor -r'
* Memory manager and memory mapper 'monitor -m' 'monitor -p' 'examine mcb'
* User specified windows at either the console or VT-100 COMM terminal.
* Assembly and High Level Language interface.
* Interrupt 15h VMiX System Services.
Today VMiX is 100Kb of code and 20Kb of Kernel data.
75% Microsoft C and 25% MASM.
VMiX is (C) Copyrighted 'try before you purchase software'. This gives us
wide distribution for a low cost, thus keeping your purchase price also low.
When you are ready to register your version, or require:
pricing for support, the programming interface documentation, the new full
printed manual, the source code, corporate pricing, or other information,
please contact us.
Enjoy exploring VMiX and thanks
for supporting its development,
ComSoft
----------------------------------------------------------------------------
_______________________________________________________________
| |
| SHIPPING LIST |
| |
| The VMiX 386 System consists of the 28 files described below. |
| |
| These files reside in the three self-extracting archives: |
| |
| VMIX???.EXE (Shareware distribution ??? version id) |
| VMIX386.EXE (Registered Owners ONLY) |
| VMIXUTL.EXE (Registered Owners ONLY) |
| |
| |
| EXECUTABLE or OBJECT FILES |
| |
| - VM_BOOT.EXE - |
| The VMiX start-up program. |
| To start, |
| type VM_BOOT from DOS's C> prompt and press <ENTER>. |
| |
| - DPATH.EXE - |
| Utility executed by user to set the directory search PATH |
| for data files. |
| |
| Use DOS's 'PATH =' or 'SET PATH =' for executables. |
| Use VMiX's 'DPATH =' or 'SET DPATH =' for data files. |
| |
| - DSTAT.EXE - |
| Utility executed by user to view device/channel status. |
| |
| - MONITOR.EXE - |
| Debugging utility executed by user to examine memory and |
| process environment. |
| |
| - OUTSIDE.EXE - |
| 'Outside' MSDOS shell spawning utility for BBS operators |
| running BBS software under VMiX. |
| |
| - PS.EXE - |
| Utility executed by user to view process status. |
| |
| - VW.EXE - |
| Utility executed by user to add a pull-down menu |
| interface to the VMiX shell. |
| |
| - SYSGATE.OBJ - |
| Link object file for accessing the VMiX API (Application |
| Programming Interface). |
|_______________________________________________________________|
_______________________________________________________________
| |
| SOURCE FILES DOCUMENTATION FILES |
| |
| SYSGATE.ASM READ.ME |
| DSTAT.C VMiX.DOC(this file) |
| DPATH.ASM REVISION.LOG(upgrade history) |
| MONITOR.C DPATH.DOC |
| OUTSIDE.C MANUAL.DOC(version 1.4X) |
| PS.C |
| VW.C |
| C_BIOS.H |
| $_KERNEL.H |
| $_CONFIG.H |
| $_MEM.H |
| $_PROC.H |
| IO_CHAN.H |
| IO_IRP.H |
| IO_OBJ.H |
|_______________________________________________________________|
_______________________________________________________________
| |
| I N S T R U C T I O N S |
| |
| 1) BEFORE using VMiX 386, you must copy |
| the self-extracting archive from the |
| Shipping Diskette to your system |
| disk (or 1.2+ MBYTE floppy). |
| |
| NEVER use the Shipping Diskette to |
| actually run VMiX 386. Use the |
| copies that you have made from it |
| and keep the Master Disk in a cool, |
| secure place. |
| |
| STEP 1: Insert the Shipping Diskette in Drive A: |
| |
| STEP 2: Make a VMiX subdirectory in your hard disk. |
| |
| md \VMiX |
| cd \VMiX |
| |
| |
| STEP 3: Copy A:*.* to C:\VMiX |
| |
| STEP 4: Execute the archive to extract the files. |
| |
| STEP 5: Verify that the CONFIG.SYS file, in your |
| boot directory, includes the following 2 |
| lines and no DEVICE= lines that invoke an |
| extended memory driver like HIMEM.SYS, |
| QEMM.SYS, or SMARTDRV.SYS. |
| |
| BUFFERS = 15 (or more) |
| FILES = 20 (or more) |
| |
| |
| 2) To execute the VMiX 386 program you |
| will need MSDOS Version 2.10 or |
| above, and 256Kb of memory. A color |
| graphics card, VGA is recommended |
| for the console display. |
| |
| If you have a Monochrome Adapter, |
| VMiX will sense it. |
| |
| VMiX 386 does not need to operate in |
| protected mode in all configurations. |
| It will execute properly in PC's |
| with 8088 processors. |
| |
| Start VMiX by typing: |
| |
| C> VM_BOOT <ENTER> |
|_______________________________________________________________|
_______________________________________________________________
| |
| After VMiX starts, typing a '?' will |
| display all the available commands. |
| |
| Try: debug <ENTER> |
| (note the prompt changes to - ) |
| |
| Next, try 'set' or 'exam' and VMiX |
| VMiX will display how to complete |
| the command. VMiX will prompt for |
| for most command line arguments, not |
| included in the command line: |
| |
| Try: set video -m<ENTER> |
| to see the video modes available, |
| |
| set term -t<ENTER> |
| to see the terminals supported. |
| |
| |
| 3) To start VMiX 386 with the pull-down |
| menus interface: |
| |
| Set the PATH for the VMiX utilities: |
| |
| C> PATH = C:\VMiX <ENTER> |
| |
| Start VMiX by typing: |
| |
| C> VM_BOOT VW <ENTER> |
| |
| When VMiX starts, the top screen line |
| will display the available menus. |
| Move to the desired menu by pressing |
| right or left-arrow keys. Select a |
| menu by pressing the down-arrow key, |
| <ENTER>, or by typing the CAPITALIZED |
| letter of the menu name. |
| |
| Select a menu option by first moving |
| to the desired item with the down- |
| arrow and press <ENTER> to execute |
| the option. Exit from the VW utility |
| or pull-down menu with the <Esc> key. |
| |
| Pull-down options that display an ->, |
| indicate an additional pull-down, |
| reachable by pressing <ENTER> or the |
| right-arrow key. |
| |
| From a terminal running VW.EXE, use |
| <Ctrl><F> to enable function key |
| emulation, then backspace becomes |
| left-arrow, <Ctrl><J> and <Ctrl><K> |
| will act as down and up-arrow. |
|_______________________________________________________________|
_______________________________________________________________
| |
| MULTIUSER CABLING |
| |
| The RS232 cabling for COM1 and/or other user terminal/modem |
| serial ports where you intend to have VMiX loggins should be |
| constructed depending on whether the host PC will be connected|
| to a dumb terminal or to another PC acting as a terminal. |
| |
| |
| PIN PIN |
| |
| H 1 1 |
| O |
| S 2 -- - _ _ _ - -- 2 |
| T -_ __ - - |
| 3 __ _ - - - - _ __ 3 T |
| S E |
| e 4 4 R |
| r M |
| i --5 5 I |
| a -| N |
| l | --6 6 A |
| | L |
| P | 7 ------------------------- 7 |
| o | Add the jumpers to |
| r | --8 8 terminal side, only |
| t -| if using a 2nd PC as |
| --20 20 a terminal. |
| |
| |
| |
| |
| See Part II, Using VMiX 386, for |
| detailed instructions regarding the |
| use of VMiX 386 commands and options. |
|_______________________________________________________________|
----------------------------------------------------------------------------
VMiX COMMAND LOOK-UP - QUICK REFERENCE
|ROOT |DEBUG....................................|
|LEVEL..|LEVEL..|LEVEL............................|
| 0 | 1 | 2 |
|_________________________________________________|
| |
|[debug] |
| |set |
| |baud |
| -c " sets communications: chan|
| baud, parity, word, stop"|
| |dos |
| -i " toggles DOS child process|
| file inherit ON/OFF" |
| -n " sets DOS INT21 function |
| maximum nesting level" |
| -p " sets DOS current process |
| PSP: nuPSP(seg)" |
| -s " sets DOS virtual size: |
| (4Kb blocks)" |
| |font |
| -t " sets font type: (0 - 3)" |
| |pool |
| -a " adjusts program memory: |
| MCB(seg), nusize(para)" |
| -m " sets program partition |
| size: (0 - 1024Kb)" |
| -o " sets program memory |
| owner: MCB(seg), |
| nuPSP(seg)" |
| |process |
| -b " sets process shell buffer|
| size: (0 - 127)" |
| -e " toggles system evironment|
| protection ON/OFF" |
| -h " toggles process hardware |
| priviledge ON/OFF" |
| -s " toggles process system |
| priviledge ON/OFF" |
| |remote |
| -c " sets remote channel" |
| -e " toggles logins ON/OFF" |
| -l " sets terminal login |
| channel" |
| |system |
| -c " sets duration of task |
| slice: tickcnt - 1" |
| -m " toggles manager message |
| displays ON/OFF" |
| -s " toggles scheduler swapped|
| processing ON/OFF" |
| -t " toggles scheduler clock |
| processing ON/OFF" |
| -v " toggles free video memory|
| utilization ON/OFF" |
| -w " sets shutdown wait delay:|
| seconds" |
| |terminal |
| -t " sets terminal type: |
| (0 - 9)" |
| |video |
| -c " sets video bg/fg colors" |
| -C " sets window bg/fg colors"|
| -m " sets video mode:(0 - 16)"|
| -s " toggles status display |
| ON/OFF" |
| -w " sets root window size: |
| row0, col0, row1, col1" |
| -W " auto partitions (1 - 4) |
| task windows |
| (Shift-Tab toggles kbd)" |
| |init |
| |comm |
| -c " sets communications: chan|
| baud, parity, word, stop"|
| |print |
| -p " inits parallel port:chan"|
| |examine |
| |mcb |
| |status |
| |assign |
| " : process id, obj type, channel" |
| |gdt |
| |deassign |
| " : channel" |
| |gdt |
| |memory |
| |quit |
|rshell |
|remote |
| -c " sets remote channel" |
| -e " toggles logins ON/OFF" |
| -l " sets terminal login channel" |
|swap |
| " : process id" |
|chprio |
| " : process id, new priority" |
|[exec] |
| -a " adjusts program memory: MCB(seg), |
| nusize(para)" |
| -m " sets program memory partition size: |
| (0 - 1024Kb)" |
| -o " sets program memory owner: MCB(seg), |
| nuPSP(seg)" |
| |path " utility displays/sets |
| program file search path"|
| |dpath[.exe] " utility displays/sets |
| data file search path" |
| -v " sets verbose mode (default)" |
| -q " sets quiet mode" |
| -r " allows data read only" |
| -w " allows data read/write (default)"|
| -h " help" |
| |dstat[.exe] " utility displays all |
| VMiX objects" |
| -a " selects only assigned objects" |
| -r " selects only free objects" |
| |monitor[.exe] " utility monitors process/|
| system: process id" |
| -m " displays 1 megabyte memory map" |
| -p " displays VMiX memory pool" |
| -r " monitors process registers: |
| process id" |
| |ps[.exe] " utility displays all |
| processes" |
| |vw[.exe] " VMiX pull-down menu |
| utility" |
| " : MSDOS command" |
|dosjob |
| " : MSDOS command or / VMiX command" |
| [-W] " gives process the full screen: MSDOS |
| command or / VMiX command" |
|spawn |
| -c " sets channel for STDIO and executes |
| command line" |
|kill |
| " : process id" |
|quit |
|_________________________________________________|
: indicates command parameters
[ ] indicates optional
VMiX TERMINAL - IBM FUNCTION KEY EMULATION
_________________________________________________
| |
| Press ^F (1 beep) emulation ON |
| Press ^F again (2 beeps) emulation OFF |
| |
| |
| for press |
| |
| IBM PC KEY TERMINAL KEY |
| |
| [F1] 1 |
| [F2] 2 |
| [F3] 3 |
| [F4] 4 |
| [F5] 5 |
| [F6] 6 |
| [F7] 7 |
| [F8] 8 |
| [F9] 9 |
| [F10] 10 |
| |
| <Ctrl>[Break] ^C |
| <Ctrl>[NumLock] ^S |
| <Ctrl>[F3] ~ |
| [PgUp] + |
| [PgDn] - |
| [Ins] ^I |
| [Del] ^D |
| [End] ^E |
| [Home] [Home] |
| <Alt> <Shift> |
| |
| |
| |
| NOTE: The <Ctrl> key symbol for the terminal |
| keyboard has been abbreviated as ^ |
|_________________________________________________|
