




#2   213 08 Feb 86  18:05:32  
From: John Wager
To:   Sysop
Subj: SASI, etc.

I shared info. on sasi with several members of the Chicago area
PCjr users group (which ow has 210+ members!!!) and we are all
interested; do you have any flyers or 'hardcopy' that I could
take to the next meeting (Mar. 11)? If so, send to:
John Wager, Triton College, 2000 5th Ave. River Grove, Il. 60171.
If not, I will share new files found here on it.  Also glad to
see that someone has already uploaded batch patch to BAISICA to
run on expanded memory junior.  It works fine; almost a necessity
if you have more than 256K memory and want basic, but the EASIEST
way to deal with the out of memory problem is still just to rename
BASICA.COM something like BASICAJR.COM; it will then run on expanded
memory junior, as long as you still have your basic cartridge
inserted.  Also, regarding message #27 about how 'easy' it would be
to replace the 8088 if it goes, my system board has the 8088 soldered
DIRECTLY to the board, no socket!! If you are contemplating 'upgrading'
to NEC chip, make sure your system board has a socket under your 8088
first!!  I really like this board; I have been on LOTS of jr boards
lately and this one really looks promising.  I'll help all I can.




#4   112 27 May 86  23:33:37  (RECV'D) 
From: Mike Dougherty
To:   Jim Arroyo
SEE ALSO #5
Subj: One shot...

Hi Jim,

I'm not on the BBS that often but I thought I'd check to see how things
were going.  I've read your letter to Jon (or Henry).  I've got a couple
of suggestion and questions in connection with your problem.

First, are you using the latest JRSASI software release.  The second
item concerns the one shot.  The RC timing is set for approximately
6 microseconds.  The idea behind the one shot is to extend the CPU
I/O read or write cycle on a SASI data bus read or write operation
if the situation ever arises where the CPU got ahead of SASI controller.
If the CPU gets ahead of the SASI controller, the CPU will attempt to
read or write the data to the SASI bus before the controller is ready to
send or receive it.  The one shot will deassert the 8088 RDY line for
up to 6 microseconds.  If the one-shot times out the RDY line will
be reasserted, the I/O operation will complete, but the data will not
have been transferred.  The main idea is to sync up the 8088 with the
SASI bus but making sure not to lock up the CPU (waiting for non-existant data 
transfers).  The end result: you may want to try
changing the value of the 10K resistor used on the one shot to something
like 100K (60 us) or 1 meg (600 us) [I believe the RC is linear in this
case].  The problem where you must send out 7 bytes instead of six
sounds like a timeout on the one shot.

A third item, as I mentioned in SDUTIL.DOC, the 220/330 ohm termination
is more that absolutely required.  Without the termination resistors,
the REQ and ACK lines will slowly deassert themselves due to the
open collector drivers (7438) which would also present the same type
symptoms (7 bytes vs 6 bytes).  Also, 74LS38 due not output as much
current as the 7438 which is required to drive 220/330 ohm terminators.
So I hope you've got 7438 and not 74LS38s on your board.

A third item, check the GND connection between the SASI controller
and the JRSASI interface board.  You can do this by using a volt meter
and checking that the +5 reading is same using a GND on the JRSASI board
and a GND on the SASI controller (still measuring the +5 level on the
JRSASI board).  [that may have not been too clear - my strong point
has never been grammar].

And as a last item, check that the voltage levels are as close as can
be to +5 and +12 on the SASI controller and drive.  In my past work
with SASI controller and drives I have seen more problems attributed
to incorrect voltage levels than any other failure.

Well, that's all I can offer for now.  I'll be back sometime this week.
Good luck.



#5   109 03 Jun 86  21:19:30  (RECV'D) 
From: Jim Arroyo
To:   Mike Dougherty
REPLY TO #4   SEE ALSO #7
Subj: F.A.T. problem...

