SYNFUL@DRYCAS.CLUB.CC.CMU.EDU (Marc Shannon) (08/15/86)
Hmmm...Since my last mail appears to have gotten eaten by the nasty mailers, I'll try again (crossing my fingers!). Anyway, I've got a uVAX-I with a QVSS, DEQNA, and originally 2 1Mb memory boards running uVMS V4.3 with (of course) 2Mb. Now I have a third memory board (also 1Mb), but I cannot convince the uVAX to find it. It always comes up 2Mb. The DIP switches are set as follows: 1st Board 1 1 1 1 1 1 1 1 1 0 0 1 2nd Board 1 1 1 0 0 0 1 1 1 1 0 0 3rd Board 1 1 1 1 0 0 1 1 1 0 1 0 (new one) If anybody has insight into these switches, or even perhaps documentation, please let me know and make my users happy! --Marc Shannon CMU Computer Club Hacker Synful%Drycas@TE.CC.CMU.EDU
carl@CitHex.Caltech.Edu (Carl J Lydick) (08/17/86)
> Anyway, I've got a uVAX-I with a QVSS, DEQNA, and originally 2 1Mb > memory boards running uVMS V4.3 with (of course) 2Mb. > > Now I have a third memory board (also 1Mb), but I cannot convince > the uVAX to find it. It always comes up 2Mb. What you're describing is not be a hardware problem at all. I'd give you ten-to-one odds that if you check, you'll find the sysgen parameter PHYSICALPAGES set to 4000. Set it to 6000 (on most systems it's set to the maximum value allowed, just to prevent the confusion you've experienced). However, the QVSS software uses the sysgen parameter rather than the boot-time memory check to decide how much memory there is available for it. And it uses it, whether it's there or not, resulting in a MTBF for the system of about the length of time it takes for somebody to push the button on the mouse. Also, you'd better reinstall VWS as soon as you reset that parameter, unless you want to restrict yourself to about 3 windows (including menus) before the system crashes. Last time I added memory to the VAXStation II here, it took about 5 tries at reinstalling the VWS package before the system stayed up long enough for it to finish. I could've kicked myself when I finally (after the first 4 tries) thought of shutting down the QVSS system and logging in on CSA0: (the LA34 emulation window that lets all the important traceback information scroll off the screen before you can get a good look at it when the system crashes). Good luck.