>
> >
> > The IMI 5012H is I am told a clone of the Shugart ST-512, which is a
type 1
> > drive, can anyone confirm this? I am, working to resurrect an IBM AT.
> > Silly me I disconnected the battery and lost the configuration
settings. I
>
> Obvious question : Did it work before you disconencted the battery? In
> other words do you know the problem is just due to misconfiguration?
>
Yes. It worked fine before I disconnected the battery. I assumed it was
dead and I was planning on replacing it with a new one.
>
> There is a 3rd party setup program that will run on the real IBM AT (I
> know this, becuase it's what I use on mine). I has the advantage that
> when you select a particualr drive type, it displays the actual
> parameters (cylinders/heads/etc) too.
>
> That way you could at least check you're selecting someting that makes
sesne.
>
> Are you using the orignal IBM (Western Digital, actually) controller
board?
>
Yes. original board.
What I plan to do next is put the drive in an XT, because in an XT there is
no battery needed and I can use spinrite to determine the drive number.
It's possible given I was getting a 1780 error that there is a problem with
both my controllers.
Bill
Owned by a coworker of mine who says it still works fine.
He doesn't want to throw it out if there is someone
interested in preserving it. Somehow, I've never been
interested in adding printers to my collection. In the
"nostalgia era" of my computer experience, what I collect,
printers were noisy, messy and not worth the bother.
Anyway, if you want it and can arrange to pick it up fairly
quickly, let me know.
Bill
Ok guys,
The Good bit....
All this talk of SCSI to whatever got me curious so I started experementing.
What I have so far :
An AVR ATMega1284 (DIP40), connected to an SD card by SPI and to the
SCSI bus via 4 LS chips (1xLS273 and 3xLS240). I currently have
implemented just a few of the SCSI command set, Identify, read, write,
test ready and request sense.
Thist is enough to be able to connect to a PC SCSI card, format the
drive and read and write files to it....heheh I can even boot off it !
I'm using Chan's FatFS, and in this way the drive seen by the SCSI is
actually a large image file on the SD card, I did this as it will make
backing up the drive *MUCH* easier if the target system is not a PC, as
you can simply take the SD card out and copy the image file without
worrying about it's internal structure. In theory this will also make
sharing data between the target system and an emulation running on
something more modern.
There's a couple of pictures here :
http://www.stardot.org.uk/forums/viewtopic.php?f=11&t=3646
The bad bit......
Whilst this all works it's SLOWWWW, using Norton utilities SI, reports
that the disk is 0.2x the speed of an original PC, cirtainly bootup
times are much more akin to what I would expect from a floppy drive :(
So I would sugest that for replacing hard disks that using SCSI->SD is
probably not going to be fast enough.
My next experements are going to center on replacing the SD with an IDE
drive, hopefully this will provide a suitable speed increse, asuming
that this works it should be easy enough to use a CF->IDE adapter board
to use a CF drive instead of an IDE, which will allow the media to be
removable and easiliy swapable.
The other thing I want this to support is 256 byte sectors as some old
machines rely on this, a feature which is supported by some of the early
SCSI/SASI to MFM/RLL boards but very few native SCSI drives, this would
be of perticular intrest to some of the Acorn 8 bit machines.
Comments & sugestions welcome.
Cheers.
Phill.
--
Phill Harvey-Smith, Programmer, Hardware hacker, and general eccentric !
"You can twist perceptions, but reality won't budge" -- Rush.
In 1966, Ken Knowlton created a 16-minute black and white film showing
animated algorithms for the L6 language. Does anyone know if this
film is online anywhere or if the film has been archived anywhere (CHM
perhaps?). Bell Labs used to have a historian, but since Bell Labs no
longer exists, I have no idea who to contact anymore about this sort
of thing. Does anyone know?
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
Hi guys,
I've got my 3B1 emulator "mostly working" in that it runs the Boot PROM,
sees the floppy disc in the drive, and proceeds to boot from it, getting
as far as the Loader.
When it gets to the Loader, I get the following display:
AT&T UNIX(tm) pc
Loader version 3.51
Copyright (c) 1985, 1986
AT&T
All Rights Reserved
Searching floppy disk...
####
Searching hard disk...
... and it stops there. I can tell from the emulator log that it's
trying to get the hard drive controller to read CHS 0:0:0 and DMA the
data into RAM at 0x77830, but because the HDC isn't implemented, it
locks.
What I expected was for the Loader to pick up the boot files on the
Diags disk, boot from that, and ignore the HDD. Does anyone know what
"typical boot behaviour" is for a 3B1, 7300 or UNIX PC, when booted from
the Diagnostics floppy (Foundation Set, disk 1) ?
This is a bit of a head-scratcher -- I'm trying to figure out if there's
a problem with my FDC driver (wouldn't be the first one) or the
DMA/interrupt controller, or if the Loader really needs a hard drive
controller (or a really good fake) to boot the system.
I'd also really like to know why the DMA controller has two separate
direction control bits -- DMAR/W- and IDMAR/W-... this seems downright
silly, though in keeping with the rest of the TechRef. My "annotated
edition" corrects about a dozen minor and major errors in the register
set descriptions, and adds a bunch of informational sticky-notes and
scribbly comments to reinforce certain points. Ewwww...
If anyone's interested in playing with my emulator -- go to
<http://www.philpem.me.uk/code/3b1emu/>. Hit the link under "Mercurial
repository", then ".tar.bz2" to get a Tarball of the sources. Untar it.
Grab the boot PROMs, and put them in a directory called 'roms' as
'14c.rom' and '15c.rom'. Use IMDU (Imagedisk utility) on a DOS PC (or
inside Dosbox) to convert the Foundation Set disks from IMDs to binary
files, then copy the first Foundation disk (Diagnostics) as 'discim'.
Compile (you'll need libsdl, aka the Simple DirectMedia Layer) and run.
I know the code is a mess, patches to rectify this (or any of the other
millions of bugs) would be almost certainly be accepted :)
There's also no keyboard or mouse emulation yet, just the CPU, video,
RAM, ROM and a basic memory mapper and DMA emulation. As for Ethernet
emulation... that's on the "maybe later" list, right after "learn how to
send and receive Raw Ethernet frames on Linux".
Thanks,
--
Phil.
philpem at philpem.me.uk
http://www.philpem.me.uk/
At 03:14 PM 12/4/2010 -0600, you wrote:
>On Sat, Dec 4, 2010 at 2:39 PM, a50mHzHam <a50mhzham at gmail.com> wrote:
> > WANTED: A good home for my last three RACK'O'CD boxes by MDI.
>
>I'd be interested if it's easy (which means no shipping). Where are
>you located?
>
>brian
Southeast Wisconsin-- Milwaukee metro area.
-----
350. [Computing] "Formal specifications yield correct programs." No. Formal
specifications yield PhD theses. They may also occasionally yield
programs as by-products, but no useful ones. --Ronald F. Guilmette
--... ...-- -.. . -. ----. --.- --.- -...
tpeters at nospam.mixcom.com (remove "nospam") N9QQB (amateur radio)
"HEY YOU" (loud shouting) WEB: http://www.mixcom.com/tpeters
43? 7' 17.2" N by 88? 6' 28.9" W, Elevation 815', Grid Square EN53wc
WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531
SCSI to SD/IDE
Phill Harvey-Smith afra at aurigae.demon.co.uk
<mailto:cctalk%40classiccmp.org?Subject=Re%3A%20SCSI%20to%20SD/IDE&In-Reply-
To=%3C4CFAF40D.30108%40aurigae.demon.co.uk%3E>
Sat Dec 4 20:08:13 CST 2010
* Previous message: SCSI to IDE
* Next message: SCSI to SD/IDE
* Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
________________________________
Ok guys,
The Good bit....
All this talk of SCSI to whatever got me curious so I started experementing.
What I have so far :
An AVR ATMega1284 (DIP40), connected to an SD card by SPI and to the
SCSI bus via 4 LS chips (1xLS273 and 3xLS240). I currently have
implemented just a few of the SCSI command set, Identify, read, write,
test ready and request sense.
Thist is enough to be able to connect to a PC SCSI card, format the
drive and read and write files to it....heheh I can even boot off it !
I'm using Chan's FatFS, and in this way the drive seen by the SCSI is
actually a large image file on the SD card, I did this as it will make
backing up the drive *MUCH* easier if the target system is not a PC, as
you can simply take the SD card out and copy the image file without
worrying about it's internal structure. In theory this will also make
sharing data between the target system and an emulation running on
something more modern.
There's a couple of pictures here :
http://www.stardot.org.uk/forums/viewtopic.php?f=11&t=3646
The bad bit......
Whilst this all works it's SLOWWWW, using Norton utilities SI, reports
that the disk is 0.2x the speed of an original PC, cirtainly bootup
times are much more akin to what I would expect from a floppy drive :(
So I would sugest that for replacing hard disks that using SCSI->SD is
probably not going to be fast enough.
My next experements are going to center on replacing the SD with an IDE
drive, hopefully this will provide a suitable speed increse, asuming
that this works it should be easy enough to use a CF->IDE adapter board
to use a CF drive instead of an IDE, which will allow the media to be
removable and easiliy swapable.
The other thing I want this to support is 256 byte sectors as some old
machines rely on this, a feature which is supported by some of the early
SCSI/SASI to MFM/RLL boards but very few native SCSI drives, this would
be of perticular intrest to some of the Acorn 8 bit machines.
Comments & sugestions welcome.
Cheers.
Phill.
--
Phill Harvey-Smith, Programmer, Hardware hacker, and general eccentric !
"You can twist perceptions, but reality won't budge" -- Rush.
________________________________
* Previous message: SCSI to IDE
* Next message: SCSI to SD/IDE
* Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
________________________________
More information about the cctalk mailing list
<http://www.classiccmp.org/mailman/listinfo/cctalk>
________________________________
-----REPLY-----
Huzzah! Good for you! Glad to see *something* coming out of all of this.
Congratulations! Have a nice day!
Andrew Lynch
Hi! Thinking about this some more, we already have simple Z80 with RAM/ROM
circuits and 8255 PIA for I/O including circuitry for 8255 to IDE.
The only new element of this design would be converting a pair of 8255 PIAs
to SCSI-2. Looking at a pin out of a SCSI-2 pin out of the 68 pins, 34 are
grounds and a few more are power related. Basically it is about 30 pins
which actually do anything and of those 24 are data lines. This does not
appear to be a difficult interface to "bit bang" and would be somewhat akin
to the 8255 to IDE circuits.
Yes, performance would just OK and not fast. I think it would probably work
and be fairly cheap to make. I am willing to support other approaches but
would like to just help with the schematic capture, PCB design, and
prototype board development. The key to success is to keep it simple and
easily understood. Adding a bunch of unnecessary complexity just dooms the
project IMO.
Please contact me if interested. Thanks and have a nice day!
Andrew Lynch
>Date: Fri, 03 Dec 2010 19:13:08 -0800
>From: Eric Smith <eric at brouhaha.com>
>Dyslexia strikes again. I thought you were looking for the 85C30, not
>the 53C80. Sigh.
>
>I doubt that anyone makes the 5380 or 53C80 anymore.
Not quite the 53C80, but perhaps the next best thing:
I have three 53C94 and three 53CF94 in 84 pin PLCC packages which I will
happily ship (for free) to anyone who wants to dabble on this project.
They are untested, and I'm looking at my inventory trying to figure out
whatever possessed me to buy them in the first place. Perhaps I got them
with a larger lot. I only ask that you actually be about to experiment
before you ask me to send them to you. It's too easy to acquire stuff
with the intention of doing a project and then for various reasons never do
it.
I also have a brick of 660 NCR 53C96 chips. Unfortunately, these are a
(IIRC) 100 pin QFP (30 X 20?), which is more difficult to work with than a
DIP or socketable PLCC. I am reluctant to open the (sealed) brick to pull
out one or two, but if someone wants to develop this project with the 53C96
in mind I'd be happy to supply 53C96s for the production at a nominal cost;
certainly no more than $1 per chip. Again, not quite sure what I was
thinking when I bought them....
If these are usable and not too modern for this project that should help
keep the cost down as compared to paying $5 - $10 per SCSI chip.
Finally having a written inventory really helps to bring home all those
items that I just can't imagine any realistic future use for....
I put the datasheets for the AMD 53C94/96 and the 53CF94/96 as well as the
Zilog 53C80 up at:
<http://www.io.com/~trag/DataSheet/>
Jeff Walther