Steve,
I believe he needs the one wiht the pronged holder that stays in the drive
while the outer clear cover comes back out when you load a CD in the drive. To the best of my knowledge only one company made these drives. I actually
have bare drive still in the box, and an external RRD40.
My question would be, does the Infoserver allow upgrading the CD-ROM drive? If so I'd look into something like an RRD42 or a Plextor drive if it will
work (I've had good luck with Plextor drives in DEC gear). The RRD40 is the
most agonizingly slow CD-ROM drive I've ever used!
Zane
On Tue, 8 Dec 2009, Steve Davidson wrote:
Ian,
The caddy is made by NEC (among others). I would start on the NEC web
site. Stores that specialize in refurbished PC's or places that have random
electronics may be able to help as well. If you are still stuck let me know
off-line and I'll see what I can come up with.
-Steve
____________________________________________________________________________
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf
Of Ian McLaughlin
Sent: Tuesday, December 08, 2009 00:58
To: hecnet at Update.UU.SE
Subject: [HECnet] RRD40 / Infoserver 100 CDROM Caddy
Hello All, Does anyone have for sale, or know of a location to purchase, a
disk caddy for the RRD40 CDROM drive found in an InfoServer 100? It's not
the same style as the 'standard' CD caddies. I have acquired an InfoServer
100, but it's missing the caddy.
I'd appreciate any assistance in getting a caddy. Thanks!
Ian.
Ian,
The caddy is made by NEC (among others). I would start on the NEC web site. Stores that specialize in refurbished PC's or places that have random electronics may be able to help as well. If you are still stuck let me know off-line and I'll see what I can come up with.
-Steve
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Ian McLaughlin
Sent: Tuesday, December 08, 2009 00:58
To: hecnet at Update.UU.SE
Subject: [HECnet] RRD40 / Infoserver 100 CDROM Caddy
Hello All,
Does anyone have for sale, or know of a location to purchase, a disk caddy for the RRD40 CDROM drive found in an InfoServer 100? It's not the same style as the 'standard' CD caddies. I have acquired an InfoServer 100, but it's missing the caddy.
I'd appreciate any assistance in getting a caddy. Thanks!
Ian.
Ian McLaughlin wrote:
Hello All,
Does anyone have for sale, or know of a location to purchase, a disk caddy for the RRD40 CDROM drive found in an InfoServer 100? It's not the same style as the 'standard' CD caddies. I have acquired an InfoServer 100, but it's missing the caddy.
I'd appreciate any assistance in getting a caddy. Thanks!
Ian.
Hi Ian,
Wouldn't it be easier to replace the RRD40 with an newer drive? E.g. a RRD43, RRD44 or RRD45. They are faster and you don't need any caddies.
Kari
On 2009-12-06, at 9:23 AM, Dan Williams wrote:
The online docs aren't the easiest to look through. But they are there
it's in this book
http://h71000.www7.hp.com/doc/73final/documentation/pdf/DECNET_OVMS_NET_MAN…
Page 3-49.
I only found it by searching the whole document for routing and
looking at every result.
Thanks for finding that! I know where I went wrong - I'm old-school when it comes to documentation - I've got the PDFs printed out, because I prefer dead-tree format.
Ian.
2009/12/5 Ian McLaughlin <ian at platinum.net>:
On 2009-12-04, at 7:23 AM, Brian Hechinger wrote:
You know, all this DECnet routing talk has got me thinking. It's been a
LONG time since I've done any DECnet networking. Is there a good place to
read up on it or should I just read the VMS manuals online since I'll be
doing this from VMS mainly at first.
I spent quite some time trying to get an area router working. I couldn't
find any documentation other than the standard DEC manuals (available
online). The DEC manuals talk about the theory, including non-routing,
level 1 routing and level 2 routing (area routing), but I couldn't find any
document that explained how to enable level 2 routing. Thankfully, this
list was able to help me out.
Ian.
The online docs aren't the easiest to look through. But they are there
it's in this book
http://h71000.www7.hp.com/doc/73final/documentation/pdf/DECNET_OVMS_NET_MAN…
Page 3-49.
I only found it by searching the whole document for routing and
looking at every result.
Dan
On Fri, Dec 04, 2009 at 09:55:47PM -0800, Ian McLaughlin wrote:
You know, all this DECnet routing talk has got me thinking. It's been a
LONG time since I've done any DECnet networking. Is there a good place to
read up on it or should I just read the VMS manuals online since I'll be
doing this from VMS mainly at first.
I spent quite some time trying to get an area router working. I couldn't find any documentation other than the standard DEC manuals (available online). The DEC manuals talk about the theory, including non-routing, level 1 routing and level 2 routing (area routing), but I couldn't find any document that explained how to enable level 2 routing. Thankfully, this list was able to help me out.
Ok, so I'll read the online docs then and use the emails from this list I
saved to setup my L2 router. :)
Thanks!
-brian
--
"Coding in C is like sending a 3 year old to do groceries. You gotta
tell them exactly what you want or you'll end up with a cupboard full of
pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435)
On 2009-12-04, at 7:23 AM, Brian Hechinger wrote:
You know, all this DECnet routing talk has got me thinking. It's been a
LONG time since I've done any DECnet networking. Is there a good place to
read up on it or should I just read the VMS manuals online since I'll be
doing this from VMS mainly at first.
I spent quite some time trying to get an area router working. I couldn't find any documentation other than the standard DEC manuals (available online). The DEC manuals talk about the theory, including non-routing, level 1 routing and level 2 routing (area routing), but I couldn't find any document that explained how to enable level 2 routing. Thankfully, this list was able to help me out.
Ian.
Paul Koning wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Friday, December 04, 2009 10:17 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Others DECnets
Hmm, which wouldn't neccesarily result in the same thing...
Named objects use object #0, and then you specify the object name,
which
for instance in RSX means the task name.
Now, I don't even think numbered objects and named ones are handled
the
same way in RSX, since numbered objects are usually in the form
NNN$$$,
where $$$ is replaced by a number, for the service to be able to run
several instances in parallel. I don't think this $$$ replaced by a
number ever is done for named objects.
Also, the name of the task used for a service is not standardized. So,
the mail service task name can be anything. All you know is that it is
#27.
So, trying to talk with an named object called MAIL might cause to you
to talk with just about anything.
In RSX, the known objects of my system looks like this:
.ncp sho kno obj
Known objects summary as of 4-DEC-09 16:07:24
Object Name Copies User Verification
0 Single Default Off
15 TCL... Single Default On
16 LSN$$$ 5 Default Off
17 FAL$$$ 8 Login On
18 HLD... Single Default Off
19 NIC$$$ 5 Default Inspect
23 RMHACP Single Default Off
25 MIR$$$ 5 Default Off
26 EVR$$$ 5 Default Off
27 MAL$$$ 8 Default Off
29 PHO$$$ 5 Default Off
42 RTH Single Default Off
63 DTR... Single Default Off
So, trying to talk to MAIL would simply just fail, unless there is a
MAIL task installed, in which case that will be started. What program
that might be, and what it might do is beyond guess, but most likely
not
what a programmer of a remote system might have expected, if he tried
to
talk to an object called MAIL, thinking that was the right way to talk
with a MAIL-11 server accepting mails.
Good point. The name flavor of object reference is OS specific, because
the conventions for what names appear aren't the same everywhere. So
the numbers provide the portable way. If you use the name form you have
to know what you're dealing with. The example I gave (connect to
"MAIL") would work for DECnet/E.
Yes, it will be OS specific.
But even more so, I don't think it will work out right for you even if you try to talk to MAL$$$ on an RSX system, because RSX will see that MAL$$$ is a prototype task, and is not allowed to run, and will just fail on you.
When you invoke object 27, as I mentioned, DECnet will actually create a copy from the prototype task, and replace $$$ with a number, making an actual task appear, which is started, and which is not a prototype.
Now, I haven't actually tried this, so I could be wrong, and that DECnet-RSX will actually handle the $$$ substitution for named tasks as well, but I don't think it do. I think that is also tied into the "Copies" parameter, which for named tasks is "Single".
Johnny
Yes, except that object numbers are just one byte... ;-)
Johnny
Bob Armstrong wrote:
However, the object identifier in the
connect message can be either a number or a name. So while normal
practice would be to connect to mail by connecting to object 27, it's
also valid to connect to object "MAIL".
FWIW, this is all in the DECnet database (at least on VMS it is) -
$ MCR NCP SHOW KNOWN OBJECTS
will give you a list. You can also use DEFINE/SET to modify the list
$ MCR NCP DEFINE OBJECT foo NUMBER 493
Bob
Right, except that object numbers are one byte so the upper limit is
255.
paul
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Bob Armstrong
Sent: Friday, December 04, 2009 10:12 AM
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Others DECnets
However, the object identifier in the
connect message can be either a number or a name. So while normal
practice would be to connect to mail by connecting to object 27, it's
also valid to connect to object "MAIL".
FWIW, this is all in the DECnet database (at least on VMS it is) -
$ MCR NCP SHOW KNOWN OBJECTS
will give you a list. You can also use DEFINE/SET to modify the list
$ MCR NCP DEFINE OBJECT foo NUMBER 493
Bob
