27 Mar
2020
27 Mar
'20
12:57 a.m.
I have obtained a MicroVAX 3100-80 with a Storageworks pizza box, a CD-ROM drive, a tape
drive, some cables and no monitor.
It powers on, does not smoke or explode. The 8 LEDs at the back settle down to all on
except 2 and 3 counting from zero on the right. I can hear a hard disk spin up.
The cables include two MMJs. I have a PC with a 9-pin female serial connector. It runs
Linux.
The first two of many questions: does the ?0? connector connect to the console? What
exactly do I need to do to connect the PC?s serial port to the MMJ cable? Note: I have
passable soldering skills.
Next question will be about the BNC connector and networking. One thing at a time.
Here are some pictures: https://photos.app.goo.gl/KduorZEimMQ73bMdA
Thanks in advance
Supratim
---
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
27 Mar
27 Mar
1:02 a.m.
Sorry the PC?s 9-pin serial connector is male.
On Mar 26, 2020, at 7:57 PM, Supratim Sanyal
<supratim at riseup.net> wrote:
I have obtained a MicroVAX 3100-80 with a Storageworks pizza box, a CD-ROM drive, a tape
drive, some cables and no monitor.
It powers on, does not smoke or explode. The 8 LEDs at the back settle down to all on
except 2 and 3 counting from zero on the right. I can hear a hard disk spin up.
The cables include two MMJs. I have a PC with a 9-pin female serial connector. It runs
Linux.
The first two of many questions: does the ?0? connector connect to the console? What
exactly do I need to do to connect the PC?s serial port to the MMJ cable? Note: I have
passable soldering skills.
Next question will be about the BNC connector and networking. One thing at a time.
Here are some pictures: https://photos.app.goo.gl/KduorZEimMQ73bMdA
Thanks in advance
Supratim
---
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
1:06 a.m.
On 3/26/20 7:57 PM, Supratim Sanyal wrote:
I have obtained a MicroVAX 3100-80 with a Storageworks
pizza box, a
CD-ROM drive, a tape drive, some cables and no monitor.
It powers on, does not smoke or explode. The 8 LEDs at the back settle
down to all on except 2 and 3 counting from zero on the right. I can
hear a hard disk spin up.
The cables include two MMJs. I have a PC with a 9-pin female serial
connector. It runs Linux.
The first two of many questions: does the ?0? connector connect to the
console? What exactly do I need to do to connect the PC?s serial port to
the MMJ cable? Note: I have passable soldering skills.
Next question will be about the BNC connector and networking. One thing
at a time.
Very cool! Those are wonderful systems.
The console is on port 3. Connect it to your Linux box via the
appropriate chain of adapters. If you don't get any output, insert a
null modem into the mix and try again.
(Yes, I know the DTE/DCE rules. The above approach is by far the
quickest way to get something talking if you know it's only doing 2/3/7
anyway.)
Here are some
pictures:?https://photos.app.goo.gl/KduorZEimMQ73bMdA
Beautiful!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
1:10 a.m.
On Mar 26, 2020, at 8:06 PM, Dave McGuire <mcguire
at neurotica.com> wrote:
Dave - There is a MMJ to 25-pin cable on Amazon. Would the appropriate chain of adapters
then be this cable and then and 25-to-9 serial female?
On 3/26/20 7:57 PM, Supratim Sanyal wrote:
I have obtained a MicroVAX 3100-80 with a Storageworks pizza box, a
CD-ROM drive, a tape drive, some cables and no monitor.
It powers on, does not smoke or explode. The 8 LEDs at the back settle
down to all on except 2 and 3 counting from zero on the right. I can
hear a hard disk spin up.
The cables include two MMJs. I have a PC with a 9-pin female serial
connector. It runs Linux.
The first two of many questions: does the ?0? connector connect to the
console? What exactly do I need to do to connect the PC?s serial port to
the MMJ cable? Note: I have passable soldering skills.
Next question will be about the BNC connector and networking. One thing
at a time.
Very cool! Those are wonderful systems.
The console is on port 3. Connect it to your Linux box via the
appropriate chain of adapters. If you don't get any output, insert a
null modem into the mix and try again.
(Yes, I know the DTE/DCE rules. The above approach is by far the
quickest way to get something talking if you know it's only doing 2/3/7
anyway.)
Here are some pictures:
https://photos.app.goo.gl/KduorZEimMQ73bMdA
Beautiful!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA 
1:08 p.m.
On Thu, 26 Mar 2020, Dave McGuire wrote:
I think the most good looking part of that is the Storageworks pizza box.
I am used to the "bigger" variants that are either DEC or Compaq logo'ed
with the 4GB SCSI drives in those dark blue/grey/beige cases.
Fred
Here are some
pictures:?https://photos.app.goo.gl/KduorZEimMQ73bMdA
Beautiful!
5:27 p.m.
On 3/27/20 8:08 AM, Fred wrote:
I think the most good looking part of that is the Storageworks pizza box.
Oh yes, those are fantastic. We just got a few of those at LSSM not
long ago.
Here are some
pictures:?https://photos.app.goo.gl/KduorZEimMQ73bMdA
?Beautiful! I am used to the "bigger" variants that are
either DEC or Compaq logo'ed
with the 4GB SCSI drives in those dark blue/grey/beige cases.
Yes, those are great. The only issue with them is that their AC power
supplies have started dropping like flies, and while I can SEE the
capacitor that has failed, I cannot reasonably get to it to replace it.
There is a big metal cage, which doubles as a heat sink, over the
entire board that is soldered to it at several places.
We now have a stack of six that have failed.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
6:21 p.m.
On Fri, 27 Mar 2020, Dave McGuire wrote:
There is a big metal cage, which doubles as a heat
sink, over the
entire board that is soldered to it at several places.
We now have a stack of six that have failed.
Hmmmmm. That may have unlocked the mystery of what happened to the one I
had attached to my 4000/90A that I ended up virtualizing with SIMH. Just
went up and died one day and wouldn't power on. No smoke, no pop, just
powered itself off one day and wouldn't power back on. Tested everything
I could (power cord, plug on the shelf itself, etc). Short of busting it
I couldn't figure out how to get "in" to the power supply to poke around.
I kept all of the drives, but scrapped the shelf. :( It pained me to do
that. I try not to throw *anything* electronic away even if I think there
is a "whisper" of it being able to be repaired/salvaged for parts. I'm
sure everyone on list has got their "bacon" saved by being able to rob a
part from something that you kept around just in case ...
Fred
6:29 p.m.
On 3/27/20 1:21 PM, Fred wrote:
Urr? Why didn't you just get another power supply? They are readily
available cheaply, at least for awhile longer.
The typical failure mode is the "blink blink blink" of the power LED
as the switcher fails to start. If you open it up, one of the big
output capacitors will have swollen and barfed its guts out onto the board.
There is a big
metal cage, which doubles as a heat sink, over the
entire board that is soldered to it at several places.
?We now have a stack of six that have failed.
Hmmmmm.? That may have unlocked the mystery of what happened to the one
I had attached to my 4000/90A that I ended up virtualizing with SIMH.?
Just went up and died one day and wouldn't power on.? No smoke, no pop,
just powered itself off one day and wouldn't power back on.? Tested
everything I could (power cord, plug on the shelf itself, etc).? Short
of busting it I couldn't figure out how to get "in" to the power supply
to poke around.
I kept all of the drives, but scrapped the shelf. :( It pained me to
do that.? I try not to throw *anything* electronic away even if I think
there is a "whisper" of it being able to be repaired/salvaged for
parts.? I'm sure everyone on list has got their "bacon" saved by being
able to rob a part from something that you kept around just in case ...
Oh yes. :) And capacitors are a special case anymore; I have a large
(very large) stock of them at my lab. We draw from that at the museum
on every work day.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
28 Mar
28 Mar
12:54 a.m.
On 2020-03-27 17:27, Dave McGuire wrote:
On 3/27/20 8:08 AM, Fred wrote:
I think the most good looking part of that is the Storageworks pizza box.
Oh yes, those are fantastic. We just got a few of those at LSSM not
long ago.
I have a few and like them. One thing though. The rightmost bay can be
reconfigured for 5" wide stuff instead of the normal 3.5" (or whatever
size the normal bricks are). However, I have never seen what the
mounting hardware looks like if you want to mount something like a CD in
there. I've always just kept the CD laying on the bottom, but if anyone
have any details on how something larger was expected to be mounted, I
would be rather interested in hearing about it.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Here are some
pictures:?https://photos.app.goo.gl/KduorZEimMQ73bMdA
?Beautiful! 
27 Mar
27 Mar
1:11 a.m.
On Mar 26, 2020, at 7:57 PM, Supratim Sanyal
<supratim at riseup.net> wrote:
I have obtained a MicroVAX 3100-80 with a Storageworks pizza box, a CD-ROM drive, a tape
drive, some cables and no monitor.
It powers on, does not smoke or explode. The 8 LEDs at the back settle down to all on
except 2 and 3 counting from zero on the right. I can hear a hard disk spin up.
The cables include two MMJs. I have a PC with a 9-pin female serial connector. It runs
Linux.
The first two of many questions: does the ?0? connector connect to the console? What
exactly do I need to do to connect the PC?s serial port to the MMJ cable? Note: I have
passable soldering skills.
This should do the job, you just need to verify the pinouts. A pin insert/remove tool
might be a good investment to make adjustments in case the first choice of pinout turns
out to be not what you want.
Next question will be about the BNC connector and
networking. One thing at a time.
That is a 10Base2 connector. Next to it is an AUI connector. So if you have a 10Base2
repeater or switch, just run coax between the two. It most likely needs a T connector at
this end with a terminator on the T (or going to other stations if you have more). The
AUI connector could be used instead, for example if you have a 10BaseT transceiver that
might be convenient. Those are still sold; Amazon lists one from Unicom for $30.
Here are some pictures:
https://photos.app.goo.gl/KduorZEimMQ73bMdA
<https://photos.app.goo.gl/KduorZEimMQ73bMdA>
Nice!
paul
1:26 a.m.
Hello,
When I purchased a DEC 3000 with MMJ console connectors, before the MMJ
cables arrived, I created a makeshift connector by cutting off part of an
RJ-45 connector leaving 6 wires. Filed off the clip and smoothed all four
sides.
Wiring as follows for makeshift MMJ to DB9:
Pin 1 Blue DTR to Pin 6 DSR
Pin 2 Orange TX to Pin 2 RX
Pin 3 Black TX Gnd to Pin 5 GND
Pin 4 Red TX Gnd to Pin 5 GND
Pin 5 Green RX to Pin 3 TX
Pin 6 Yellow DSR to Pin 4 DTR
On DB9, leave 7, 8 and 9 unconnected (RTS, CTS and N/C).
Makeshift MMJ from front: Pins 1 thru 6
DB9 connector from front: Pins 1 thru 5 on top, Pins 6 thru 9 on bottom
Cable colors may differ depending on the RJ45 cable. Cable worked until the
real MMJ cable arrived.
HTH!
Regards,
Jason
On Thu, Mar 26, 2020 at 5:14 PM Paul Koning <paulkoning at comcast.net> wrote:
On Mar 26, 2020, at 7:57 PM, Supratim Sanyal <supratim at riseup.net> wrote:
I have obtained a MicroVAX 3100-80 with a Storageworks pizza box, a CD-ROM
drive, a tape drive, some cables and no monitor.
It powers on, does not smoke or explode. The 8 LEDs at the back settle
down to all on except 2 and 3 counting from zero on the right. I can hear a
hard disk spin up.
The cables include two MMJs. I have a PC with a 9-pin female serial
connector. It runs Linux.
The first two of many questions: does the ?0? connector connect to the
console? What exactly do I need to do to connect the PC?s serial port to
the MMJ cable? Note: I have passable soldering skills.
This should do the job, you just need to verify the pinouts. A pin
insert/remove tool might be a good investment to make adjustments in case
the first choice of pinout turns out to be not what you want.
Next question will be about the BNC connector and networking. One thing at
a time.
That is a 10Base2 connector. Next to it is an AUI connector. So if you
have a 10Base2 repeater or switch, just run coax between the two. It most
likely needs a T connector at this end with a terminator on the T (or going
to other stations if you have more). The AUI connector could be used
instead, for example if you have a 10BaseT transceiver that might be
convenient. Those are still sold; Amazon lists one from Unicom for $30.
Here are some pictures: https://photos.app.goo.gl/KduorZEimMQ73bMdA
Nice!
paul
2:40 a.m.
On 3/26/2020 6:57 PM, Supratim Sanyal wrote:
I have obtained a MicroVAX 3100-80 with a Storageworks
pizza box, a CD-ROM drive, a tape drive, some cables and no monitor.
It powers on, does not smoke or explode. The 8 LEDs at the back settle down to all on
except 2 and 3 counting from zero on the right. I can hear a hard disk spin up.
The cables include two MMJs. I have a PC with a 9-pin female serial connector. It runs
Linux.
The first two of many questions: does the ?0? connector connect to the console? What
exactly do I need to do to connect the PC?s serial port to the MMJ cable? Note: I have
passable soldering skills.
Next question will be about the BNC connector and networking. One thing at a time.
Here are some pictures: https://photos.app.goo.gl/KduorZEimMQ73bMdA
Thanks in advance
Supratim
---
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet <http://www.update.uu.se/~bqt/hecnet.html>
I have a MicroVAX 3100 Model 95.? The backside is nearly identical to yours.? The
OPA0: port is #3 (don't ask me why)
This web site has just about everything you want to know about DEC modular wiring and
their parts (plus a lot more, check out the RS-232 pages)).
<https://www.lammertbies.nl/comm/cable/dec-mmj#bc16>
--
John H. Reinhardt
2:55 a.m.
John H. Reinhardt <johnhreinhardt at
thereinhardts.org> wrote:
The OPA0: port is #3 (don't ask me why)
In the VAXstation (NOT MicroVAX), starting with the 2000 family, serial ports 0 and 1
were for the keyboard and mouse. Port 2 was for the modem/communications, and port 3 was
for the printer. VAXstations didn't normally need a serial console, but if you had to
connect one for some reason the printer port was used. They couldn't use ports 0 or 1
because those were needed for the keyboard/mouse, and I guess DEC decided they wanted to
keep the modem port open. The MicroVAX-2000 and 3000s are the same hardware as the
corresponding VAXstation, and DEC kept the serial port assignments the same.
Bob
This web site has just about everything you want to know about DEC modular wiring and
their parts (plus a lot more, check out the RS-232 pages)).
<https://www.lammertbies.nl/comm/cable/dec-mmj#bc16>
--
John H. Reinhardt
3:04 a.m.
Actually, port 0 is the console port, depending on the position of the s1 switch. Simply
try both positions and one will work.
I only use my MicroVAXen and VAXstations with console terminals. I don't have any of
them hooked up to displays or mice or keyboards.
-----Original Message-----
From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> On Behalf Of
Robert Armstrong
Sent: Thursday, March 26, 2020 6:56 PM
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Bringing up a MicroVAX 3100-80
John H. Reinhardt <johnhreinhardt at
thereinhardts.org> wrote:
The OPA0: port is #3 (don't ask me why)
In the VAXstation (NOT MicroVAX), starting with the 2000 family, serial ports 0 and 1
were for the keyboard and mouse. Port 2 was for the modem/communications, and port 3 was
for the printer. VAXstations didn't normally need a serial console, but if you had to
connect one for some reason the printer port was used. They couldn't use ports 0 or 1
because those were needed for the keyboard/mouse, and I guess DEC decided they wanted to
keep the modem port open. The MicroVAX-2000 and 3000s are the same hardware as the
corresponding VAXstation, and DEC kept the serial port assignments the same.
Bob
This web site has just about everything you want to know about DEC modular wiring and
their parts (plus a lot more, check out the RS-232 pages)).
<https://www.lammertbies.nl/comm/cable/dec-mmj#bc16>
--
John H. Reinhardt
6:33 a.m.
Thanks everyone. I found a H8571-J adapter at eBay which should address
the PC serial port connection, as well as a "Unicom ETP-20028T-2" which
is a rather cute "AUI cable, transeiver and patch cord all-in-one". Both
should be here by April.
What is "jabber" ?
Also, the serial OPA0: runs at 9600/8/N/1?
On 3/26/20 10:04 PM, David Cooper wrote:
Actually, port 0 is the console port, depending on the
position of the s1 switch. Simply try both positions and one will work.
I only use my MicroVAXen and VAXstations with console terminals. I don't have any of
them hooked up to displays or mice or keyboards.
-----Original Message-----
From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> On Behalf Of
Robert Armstrong
Sent: Thursday, March 26, 2020 6:56 PM
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Bringing up a MicroVAX 3100-80
--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
John H. Reinhardt <johnhreinhardt at
thereinhardts.org> wrote:
The OPA0: port is #3 (don't ask me why)
In the VAXstation (NOT MicroVAX),
starting with the 2000 family, serial ports 0 and 1 were for the keyboard and mouse. Port
2 was for the modem/communications, and port 3 was for the printer. VAXstations
didn't normally need a serial console, but if you had to connect one for some reason
the printer port was used. They couldn't use ports 0 or 1 because those were needed
for the keyboard/mouse, and I guess DEC decided they wanted to keep the modem port open.
The MicroVAX-2000 and 3000s are the same hardware as the corresponding VAXstation, and DEC
kept the serial port assignments the same.
Bob
This web site has just about everything you want to know about DEC modular wiring and
their parts (plus a lot more, check out the RS-232 pages)).
<https://www.lammertbies.nl/comm/cable/dec-mmj#bc16>
7:57 a.m.
On 3/27/2020 12:33 AM, Supratim Sanyal wrote:
Thanks everyone. I found a H8571-J adapter at eBay which should address the PC serial
port connection, as well as a "Unicom ETP-20028T-2" which is a rather cute
"AUI cable, transeiver and patch cord all-in-one". Both should be here by
April.
What I have is an Allied Telesyn CentreCOM 210TS AUI to Twisted Pair adapter.? It
clips on the 15-pin AUI port on the back and then you plug in a standard 10BaseT ethernet
cable.
What is "jabber" ?
Wasn't that a communication program like Yahoo Messenger/AOL chat ?
Also, the serial OPA0: runs at 9600/8/N/1?
Yep
--
John H. Reinhardt--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
2:17 p.m.
On Mar 27, 2020, at 9:11 AM, Brian Hechinger <wonko
at 4amlunch.net> wrote:
It?s also a LED on 31-year old AUI-10baseT transceivers ...
Status update: H8571-J from eBay fell thorough - guy?s in self isolation for two weeks.
But these guys in New Hampshire seem to be selling replicas for $15!
https://www.stonewallcable.com/checkout/cart/
On 3/27/20 2:57 AM, John H. Reinhardt wrote:
It's the original name for the XMPP protocol. Also now a Cisco product. :) On 3/27/2020 12:33 AM, Supratim Sanyal wrote:
What is "jabber" ?
Wasn't that a communication program like Yahoo Messenger/AOL chat ?
-brian
8:37 p.m.
On 3/27/2020 8:17 AM, Supratim Sanyal wrote:
It?s also a LED on 31-year old AUI-10baseT transceivers ...
Status update: H8571-J ?from eBay fell thorough - guy?s in self isolation for two weeks.
But these guys in New Hampshire seem to be selling replicas for $15!
https://www.stonewallcable.com/checkout/cart/
>
>
> -brian
>
I like Stonewall and have ordered from them quite a bit a few years ago.? This
place has them also (cheaper) but no experience with them. THey're in Washington state
so may be locked down also.
<http://www.pacificcable.com/Picture_Page.asp?DataName=H8571-J>
You can also buy a shell that you can wire yourself (just push the pins in to the right
place - see the pinouts on
<https://www.lammertbies.nl/comm/cable/dec-mmj#bc16>
<http://www.pacificcable.com/Picture_Page.asp?DataName=A9M12D> - male
<http://www.pacificcable.com/Picture_Page.asp?DataName=A9F12D> - female
--
John H. Reinhardt
PRRT&HS #8909
C&O HS #11530
N-Trak #7566
5:23 p.m.
On 3/27/20 9:11 AM, Brian Hechinger wrote:
It's the original name for the XMPP protocol. Also now a Cisco product. :)
And thirty years ago, it, was an oversized, errored Ethernet frame. :)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
What is "jabber" ?
Wasn't that a communication program like Yahoo Messenger/AOL chat ?
3:20 p.m.
On Mar 26, 2020, at 9:40 PM, John H. Reinhardt
<johnhreinhardt at thereinhardts.org> wrote:
I have a MicroVAX 3100 Model 95. The
backside is nearly identical to yours. The OPA0: port is #3 (don't ask me why)
John - what are the 8 LEDs showing at the back of your 3100-95?
This web site has just about everything you want to know about DEC modular wiring and
their parts (plus a lot more, check out the RS-232 pages)).
<https://www.lammertbies.nl/comm/cable/dec-mmj#bc16>
--
John H. Reinhardt
5:23 p.m.
Ethernet Jabber is https://en.wikipedia.org/wiki/Ethernet#Jabber
On Fri, Mar 27, 2020 at 10:21 AM Supratim Sanyal <supratim at riseup.net>
wrote:
I
have a MicroVAX 3100 Model 95. The backside is nearly identical to yours. The
OPA0: port is #3 (don't ask me why)
John - what are the 8 LEDs showing at the back of your 3100-95?
On Mar 26, 2020, at 9:40 PM, John H. Reinhardt
<
johnhreinhardt at thereinhardts.org> wrote:
This web site has just about everything you want to know about DEC
modular wiring
and their parts (plus a lot more, check out the RS-232
pages)).
<https://www.lammertbies.nl/comm/cable/dec-mmj#bc16>
--
John H. Reinhardt
9:39 p.m.
possible, mine is a 3100 server, not a -95 ...
--
?On the whole, professional pessimists prove right at the end if one
does not hold them too tightly to a time scale.? (Erwin Chargaff,
1978, Heraclitean Fire)
Notice for the terrestrials: This communication may be unlawfully
collected and stored by the National Security Agency (NSA), its
contractors, internet providers, subsidiaries, government agencies
foreign or domestic, and agents, as well as by private parties,
corporations and isp providers, in secret. The parties to this email
do not consent to the retrieving or storing of this communication and
any related metadata, as well as printing, copying, re-transmitting,
disseminating, or otherwise using it. If you believe you have received
this communication in error, please delete it immediately.
Notice for the aliens: based on theories presumably related to fantasy
friends and/or hands, the majority of living organisms on the third
planet from the central star in this solar system are being negatively
impacted by the dominant species, who are choosing to replicate
themselves against the better judgement of the minority, which will
likely result in the elimination of all living organisms on said
planet within the next few decades.
8:45 p.m.
On 3/27/2020 9:20 AM, Supratim Sanyal wrote:
Only #4 is on.
--
John H. Reinhardt
On Mar 26,
2020, at 9:40 PM, John H. Reinhardt <johnhreinhardt at thereinhardts.org> wrote:
I have a MicroVAX 3100 Model 95. The backside is nearly identical to yours. The OPA0:
port is #3 (don't ask me why)
John - what are the 8 LEDs showing at the back of
your 3100-95?
> This web site has just about everything you want to know about DEC modular wiring and
their parts (plus a lot more, check out the RS-232 pages)).
>
> <https://www.lammertbies.nl/comm/cable/dec-mmj#bc16>
>
> --
> John H. Reinhardt
>
9:29 a.m.
yes, zero is the console
http://www.bitsavers.org/
find the manual, probably leds are on because you don't have a
terminator plug on aui and bnc ...
has been a while ...
--
?On the whole, professional pessimists prove right at the end if one
does not hold them too tightly to a time scale.? (Erwin Chargaff,
1978, Heraclitean Fire)
Notice for the terrestrials: This communication may be unlawfully
collected and stored by the National Security Agency (NSA), its
contractors, internet providers, subsidiaries, government agencies
foreign or domestic, and agents, as well as by private parties,
corporations and isp providers, in secret. The parties to this email
do not consent to the retrieving or storing of this communication and
any related metadata, as well as printing, copying, re-transmitting,
disseminating, or otherwise using it. If you believe you have received
this communication in error, please delete it immediately.
Notice for the aliens: based on theories presumably related to fantasy
friends and/or hands, the majority of living organisms on the third
planet from the central star in this solar system are being negatively
impacted by the dominant species, who are choosing to replicate
themselves against the better judgement of the minority, which will
likely result in the elimination of all living organisms on said
planet within the next few decades.
10:03 a.m.
Hi,
I've played around with a model 20 (and an Infoserver 150, which is based
on a model 10, I believe. Maybe my hints also apply to the model 80.
Open the machine, look for something that looks like a battery pack. Check
the voltage. You might find it empty.
It may be a pack consisting of three NiCd AAA-cells, which can be replaced
with a similar pack of NiMH cells. The charge circuitry is similar.
--
Alex
Op vr 27 mrt. 2020 09:30 schreef Dan B <dibi58 at gmail.com>:
yes, zero is the console
http://www.bitsavers.org/
find the manual, probably leds are on because you don't have a
terminator plug on aui and bnc ...
has been a while ...
--
?On the whole, professional pessimists prove right at the end if one
does not hold them too tightly to a time scale.? (Erwin Chargaff,
1978, Heraclitean Fire)
Notice for the terrestrials: This communication may be unlawfully
collected and stored by the National Security Agency (NSA), its
contractors, internet providers, subsidiaries, government agencies
foreign or domestic, and agents, as well as by private parties,
corporations and isp providers, in secret. The parties to this email
do not consent to the retrieving or storing of this communication and
any related metadata, as well as printing, copying, re-transmitting,
disseminating, or otherwise using it. If you believe you have received
this communication in error, please delete it immediately.
Notice for the aliens: based on theories presumably related to fantasy
friends and/or hands, the majority of living organisms on the third
planet from the central star in this solar system are being negatively
impacted by the dominant species, who are choosing to replicate
themselves against the better judgement of the minority, which will
likely result in the elimination of all living organisms on said
planet within the next few decades.
10:13 p.m.
mine was dead a few times in the last 10 years, all i did is letting
it plugged in and a week later came back up ...
30 Mar
30 Mar
11:51 p.m.
MMJ to Serial adapter arrived today, and I now have console access via
minicom on a Linux PC.
DKA100 is inside the MicroVAX and DKA200 is in the StorageWorks. Neither
is straightaway bootable.
What is the recommended way to recover from "FILNOTCNTG" error?
KA47-A V1.2-343-V4.0
08-00-2B-2D-FF-39
24MB
?? 001?? 9??????? NI? 0172
?? 100? 10????? SCSI? 0034
>> sh dev
? VMS/VMB????? ADDR????? DEVTYPE??? NUMBYTES???? RM/FX??? WP
DEVNAM????? REV
? -------????? ----????? -------??? --------???? -----??? --
------????? ---
? ESA0???????? 08-00-2B-2D-FF-39
?????????????? A/0/0
?????????????? A/0/1
?????????????? A/0/2
?????????????? A/0/3
?????????????? A/0/4
?????????????? A/0/5
?????????????? A/0/6
?????????????? A/0/7
? DKA100?????? A/1/0???? DISK???????? 1.05GB????? FX RZ26L?????? 440C
? DKA200?????? A/2/0???? DISK???????? 2.10GB????? FX RZ28??????? 442C
?..HostID..??? A/6?????? INITR
>> b dka200
-DKA200
?43 FILESTRUCT
>> b dka100
-DKA100
?47 FILNOTCNTG
>>
>> help
? BOOT [/[R5:]<bflg>] [<ddau>[:]]
? CONTINUE
? DEPOSIT [{ /B | /W | /L | /Q | /A }] [{ /P | /V | /I }] [/G] [/U]
[/N:<n>]
????????? [{ <addr> | <sym> | + | - | * | @ } [<datum>]]
? EXAMINE [{ /B | /W | /L | /Q | /A }] [{ /P | /V | /I }] [/G] [/U]
[/N:<n>]
????????? [{ <addr> | <sym> | + | - | * | @ }]
? FIND [{ /MEMORY | /RPB }]
? HALT
? HELP
? INITIALIZE
? LOGIN
? REPEAT <cmd>
? SET BOOT <ddau>
? SET BFLG <bflg>
? SET DIAGENV <1-3>
? SET FBOOT <0-1>
? SET HALT <1-3>
? SET KBD <0-15>
? SET MOP <0-1>
? SET PSE <0-1>
? SET PSWD
? SET SCSI <0-7>
? SET TRIG <0-1>
? SHOW { BOOT | BFLG | CONFIG | DEV | DIAGENV | FBOOT | ETHER | ERROR |
???????? ESTAT | HALT | KBD | MEM | MOP | PSE | SCSI | TRIG }
? START <addr>
? TEST [/UTIL] <devnam | devnbr>
? UNJAM
? X <addr> <cnt> ...
? ?
On 3/27/20 5:13 PM, Dan B wrote:
mine was dead a few times in the last 10 years, all i
did is letting
it plugged in and a week later came back up ...
--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
31 Mar
31 Mar
12:14 a.m.
On Mon, 30 Mar 2020 17:51:21 -0400, Supratim Sanyal wrote:
What is the recommended way to recover from
"FILNOTCNTG" error?
Boot the system in some other way (cluster satellite, CD-ROM, etc.) and
check that SYSBOOT.EXE is contiguous:
$ DIR/FULL DKA100:[VMS$COMMON.SYSEXE]SYSBOOT.EXE;0
The "File Attributes" line must show "Contiguous" and hopefully
"MoveFile
disabled" too. If not, COPY/CONTIGUOUS it to a newer version of the same in
the same directory and try the boot again.
The other possibility is that the volume is damaged or does not contain a
valid VMS file structure. In this case the FILNOTCNTG error is just an
indication that VMB.EXE (in ROM) got very confused by your disk's contents.
HTH, :)
G.
12:24 a.m.
If you can mount it some how, try...
$ mount/override=id dka100:
$ analyze/disk/repair/read dka100:
-Steve
SF:IP2
On Mar 30, 2020, at 18:14, G. <gerry77 at
mail.com> wrote:
?On Mon, 30 Mar 2020 17:51:21 -0400, Supratim Sanyal wrote:
What is the recommended way to recover from
"FILNOTCNTG" error?
Boot the system in some other way (cluster satellite, CD-ROM, etc.) and
check that SYSBOOT.EXE is contiguous:
$ DIR/FULL DKA100:[VMS$COMMON.SYSEXE]SYSBOOT.EXE;0
The "File Attributes" line must show "Contiguous" and hopefully
"MoveFile
disabled" too. If not, COPY/CONTIGUOUS it to a newer version of the same in
the same directory and try the boot again.
The other possibility is that the volume is damaged or does not contain a
valid VMS file structure. In this case the FILNOTCNTG error is just an
indication that VMB.EXE (in ROM) got very confused by your disk's contents.
HTH, :)
G.
3:44 a.m.
On 3/30/20 6:14 PM, G. wrote:
On Mon, 30 Mar 2020 17:51:21 -0400, Supratim Sanyal
wrote:
I hooked up the RRD42, burnt the OVMS-7.3 ISO image on a CD-R, and tried
to boot dka400, didn't work. The internet is flush with discussions
about "special format" CD-ROM, ODS vs ISO, 2048 byte vs 512 byte blocks,
etc.
My MacBook refuses to brun the VMS 5.5-2H4 ISO from VAXHAVEN ("invalid
disk image"). So basically I have to research and find a way to burn a
CD-ROM in the necessary format that will boot the MicroVAX into DCL so
that I can repair the CONTIGUOUS issue on DKA100.
I am sure lots of people here have done this - any tips welcome while I
am trolling the internet.
KA47-A V1.2-343-V4.0
08-00-2B-2D-FF-39
24MB
?? 001?? 9??????? NI? 0172
?? 100? 10????? SCSI? 0034
What is the recommended way to recover from
"FILNOTCNTG" error?
Boot the system in some other way (cluster satellite,
CD-ROM, etc.) and
check that SYSBOOT.EXE is contiguous:
>>
>> sh dev
? VMS/VMB????? ADDR????? DEVTYPE??? NUMBYTES???? RM/FX WP???
DEVNAM????? REV
? -------????? ----????? -------??? --------???? ----- --???
------????? ---
? ESA0???????? 08-00-2B-2D-FF-39
?????????????? A/0/0
?????????????? A/0/1
?????????????? A/0/2
?????????????? A/0/3
?????????????? A/0/4
?????????????? A/0/5
?????????????? A/0/6
?????????????? A/0/7
? DKA100?????? A/1/0???? DISK???????? 1.05GB FX??????????? RZ26L?????? 440C
? DKA200?????? A/2/0???? DISK???????? 2.10GB FX??????????? RZ28??????? 442C
? DKA400?????? A/4/0???? RODISK????? ......?????? RM WP??? RRD42?????? 4.5d
?..HostID..??? A/6?????? INITR
$ DIR/FULL DKA100:[VMS$COMMON.SYSEXE]SYSBOOT.EXE;0
The "File Attributes" line must show "Contiguous" and hopefully
"MoveFile
disabled" too. If not, COPY/CONTIGUOUS it to a newer version of the same in
the same directory and try the boot again.
The other possibility is that the volume is damaged or does not contain a
valid VMS file structure. In this case the FILNOTCNTG error is just an
indication that VMB.EXE (in ROM) got very confused by your disk's contents.
HTH, :)
G.
--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
3:54 a.m.
When I did the VAX station all I did was burn the iso image normally. The SCSI drive was
a Toshiba 4x tray drive with a switch for 512 byte sector support.
Any switch settings on the DEC drive?
You also should be able to use dd on linux/unix to write the install iso to another scsi
disk to see if it boots.
Also--what is the scsi rom error message.
Is it using the weird DEC scsi cable like the DECstations?
Bill
Sent from pechter at gmail.com
-----Original Message-----
From: Supratim Sanyal <supratim at riseup.net>
To: hecnet at Update.UU.SE
Sent: Mon, 30 Mar 2020 21:44
Subject: Re: [HECnet] Bringing up a MicroVAX 3100-80
On 3/30/20 6:14 PM, G. wrote:
On Mon, 30 Mar 2020 17:51:21 -0400, Supratim Sanyal
wrote:
I hooked up the RRD42, burnt the OVMS-7.3 ISO image on a CD-R, and tried
to boot dka400, didn't work. The internet is flush with discussions
about "special format" CD-ROM, ODS vs ISO, 2048 byte vs 512 byte blocks,
etc.
My MacBook refuses to brun the VMS 5.5-2H4 ISO from VAXHAVEN ("invalid
disk image"). So basically I have to research and find a way to burn a
CD-ROM in the necessary format that will boot the MicroVAX into DCL so
that I can repair the CONTIGUOUS issue on DKA100.
I am sure lots of people here have done this - any tips welcome while I
am trolling the internet.
KA47-A V1.2-343-V4.0
08-00-2B-2D-FF-39
24MB
?? 001 9 NI 0172
?? 100 10 SCSI 0034
What is the recommended way to recover from
"FILNOTCNTG" error?
Boot the system in some other way (cluster satellite,
CD-ROM, etc.) and
check that SYSBOOT.EXE is contiguous:
>>
>> sh dev
VMS/VMB ADDR DEVTYPE NUMBYTES RM/FX WP
DEVNAM REV
------- ---- ------- -------- ----- --
------ ---
ESA0 08-00-2B-2D-FF-39
A/0/0
A/0/1
A/0/2
A/0/3
A/0/4
A/0/5
A/0/6
A/0/7
DKA100 A/1/0 DISK 1.05GB FX RZ26L 440C
DKA200 A/2/0 DISK 2.10GB FX RZ28 442C
DKA400 A/4/0 RODISK ...... RM WP RRD42 4.5d
..HostID.. A/6 INITR
$ DIR/FULL DKA100:[VMS$COMMON.SYSEXE]SYSBOOT.EXE;0
The "File Attributes" line must show "Contiguous" and hopefully
"MoveFile
disabled" too. If not, COPY/CONTIGUOUS it to a newer version of the same in
the same directory and try the boot again.
The other possibility is that the volume is damaged or does not contain a
valid VMS file structure. In this case the FILNOTCNTG error is just an
indication that VMB.EXE (in ROM) got very confused by your disk's contents.
HTH, :)
G.
--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
4:23 a.m.
On 3/30/20 9:44 PM, Supratim Sanyal wrote:
On 3/30/20 6:14 PM, G. wrote:
(I'm late to the party as always..)
I've done this many, many times without difficulty, like from the same
.iso file that you have, that has been floating around for years. I
think I even did it when I had a Mac but that was a long time ago. Are
you being careful not to burn it as a Mac disk image, but as a raw
image? Don't pay any attention to the people blathering on about
special formats; burn it as a raw byte image of the disk and it'll work
fine. Stuff like ODS filesystems, even "ISO" filesystems are captured
at a lower level that way and work fine.
As I'm sure you know, the term "ISO" is universally used to mean
"image of a CDROM", rather than "contains an ISO-9660 filesystem".
We're talking about the former here, not the latter...don't let MacOS
try to think it's smarter than you are where that's concerned.
The RRD42 is probably the safest drive to try this with from the VAX'
perspective.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Mon, 30 Mar 2020 17:51:21 -0400, Supratim
Sanyal wrote:
I hooked up the RRD42, burnt the OVMS-7.3 ISO image on a CD-R, and tried
to boot dka400, didn't work. The internet is flush with discussions
about "special format" CD-ROM, ODS vs ISO, 2048 byte vs 512 byte blocks,
etc.
My MacBook refuses to brun the VMS 5.5-2H4 ISO from VAXHAVEN ("invalid
disk image"). So basically I have to research and find a way to burn a
CD-ROM in the necessary format that will boot the MicroVAX into DCL so
that I can repair the CONTIGUOUS issue on DKA100.
I am sure lots of people here have done this - any tips welcome while I
am trolling the internet. What is the recommended way to recover from
"FILNOTCNTG" error?
Boot the system in some other way (cluster satellite,
CD-ROM, etc.) and
check that SYSBOOT.EXE is contiguous:
5:34 a.m.
On 3/30/2020 8:44 PM, Supratim Sanyal wrote:
On 3/30/20 6:14 PM, G. wrote:
The file downloaded from HPE for OpenVMS V7.3 is a Backup saveset and can't be written
directly to a CD to create a bootable disk. My disk image I got from an actual OpenVMS VAX
V7.3 CD.? Assuming you have a disk image you can use then you can follow this. It's
very simple on the Mac
1)? Navigate in Finder to the CD image file
2)? Right click on the file, should bring up a menu list and you choose 'Burn
"xxxxxxx" to Disc...'
3)? In the dialog choose the slowest? burn speed. I don't have any proof, but I've
always gotten better result with slower speeds. I typically chose the 4x speed.
4)? Choose "Verify" just for safety. I also choose "Eject on finish"
since the Mac can't mount the OpenVMS CD file system anyway.
5)? Start the CD burn
The CD-R that I use are 700MB 80 minute ones.? The brand is Philips.? Not sure how much
difference that makes. It's been along time since I did any testing. I have a large
supply of the current ones so I haven't needed to shop in a few years.
Unless there is corruption in the disk image you use, that should be all you have to do.?
Windows people have a little more, they usually need a special program but the Mac's
CD burn program works just fine for OpenVMS images.
When writing the CD, you don't need to worry about the 512 vs 2048 byte block
problem.? That's only for the CD drive hooked to the VAX.? An RRD42 has the
appropriate block size.? The only thing I don't know is if an RRD42 is too early of a
drive to handle a CD-R or not.? My oldest DEC drive is an RRD43 in my InfoTower.? My
MicroVAX 3100 has a Toshiba XM-5701A which is a RRD45 or RRD46 equivalent.? My InfoTower
is not set up at the moment but the MicroVAX can read the burnt disk without problem.
So I just wrote a V7.3 CD from image and it worked okay.? I downloaded the V5.5-H4 image
from VAXHaven and I get an "unrecognizable format" message from the Mac when
selecting the "AG-PXL1A-RE.iso" to burn.? I examined it in DiskImageMounter but
it can't figure out the format either.? It's possible the image is corrupted on
the VAXHaven site.? It's also possible that DEC used an internal format on the CD that
the current software doesn't know about.? Some combination of ISO and Joliet,
perhaps.? So next I downloaded the OpenVMS VAX V6.1 image from VAXHaven (AG-PXKUC-RE.ISO)
and it burned okay.? I can mount it in my MicroVAX and read the save sets off of it.
II have another copy of V5.5-2H4 that I got from www.winworldpc.com at the hint of one of
these message boards. Maybe Classic Comp.? But it gives the same "Could not burn
"VMS 552h4 VAX.iso". The disk image is invalid." error so I'm betting
it's probably a copy of the VAXHaven image.? I got a V5.5-2 from there and I can burn
that.? More and more I think the VAXHaven V5.5-2H4 image may be corrupted.
--
John H. Reinhardt
On Mon, 30 Mar 2020 17:51:21 -0400, Supratim
Sanyal wrote:
I hooked up the RRD42, burnt the OVMS-7.3 ISO image on a CD-R, and tried to boot
dka400, didn't work. The internet is flush with discussions about "special
format" CD-ROM, ODS vs ISO, 2048 byte vs 512 byte blocks, etc.
My MacBook refuses to brun the VMS 5.5-2H4 ISO from VAXHAVEN ("invalid disk
image"). So basically I have to research and find a way to burn a CD-ROM in the
necessary format that will boot the MicroVAX into DCL so that I can repair the CONTIGUOUS
issue on DKA100.
I am sure lots of people here have done this - any tips welcome while I am trolling the
internet. What is the recommended way to recover from
"FILNOTCNTG" error?
Boot the system in some other way (cluster satellite,
CD-ROM, etc.) and
check that SYSBOOT.EXE is contiguous:
5:39 a.m.
On 3/30/20 11:34 PM, John H. Reinhardt wrote:
The file downloaded from HPE for OpenVMS V7.3 is a
Backup saveset and
can't be written directly to a CD to create a bootable disk. My disk
image I got from an actual OpenVMS VAX V7.3 CD.? Assuming you have a
disk image you can use then you can follow this. It's very simple on the
Mac
Waitaminute...so the disk image that you generated by reading a
bootable 7.3 CD differs from the HPE-distributed 7.3 file? Does the
latter not contain standalone backup at the beginning, etc?
When writing the CD, you don't need to worry about
the 512 vs 2048 byte
block problem.? That's only for the CD drive hooked to the VAX.? An
RRD42 has the appropriate block size.? The only thing I don't know is if
an RRD42 is too early of a drive to handle a CD-R or not.
I've used CD-Rs in RRD42s. It helps to burn them at no faster than 8x.
Yes, I know, the speed at which you burn it shouldn't make any
difference. But I was beating my head against a wall trying to boot a
DECstation from a CD-R disk, three tries, and a friend told me to try
the burn again but restrict the speed to 8x. I was skeptical, but I
tried it, and it worked, and I've had no issues since.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
6:37 a.m.
On 3/30/2020 10:39 PM, Dave McGuire wrote:
--
John H. Reinhardt
On 3/30/20 11:34 PM, John H. Reinhardt wrote:
Yes.? The file I downloaded from HP (just two weeks ago) is a backup save set zipped into
an archive. It's not a disk image. Well, unless the backup saveset is a of a
diskimage. But I don't think so.
When you download from HPE from the site they give you when you get the Hobbyist licenses,
you get a file named "VAXVMS073.ZIP". So you unzip it and you get a file called
"vaxvms073.bck".? If I try burning that to CD on my Mac if says I need a 571.1MV
or larger CD.? I put a 700MB CD-R in the drive and then it fails saying it's too big
and I should remove some files.? It also thinks the contents being written to CD is called
"Untitled Disk.fpbf".? I haven't Googled that yet.? So I changed the
filename to "vaxvms073.ISO" just to see wht pahhens.? The Mac happily writes the
CD.? When I mount it on the VAX I get:
$ mount /over=id dka500:
%MOUNT-F-NOHOMEBLK, Files-11 home block not found on volume
-MOUNT-I-VOLIDENT, label = '............', owner = '............', format
= '............'
So I know it's got no Files-11 file system on it.? I re-mount it foreign and do a dump
/block of dka500:
$ dump /blocks /page dka500:
Dump of device DKA500: on 30-MAR-2020 22:23:45.63
Logical block number 0 (00000000), 512 (0200) bytes
?00000000 00000000 00000000 00000000 00000000 00000001 00010001 08000100
................................ 000000
?00004B43 422E3337 30534D56 5841560D 00000000 00007E00 86716A6E 00010101
....njq..~.......VAXVMS073.BCK.. 000020
?00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
................................ 000040
?00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
................................ 000060
?00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
................................ 000080
?00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
................................ 0000A0
?00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
................................ 0000C0
?08DC0000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
..............................?. 0000E0
?2E333730 534D5658 41560001 000D0101 00000000 00000000 00000000 000100F0
?.....................VAXVMS073. 000100
?494C414F 4E2F5946 49524556 2F454741 4D492F50 554B4341 42000200 464B4342
BCKF...BACKUP/IMAGE/VERIFY/NOALI 000120
?45535F45 5641532F 4B43422E 33373053 4D565841 56203A24 4D4F5244 43205341 AS CDROM$:
VAXVMS073.BCK/SAVE_SE 000140
?05000420 20202020 2050554B 43414200 04000C30 30303536 3D4B434F 4C422F54
T/BLOCK=65000....BACKUP????? ... 000160
?09322E37 56000800 04080000 07000200 9FA5F05B E45C5000 06000800 01004000 . at
.......P\?[??............V7.2. 000180
?4B442430 3031245F 000B000B 80000000 000A0004 3A3A584F 42474F44 5F000900
..._DOGBOX::............_$100$DK 0001A0
?0002000A 000E0002 00007E00 000D0004 31303052 32375058 41000C00 093A3041
A0:....AXP72R001.....~.......... 0001C0
?00000000 00000001 00110002 20202020 20202020 20202020 0010000C 03DF000F
..?.....??????????? ............ 0001E0
So it's definitely a VMS Backup save set.? Based on the dump it's an image backup
of the V7.3 CD.? But you can't get to it unless you already have an OpenVMS system to
run it through Backup.? So it's no good for a Hobbyist with no other machine yet.
Oops.
The file downloaded from HPE for OpenVMS V7.3 is
a Backup saveset and
can't be written directly to a CD to create a bootable disk. My disk
image I got from an actual OpenVMS VAX V7.3 CD.? Assuming you have a
disk image you can use then you can follow this. It's very simple on the
Mac
Waitaminute...so the disk image that you generated by reading a
bootable 7.3 CD differs from the HPE-distributed 7.3 file? Does the
latter not contain standalone backup at the beginning, etc? When writing
the CD, you don't need to worry about the 512 vs 2048 byte
block problem.? That's only for the CD drive hooked to the VAX.? An
RRD42 has the appropriate block size.? The only thing I don't know is if
an RRD42 is too early of a drive to handle a CD-R or not.
I've used CD-Rs
in RRD42s. It helps to burn them at no faster than 8x.
Yes, I know, the speed at which you burn it shouldn't make any
difference. But I was beating my head against a wall trying to boot a
DECstation from a CD-R disk, three tries, and a friend told me to try
the burn again but restrict the speed to 8x. I was skeptical, but I
tried it, and it worked, and I've had no issues since.
-Dave
2 Apr
2 Apr
6:55 a.m.
On 3/31/20 12:37 AM, John H. Reinhardt wrote:
...
Wow, ok, I didn't know that. My 7.3 CD image certainly isn't like
that; it's bootable into standalone BACKUP. I've burnt it to physical
disks several times, and installed VMS many times from them, on lots of
machines.
Surely they knew the other approach wouldn't be terribly useful?
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
??
Waitaminute...so the disk image that you generated by reading a
bootable 7.3 CD differs from the HPE-distributed 7.3 file?? Does the
latter not contain standalone backup at the beginning, etc?
Yes.? The file I downloaded from HP (just two weeks ago) is a backup
save set zipped into an archive. It's not a disk image. Well, unless the
backup saveset is a of a diskimage. But I don't think so.
8:04 a.m.
On 4/1/2020 11:55 PM, Dave McGuire wrote:
On 3/31/20 12:37 AM, John H. Reinhardt wrote:
...
Wow, ok, I didn't know that. My 7.3 CD image certainly isn't like
that; it's bootable into standalone BACKUP. I've burnt it to physical
disks several times, and installed VMS many times from them, on lots of
machines.
Surely they knew the other approach wouldn't be terribly useful?
-Dave
Never mind what I said.? *sigh*? Turns out there is both a zip of the CD image AND
(why, I don't know) zip of the image backup of the CD.? Somehow the other night I
missed seeing the image ZIP and unzipped the backup.? So you *can* download a working V7.3
CD image from HPE.
Too many late nights this week...
--
John H. Reinhardt
??
Waitaminute...so the disk image that you generated by reading a
bootable 7.3 CD differs from the HPE-distributed 7.3 file?? Does the
latter not contain standalone backup at the beginning, etc?
Yes.? The file I
downloaded from HP (just two weeks ago) is a backup
save set zipped into an archive. It's not a disk image. Well, unless the
backup saveset is a of a diskimage. But I don't think so. 
31 Mar
31 Mar
5:46 a.m.
I have tried both the VAXHaven and WinWorldPC copies of 5.5-2H4 and I tend
to agree that the VAXHaven one is corrupted (at least it's never worked for
me). But the WinWorldPC copy works great. Also, corrupt is the MicroVMS 4.7
TK50 image on VAXHaven.
Ray
On Mon, Mar 30, 2020, 11:34 PM John H. Reinhardt <
johnhreinhardt at thereinhardts.org> wrote:
On 3/30/2020 8:44 PM, Supratim Sanyal wrote:
On 3/30/20 6:14 PM, G. wrote:
to
boot dka400, didn't work. The internet is flush with discussions about
"special format" CD-ROM, ODS vs ISO, 2048 byte vs 512 byte blocks, etc.
On Mon, 30 Mar 2020 17:51:21 -0400, Supratim
Sanyal wrote:
I hooked up the RRD42, burnt the OVMS-7.3 ISO image on a CD-R, and tried What is the recommended way to recover from
"FILNOTCNTG" error?
Boot the system in some other way (cluster satellite,
CD-ROM, etc.) and
check that SYSBOOT.EXE is contiguous:
My MacBook refuses to brun the VMS 5.5-2H4 ISO from VAXHAVEN ("invalid
disk
image"). So basically I have to research and find a way to burn a
CD-ROM in the necessary format that will boot the MicroVAX into DCL so that
I can repair the CONTIGUOUS issue on DKA100.
I am sure lots of people here have done this - any tips welcome while I
am
trolling the internet.
The file downloaded from HPE for OpenVMS V7.3 is a Backup saveset and
can't be written directly to a CD to create a bootable disk. My disk image
I got from an actual OpenVMS VAX V7.3 CD. Assuming you have a disk image
you can use then you can follow this. It's very simple on the Mac
1) Navigate in Finder to the CD image file
2) Right click on the file, should bring up a menu list and you choose
'Burn "xxxxxxx" to Disc...'
3) In the dialog choose the slowest burn speed. I don't have any proof,
but I've always gotten better result with slower speeds. I typically chose
the 4x speed.
4) Choose "Verify" just for safety. I also choose "Eject on finish"
since
the Mac can't mount the OpenVMS CD file system anyway.
5) Start the CD burn
The CD-R that I use are 700MB 80 minute ones. The brand is Philips. Not
sure how much difference that makes. It's been along time since I did any
testing. I have a large supply of the current ones so I haven't needed to
shop in a few years.
Unless there is corruption in the disk image you use, that should be all
you have to do. Windows people have a little more, they usually need a
special program but the Mac's CD burn program works just fine for OpenVMS
images.
When writing the CD, you don't need to worry about the 512 vs 2048 byte
block problem. That's only for the CD drive hooked to the VAX. An RRD42
has the appropriate block size. The only thing I don't know is if an RRD42
is too early of a drive to handle a CD-R or not. My oldest DEC drive is an
RRD43 in my InfoTower. My MicroVAX 3100 has a Toshiba XM-5701A which is a
RRD45 or RRD46 equivalent. My InfoTower is not set up at the moment but
the MicroVAX can read the burnt disk without problem.
So I just wrote a V7.3 CD from image and it worked okay. I downloaded the
V5.5-H4 image from VAXHaven and I get an "unrecognizable format" message
from the Mac when selecting the "AG-PXL1A-RE.iso" to burn. I examined it
in DiskImageMounter but it can't figure out the format either. It's
possible the image is corrupted on the VAXHaven site. It's also possible
that DEC used an internal format on the CD that the current software
doesn't know about. Some combination of ISO and Joliet, perhaps. So next
I downloaded the OpenVMS VAX V6.1 image from VAXHaven (AG-PXKUC-RE.ISO) and
it burned okay. I can mount it in my MicroVAX and read the save sets off
of it.
II have another copy of V5.5-2H4 that I got from www.winworldpc.com at
the hint of one of these message boards. Maybe Classic Comp. But it gives
the same "Could not burn "VMS 552h4 VAX.iso". The disk image is
invalid."
error so I'm betting it's probably a copy of the VAXHaven image. I got a
V5.5-2 from there and I can burn that. More and more I think the VAXHaven
V5.5-2H4 image may be corrupted.
--
John H. Reinhardt
5:53 a.m.
On 3/30/2020 10:46 PM, Ray Jewhurst wrote:
I have tried both the VAXHaven and WinWorldPC copies
of 5.5-2H4 and I tend to agree that the VAXHaven one is corrupted (at least it's never
worked for me). But the WinWorldPC copy works great. Also, corrupt is the MicroVMS 4.7
TK50 image on VAXHaven.
Ray
The file I got from WinWorldPC came as a ".7z" archive.? and I unpacked it with
"TheUnarchiver".? Does that match what you did? The file I get from that always
gets the "Could not burn "VMS 552h4 VAX.iso". The disk image is
invalid." error from the Mac disk burn software.
Did you do something differently?
Thanks.
John H. Reinhardt
On Mon, Mar 30, 2020, 11:34 PM John H. Reinhardt <johnhreinhardt at thereinhardts.org
<mailto:johnhreinhardt at thereinhardts.org>> wrote:
On 3/30/2020 8:44 PM, Supratim Sanyal wrote:
--
John H. Reinhardt
PRRT&HS #8909
C&O HS #11530
N-Trak #7566
On 3/30/20 6:14 PM, G. wrote:
The file downloaded from HPE for OpenVMS V7.3 is a Backup saveset and can't be
written directly to a CD to create a bootable disk. My disk image I got from an actual
OpenVMS VAX V7.3 CD.? Assuming you have a disk image you can use then you can follow this.
It's very simple on the Mac
1)? Navigate in Finder to the CD image file
2)? Right click on the file, should bring up a menu list and you choose 'Burn
"xxxxxxx" to Disc...'
3)? In the dialog choose the slowest? burn speed. I don't have any proof, but
I've always gotten better result with slower speeds. I typically chose the 4x speed.
4)? Choose "Verify" just for safety. I also choose "Eject on
finish" since the Mac can't mount the OpenVMS CD file system anyway.
5)? Start the CD burn
The CD-R that I use are 700MB 80 minute ones.? The brand is Philips.? Not sure how
much difference that makes. It's been along time since I did any testing. I have a
large supply of the current ones so I haven't needed to shop in a few years.
Unless there is corruption in the disk image you use, that should be all you have to
do.? Windows people have a little more, they usually need a special program but the
Mac's CD burn program works just fine for OpenVMS images.
When writing the CD, you don't need to worry about the 512 vs 2048 byte block
problem.? That's only for the CD drive hooked to the VAX.? An RRD42 has the
appropriate block size.? The only thing I don't know is if an RRD42 is too early of a
drive to handle a CD-R or not.? My oldest DEC drive is an RRD43 in my InfoTower.? My
MicroVAX 3100 has a Toshiba XM-5701A which is a RRD45 or RRD46 equivalent.? My InfoTower
is not set up at the moment but the MicroVAX can read the burnt disk without problem.
So I just wrote a V7.3 CD from image and it worked okay.? I downloaded the V5.5-H4
image from VAXHaven and I get an "unrecognizable format" message from the Mac
when selecting the "AG-PXL1A-RE.iso" to burn.? I examined it in DiskImageMounter
but it can't figure out the format either. It's possible the image is corrupted on
the VAXHaven site. It's also possible that DEC used an internal format on the CD that
the current software doesn't know about.? Some combination of ISO and Joliet,
perhaps.? So next I downloaded the OpenVMS VAX V6.1 image from VAXHaven (AG-PXKUC-RE.ISO)
and it burned okay.? I can mount it in my MicroVAX and read the save sets off of it.
II have another copy of V5.5-2H4 that I got from www.winworldpc.com
<http://www.winworldpc.com> at the hint of one of these message boards. Maybe
Classic Comp.? But it gives the same "Could not burn "VMS 552h4 VAX.iso".
The disk image is invalid." error so I'm betting it's probably a copy of the
VAXHaven image.? I got a V5.5-2 from there and I can burn that.? More and more I think the
VAXHaven V5.5-2H4 image may be corrupted.
--
John H. Reinhardt
On Mon, 30 Mar 2020 17:51:21 -0400, Supratim
Sanyal wrote:
I hooked up the RRD42, burnt the OVMS-7.3 ISO image on a CD-R, and tried to boot
dka400, didn't work. The internet is flush with discussions about "special
format" CD-ROM, ODS vs ISO, 2048 byte vs 512 byte blocks, etc.
My MacBook refuses to brun the VMS 5.5-2H4 ISO from VAXHAVEN ("invalid disk
image"). So basically I have to research and find a way to burn a CD-ROM in the
necessary format that will boot the MicroVAX into DCL so that I can repair the CONTIGUOUS
issue on DKA100.
I am sure lots of people here have done this - any tips welcome while I am trolling the
internet. What is the recommended way to recover from
"FILNOTCNTG" error?
Boot the system in some other way (cluster satellite,
CD-ROM, etc.) and
check that SYSBOOT.EXE is contiguous:
5:59 a.m.
I haven't tried burning but I used p7z through File Roller on a Linux Mint
system. I have only used it as an image on Simh. I am not at my computer
tonight but if you need it tomorrow I can get you a checksum on the
unzipped image.
Ray
On Mon, Mar 30, 2020, 11:53 PM John H. Reinhardt <
johnhreinhardt at thereinhardts.org> wrote:
On 3/30/2020 10:46 PM, Ray Jewhurst wrote:
I have tried both the VAXHaven and WinWorldPC
copies of 5.5-2H4 and I
tend to agree that the VAXHaven one is corrupted (at least
it's never
worked for me). But the WinWorldPC copy works great. Also, corrupt is the
MicroVMS 4.7 TK50 image on VAXHaven.
Ray
The file I got from WinWorldPC came as a ".7z" archive. and I unpacked it
with "TheUnarchiver". Does that match what you did? The file I get from
that always gets the "Could not burn "VMS 552h4 VAX.iso". The disk image
is
invalid." error from the Mac disk burn software.
Did you do something differently?
Thanks.
John H. Reinhardt
On Mon, Mar 30, 2020, 11:34 PM John H. Reinhardt <
johnhreinhardt at
thereinhardts.org <mailto:johnhreinhardt at thereinhardts.org>>
wrote:
On 3/30/2020 8:44 PM, Supratim Sanyal wrote:
> On 3/30/20 6:14 PM, G. wrote:
>
>> On Mon, 30 Mar 2020 17:51:21 -0400, Supratim Sanyal wrote:
>>
>>> What is the recommended way to recover from "FILNOTCNTG"
error?
>> Boot the system in some other way (cluster satellite, CD-ROM,
etc.)
and
>> check that SYSBOOT.EXE is
contiguous:
>>
> I hooked up the RRD42, burnt the OVMS-7.3 ISO image on a CD-R, and
tried
to boot dka400, didn't work. The internet is flush with discussions
about "special format" CD-ROM, ODS vs ISO, 2048 byte vs 512 byte blocks,
etc.
>
> My MacBook refuses to brun the VMS 5.5-2H4 ISO from VAXHAVEN
("invalid disk image"). So basically I have to research and find a way to
burn a CD-ROM in the necessary format that will boot the MicroVAX into DCL
so that I can repair the CONTIGUOUS issue on DKA100.
>
> I am sure lots of people here have done this - any tips welcome
while I
am trolling the internet.
The file downloaded from HPE for OpenVMS V7.3 is a Backup saveset
and
can't be written directly to a CD to create a bootable disk. My disk
image I got from an actual OpenVMS VAX V7.3 CD. Assuming you have a disk
image you can use then you can follow this. It's very simple on the Mac
1) Navigate in Finder to the CD image file
2) Right click on the file, should bring up a menu list and you
choose
'Burn "xxxxxxx" to Disc...'
3) In the dialog choose the slowest burn speed. I don't have any
proof,
but I've always gotten better result with slower speeds. I typically
chose the 4x speed.
4) Choose "Verify" just for safety. I also choose "Eject on
finish"
since the Mac can't mount the OpenVMS CD file system anyway.
5) Start the CD burn
The CD-R that I use are 700MB 80 minute ones. The brand is
Philips. Not sure
how much difference that makes. It's been along time
since I did any testing. I have a large supply of the current ones so I
haven't needed to shop in a few years.
Unless there is corruption in the disk image you use, that should be
all you
have to do. Windows people have a little more, they usually need a
special program but the Mac's CD burn program works just fine for OpenVMS
images.
When writing the CD, you don't need to worry about the 512 vs 2048
byte
block problem. That's only for the CD drive hooked to the VAX. An
RRD42 has the appropriate block size. The only thing I don't know is if an
RRD42 is too early of a drive to handle a CD-R or not. My oldest DEC drive
is an RRD43 in my InfoTower. My MicroVAX 3100 has a Toshiba XM-5701A which
is a RRD45 or RRD46 equivalent. My InfoTower is not set up at the moment
but the MicroVAX can read the burnt disk without problem.
So I just wrote a V7.3 CD from image and it worked okay. I
downloaded the
V5.5-H4 image from VAXHaven and I get an "unrecognizable
format" message from the Mac when selecting the "AG-PXL1A-RE.iso" to
burn.
I examined it in DiskImageMounter but it can't figure out the format
either. It's possible the image is corrupted on the VAXHaven site. It's
also possible that DEC used an internal format on the CD that the current
software doesn't know about. Some combination of ISO and Joliet, perhaps.
So next I downloaded the OpenVMS VAX V6.1 image from VAXHaven
(AG-PXKUC-RE.ISO) and it burned okay. I can mount it in my MicroVAX and
read the save sets off of it.
II have another copy of V5.5-2H4 that I got from www.winworldpc.com
<http://www.winworldpc.com> at the hint of one of these message boards.
Maybe Classic Comp. But it gives the same "Could not burn "VMS 552h4
VAX.iso". The disk image is invalid." error so I'm betting it's
probably a
copy of the VAXHaven image. I got a V5.5-2 from there and I can burn
that. More and more I think the VAXHaven V5.5-2H4 image may be corrupted.
--
John H. Reinhardt
--
John H. Reinhardt
PRRT&HS #8909
C&O HS #11530
N-Trak #7566
6:25 a.m.
On 3/30/2020 10:59 PM, Ray Jewhurst wrote:
I haven't tried burning but I used p7z through
File Roller on a Linux Mint system. I have only used it as an image on Simh. I am not at
my computer tonight but if you need it tomorrow I can get you a checksum on the unzipped
image.
Ray
Okay. Maybe it's a difference between Linux and macOOS.? I downloaded the file from
WInWorldPC.? The actual file came from someone named "Ricky" in Germany.? The
file downloaded was "DEC VMS 5.5-2H4 (Jul 1993) [VAX] (ISO).7z"? I ran it
through "TheUnarchiver" and it produced a folder with two files.? A txt file and
"VMS 552h4 VAX.iso". I tried burning that ISO file but then I get the disk image
is invalid error.
I'll have to get a copy of SimH running on my Mac and see it it can read the ISO.
On Mon, Mar 30, 2020, 11:53 PM John H. Reinhardt <johnhreinhardt at thereinhardts.org
<mailto:johnhreinhardt at thereinhardts.org>> wrote:
On 3/30/2020 10:46 PM, Ray Jewhurst wrote:
I have tried both the VAXHaven and WinWorldPC
copies of 5.5-2H4 and I tend to agree that the VAXHaven one is corrupted (at least
it's never worked for me). But the WinWorldPC copy works great. Also, corrupt is the
MicroVMS 4.7 TK50 image on VAXHaven.
Ray
The file I got from WinWorldPC came as a ".7z" archive.? and I unpacked it
with "TheUnarchiver".? Does that match what you did? The file I get from that
always gets the "Could not burn "VMS 552h4 VAX.iso". The disk image is
invalid." error from the Mac disk burn software.
Did you do something differently?
Thanks.
John H. Reinhardt
7 a.m.
On 3/31/20 12:25 AM, John H. Reinhardt wrote:
--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
On 3/30/2020 10:59 PM, Ray Jewhurst wrote:
Vaxhaven's AG-PXL1A-RE.iso is 236013792 bytes, Winworld's "VMS 552h4
VAX.iso" is 205508764. Neither can be burnt by MacOS directly from the
GUI. The following command line results in a "raw" burn (remove the
-testburn switch to enable the laser).
$ hdiutil burn -testburn -imagekey diskimage-class=CRawDiskImage -speed
2 Downloads/DEC\ VMS\ 5.5-2H4\ \(Jul\ 1993\)\ \[VAX\]\ \(ISO\)/VMS\
552h4\ VAX.iso
The Vaxhaven raw burn does not boot. I will try the Winworld version
next. BUT, just to make sure the RRD42 is not the problem, here's a
couple of questions about it:
1) I have connected the SCSI cable at the bottom and a terminator at the
top. Is this okay?
2) When I insert the caddie in (with the CD in the caddy), the green
light turns on for a few seconds and then turns off. Nothing else
happens. MicroVAX comes back to ">>>" prompt after a few minutes, no
other messages. Should I expect to hear some noises of the plate at the
bottom of the caddie moving sideways to expose the CD to the laser, etc?
Also, even if I get to a point where I boot into standalone backup, how
am I to fix the problem with DKA100's contiguity issue?
The previous owner said he had actual PAKs that he could not find, but
are loaded in the LMF databse. I would very much like to at least be
able to copy the LMF and am averse to reinstalling a fresh copy of VMS
on DKA100 (everyobdy here will understand exactly why this is
super-important now).
I haven't tried burning but I used p7z
through File Roller on a Linux
Mint system. I have only used it as an image on Simh. I am not at my
computer tonight but if you need it tomorrow I can get you a checksum
on the unzipped image.
Ray
Okay. Maybe it's a difference between Linux and macOOS.? I downloaded
the file from WInWorldPC.? The actual file came from someone named
"Ricky" in Germany.? The file downloaded was "DEC VMS 5.5-2H4 (Jul
1993) [VAX] (ISO).7z"? I ran it through "TheUnarchiver" and it
produced a folder with two files.? A txt file and "VMS 552h4 VAX.iso".
I tried burning that ISO file but then I get the disk image is invalid
error.
I'll have to get a copy of SimH running on my Mac and see it it can
read the ISO.
On Mon, Mar 30, 2020, 11:53 PM John H. Reinhardt
<johnhreinhardt at thereinhardts.org
<mailto:johnhreinhardt at thereinhardts.org>> wrote:
??? On 3/30/2020 10:46 PM, Ray Jewhurst wrote:
??? > I have tried both the VAXHaven and WinWorldPC copies of 5.5-2H4
and I tend to agree that the VAXHaven one is corrupted (at least it's
never worked for me). But the WinWorldPC copy works great. Also,
corrupt is the MicroVMS 4.7 TK50 image on VAXHaven.
??? >
??? > Ray
??? The file I got from WinWorldPC came as a ".7z" archive.? and I
unpacked it with "TheUnarchiver".? Does that match what you did? The
file I get from that always gets the "Could not burn "VMS 552h4
VAX.iso". The disk image is invalid." error from the Mac disk burn
software.
??? Did you do something differently?
??? Thanks.
??? John H. Reinhardt
3:52 p.m.
On Tue, 31 Mar 2020 01:00:08 -0400, Supratim Sanyal wrote:
Also, even if I get to a point where I boot into
standalone backup, how
am I to fix the problem with DKA100's contiguity issue?
Recent OpenVMS VAX installation CD-ROM volumes have both the standalone
backup (on root 0) and a limited DCL environment (on root 1). Choose the
latter and see if you can run COPY from there (I have never tried it).
See for example section 3.1.3 at the following link:
http://h30266.www3.hpe.com/odl/vax/opsys/vmsos73/vmsos73/6630/6630pro_002.h…
HTH, :)
G.
4 p.m.
Supratim,
If you can contact me offline I can probably walk you through any number of scenarios to
deal with this.
-Steve Davidson
SF:iP1
On Mar 31, 2020, at 01:00, Supratim Sanyal
<supratim at riseup.net> wrote:
? On 3/31/20 12:25 AM, John H. Reinhardt wrote:
--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
On 3/30/2020 10:59 PM, Ray Jewhurst wrote:
Vaxhaven's AG-PXL1A-RE.iso is 236013792 bytes, Winworld's "VMS 552h4
VAX.iso" is 205508764. Neither can be burnt by MacOS directly from the GUI. The
following command line results in a "raw" burn (remove the -testburn switch to
enable the laser).
$ hdiutil burn -testburn -imagekey diskimage-class=CRawDiskImage -speed 2 Downloads/DEC\
VMS\ 5.5-2H4\ \(Jul\ 1993\)\ \[VAX\]\ \(ISO\)/VMS\ 552h4\ VAX.iso
The Vaxhaven raw burn does not boot. I will try the Winworld version next. BUT, just to
make sure the RRD42 is not the problem, here's a couple of questions about it:
1) I have connected the SCSI cable at the bottom and a terminator at the top. Is this
okay?
2) When I insert the caddie in (with the CD in the caddy), the green light turns on for a
few seconds and then turns off. Nothing else happens. MicroVAX comes back to
">>>" prompt after a few minutes, no other messages. Should I expect to
hear some noises of the plate at the bottom of the caddie moving sideways to expose the CD
to the laser, etc?
Also, even if I get to a point where I boot into standalone backup, how am I to fix the
problem with DKA100's contiguity issue?
The previous owner said he had actual PAKs that he could not find, but are loaded in the
LMF databse. I would very much like to at least be able to copy the LMF and am averse to
reinstalling a fresh copy of VMS on DKA100 (everyobdy here will understand exactly why
this is super-important now).
I haven't tried burning but I used p7z
through File Roller on a Linux Mint system. I have only used it as an image on Simh. I am
not at my computer tonight but if you need it tomorrow I can get you a checksum on the
unzipped image.
Ray
Okay. Maybe it's a difference between Linux and macOOS. I downloaded the file from
WInWorldPC. The actual file came from someone named "Ricky" in Germany. The
file downloaded was "DEC VMS 5.5-2H4 (Jul 1993) [VAX] (ISO).7z" I ran it
through "TheUnarchiver" and it produced a folder with two files. A txt file and
"VMS 552h4 VAX.iso". I tried burning that ISO file but then I get the disk image
is invalid error.
I'll have to get a copy of SimH running on my Mac and see it it can read the ISO.
On Mon, Mar 30, 2020, 11:53 PM John H. Reinhardt <johnhreinhardt at thereinhardts.org
<mailto:johnhreinhardt at thereinhardts.org>> wrote:
On 3/30/2020 10:46 PM, Ray Jewhurst wrote:
I have tried both the VAXHaven and WinWorldPC
copies of 5.5-2H4 and I tend to agree that the VAXHaven one is corrupted (at least
it's never worked for me). But the WinWorldPC copy works great. Also, corrupt is the
MicroVMS 4.7 TK50 image on VAXHaven.
Ray
The file I got from WinWorldPC came as a ".7z" archive. and I unpacked it
with "TheUnarchiver". Does that match what you did? The file I get from that
always gets the "Could not burn "VMS 552h4 VAX.iso". The disk image is
invalid." error from the Mac disk burn software.
Did you do something differently?
Thanks.
John H. Reinhardt
9:46 p.m.
I am happy to report that Supratim and I have managed to connect me to
his system, create a VAXcluster boot node on SimH, boot the system into
the cluster as a satellite and now running ANALYZE/DISK/REPAIR/READ
against the troubled disk.
-Steve
On Tue, 2020-03-31 at 10:00 -0400, Steve Davidson wrote:
Supratim,
If you can contact me offline I can probably walk you through any
number of scenarios to deal with this.
-Steve Davidson
SF:iP1
> On Mar 31, 2020, at 01:00, Supratim Sanyal <supratim at riseup.net>
> wrote:
>
> ?
>
>
>
>
> On 3/31/20 12:25 AM, John H. Reinhardt wrote:
>
>
> > On
> > 3/30/2020 10:59 PM, Ray Jewhurst wrote:
> >
> >
> >
> > > I haven't tried burning but I used p7z
> > > through File Roller on a Linux Mint system. I have only
> > > used it
> > > as an image on Simh. I am not at my computer tonight
> > > but if you
> > > need it tomorrow I can get you a checksum on the
> > > unzipped image.
> > >
> > >
> > >
> > >
> > > Ray
> > >
> > >
> > >
> >
> >
> >
> >
> >
> > Okay. Maybe it's a difference between Linux and macOOS. I
> > downloaded the file from WInWorldPC. The actual file came
> > from
> > someone named "Ricky" in Germany. The file downloaded was
> > "DEC
> > VMS 5.5-2H4 (Jul 1993) [VAX] (ISO).7z" I ran it through
> > "TheUnarchiver" and it produced a folder with two files. A
> > txt
> > file and "VMS 552h4 VAX.iso". I tried burning that ISO file
> > but
> > then I get the disk image is invalid error.
> >
> >
> >
> >
> > I'll have to get a copy of SimH running on my Mac and see
> > it it
> > can read the ISO.
> >
> >
> >
> >
> >
>
>
>
>
> Vaxhaven's AG-PXL1A-RE.iso is 236013792 bytes,
> Winworld's "VMS 552h4 VAX.iso" is 205508764. Neither can be
> burnt by MacOS directly from the GUI. The following command
> line
> results in a "raw" burn (remove the -testburn switch to
> enable
> the laser).
>
>
> $ hdiutil burn -testburn -imagekey
> diskimage-class=CRawDiskImage -speed 2 Downloads/DEC\ VMS\
> 5.5-2H4\ \(Jul\ 1993\)\ \[VAX\]\ \(ISO\)/VMS\ 552h4\
> VAX.iso
> The Vaxhaven raw burn does not boot. I will
> try the Winworld version next. BUT, just to make sure the
> RRD42
> is not the problem, here's a couple of questions about it:
> 1) I have connected the SCSI cable at the
> bottom and a terminator at the top. Is this okay?
> 2) When I insert the caddie in (with the CD in
> the caddy), the green light turns on for a few seconds and
> then
> turns off. Nothing else happens. MicroVAX comes back to
> ">>>" prompt after a few minutes, no other messages.
> Should I expect to hear some noises of the plate at the
> bottom
> of the caddie moving sideways to expose the CD to the
> laser,
> etc?
>
>
> Also, even if I get to a point where I boot into standalone
> backup, how am I to fix the problem with DKA100's contiguity
> issue?
> The previous owner said he had actual PAKs that he could not
> find, but are loaded in the LMF databse. I would very much
> like to
> at least be able to copy the LMF and am averse to
> reinstalling a
> fresh copy of VMS on DKA100 (everyobdy here will understand
> exactly why this is super-important now).
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> >
> > >
> > >
> > > On Mon, Mar 30, 2020, 11:53 PM John H. Reinhardt
> > > <johnhreinhardt at thereinhardts.org
> > > <mailto:johnhreinhardt at thereinhardts.org>> wrote:
> > >
> > >
> > >
> > >
> > > On 3/30/2020 10:46 PM, Ray Jewhurst wrote:
> > >
> > >
> > > > I have tried both the VAXHaven and WinWorldPC
> > > copies of
> > > 5.5-2H4 and I tend to agree that the VAXHaven one is
> > > corrupted
> > > (at least it's never worked for me). But the WinWorldPC
> > > copy
> > > works great. Also, corrupt is the MicroVMS 4.7 TK50
> > > image on
> > > VAXHaven.
> > >
> > >
> > > >
> > >
> > >
> > > > Ray
> > >
> > >
> > >
> > >
> > > The file I got from WinWorldPC came as a ".7z"
> > > archive. and
> > > I unpacked it with "TheUnarchiver". Does that match
> > > what you
> > > did? The file I get from that always gets the "Could
> > > not burn
> > > "VMS 552h4 VAX.iso". The disk image is invalid."
error
> > > from the
> > > Mac disk burn software.
> > >
> > >
> > >
> > >
> > >
> > >
> > > Did you do something differently?
> > >
> > >
> > >
> > >
> > >
> > >
> > > Thanks.
> > >
> > >
> > >
> > >
> > >
> > >
> > > John H. Reinhardt
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
> -- Supratim Sanyal, W1XMT39.19151 N, 77.23432 WQCOCAL::SANYAL
> via HECnet
>
>
10:05 p.m.
Remote troubleshooting and system recovery at its absolute best, executed by a master.
Also many lessons learned about things I have heard about but never really got into in a
pure simulated environment.
Thanks Steve.
---
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
On Mar 31, 2020, at 3:46 PM, Steve Davidson <steve
at davidson.net> wrote:
I am happy to report that Supratim and I have managed to connect me to his system, create
a VAXcluster boot node on SimH, boot the system into the cluster as a satellite and now
running ANALYZE/DISK/REPAIR/READ against the troubled disk.
-Steve
> On Tue, 2020-03-31 at 10:00 -0400, Steve Davidson wrote:
> Supratim,
>
> If you can contact me offline I can probably walk you through any number of scenarios
to deal with this.
>
> -Steve Davidson
>
> SF:iP1
>
>> On Mar 31, 2020, at 01:00, Supratim Sanyal <supratim at riseup.net> wrote:
>>
>> ? On 3/31/20 12:25 AM, John H. Reinhardt wrote:
>>>> On 3/30/2020 10:59 PM, Ray Jewhurst wrote:
>>>> I haven't tried burning but I used p7z through File Roller on
a Linux Mint system. I have only used it as an image on Simh. I am not at my computer
tonight but if you need it tomorrow I can get you a checksum on the unzipped image.
>>>>
>>>> Ray
>>>
>>>
>>> Okay. Maybe it's a difference between Linux and macOOS. I downloaded the
file from WInWorldPC. The actual file came from someone named "Ricky" in
Germany. The file downloaded was "DEC VMS 5.5-2H4 (Jul 1993) [VAX] (ISO).7z" I
ran it through "TheUnarchiver" and it produced a folder with two files. A txt
file and "VMS 552h4 VAX.iso". I tried burning that ISO file but then I get the
disk image is invalid error.
>>>
>>> I'll have to get a copy of SimH running on my Mac and see it it can read
the ISO.
>>>
>>
>> Vaxhaven's AG-PXL1A-RE.iso is 236013792 bytes, Winworld's "VMS 552h4
VAX.iso" is 205508764. Neither can be burnt by MacOS directly from the GUI. The
following command line results in a "raw" burn (remove the -testburn switch to
enable the laser).
>>
>> $ hdiutil burn -testburn -imagekey diskimage-class=CRawDiskImage -speed 2
Downloads/DEC\ VMS\ 5.5-2H4\ \(Jul\ 1993\)\ \[VAX\]\ \(ISO\)/VMS\ 552h4\ VAX.iso
>>
>> The Vaxhaven raw burn does not boot. I will try the Winworld version next. BUT,
just to make sure the RRD42 is not the problem, here's a couple of questions about
it:
>>
>> 1) I have connected the SCSI cable at the bottom and a terminator at the top. Is
this okay?
>>
>> 2) When I insert the caddie in (with the CD in the caddy), the green light turns
on for a few seconds and then turns off. Nothing else happens. MicroVAX comes back to
">>>" prompt after a few minutes, no other messages. Should I expect to
hear some noises of the plate at the bottom of the caddie moving sideways to expose the CD
to the laser, etc?
>>
>> Also, even if I get to a point where I boot into standalone backup, how am I to
fix the problem with DKA100's contiguity issue?
>>
>> The previous owner said he had actual PAKs that he could not find, but are loaded
in the LMF databse. I would very much like to at least be able to copy the LMF and am
averse to reinstalling a fresh copy of VMS on DKA100 (everyobdy here will understand
exactly why this is super-important now).
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>>>
>>>> On Mon, Mar 30, 2020, 11:53 PM John H. Reinhardt <johnhreinhardt at
thereinhardts.org <mailto:johnhreinhardt at thereinhardts.org>> wrote:
>>>>
>>>> On 3/30/2020 10:46 PM, Ray Jewhurst wrote:
>>>> > I have tried both the VAXHaven and WinWorldPC copies of 5.5-2H4
and I tend to agree that the VAXHaven one is corrupted (at least it's never worked for
me). But the WinWorldPC copy works great. Also, corrupt is the MicroVMS 4.7 TK50 image on
VAXHaven.
>>>> >
>>>> > Ray
>>>>
>>>> The file I got from WinWorldPC came as a ".7z" archive.
and I unpacked it with "TheUnarchiver". Does that match what you did? The file
I get from that always gets the "Could not burn "VMS 552h4 VAX.iso". The
disk image is invalid." error from the Mac disk burn software.
>>>>
>>>>
>>>> Did you do something differently?
>>>>
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> John H. Reinhardt
>>>>
>>>
>> --
>> Supratim Sanyal, W1XMT
>> 39.19151 N, 77.23432 W
>> QCOCAL::SANYAL via HECnet
11:42 p.m.
folks,
ummm ... not sure how to sugarcoat this, but Steve found the root problem:
the hard disk in the MicroVAX 3100 model 80 has OpenVMS Alpha installed
on it.
Best,
Supratim
On 3/31/20 4:05 PM, Supratim Sanyal wrote:
Remote troubleshooting and system recovery at its
absolute best,
executed by a master.
Also many lessons learned about things I have heard about but never
really got into in a pure simulated environment.
Thanks Steve.
---
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet <http://www.update.uu.se/~bqt/hecnet.html>
On Mar 31, 2020, at 3:46 PM, Steve Davidson <steve at davidson.net
<mailto:steve at davidson.net>> wrote:
> I am happy to report that Supratim and I have managed to connect me
> to his system, create a VAXcluster boot node on SimH, boot the system
> into the cluster as a satellite and now running
> ANALYZE/DISK/REPAIR/READ against the troubled disk.
>
> -Steve
>
> On Tue, 2020-03-31 at 10:00 -0400, Steve Davidson wrote:
>> Supratim,
>>
>> If you can contact me offline I can probably walk you through any
>> number of scenarios to deal with this.
>>
>> -Steve Davidson
>>
>> SF:iP1
>>
>>> On Mar 31, 2020, at 01:00, Supratim Sanyal <supratim at riseup.net
>>> <mailto:supratim at riseup.net>> wrote:
>>>
>>> ? On 3/31/20 12:25 AM, John H. Reinhardt wrote:
>>>> On 3/30/2020 10:59 PM, Ray Jewhurst wrote:
>>>>> I haven't tried burning but I used p7z through File Roller on a
>>>>> Linux Mint system. I have only used it as an image on Simh. I am
>>>>> not at my computer tonight but if you need it tomorrow I can get
>>>>> you a checksum on the unzipped image.
>>>>>
>>>>> Ray
>>>>
>>>>
>>>> Okay. Maybe it's a difference between Linux and macOOS.? I
>>>> downloaded the file from WInWorldPC. The actual file came from
>>>> someone named "Ricky" in Germany.? The file downloaded was
"DEC
>>>> VMS 5.5-2H4 (Jul 1993) [VAX] (ISO).7z"? I ran it through
>>>> "TheUnarchiver" and it produced a folder with two files.? A txt
>>>> file and "VMS 552h4 VAX.iso". I tried burning that ISO file but
>>>> then I get the disk image is invalid error.
>>>>
>>>> I'll have to get a copy of SimH running on my Mac and see it it
>>>> can read the ISO.
>>>>
>>>
>>> Vaxhaven's AG-PXL1A-RE.iso is 236013792 bytes, Winworld's "VMS
>>> 552h4 VAX.iso" is 205508764. Neither can be burnt by MacOS directly
>>> from the GUI. The following command line results in a "raw" burn
>>> (remove the -testburn switch to enable the laser).
>>>
>>> $ hdiutil burn -testburn -imagekey diskimage-class=CRawDiskImage
>>> -speed 2 Downloads/DEC\ VMS\ 5.5-2H4\ \(Jul\ 1993\)\ \[VAX\]\
>>> \(ISO\)/VMS\ 552h4\ VAX.iso
>>>
>>> The Vaxhaven raw burn does not boot. I will try the Winworld
>>> version next. BUT, just to make sure the RRD42 is not the problem,
>>> here's a couple of questions about it:
>>>
>>> 1) I have connected the SCSI cable at the bottom and a terminator
>>> at the top. Is this okay?
>>>
>>> 2) When I insert the caddie in (with the CD in the caddy), the
>>> green light turns on for a few seconds and then turns off. Nothing
>>> else happens. MicroVAX comes back to ">>>" prompt after a
few
>>> minutes, no other messages. Should I expect to hear some noises of
>>> the plate at the bottom of the caddie moving sideways to expose the
>>> CD to the laser, etc?
>>>
>>> Also, even if I get to a point where I boot into standalone backup,
>>> how am I to fix the problem with DKA100's contiguity issue?
>>>
>>> The previous owner said he had actual PAKs that he could not find,
>>> but are loaded in the LMF databse. I would very much like to at
>>> least be able to copy the LMF and am averse to reinstalling a fresh
>>> copy of VMS on DKA100 (everyobdy here will understand exactly why
>>> this is super-important now).
>>>
>>>
>>>
>>>
>>>
>>>
>>>>>
>>>>> On Mon, Mar 30, 2020, 11:53 PM John H. Reinhardt
>>>>> <johnhreinhardt at thereinhardts.org
>>>>> <mailto:johnhreinhardt at thereinhardts.org>> wrote:
>>>>>
>>>>> ??? On 3/30/2020 10:46 PM, Ray Jewhurst wrote:
>>>>> ??? > I have tried both the VAXHaven and WinWorldPC copies of
>>>>> 5.5-2H4 and I tend to agree that the VAXHaven one is corrupted
>>>>> (at least it's never worked for me). But the WinWorldPC copy
>>>>> works great. Also, corrupt is the MicroVMS 4.7 TK50 image on
>>>>> VAXHaven.
>>>>> ??? >
>>>>> ??? > Ray
>>>>>
>>>>> ??? The file I got from WinWorldPC came as a ".7z"
archive.? and
>>>>> I unpacked it with "TheUnarchiver".? Does that match what
you
>>>>> did? The file I get from that always gets the "Could not burn
>>>>> "VMS 552h4 VAX.iso". The disk image is invalid." error
from the
>>>>> Mac disk burn software.
>>>>>
>>>>>
>>>>> ??? Did you do something differently?
>>>>>
>>>>>
>>>>> ??? Thanks.
>>>>>
>>>>>
>>>>> ??? John H. Reinhardt
>>>>>
>>>>
>>> --
>>> Supratim Sanyal, W1XMT
>>> 39.19151 N, 77.23432 W
>>> QCOCAL::SANYAL via HECnet
--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
11:44 p.m.
Hello!
I''m surprised. What next then?
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Tue, Mar 31, 2020 at 5:42 PM Supratim Sanyal <supratim at riseup.net> wrote:
folks,
ummm ... not sure how to sugarcoat this, but Steve found the root problem:
the hard disk in the MicroVAX 3100 model 80 has OpenVMS Alpha installed on it.
Best,
Supratim
On 3/31/20 4:05 PM, Supratim Sanyal wrote:
Remote troubleshooting and system recovery at its absolute best, executed by a master.
Also many lessons learned about things I have heard about but never really got into in a
pure simulated environment.
Thanks Steve.
---
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
On Mar 31, 2020, at 3:46 PM, Steve Davidson <steve at davidson.net> wrote:
I am happy to report that Supratim and I have managed to connect me to his system, create
a VAXcluster boot node on SimH, boot the system into the cluster as a satellite and now
running ANALYZE/DISK/REPAIR/READ against the troubled disk.
-Steve
On Tue, 2020-03-31 at 10:00 -0400, Steve Davidson wrote:
Supratim,
If you can contact me offline I can probably walk you through any number of scenarios to
deal with this.
-Steve Davidson
SF:iP1
On Mar 31, 2020, at 01:00, Supratim Sanyal <supratim at riseup.net> wrote:
? On 3/31/20 12:25 AM, John H. Reinhardt wrote:
On 3/30/2020 10:59 PM, Ray Jewhurst wrote:
I haven't tried burning but I used p7z through File Roller on a Linux Mint system. I
have only used it as an image on Simh. I am not at my computer tonight but if you need it
tomorrow I can get you a checksum on the unzipped image.
Ray
Okay. Maybe it's a difference between Linux and macOOS. I downloaded the file from
WInWorldPC. The actual file came from someone named "Ricky" in Germany. The
file downloaded was "DEC VMS 5.5-2H4 (Jul 1993) [VAX] (ISO).7z" I ran it
through "TheUnarchiver" and it produced a folder with two files. A txt file and
"VMS 552h4 VAX.iso". I tried burning that ISO file but then I get the disk image
is invalid error.
I'll have to get a copy of SimH running on my Mac and see it it can read the ISO.
Vaxhaven's AG-PXL1A-RE.iso is 236013792 bytes, Winworld's "VMS 552h4
VAX.iso" is 205508764. Neither can be burnt by MacOS directly from the GUI. The
following command line results in a "raw" burn (remove the -testburn switch to
enable the laser).
$ hdiutil burn -testburn -imagekey diskimage-class=CRawDiskImage -speed 2 Downloads/DEC\
VMS\ 5.5-2H4\ \(Jul\ 1993\)\ \[VAX\]\ \(ISO\)/VMS\ 552h4\ VAX.iso
The Vaxhaven raw burn does not boot. I will try the Winworld version next. BUT, just to
make sure the RRD42 is not the problem, here's a couple of questions about it:
1) I have connected the SCSI cable at the bottom and a terminator at the top. Is this
okay?
2) When I insert the caddie in (with the CD in the caddy), the green light turns on for a
few seconds and then turns off. Nothing else happens. MicroVAX comes back to
">>>" prompt after a few minutes, no other messages. Should I expect to
hear some noises of the plate at the bottom of the caddie moving sideways to expose the CD
to the laser, etc?
Also, even if I get to a point where I boot into standalone backup, how am I to fix the
problem with DKA100's contiguity issue?
The previous owner said he had actual PAKs that he could not find, but are loaded in the
LMF databse. I would very much like to at least be able to copy the LMF and am averse to
reinstalling a fresh copy of VMS on DKA100 (everyobdy here will understand exactly why
this is super-important now).
On Mon, Mar 30, 2020, 11:53 PM John H. Reinhardt <johnhreinhardt at thereinhardts.org
<mailto:johnhreinhardt at thereinhardts.org>> wrote:
On 3/30/2020 10:46 PM, Ray Jewhurst wrote:
I have tried both the VAXHaven and WinWorldPC
copies of 5.5-2H4 and I tend to agree that the VAXHaven one is corrupted (at least
it's never worked for me). But the WinWorldPC copy works great. Also, corrupt is the
MicroVMS 4.7 TK50 image on VAXHaven.
Ray
The file I got from WinWorldPC came as a ".7z" archive. and I unpacked it
with "TheUnarchiver". Does that match what you did? The file I get from that
always gets the "Could not burn "VMS 552h4 VAX.iso". The disk image is
invalid." error from the Mac disk burn software.
Did you do something differently?
Thanks.
John H. Reinhardt
--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
11:50 p.m.
You?re surprised. You should have been here when I tried to execute WRITEBOOT from the
local drive and it comes back ?not a VAX image?...
Now I will rebuild the system using the boot node for disk connectivity. Should be pretty
quick after the savesets are out in place. It will FLY when I?m finished with it...
-Steve
SF:IP2
On Mar 31, 2020, at 17:46, Gregg Levine
<gregg.drwho8 at gmail.com> wrote:
?Hello!
I''m surprised. What next then?
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
> On Tue, Mar 31, 2020 at 5:42 PM Supratim Sanyal <supratim at riseup.net>
wrote:
>
> folks,
>
> ummm ... not sure how to sugarcoat this, but Steve found the root problem:
>
> the hard disk in the MicroVAX 3100 model 80 has OpenVMS Alpha installed on it.
>
> Best,
> Supratim
>
> On 3/31/20 4:05 PM, Supratim Sanyal wrote:
>
> Remote troubleshooting and system recovery at its absolute best, executed by a
master.
>
> Also many lessons learned about things I have heard about but never really got into
in a pure simulated environment.
>
> Thanks Steve.
>
>
> ---
> Supratim Sanyal, W1XMT
> 39.19151 N, 77.23432 W
> QCOCAL::SANYAL via HECnet
>
>
> On Mar 31, 2020, at 3:46 PM, Steve Davidson <steve at davidson.net> wrote:
>
> I am happy to report that Supratim and I have managed to connect me to his system,
create a VAXcluster boot node on SimH, boot the system into the cluster as a satellite and
now running ANALYZE/DISK/REPAIR/READ against the troubled disk.
>
> -Steve
>
> On Tue, 2020-03-31 at 10:00 -0400, Steve Davidson wrote:
>
> Supratim,
>
> If you can contact me offline I can probably walk you through any number of scenarios
to deal with this.
>
> -Steve Davidson
>
> SF:iP1
>
> On Mar 31, 2020, at 01:00, Supratim Sanyal <supratim at riseup.net> wrote:
>
> ? On 3/31/20 12:25 AM, John H. Reinhardt wrote:
>
> On 3/30/2020 10:59 PM, Ray Jewhurst wrote:
>
> I haven't tried burning but I used p7z through File Roller on a Linux Mint
system. I have only used it as an image on Simh. I am not at my computer tonight but if
you need it tomorrow I can get you a checksum on the unzipped image.
>
> Ray
>
>
>
> Okay. Maybe it's a difference between Linux and macOOS. I downloaded the file
from WInWorldPC. The actual file came from someone named "Ricky" in Germany.
The file downloaded was "DEC VMS 5.5-2H4 (Jul 1993) [VAX] (ISO).7z" I ran it
through "TheUnarchiver" and it produced a folder with two files. A txt file and
"VMS 552h4 VAX.iso". I tried burning that ISO file but then I get the disk image
is invalid error.
>
> I'll have to get a copy of SimH running on my Mac and see it it can read the
ISO.
>
>
> Vaxhaven's AG-PXL1A-RE.iso is 236013792 bytes, Winworld's "VMS 552h4
VAX.iso" is 205508764. Neither can be burnt by MacOS directly from the GUI. The
following command line results in a "raw" burn (remove the -testburn switch to
enable the laser).
>
> $ hdiutil burn -testburn -imagekey diskimage-class=CRawDiskImage -speed 2
Downloads/DEC\ VMS\ 5.5-2H4\ \(Jul\ 1993\)\ \[VAX\]\ \(ISO\)/VMS\ 552h4\ VAX.iso
>
> The Vaxhaven raw burn does not boot. I will try the Winworld version next. BUT, just
to make sure the RRD42 is not the problem, here's a couple of questions about it:
>
> 1) I have connected the SCSI cable at the bottom and a terminator at the top. Is this
okay?
>
> 2) When I insert the caddie in (with the CD in the caddy), the green light turns on
for a few seconds and then turns off. Nothing else happens. MicroVAX comes back to
">>>" prompt after a few minutes, no other messages. Should I expect to
hear some noises of the plate at the bottom of the caddie moving sideways to expose the CD
to the laser, etc?
>
> Also, even if I get to a point where I boot into standalone backup, how am I to fix
the problem with DKA100's contiguity issue?
>
> The previous owner said he had actual PAKs that he could not find, but are loaded in
the LMF databse. I would very much like to at least be able to copy the LMF and am averse
to reinstalling a fresh copy of VMS on DKA100 (everyobdy here will understand exactly why
this is super-important now).
>
>
>
>
>
>
>
> On Mon, Mar 30, 2020, 11:53 PM John H. Reinhardt <johnhreinhardt at
thereinhardts.org <mailto:johnhreinhardt at thereinhardts.org>> wrote:
>
> On 3/30/2020 10:46 PM, Ray Jewhurst wrote:
>> I have tried both the VAXHaven and WinWorldPC copies of 5.5-2H4 and I tend to
agree that the VAXHaven one is corrupted (at least it's never worked for me). But the
WinWorldPC copy works great. Also, corrupt is the MicroVMS 4.7 TK50 image on VAXHaven.
>>
>> Ray
>
> The file I got from WinWorldPC came as a ".7z" archive. and I unpacked
it with "TheUnarchiver". Does that match what you did? The file I get from that
always gets the "Could not burn "VMS 552h4 VAX.iso". The disk image is
invalid." error from the Mac disk burn software.
>
>
> Did you do something differently?
>
>
> Thanks.
>
>
> John H. Reinhardt
>
>
> --
>
> Supratim Sanyal, W1XMT
>
> 39.19151 N, 77.23432 W
>
> QCOCAL::SANYAL via HECnet
>
> --
> Supratim Sanyal, W1XMT
> 39.19151 N, 77.23432 W
> QCOCAL::SANYAL via HECnet
3 Apr
3 Apr
3:33 a.m.
know for a fact that vms 6.2 on vaxhaven works, have one installed on
a removable disk for the ka41 vax 3100 server from standalone backup
from cdrom
think burned from k3b on linux x64 and used a 512 cd ...
also the vax software product libraries and either vms 7.1 or 7.2
images work on simh directly, either x64, sparc 64 or arm 64
--
?On the whole, professional pessimists prove right at the end if one
does not hold them too tightly to a time scale.? (Erwin Chargaff,
1978, Heraclitean Fire)
Notice for the terrestrials: This communication may be unlawfully
collected and stored by the National Security Agency (NSA), its
contractors, internet providers, subsidiaries, government agencies
foreign or domestic, and agents, as well as by private parties,
corporations and isp providers, in secret. The parties to this email
do not consent to the retrieving or storing of this communication and
any related metadata, as well as printing, copying, re-transmitting,
disseminating, or otherwise using it. If you believe you have received
this communication in error, please delete it immediately.
Notice for the aliens: based on theories presumably related to fantasy
friends and/or hands, the majority of living organisms on the third
planet from the central star in this solar system are being negatively
impacted by the dominant species, who are choosing to replicate
themselves against the better judgement of the minority, which will
likely result in the elimination of all living organisms on said
planet within the next few decades.
1 Apr
1 Apr
1:26 p.m.
On 3/31/2020 4:42 PM, Supratim Sanyal wrote:
folks,
ummm ... not sure how to sugarcoat this, but Steve found the root problem:
the hard disk in the MicroVAX 3100 model 80 has OpenVMS Alpha installed on it.
Best,
Supratim
That's a pretty neat trick.? Are you still saving the disk contents?? Harvesting Alpha
PAKS from the LMF database is also worthwhile.? Wanna ship the drive to Texas? I'll
hook it up to my DS10 and see what comes off ;-P
John H. Reinhardt
1:45 p.m.
On 4/1/20 7:26 AM, John H. Reinhardt wrote:
On 3/31/2020 4:42 PM, Supratim Sanyal wrote:
:)
An image backup is taken. The LMF db has been saved. It doesn't have
much - Pathworks and UCX.
?License Management Facility? V1.2
?License Database File:??? ????? DUA0:[000000]LMF$LICENSE.LDB;1
?Created on:??? ??? ????? 29-DEC-1997
?Created by user:??? ????? SYSTEM
?Created by LMF Version:????? V1.1
?-----------------------------------
?DW-MOTIF??? ??? ????? DEC
?NET-APP-SUP-150??? ????? DEC
?OPENVMS-ALPHA??? ??? ????? DEC
?OPENVMS-ALPHA??? ??? ????? DEC
?OPENVMS-ALPHA-ADL??? ????? DEC
?PWLMXXXCA06.00??? ??? ????? DEC
?PWLMXXXCA06.00??? ??? ????? DEC
?PWLMXXXFP05.00??? ??? ????? DEC
?PWXXWINAT07.00??? ??? ????? DEC
?PWXXWINAT07.00??? ??? ????? DEC
?UCX??? ??? ??? ????? DEC
folks,
ummm ... not sure how to sugarcoat this, but Steve found the root
problem:
the hard disk in the MicroVAX 3100 model 80 has OpenVMS Alpha
installed on it.
Best,
Supratim
That's a pretty neat trick.? Are you still saving the disk contents??
Harvesting Alpha PAKS from the LMF database is also worthwhile.? Wanna
ship the drive to Texas? I'll hook it up to my DS10 and see what comes
off ;-P
John H. Reinhardt
--
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet
27 Mar
27 Mar
5:23 p.m.
3 is the console on mine..
-Dave
On 3/27/20 4:29 AM, Dan B wrote:
yes, zero is the console
http://www.bitsavers.org/
find the manual, probably leds are on because you don't have a
terminator plug on aui and bnc ...
has been a while ...
--
Dave McGuire, AK4HZ
New Kensington, PA
8:41 p.m.
On 3/27/2020 11:23 AM, Dave McGuire wrote:
3 is the console on mine..
-Dave
Mine as well.? Looking at the back, from left to right it's 0, 1, 3.? 3 is the
console.? 0 and 1 are TTA0: and TTA1: (Under OpenVMS)
--
John H. Reinhardt
On 3/27/20 4:29 AM, Dan B wrote:
yes, zero is the console
http://www.bitsavers.org/
find the manual, probably leds are on because you don't have a
terminator plug on aui and bnc ...
has been a while ...
1495
days inactive
1503
days old
54 comments
18 participants
participants (18)
-
bob＠jfcl.com -
bqt＠softjar.se -
davecoo＠marmotking.com -
denz＠hack42.nl -
dibi58＠gmail.com -
fcoffey＠misernet.net -
gerry77＠mail.com -
gregg.drwho8＠gmail.com -
johnhreinhardt＠thereinhardts.org -
jrbrady65＠gmail.com -
mcguire＠neurotica.com -
pamorin＠gmail.com -
paulkoning＠comcast.net -
pechter＠gmail.com -
raywjewhurst＠gmail.com -
steve＠davidson.net -
supratim＠riseup.net -
wonko＠4amlunch.net