The ROI is a rebadged Emulex UC07 SCSI disk or Tape, If you don't have docs
let me know and I will organize something.
The Emulex_unknown_001.jpg is a CS08 8 line mux - DHV11 emulation.
I will need some more # from the plessey to figure it out.
Dan
->Rather then describe them, I've got scanned images... can someone
>take a look and tell me what they might be? Even better, if someone
>can tell me how they are configured, I'd really appreciate it.
>
> ftp://ftp.std.com/ftp/pub/mbg/scans/
> emulex_unknown_001.jpg
> plessey_unknown_001.jpg
> roi_unknown_scsi.jpg
> I know this is a scsi board, for qbus, but
> it may be a proto...
> g5389_q22_bus_exer_rev_b.jpg
> I know what it is (not the option name, though),
> I'd like to know how to use it...
>
> Thanks in advance...
> Megan Gentry
> Former RT-11 Developer
>
>+--------------------------------+-------------------------------------+
>| Megan Gentry, EMT/B, PP-ASEL | Internet (work): gentry(a)zk3.dec.com |
>| Unix Support Engineering Group | (home): mbg(a)world.std.com |
>| Compaq Computer Corporation | |
>| 110 Spitbrook Rd. ZK03-2/T43 | URL: http://world.std.com/~mbg/ |
>| Nashua, NH 03062 | "pdp-11 programmer - some assembler |
>| (603) 884 1055 | required." - mbg |
>+--------------------------------+-------------------------------------+
>
Rather then describe them, I've got scanned images... can someone
take a look and tell me what they might be? Even better, if someone
can tell me how they are configured, I'd really appreciate it.
ftp://ftp.std.com/ftp/pub/mbg/scans/
emulex_unknown_001.jpg
plessey_unknown_001.jpg
roi_unknown_scsi.jpg
I know this is a scsi board, for qbus, but
it may be a proto...
g5389_q22_bus_exer_rev_b.jpg
I know what it is (not the option name, though),
I'd like to know how to use it...
Thanks in advance...
Megan Gentry
Former RT-11 Developer
+--------------------------------+-------------------------------------+
| Megan Gentry, EMT/B, PP-ASEL | Internet (work): gentry(a)zk3.dec.com |
| Unix Support Engineering Group | (home): mbg(a)world.std.com |
| Compaq Computer Corporation | |
| 110 Spitbrook Rd. ZK03-2/T43 | URL: http://world.std.com/~mbg/ |
| Nashua, NH 03062 | "pdp-11 programmer - some assembler |
| (603) 884 1055 | required." - mbg |
+--------------------------------+-------------------------------------+
>This is probably one of the multi-processor machines, and is in a
>deskside configuration, if I'm guessing correctly.
Correct. It is in a tower-style case and has a basic terminal for the
console. I worked on this box a few years ago when I was at this
company and seem to recall it had something like dual M88100s.
>DG seem to have that philosophy, yes. They have an odd market
>presence.
Strange isn't it? :-)
>Let us know if you find anything.
I'll check those newsgroups. Isn't there a DG newsgroup? I'll have
to check. So far about all I've found are some dealers selling
memory or re-selling old boxes. I did find one guy who says he
has a couple of boxes too and is trying to get enough info to begin
porting Linux to them. That's about it so far.
-----
David Williams - Computer Packrat
dlw(a)trailingedge.com
http://www.trailingedge.com
He's gotta be out there somewhere. I had some OSI computer marketing material
out on extended loan to him and I got the materials back about 2.5 weeks ago.
In a message dated 15/04/99 8:37:57 Eastern Daylight Time,
fauradon(a)pclink.com writes:
<< He cashed mine about a month ago and I also Have had very little contact
with him. Last I got was that he was traveling or otherwise swamped by his
job. His last e-mail stated that he'll ship on monday and confirm by e-mail
but I have not received such confirmation... I'm getting impatient too...
Francois
>I haven't heard from him either. He cashed my check on April 5, 1999. Let
me
>know if you hear from him.
>
>
>>
He cashed mine about a month ago and I also Have had very little contact
with him. Last I got was that he was traveling or otherwise swamped by his
job. His last e-mail stated that he'll ship on monday and confirm by e-mail
but I have not received such confirmation... I'm getting impatient too...
Francois
>I haven't heard from him either. He cashed my check on April 5, 1999. Let
me
>know if you hear from him.
>
>
I'm thinking about attending the upcoming Trenton Computer Festival.
Unfortunately, if I do go, I won't be able to make it until Sunday. Any
opinions on whether or not the second day of the TCF is worth a two and a
half hour drive?
Thanks.
Tom Owad
At 09:26 AM 4/15/99 +1000, you wrote:
>
>There is a touchscreen alignment option, but i've yet to figure out if
>it's working properly.
I've never had much luck with that one. There are other tests there
somewhere in the menu.
Joe
Ok, on a polarised 34 pin floppy connector, which end is pin 1?
I'd rather not wire my adapter cables backwards, even though they would
still be usable if i connected it to a non-polarised adapter...
-Lawrence LeMay
Max,
How many of the oddball PS2 floppy drives were wasted? I could use one or
two. Sure they arent valueable but when you need one... I also use parts
to the soldered board level.
As to your comment 1.2*shipping, that's actually quite fair.
MA is the enemy, they want to make up all poor.
Allison
>> To try and keep this on topic, how did Ferguson do ABS in the early 1970s? I
>> don't believe they would have used a microprocessor. I'd guess at an
analogue
>> computer, probably not even electronic. Would this be less frightening to
>> Tony.
>
>
> Was this the Jenson FFS?
I've never heard of the Jenson FFS, I'm afraid. The system I was thinking of
was called the Ferguson "Formula" All-Wheel Control system. It had four-wheel
drive and ABS. I heard about it beacuse one was fitted to a Triumph Stag in
?1973, and said car was on display at the Stag Owners' Club National Day in
1991.
Philip.
Just when you thot it would never happen...
(and with almost no notice as usual)
Its going down this Saturday, 17-April-1999!
Preview at 0900 Auction starts at 1100
Details (such as they are) at:
http://members.aol.com/innfograph
(for those not familiar with this - its in Portland, Oregon)
-jim
---
jimw(a)computergarage.org
The Computer Garage - http://www.computergarage.org
Computer Garage Fax - (503) 646-0174
>>> Coming soon to www.computergarage.org - the CBBS/NW on-line archives
>>> Coming to VCF III (2-3 October 1999) - CBBS/NW live!
Well, theres good news and bad news. The good news is, I saved a pair of
AT&T 3B2 computers. The bad news is, they have been trashed pretty badly
by our local chapter of ACM.
No screws holding the case together, or even holding most of the internal
stuff together (power supply floating around, floppy floating, etc). The
case is not attractive, and one has spray painted words on it, i think
in an attempt to prevent theft (i guess it stops dumb thieves who cant
figure out hwo to ether remove teh paint, or paint over the paint).
Anyways, any pointers to 3B2 information would be helpful. Possibly these
are only good for parts, i know they only had one of them working, and that
one apparently woudl crash frequently...
These are 3B2/300's if that matters much.
-Lawrence LeMay
<It'll run as a 3 channel logic analyser, up to 100MHz. 3 channels doesn't
<sound like much, and compared to a 32 channel benchtop analyser it isn't.
<But it's enough to tell if there ever is overlap between D and clock on a
<flip-flop or somethign like that
Gotta get me one of those.
<[Trivial reason] It has selectable input thresholds. Most logic probes
<are TTL only, or maybe TTL and CMOS switchable. The LogicDart will do ECL
<levels. It'll even work with the -15V logic used in the HP9100...
My suggestion was adaquate to get that person out of a jam if need be.
Simple probles are fairly easy to make. Another useful tools is a
14/16pin logic clip, a self powered clicp that displays the pins as
leds. it has it limits but can be handy. If there is a point sometimes
the expensie spread is not needed to see that an input or output is simply
stuck.
Allison
Well, I'm about to start making various custom ribbon cables, for
hooking a terak disk drive to a pc controller, to connect a
DSDD 8" drive to a pc controller, and to connect a 5.25" drive
to a 8" controller (cromemco).
As I dont have all the necessary connectors yet, my first attempt
will be hooking a terak drive to my PC. I have 3 different
documents all describing this sort of thing, and it looks like
you have to read carefully and consider exactly what you're trying
to connect, in order to get a few of the lines connected correctly.
Thats fine, i'll see if i can figure that out.
One thing concerns me though. My oldest document mentions using
pull-up resistors connected to a +5 source, on 11 of the connections
on the 50 pin side. The explanation is that some signals are open
collector driven, and thus you need 2200 Ohm pull up resistors.
Does anyone know what the deal is, and is this really necessary, or
just a nice idea that you can usually ignore...
-Lawrence LeMay
PS: The terak drive is a SSSD shugart, and it has a 40 pin external
connector on the case (they dont bother connecting the first 10 pins).
Karl Maftoum <karlm(a)blitzen.canberra.edu.au> wrote:
> be able to tell me what "Power-on error 1000" means? and how to test out
> the touchscreen?
Joe thinks that that is "batteries dead", and I can't remember. One
other thing you may want to do, assuming this is the sort of 150 with
a 9-inch (~23cm) screen, is to get a can of compressed air and blow the
dust out of the touchscreen sensor holes -- part of the power-on
self-test checks out the touchscreen (if present) and if some of the
sensors don't see the IR light it will fail with some other code (F000?
-- it's been a long time!). The computer will continue to work (maybe
even the touchscreen will!) after this though.
Yeah, there's also a 150 with a 12-inch screen that is tiltable. That
is a 150C aka Touchscreen II and it has later ROMs that know about
more devices. I don't really know how to tell the difference between
a 150A, a 150B, and a 150A with the later B ROMs (yes an upgrade was
available).
-Frank McConnell
At 01:27 AM 4/15/99 +1000, you wrote:
>
>Today I dusted off the HP150 I picked up the other week, when I saw it I
>actually believed it was only a terminal, but it had a HP-IB interface
>which made me pick it up. Discovering that it is a non-IBM compatable 8088
>based machine with a touch-screen was nice :-) Not having any drives with
>it renders it useless as a computer, but I am interested in getting it
>working as a touch screen terminal, does anyone have the docs for this? or
>be able to tell me what "Power-on error 1000" means?
The N-cell batteries in the back are dead and it's lost it's CMOS settings.
and how to test out
>the touchscreen?
There are built-in tests. I don't have my manual handy so I can't tell
you exactly how to get to them but they're in the menu at the bottom of the
screen.
I have some floppy and hard drives and prnters that will work with the
150 if you're interested. I have docs and software for it too but I don't
have time to make copies.
Joe
>
>Megan: I haven't forgotton about the VSV-11, I have holidays next week so
>I'll fire it up and see if it still works for you, been a busy fortnight
>:-)
>
>Cheers
>Karl
>
>
>
>---------------------------------------------------------------------------
---
>
>Karl Maftoum
>Computer Engineering student at the University of Canberra, Australia
>
>Email: k.maftoum(a)student.canberra.edu.au
>
>
At 01:52 PM 4/14/99 -0700, Sellam Ismail wrote:
>October 2-3. If you don't come you'll wake up on Monday, October 4th,
>with much regret.
If we had any sort of advertising budget I'd suggest that people who don't
want to keep their non-Y2K compliant computers (say pre-1989) should bring
them to give away at the swap meet portion :-)
--Chuck
>
> As I understand the charter (and please correct me), this list is for the
> discussion of any computer-related item over 10 years old. This includes
> hardware, software, peripherals, storage media, preservation, repair,
etc.
>
> While I'm not particularly interested in old application software, I
> don't think anyone would mind a discussion of it here.
>
> -tony
>
These old computers aren't much good without the software. I'd welcome the
discussion as long as it's not the same old "Linux is great, MS sucks"
rant. There are more appropriate places for that discussion.
Personally, I found the PICK messages to be enlightning and informative.
Discussions of that nature are a real asset to the group.
Just my $.02
Steve Robertson - <steverob(a)hotoffice.com>
I think it is now safe to say that the State of Massachusetts is the enemy
of Classic Computer enthusiasts everywhere!
http://cnn.com/NATURE/9904/07/computers.potholes.ap/
"We want people to take those computers out
of the attics, get them out of the landfills and
make use of the good parts," said Rick
Lombardi, spokesman for the department.
"And God knows, we have plenty of potholes
to fill in New England."
This is sickening!
Zane
| Zane H. Healy | UNIX Systems Adminstrator |
| healyzh(a)aracnet.com (primary) | Linux Enthusiast |
| healyzh(a)holonet.net (alternate) | Classic Computer Collector |
+----------------------------------+----------------------------+
| Empire of the Petal Throne and Traveller Role Playing, |
| and Zane's Computer Museum. |
| http://www.dragonfire.net/~healyzh/ |
Tony wrote:
>> Tony said, on processor design, you can either have one flip-flop to each
>> machine state (like a P850) or microcode. Again there are intermediate
points.
>> I claim you can do quite well by numbering the machine states in a suitably
>> chosen binary code and having one flip-flop to each bit. Logic for changing
>> flip-flops is often _easier_ than when you have one flip-flop per state. (I
>
> Although, of course, the advantage of one f/f per state is that you can't
> get glitches when you decode the outputs of the flip-flops.
Because you don't decode them, right?
As Tony probably remembers, my final year project at university was a GPIB
interface for a Trend papertape reader (no, it isn't finished yet - ten years
on!). My original design used a flip-flop for each machine state in three state
machines.
I recently looked at using fewer flipflops. I recall one of the state machines
had six states. Using three bits, one could define the two redundant states in
such a way that this was also glitch-free. Additionally, one of the state
variables was an input, not a flipflop...
>> have done both designs for the same circuit BTW). If you put this logic into
a
>> ROM, this becomes in a sense a microcode ROM, but you can do it
combinatorially
>> as well...
>
> A ROM _is_ combinatorial logic. I don't want to get into a silly argument
> over this, but I have great difficulty finding a conceptual difference
> between a combinatorial circuit built from a pile of AND, OR and NOT
> gates and the same circuit built (albeit using a lot more transistors) in
> a ROM. To claim that a CPU using a ROM is microcoded but one with
> _identical_ internal states using simple gates as the feedback logic
> round the sequencer flip-flops is not is a very strange way of thinking
> about things.
Fair enough. Just another example of different places to draw boundaries, with
grey areas in between. I would call the ROM version microcoded, and the hard
wired version not, because the ROM version contains CODE. (I would agree that
the two machines are equivalent, one implemented using a store of (micro-) code
and the other using gates.) But your view is equally valid. Perhaps this
displays your hardware background and my more software-based upbringing.
To show how grey this is, if you use a ROM to implement the combinatorial logic
for a flipflop-per-state machine, would you call the code in this ROM microcode?
It performs that function, viz. to output signals based on the machine state
which control the operation of the machine including the selection of the next
state.
For that matter, remember your example on this list a while back, using logic
gates to implement Z80 instructions.
> Well, I might accept it once I'd drawn out the full schematics and
> figured out what it was going to do. The problem of what happens if it
> fails is another matter, though. As I said time and again, the time to
> try a different braking technique is _not_ when the car is skidding all
> over the place on a normal road.
I'm not convinced the braking technique is different, though. I would generally
try to brake thus: brake only just not hard enough to skid. If skid occurs,
start pumping. I claim this applies to both sorts of car, but skid is less
likely to occur with ABS.
I read once (in a sci-fi novel) about a braking system where the brake for each
wheel derived hydraulic pressure from a turbine on that axle. ABS wasn't the
issue there, but I claim this system is passive and intrinsically anti-lock. It
also has the advantage that a failure on one wheel doesn't affect the rest of
the vehicle (though with only a small number of wheels, as in a car, this may be
a problem). I wonder if something of this nature could be made to work usefully
for ABS...
Philip.
I did the same thing for an OSI system a few
months ago. Look in the list archive. In brief:
1) using the second set of pinouts in the comp.os.cpm
faq worked best for me.
2) build your converter on a Radio Shack Experimenters
board (part no. 276-168B). Works very well.
3) use 22disk version 1.31 or earlier. Newer versions have
timing problems with 8 inchers.
Hello. This 4000/300 has been dominating my computer room for a while,
and I love how it looks, but it'd be great if it worked.
The boot-diagnostic LED on the inside panel is stuck at 'F'. I don't have a
field service manual, so I don't know the exact meaning. I've checked all
of the boards inside to make sure they're snug inside, but no luck. Nothing
shows up on a terminal hooked up to the MMJ jack. The drives seem to
power up.
Anybody have any ideas? I'd love to have another VAX running here.
Thanks in advance.
--
<cstone(a)pobox.com>
<boards? My strategy was this:
< 1.) Debug the chassis.
< 2.) Install components from a working 8/M.
< 3.) Replace componets from the working 8/M with questionable
< components.
< 3a.) If the replaced component failed: Fix it.
< 3b.) If the replaced component worked: Move to the next one.
This is a good plan. Pay attention to debug the chassis though as there
can be latent bugs like bad connectors.
<BTW, the "best" tool I've found for working on PDP-8s is the Radio Shack
<scope probe. Its more than fast enough to look at the signals. I suspect a
<Logic Dart would be better but I've not had enough funds for that toy yet.
For the PDP-8 any cheap logic probe will do if it can see 50nS pulses.
or you can make one with 7404, a oneshot (7412x) and three leds. the
oneshot is to strecth the fast ones to light a led.
Allison
First, thanks for the references. I will look into the "apparently hidden
board" in a day or two. For now, I have some of the information that I
need regarding the 11/45, thanks to those on this list.
As with the 11/45 listing, these are readability oriented, given R to L.
The 11/44 had this set: (all numbers begin with M, save the G7273)
7090
empty
7093
7094
7095
7096
empty
7098
unsure of occupancy of this slot
8743
empty
empty
7982
7273, in the top two thirds, with 7297 in the lower third of this slot
7297
7295
7294
5904, these three are located in the middle third of the slot
5904
5904
9300
unsure of occupancy of this slot
empty
9202, in top third, and 7258 in bottom two thirds of the slot
some Emulex card
unsure of occupancy of this slot
9302, in top third, and some Emulex in bottom two thirds of the slot
The tape drive for this unit is a TS11.
How much power should I expect to supply in order to run the CPU, TS11,
two RM02's (with a whopping 67MB capacity, and at this size, we'll never
run out of available storage), and the terminal? Do I need the services of
an electrician?
William R. Buckley