[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | "ASK THE WIZARDS" |
|
| Moderator: | QUARK::LIONEL |
|
| Created: | Mon Oct 30 1995 |
| Last Modified: | Mon May 12 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1857 |
| Total number of notes: | 3728 |
1632.0. "Closed: why am I getting this memory message?" by STAR::JKEENAN () Mon Feb 24 1997 15:42
Return-Path: "VMS001::WWW"@vms001.das-x.dec.com
Received: by vmsmkt.zko.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX);
Mon, 24 Feb 1997 15:23:13 -0500
Received: from vms001 by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV)
id PAA31845; Mon, 24 Feb 1997 15:11:05 -0500 (EST)
Date: Mon, 24 Feb 1997 15:11:56 -0500
Message-Id: <[email protected]>
From: "VMS001::WWW"@vms001.das-x.dec.com (24-Feb-1997 1512)
To: [email protected], [email protected], [email protected]
Subject: Ask the Wizard: '[email protected]'
X-VMS-To: [email protected]
Remote Host: (null)
Browser Type: Mozilla/0.9 Beta (Windows)
Remote Info: <null>
Name: Andreas Sorenby
Email Address: [email protected]
CPU Architecture: VAX
Version: v 6.2
Questions:
Hello, My name is Andreas and I'm from Sweden.
My question is:
At work we have a VAXstation 3100 loaded with 72 Mb
memory. This is shown when we starts the machine.
When we start VMS and use the VMS-command SHOW MEMORY
we are told that there are only 32 Mb memory in our
VAXstation.How is this possible?
What can we do use all the memory?
I would be very happy if you could give me some answers.
Have a nice day,
Andreas
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1632.1 | | QUARK::LIONEL | Free advice is worth every cent | Mon Feb 24 1997 16:21 | 13 |
| You asked:
> At work we have a VAXstation 3100 loaded with 72 Mb
>memory. This is shown when we starts the machine.
>When we start VMS and use the VMS-command SHOW MEMORY
>we are told that there are only 32 Mb memory in our
>VAXstation.How is this possible?
>What can we do use all the memory?
This is usually due to the SYSGEN parameter PHYSICALPAGES not having been reset
when more memory was added. To fix this, do a:
$ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT
|