Date: Mon, 9 Sep 2002 12:38:06 -0700 (PDT)
From: David Chien <[EMAIL PROTECTED]>
Subject: Re: [LIB] Libretto 100CT Cardbus controller

Given that someone is the Usenet newsgroups has already replied re: the FAT32 &
DR-DOS issue, here's their reply (search www.deja.com for more answers):

(Oh, and had too much fun downloading all the latest DOS program releases here:
Lots of freeware, interesting DOS programs)
http://www.opus.co.tt/dave/

=====
with CONFIG.SYS containing only DEVICE=HIMEM.SYS and DOS=HIGH, free
conventional memory reported by MEM.EXE is:

                No CONFIG.SYS or                 w/ CONFIG.SYS
                AUTOEXEC.BAT            & no AUTOEXEC
DR-DOS 7.03             583K                            620K
PC DOS 2000             576K                            620K
PC DOS 6.1              575K                            619K
PC DOS 5                575K                            619K
M$DOS 6.22              574K                            619K
M$DOS 7.1               548K                            610K
=====

From: Matthias Paul ([EMAIL PROTECTED])
Subject: Re: DR-DOS and FAT32 - newbie question
Newsgroups: alt.os.free-dos
View: Complete Thread (13 articles) | Original Format
Date: 2002-06-28 05:48:29 PST

On 2002-06-26, David Raleigh Arnold wrote:

>> I have found a file DRFAT32.zip on the net, and it contains just
>> drfat32.exe and drfat32.sys - no readme for newbies like me.
>>
>> What on earth do I do with them to make them work?!
>
> drfat32.exe is probably a sez, self-extracting zipfile.  You
> may have the necessary docs right there.  :-)

There is no documentation because DRFAT32.SYS + DRFAT32.EXE was
a solution for OEM use (for example for virus scanning and disk
maintenance), and as such it was used by Ontrack's Easy Recovery 4.
It was not intended for use by normal end users on desktop systems.

DRFAT32.SYS is a special device driver which should be loaded
in [D]CONFIG.SYS. This driver talks to the INT 13h interface of
the System BIOS in order to communicate with the disk. You can
control the behaviour of DRFAT32.SYS by a multitude of command
line options. If you specify an invalid option, it will even
display a help screen (shortened):

|DEVICE[HIGH] = DRFAT32.SYS [/Options]
|
|  /A           assume more than 1024 cylinders and less than 64 heads
|  /B           allow client sided asynchronous read/write buffering
|  /C           search for CHS FAT32 partition (ID 0Bh)
|  /D:devname   device driver name up to 8 chars (default: FAT32XXX)
|  /E[:number]  search for logical drive in ext. partition (1..255)
|  /F           force override of (some) sanity checks
|  /G           save guard by blocking write access on faults
|  /H           search for hidden FAT32/FAT32X partition (IDs 1Bh/1Ch)
|  /L           search for LBA FAT32X partition (ID 0Ch)
|  /M           always signal media change for removable drive
|  /N           relative sectors in logical drive chain are absolute
|  /O           try to use CHS addressing even for LBA partitions
|  /P[:number]  search for primary partition (number = 1..4)
|  /R           disable write access via driver
|  /S[:number]  use CHS multi sector access in /A mode (0,2,4,8,16)
|  /U:min[,max] search on drive unit min to max (min, max = 128..255)
|  /V[:level]   display verbose messages (level = 1..2)
|  /W           force write with verify (default: system setting)
|  /X           use LBA entries and addressing even for CHS partitions

Without overriding options, the driver will log-in the first eight
matching FAT32 partitions found in a system by successively scanning
each drive unit for CHS / LBA (and hidden CHS / LBA), primary
partitions / logical drives. If you'd have more FAT32 partitions,
you would have to load multiple instances of DRFAT32.SYS and use
the /D:name option to change the name of the subsequently loaded
drivers to something else but the default "FAT32XXX".

In most cases, you don't need to specify any options at all.
However, in case DRFAT32.SYS would bail out with error messages
you may be able to change the interpretation of the geometry
data or the access method or even override some of the sanity
checks by trying various combinations of options like /X, /O,
and /F. In rare cases you may also need /A or /N, and there are
also a few cases, where DRFAT32.SYS will refuse to work with
a given FAT32 partition at all.

However, loading DRFAT32.SYS is only one part of FAT32 support.
DRFAT32.SYS provides a special device driver with a default name
of "FAT32XXX" (see MEM /AP) for other drivers to interface with.
Since it was a requirement for DRFAT32 to run with *any* DOS 3.3+
(or DR DOS 5.0+), there is no provision in the DOS kernel to
handle a FAT32 volume, on which the DRFAT32 solution could build.

