home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DOS/V Power Report 1999 May
/
VPR9905A.BIN
/
DRIVER
/
TEKRAM
/
DC390FU
/
DOS
/
README.DOS
< prev
next >
Wrap
Text File
|
1996-12-09
|
4KB
|
81 lines
< ABOUT Version 1.80 TFDISK.EXE and TRMDISK.SYS >
The TFDISK.EXE and TRMDISK.SYS are modified to support non-512 bytes/sector
media to be compatible with WIN95 and Windows-NT. Previous versions using
512 bytes/sector emulation method to access the media are not compatible with
WIN95 or Windows-NT and would result in media exchange problem.
To have the best compability, the SUPER FLOPPY format* is recommended to be
compatible across DOS/Windows/WIN95/Windows-NT!
(* SUPER FLOPPY format: means no partition table for removable media. The
entired media would be treated as one large-capacity floppy disk. *)
The new driver will accept ALL WIN95/Windows-NT format, either SUPER FLOPPY or
partition based formatted.
However, WIN95 will NOT recognize Windows-NT's partition based format.
< Options for TFDISK.EXE and TRMDISK.SYS >
1. TFDISK.EXE
/emu Using 512 bytes/sector emulation method to handle media with
1024 or 2048 bytes/sector. This method must be used with
/e option of TRMDISK.SYS, i.e., "TRMDISK.SYS /e".
2. TRMDISK.SYS
/e Using 512 bytes/sector emulation method. This method must be
used with /emu option of TFDISK.EXE, i.e., "TFDISK.EXE /emu".
/q Bypass Read Verify command to speed up FORMAT speed. It is
useful when user is testing functions of driver.
/d n1 n2 n3 ...
n1 = Reserved logical drive for 1st removable media
n2 = Reserved logical drive for 2nd removable media
...
...
* 512 bytes/sector emulation method: is used to handle 512, 1024, &
2048 bytes/sector media with 512B/sec BPB (BIOS Parameter Block) under
DOS/Windows. For Win 95 & NT, there are three BPBs that handle 512, 1024, &
2048 B/sec, respectively and don't use this emulation method.
- under DOS/Win 3.1x: would only see 512 bytes/sector &
- under Win 95/NT : can recoginze 512/1024/2048 bytes/sector via 3 different
BPBs
=> have problem with media change under DOS/Windows: try this emulation method
(The previous version of driver uses this emulation method and some other
control cards may be, too.)
=> media change between DOS/Windows & Win 95/NT: don't run with this emulation
method, i.e., don't add /emu & /e options for TFDISK.EXE & TRMDISK.SYS
<V1.81 TRMDISK.SYS>
==> Add a switch to exclude TRMDISK.SYS's control over some removable media
e.g. DEVICE=c:\DC390\TRMDISK.SYS /x=3
/x=3: The TRMDISK.SYS DO NOT control the SCSI device at SCSI ID=3
==> The /x= syntax is as follows:
e.g., TRMDISK.SYS /x=1,4,c,d (devices of SCSI ID=1, 4, 12, 13 are not
controlled via TRMDISK.SYS)
* No space or tab is allowed between each ID
* The possible SCSI IDs = 0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f
==> When to use this switch:
Example =>
SCSI ID 0 = Fixed disk (controlled by BIOS INT13)
SCSI ID 2 = Removable MO device (controlled by Removable Disk driver)
SCSI ID 4 = IOMEGA JAZ removable device (controlled by Removable Disk driver)
Since IOMEGA has its own device driver for JAZ device and its utility
requires its device driver to be installed, the TRMDISK.SYS should
then control the removable MO only and EXCULDE the IOMEGA JAZZ device.
So, the configuration file ( CONFIG.SYS ) may be as follows:
DEVICE=c:\DC390\ASPI.SYS --> TRM ASPI driver
DEVICE=c:\DC390\TRMDISK.SYS /x=4 --> TRMDISK only controls SCSI ID2
DEVICE=c:\IOMEGA\SCSICFG.EXE /V --> IOMEGA SCSI configuration S/W
DEVICE=c:\IOMEGA\SCSIDRVR.SYS --> IOMEGA driver controls SCSI ID4