Thank you Mike for the tips. I've come a little ways since my last request for 
help.  The SASI board seams to be working now.  I was trouble shooting the 
REQ/ACK circuits using a logic/pulse type probe and found while running an 
automated version of the DEBUG routine (written in BASIC)  that the second 
byte of issue drive characteristics and the third byte of the eight bytes 
going to the controller resulted in no REQ response on the input side of the 
74LS04 but when I placed the probe on the output side of the 74LS04 each byte 
gave a REQ pulse and the whole DEBUG routine worked fine.  That is strange!! 
This may sound strange but then 
I placed a .1 micro farad cap between pin 12 and ground and got the same 
positive results.  I was very happy to see this and only hope I haven't 
addressed a symptom.  I proceeded to set up the disk using SDUTIL.  Everything 
worked great.  There weren't even any errors in the multipule writes and 
reads. For the 20 meg Seagate ST225 I issued the values: DOS INITIALIZATION- 1 
(0), 2 (615), 3 (4), 4 (400), 5 (300), 6 (8) this is the Shugart 1610-3f, 7 
(0), 8 (17), 9 (512), 10 (4), 11 (2),
12 (1), 13 (256), 14 (0), 15 (41820), 16 (41).  I set up DEVICE=SASI.COM
and BUFFERS=24 and FILES=24 and restarted the harddisk and rebooted the 
system.  I was able to access drive C:.  My new problem is the FAT is being 
altered.  I'm getting cluster errors, truncated files and a whole bunch of 
ugly things that CHKDSK tells me.
Is it true that when  addressing more than 4080 clusters we need a 16-bit FAT. 
  I'm only getting a 12-bit FAT.
Any help on this would greatly reduce my hair loss.  (I'm using DOS 2.1
have only attempted to load a few files on the disk and also I'm using 
version 1.2 of SDUTIL)
                                  Thanks again,
                                        Jim Arroyo




#6   117 04 Jun 86  00:58:07  (RECV'D) 
From: Jon Kosmoski
To:   Jim Arroyo
Subj: FAT trashing

