HDTenEightyP/NetNews huggingface dataset:
From: edsver4@cecil.lerc.nasa.gov (Jane Kramer)
Subject: Can a non-DEC disk be the primary (boot) disk?
Reply-To: edsver4@cecil.lerc.nasa.gov
Organization: NASA - Lewis Research Center
Date: Tue, 29 Dec 1992 16:24:01 GMT

I've got a DECstation 5000 model 200 (currently running ULTRIX 4.2A) whose
primary (boot) disk, rz0, is a 300MB disk originally supplied by DEC with the
workstation.  The workstation also has two 1 GB disks which happen to be
IMPRIMISes.  I would like to make one of the IMPRIMIS disks be the primary
disk, since each release of ULTRIX gets bigger and bigger, and it no longer
fits on my 300MB disk.  

One of the IMPRIMIS disks died recently, and I just received a replacement
for it.  I partitioned it today using newfs.  I partitioned the 'a' partition
(for /) so that it would contain bootstrap information, and I partitioned the 
'b' (for swap) and 'g' (for /usr) partitions with the -n option of newfs (no 
bootstrap program).  I gave newfs a disk-type of rz57 (there was no exact 
match in /etc/disktab) which it overrode for the 'b' and 'g' partitions.  
Afterwards, I was able to run fsck successfully on all three partitions.

I then tried to load 4.3 from my TK50.  When the install program got to the 
part where it wants to know which disk to load to, it showed all three of my 
disks as options.  I chose rz2, my newly partitioned disk.  The install 
program then balked, and said:

	Unable to obtain device geometry for rz2.
	This is not a supported system disk.

I don't set up new disks everyday, and I've exhausted the "Disk Maintenance" 
section of the "System and Network Management" volume.  Have I missed any step 
in initializing the new disk? Or does the primary disk have to be a DEC disk?
Any advice would really be appreciated.

Thanks.
-- 

-----------------------------------------------------------------------------
Jane Kramer			|     phone: 216-826-6737
NASA Lewis Research Center     	|     Sverdrup Technology, Inc.
Cleveland, Ohio  44135         	|     email: edsver4@cecil.lerc.nasa.gov 
-----------------------------------------------------------------------------
From: toreh@bootes.sds.no (Tore Haraldsen)
Newsgroups: comp.sys.dec
Subject: Mapping of cdfs file names
Date: 29 Dec 92 12:59:59 GMT
Organization: Statens Datasentral A/S, SDS, Norway

In accessing a CD-ROM mounted on an Ultrix box from a PC with PC-NFS
software, all file names looks horrible, because of the habit of PC-NFS
to map all file names containing upper case characters into strange file
names.

Is there a way to get the cdfs file names mapped to lower case by
default, for instance with a mount option on the Ultrix box?

-- tore
-- 
------------------------------------------------------------------------
Tore Haraldsen, Statens Datasentral A/S - SDS, Norway
email: toreh@bootes.sds.no
Newsgroups: comp.sys.dec
From: beaulieu@bose.com (Larry Beaulieu)
Subject: Re: VAX BSD final answer...
Organization: Bose Corporation
	<1992Dec14.041235.4661@panix.com> <1992Dec15.093732.364@hsh.com>
	<BEAULIEU.92Dec21155956@monk.bose.com> <Bzn2Dr.Bwo@world.std.com>
Date: Thu, 24 Dec 1992 20:29:56 GMT


>What about RT-11 (she asks, expecting another comparison against
>RSX)

	OK. I *liked* RT-11.  I just liked RSX more!
--

--
Larry Beaulieu			beaulieu@bose.com
Bose Corporation		Phone: 508-879-1916 x6479
Framingham, MA 01701-9168	FAX:   508-820-4865	

		All flames gleefully ignored.
Newsgroups: comp.sys.dec
From: beaulieu@bose.com (Larry Beaulieu)
Subject: Re: VAX BSD final answer...
Organization: Bose Corporation
	<1992Dec14.041235.4661@panix.com> <1992Dec15.093732.364@hsh.com>
Date: Mon, 21 Dec 1992 20:59:56 GMT