Hence, an external filesystem driver is required for FAT32 support.
This is provided by the redirector driver DRFAT32.EXE, which gets
loaded in AUTOEXEC.BAT. By default DRFAT32.EXE tries to communicate
with a driver named name "FAT32XXX", but the name can be changed
using option /D:name (in case, multiple instances of DRFAT32.SYS
were loaded, you can repeat the /D:name option accordingly). Here's
an overview on DRFAT32.EXE command line options (shortened):

|DRFAT32 R1.00  Redirector Extension for FAT32 Partitions
|Copyright (c) 1997,1998 Caldera, Inc.  All rights reserved.
|
|DRFAT32 [/Help][/D:driver...][/F:files][/L:letter][/M:buffers][/V]
|
|  /D:driver   name of FAT32 installable device driver(s) (FAT32XXX)
|  /F:value    number of file handles to allocate (5..99, <20>)
|  /L:drive    specifies start drive letter (default: 1st unused)
|  /M:value    number of buffers to allocate (1..64, <48>)
|  /V          print out debug information during initialization

As you see, this works very similar to the method used to install
CD-ROM support in DOS.
Of course, there are differences, NWCDEX or MSCDEX provide ISO 9660
and High Sierra file system support, not FAT32. And while the
hardware specific CD-ROM device drivers are also special CD-ROM
specific extensions of character device drivers, the internal
commands understood by DRFAT32.SYS differ from those understood
by CD-ROM drivers like ATAPI.SYS (for details see RBIL).
But keeping in mind how you install CD-ROM drivers may help
you to understand how DRFAT32 works in general.

