| Title: | laser |
| Moderator: | PROXY::ALLEN |
| Created: | Thu Jul 16 1992 |
| Last Modified: | Wed May 28 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1267 |
| Total number of notes: | 4891 |
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 552.1 | FCO current schedule | TKTVFS::YAMAGUCHI_KA | Kazumi Yamaguchi,TSSG/CSC/Japan | Fri Mar 18 1994 00:03 | 9 |
| 552.2 | Any further status ?? | GLDOA::SISSOM | Fri Jun 24 1994 16:01 | 9 | |
| 552.3 | ELMAGO::JREDDING | Fri Jun 24 1994 16:04 | 10 | ||
| 552.4 | FCO No. is "KN7AA-O001" | TKTVFS::YAMAGUCHI_KA | Kazumi Yamaguchi,TSSG/CSC/Japan | Mon Jun 27 1994 00:07 | 64 |
| 552.5 | We FCO only if you pay more doe? | SUBSYS::DUVAL | Mon Mar 24 1997 19:04 | 20 | |
Hi,
We have a DEC7630 with 512mb memory. We bought a 128mb memory board
to upgrade to 640mb. The other 2 nodes in the cluster were upgraded
to 640mb from 512mb with no problem. When the system boots after my
MCSperson puts the 128 board in, we get "Invalid memory interleaving
- boot disallowed" just as described in .4 . MCS says our contract
does not allow for this FCO to be applied now, if we wanted to add
memory back in 94 and we ran into this then it would? Is this true?
So MCS is saying we must pay for new CPUs or whatever needs to be done
to make them work with the new memory. Customers must love to hear an
answer like that, no wonder ............
The FCO in .4 says "all DEC 7xxx" should get the FCO, but our system
existed then and did not obviously. What does the "O" code mean in
an FCO?
| |||||
| 552.6 | O=Produce Operation | WRKSYS::DENNING | Mon Mar 31 1997 19:30 | 3 | |
O - Means Product Operation.
Don
| |||||