kaldis@traffic.rutgers.edu (Theodore A. Kaldis) (05/14/88)
Fellas, I wish I could tell you! But it is a secret to me, too. I
have an acquaintance with an AT clone, equipped with a 1.2 Meg. drive,
a 360K, and an 80 Meg. Seagate with Speedstor. When he first
installed the 80 Meg., he couldn't get it to work for nothing. He
kept having one problem after another, removing one or the other
floppy, configuring the 1.2 Meg. as a 360, where it would work as a
360, or taking one or the other Floppy out, and the system would work.
The floppy drives were Toshiba's. Finally, he replaced the 360K with
a Qume drive, and the whole system worked fine. For some reason or
another, Toshiba drives wouldn't work with Speedstor.
Also, some later clone BIOS's support 720K and 1.44 Meg. floppies,
eliminating the need for DRIVER.SYS (or DRIVPARM for DOS 3.2). I have
and AWARD BIOS in an AT clone which does, and also has a built-in
setup program. I don't know whether it is legally possible (and I
won't do it if it isn't), but I have an EPROM burner and have the
capability of duplicating the chips for you.
As far as the 720 K Toshiba goes, I once installed one in an EPSON, as
drive A: no less, without any apparent problems. They were using DOS
3.2, and I used the DRIVPARM command in the CONFIG.SYS.
The proper parameter flags for either DRIVPARM or DRIVER.SYS are, for
a 720K: /D:n /F:2 /H:2 /T:80 /S:9
and for a 1.44 Meg (DOS 3.3 only?): /D:n /F:7 /H:2 /T:80 /S:16
where n is 0 for drive A:, and 1 for drive B:.
--
----------------------------------------------------------------------------
Theodore A. Kaldis | kaldis@remus.rutgers.edu
P.O. Box #1212 | {...}!rutgers!remus.rutgers.edu!kaldis
Woodbridge, NJ 07095 | (201) 283-4855 (voice)
----------------------------------------------------------------------------wew@naucse.UUCP (Bill Wilson) (05/21/88)
I have an acquiantance that is having a problem with their machine.
They have installed a 1.44 Meg Toshiba 3.5" drive in an AT clone
with Phoenix 3.1 BIOS and are using MS-DOS 3.3. When they use
DRIVER.SYS and try to format the drive, no matter what they do
they receive an INVALID PARAMETER error message. If they install
it as a 1.2 Meg device and do not use DRIVER.SYS it formats fine
as a 1.2 Meg device which isn't quite up to par.
Question: Has anyone had this problem and what is the fix?
--
Bill Wilson (Bitnet: ucc2wew@nauvm)
Northern AZ Univ
Flagstaff, AZ 86011
{These views are mine and do not necessarily reflect those of my employer}leonard@bucket.UUCP (Leonard Erickson) (05/25/88)
In article <718@naucse.UUCP> wew@naucse.UUCP (Bill Wilson) writes:
<
<I have an acquiantance that is having a problem with their machine.
<They have installed a 1.44 Meg Toshiba 3.5" drive in an AT clone
<with Phoenix 3.1 BIOS and are using MS-DOS 3.3. When they use
<DRIVER.SYS and try to format the drive, no matter what they do
<they receive an INVALID PARAMETER error message. If they install
<it as a 1.2 Meg device and do not use DRIVER.SYS it formats fine
<as a 1.2 Meg device which isn't quite up to par.
<
<Question: Has anyone had this problem and what is the fix?
I've just "solved" a similar problem. I have 720k Toshiba 3.5"
driive. I'd been unable to get it to format or write disks on
my XT clone. Today, I swapped it with a Teac. The Teac worked
the first time.
What's really annoying is that the Toshiba drive will write and
format quite happily if I stick it in my old 8-bit system....
I hope someone can tell us what's going on. The TEAC is a
35FD. The Toshiba is a FDD 4403A0K13 D02. Both have the jumpers
set "correctly". <sigh>
--
Leonard Erickson ...!tektronix!reed!percival!bucket!leonard
CIS: [70465,203]
"I used to be a hacker. Now I'm a 'microcomputer specialist'.
You know... I'd rather be a hacker."