However, there are several limitations which will render DRFAT32
useless in most situations for permanent use of FAT32 drives on
desktop systems (it just wasn't designed for this purpose):

- DRFAT32.SYS + DRFAT32.EXE consume much memory
  (DPMS and EMS support is disabled in the public version)
- You cannot boot off a FAT32 drive
- The order of the drive letters changes
- You cannot use normal FAT32 enabled low-level disk tools to
  repair FAT32 volumes mounted with DRFAT32. This is due to
  limitations of the redirector interface.

One of the advantage is that DRFAT32 works on virtually any
non-FAT32-enabled DOS system.

For use on desktop systems, I recommend to either *not* use
FAT32 partitions at all (or at least not on the boot drive),
or use a DOS implementation which supports FAT32 natively,
not one based on external drivers.

For example, OEM DR-DOS 7.04/7.05 natively supports FAT32
and LBA without external drivers such as DRFAT32, but
unfortunately this OEM version has a few other shortcomings
which doesn't make it really useable on desktop systems as
well (see http://www.drdos.org) and it doesn't look, as if
they will be fixed in public versions so soon.

If you just want to use DR-DOS with disks larger than 8 Gb,
there are other options of peaceful coexistance with LBA-
enabled OSes without a need for FAT32. One possible solution
is the use of the "secured" extended partition type C5h
instead of the normal 05h type, and combine the C5h type
with a LBA-enabled extended partition type 0Fh. This will
give you up to 8 Gb per disk to be used by DR-DOS without
sacrificing the remainder of the disk for LBA-enabled systems.

Another "unofficial" option (which will only work if you do
*not* have any FAT32 partitions) is to combine the OEM DR-DOS
7.04/7.05 IBMBIO.COM with the DR-DOS 7.03 IBMDOS.COM. This
will give DR-DOS 7.03 LBA capabilities, but you should avoid
FAT32 then, because the DR-DOS 7.03 BDOS (IBMDOS.COM) does
not know how to handle it. See http://www.drdos.org for details.

FreeDOS (http://www.freedos.org) meanwhile supports FAT32
as well, and it is actively being worked on. However, FreeDOS
is still in Beta and at the present stage not as mature and
compatible as DR-DOS is in general. However, this may change
in the future, and it shouldn't matter here anyway, as this is
mainly a FreeDOS forum, so I suggest to try out FreeDOS as well.

I think, there are also FAT32 enabled DOS implementations
available from PTS and Datalight, but I haven't tried them.

And, of course, you could upgrade from Windows ME to Windows 98SE
(IMHO the most stable version in the Windows 9x series, if you
apply the upgrades to it). This would give you much more complete
DOS and Windows support than the crippled ME does. Always keep in
mind that higher version numbers do not necessarily mean "better".

Hope it helps,

 Matthias

--
<mailto:[EMAIL PROTECTED]>; <mailto:[EMAIL PROTECTED]>
http://www.uni-bonn.de/~uzs180/mpdokeng.html; http://mpaul.drdos.org

"Programs are poems for computers."

===========

From: Matthias Paul ([EMAIL PROTECTED])
Subject: Re: Fat 32
Newsgroups: comp.os.geos.misc
View: Complete Thread (8 articles) | Original Format
Date: 2002-03-11 13:18:34 PST

On 2002-03-08, Jens-Michael Gross wrote:

> ZIP drives are implemented as block drivers. Fat32 isn't, and also
> CDrom isn't, btu for CDrom there is a separate driver and for normal
> network drivers there is too.

Well, in MS-DOS 7.10+ and OEM DR-DOS 7.04/7.05, FAT32 is supported
natively, so FAT32 drives are actually implemented as block
device driver. Some of the internal structures are different
from the structures in previous DOS issues - depending on which
information is used by NDO/GEOS, this may or may not work.
(I haven�t found the time to sort out the partial mess of drive
letter icon assignments used by NDO 3.2A on my system, but with
around 40 different partitions arranged in a special way for OS
testage it is a real stress-test for most OSes... ;-) I think,
however, NDO 3.2A did access at least some FAT32 partitions
under MS-DOS 7.10 correctly. I don�t have files larger than
2 Gb on them, though...) The INT 21h interface has not changed
very much, but there are a number of subtle differences and a
bunch of new functions.

Wolfgang, does NDO see your FAT32 drives correctly, when
you start it in plain MS-DOS 7.10 (no Windows 4.xx GUI)?

While DR-DOS 7.04/7.05 also supports FAT32 natively, it still
uses the old internal structures. This is not 100% compatible
with what MS-DOS 7.10 does, but the advantage is that most
old applications will continue to work, while many of the
older low-level tools will refuse to run under MS-DOS 7.10+.
Would the OEM DR-DOS 7.04/7.05 not have an annoying bug in
the rename function and would show a few other peculiarities
(as a result of the fact that it was not meant to be used on
desktop systems), it would preferable over using the external
DRFAT32 driver. I have not tried, but I assume, that NDO would
work fine under this kernel version.
Unfortunately, the issue of DRFAT32 1.00 which is floating around
has EMS and DPMS disabled, so it really is a memory hog and given
NDO�s conventional memory problems, it is not very advisable to
use this combination other than for testing (or with a DRFAT32
issue which has EMS and DPMS support enabled). Also, redirector
drives cannot be cached, this and the design on the FAT32 file
system as is, makes FAT32 access through DRFAT32 very slow.
A special disk cache is needed to support FAT32, while due to
its internal backward-compatible design OEM DR-DOS 7.04/7.05 FAT32
volumes can be cached with the normal DR-DOS 7.03 NWCACHE.

====
http://www.paragon-gmbh.com/n_dos.htm

PTS DOS 2000 Pro is a powerful and fast DOS developed by Paragon Software.
It comes with: a simple graphical DOS Navigator; with FAT32, big hard drive,
and CD-ROM support; Partition Manager Easy to partition hard drives; DOS Drive
Backup to create hard drive images; and other important components.
PTS DOS 2000 Pro includes source-code.
PTS DOS includes several add-on components.� Internal BootManager, providing
"friendly" coexistence with other DOS's & OS's.

    * Supports big hard drives (> 8GB).
    * FAT32 Special version.
    * Paragon Partition Manager Easy to partition hard drive. (Easy version
does not resize partitions!)
    * DOS Drive Backup to create a backup image of a partition or hard drive.
    * Simple utilities.
    * Built-in CD support for CD-ROM drives .
    * Special versions: Boot-It , Industrial DOS, FAT32 version.
    * Dynamic data compression system DATACOMP.
    * Source code.


=====
adorable toshiba libretto
The latest news and information for the Toshiba Libretto owner.
http://www.silverace.com/libretto/

__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com



**************************************************************
http://libretto.basiclink.com - Libretto mailing list
http://www.silverace.com/libretto/ - Archives

                 -------TO UNSUBSCRIBE-------
Reply to any of the list messages. The reply mail should be
addressed to: [EMAIL PROTECTED] - Then replace any text
on the message's subject line: cmd:unsubscribe
              --------TO UNSUBSCRIBE DIGEST------
Do above but with this on subject line: cmd:unsubscribe digest
**************************************************************


Reply via email to