Hi Jim
Allow me to answer for Mike since you are on the ragged edge of getting this 
thing to work perfectly (and it's gonna) and Mike is not on the BBS that often 
these days.
 
This information comes from Mike although he could probably explain it a bit 
better than me.  You are exactly right about what is happening to your FAT.  
It turns out we screwed up and only just recently discovered the error.  We 
were looking at DOS 3.1 documentation and decided that 12 or 16 bit cluster 
pointers were used according to the total number of sectors involved.  And 
this is correct.  DOS 3.1 uses 12 bit FAT entries if the disk has less that 
20704 sectors (<= 10 Meg) and uses 16 bit entries if the disk is larger than 
10 Meg.  DOS 2.1 on the other hand uses only 12 bit FAT entries.  12 bit FAT 
entries can accomodate only 4096 clusters.  If you are using 4 sectors per 
cluster then the FAT can only keep track of 4096 * 4 * 512 or 8 Megabytes.  
There are two solutions.  The first is to switch to DOS 3.1 which supports the 
16 bit FAT entries.  This is the solution I'd choose since I have heard of 
many other bug fixes and enhancements that make 3.1 a lot better than 2.1.  I 
use only 3.1 these days and have yet to find fault with it.
If you would rather stay with 2.1, then you must increase the number of 
sectors per cluster to a value such that all the available sectors can be kept 
track of by the 4096 12 bit FAT entries.  8 sectors per cluster for a 10 meg 
and 16 sectors per cluster for a 20 meg should do it.,  Well, good luck.  I 
hope this helped.  Let me or Mike know.
Jon




#7   113 05 Jun 86  17:40:42  (RECV'D) 
From: Mike Dougherty
To:   Jim Arroyo
REPLY TO #5   
Subj: 2.1 vs 3.x FAT pointers

Hi Jim,

I made the mistake of not specifying that 16 bit pointers are for
DOS 3.x and that any earlier DOS (e.g. 2.1) uses only 12 bit pointers
(for every device including hard drives).  There are two solutions
to the problem.  The first solution, which is the best, but requires
spending $90 is buy DOS 3.1.  DOS 3.1 speeds up the display screen
painting and scrolling signficantly (I've heard though that DOS 3.2
is real slow on accessing the disk drives - but that's only hearsay).
The other solution which can be immediately invoked is to set the
number of sectors per cluster to 8 for a 10 meg drive, 16 or so for
a 20 meg drive.   The drawback is that you end up wasting disk space
much of the time but it does correct the DOS 2.1 limitation.

As for installing the .1 microfarad cap on pin 12... I would have
to be there to see what's actually going on (I will admit I've seen
that symptom before but all another design - I can't remember what the cause 
was).

By the way, I've been doing some further work on the JRSASI software.
I've interface the system to an IOMEGA drive which is the same removeable 
drive as used in the Bernoulli (sp?) box.  Think anybody would be interested 
in hooking up their Jr to a Bernoulli Box (it costs about $2000)?

Good luck, I'll be back later this week.

Mike D.




#13  78 15 Oct 86  12:58:05  (RECV'D) 
From: Jon Kosmoski
To:   Lee Meredith
Subj: 20 MB drive parameters

Hi Lee
I wanted to explain how the parameters for a given drive (including a 20 MB) 
were arrived at so rather than simply listing them for you in a mail message, 
I wrote a new document for the TPL files area.  It is available as SETUP20.ARC 
(or SETUP20.DOC unARCed).  This file is a supplement to SDUTIL.DOC and gives 
step-by-step instructions for setting up a Shugart ST-225 or similar 20 MB 
hard drive.  The SDUTIL program is very general and has many parameters which 
can be set.  This can be very confusing.  SETUP20.DOC explains how that only a 
very few of these actually ever need to be changed.  Only those which must be 
changed for the 20 MB drive are discussed to avoid further confusion.
Let me know if you have any other questions and what you think of SETUP20.DOC.
 
Thanks!
Jon Kosmoski




#14  102 22 Oct 86  19:25:49  (RECV'D) 
From: Jon Kosmoski
To:   Al Cultreri
Subj: NEC V20 and jrSASI

Hi Al
Yes!  The jrSASI hardware and software works perfectly with a NEC v20
chip replacing the standard 8088 in the PCjr.  In fact, the system upon
which we test the assembled and tested boards before placing them into 
inventory has a V20 chip.
Thanks for your interest in the jrSASI system.
If you have any other questions or would like to place an order
please leave me a message.
Jon




#15  95 27 Oct 86  04:45:20  
From: Craig Soderland
To:   Tony Cooper
Subj: sasi w/dma

Tony am I to understand that you were able to get the jr to run with the sasi 
interface ? Does it work in the pc mode w/dma ? From your message #67 I am 
sorta led to believe that it does. would you get back to me and let me know 
the how why what and when of the matter it would be extremely appreciated.
                 Craig soderland.




#16  98 31 Oct 86  17:40:58  (RECV'D) 
From: Jon Kosmoski
To:   Joe Frassica
Subj: jrSASI and jrCAPTAIN and floppies

Hi Joe
Thank you for your interest in the jrSASI system.  Yes!  The jrSASI system 
works fine with the jrCAPTAIN multi-function sidecar.  In fact, the PCjr 
running this BBS uses exactly that combination of expansion options and runs 7 
days a week, 24 hours a day.  
 
About using the jrSASI interface to add floppies as well as a hard disk,I'm 
afraid that is not an option.  What the jrSASI interface does is allow SASI 
(Shugart Associates Standard Interface) device controller to talk to the PCjr. 
 Once the jr can understand SASI, then a another interface is needed to allow 
a host using SASI commands to talk to a specific peice of hardware.  To add a 
hard disk to your jr, you need our
jrSASI interface connected to a SASI hard disk controller connected to a hard 
disk connected to a power supply.  If you could find a SASI hard disk and 
floppy disk controller, then you could do it.  I have never heard of such a 
controller or any kind of SASI floppy controller.  They may be out there, 
however.  If it's any consolation, I can't imagine why you would want 
additional floppy drives once you have a hard disk available.  About the only 
More? 
thing I can think of would be allowing to copy a floppy disk more easier than 
you can with one drive.  Other than that I doubt you would use the 2nd floppy 
that much.
 
Let me know if you have any other questions.
Jon Kosmoski
V.P. Engineering, TPL Corp.




#17  98 04 Nov 86  10:09:57  (RECV'D) 
From: Jon Kosmoski
To:   Tom May
SEE ALSO #30
Subj: jrSASI Hard Disk

Hi Tom
Thank you for your interest in our PCjr SASI interface.  Yes!  We have these 
units assembled and tested now.  Unfortunately we are not set-up to handle 
credit card orders at this time.  Normally we ship products C.O.D.  I realize 
this can be a problem since someone has to be there to had U.P.S. the check.  
If you wish to order the jrSASI Interface you can place your order right here 
on this BBS by A)nswering the Questionaire at the main menu.  Once we know 
your address, we could figure the shipping charges in advance so you could 
pre-pay your order.
 
