home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-387-Vol-3of3.iso
/
o
/
os2_util.zip
/
SUBSTP.ZIP
/
SUBSTP.DOC
< prev
Wrap
Text File
|
1992-03-07
|
9KB
|
195 lines
SUBST for OS/2, Version 0.01, Sat 03-07-1992
---------------------------------------------
Bugfixes:
- Version 0.00 would only allow a dozen or so files to be opened at
the same time. This caused problems with programs such as
QuickHelp, which leaves open many files. This version will allow
approximately 500 files to be open at the same time.
- Long file names were not supported for all APIs (oops!). This
has been fixed.
Features:
- OS/2 2.00 support. Only beta version 6.304 of OS/2 2.00 has
been tested.
Packing list:
Substp.doc - This document
sub_120.LZH - Subst IFS kit for OS/2 1.2, 1.3.
sub_200.LZH - Subst IFS kit for OS/2 2.00
qdisk.exe - A simple command line utility which tells you which
file system is attached to each drive letter.
SUBST for OS/2, Version 0.00, Tue 04-30-1991
---------------------------------------------
This program was written as an exercise to learn about IFS's
(Installable File Systems). It provides the same function as the
old DOS command: SUBST. It is not a considered a completed
product, and may not be of the same quality as other A:WARE Inc.
products. Although it is the property of A:WARE Inc, there is no
charge for the use of this program.
The program is broken into four parts:
SUBSTFSD.IFS -- The FSD (File System Driver) which must be
installed in CONFIG.SYS with the IFS= statement.
USUBST.DLL -- This is provided to conform to the IFS
specification. Each FSD is supposed to supply a
DLL that is named "U<file system name>.DLL", to
support CHKDSK, FORMAT, etc. UHPFS.DLL and
ULAN.DLL are other examples.
USUBST.DLL simply prints a message saying that "The
SUBST file system does not support the XXXXX
command." It is not a required part of the SUBST
system. You can loose it if you want. :-).
SUBSTHST.EXE -- The file system host program, which must be
running at all times to use SUBSTituted drives. It
can be started in one of three ways:
1) RUN=SUBSTHST.EXE in config.sys
2) DETACH SUBSTHST
3) START SUBSTHST
The third method will allow you to see any messages
the program may display. Starting it with the /v
(verbose) switch causes it to print out a LOT of
information (this also causes it to run more
slowly). If you experience a problem, running it
with the /v switch may help discover where the
problem is.
This program may be terminated at any time (with
^C, for example) and restarted. When it
terminates, it automatically detaches all of the
drives attached to it.
SUBSTP.EXE -- The program you use to do the substitutions
(attaches). It has the same syntax as the DOS SUBST
command:
┌─────────────────────────────────────────────────────────────────────────────┐
│substp [[drive1: drive2:path]|[drive1: /d]] │
│ │
│Temporarily substitutes a drive letter for another drive letter and │
│directory path. While a substitution is in effect, MS OS/2 regards any │
│reference to drive1 as a reference to drive2:path. │
│ │
│Parameters Description │
│ ─────────────────────────────────────────────────────────────────────────── │
│drive1: Specifies the drive letter you want to substitute for a │
│ directory on drive2. │
│ │
│drive2:path Specifies the drive and path of the directory for which you │
│ want to substitute drive1. │
│ │
│/d Deletes an existing substitution. You must specify drive1 to │
│ identify which substitution is to be deleted, but you must not │
│ specify drive2:path with the /d option. │
│ │
│Comments │
│ │
│If you type subst by itself, the utility displays the substitutions │
│currently in effect. │
│ │
│The following utilities do not work on a drive you have substituted for a │
│directory on another drive: │
│ │
│ backup │
│ chkdsk │
│ diskcomp │
│ diskcopy │
│ fdisk │
│ format │
│ label │
│ recover │
│ restore │
└─────────────────────────────────────────────────────────────────────────────┘
Caveats:
--------
DosFindNotifyFirst(), DosFindNotifyNext() and DosFindNotifyClose()
are not supported. These functions are not yet documented by IBM
or MS, but perhaps they will be soon.
Direct disk access via DosDevIOCtl() is not supported. It doesn't
really make sense to support it.
A SUBSTed drive has all of the properties and limitations of a LAN
drive; in fact, OS/2 thinks it is a "remote" drive.
Do not try to use a drive letter that is already being used by the
DOS BOX subst command. This will probably cause a system crash.
Instead, use only this program -- although the DOS BOX can't run
SUBSTP.EXE, it DOES have access to all of the drives SUBSTed by an
OS/2 session.
DISCLAIMER
----------
The Program is supplied "AS IS" without any warranty of any kind,
either expressed or implied, including, but not limited to, the
implied warranties of merchantabilty and fitness for a particular
purpose.
In no event shall A:WARE INC be liable for any damages, either
direct or consequential, caused by the use, or inability to use,
this program, even if A:WARE INC has been advised of the
possibility of such damages.
WARRANTY
--------
This program has no warranty. It is a completely unsupported
product. Bug reports/suggestions will be listened to, but not
necessarily acted upon.
--------
The FSD code runs in "kernel protect mode" (ring 0). If there is a
bug in it, you'll get the dreaded register dump and "The system
detected an internal processing error at xxxx:yyyy. The system is
stopped". Only one code segment is used by this FSD, so it will
be easy to find out if this program is to blame if your system
crashes. If the CS register is equal to the value that
SUBSTHST.EXE displays when it is first started, then SUBSTFSD.IFS
caused the crash. Note that the CS value is displayed in the
register dump, NOT in the 'xxxx' in the message "The system
detected an internal processing error at xxxx:yyyy."
Neither of the two *.EXE programs supplied are capable of crashing
the system, since they run at Ring 3.
Performance
-----------
Using a SUBSTed drive is slower than using one that isn't. For most
programs, you probably won't notice. If you were to write a bench
test that very rapidly opened and closed a file 500 times, then you
might notice the difference.
--------
Copyright (C) 1991 A:WARE Inc.
A:WARE Inc. develops custom OS/2 applications, device drivers, and
utilities.
Peter Fitzsimmons
A:WARE Inc.
P.O. Box 670
Adelaide St Postal Stn.
Toronto, Canada
M5C 2J8.
Voice: (416)858-3222
FidoNet: 1:250/628
BBS: RT-LAB (416)867-9663