T.R | Title | User | Personal Name | Date | Lines |
---|
1795.1 | | BSYBEE::EGOLF | John C. Egolf LKG2-2/T02 x226-7874 | Mon Nov 11 1991 20:50 | 8 |
| Rick,
16M *is* enough memory for a small configuration and your
configuration is small. I'll see if anybody has any ideas. In
the meantime, do you have a mcc_resource.dat file? If you do,
rename it to something else and see if it makes any difference?
JCE
|
1795.2 | More than 20MB | MLNEDU::GIAMMARINI | Roma Caput Mundi | Tue Nov 12 1991 07:07 | 12 |
| John,
I'm not sure 16MB is enough. 20MB memory is not enough too. I led
just last week the Network Management Using DECmcc course, and the
stations with 20MB (two) had a lot of problems with a small
configuration (4 stations and one bridge). A couple of times, only
with three Alarms Rules active, one background process for the
Historian and another for the Exporter, the DECmcc windows
disappeared and the process dead. (DNA V1.1 & BMS V1.1)
Regards
Dom
|
1795.3 | | BSYBEE::EGOLF | John C. Egolf LKG2-2/T02 x226-7874 | Tue Nov 12 1991 08:16 | 10 |
| Dom,
If you have a workstation (3100) that is running just DECmcc,
trust me, 16meg is a good starting place. You can never have
enough memory. The more you have the faster DECmcc will run.
Most of our deveoplment systems have 16M. Our standard demo
system has 16M. Your system either was running other memory
intensive programs or it wasn't tuned right.
JCE
|
1795.4 | I trust you | MLNEDU::GIAMMARINI | Roma Caput Mundi | Tue Nov 12 1991 08:57 | 10 |
|
John,
I trust you of course. I only explained my experience. My VAXstations
3100 have only DNS and DECmcc running, are configurated as written in
the course student guide (written by the big Bill Wade) and as written
in the guidelines contained inside the DECmcc Fullinstall document.
Regards
Dom
|
1795.5 | That Worked!! | ODIXIE::PEACOCKR | | Tue Nov 12 1991 09:54 | 10 |
| John,
Thanks!! That appears to have solved the problem. Just for future
reference, how did this happen? Was it because some of the MCC Sysgen
parameters were not right and when it ran into a problem it
"remembered" via the MCC_RESOURCE.DAT file?
(This looks like a pretty "sensitive" product)
Rick
|
1795.6 | | BSYBEE::EGOLF | John C. Egolf LKG2-2/T02 x226-7874 | Tue Nov 12 1991 11:40 | 13 |
| re .5
The sysgen parameters changing should not have anything to do
with the mcc_resource.dat file.
I can only assume that something in the file (mcc_resource.dat)
is corrupted and the Iconic Map PM is trying to do something it
shouldn't.
Mail me the file (its just an ascii file) and we'll try to see
what the problem is.
JCE
|