I'm searching out documentation for the Morrow Micro Decision MD5, MD11 and/or MD34
Z80 CP/M machines.
I had a line onto someone that had them, but he moved and his email address
no longer works.
Does anyone out there have any such documentation, preferably already scanned?
TIA,
-scott
I FINALLY got my TI portable professional in the mail
today. Nearly 50 lbs oi. Did anything sporting a color
crt predate this unit? Whos going to help me retrofit
a more modern and snappy tube?
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Dear Sir,
Do you still have any of the old tape drives referenced in your message? If
so I am interested.
Thanks.
Wes Goodwin
Well, I went through the hardware I have at home and here is the list. Most
of the stuff hasn't been turned on for over 10 years, probably more like 15.
It has been in my workshop/basement, so it is pretty dry. The list of
manuals will come later. The list of tape drives at work will come after
that, but those (I think) are all 9 track, as are most of these. Anyway,
here is the list of drives/controllers/formatters. Kennedy 9220
(192-9220-066) two cables, and a Kennedy 5427 mounted on the back. Formatter
maybe. Cipher F880 1600/3200 BPI, 100/50/25 IPS IDT (Innovative Data
Technology) TD11051, 800/1600 BPI, 45 IPS, 3 connectors, read, write,
motion, 36 pin edge connectors, and a cable from (THIS) drive? bringing all
3 connectors into a single 50 pin edge higher densidy connector. Kennedy
9000 (192-9000-019) 9 track 800/1600 BPI, 37.5 IPS Cipher 910640 800/1600
BPI, 75 IPS 2 Emulex TC01/TU01 board pairs, QBUS 1 Emulex TC02 Formatters?:
Pertec F6181-1/0085 Formatter, 2 boards, NRZI Read/Write, PE Read Datum
10341 Q/HP (Kennedy 120-0025-01) controller Datum Formatter 5091-120 Pertec
f84942(0)/13.9, 901006-01 with R/W 7/9 NRZI Prime formatter 3101-0001
(Kennedy 9219-509), 3 boards inside As I said, I have been holding on to
this stuff so I could someday set up a system to read the 15 or 20 tapes I
have. All RT-11 or VMS, with a couple off an RSX-11 system. If there is
something here that could help out with somebodys project, I would be glad
to lend it out, or even give it away, just as long as it either makes it
back so I can eventually read my tapes, or if somebody wants to read the
tapes they can have all/any of the tape drive hardware. The list of manuals
for the formatters/drives will be along shortly.
Regards, Joe Heck
>From: ard at p850ug1.demon.co.uk
>
>> That's odd.
>>
>> Usually ." Hello, world." words on all forths.
>
>
>Watch out. In some Forths, ." can only be used inside a colon definition,
>not in the imput like (you get some very odd effects, possibly even a
>crash if you try). I used to know the reason for this, something about it
>needing to allocate space for the string.
>
>At least one Forth used " rather than ." too.
>
>>
>> Keep in mind you do need the space between ." and the first letter of
>> the string, since ." is a word (a "parsing" word since it reads ahead in
>> the stream till the ending ")
>
>But there does not need to be a space before the closing quote (if there
>is one, it will be output as part of the string)
Hi
As an example, : HI ." HELLO WORLD" ;
should echo when you enter the word HI.
>
>> Might help. Sometimes you can also type WORDS at the command prompt and
>> see all the words.
Tony mentions VLIST but I've also seen WORDS or LIST used for
this function as well.
As for filenames, this is something that each implementation
does differently. If you can get a VLIST, we can most likely
figure out what is going on.
Some simple test.
100 CONSTANT FRED ( should create the constant FRED )
FRED . ( should print 100 )
200 VARIABLE SAM ( should create the variable SAM but
depending on implementation it may or
may not initialize the value to 100 )
SAM @ . ( should display the value 200 )
300 SAM ! ( should store 300 to SAM )
SAM ? ( if implemented should display the value in SAM )
SAM . ( displays the address of SAM )
Anyway, try to get a complete list of words with something like
VLIST. It'll pick up things like single character words like
! or . that would otherwise be hard to find.
As was mentioned, even though it may only store 4 characters
of a word, most times it also stores the length so even though
VARI doesn't work VARIABLE should work ( even VARIXXXX would
do the same ).
I like Forth but I think the truncated names are a pain.
It would be better to have the first 3 letters and a hash
of the word as a last byte. I guess for a memory constrained
system, one has trade-offs.
Dwight
________________________________
Van: cctalk-bounces at classiccmp.org namens Tony Duell
Verzonden: di 24-01-2006 01:10
Aan: cctalk at classiccmp.org
Onderwerp: Re: RK07 questions - now RK611 questions
>
> You are correct, Tony, board swapping tricked me (this time)!
And yet you persist in wanting to do it...
> I think I can forget the RK07 drive for now, and concentrate on the RK611
> controller. First, I checked the flat cable from the controller M7904 (dri=
> ve
> interface) module to the home-made bulkhead. That flat cable is 100% OK.
> The round cable from the bulkhead to the drive is NOS, and the label is
> 70-12292-25, so I'm sure it is the RK06/RK07 drive cable, not the RL0x cabl=
> e.
Can you open the hood at one end of that cable (it will unclip fairly
easilt, I think you undo the screws on the cable clamp first). An RK07
cable as virtually all the pins wired, an RL cable has a lot unwired.
I have learnt not to assume anything when tracing faults....
And do stick a voltmeter on the +5V line. Bitter experience (again) has
taught me that this is a the cause of a lot of obscure problems. Best to
eliminated it now...
> =
>
> Before pulling out all kind of equipment, I started with what a DEC enginee=
> r
> probably also would do: run the diagnostics! So, I loaded XXDP and ran
> ZR6A??.??? which is the test "RK611 diskless controller diagnostic #1".
OK...
> Here is the output.
> =
>
> .R ZR6A??.???
> ZR6AD0.BIN
> RK611 DISKLESS DIAGNOSTIC: PART 1 CZR6AD0
> @
> ATTEMPTING TO CLEAR CS1 WITH A SUB CLEAR
> BUS ADD INCORRECT
> TEST ERROR
> NUM PC
> 000041 033024
> PREV EXPECT ACTUAL
> VALUE VALVE VALVE
> 013776 000200 100200
> =
>
> So, there is already a problem with the RK611 controller reported after the=
>
> diagnostic runs some 5 seconds! A few months ago I scanned a pile of XXDP
> doc, but the ZR6A et al. was not amongst them :-(
> I am not sure I have a spare RK611 controller board set (going to the attic=
> k
> after this e-mail), but can somebody tell me which board is likely to be su=
> spected?
Do you want my help or not? Because I sure am not going to help you to
swap boards.
What I can tell you is how to trace that fault. The diagnostic seems to
be saying that the top bit (bit 15) of CSR1 could not be cleared. So,
let's grab the prints (but not tonight, it's late...) and find CSR 1,
find out what should set and clear bit 15, and see what's going on there.
-tony
This message and attachment(s) are intended solely for the use of the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by telephone and with a "reply" message.
Thank you for your cooperation.
I have an HP LaserJet IIISi. It's mostly Just Worked for me (though
there was one mildly spectacular incident involving a failed
electrolytic a while back). But recently (the last month or so), it's
been exhibiting odd streakiness. Given the amount of collected wisdom
here regarding such things, I thought it would be a reasonable place to
ask to see if anyone can tip me off what's up with it and how I might
be able to fix it.
Specifically....
After leaving the printer off for a long period (a weekend, say), upon
turning it on and printing, the first page is fine. The second page
exhibits a few grey vertical streaks, worse towards the bottom of the
page - not clean vertical lines; it looks as though toner is getting
into the paper path where it shouldn't, and rubbing off on the page
before it hits the fuser. Printing more pages works fine, but they get
worse and worse. I've never had the streaks get so dark that I can't
read printing for them, but the printing definitely becomes
black-on-grey instead of black-on-white.
Letting the printer sit will improve matters somewhat, but only
somewhat; recently, I've even had the first page come out with some
streakiness.
I'm wondering if there's something like a static bleeder that's failed
open, or a mechanical part that's not moving where it should, or some
such.
I can do a greyscale scan of a page if it would matter, if the details
of exactly what kind of streaks I'm seeing can affect the answer.
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse at rodents.montreal.qc.ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
At 08:43 AM 1/24/06 -0500, you wrote:
>Okay, I figured out the immediate problem. Three of the pins on one
>of the EPROMs have broken off. One was hanging by a thread and fell
>off when I inspected it. I see no evidence that the pins remain in
>the sockets so I guess they must have fallen off when I removed the
>EPROMs to read them in my EPROM programmer. I suppose this suggests
>that they may have fallen off *before* I read them and that is why
>your SnapFORTH ROMs don't work. I don't think that's the case though
>because I'm sure I would have noticed that. Do EPROM (or chip pins in
>general) get more brittle as they get older?
They were plenty brittle to begin with! See for example the graph labeled
"Number of pins remaining vs number of socket insertions" in the WOM data sheet:
http://academics.vmi.edu/ee_js/Research/IC_Datasheets/digital_cmos/Write%20…
Tim.
