Is anyone using this combination? I'm having problems getting it to work
reliably on a soft-sector controller in my Heath H89 and their forum is
essentially dead.
--
The WD9000 Pascal Microengine main box does not include floppy drives.
It can support up to four floppy drives, which can be either 8-inch
(500 kbps transfer rate), or 5.25-inch (250 kbps transfer rate), as
selected by a DIP switch setting on the WD900 board. Unfortunately
the DIP switch directly controls the clock rate into the 1793 FDC
chip, so it is not possible to mix 250 kbps and 500 kbps drives.
However, it should be possible to mix 8-inch drives with high-density
5.25 inch or 3.5 inch drives that use the 500 Kbps transfer rate.
The floppy connector on the back of the WD9000 box (and the WD900
board) uses a DC37S connector, and the pinout seems to be unique to
the Pascal Microengine. My Microengines did not come with the floppy
drives or cabling. I've designed a simple adapter PCB, and just got
the first boards back from PCBWay today. I haven't yet finished
assembling one because I screwed up ordering on some of the components
and connectors. Photos:
https://www.flickr.com/photos/22368471 at N04/albums/72157660580290148
The WD900 board uses an FD1791 double-density floppy controller. It
appears that the main board may have been originally intended for the
FD1771 single-density controller, as the board revs I've seen don't
have a suitable double-density data separator built in. On one of my
units, the FD1791 is on a daughterboard with a typical analog data
separator design using the WD1691 floppy support logic and a 74LS629
VCO. My other board has the FD1791 on the main board, but has some
significant rework to install an SMC FDC9216B digital data separator
chip in place of one of the TTL chips originally used by the main
board design. I've seen other WD900 boards with the FDC9216B
modification, so I think this was rework done at manufacturing time,
rather than a field change.
One aspect of the floppy controller design seems a bit unusual. The
WD controllers have a HLD output used to tell the floppy drive to load
the head, and an HLT input (Head Load Timing) to indicate that the
head is loaded. After the controller asserts HLD, it waits for HLT to
go true before proceeding with read, write, or format operations. A
typical 8-inch drive takes 35 ms to load the head, and maybe a few
more for head settling. A common way to wire the controller is to use
an external one-shot triggered by HLD, with its output wired to HLT,
and adjusted for a time delay a little longer than the drive requires
for loading the head. 8-inch drives typically can either be jumpered
to use a dedicated head load control line on the interface to control
the head load solenoid, or to automatically load and unload the head
as the drive select signal is asserted and deasserted.
Normal 8-inch drives have the head load solenoid to do what was
previously described, and run the spindle motor either all the time,
or whenever a disk is inserted and the door closed. 5.25-inch drives,
and some later 8-inch drives such as the Tandon TM848, do away with
the head load solenoid and instead are intended to operate with the
spindle motor active only when the drive is selected, or when a motor
control signal is active. As such, they don't require any head load
time, but instead require a motor startup time that is even longer;
the slowest drives require about a second for spinup. With a WD
controller, this is also sometimes accomodated by using the one-shot
between HLD and HLT.
Some WD-based controller designs, such as those in the TRS-80 Model I,
III, and 4, are only intended for 5.25-inch drives (or the 8-inch
drives that use motor control and no head load solenoid), and tie the
READY signal from the drive to the HLT input of the FDC.
The WD900 board tries to acommodate these variations by bringing the
HLT signal to its DC37S connector, for the system integrator to wire
up as desired. The only complete Pascal Microengine system I've seen
up close in recent history had a hand-wired drive cable to 8-inch
drives, with the HLT signal simply tied to a +5V pin on the same
connector. The net effect of that is that the FD1791 asserts HLD,
delays 15ms if the h bit of the command is 1, and does not delay any
further. Unless the drive can actually load its head that quickly,
this doesn't seem ideal, but I suppose it works because the FDC won't
be able to read a valid sector address field until the head is loaded.
For a write operation, I'd worry that the head might not have fully
settled by the time the actual write begins, possibly leading to
unreliable writes.
To support proper head load or motor spinup timing, I put an optional
PIC microcontroller and DIP switch on the adapter, to act as a digital
delay between HLD and HLT, with sixteen switch-selectable delays. The
drive select lines are wired to PIC inputs, so if desired, firmware
could actually use different delays for different drive selects, if
you mix drives with different head load timing requirements. I
haven't yet written any PIC code for it. The board should basically
work as described above with HLT jumpered to +5V, without the PIC and
related components installed.
The adapter has both a 50-pin connector for 8-inch drives, and a
34-pin connector for 5.25-inch or 3.5-inch drives. It is intended for
one connector or the other to be used, but not both. Even if you use a
combination of drives that all use the 500 kbps transfer rate, having
them cabled separately to the two connectors could result in
termination problems.
Naturally, only hours after ordering the PCBs I thought of
improvements that I'd like to make to the design, but I don't
anticipate that there will be a second run of boards.
I don't presently have any bootable disk for the Pascal Microengine,
so I'm not yet able to test the adapter. However, if anyone else needs
such a thing, I have a small number of bare boards that can be made
available inexpensively. (I don't have time to assemble boards other
than for myself.) If there's any interest, I'll publish the Eagle
design files, gerber and excellon files, a PDF of the schematic, and
source and object code for the PIC firmware. The firmware will be
GPLv3 licensed, and the other design files with be under a Creative
Commons license, probably CC BY-SA 4.0.
Hi there everyone.
I'm hunting for an NEC PC-8031A mini-disk module for the NEC PC-8001A
computer. I have the computer itself and PC-8012A expansion chassis
already.
Additionally looking for anything else relating to this computer that you
might have kicking around and be willing to part with. Including but not
limited to the "Wedge", expansion unit cabling, expansion cards, etc.
Note: I have seen the one floating periodically on eBay and am keeping a
close eye on eBay in general for this unit so am looking for leads outside
of that.
If anyone has stuff for this computer, please contact me off-list. I'm
near Philadelphia and willing to drive to avoid you having to pack/ship.
Not against shipping stuff either.
Thanks!!
-Todd
From: Mike Ross <tmfdmike at gmail.com>
> I have a 3172 controller; physically rough and needs restoration but *should* work if
> I can fake the remote connection and modem - bisync etc. B
From: Paul Berger <phb.hfx at gmail.com>
> you need a modem eliminator mostly to provide the clocks for the sync data line,
> other than that is is similar to a null modem.
Not sure if this would work here, but the Cisco IOS "IBM Feature Set"
has support for all sorts of weird bisync use cases. I've used it to
fake termination of an ALC (Airline Line Control) bisync connection
where a modem connection was expected. You can then convert, tunnel
or bridge to any number of other strange things.
There even exists an IBM channel attach card for the Cisco 7k routers
that turns it into the equivalent of a 3172 and/or 3745.
KJ
> From: Brent Hilpert
> I need to move to something newer but I haven't evaluated current
> schematic-drawing programs
Dave Bridgham got me started with KiCAD, and that seems like a pretty good
system to me. It has separate sub-systems for schematic capture; circuitry
checking; netlist generation; PCB layout; etc, etc. I've only worked with the
first three, but it seemed pretty good for them.
> I'm a little concerned they won't provide the degree of control or
> finesse I like
Well, you'll have to try it and see, but it's pretty customizable: they
provide libraries of common components, but it has a nice component editor
for drawing up new ones (or customizing the ones it comes with).
Component location and line routing (in the schematic capture) are manual,
but it's grid-based, so things line up.
Noel
I?ve been tinkering around with my IBM Mainframe terminals and I?m pretty close to having everything the way that I want it.
I currently have an IBM 3174-61R Establishment controller connecting to my ?mainframes? via TCP/IP. This allows me to not only connect to my Multiprise 3000 S/390 but also some PCs running Hercules to allow me to run older versions of the mainframe OS?s. I currently have 3 IBM 3179 terminals hooked up.
I?ve upgraded the 3174 to be able to boot from a hard disk (it was a supported option). I actually purchased the upgrade from a reputable vendor but after many attempts we could not actually get it to do anything useful. I learned about DavidG?s MFM emulator and that?s now installed in the 3174 which happily boots from it. I still have to figure out a permanent mount for it since the standard 3174 HDD mounts don?t work for the MFM emulator board.
One of the last things that I wanted to figure out was how to support multiple sessions. I had configured the 3174 to support multiple sessions on each terminal but following the documentation, I could never figure out how to actually switch between the sessions. Well today I managed to do that. Success! I finally figured out the key sequence for switching sessions. It doesn?t match the IBM documentation. It?s not clear to me if that?s because I haven?t configured something properly on the 3174 or if there?s some other reason behind it.
Since I also have the AEA feature that allows me to connect ASCII terminals to the 3174, my next project will be to hook up a couple of the terminals that?re deemed ?compatible? (VT100, ADM5 are on the list) and see how that works. But that also involves navigating the 3174 configuration process which is opaque to say the least (there are configuration screens but you need a manual because the fields only have numbers (e.g. 721) to identify them and no other indication as to how they need to be filled in).
Oh, the other bizarre thing about the 3174 that?s been configured with TCP/IP is that I can also connect to ?unix? servers with the 3174?s (and the ASCII terminals too). It?ll be interesting to see how that works on a CUT mode terminal. ;-)
TTFN - Guy
ok we have this
In the PS/2 days there where suitcase size machines with plasma displays
but they only had a single diskette drive that folded out of the front,
we also have the dual disc laptop 1st thing IBM made with lcd
then we also have a one that is like a suitcase compaq portable that
made compaq famous
ok thinks for it all being non scsi!
Ed# _www.smecc.org_ (http://www.smecc.org)
In a message dated 12/18/2015 1:15:22 P.M. US Mountain Standard Time,
ggs at shiresoft.com writes:
> On Dec 18, 2015, at 12:03 PM, Paul Berger <phb.hfx at gmail.com> wrote:
>
>>
> The screen on the convertable is not plasma, it is a LCD screen and
there where two versions one reflective and the other backlit. In the PS/2
days there where suitcase size machines with plasma displays but they only had
a single diskette drive that folded out of the front, one model is the
8573-P70. There where 386 and 486 versions of these machines with
microchannel card slots and a SCSI disk.
>
Again, no. They did not ship with a SCSI disk. They used the same disks
as were in the model 50 & 70 (which were *not* SCSI).
A number of us at IBM (who worked on the SCSI cards spock & tribble) did
fit the card (usually spock because it had 512KB of cache) and an IBM 320MB
SCSI drive in the P70. It was *not* a standard (ie orderable)
configuration but at the time created a wicked machine!
TTFN - Guy
Looking for some Fluke Micro System Troubleshooter stuff:
Looking for the following key caps: AUTO, BUS, RAM SHORT, and C
Bonus key caps (not needed, but better ones would be nice): RAM LONG,
I/O, 1, 2
Also looking for PODS for:
6502
Z80
6809
8080
If you have any of these available, please let me know what you have
and a price.
Thanks,
-- Curt
> From: Doug Ingraham
> I regret that when I obtained my Straight 8 system in the early 80's I
> chose not to take the ASR-35.
> ...
> A glass terminal is not the same experience as a teletype.
Thank goodness for that! I had the 'joy' of using exclusively Teletypes for
the first two years I worked with computers, and I didn't (and still don't)
miss them one bit!
Which is not to say I look down on those who collect/restore them, I
understand they are an important part of the history, and I salute those who
are into them. I'm just saying that, as a user, I was glad to move on!
Noel