Our interface is actually 1/3 of what is required to get a hard disk running 
on your PCjr.  You will also need a SASI hard disk controller and a hard disk 
and power supply.  We also sell the SASI hard disk controller and a Shugart 20 
MB hard disk.  Surplus power supplies are easily found from mail order houses 
that advertise in magazines such as BYTE and The Computer Shopper.
 
Thanks again and free to drop us a line with any other questions you may
have.
Jon Kosmoski
V.P. Engineering, TPL Corp.




#21  82 29 Nov 86  08:45:12  (RECV'D) 
From: Lee Meredith
To:   Jon Kosmoski
Subj: JRSASI Hard Drive

Jon--
     I finally got my fixed disk up and running.  I was beginning to wonder if 
this was ever going to happen.  Now, I don't know how I got along without it.  
I've got two minor problems I wanted to ask you (or anybody else here) about. 
 When I first power up, I get seek read errors when trying to use parts of the 
harddrive.  After about five minutes, no problem.  Does the drive need to warm 
up?  Second problem is this -- while I was waiting to get the hard drive parts 
together, I bought Legacy's serial port card (plugs into internal modem slot 
to give PCjr two serial ports).  For some reason, the hard drive interferes 
with this serial port.  The hard drive failed to run a communications program. 
 The program then ran fine from drive a:.  I tried another communications 
program from the hard drive with the same result.  Then I switched the modem 
and the mouse, and sure enough, the communications programs would run fine 
from the fixed drive, but the mouse wouldn't work.  Any ideas?  Also, I'm not 
sure I ever heard the definitive word on this . . . does the SASI interface 
hard drive work with Racore Drive II with DMA?  I'm really pleased with the 
hard drive and appreciate all the help you gave me on this project.  I was 
within a couple of days of junking the junior and buying a new computer.
                                          --Lee




#22  85 29 Nov 86  13:27:49  
From: Ethan Young
To:   Sysop
Subj: SASI interface

I am a PCjr owner.  I used to own an AT with a full height 30mb hard disk. I 
would now like to attach this to my jr.  What I would like to know is:  Does 
your SASI Interface card and hd controller work with a 30mb drive?  And, do 
you have the proper software needed to support a 30mb drive?  If you have all 
the above, would you also be able to supply us with the power supply, fan, and 
casing for the disk?  And if not, could you recommend a good place to buy 
those?  I would really appreciate it if you could help me.
     Thanks,
     Ethan Young.




#25  83 05 Dec 86  07:24:16  
From: Gary Myers
To:   Sysop
SEE ALSO #26
Subj: SASI Controller Problem

I have recently completed the Jr SASI Project and am now having
a problem I need some advice on. All parts of the Jr Sasi board ohm 
out ok and the format and write sector portions od SDUTIL complete
without error, however the thing times out on a read multiple sector
command (error 84). I have double checked everything many times. In 
the debug section all commands complete ok except for the final check
listed as "Command-Data Exchange. When I enter I3FFD I get "0B" as a read from 
the SASI data port.  Any hints???  Also, on page 2 of the
schematics, the common lines from the 7438s, they are listed as going
to (SIO), but not connected. Is this a reference point?
       Any comments will be appreciated.
                     Thanks,     
                            Gary Myers
                            (713)643-6524




#26  87 06 Dec 86  02:37:22  
From: Jim Arroyo
To:   Gary Myers
REPLY TO #25   
Subj: solution?

Hi Gary,
This is Jim Arroyo from Los Angeles, Calif.  Try placing a .1 mf CAP from pin 
12 of U6 (7404) and ground.  This fixed a similar problem for me when I was 
building my hard disk interface.  I hope it works out.
                                           Good Luck!
                                               Jim




#27  85 25 Dec 86  23:34:51  
From: Craig Kamman
To:   Sysop
SEE ALSO #28
Subj: 2 drives + Hard drive

  I was wondering if I could add a hard drive to my PCjr when I already have 
the RACORE DRIVE 2 ENHANCEMENT PACKAGE...  does anyone know if I
would still be able to run a hard drive and 2 floppy drives +640k on my jr?    
           Thanks!
                           -Craig




#28  90 27 Dec 86  22:01:18  (RECV'D) 
From: John Wager
To:   Craig Kamman
REPLY TO #27   SEE ALSO #29
Subj: Hard Drive + Racore

