home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
hobbes.nmsu.edu
/
2008-06-02_hobbes.nmsu.edu.zip
/
dos
/
hpfs4dos.zip
/
MANUAL.ENG
< prev
next >
Wrap
Text File
|
1995-10-10
|
14KB
|
417 lines
┌──────────────────────────────────────────────────────────────┐
│ │
│ HPFS Access │▓▓
│ Version 0.2ß │▓▓
│ │▓▓
│ by │▓▓
│ │▓▓
│ ┌─────────┐ ANDREAS KINZLER ┌─────────┐ │▓▓
│ │ FAT │──────────────────────────────»>│ HPFS │ │▓▓
│ │=======■=│ (c) 1994-95 Andreas Kinzler │=======■=│ │▓▓
│ └─────────┘<«──────────────────────────────└─────────┘ │▓▓
│ │▓▓
│ │▓▓
│ │▓▓
└──────────────────────────────────────────────────────────────┘▓▓
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
Instruction to HPFS-Access (Shareware Version)
──────────────────────────────────────────────────────────────────────
1 Introduction
What is HPFS-Access?
Shareware version and registration
Restrictions in the shareware version
Guarantee, and exclusion from liability
Hardware requirements
Software requirements
Use
What to do about questions and problems?
2 Problems and safety references
3 How HPFS-Access works
4 Appendix
Contacting the author
Acknowledgements
Trademarks
1 Introduction
──────────────────────────────────────────────────────────────────────
What is HPFS-Access?
───────────────────
HPFS-Access is a DOS (TSR) driver which allows you to access your HPFS
partitions from DOS. After installing HPFS-Access you can use under DOS
your HPFS partitions in the same way you use your FAT partitions.
An overview of the main features in HPFS-Access are the following:
- Read and writes (!!!) are supported.
- Requires only about 8 KB DOS storage.
- When UMBs are available they will be automatically used by
HPFS-Access (auto loadhigh).
- Very fast. In many cases quicker than the OS/2 HPFS driver.
- Includes a Cache. It can be write-through or write-back.
Shareware version and registration
──────────────────────────────────
This program is distributed under the shareware principle. This means
that you may test the program 30 days. If you want to further use the
program after this time frame you must become a registered user.
Unregistered use of the program at the end of the 30 days test period
is not allowed.
If you do not work alone with HPFS-Access you must buy several
licenses, as many as persons work simultaneously with HPFS-Access. For
example, if you can ensure that in a network with 10 computers only 2
persons will work with HPFS-Access, then you need to buy only 2
licenses.
You can find the registration information in file "REGISTER.eng".
Restrictions in the shareware version
────────────────────────────────────────
The driver deactivates itself after some time. The restriction in the
currente shareware version are the following:
Deactivation time: 20 minutes
Data quantity: 16 megabytes
Please, do not take advantage of these limits until the very last
second, as you could lose your data. If you are editing a file, when
the time limit is reached you will not be able to store your changes.
The same will happen when you reach the data quantity limit.
These limits do not apply to the registered version.
Guarantee, and exclusion from liability
───────────────────────────────────────
Andreas Kinzler hereby disclaims all warranties relating to this
software, whether express or implied, including without limitation
any implied warranties of merchantability or fitness for a particular
purpose. Andreas Kinzler will not be liable for any special,
incidental, consequential, indirect or similar damages due to loss
of data or any other reason, even if Andreas Kinzler has been advised
of the possibility of such damages.
The person using the software bears all risk as to the quality and
performance of the software.
DURCH DIE NUTZUNG DER VORLIEGENDEN SOFTWARE UND/ODER EINGABE DES
ZUGANGS-SCHLÜSSELS BEI DER INSTALLATION ERKLÄRT DER ANWENDER SEIN
EINVERSTÄNDNIS MIT O. G. GARANTIE- UND HAFTUNGSAUSSCHLUSS. WEITERHIN
STIMMT ER (DER ANWENDER) ZU, ANDREAS KINZLER FÜR NICHTS VERANTWORTLICH
ZU MACHEN, AUSSER DASS DIESE SOFTWARE PLATZ AUF DER DISKETTE/FESTPLATTE
BELEGT.
The entrance key is: "I AGREE" (without quotation marks)
Hardware requirements
─────────────────────
A PC with 386+ (32-bit-CPU) and at least 2 MB RAM is required.
Software requirements
─────────────────────
HPFS-Access can be used with the following DOS versions. Other DOS
versions are NOT supported.
MS-DOS 5
MS-DOS 6.0, 6.2x
DR-DOS 6
PC-DOS 6
Novell DOS 7
In addition Windows 3.1 is supported i. For this, an XMSK driver must
be installed.
Use
───
There are 4 versions of the driver.
DOS_GER.EXE (DOS version with German texts)
WIN_GER.EXE (WIN version with German texts)
DOS_ENG.EXE (DOS version with English texts)
WIN_ENG.EXE (WIN version with English texts)
The DOS versions of the driver can be used exclusively under DOS. The
Win versions can be used both under DOS and Windows 3.1.
Preparations for Windows 3.1:
If you want to use the WIN version and you also plan to start
Windows, then you must enter the 'VHPFSD.386' driver in the your
'system.ini' file.
Your SYSTEM.ini file will look as follows:
[386Enh]
...
...
device=vhpfsd.386
...
...
Please do not forget to copy the file 'VHPFSD.386' in the Windows
system list.
Installing the driver:
There are 2 possibilities.
a) Inovoke the EXE-Files without parameters
In this case HPFS-Access looks for HPFS partitions and
automatically assigns them to free DOS drive letters.
A Maximum of 4 partitions will be bound.
b) Invocation with parameters
The parameters syntax is:
EXEFILE driveletter = partitionnumber [cachesize[T/B]] [,...]
A couple of examples for clarification:
EXEFILE x=2,y=1
The 2nd HPFS partition becomes the drive letter X:
if the 1st HPFS partition is free, it gets associated to drive
letter Y:
EXEFILE l=3 1024
L: becomes associated with the 3rd HPFS partition. For this
partition a 1024 KB Cache is used
EXEFILE z=1 512t, m=3 256w
Z: becomes associated with the 1st HPFS partition. This partition
uses a 512 KB Cache. The cache mode is write-through.
M: becomes associated with the 3rd HPFS partition. The cache used
is write-back. The Cache size is 256 KB
If you wish optimal performance, then you must set the cache
size larger to at least the partition size divided by 4
megabytes.
For example, if you have an 800 megabyte partition and want you
optimal performance, then you must make the cache size for this
partition at least 200 KB large.
Uninstalling the driver:
If the driver is installed, then it can be uninstalled using the same
EXE-Files used to install it.
Please uninstall the driver with the same version used to install it
(DOS/WIN and/or GER/ENG).
What to do about questions and problems?
────────────────────────────────────────
If you cannot come through, then please try to find first the answer to
your questions and problems in this small FAQ. If you still cannot come
through, or if you still have questions, then you can contact me
through one of my network addresses.
I am pleased over inspirations and (constructive) criticism ;-)))
Q: Windows will start no more. Has that something to do with the
VHPFSD.386 driver?
A: Very unlikely. Reboot and start Windows anew. If you still cannot
come through, then remove the VHPFSD driver and try to start Windows
again (after a Reboot). If you cannot still come through, then the
error does not lie within VHPFSD. If it does not go away, then
please write down the error message and send me mail.
2 problems and safety references
──────────────────────────────────────────────────────────────────────
- Backups
Please backup before your first use of HPFS-Access, and then at
stated intervals backup your data. To be on the safe side, please
also backup FAT drives in other partitions.
- Storage managers
I recommend not to use other storage managers, as them, which were at
your DOS version thereby.
QEMM should function now.
- Installed Cache
Please you keep at the current safety precaution if you use the
Write-back-Cache.
- Other Cache programs
Use no other Cache programs with write-back.
- (E)IDE Controllers
HPFS-Access supports hard disks with more than 1024 cylinders.
Indeed the process is not standardized to this and can lead thus to
problems. EIDE Controllers must be set to NORMAL mode. The versions
I know of 'Ontrack' support not more than 1024 cylinders.
- SCSI
There should be no problems with SCSI hard disks. I use personally my
driver on a 1.2G-SCSI-HPFS-Partition. Up until now I have never had
any problems.
- DOS Taskswitcher/Multitasker
Please do not use these programs. This includes specially Novell DOS
7.
- Windows
Do not copy Windows itself on an HPFS partition.
- CHKDSK
If you leave run at stated intervals CHKDSK of OS/2. It has occurred
already that the HPFS driver of OS/2 did not leave behind a flawless
structure. HPFS-Access is very sensitive to structure errors, and
reacts accordingly.
3 How HPFS-Access works
──────────────────────────────────────────────────────────────────────
For DOS, HPFS partitions look like network drives. This protects them
from grab programs, like Defragmenters or Disk Editors. With DOS the
safest way besides this is to bind a file system driver.
Fundamentally counts, that DOS was never prepared for networks or
installable file systems. That it is altogether possible today, to
bind networks in DOS, lies in it, that one of late interfaces has
invented. At this point in time a clean solution naturally was no more
possible. Things are completely different for OS/2. Here the
possibility was anticipated from the beginning, to bind a file system.
Under OS/2 a HPFS driver has been able to imagine everything which one.
A good concept and much storage. Under DOS everything looks that
completely differently. Here storage stands hardly at the disposal.
The HPFS-Filesystem needs however several hundred Kbytes around
altogether write to be able to do. If one would take for it the
conventional storage of DOS, would run almost no program more (because
of storage defect). The problem is, that the storage is needed however,
to make possible the Schreibfähigkeiten. One could get along of course
with less, which however very at the expense of the safety would go.
Thus HPFS-Access has an installed 32-Bit-TSR-DOS/WIN-Extender. The real
driver exists to 100% of 32-Bit-Protected-Mode-Assembler.
With it the storage problem is solved. Indeed problems with
incompatible catch now storage managers at (see above). Programs,
which use a DOS-Extender (Borland Pascal, Borland C++, WATCOM C/C++),
put indeed no problem there and function flawlessly.
The linking a Caches (counts also for SMARTDRIVE,...) IF DOS is very
difficult under DOS, since also here does not make available the sure
environment for such programs. Thus you should use no other Cache
programs besides HPFS-Access, since these otherwise ungewu"nschte could
call forth side-effects. For it HPFS-Access can however neither nor
the other Cache program something.
4 Appendix
──────────────────────────────────────────────────────────────────────
Contacting the author
─────────────────────
FIDO: 2:2455/112.58
Internet: akinzler@rbg.informatik.th-darmstadt.de
Adresse: Andreas Kinzler
Albert-Schweitzer-Straße 8
55283 Nierstein
Tel.: 06133/58206 (only in extremely important cases)
Acknowledgements
────────────────
Hauke Hagenhoff. ............... Divide the instruction and beta
tests Markus Eckert. ........... Betatester
Trademarks
──────────
Them in this instruction, in the order form and by the program
mentioned Soft and hardware products as well as programs with entered
trademark are acknowledged property of their respective owners and/or
maker and become herewith.
Translation:
1) Bill Zirkle 75704,3443@compuserve.com [HPFSMANL.txt]
2) Adolfo Di Mare adimare@cariari.ucr.ac.cr [MANUAL.eng] Oct/95