|
01. General Questions
01.01: What old-computer hardware does the SVD support and what does "support" mean?
02. General Hardware
02.01: How is the SVD connected to the floppy cable, and what do the different connectors do?
02.02: What the heck is a terminator, and why is it important?
02.03: What if I don't have a serial/RS232 port on my PC?
03. General Software
03.01: What disk image formats are supported?
03.02: There's a BUG!
10. TRS-80 Model I
10.01: What type of cable do I use for my Model I?
10.02: The original TRS-80 cable connectors look really weird...why?
11. TRS-80 Model 3 & 4
12. TRS-80 Color Computer (CoCo)
13. Heathkit H8 & H89
13.01: Can I format the floppy image in the SVD?
13.02: Can I sysgen the floppy image in the SVD?
13.03: What does the "wrong init" message mean when sysgen'ing?
13.04: HDOS 2.0 BASIC is not starting
14. Apple 2
14.01: Why is an extra board needed for SVD Apple 2 support?
14.02: How can I connect the SVD to the Apple UniDisk controller (db-19 connector)?
15. TI99/4a
15.01: What about double sided?
|
01.01: What old-computer hardware does the SVD support and what does "support" mean?
By "support" we mean two things:
- What old computer hardware will
be able to read floppy images from the SVD?
- What old filesystems are supported?
The first question refers to what old hardware you can
physically connect the SVD to, and will
allow the old machine to either boot or read from the
SVD as if it were an old floppy drive.
The second question refers to a feature of the SVD that
allows you to download a single file to the
SVD. This would allow you to, say, download a single
BASIC file and run it without having a complete floppy
image. This is done through the
PC-based SVD control software, which knows about the
file-system that is used for the target old machines.
It can add a single file to a pre-packaged OS image,
and then download that image to the SVD.
For the answer to the question of what hardware
is supported, see here.
|
02.01: How is the SVD connected to the floppy cable, and what do the different connectors do?
The SVD initially comes with two different edge-card connectors
that connect to the left-side 34-pin header of the SVD. It is
extremely important that you use one
of these connectors. Please do not try to plug a floppy cable
directly into the 34-pin header. The SVD uses one of the 34-pin
header pins to deliver +5 to the terminated connector.
The "straight through" connector is used when there is a terminated
floppy drive or another SVD physically on the floppy cable. It
includes no termination.
The "terminated" connector has a resistor network on the bottom,
and will effectively terminate the floppy buss. This should only
be used when there is no other device terminating the floppy cable.
It is always safer to try to straight through connector first.
Note, too, that the floppy or SVD with termination should be the
last device on the cable (the farthest away from the computer).
02.02: What the heck is a terminator, and why is it important?
The old-style floppy busses (at least the ones that the SVD
supports) often required the use of "termination." This
refers normally to special cable, connector, or even a special
floppy drive that had internal circuitry that would "terminate"
the floppy buss. "Termination" in these cases consists of a
set of resistors that tie certain signals to ground or to
+5 volts. Through termination the buss is kept at a known
state and noise is reduced allowing a more useful connection
between the floppy and computer.
If you don't terminate a floppy buss, it probably won't work.
That is, the computer and the floppy device won't be able to
talk to each other.
Note that the SVD comes with a special connector that includes
termination resistors on it. You should only use the terminated
connector when there is not another terminated floppy connected
to the cable. Note, too, that the terminated floppy (or SVD)
should be the last device physically on the cable.
02.03: What if I don't have a serial/RS232 port on my PC?
Well, that is indeed a problem!
The SVD only has a serial interface. This was done to
keep the cost low.
There are two solutions to this problem: (1) purchase a serial
card for your PC, or more likely (2) purchase a USB to Serial
converter. USB/Serial converters aren't too expensive and provide
a means to either add an initial serial port to your PC (or laptop) or to
expand the number of serial ports that you have. Personally, I
have used two SVD's on my laptop, each hooked to a converter.
You can find these converters many places including Radio Shack,
CompUSA, and Best Buy. Get the cheapest one you can...the SVD requires
only the very basic functionality for the serial port.
|
03.01: What disk image formats are supported?
File Extension | Common Machine | Description
| .dmk |
TRS-80 1/3/4 |
The .dmk format is quite common for TRS-80 disk images.
Originally named for its creator, David Keil, this format is
a raw image of the bytes found on a TRS-80 diskette. This includes
sector headers and such, although special clocks and bit transitions
for FM or MFM are not represented. Most copy-protected diskettes can
be represented in this format.
| .jv1 |
TRS-80 1/3/4 |
Name for its creator, Jeff Vavasour, the .jv1 format is a simple contiguous set of floppy sectors.
.jv1 is only used for single-sided single-density diskettes,
and normally only for Model I files.
| .jv1 |
TRS-80 1/3/4 |
Also named for its creator, Jeff Vavasour, the .jv3 format
includes custom header information in addition to sector data.
This allows some copy-protected images to be represented.
Double-density diskettes are often represented in this format.
| .dsk |
TRS-80 1/3/4 |
All of the above formats (.dmk, .jv1, .jv3)
can have the .dsk extension.
Fortunately, due to the very different formats, the SVD can determine
which format is in a .dsk file.
|
.jvc |
TRS-80 CoCo |
Name for its creator, Jeff Vavasour, the .jvc format
is a hybrid of a simple contiguous set of floppy sectors and
optional header information.
In most cases, there is no header information and the image
file contains 18-sector 256-byte contiguous data for 35 or 40
tracks.
| .dsk |
TRS-80 CoCo |
Often used in place of .jvc in filenames.
Unfortunately, the .dsk extension is extremely popular
and makes guessing the format of disk images problematic.
The SVD does a pretty good job of it, however.
|
.h17 |
Heathkit |
One of the original formats for Heathkit H8/H89 floppy images,
.h17 is a text-based (read "big") format that contains
a sector by sector hex dump of the data on the disk. It includes
descriptive information about the disk in the title as well.
One of the nice things about this format is that it preserves
the volume number of the diskette even if it is a CP/M diskette.
For HDOS diskettes, the volume number is elsewhere on the image.
| .h8d |
Heathkit |
The compact analog to the .h17 format is the binary
.h8d format.
This format is a binary dump of contiguous sectors from the
floppy.
It is assumed that there are 35 tracks of 10 256-byte sectors.
So the size of these files is fixed.
Note that this format is easily confused with many other binary
dump formats.
But, again, the SVD sorts things out pretty well...in this case
based upon the file extension.
|
.do |
Apple ][ |
This extension refers to DOS Ordered sectors.
The data in this type of image is that only of the sector's data.
In fact, the file is simply each sector of the diskette packed end to end.
The SVD software understands this type of file and can order the sectors
appropriately.
| .po |
Apple ][ |
This extension refers to ProDOS Ordered sectors.
The data in this type of image is that only of the sector's data.
In fact, the file is simply each sector of the diskette packed end to end.
This file type looks JUST like the .do except that the
SVD assumes a different ordering for the sectors.
| .dsk |
Apple ][ |
Often, the .dsk extension is used in place of .do.
But sometimes, it will refer to .po.
The SVD software will assume it is the same as .do,
because it can't currently descriminate between the two.
So if a .dsk won't work, try renaming it to have the .po
extension.
| .nib |
Apple ][ |
The NIBble format is made up of raw sector transitions that
would occur on the Apple diskette.
Since it is this raw format, most copy-protected disk images will use it.
The SVD software translates this image file directly to the hardware
without changes.
| .shk |
Apple ][ |
Often you will see files with the ShrinkIT extension.
The SVD software cannot handle this type of file directly.
You will need to use either a ShrinkIT utility to unpack
the file, or simply use CiderPress.
|
.v9t9 |
TI99/4a |
This format is also known by .t99 and .tidisk.
It is a binary data format with contiguous sectors.
There is no header information and it is, therefore, impossible
to distinguish between DS SD and DD SS images looking only
at the size of the file.
These files are normally 40 tracks with 9 sectors and in single density.
| .pc99 |
TI99/4a |
The .pc99 format is a raw dump of disk sector data
and includes sector header information.
| .dsk |
TI99/4a |
Both .pc99 and .v9t9 formats can be named
a .dsk file.
This often raises issues because the SVD finds it hard to
distinguish between these file formats and many others.
When using these formats, it is wise to name with an extension of something
other than .dsk.
|
|
03.02: There's a BUG!
There's a bug in the SVD CP (control program) that I can't fix.
Microsoft won't fix it either.
The problem occurs when you write/save an image out to your PC Desktop
for Windows 98/2000/Me/XP. The save of the image works just fine.
Though, normally, the extensions that are used in naming disk
image formats are no known by the operating system. This is where
the problem lies.
Let's say, now, you want to re-load that file back into
the SVD CP. You click on Load, the Browse. You navigate to the
Desktop and use your mouse to select the file you saved before.
Almost always, when the "information balloon" tries to pop-up over
the file with the unknown extension, the SVD CP will crash.
Normally, it takes two times for the balloon to pop-up for it
to happen.
Note that this isn't a problem with the SVD CP itself. ALL windows
programs will exhibit this same behavior...but only on certain
machines.
To get around this problem, don't write/save images to the Desktop.
It is that simple.
|
10.01: What type of cable do I use for my Model I?
Any 34-pin edge-card connector cable will work.
However, you have to be concerned with the following issue:
-
The TRS-80 floppy drives are "turned on" with ANY
of the floppy drive select lines on the cable.
So if you have a straight-through cable connected to more than
one existing floppy, you will have problems.
The original TRS-80 cable came with pulled-pins which
caused only one of the floppy select signals to be sent to any
particular drive...selected by the connector itself.
For more information, see the
TRS-80 Model I
section.
10.02: The original TRS-80 cable connectors look really weird...why?
The original cable came with connectors that are "keyed" to
particular drives. That is, the first connector on the cable
has "pulled pins" that causes it to select drive #0. The second
connector has pulled pins that selects drive #1 and so on.
Please see the
TRS-80 Model I
section for more information.
|
|
|
13.01: Can I format the floppy image in the SVD?
In H8/89-speak, this refers to doing an init
of the image in the SVD.
So can I do it?
Nope! The SVD emulates floppies by generating
the sector header information dynamically.
This means, however, that operations that attempt
to write out this information (like when formatting)
will not work.
In fact, they tend to confuse the crap out of the
SVD, causing you to have to re-download whatever
image you were using.
Fortunately, there is very few reasons to format
the SVD.
13.02: Can I sysgen the floppy image in the SVD?
Yup!
Although you can't init
the image in the SVD, you can
sysgen it.
What this does is copy the boot files
(along with others if you do the *.*
option) to the SVD.
This is a nice way of copying a whole
diskette.
13.03: What does the "wrong init" message mean when sysgen'ing?
This means that the image in the SVD was init'ed
with a different version of the OS.
This means that you can't use sysgen with this
image.
Unfortunately, it's a bit hard to deal with this issue.
You need have have an SVD-downloadable image with the
right init in order to sysgen
it.
Please let me know if you have run into this problem.
Maybe you can help me come up with a good solution!
13.04: HDOS 2.0 BASIC is not starting
If BASIC won't start when running the supplied HDOS 2.0 image,
you need to turn off the write-protect check-box
before downloading the HDOS image to the SVD. For some reason
BASIC requires write-access to the image.
|
14.01: Why is an extra board needed for SVD Apple 2 support?
The extra board, or dongle as it is called, converts
the Apple 2 floppy control signals to the signals used by the
"standard" 5 1/4 floppies of the day. For a bunch of information
about the dongle, see
here.
Here is a quick overview
of the signals that are converted:
Head Stepping |
The Apple 2 uses low-level stepper motor phase pulses to
manually advance the track head through the separate
tracks of the floppy. The dongle converts these phase pulses
into a direction signal and a step
pulse based upon the direction of the progression of the pulses.
In addition, the dongle ensures that the phase pulses coming from the
Apple are the appropriate width since, when booting, the Apple actually
holds the phase 0 pulse high for an extended period.
|
Signal Polarity |
The logic sense (polarity) of the Apple 2
signals are often the inverse of those for the "standard" floppy controllers.
This includes inverting the read and write lines as well as creating a
"motor_on" signal based upon the drive select signals.
|
Signal "Levels" |
Closely related to the signal polarity,
it is also necessary for the dongle to provide
for the open-collector signals used in standard floppy controller implementations.
This includes adding pull-up resistors for OC signals as well as creating
an appropriate tri-state level for the read signals going back to the
Apple controller.
|
14.02: How can I connect the SVD to the Apple UniDisk controller (db-19 connector)?
I seriously considered putting the UniDisk db-19 connector
on the SVD - or more accurately, the dongle.
However, I simply could not find an economical supply
of them. It appears that the db-19 is a connector of
the past. The 20-pin headers are far easier to come
by, and quite a bit cheaper...and you all know my mantra
relative to the SVD "the cheaper the better."
However, it is a theoretically simple matter to connect
the SVD to the UniDisk controller.
Back "in the day" there were cheap adapter cables which
were meant to connect the Disk ][ to the 2e. These
cables simply mapped the pins from the 20-pin header
to the db-19.
These cables are rather hard to come by these days too.
Here's one
place I've come across
that sells them, but check out that price-tag!
(Plese let me know if you've found another source for these
adapters or if the above link starts to fail).
If you want to create your own,
here
is a good reference.
(Here's a
local mirror if this link dies.)
Note that I have not tried to create this cable myself.
This web page looks
right. Please let me know if you try it and it works (or doesn't).
Note too, that this mechanism is intended for the Apple 2
series and controller cards for 5¼ inch drives. It does not
work for 3½ inch drives and also does not work for the Mac.
|
15.01: What about double sided?
|
|