You can add a hard drive to your Jr with Racore second drive; if
you do not have DMA, the Jrsasi project here should work fine.  If
you have DMA, you will need to use some other way of adding a
hard disk controller interface; I have a Racore Drive II with DMA
and bought the RIM adapter card (fits in the internal modem slot)
and added my own controller, case, power, and 20 meg ST225 drive
for about $500 total, mail order.  It saved some money, but it took
quite a while to get everything working together and that only after
a few returns of some items. {




#29  77 07 Jan 87  15:03:43  (RECV'D) 
From: Craig Kamman
To:   John Wager
REPLY TO #28   
Subj: thanks!

Thanks!  I'll check around for pricing on hard drives.  The standard PC modem 
cables should plug in shouldn't they?  I mean if I can get a used
Seagate external 20meg with cables, that would plug right in to the SASI board 
right?  Just double checking.. I'll download the SASI files today... Thanks 
again...
                           Craig




#31  89 14 Jan 87  01:10:50  
From: Al Cultreri
To:   Sysop
SEE ALSO #33
Subj: Hard drive controllers for jr

Will RLL type controllers work with the jr SASI interface? Or the other types ,
 MFM?, of obtaining approx. 50% increase of capacity? (Adaptec, etc.)      
....... Also, you may have seen the low prices on some 8 inch hard drives in 
Computer Shopper,   .....are they incompatible, noiser, etc with the jr SASI 
system?  Is their some reason not to consider used or 8 inch new/used hard 
drives?   Appreciate your answer.




#33  51 17 Feb 87  15:33:50  (RECV'D) 
From: Jon Kosmoski
To:   Al Cultreri
REPLY TO #31   
Subj: Using RLL (Run Length Limited) SASI Controllers with jrSASI

Hi Al
No, I'm afraid the new batch of RLL controllers on the market cannot be used 
with the jrSASI interface.  I'm not exactly sure as to the technical details 
of why they won't work.  If you like I can find out from the original designer 
of the jrSASI hardware.
Jon




#34  55 17 Feb 87  16:15:23  (RECV'D) 
From: Jon Kosmoski
To:   John Wager
Subj: ST225N

Hi John
We have not tried it ourselves, but as you said, if it is a "standard" SASI 
controller, it should work fine.  I thought I heard at one time that the 225N 
uses an enhanced interface, SCSI, instead of SASI, but I could be wrong.  If 
it's SASI, then it should work.  [It does have a SCSI controller and therefore
will not work.]
Jon




#38  54 19 Feb 87  09:53:53  (RECV'D) 
From: Jon Kosmoski
To:   Peter Bottari
Subj: Usable hard drives

Hi Peter
If the drives you mentioned connect to a SASI controller via the 
industry-standard ST-506 interface, they should work fine with the Xebec 1410 
(or compatible controller) and with the our SASI to PCjr interface sidecar.
Jon




#40  71 23 Feb 87  10:56:47  
From: Paul Baxter
To:   Sysop
Subj: TPL SASI HARD DRIVE QUESTIONS

I've tried to phone you, but...  So my questions will be here:
1) I have a PCjr with 640K using Tecmar's Jr Captain and Jr Cadet.  Is your 
hard drive compatible with these boards?  [Yes]
2) What will shipping costs be to my address (ZIP 15668, Murrysville PA)?  
What are current costs for your prototyping board, SASI ontroller, and drive?
3) You've recommended DOS 3.1.  Where can I get it?  My local stores all stock 
only DOS 3.2, which you reported trouble with.  [Look for a sale or swap meet]
4) Have most of your customers had success with this drive?  What are the most 
frequent problems they report?  [Conflicts with internal modem slot.]
5) Where do I get the cables to connect the SASI board to the controller, the 
controller to the drive, and the power supply to both?  Are there maximum 
lengths advised for these cables?  [Electronics store; keep them short.]
6) I've noticed ads for ST225 drives for about $100 less than your price.  Are 
there reasons I should avoid them?  [Poor packing -- but mine arrived okay.]
7) Will I need a C compiler for the software, or are all modules supplied in 
executable form?  [All executable.]
8) Do most of your customers just let the parts hang in space or do they buy 
a box?  [Boxes are expensive -- let it all hang out.]
Thank you for your time.
Paul Baxter



