Hi guys, I have a MicroVAX 3100, but I am unsure of which model ... On the back, it has a model number of; DV-31ETA-A-A01 On the bottom of the case it has; Series BA42B & CPU KA41 I've google a bit but have no obvious link between these numbers and the human readable model number, like say; 3100/80. Any ideas? regards, Kim
On Fri, 7 Apr 2006, Kim Hawtin wrote:
> Hi guys,
>
> I have a MicroVAX 3100, but I am unsure of which model ...
>
> On the back, it has a model number of; DV-31ETA-A-A01
> On the bottom of the case it has; Series BA42B & CPU KA41
>
> I've google a bit but have no obvious link between these numbers and the
> human readable model number, like say; 3100/80.
>
> Any ideas?
I think some people here speak the language of DEC model codes
fluently, and will perhaps give you an exact answer. Meanwhile,
here's some of what I know...
I think the "BA"-number refers to the physical enclosure of the
machine. The "KA"-numers are much more common and are used to
refer to specific VAX CPU modules, although that scheme is
almost never seen in VAX literature from DEC or 3rd parties.
I've noticed that they sometimes correspond to the value in the
"Id" column of Paul Hardy's CPU model summary, which is
available from:
http://www.hardy.demon.co.uk/paul/programs/vms_cpus.html
For example, my VAXstation 4000/60 is a KA46. My guess is that
yours is one of the CVAX-series MicroVAX/VAXstations:
(Continue reading)Although slow in comparison with rlogin/telnet, the serial console is by far more reliable and comes in handy at times. The problem is what befalls the VAX whenever the PC on the other end of the cable is rebooted (or powered on). As part of its initialisation procedures, the PC BIOS appears to send "break" characters/sequences (what exactly is it?) down the serial cable, and the VAXstation responds by halting to the ">>>"-prompt of the firmware. (Often the situation remains undetected+uncorrected until I need DNS-services or someone else complains about "Internet" not working...) Can this "feature" be disabled? How? -aw
----- Original Message ----- From: "A. Wik" <aw <at> aw.gs> To: <port-vax <at> NetBSD.org> Sent: Friday, April 07, 2006 3:48 AM Subject: Serial breaks > Although slow in comparison with rlogin/telnet, the serial > console is by far more reliable and comes in handy at times. > The problem is what befalls the VAX whenever the PC on the > other end of the cable is rebooted (or powered on). My solution was to get a terminal server. That way, if I reboot the PC, the terminal server stays running and so does the vax. It also lets me log into the console of my Vaxen from any machine on my lan, which is rather nice. I use a DECserver 200M (MC?). Jim
> The problem is what befalls the VAX whenever the PC on the other end
> of the cable is rebooted (or powered on). As part of its
> initialisation procedures, the PC BIOS appears to send "break"
> characters/sequences (what exactly is it?) down the serial cable,
A break condition is not a character. (It also may not be what's
happening here - see below.)
To understand what a break condition actually is, you need to
understand how characters are represented on a serial line. You may
already know some of this; to avoid back-and-forth explanations, I'll
assume you know just about nothing.
Serial lines such as your VAX's console are, electrically, RS-232.
(They often do not follow the other parts of RS-232; for example, some
(all?) VAX consoles use a DE9 connector instead of a DB25.) RS-232 (an
EIA standard, EIA RS-232-C I think it is in full) is a voltage-based
spec, specifying two states for data transmission: two different
voltages on the data line (referenced to the signal ground line).
There are a bunch of other lines as well, carrying non-data information
such as "ring indicator" - the standard was designed for use with
modems and the like. (These voltages are something like, +3 to +15
volts is one state and -3 to -15 volts is the other. ±12V is perhaps
most commonly used.) You may sometimes see these two states called
"mark" and "space", largely for historical reasons.
When idling (ie, no data being sent), the line is in one of these two
voltage states. Since it is the one corresponding to a 1 data bit, it
is usually taken as "high" when drawing graphs. When a character
starts, the line is driven to the other state ("0") for a particular
(Continue reading)
A. Wik wrote: > Although slow in comparison with rlogin/telnet, the serial > console is by far more reliable and comes in handy at times. > The problem is what befalls the VAX whenever the PC on the > other end of the cable is rebooted (or powered on). As part > of its initialisation procedures, the PC BIOS appears to send > "break" characters/sequences (what exactly is it?) down the > serial cable, and the VAXstation responds by halting to the > ">>>"-prompt of the firmware. (Often the situation remains > undetected+uncorrected until I need DNS-services or someone > else complains about "Internet" not working...) > > Can this "feature" be disabled? How? > > -aw > > The solution that worked for me with NetBSD/alpha 3.0 was to compile a kernel with: options DDB_FROMCONSOLE=0 as explained here: http://mail-index.netbsd.org/port-alpha/2005/01/04/0000.html Worked like a charm on a DEC 3000/700, might work also for a VAX :) Rowdy(Continue reading)
blaz.antonic <at> siol.net wrote: >>I have a MicroVAX 3100, but I am unsure of which model ... >> >>On the back, it has a model number of; DV-31ETA-A-A01 >>On the bottom of the case it has; Series BA42B & CPU KA41 >> >>I've google a bit but have no obvious link between these numbers and the >>human readable model number, like say; 3100/80. >> >>Any ideas? > > http://www.netbsd.org/Documentation/Hardware/Machines/DEC/vax/microvaxes.html#section:microvaxes > > Boot it up for exact CPU string (KA41-what exactly ?). Not sure will have to check. However, spent a whole lot more time on goolge and matched the serial# and model# to a 3100/20e... will check what the CPU type is next time I reboot it. The above netbsd page also points to same. cheers, Kim
Hello, Your mail to andrewf <at> bcs.org.uk was caught by the SpamAssassin filter running on the bcs.org.uk mail system. To confirm that your mail is genuine, please click this link, or paste it into your browser: https://bcsnet.bcs.org.uk/approve.php?c=63de45d27e67aad43c13ed5a You will not have to do this again for any mail sent to this recipient (andrewf <at> bcs.org.uk). Thank you. -- -- British Computer Society - www.bcs.org.uk Email Services from gradwell dot com - www.gradwell.com
Hello, Your mail to efmiwg7 <at> bcs.org.uk was caught by the SpamAssassin filter running on the bcs.org.uk mail system. To confirm that your mail is genuine, please click this link, or paste it into your browser: https://bcsnet.bcs.org.uk/approve.php?c=6b918fd45057059bc6c2649 You will not have to do this again for any mail sent to this recipient (efmiwg7 <at> bcs.org.uk). Thank you. -- -- British Computer Society - www.bcs.org.uk Email Services from gradwell dot com - www.gradwell.com
Hello! Just for the sake of argument, is everyone seeing that below in their message traffic? Can we convince the recipient to do something about it? Because what it says there is false. It happens that it arrives every time that broken software he's got running even thinks it trapped something from us. (Which will probably happen here, and I'll ignore it, since I'm the blankety-blank who's doing it.) --- Gregg C Levine hansolofalcon <at> worldnet.att.net --- "Remember the Force will be with you. Always." Obi-Wan Kenobi > -----Original Message----- > From: port-vax-owner <at> NetBSD.org [mailto:port-vax-owner <at> NetBSD.org] On > Behalf Of efmiwg7 <at> bcs.org.uk > Sent: Saturday, April 22, 2006 7:44 PM > To: port-vax <at> netbsd.org > Subject: Re: Returned mail: see transcript for details > > Hello, > > Your mail to efmiwg7 <at> bcs.org.uk was caught by the > SpamAssassin filter running on the bcs.org.uk mail system. > > To confirm that your mail is genuine, please click this > link, or paste it into your browser: > https://bcsnet.bcs.org.uk/approve.php?c=6b918fd45057059bc6c2649 > > You will not have to do this again for any mail sent(Continue reading)
RSS Feed3 | |
|---|---|
58 | |
98 | |
37 | |
263 | |
27 | |
2 | |
5 | |
4 | |
5 | |
31 | |
86 | |
46 | |
24 | |
32 | |
31 | |
1 | |
4 | |
5 | |
3 | |
6 | |
7 | |
5 | |
26 | |
14 | |
1 | |
5 | |
5 | |
13 | |
12 | |
68 | |
15 | |
9 | |
28 | |
28 | |
11 | |
81 | |
6 | |
3 | |
1 | |
5 | |
2 | |
4 | |
9 | |
11 | |
21 | |
20 | |
35 | |
109 | |
194 | |
39 | |
23 | |
3 | |
7 | |
4 | |
32 | |
4 | |
7 | |
48 | |
77 | |
32 | |
2 | |
9 | |
33 | |
12 | |
27 | |
59 | |
7 | |
25 | |
100 | |
41 | |
24 | |
12 | |
20 | |
8 | |
21 | |
31 | |
3 | |
12 | |
19 | |
7 | |
19 | |
88 | |
57 | |
11 | |
68 | |
52 | |
17 | |
3 | |
18 | |
2 | |
27 | |
32 | |
73 | |
46 | |
20 | |
46 | |
55 | |
18 | |
51 | |
17 | |
53 | |
103 | |
33 | |
26 | |
62 | |
72 | |
70 | |
126 | |
126 | |
98 | |
72 | |
50 | |
34 | |
119 | |
58 | |
119 | |
83 | |
190 | |
132 | |
167 | |
188 | |
182 | |
356 | |
66 | |
33 | |
159 | |
279 | |
315 | |
227 | |
63 | |
1 | |
1 |
