Jochen wrote:
> You mean it is possible to speak MSCP on a DSSI bus without
> an additional protocol layer?
> Or do you mean that (only?) non-DSSI controllers a la RQDXx and
> KU]DA50 can speak MSCP without SCA/SCS?
And Roar wrote:
I have got a very strong feeling I was wrong. (Sorry)
> But if you have to talk SCA/SCS with the DSSI-devices, that might
> be a
> problem, since SCA/SCS is not published, and no implementations are
> available.
In my experience with the SII chip you set up a buffer in its shared memory
with the MSCP "packet" layed out, and the node number of where you wanted
it to go at the front. Then you write the that address into the descriptor
register and the SII chip picks it up and drops it off at the drive.
In my case I was writing the equivalent of the SCSI INQUIRE command, and
then a bit later, the SII chip interrupts you to tell you that there is a
new descriptor in its buffers and if you look at it (which I did from the
kernel debugger because I had just panic'd on the interrupt :-) you can see
that the drive has returned to you the information you requested.
Questions that were unanswered in my mind when I put this down about this
time last year were:
1) maintaining the physical/virtual mapping between the 128KB buffer
and main memory.
2) Hooking the MSCP code that was there so that it could fill in
the packets.
3) Writing the bus "enumerator" for config so that I could create
a device instance for each disk I found (tapes I would ignore
for now)
4) Hooking send and receive queues through a top level structure that
would feed/retrieve them from the SII chip.
So I tried last night to get a 'diff' of my build tree from the cvs tree
but since its from 1.5.1 pre-release, the number of diffs is _huge_
relative to the 1.5.2 tree. I'll put a tarball of my sys tree up later
today for anyone who might want to look at it. What I've not been able to
find was my code that set up the INQ command. It shouldn't be too hard to
recreate however.
--Chuck
Folks --
I made the ghastly mistake of bidding on an IBM 5360 ($25). The sale closes
today, and it doesn't look like there'll be other bidders to get me off the
hook. So I thought I do the seller a little favor and spread the publicity
around for him, in case any of you have some unused warehouse space and
were stumped for a way to fill it. I, of course don't. All you need do is
outbid $25 on item 2004672608. ;->~
Seriously (or slightly more seriously) if I'm landed with this thing I'll
probably want to make copies of all the disks and manual then donate it to
a museum collection -- should any be interested. Or a private collector if
their not. The real reason I bid on it was to ensure it's survival of
course. I wasn't actually planning on testing the floor joists in my
1-bedroom apartment. As far as I can tell it's complete, with two printers
and two tape drives. And it's located in Connecticut. If anyone else has a
better idea for preserving it, or wants to lend me a hand (I'm in
Massachussetts) please chime in.
Thanks,
Colin Eby
Senior Consultant
CSC Consulting
Umm, IIRC, I just stuck it in. Yes, you're supposed to have done
some hardware changes, but I thought I'd try anyway. ARCconsole reports it
right, but I haven't done any real benchmark to see if it really is running
at 233...
I'll have to dig up the info. And maybe someone here can burn a new
chip for me?
--- David A Woyciesjes
--- C & IS Support Specialist
--- Yale University Press
--- mailto:david.woyciesjes@yale.edu
--- (203) 432-0953
--- ICQ # - 90581
Mac OS X 10.1.2 - Darwin Kernel Version 5.2: Fri Dec 7 21:39:35 PST 2001
Running since 01/22/2002 without a crash
> ----------
> From: Megan
> Reply To: classiccmp(a)classiccmp.org
> Sent: Tuesday, February 26, 2002 6:09 PM
> To: classiccmp(a)classiccmp.org
> Subject: RE: MicroVAX 4000/VLC
>
> > I have a 233 MHz CPU from a dead Multia in my AXPpci33
>
> What did you have to do to get it working? I was under the impression
> that using a faster processor required some board modifications...
>
> If it will simply work, I guess I need to locate a 233 Mhz CPU.
>
> Megan Gentry
> Former RT-11 Developer
>
> +--------------------------------+-------------------------------------+
> | Megan Gentry, EMT/B, PP-ASEL | Internet (work): gentry!zk3.dec.com |
> | Unix Support Engineering Group | (home): mbg!world.std.com |
> | Compaq Computer Corporation | addresses need '@' in place of '!' |
> | 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 KB1FCA |
> +--------------------------------+-------------------------------------+
>
>
On Feb 26, 19:00, Jerome Fine wrote:
> I seem to remember someone saying that the DSD 440 reads block zero
> of drive zero on power on, then times out and jumps to location zero
> to start.
That's how most 3rd-party RX controllers seem to work, in my experience.
> Try typing in the MSCP bootstrap.
Why? The RX02/DSD440 is a DY: device, not DU:
> The standard RX02 bootstrap uses UNIT=0, so it may need to
> be modified to use UNIT=1 for DY1:, however that stuff is not
> accessible to me right now. Does anyone have the release
> notes for RT-11? It may be there.
I've had it online for a long time, at
http://www.dunnington.u-net.com/public/ODT/Listings/RXV21BootD
I recently made a minor correction (almost all the DEC printed copies have
several errors). It's a Unit 0 bootstrap, but changing the word at
locations 001036 from 407 to 427 should make it work for Unit 1. At least,
I think so; I used it recently and I think that's what I did.
--
Pete Peter Turnbull
Network Manager
University of York
On Tue, 26 Feb 2002, Alan Pearson <alan.pearson(a)cramer.com> wrote:
> I'm looking for a DEC BC09J cable to hook up a VS3100 to a CD drive...
That's the same cable as used with the DECstation 2100/3100. A couple
DS3100s I hauled home had a different cable, p/n BC56H-03. This one is
a few inches longer and the cable comes straight into the 50 pin
Centronics connector as opposed to the BC09J which is right angle.
HTH
Mike
> I came across this ebay item, its some sort of Control Data tape drive.
> I'm just mentioning it in case someone in the Virginia area is interested.
I see he's relisted it... I considered buying this last year when he
ran it previously, but he's not interested in shipping it, and I don't
have a Virginia connection likely to help out.
:(
-dq
> -----Original Message-----
> From: nerdware(a)ctgonline.org [mailto:nerdware@ctgonline.org]
> I remember reading an early interview with Geddy and he was
> talking about auditioning drummers after Rutsey left. He said
> Peart came in, and while they were impressed with his
> drumming abilities, they were also thinking, "Hey! This guy can READ!"
I suppose that is kind of impressive these days, sadly... on the other
hand, if he reads that much Rand, I would have been more disappointed in
the quality of his books, than concerned with whether he could read.
Personal opinion, of course.
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
> -----Original Message-----
> From: Jeffrey S. Sharp [mailto:jss@subatomix.com]
> I vote you call this new breed of VAXen the SuperVAX. Start
> out with the
> SuperVAX 1000 and see where it takes you. Whatever the name,
> I want one.
Or perhaps you could call it something like "Extended VAX"
--err, well, I suppose that one will still be in use for a
couple of years... :)
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'