| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 212.1 | 3 EISA/ISA Slots | DANGER::HAYES | | Fri Aug 23 1996 12:57 | 7 |
| 212.2 | | POBOXB::BAK | | Fri Aug 23 1996 13:02 | 13 |
| 212.3 | Which slots are PCI/EISA? | TEXAS1::SOBECKY | runnin' against the wind | Mon Aug 26 1996 16:18 | 9 |
| 212.4 | Decal misleading | POBOXB::DUNCAN | | Mon Aug 26 1996 17:54 | 4 |
| 212.5 | ECU TO BE RUN | JGODCL::BRINKS | Peter Brinks, DTN 7889-9458 Logist. Eng/Tr Nijmegen | Tue Sep 24 1996 12:03 | 7 |
| 212.6 | | LANDO::CUMMINS | | Tue Sep 24 1996 12:18 | 25 |
| 212.7 | Move the NVRAM to the new module | DANGER::HAYES | | Tue Sep 24 1996 17:11 | 9 |
| 212.8 | EISA Peculiarity | DABEAN::REED | | Mon Jun 02 1997 15:26 | 11 |
| We had to run the ECU in order to get a new installation (tailoring
the Factory Installed Software- in this case, DUNIX 4.0B-) to work.
Fortunately, RDG knew about this. It was hard for us to understand at
first, since there were no EISA options...
Also some confusion arose from the fact that the distribution CD was
labeled v4.0C, which doesn't exist yet. System banner says 4.0B as it
should.
Chris Reed MCS E. Prov., RI
|
| 212.9 | When to run ECU | HARMNY::CUMMINS | | Tue Jun 03 1997 09:52 | 28 |
| Have seen some questions from Field recently re: ECU and when it should
be run. Here's a summary.. Once ECU has been run, it need not be run
again unless:
1. Your EISA/ISA config changes.
2. You swap/upgrade the board which has the embedded NVRAM part used
to store the config data. On 4000/4100, this is the PCI motherboard
(aka the Saddle, which has the 8KB ESC NVRAM part on it).
3. You clear the NVRAM part via deposit commands or SRM console-based
script (e.g. CLEAR_ARC_NVRAM).
4. You switch between booting NT and one of UNIX/VMS (or vice versa).
E.g. UNIX will appear to hang during boot-up if NT ECU data is in
NVRAM rather than UNIX/VMS ECU data. And it won't necessarily be
obvious why it is hung (serial port, which typically hangs off
Xbus, not configured properly).
Note that even if no EISA options are installed, ECU must be run at
some point (typically, in Manufacturing).
There are some twists, however. For instance, AlphaBIOS, upon seeing a
blank ECU data region in the ESC NVRAM part, will initialize said
region with NT-specific ECU data (assuming an empty EISA bus). Another
example is that the AlphaServer 4000/4100 SRM console will hard-code
UNIX/VMS ECU data in the HWRPB data structure passed to UNIX/VMS during
booting if it finds an empty ECU data region. [Note that SRM will not
auto-update the data region, however, and it will warn the user during
power-up that ECU should be run when it finds a lack of valid ECU data
in the NVRAM part.]
|
| 212.10 | 4.0c is for PWSau | BBPBV1::WALLACE | PC: mega$ fashion accessories | Wed Jun 04 1997 06:00 | 2 |
| I think 4.0c does exist, but it's solely for PWSau support. Or so I was
told.
|
| 212.11 | Probably was V.0C media | WIBBIN::NOYCE | Pulling weeds, pickin' stones | Wed Jun 04 1997 08:54 | 11 |
| .8> Also some confusion arose from the fact that the distribution CD was
.8> labeled v4.0C, which doesn't exist yet. System banner says 4.0B as it
.8> should.
.10> I think 4.0c does exist, but it's solely for PWSau support.
Right. And if you install using the V4.0C media on anything else, it
installs V4.0B instead.
Part of the confusion is that the release code named "PTmin", which is about
to enter field test, was once expected to be called V4.0C.
|