From: Chuck McManis <cmcmanis(a)mcmanis.com>
>Hello all, I've got a VT340 that is very fuzzy. (blurry) I'd like to try
>and refocus it but I don't have the maintenance manual for this
terminal.
>Does anyone have any suggestions on where to start (well I'm going to
start
>by seeing if the yoke has slipped backward on the tube neck, but other
than
>that)
The focus pot is part of the flyback as is the HV adjust. I believe the
Yoke
is bonded on that tube so movement is unlikely.
Allison
Same way you would for floppy only slower.
I'd make a bootable floppy first and put the DU/MU drivers
on it plus anything else you need as RX50 is has enough room for
a useable system. Then I think, you need DUP and BUP on there.
I have the capability but I backup to RL02 as it's much faster.
Also that RD54 (159mb) will likely be partitioned into 5 drives
as RT-11 can only address up to 32mb disks.
Allison
From: emanuel stiebler <emu(a)ecubics.com>
>I have rd54 & rx50 & tk70 in a system running rt11 5.4
>
>How can I make an bootable backup tape of the system drive ?
>
>cheers & thanks,
>emanuel
>
From: Jay West <west(a)tseinc.com>
>Several bugs were found in the list archives at www.classiccmp.org and
these
>have all been fixed to the best of my knowledge. If anyone sees anything
>further, please let me know asap.
Jay, the email address for me is changed. I was getting burried in
UCE/SPAM
so the replacement is kb1gmx(a)qsl.net.
Allison
From: Jeff Hellige <jhellige(a)earthlink.net>
> Here's a question somewhat related. As mentioned previously,
>I had two Maxtor XT-8380E hard disks in my MicroVAX II, but removed
>one of them to put the TK-50 in the machine. I've never gotten the
>TK-50 working correctly though and would like to use the second hard
>disk to back up the data that's on the one that is still in the
>machine. It is running VMS 4.6. What is the best way of mirroring
>the first drive on the second, regardless of what might be on the
>second? I'll likely pull the second drive back out after copying the
>data over to it. Without any kind of media or a working TK-50, this
>is really the only option I have for backing up the data and
>restoring it in case of a problem later on.
Easy run INIT the target disk and run standalone backup with /image
>from dua0: to duan: I generally do that. You can close the OS that
way too but only if you dont fully configure it first. Run HELP for
details.
Allison
Allison
We spent a lot of time testing the classiccmp mailing list - couldn't find a
single problem. There were one or two people who said they were getting the
digests twice, but they never gave me details. The only thing I can think
of, is that they were having problems with their pop mail session to their
ISP? If you start to download your mailbox of say 50 messages, and the
connection is lost (not the internet connection, but the pop session), the
server will re-transmit the entire batch so you'll keep getting those
messages over again until a complete sucessful download occurs - then it
will mark them as deleted on the server end. Again, this would be an issue
with the ISP, not us. If anyone still has problems or can supply further
details, please let me know.
Several bugs were found in the list archives at www.classiccmp.org and these
have all been fixed to the best of my knowledge. If anyone sees anything
further, please let me know asap.
Regards,
Jay West
From: emanuel stiebler <emu(a)ecubics.com>
>> I'd make a bootable floppy first and put the DU/MU drivers
>> on it plus anything else you need as RX50 is has enough room for
>> a useable system. Then I think, you need DUP and BUP on there.
>> I have the capability but I backup to RL02 as it's much faster.
>
>My intention was to get rid of the floppy drive. (And get a smaller
>system this way)
>What I was (probably ;-) really asking,
>if there is anything like the BRU & SAVESET combination we know
>from RSX11.
I thought I mentioned BUP, yes it did.
Allison
Browsing the surplus stores today - came across three things I don't have
any interest in... maybe someone does - if so, email me.
Calcomp 1034 (Or was it 1038?) plotter. This thing is BIG. Appears to be in
good cosmetic shape, have no idea if it works or not.
AT&T PC 6300
Something called an AT&T 6386 (or something like that) WGS. Noticed a few
recent posts on the list about this machine too.
Jay West
Jeff Hellige <jhellige(a)earthlink.net> wrote:
> EDS (my mistype) is Ross Perot's company and they now have a
> signed contract with the Dept. of Navy to take over the LANs and
> pretty much every other aspect of computers and thier maintainance.
> NMCI is the arm of the company doing it. The contract is for an
> astronimical amount of money and the closest comparison is the Borg:
> they are coming in, taking all exisiting equipment, replacing it with
> a 'one size fits all' desktop and charging you handsomely for both
> the replacement and every little thing you want to do with it.
Y'all might want to wander over to alt.tasteless and look for a thread
titled something like "Near Ape Shit At Work Today". Seems someone
did not like his Mac being replaced and so attacked the EDS staffer(s)
who came to do the deed with a hacksaw. However he was not
successful.
-Frank McConnell
On Apr 6, 18:12, John Honniball wrote:
> Are you thinking of the Pertec magnetic tape interface? I
> have a Cifer front-loading half-inch magtape drive that
> (I'm told) has the Pertec interface. It has two large
> 50-way ribbon cables coming out of the back.
>
> So, much as I hate to say "Me Too", I'd also like to find
> out more about the Pertec interface. Was there ever a PC
> ISA-bus card for this? Or a VME (Sun-3) card?
I'm sure there are VME cards. Dunno about ISA.
I've posted the pinout for the 2 x 50-way interface on my website at
http://www.dunnington.u-net.com/public/pertec.ps. It's a PostScript file.
I can't remember where the information originally came from, it was either
an Emulex TC02 manual or the manual for my tape deck.
--
Pete Peter Turnbull
Network Manager
Dept. of Computer Science
University of York
Joe <rigdonj(a)intellistar.net> wrote:
> FWIW I do consider the 9000 520 an odd machine. Perhaps unusual would be
> a better term. I've been collecting HP computers for a good number of years
> and I've never seen one before. I found (and bought) one a couple of weeks
> ago. Before that the only person that I know of that actually had one was
> Frank McConnell. My research indicates that there were a lot 520s used by
> the US navy and some of it's subcontractors but few elsewhere. Even my
> contacts at HP tell me that the 520 was problematic and was very late
> getting into production and was a commercail failure. Despite the large
> number of them used by the US Navy, very few managed to get into the
> surplus market. I couldn't find a single surplus dealer that had one or
> that even knew what they were.
The 9000/500 may have been a commercial failure, but HP learned a lot
>from it -- its I/O bus (later known as CIO I think) was adopted by the
PA-RISC 9000/800 (and 3000/900) machines. I expect this meant the
machines had trade-in value for their I/O cards (as well as the gold
and copper in the CPU, IOP, and memory cards, which are all
surprisingly heavy from the copper core and shiny from the
characteristic HP gold plating).
The packaging is interesting, especially on the CPU/IOP/memory cards:
the boards don't have sockets for the ICs. Instead, there is a cavity
in the non-conductive board material, exposing the copper sheet at the
core of the board. The IC substrate is bound to this copper core, and
its bond-out wires are soldered to the traces on the board. Then a
lid is fitted over the cavity(ies) to protect the ICs and bond-out
wires. This was done to carry heat away from the ICs, which ran from
a 16MHz clock and did a pretty good job of turning electricity into
heat.
It was also HP's first entry into the Unix market. The 520 could also
be a BASIC workstation (a high-powered multiprocessor replacement for
the 9845!) but I have not seen any configured that way.
It was also HP's last big stack machine, or at least the last one
that made it to market. (Maybe Lee Courtney can tell us more about
Vision.)
HP contracted with The Wollongong Group to provide TCP/IP transport
and application software for HP-UX v5 on these in the mid-to-late
1980s. I started working at TWG in 1989, by which time engineering
support for the product was over, and soon found that from their point
of view, 9000s and 3000s were all the same and so I got to support
that product as well. That was my first introduction to it.
Then I found the FOCUS machine instruction set manual in TWG's
library. Oh my. It's a 32-bit stack machine, sort of a big 3000.
Oh my.
Then I got to investigating a remsh crash that took me deep into the
kernel. That was how I became a TCP/IP stack internals kind of guy.
My memories are dim and distant (TWG ended support for the 9000/500s
in early 1994 I think, due to no sales and no contract renewals), but
most of the customers I talked to were either US military or
contractors.
Its Unix port has some oddities. It was ported on top of another HP
OS called SUNOS that provided low-level generic services to both BASIC
and HP-UX, and the AT&T filesystem was layered on top of an HP
filesystem structure called Structured Directory Format or SDF. SDF
makes itself visible by the absence of . and .. in directories -- ls
and open() will fake them as needed, but if your code opens the
directory and reads it they aren't there!
I don't think it has the concept of partitioning a disc into multiple
filesystems: one disc volume is one filesystem, no way around it.
Swap space is taken as needed from whatever free space is available on
at least the / volume, maybe others too. Strange but nice in its own
way.
-Frank McConnell
Curt Vendel <curt(a)atari-history.com> wrote:
> Old Odd Machine??? The HP 9000 K520 isn't that terribly old, I
But that's different iron, obviously named by someone with no sense of
what had gone before, or someone who thought that alphabet soup and a
few years would be enough to avoid confusion. The 9000 Series 520 aka
9020 aka 9000 Model 20 was one of the first machines to ship under the
9000 label, a 32-bit (potentially-)multiprocessing stack architecture
>from 1982.
Take a look at <http://www.reanimators.org/hp/> for some pictures of
an Integral (top) and my 9000/520 (bottom). I think you will agree,
it's not what you're thinking of.
-Frank McConnell
Our hospital now considers any computers less than 300 MHz as "old" and
needing to be replaced. Most of our software venders now say that anything
less than that is not acceptable for their applications, most also want 64
Mb of memory.
Our department still uses 486/33's and WordPerfect 5.1 for word processing
and they are very reliable.
mike
mmcfadden(a)cmh.edu
>From: Dave McGuire <mcguire(a)neurotica.com>
>Subject: Re: HP 9000 520
>
> I've been noticing a very disturbing trend...anything that isn't an
>overclocked Intel box is "old" or "legacy".
>
> For those of us who care about the quality of what we put on our
>desktops (and in our computer rooms), this is pretty frightening.
>
> -Dave McGuire
>>Thanks Allison! I got the cover off and found the adjustment side of
the
>>terminal (left side looking at it from the front) and the focus is a
screw
>>that goes into what looks like an HV transformer. I've adjusted it to
be
>>razor sharp, now what do I use to "lock it down" ? What is that stuff
that
>>looks like nail polish called?
>>
>>--Chuck
It might just be nail polish. I often use that as it's handy and
available cheap
at the corner store.
Fashon sense demands I make a point of using leftover last years colors.
;)
Allison
On Fri, 6 Apr 2001 03:28:22 -0700 Mike Ford <mikeford(a)socal.rr.com>
writes:
> >I can just imagine the Pro-M$ History aka... propoganda!!!
>
> Yeah I can just see the entry lobby with a copy of PC DOS 1.0 next
> to the original source.
You forgot to add that the accompanying blurb would explain how
Bill G. wrote it (single-handedly) over a 72 hour period after
IBM requested he write them an OS. :^/
________________________________________________________________
GET INTERNET ACCESS FROM JUNO!
Juno offers FREE or PREMIUM Internet access for less!
Join Juno today! For your FREE software, visit:
http://dl.www.juno.com/get/tagj.
I was in a local electronic surplus store today and bought some old
laptops at what I consider a good price. 2 Grid 1520s, a Grid 1755,
a Commodore C386SX, a DEC PCP11, and an External SCSI HD for $75
All lacking power supplies tho. I had power packs for the 1520s and
they're both working but one has the same problem that Mike Ford has
with his Grids- password protected. It's now sitting unassembled on my
work table while I search for the battery to see if shorting or removing that
will get rid of the P-W. While I have programs to zap the Award and AMI
BIOS' ,unfortunately this is a Phoenix.
The Grids all have a socket also for a 16v transformer and it appears to
be the same as the DECs 15v so I am looking for either a Grid or DEC
transformer. The Commodore has an 8pin mini socket for power and a
16v battery.
In examining the 1755 and DEC closer I see that they are identical except
for color. Who would have made these for Grid and DEC ? Kyocera ?
larry
Reply to:
lgwalker(a)look.ca
You know, I've signed-up for that a few times and *never* received my
handbook. I get the advertising, but no book. If anyone actually does get a
handbook, I'd like to know...
Rich
-----Original Message-----
From: Mike Ford [mailto:mikeford@socal.rr.com]
Sent: Thursday, April 05, 2001 4:36 AM
To: classiccmp(a)classiccmp.org
Subject: Free PC handbook
I got this in the mail today, and I am just passing it on. I don't know
what happens when the registration gets filled out without a VIP code, but
its a nice free book if it works.
http://www.advantechdirect.com
My VIP code is NCE011IAG20011B42584 which looks like it is just my code,
but if it is its not smart enough to already know who I was. I suggest not
filling out the reg unless you have an interest in the products, industrial
computers, rack mount, etc. If you are a legitamite user/buyer of this kind
of stuff I can't see them griping about the offer being passed around.
The free book is the neat PC Handbook, with all the facts on PC parts etc.
In a message dated 4/5/01 8:36:58 PM Pacific Daylight Time,
jpero(a)sympatico.ca writes:
> any
> suggestions for inexpensive s-video cables?
This is a funny thread. Going around in a circle
I have been using cheap ADB cables for S-video cables in my video work. I
have found all the ADB cables I need for $1 each at the Eugene, Oregon
Goodwill store.
Paxton
Portland, OR
Hi Curt Vendel, you wrote on 4/6/01 8:32:07 PM:
A HP 9000 Model 520 would be roughly 15 years old.
I administered a couple about 10 years ago. ran
HPUX 5.x. Great systems, reliable.
A newer Model 800 series K5xx would be cool to have as well.
So, the question is, exactly which model is it?
kelly
>Joe,
>
> Old Odd Machine??? The HP 9000 K520 isn't that terribly old, I
>installed
>one of those with HPUX 11.3 at GT Interactive in Manhattan back in 95' A
>damn good and powerful machine.
>
>
>Curt
>
>
>
>Joe wrote:
>
> FWIW there were two of these for sale at the auction at the Goddard
>Space
> Flight Center in Huntsville, Alabama this past week. A guy that I know
>went
> to the auction and I asked him to try and pick them up for me but I don't
> know if he did or not. He should be back in a day or two and then I'll
> know. The point is there's still lots of these old odd machines around if
> someone is willing to search for them.
>
> Joe
Well here it is......
I hooked the Vax up to my IBM Model 80 with Tera Term. Anybody have any
other favorite terminal programs?
What should I be able to see from the below info?
>>>show mem
Memory 0: 00000000 to 003FFFFF, 4MB, 0 bad pages
Memory 1: 00400000 to 00BFFFFF, 8MB, 0 bad pages
Memory 2: 00C00000 to 01BFFFFF, 16MB, 0 bad pages
Memory 3: 01C00000 to 02BFFFFF, 16MB, 0 bad pages
Total of 44MB, 0 bad pages, 118 reserved pages
>>>show dev
DSSI Node 0 (TSD4A)
-DIA0 (RF71)
DSSI Node 1 (R5ARYC)
-DIA23 (RF35)
DSSI Node 2 (R5DKVC)
-DIA20 (RF35)
DSSI Node 7 (*)
UQSSP Tape Controller 0 (774500)
-MUA0 (TK70)
Ethernet Adapter
-ESA0 (08-00-2B-12-41-19)
>>>show qbus
Scan of Qbus I/O Space
-20000120 (760440) = 0080 (300) DHQ11/DHV11/CXA16/CXB16/CXY08
-20000122 (760442) = F081
-20000124 (760444) = DD18
-20000126 (760446) = 0140
-20000128 (760450) = 0000
-2000012A (760452) = 0000
-2000012C (760454) = 8000
-2000012E (760456) = 0000
-20001940 (774500) = 0000 (260) TQK50/TQK70/TU81E/RV20/KFQSA-TAPE
-20001942 (774502) = 0BC0
-20001F40 (777500) = 0020 (004) IPCR
Scan of Qbus Memory Space
>>>help
Following is a brief summary of all the commands supported by the
console:
UPPERCASE denotes a keyword that you must type in
| denotes an OR condition
[] denotes optional parameters
<> denotes a field that must be filled in
with a syntactically correct value
Valid qualifiers:
/B /W /L /Q /INSTRUCTION
/G /I /V /P /M
/STEP: /N: /NOT
/WRONG /U
Valid commands:
DEPOSIT [<qualifiers>] <address> [<datum> [<datum>]]
EXAMINE [<qualifiers>] [<address>]
MOVE [<qualifiers>] <address> <address>
SEARCH [<qualifiers>] <address> <pattern> [<mask>]
SET BFLG <boot_flags>
SET BOOT <boot_device>[:]
SET HOST/DUP/DSSI <node_number> [<task>]
SET HOST/DUP/UQSSP </DISK | /TAPE> <controller_number> [<task>]
SET HOST/DUP/UQSSP <physical_CSR_address> [<task>]
SET HOST/MAINTENANCE/UQSSP/SERVICE <controller_number>
SET HOST/MAINTENANCE/UQSSP <physical_CSR_address>
SET LANGUAGE <language_number>
SHOW BFLG
SHOW BOOT
SHOW DEVICE
SHOW DSSI
SHOW ETHERNET
SHOW LANGUAGE
SHOW MEMORY [/FULL]
SHOW QBUS
SHOW RLV12
SHOW UQSSP
SHOW VERSION
HALT
INITIALIZE
UNJAM
CONTINUE
START <address>
REPEAT <command>
X <address> <count>
FIND [/MEMORY | /RPB]
TEST [<test_code> [<parameters>]]
BOOT [/R5:<boot_flags> | /<boot_flags>] [<boot_device>[:]]
NEXT [count]
CONFIGURE
HELP
>>>boot
No default boot device has been specified.
Available devices.
-DIA0 (RF71)
-DIA23 (RF35)
-DIA20 (RF35)
-MUA0 (TK70)
-ESA0 (08-00-2B-12-41-19)
Device? [ESA0]: dia0
(BOOT/R5:0 DIA0)
2..
-TSD4A$DIA0
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
OpenVMS (TM) VAX Version V6.2 Major version id = 1 Minor version
id = 0
%DECnet-I-LOADED, network base image loaded, version = 05.08.00
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM)
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 04-APR-2001
%SYSINIT, primary PAGEFILE.SYS not found; system initialization
continuing
$! Copyright (c) 1995 Digital Equipment Corporation. All rights
reserved.
%STDRV-I-STARTUP, OpenVMS startup begun at 4-APR-2001 00:02:05.12
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\B$\
>>> Starting TCPIP ... <<<
%MOUNT-I-MOUNTED, USER mounted on _$1$DIA20: (R5DKVC)
%MOUNT-I-REBUILD, volume was improperly dismounted; rebuild in progress
%MOUNT-I-MOUNTED, USER2 mounted on _$1$DIA23: (R5ARYC)
%MOUNT-I-REBUILD, volume was improperly dismounted; rebuild in progress
%DCL-S-SPAWNED, process SYSTEM_1 spawned
%SET-I-NEWAUDSRV, identification of new audit server process is 0000010A
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:24.51 %%%%%%%%%%%
Operator _ALERTN$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:25.13 %%%%%%%%%%%
Operator status for operator _ALERTN$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER,
SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9,
OPER10,
OPER11, OPER12
%LICENSE-W-TERM, UNICM 99302-323 License has terminated
%SYSTEM-W-PROXYCONVERT, old-format proxy database needs to be converted
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:38.55 %%%%%%%%%%%
Failed logfile operation on file _ALERTN$OPA0:
SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:39.15 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:39.16 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
%LICENSE-E-TERM, UNICM 99302-323 License has terminated
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:39.16 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
%QMAN-W-CRITCLSPACE, free more space on _$1$DIA0 - allocated only 20% of
520 blo
cks needed for full journal file
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:39.17 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:40.21 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
%QMAN-E-OPENERR, error opening
$1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]SYS$QUEUE_MANAGE
R.QMAN$JOURNAL;1
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:40.21 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
-RMS-F-FUL, device full (insufficient space for allocation)
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:40.22 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
-SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:40.50 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
%QMAN-E-NODISKSPACE, disk space not available for queue manager to
continue
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:40.51 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
-QMAN-I-FREEDISK, free up 1044 blocks on disk _$1$DIA0
Copyright (c) Digital Equipment Corporation 1993, 1994. All rights
reserved.
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:42.69 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:42.87 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:42.94 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
%SECSRV-I-SERVERSTARTINGU, security server starting up
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:43.81 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now
starting u
p
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:44.43 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:46.76 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:48.98 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%SHOW-F-WRITEERR, error writing
SYS$SYSROOT:[SYS$STARTUP]NET$STARTUP_CHECKPRIVS.
DAT;4
-RMS-F-FUL, device full (insufficient space for allocation)
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:53.80 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:56.42 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:03:58.97 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:01.75 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
>>> Executing SYSTARTUP_VMS.COM for VMS 6.2 startup procedure <<<
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:04.08 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) and security audit (SECURITY) on ALERTN,
system id: 62
474
Auditable event: Audit server starting up
Event time: 4-APR-2001 00:04:02.41
PID: 00000103
Username: SYSTEM
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:04.46 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file removal
Event time: 4-APR-2001 00:04:03.73
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file: $1$DIA0:[SYS0.SYSCOMMON.SYSEXE]ANALIMDMP.EXE;1
INSTALL flags: /PRIVILEGED
Privileges: CMKRNL,CMEXEC
%MOUNT-F-VOLALRMNT, another volume of same label already mounted
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:06.23 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%MOUNT-F-VOLALRMNT, another volume of same label already mounted
%SYSGEN-W-OPENIN, error opening $1$DIA20:[000000]PAGEFILE2.SYS; as input
-RMS-E-FNF, file not found
>>> Disk Startup Complete <<<
>>> Disk startup procedure completed <<<
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:09.01 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
Copyright (c) 1995 Digital Equipment Corporation. All rights reserved.
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:12.38 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%AMDS-I-RMSTART, starting Data Provider processing for this node
%AMDS-I-LOADSECDB, loading security database
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:14.57 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%AMDS-S-RMSUCCESS, Data Provider startup successful
>>> Terminals Startup Complete <<<
>>> Terminals startup procedure completed <<<
>>> Accounting disable procedure completed <<<
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:17.13 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:19.09 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:19.05
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file:
$1$DIA0:[SYS0.SYSCOMMON.SYSLIB]UCX$ACCESS_SHR.EXE;3
INSTALL flags: /OPEN/SHARED
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:19.78 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:20.07 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:20.04
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file: $1$DIA0:[SYS0.SYSCOMMON.SYSMSG]UCX$MSG.EXE;3
INSTALL flags: /OPEN/SHARED
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:20.96 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:20.92
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file:
$1$DIA0:[SYS0.SYSCOMMON.SYSLIB]UCX$IPC_SHR.EXE;2
INSTALL flags: /OPEN/SHARED
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:21.94 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:21.90
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file:
$1$DIA0:[SYS0.SYSCOMMON.SYSLIB]UCX$RPCXDR_SHR.EXE;3
INSTALL flags: /OPEN/SHARED
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:22.30 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:22.90 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:22.86
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file:
$1$DIA0:[SYS0.SYSCOMMON.SYSLIB]UCX$CFS_SHR.EXE;3
INSTALL flags: /OPEN/SHARED/PROTECTED
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:23.93 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:23.89
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file: $1$DIA0:[SYS0.SYSCOMMON.SYSEXE]UCX$UCP.EXE;3
INSTALL flags: /OPEN/HEADER_RESIDENT/SHARED
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:24.87 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:28.27 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:31.01 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:33.59 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:33.55
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file:
$1$DIA0:[SYS0.SYSCOMMON.SYSEXE]UCX$BIND_SERVER.EXE;3
INSTALL flags: /OPEN/HEADER_RESIDENT/SHARED/PRIVILEGED
Privileges: OPER
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:34.05 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:34.58 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:34.54
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file:
$1$DIA0:[SYS0.SYSCOMMON.SYSEXE]UCX$BIND_SERVER_XFER.EX
E;2
INSTALL flags: /OPEN/HEADER_RESIDENT/SHARED/PRIVILEGED
Privileges: OPER
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:36.34 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:36.30
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file: $1$DIA0:[SYS0.SYSCOMMON.SYSEXE]UCX$FTPC.EXE;3
INSTALL flags: /OPEN/HEADER_RESIDENT/SHARED/PRIVILEGED
Privileges: PSWAPM,OPER
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:36.54 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - ERROR ACCESSING ERROR LOG FILE
%RMS-F-FUL, device full (insufficient space for allocati
%SYSTEM-W-DEVICEFULL, device full; allocation failure
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:36.60 %%%%%%%%%%%
Message from user SYSTEM on ALERTN
ERRFMT - DELETING ERRFMT PROCESS
ERROR LOG FILE UNWRITABLE
TO RESTART ERRFMT PROCESS, USE "@SYS$SYSTEM:STARTUP ERRFMT"
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:37.73 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:37.69
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file: $1$DIA0:[SYS0.SYSCOMMON.SYSEXE]UCX$FTPD.EXE;3
INSTALL flags: /OPEN/HEADER_RESIDENT/SHARED/PRIVILEGED
Privileges: SYSNAM,DETACH,WORLD,BYPASS
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:39.47 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:39.44
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file: $1$DIA0:[SYS0.SYSCOMMON.SYSEXE]UCX$FTP.EXE;3
INSTALL flags: /OPEN/HEADER_RESIDENT/SHARED/PRIVILEGED
Privileges: PSWAPM,OPER
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:41.00 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:40.97
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file:
$1$DIA0:[SYS0.SYSCOMMON.SYSLIB]UCX$LPD_SHR.EXE;3
INSTALL flags: /OPEN/SHARED
%%%%%%%%%%% OPCOM 4-APR-2001 00:04:41.68 %%%%%%%%%%%
Message from user AUDIT$SERVER on ALERTN
Security alarm (SECURITY) on ALERTN, system id: 62474
Auditable event: Installed file addition
Event time: 4-APR-2001 00:04:41.65
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: $1$DIA0:[SYS0.SYSCOMMON.][SYSEXE]INSTALL.EXE
Installed file:
$1$DIA0:[SYS0.SYSCOMMON.SYSEXE]UCX$LPD_RCV.EXE;3
INSTALL flags: /PRIVILEGED
Privileges: BYPASS
%%%%%%%%%%% OPCOM 4-APR-2001 00:05:40.50 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
%QMAN-E-NODISKSPACE, disk space not available for queue manager to
continue
%%%%%%%%%%% OPCOM 4-APR-2001 00:05:40.52 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
-QMAN-I-FREEDISK, free up 1044 blocks on disk _$1$DIA0
%%%%%%%%%%% OPCOM 4-APR-2001 00:07:40.50 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
%QMAN-E-NODISKSPACE, disk space not available for queue manager to
continue
%%%%%%%%%%% OPCOM 4-APR-2001 00:07:40.52 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
-QMAN-I-FREEDISK, free up 1044 blocks on disk _$1$DIA0
%%%%%%%%%%% OPCOM 4-APR-2001 00:09:40.51 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
%QMAN-E-NODISKSPACE, disk space not available for queue manager to
continue
%%%%%%%%%%% OPCOM 4-APR-2001 00:09:40.52 %%%%%%%%%%%
Message from user QUEUE_MANAGE on ALERTN
-QMAN-I-FREEDISK, free up 1044 blocks on disk _$1$DIA0
?02 EXT HLT
PC = 82221B4D
>>>show boot
DIA0
>>>
Chad Fernandez
Michigan, USA
Does anyone know what a Kinetic Systems Corp model D1391 dual wide Q-bus
board is?
It has two 40 pin connectors, they look kind of like the M3107 (8 port
async) but they connect to resistor packs so I'm thinking either a parallel
port or bus extender. There are several DS8833 chips (Nat'l Semi) and what
looks like a CSR switch pack. An M7951 clone perhaps?
--Chuck
In a message dated 4/6/01 5:11:54 PM Pacific Daylight Time,
ecloud(a)bigfoot.com writes:
> Yep that monitor looks a lot like one I have... but mine has a logo
> that says "LexiData", I think. It has 10 BNC connectors (separate
> sync, and a set of pass-through connectors I guess).
>
LexiDatas are more of a RGB separate sync monitor. Very similar chassis.
I bought and sold one of the Sun 1s in 1988. Got it surplus from a local
computer dealer, I think it was a lease return, and sold it for $500 to the
computer department of Stanford University. They were still using some of
them.
Thanks for the pictures. It brought back memories.
Paxton
Portland, Oregon
Hello all, I've got a VT340 that is very fuzzy. (blurry) I'd like to try
and refocus it but I don't have the maintenance manual for this terminal.
Does anyone have any suggestions on where to start (well I'm going to start
by seeing if the yoke has slipped backward on the tube neck, but other than
that)
--Chuck
Umm, this story is also something around 20 or more years old, too, based in
my recollection in the universal jfvts (Jennings Family Vehicle Time Scale).
We had our Volkswagon Quantum then, meaning I was at most 14 or so, and the
story was old already, I think I happened in the mid-80's...
Will J
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
