I changed the software controller parameter on my Zenith Z-100 to get 96 TPI on the 5.25
inch drives. Simple change, although had to add a thin metal shield on top of drive
because of interference from monitor.
Sent from my Ohio Challenger 2P
Asteroid 2012 DA14 Earth Flyby on Feb 15, 2013. I will come close but will not hit the
earth.
See video information at:
On Wed, 13 Feb 2013, Scott Quinn wrote:
3B2s are DSQD floppies, and I'm trying to
figure out my best approach. I
have the utility software in a disk image, but PCs usually don't ship
with DSQD drives. I've found three possible options, but don't know if
anyone's used any of them (or one that I haven't come across).
You should be OK.
Depends on what you mean by "DSQD".
"THERE AIN'T NO SECH ANIMAL."
DO you mean DSDD with 96TPI? (aka "720K" (which could easily be from 640K
to 800K) Ignorant marketing people (not NECESSARILY suits) created a
ridiculous technically bogus name for that of "quad density"
OR DID YOU MEAN SOMETHING ELSE by "DSQD"?
If "720K", most "1.2M" drives can handle that. You need to switch
the
speed to 300RPM OR switch the data transfer rate of the controller to 300K,
(just like what is done for reading "360K" disks in a "1.2M" drive)
AND
not let it double step (when reading "360K" disks in a "1.2M" drive,
every
other track of the 96TPI is used to get the needed 48TPI)
OR
connect a "720K" drive to the PC.
cable it, and jumper DS, etc exactly the same as the 360K version of
that drive.
Teac 55FG is an excellent drive that is designed for both "720K" AND
"1.2M" (F is their "720K" model, G is their "1.2M"
model)
If you are NOT using a PC, but instead, some newer device, such as an AT,
you can tell the CMOS that it is 720K 3.5" OR tell it is "360K" (for
pre-3.5" ATs)
On a PC or XT (5150, 5160), the hardware doesn't know the difference
between a "360K" drive and a "720K" drive. (Although MS-DOS, to
select
WHICH MS-DOS format it expects, wants DRIVER.SYS or DRIVPARM)
THE BEST reason for keeping a 5160!
OR
use a "720K" 3.5" in the 3B2
no idea about special jumpering, etc.
("1.4M" would actually probably work, but further compound jumpering
issues due to density select)
NOTE: the commonly used format is 1.406M (80 * 2 * 9 * 512), and you
CAN NOT GET 1.44M unless you REALLY create a bizarre UNIQUE format,
OR misdefine a megabyte to be 2^10 * 10^3 (which nobody outside of
marketing would knowingly do!)
NOTE: I am forced to refer to drive types by their grossly inaccurate
popular names, since otherwise I need an entire line of text to identify
the drive and format type,
"Industry standard 5.25" 96 track per inch using MFM, at 300RPM with
a 250K data transfer rate, or at 360RPM with a 300K data transfer rate"
or would need to use the nonstandardized IBM drive type
names of "type 0", "type 1", "type 2", "type 7",
etc.
Isn't "720K" understandable and simpler?
USUALLY, when people say "quad density", they are referring to DSDD with
96TPI.
BUT NOT ALWAYS. THERE REALLY ISN'T ANY SUCH THING AS "QUAD DENSITY".
For example, when Superbrain (Intertec) went to DOUBLE SIDED on their
DOUBLE DENSITY disks, (doubling the capacity from ~180K to ~360K),
(which the entire civilized world called "DOUBLE DENSITY"),
they called THAT "Quad Density" ("QD")!
When Superbrain (Intertec) went to 80 tracks (96tpi V 48tpi) on THEIR
"QUAD DENSITY" (increasing the capacity from ~360K to ~720K, which
MARKETING of most other companies called "quad density"), they had
to follow the lead of olive size names, and called them "SUPER DENSITY"!!
They abbreviated THAT "SD", which everybody in the civilized world knows
to be "single density".