#41  52 27 Feb 87  05:21:06  
From: Bert Stark
To:   Sysop
Subj: Sasi interface

         Is there a way to speed up the sasi interface? I know setting
         the interleave helps a lot but is it possible to possibly
         change the 74LS--- chips to 74S--  or even 74HCT---  type
         chips. The interface works great and does things that often
         simulate DMA. I run Qmodem 2.2 off the hardisk on the Jr. and
         do not have DMA. Am I possibly barking up the wrong tree and
         possibly should I look at the software end of the
         enhancement ? I use the Segate 225   20 meg and  as of yet
         have no complaints. Thanks in advance . I guesss I am another
         caught up in the ever widening circle of making things happen
         faster.  Bert Stark: San Antonio, TX .




#42  48 03 Mar 87  13:21:59  (RECV'D) 
From: Jon Kosmoski
To:   Chuck Holst
SEE ALSO #43
Subj: SCSI vs. SASI

Hi Chuck

Thanks for your interest in the jrSASI project.  Yes, SCSI is a
superset of SASI, but no, our interface will not work with a SCSI
controller.  SCSI and SASI are different enough that changes to
the driver and setup software would be required for SCSI.

Yes, we do have sidecar cases to go with the prototype board.
I'll have to check on the pricing and get back to you.

Are you aware that we have an assembled and tested version of the
jrSASI interface.  The assembered version is mounted in a sidecar
case and comes complete with the 50-pin cable required to connect
the interface to a SASI hard disk controller and the driver and
setup software required.  Besides the assembed jrSASI interface
you still need a SASI hard disk controller, a hard disk and a
suitable power supply (at least 1 amp of +5 and 3-4 amps of +12).

The advantage of the assembled and tested interface is obviously,
that you don't have to build it and risk not having it work.  The
cost of the assembled version is $169.95.  The protoboard is
$39.95.  You will have to decide whether you think you are
skilled enough to build the interface yourself and save or if you
should spend a bit more to get the pre-built and tested unit.

I hope this answered your questions.  Feel free to ask any others
you may have.

Take care...
Jon Kosmoski
V.P. Engineering, TPL Corp




#43  49 03 Mar 87  20:13:40  (RECV'D) 
From: Chuck Holst
To:   Jon Kosmoski
REPLY TO #42   
Subj: TPL Interface

     Thanks for the info.  It jibes with what one of the engineers at work 
told me, and contradicts what someone else told me -- it always pays to check 
more than one source.  I am an electronics technician with a lot of experience 
wire-wrapping prototype circuits, so I am confident about my construction 
abilities.  Whether I build or buy depends primarily on the cost of materials, 
so I would still like to know the cost of the sidecar shell.  I expect, though,
that I'll be ordering the prototype board, the shell, and the controller from 
you.




#44  46 04 Mar 87  15:26:52  
From: Dave Olson
To:   Sysop
SEE ALSO #45
Subj: 3.5" drives on JR.

Does your interface board support 3.5" drives if I have DOS 3.2?
What exactly is the function of the jrsasi interface board (technically 
speaking)?     
                            Dave Olson




#45  51 08 Mar 87  12:06:57  (RECV'D) 
From: Jon Kosmoski
To:   Dave Olson
Subj: Our jrSASI interface board

Hi Dave
Our interface board when used with our software driver allows the PCjr to be 
connected to and use a hard disk using what is known as a SASI interface.  
jrSASI is strickly for SASI devices such as hard disks and not for any size 
floppy disk including the new 3.5" drives.
 
I am not sure but using a commercial PCjr 2nd drive adaptor, one might be able 
to connect a 3.5 to the jr.  Maybe someone else on this board might know more 
about this than I or has actually done it.  Feel free to send a message to ALL.
 
Jon




#48  7 27 Mar 87  07:30:21  
From: Bert Stark
To:   Sysop
Subj: 2nd Harddrive

I am very impressed with my 20 meg hardisk ands it works fantastic. I am ready 
at this time to try to add a second harddrive if you will release the info. I 
have a second Segate 20 meg and hope to use it soon. Please advise me as to 
what I need to do if at all possible.
Bert Stark SA TX




#50  1 30 Mar 87  19:19:48  
From: Chuck Holst
To:   Jon Kosmoski
REPLY TO #34   
Subj: ST225N

    As an addendum to your reply about the ST225N, I would like to say that 
the only references to the controller I have seen in Computer Shopper ads say 
that it is SCSI, not SASI, and therefore will not work with the TPL interface.