>> Except of course for VMS, which was as slow and ungainly a decade ago as UNIX
>> has only just started to become.
>> 
>>(Now if there were only a TOPS-20 or ITS port for the vax...)

>How about a RSTS port :-)

	Nah. Native RSX-11M+, not that crappy VMS emulator drivel of RSX11M.  RSX
	was always better than RSTS, anyways. :-)



--
Larry Beaulieu			beaulieu@bose.com
Bose Corporation		Phone: 508-879-1916 x6479
Framingham, MA 01701-9168	FAX:   508-820-4865	

		All flames gleefully ignored.
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.sys.dec
Subject: Re: Help on programming VAX disk controller
Date: 31 Dec 92 04:17:37 GMT
Distribution: na
Organization: St. Peter's College, US

In article <1245@blue.cis.pitt.edu>, slimick+@pitt.edu (John C Slimick) writes:
> He needs help on programming the VAX disk controller. In
> particular, he is interested in a publication titled
> 
>    "How to Program the UDA-50"
> 
> which comes in three volumes, and, at one time, was
> sold by DEC as part number LK<something>. If anyone can
> help, please send email to:

  It's QP905-GZ. You might also be interested in QP906-GZ, which describes the
controllers from a physical point of view (what the LED's mean, etc.).

  However, this is a really _bad_ way to learn how to do MSCP programming.
First, the examples are really poor. Second, the Q-bus controllers (RQDXn)
work differently from the Unibus versions and the documentation does not
cover them. Third, many of the more useful sections have been censored out
of the customer edition of this document.

  If you can, grab hold of the fully functional MSCP driver that DEC donated
to UC Berkeley for the BSD Unix project. You could be able to find this on
any BSD Unix tape. There are also some other drivers kicking around in the
BSD Unix distributions, including at least one done without looking at any
DEC code (if that is important to you).

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
From: jeh@cmkrnl.com
Newsgroups: comp.sys.dec
Subject: Re: File system vs. RMS
Date: 29 Dec 92 13:46:47 PST
Distribution: world
Organization: Kernel Mode Consulting, San Diego, CA

In article <3936363@zl2tnm.gen.nz>, don@zl2tnm.gen.nz (Don Stokes) writes:
> jeh@cmkrnl.com writes:
>> To be precisely correct, RMS implements record structure within files.  RMS
>> does not implement files.  Files are implemented by the Files-11 XQP, 
>> or (for RSX-compatible volumes) the ODS-1 ACP, or (for tapes) by the 
>> mag tape ACP.  
> 
> While you are correct here, it's not a useful definition (except to internals
> types).  My point is that RMS is sufficiently pervasive under VMS that the
> normal user or applications programmer has no need to make that distinction;

This is true in most cases.  Nevertheless, I must forcefully disagree with this
philosophy. 

I have taught VMS programming and internals for about 3 years full time,
followed by about nine years of occasional teaching.  And in my experience,
early exposure to correct terminology makes it much easier to learn the
concepts behind the terminology later on. 

Correct terminology encourages the formation of correct mental models, with
which the student is better able to answer questions for themselves.  Sloppy
use of terminology leads to incorrect conclusions.  I've seen this again and
again. 

It's true that only a few of those who are learning system services or RMS
calls today will go on to learn internals later.  And if you could just
figure out who they are, you could avoid bothering the rest with these details.
But there is no way to make that prediction. 

Besides, even though the typical user or applications programmer may not *need*
to make the distinction, it takes all of a few minutes to explain it, and it
isn't going to hurt anyone to make the distinction where it isn't necessary. 

We're going to have to agree to disagree here.

	--- Jamie Hanrahan, Kernel Mode Consulting, San Diego CA
