Hey all,
Anyone know whether the Emulex UC04 works with the sd2scsi? I just
bought a uc04 and it won't talk to any of my old scsi disks, seems to think
there's supposed to be a "controller" in between :\ yuck.
thx
jake
P.S. While I'm at it, anyone know how to get UC04 to talk to directly to
plain scsi disks and tapes instead of these lunatic ESDI controller bridge
things?
Howdy? from the? ?desert? lands in Arizona!Early in the? HP DOS? PC? campaign? there was the? monarch? butterfly poster used to advertise? HP? 150 ... seeking to recreate? a duplicate? in a? corner of? the? room our? little? hp 150? computer exchange inc? ?demo desk? area? .... the? poster ( or a? print of it... )? ?is? needed!
What? great? fun we are? having...? got a? 2886a? (need paper feeder? and receiver? little? flap? things that hung off? printer though)and the? stake of? all the? '150' blue? box? ?software'? to have there too? and other things? ? for the era...any other early poster material? good? too... the monarch? one is? what? sticks in my? brain...
OK? also the? HP Portable 110? came? along too... interested in Ad? material for? it... have most of the hardware? to? look? ?interesting I? think.
THANKS IN ADVANCE? ED SHARPE? ARCHIVIST FOR SMECC
The copy of the KD11-EA engineering drawings (in the 11/34A Field Maintenance
Print Set, MP-00190) on Bitsavers is missing most of the pages that hold the
microcode flow diagrams. I have a set of the KD11-EA FMPS (MP-00192), which
does have all the missing pages, which I can eventually scan. However, in the
interim, the 11/34 Field Maintenance Print Set Vol. 2 (MP-00082) on Bitsavers
has a complete set of microcode flow diagrams for the KD11-E (pp. 15-40 of the
PDF), and they are almost identical to the KD11-EA diagrams.
The only difference I can see (I compared page by page, to see if each page
had the same microinstructions on it) is that on sheet 17; the last
microinstruction for RTI/RTT has been moved from 002 -> 744. (The actual
microinstruction contents seem to be the same.)
I don't know whyo the changed address; I originally thought that perhaps they
had to re-do the IR Decode ROMs when they added floating point, and they
needed the original location to handle the start of the floating point
microcode, but that doesn't seem to be the case.
Noel
Chuck! Many thanks!
Update on? 422 UNIVAC? docs . .? some kind? ?people have mailed in? docs and? ?things? they have? found related to this? 422 UNIVAC ...? things are? shaping up! Many? thanks? ?to? all? these? folks-
I? fear ever putting power to this? thing... so? may? parts to go? POP... I have a nice large? Variac.....? ?suggestions?
Ed
In a message dated 1/5/2019 11:18:00 AM US Mountain Standard Time, cctalk at classiccmp.org writes:
Since it was a 53-year old high-school project, I doubt that you're
going to find much on it.? However, see the post by Steve Schweda here:
https://community.hpe.com/t5/Operating-System-OpenVMS/Left-shift-by-more-th…
He may actually have some familiarity with ELTRAN and know where some
documentation exists.
--Chuck
On 1/5/19 10:10 AM, Chuck Guzis via cctalk wrote:
> Okay, I think I found the reference to it.
>
> It turns out that it was a high-school student's project entered in the
> "Fourth Annual Computer Programming Contest for Grades 7 to 12'.? To quote:
(COME ON SOCRATES ...? DO YOUR? THING!)
In a message dated 1/5/2019 1:49:38 AM US Mountain Standard Time, cctalk at classiccmp.org writes:
no is compiler a small one only 2 do loops allowed...ed#
Sent from AOL Mobile MailOn Friday, January 4, 2019 Chuck Guzis via cctalk <cclist at sydex.com; cctalk at classiccmp.org> wrote:On 1/4/19 8:42 PM, Fred Cisin via cctalk wrote:> Would be? interesting when you find it.> Not necessarily "tiny"> Remember WATFOR??? (very impressive!)
I guesss not too many numerical methods types hwere, but ELTRAN is asubroutine in the EISPACK linear programming set.? Yes, it's all FORTRAN:
>From the subroutine:
cc? ? this subroutine is a translation of the algol procedure elmtrans,c? ? num. math. 16, 181-204(1970) by peters and wilkinson.c? ? handbook for auto. comp., vol.ii-linear algebra, 372-395(1971).cc? ? this subroutine accumulates the stabilized elementaryc? ? similarity transformations used in the reduction of ac? ? real general matrix to upper hessenberg form by? elmhes.
--Chuck
no is compiler a small one only 2 do loops allowed...ed#
Sent from AOL Mobile Mail
On Friday, January 4, 2019 Chuck Guzis via cctalk <cclist at sydex.com; cctalk at classiccmp.org> wrote:
On 1/4/19 8:42 PM, Fred Cisin via cctalk wrote:
> Would be? interesting when you find it.
> Not necessarily "tiny"
> Remember WATFOR??? (very impressive!)
I guesss not too many numerical methods types hwere, but ELTRAN is a
subroutine in the EISPACK linear programming set.? Yes, it's all FORTRAN:
>From the subroutine:
c
c? ? this subroutine is a translation of the algol procedure elmtrans,
c? ? num. math. 16, 181-204(1970) by peters and wilkinson.
c? ? handbook for auto. comp., vol.ii-linear algebra, 372-395(1971).
c
c? ? this subroutine accumulates the stabilized elementary
c? ? similarity transformations used in the reduction of a
c? ? real general matrix to upper hessenberg form by? elmhes.
--Chuck
> From: Paul Koning
>> On Dec 31, 2018, at 6:32 PM, Henk Gooijen via cctalk <cctalk at classiccmp.org> wrote:
>> ...
>> There are one or two bits in a register of the RK11 that have a
>> different meaning/function, depending on the controller being a -C or
>> -D.
> If someone can point me to the description of the differences I should
> be able to say what RSTS will do with them.
AFAIK, the only difference (in programming terms) between the -C and -D is
that the -D has dropped the maintainance register.
Although I cheerfully admit I haven't sat down with -C and -D manuals and
done a bit-by-bit compare. I just did that (I used the "RK11-C Moving Head
Disk Drive Controller Manual", DEC-11-HRKA-D, and the 1976 "Peripherals
Handbook"), and found in the following:
In the RKDS: bit 7 has changed the definition slightly ("Drive Ready" to
"R/W/S Ready"), but seems to be basically the same. In the RKCS, bit 9 is
"Read/Write All" in the -C, and unused in the -D; bit 12 is "Maint" in the
-C, unused in the -D.
In other words, a -D driver should work just fine with a -C, IMO.
Noel
>-----Original Message-----
>From: cctalk [mailto:cctalk-bounces at classiccmp.org] On Behalf Of Carlo Pisani via cctalk
>Sent: Tuesday, January 01, 2019 5:35 PM
>To: ben; General Discussion: On-Topic and Off-Topic Posts
>Subject: Re: Motorola M88K books & user manuals (looking for)
>
>> I was never a fan of RISC architecture as does not fit the standard high
>> level language model. Everybody wants a 1 pass compiler, thus the RISC
>> model. If you are doing your own RISC model, you might consider a model
>> that supports Effective addressing better since we have got the point
>> where fetching the data is taking longer than processing it.
>
>yup. I am a 68k programmer so I know what you mean.
>the 68k is more comfortable to be programmed in assembly, and even the
>EA modes (especially in the 68020 and CPU32) help a lot.
>
>unfortunately, the 68K is very complex to be designed, and the first
>68020 used microcode, which is a no-go for modern designs.
>
>...
I'm curious as to why you make this claim that microcode is no-go in "modern" designs. Could you please elaborate on this point? I don't see why the alternative random control logic would be a better proposition.
Thanks,
paul