>OTOH, what forces you to upgrade? - If you want to cluster a VAX to an
>Alpha running 6.1, that should be OK: this is the usual way to upgrade a
V6.0 on VAX was OK but short-lived; V6.1 was
somewhat better. Most people either stayed with
V5.5-2 or moved rapidly to V6.1 or V6.2.
I believe that the VAX V6.1 CDs were the
first ones that could be booted directly
into OpenVMS (rather than just being
able to boot S/A BACKUP to restore
the .B saveset).
The Hobbyist people should be able
to supply V7.3. If they cannot do so,
then I believe that you are allowed to
acquire media by any means (specifically
you can have someone copy the CD
On Wed, 29 May 2002, Kevin Murrell wrote:
> I switched from the original group, as I was getting fed up with the
> spam and the rants, but now I found i'm all alone!
> Should I have switched back to cctalk (?)
cctech is a pointless mailing list. It was supposed to stop off-topic
postings but the concept wasn't thought out very well. Hence, no traffic.
Everything is going on at cctalk. I suggest you switch.
Sellam Ismail Vintage Computer Festival
International Man of Intrigue and Danger http://www.vintage.org
* Old computing resources for business and academia at www.VintageTech.com *
cctech mailing list
>I just tried, my VAX 7.2 VMS CD also boots into a minimal VMS from SYS1
>on my MicroVAX. So I guess they changed it between 7.1 and 7.2.
I don't know where they changed but I looked
at a V7.1 binary disk and it had a [SYS1]
directory with many files underneath. The
easy-to-spot difference between S/A BACKUP
and full OpenVMS boot is the number of files.
I don't have either V6.2 or V6.1 to hand so I
don't know if this (undocumented and
unsupported) facility was there back then.
If you tried booting V7.1 and it didn't work,
then either I looked at something other than
V7.1 or you booted incorrectly.
This is a question about an older linux..
I am running redhat 5, on an IBM755c (486)
OH perhaps my laptop is old enough... : ^ )
Anyway I have to enter the following lines every time I reboot:
modprobe ne io=0x300
ifconfig eth0 up
so networking is ready...
my question, Anybody know the --proper-- place to put these 3 lines?
I could just put them in local.rc and be done wid um, but that wouldn't be
the --proper-- place to put them.
Thanks! : ^ )
> From: Sellam Ismail <foo(a)siconic.com>
> cctech is a pointless mailing list. It was supposed to stop off-topic
> postings but the concept wasn't thought out very well. Hence, no
> Everything is going on at cctalk. I suggest you switch.
Yeah, but the flames and OTs sure have cooled down, so in that regard the
What is the best current source for 5.25" floppy cleaning kits?
Collector of classic computers
Build Master for the Altair32 Emulation Project
Web site: http://highgate.comm.sfu.ca/~rcini/classiccmp/
"Jay West" <jwest(a)classiccmp.org> wrote:
> Sellam wrote...
> > cctech is a pointless mailing list. It was supposed to stop off-topic
> > postings but the concept wasn't thought out very well. Hence, no traffic.
> > Everything is going on at cctalk. I suggest you switch.
> Sellam, do you have to be so derrogatory? Just because you didn't like the
> way I set it up is no reason to say the concept wasn't thought out very
Sheesh, here we go again.
OK, it's short shameful confession time. I read Jay's proposal (which
he posted to classiccmp). I even replied (privately) with a
suggestion about how to do one of the things he wanted to do. What I
didn't do was think about the proposal and realize how this was likely
to play out. Hindsight being 20/20, I now recognize my error.
So. Can we just blame me and quit kvetching about this 'til the next
time our most gracious list host feels like it's time to make a
>Normally, a machine that damages boards has got PSU problems (the 5V rail
>sitting at 12V or something). Do you know what the outputs of the PSU
>should be and can you check them? (use a 'scope as well if you have one
>to look for HV ripple on the output -- a common failure mode of SMPSUs is
>a high ESR (or open) output capacitor and you can then get 10-20V spikes
>on the 5V output...).
I no longer have one to look at, but from memory, the
6K regulators are at the back and the outputs are
shielded by transparent plastic covers. Should be easy
enough to remove these and 'scope away. Note however,
that these are there for protection: the voltage is low
but the current is high - remove metal from body before
trying this out!
>One board damaging another is less common unless some component failure
>is shorting one of the pins to a supply line or ground. It can happen (as
>here). Do you know what to expect on each pin (I guess not, as AFAIK DEC
>never published real technical documentation for the VAX 6000 series).
The 6000 tech manuals tended to concentrate on the
programming aspects. There was an XMI handbook which
covered the bus signals and protocol in some detail.
>If there are any recognisable chips on the boards (especially bus
>buffers), check them. And if there are picofuses for the supply lines
>(some machines have them, I have no idea if the VAX 6000 is one of them),
>check those too. It's not unheard-of for a bus short to blow a fuse and
>not damage much else.
The XMI connection was handled by a dedicated chip
(in the "XMI corner") with possibly a few drivers and such
strung around it (much the same concept as with the
I would be surprised if a dead XBIA managed to
also take out an associated XBIB. There are rules about
which boards can go in which slots etc. I had
a few "funny turns" with my 6K but it always turned out
to be a badly seated board, or a missing cable
or the problem being somewhere else and me being
in a rush.
My first step would be to ignore the VAXBI,
remove as many boards as are needed to get the
thing to start at all (which in this case seems
to mean remove the BI-XMI interface boards) and
then add in the XMI end of the interface. Now
try to run diags and see whether the board is
even partially alive. (Obviously it will fail the
tests that go look for the other end of the
interface). If OK so far, empty the VAXBI cage
and add in the BI end of the interface board,
properly hooked up. Pay careful attention to
the transition headers and plugs on the BI
and XMI interfaces. Now see if the diags are
happy or not. If OK, season with further
I did this a few times myself and always
ended up with a full set of working
boards. Maybe I was lucky, maybe there really
were problems with boards being badly seated
or maybe I had a marginal board or two.
Since all my problems happened when I needed
to reconfigure the hardware, I assumed it was
just seating rather than marginal hardware.
I have an adapter that has MMJ female and a DE25-F connector. The
adapter needs to be "made" (i.e. I've got wires coming out of it that
plug into holes in the DE25-F connector). I want to make it so that I'll
use an MMJ cable from the console port of my MicroVAX 3100 to the
adapter, and plug the adapter into the 9-25 adapter cable that's
connected to my PC Serial port.
How do I wire it?
I've got these color wires (not in any particular order)
Which holes should I plug which colors into? Please describe how I
should orient the connector when describing which holes to plug the