drivers, internals, networks, applications, and training for VMS and Windows-NT
uucp 'g' protocol guru and release coordinator, VMSnet (DECUS uucp) W.G., and 
Chair, Programming and Internals Working Group, U.S. DECUS VMS Systems SIG 
Internet:  jeh@cmkrnl.com, hanrahan@eisner.decus.org, or jeh@crash.cts.com
Uucp:  ...{crash,eisner,uunet}!cmkrnl!jeh
From: refling@sloth.eng.uci.edu (John P. Refling)
Subject: Re: RD53s won't stay spun-up (anyone have a fix yet? - I may soon)
Newsgroups: comp.sys.dec
Organization: University of California, Irvine
Date: 3 Jan 93 20:48:39 GMT

In article <C0AGzD.GtH@watdragon.uwaterloo.ca> kcwellsc@watdragon.uwaterloo.ca (Ken Wellsch) writes:
>> I have a pair of RD53s (real DEC-labelled RD53s) which I tried to put
>> on a DOS machine.  I pulled the R7 jumper and set the drive select to
>> 1, and managed to get one to format on the ST506 controller.  However
>> it then started to exhibit a strange behavior:  It won't stay spun up.
>> When power is applied it spins up to what seems to be close to full speed;
>> I think I hear the click indicating that the heads are being released;
>> but then it spins down again.
>> 
>> Same thing happened with the other drive even before I tried formatting
>> it.
>> 
>> What could I have done to these drives???
>
>You don't say anything about the history of the drives.  We here at U of
>Waterloo have loads of RD53's that have the same behavior.  Our hardware
>wizards have swapped the board portion among the drives from known working
>drives without success.  So my guess is you've received these drives with
>this condition (i.e. they did the same in their DEC equipment as well
>which maybe why you've now got them?)
>
>The current theory is this: these Micropolis 1325's and 1335's apparently
>have quite sophisticated current sensing circuits to monitor the motor
>load and such.  With time, the motor windings degrade and the current
>load exceeds the tolerance of the limiting circuit.  The spin-up spin-down
>behavior is the drive saying I am not working correctly.
>
>I've also heard about these puppy's having thermal troubles as well, they
>run for a while then spin down.  I think it may be a similar problem.
>
>Indeed as others have pointed out, they do draw a heck of a current normally
>as well -- 2.5A as +12V normally.

YES---- I agree!  I have several micropolis drives which were in PCs
which failed the same way.

Then, when I inherited a microvax with a micropolis drive, I installed
the OS (ultrix 1.1!) successfully, cycled the power, and had the drive
spin up and then down, I could have kicked myself.  Needless to say, I
wasn't that surprised.  Sometimes it works, sometimes it doesn't.  If you
get it spinning, don't shut it down!

So now I have 7 of these drives and it may be worth my time to figure
out how to fix them!  (if nobody else has).  My top prioity is
finishing my disseration, so the micropolis project will be on hold
for at least a month.  (So what am I doing reading news?)

If people have some dead drives to donate to me to experiment on, I
could use them.........
Newsgroups: comp.sys.dec
Subject: Re: TABLE OF VUPS WANTED
From: Programmierer@BEIZ.mediatex.ch (055485666: MEDIAtex AG)
Date: 25 Dec 1992 22:28:37 CET
Organization: MEDIAtex AG, CH-8807 Freienbach/SZ

I have a table with not all, but a lot of the CPU' s and her VUP's.

I'm currently not in the office so I'm not able to post the whole list, but I
have the numbers of your request:


4000-600     32 VUPs

the number of the 6000-310 I don't have but the 6000-series is following:

6000-210      2.8 VUPs
6000-410      7 VUPs
6000-510      13 VUPs
6000-610      33 VUPs

I assume the 6000-310 is somwhere betwin 2.8 and 7 VUPs. 
If it's of general interest, I could post my list on a regular basis.

I have not only the VUP-data of the VAX-Processors, I have also collected
some other data (like TPU) and of course, also datas about the new ALPHA AXP
processors.

If there is a general interesting about that, please e-mail to me and I will
do that.





|B                                    B|
|E           CH: VTX *3600#           E|
|I           D:  BTX *28881#          I|
|Z                                    Z|
From: vance@lpl.arizona.edu (Vance Haemmerle x4021)
Newsgroups: comp.sys.dec
Subject: Re: Table of VUPs wanted
Date: 24 Dec 92 06:21:58 GMT
Distribution: world,local
Organization: Lunar & Planetary Laboratory, Tucson AZ.

In article <1haqn0INNfla@msuinfo.cl.msu.edu> mrr@cl.msu.edu (Mark Riordan) writes:
>Hello.  This may be a FAQ, but where can I find a table of
>DEC VAX CPU model number vs. VUPs?  
>
>Barring that, can anyone tell me the VUPs rating of the
>VAX 4000-600 and the older VAX 6000-310?
>I could probably dig up the information from old DEC literature
>in my office and by logging into DEC's Electronic Store,
>but it would be painful.
>
>Thanks!
>
>Mark Riordan   mrr@scss3.cl.msu.edu

 Here is a small not-all-inclusive (mostly newer midrange) table:

 VUPS      Models
  0.3   VAX-11/730, MicroVAX I, VAXstation I
  0.6   VAX-11/750
  0.9   MicroVAX II, VAXstation II, MicroVAX 2000, VAXstation 2000
  1.0   VAX-11/780
  1.5   VAX-11/785
  2.4   MicroVAX 3100, MicroVAX 3300, 3400
  2.7   VAXstation 3100/M30 & M40, VAXstation 3200, 3500, MicroVAX 3500, 3600
  2.8   VAX 6000-210
  3.5   MicroVAX 3100 M10e & M20e
  3.8   VAXstation 3100/M38 & M48, MicroVAX 3800, 3900, VAX 6000-310
  5.0   VAX 4000-200, VAXstation 4000-VLC, MicroVAX 3100 M30 & M40
  7.0   VAX 6000-410
  7.6   VAXstation 3100/M76
  8.0   VAX 4000-300
 10.0   MicroVAX 3100 M80
 12.0   VAXstation 4000/M60
 13.0   VAX 6000-510
 16.0   VAX 4000-400
 24.0   MicroVAX 3100 M90, VAX 4000-100, VAX 4000-500
 32.0   VAX 6000-610, VAX 4000-600
 32.7   VAXstation 4000/M90
 35.0   VAX 7000-610, VAX 10000-610

--
 Vance Haemmerle                              vance@vips.lpl.arizona.edu
 Support Systems Analyst, Senior              vance%toyvax@arizona.edu
 Lunar & Planetary Lab
 University of Arizona
From: carrato@mhinfo.UUCP (Tony Carrato)
Newsgroups: comp.sys.dec
Subject: Re: Can a non-DEC disk be the primary (boot) disk?
Date: 3 Jan 93 18:33:35 GMT
Reply-To: carrato@mhinfo.UUCP (Tony Carrato)
Organization: Mile-High Information Services, Inc.

In article <1992Dec29.162401.29264@eagle.lerc.nasa.gov> edsver4@cecil.lerc.nasa.gov writes:
>I've got a DECstation 5000 model 200 (currently running ULTRIX 4.2A) whose
>primary (boot) disk, rz0, is a 300MB disk originally supplied by DEC with the
>workstation.  The workstation also has two 1 GB disks which happen to be
>IMPRIMISes.  I would like to make one of the IMPRIMIS disks be the primary
>disk, since each release of ULTRIX gets bigger and bigger, and it no longer
>fits on my 300MB disk.  
>
>Jane Kramer			|     phone: 216-826-6737

Jane, you mention that ULTRIX no longer fits on a 300 Mbyte disk.  I suspect
part of the problem, perhaps even most, is that you are doing a basic
installation or, at least, taking the defaults for where various file systems
get put.  My suggestion would be that:

a) You go ahead and install ULTRIX with its root on rz0, the DEC disk.  That
gives you an easy installation.

