Anybody got a copy of OpenVMS/VAX 7.2 that they can make an image of
for me? (if possible; easier to download/burn than to mail)...
I got one from Doc a few months ago, but cant find it now...
Bill
--
Bill Bradford
mrbill(a)mrbill.net
Austin, TX
On May 18, 10:19, Zane H. Healy wrote:
> I'm assuming the following means it's safe for me to have this system
> connected to the net. I'm now in the process of also testing with
> www.ordb.com, and have already tried the telnet trick posted earlier.
> Relay test 3
>
> >>> RSET
> <<<
>
> Relay test result
>
> Could not reset connection, test failed.
Um, no, I'm afraid it means your SMTP software bombed. It failed to go to
the reset (initial) state after the second test, so the test sequence was
aborted, and the remaining 16 or so (?) tests weren't carried out. I
wouldn't trust that software just yet...
I think the next test would have been something involving a message
ostensibly from the "<>" address (which represents the mailer daemon), and
then some tests involving forged addresses intended to look like your own
domain, and then assorted routed or malformed addresses. Some of these are
very important, and your site hasn't been tested for most of them.
--
Pete Peter Turnbull
Network Manager
University of York
Hello all,
I am relatively new to vintage computing and this list,
although I've been working and playing with computers for a
long time. I am, however, a software guy and have only a
little skill with or knowledge of hardware.
I've recently acquired a pair of Altair computers (8800 and
8800a) both equipped with the "88-DCDD" single 8" disk
drives. Unfortunately, I am having various difficulties
with these machines. Hopefully the answers to some
questions will push me towards a better understanding of
these systems.
My main issue at the moment revolves around the EPROM cards
that hold the disk boot loader (DBL) PROMs for these
machines. The cards are Solid State Music ?2K/4K? cards
with 16 slots for 1702s. I asked the list about these cards
before and have since obtained an assembly/instruction
manual, but it is still unclear to me how these things are
configured and addressed.
There are four address switches which are supposed to
address the board as follows (this is taken from the
manual):
Address:
000 000 to 017 377 - All switches on
020 000 to 037 377 - A2, A3, A4 on
040 000 to 057 377 - A1, A3, A4 on
060 000 to 077 377 - A3, A4 on
100 000 to 117 377 - A1, A2, A4 on
120 000 to 137 377 - A2, A4 on
140 000 to 157 377 - A1, A4 on
160 000 to 177 377 - A4 on
200 000 to 217 377 - A1, A2, A3 on
220 000 to 237 377 - A2, A3 on
240 000 to 257 377 - A1, A3 on
260 000 to 277 377 - A3 on
300 000 to 317 377 - A1, A2 on
320 000 to 337 377 - A2 on
240 000 to 357 377 - A1 on
360 000 to 377 377 - None on
I see issues with this from the outset. First, assuming
this is octal, the addresses past 160 000 are beyond the
address space of the 8080 chip in the Altair (200 000 being
64K). As well, the gap of 16k at 160 000 to 200 000 is
either an error in the manual or something I am missing
since I can?t imagine the binary progression of switches
having that gap. How is this card addressed?
I?ve tried examining my way through the memory areas that I
think are supposed to be addressed into the EPROMs (based
upon various assumptions) but I get results that have me
confused. Answers to some of these questions might help:
Why would the address lights on the Altair not properly
correspond to the address switches being set? If I set the
switches at 1110111000000000, for instance, when I reset
then examine the light at A11 doesn?t come on (the lights
show 1110011000000000) even though I know that LED to be
functioning.
Why would the data lights ever show anything but on or off?
I sometimes get dim glows from the data LEDs.
What data can I expect to be in the RAM on boot-up? Is this
answer different for Static vs. Dynamic RAM?
What is the best way to execute the boot loader should I
locate it? Can I set the address switches to the proper
spot and run or do I need to code a simple program that will
?JMP? to the known address?
Much of my confusion might stem from the EPROMs themselves
since they may have been erased by time. I have a freshly
burned set on order which may help.
Please forgive my ignorance and this really long post.
Thanks in advance,
Erik
_______________________________________________
cctech mailing list
cctech(a)classiccmp.org
http://www.classiccmp.org/mailman/listinfo/cctech
>Well, a diskette jammed in the PB 5300ce's drive last week,
>and in addition to a spring or something broken or missing
>on the eject mechanism, I seem to have knocked the upper
>head out of alignment, so it's kaput (and the topic is
>admittedly off-topic as the 5300 is a 1996 product).
>
>Assuming no one has one, I'd really appreciate it if those
>of you who come by such things on a fairly regular basis
>would keep an eye out for one. They may be unique to the
>5300, or may be used in one of the contemporaneous models.
>
>I'm sure Shreve Systems likely has them, but their prices
>vary widely, perhaps based on supply/demand, perhaps not.
Check the LEM Swap list. you can subscribe at www.lowendmac.com.
If you don't want to deal with subscribing just to look for one item, let
me know, and I will be happy to act as proxy for you.
-chris
<http://www.mythtech.net>
Hello Erik,
Tony's response to your post was right on. I would like to add that
the MITS boot eprom must be located at 177400 (or FF00H) to
work correctly.
So in your case, all switches should be off to locate the card at
360 000 to 377 377 (F000 to FFFF) in the last 4k block. The
DBL eprom should then be in the last socket (highest addressable
socket) of the eprom card.
Once things are configured correctly, you should be able to set
the front panel switches to FF00, hit 'Examine', and then hit 'Run' ...
at which point the drive should enable, the head should load, and
then an attempt to read the boot tracks (0-5 is typical for MITS
software) should proceed.
Best regards,
Scott
I saw a pair of Evans & Sutherland PS-390's (small end table sized) down
at Purdue Salvage today. I was wondering if they had any value... I saw a
few cables for them and keyboard and a digitizing tablet, but no monitors.
Drop me a line if anyone wants one. I should be able to get them for
somewhere between $50 and $100 for it all (both of them + accessories).
Also there were several binders full of stuff. At a minimum, I'm gonna
get the manuals for them...
-- Pat
Hi,
finally I got around branching off a power line from my 220V 60A
dedicated computer power circuit :-) I have all three phases of
the VAX connected to a single 110 V phase.
Matt, I fiddled with the fuses and found that I had to have F1 and
F2 connected or else more than half of the outlets would habve no
power. This whole power distribution and interlock system is still
a mystery to me, does anyone have schematics for it? What worries
me is that the key switch seems to have no effect whatsoever, it
doesn't provide any more or less power, and throwing it from OFF
to LOCAL doesn't effect any reboot attempt on the console system.
Anyhow, I can get to the console and do some
@140200G
and indeed the RX01 starts klicking and up comes the console
program. It tells me that the WCS and FPLA versions mismatch,
(0E-xx vs 0F) but that isn't fatal, I gather.
Then I did a TEST with the MIC diagnostics floppy and that
runs through sections 01 to 07 and then has an error to
report with module M8234 (PCS CPU PROM CONTROL STORE, as I
gather.) The appropriate course of action would be to call
DEC field service and replace the board, I guess. Too bad.
I suppose the trick with replacing the M8234 will be the
PCS version. I noted that if WCS and PCS versions mismatch,
that would be a fatal error to begin with. That means it
will be extremely hard to replace the PCS, or won't it?
Could one do anything to repair that PCS? I suppose so, but
not if one has no idea what's wrong with it. Any advice?
Back in normal console mode, I tried to do a BOOT anyway,
just to see if that PCS problem may be not that bad. But
that's a no go, it comes up to a failure pretty quick. Could
be that it's just because the default boot device isn't there,
but it's too quick with the error.
So, that will be a more difficult start then. But I guess I'm
still lucky because at least I can get to the MIC diagnostics
at all (poor Matt.) But of course one wonders what else might
be broken?
Is there a way to copy console floppies? I noticed some
serious bit rott, as only one out of three standard console
floppies actually worked. I guess it's about time to back
up the good ones before they go too.
thanks
-Gunther
--
Gunther Schadow, M.D., Ph.D. gschadow(a)regenstrief.org
Medical Information Scientist Regenstrief Institute for Health Care
Adjunct Assistant Professor Indiana University School of Medicine
tel:1(317)630-7960 http://aurora.regenstrief.org
Tony Duell wrote:
> [Long political rant deleted]
>
> Could somebody please explain to me how that rant has anything to do with
> classic computers
Hehe... I think the problem is that good old Godwin's Law
[http://www.godwinslaw.com/] seems to infest this list at times. :)
People are too willing to fan the flames when quasi-political ranting is
brought up, instead of letting the moderator take care of it. That's the
real problem.
--
Ryan Underwood, <nemesis at icequake.net>, icq=10317253
Eric Klein said:
> I see issues with this from the outset. First, assuming
> this is octal, the addresses past 160 000 are beyond the
> address space of the 8080 chip in the Altair (200 000 being
> 64K).
Not if it's split octal. Each byte converted to octal and listed
separately.
Roger Ivie
ivie(a)cc.usu.edu
> jkunz(a)unixag-kl.fh-kl.de wrote:
>On 17 May, Antonio Carlini wrote:
>
>> There should be a little slide switch at the back. When it is
>> up it will use that port (3 - with the printer icon)
>And what will it do when the switch is down? Autoboot? I know that
>switch from VAXstations to switch the machine from graphics to serial
>console. But this machine has no graphics.
With the switch down (the normal position)
the console is on MMJ-0 and a <BREAK>
on the terminal will be ignored. With the
switch up MMJ-3 will be used as the
alternative console and <BREAK> will
halt the system.
As far as autobooting goes, that's
not dependent on the switch setting - it
depends on the console settings as
stored in NVRAM.
I think this is pretty much the same
for all the MicroVAX 3100 systems.
It is also true for all the VAXstation
3100/4000 systems except (as you note)
with the switch down the graphics
head is used as a console and
not MMJ-0.
Antonio