b) Put other file systems, including the swap areas, /usr and /var on
the other drives.  A swap area on each of the Impris drives, /usr on one
and /var on the other would (without, I admit, seeing much about how
you are actually using the system) appear to balance your workload to
the drives.

c) When you newfs the Imprimis drives you need an entry in /etc/disktab
that describes the geometry of the drives and probably a patch to
scsi_data.c, which is used in building the kernel, in order to get the
most out of them.  Something I recommend pretty often is to require your
vendor to supply those to you or not buy the drives from them.  You
can see if you can still get it.  If not, the net is probably full of
people who've already brought the drives up and can supply that info.

d) On one of the new Imprimis drives, put a copy of the root file system
you are normally using, in an a partition on that drive, as a backup.
Be sure  to either config a kernel to understand it's booting from that
drive or always boot genvmunix from it.  Having a backup root
partition can make you look awfully smart sometime.

Hope this helps.

Tony

----------------------------------------------------------------------------
Tony Carrato				Mile-High Information Services, Inc.
carrato@mhinfo.com			(303) 721-0851
----------------------------------------------------------------------------
-- 
----------------------------------------------------------------------------
Tony Carrato				Mile-High Information Services, Inc.
carrato@mhinfo.com			(303) 721-0851
----------------------------------------------------------------------------
Newsgroups: comp.sys.dec
From: alan@nabeth.enet.dec.com (Alan Rollow - Alan's Home for Wayward Tumbleweeds.)
Subject: Re: Can a non-DEC disk be the primary (boot) disk?
Reply-To: alan@nabeth.enet.dec.com (Alan Rollow - Alan's Home for Wayward Tumbleweeds.)
Organization: Digital Equipment Corporation
Date: Wed, 30 Dec 1992 00:19:52 GMT


In article <1992Dec29.162401.29264@eagle.lerc.nasa.gov>, edsver4@cecil.lerc.nasa.gov (Jane Kramer) writes:
>
> [ The customer is trying an installation to a 3rd party disk. ]
>
>I then tried to load 4.3 from my TK50.  When the install program got to the 
>part where it wants to know which disk to load to, it showed all three of my 
>disks as options.  I chose rz2, my newly partitioned disk.  The install 
>program then balked, and said:
>
>	Unable to obtain device geometry for rz2.
>	This is not a supported system disk.
>
>I don't set up new disks everyday, and I've exhausted the "Disk Maintenance" 
>section of the "System and Network Management" volume.  Have I missed any step 
>in initializing the new disk? Or does the primary disk have to be a DEC disk?
>Any advice would really be appreciated.

Before ULTRIX V4 supported disks were known by the installation procedure
since some geometry information was desired by the mkfs(8) used to create
the initial root file system.  Starting in V4, a new I/O control was added,
DEVGETGEOM, that would allow a program to query a disk for it's geometry.
The installation procedure was modified to use this I/O control to get
the information.

Some disks put their geometry information in the places that the ULTRIX
drivers expect and you can perform an installation using these disks.
Other disks don't put their geometry inforation in the expected place
and the installation fails.  The message you're getting is the symtom
of this problem.  The solutions are:

1.  Once the standalone system is loaded, use the System Management
    option and edit the appropriate installation script so that it
    doesn't try to ask the disks it's geometry and uses one you give
    it instead.  The script to modify is install.1.

    It's worth noting that if the early part of the installation
    doesn't recognize the disk and can't get the geometry the later
    part of the installation that creates the /usr (and /var) file
    system(s) won't work either.

2.  Do enough installation on a supported disk to get a working system
    up and then move what file system you want on the other disk to
    that disk.
>
>Thanks.
>-- 
>
>-----------------------------------------------------------------------------
>Jane Kramer
>
--
Alan Rollow				alan@nabeth.cxo.dec.com
From: collum@paradise1.ncd.com (Jim Collum)
Newsgroups: comp.sys.dec
Subject: RZ55 drive on other systems
Date: 21 Dec 92 18:03:39 GMT
Organization: Network Computing Devices, Mt. View, CA, USA

By default, the RZ55 is set up not to spin up on power-up.  Does anyone
know which jumper controls this?  I need it to spin up on power up so
I can use this on a non DEC system.


		thanks
		jim collum

Xref: sparky comp.sys.dec:6648 comp.unix.ultrix:9119
From: pavlov@niktow.canisius.edu (Greg Pavlov)
Newsgroups: comp.sys.dec,comp.unix.ultrix
Subject: Re: How do I attach an RA81 to a DECsystem 5400?
Date: 30 Dec 92 14:28:38 GMT
Followup-To: comp.sys.dec,comp.unix.ultrix
Organization: Canisius College, Buffalo NY. 14208

In article <1992Dec29.212620.19060@blaze.cs.jhu.edu>, bogstad@blaze.cs.jhu.edu (Bill Bogstad) writes:
> 
> 	I've got a couple of RA81s which used to be used on a now defunct
> VAX 8530 which I would like to use.  I've been digging through the manuals
> for our 5400 and it appears that I can probably attach these drives; but I
> will need a KDA50 controller to do so.  Can somebody tell me if this is
> correct and if there is anything else that I need to worry about (the rev of
> the KDA50 for example)? .....  Will I
> have any problems with the MSCP implemented by the KDA50 controller versus
> that used by the DSSI/RF disk combination?.  Can I put a KDA50 in a 210QS
> package?  What should I pay for a used KDA50?
> 

  Yes, you will need a KDA50 controller for your RA81s and yes, there is such
  a beast for the 5400.  Note that the KDA50 will a) consume two slots with two
  boards, b) make a third useless, c) consume a fair amount of power, and d),
  cost a fair amount of money.

  A new KDA50 is apx. $6,000 "list price", more for "standard price" (e.g., one
  year's maintenance included).  Asking price for used units seems to be all
  over the map, from $400 to $1500 or so.  I assume that there are reasons for
  this range, e.g., rev. levels, etc.  I would worry about the rev level for
  two reasons, one optional:  a) bug fixes, b) support by DEC (if you plan to
  put this under maintenance). 

  I am not 100% sure what your concern re MSCP was, but:  we had a 5400 with
  a mix of DSSI and RA disks (it had two KDA50's in it) and everything worked
  fine. But we dumped the mess first chance we got: replaced the KDAs and the
  RAs with third-party SCSI and disks.  Much much cheaper to operate. 

  greg pavlov
  pavlov@fstrf.org
From: kong@ece.ucdavis.edu (Timothy Kong)
Newsgroups: comp.sys.dec
Subject: instruction trace generator wanted
Date: 22 Dec 92 05:09:14 GMT
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science
Originator: kong@maple.eecs.ucdavis.edu

Can anyone suggest ways/tools to generate program traces on the
DECstation?  I looked at pixie, but it only gives basic block
execution frequencies.  The -itrace option on my version of pixie
doesn't seem to do anything.

Also, does anyone know of any publicly available cache simulators?

Thanks very much.

Timothy Kong
kong@eecs.ucdavis.edu
Newsgroups: comp.sys.dec,vmsnet.pdp-11
From: rflukes@ccu.umanitoba.ca (Richard F. Lukes)
Subject: FORSALE: SDI Cables for RA60,RA80 & RA81
Organization: University of Manitoba, Winnipeg, Canada
Date: Sun, 27 Dec 1992 20:32:18 GMT

I have two BC26V-12 cables plus a mounting panel which I would like
to sell.  Best offer takes them.  Willing to sell separately.

Thanks
--Rich
-- 
Richard F. Lukes                    rflukes@ccu.UManitoba.CA
Computer Science Department         (or rflukes@ccm.UManitoba.CA)
University of Manitoba
WORK: (204)-474-8696                HOME: (204)-257-6701
From: mrr@cl.msu.edu (Mark Riordan)
Newsgroups: comp.sys.dec
Subject: Table of VUPs wanted
Date: 23 Dec 92 22:54:24 GMT
Organization: Michigan State University
NNTP-Posting-Host: scss3.cl.msu.edu
X-Newsreader: TIN [version 1.1 PL6]

Hello.  This may be a FAQ, but where can I find a table of
DEC VAX CPU model number vs. VUPs?  

Barring that, can anyone tell me the VUPs rating of the
VAX 4000-600 and the older VAX 6000-310?
I could probably dig up the information from old DEC literature
in my office and by logging into DEC's Electronic Store,
but it would be painful.

Thanks!

Mark Riordan   mrr@scss3.cl.msu.edu
Newsgroups: comp.sys.dec