Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.7.0.8 $; site waltz
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!convex!waltz!haddock
From: haddock@waltz
Newsgroups: net.unix
Subject: Re: Need Help with Ultrix (lack thereof
Message-ID: <56500002@waltz>
Date: Mon, 16-Sep-85 18:33:00 EDT
Article-I.D.: waltz.56500002
Posted: Mon Sep 16 18:33:00 1985
Date-Received: Sun, 29-Sep-85 04:59:38 EDT
References: <169@plx.UUCP>
Lines: 32
Nf-ID: #R:plx.UUCP:-16900:waltz:56500002:000:1329
Nf-From: waltz!haddock    Sep 16 17:33:00 1985


/* Written  4:06 pm  Sep 10, 1985 by plx.UUCP!jk in waltz:net.unix */
/* ---------- "Need Help with Ultrix (lack thereof" ---------- */
I desparately need to talk
with someone that is using Ultrix 32M for the microvax II.
Please call me at (408)252-8713 or send email to 
..!sun!plx!adams who will graciously forward it to me.
thanks in advance,
John Kullmann
AIT
/* End of text from waltz:net.unix */

I can't say that this is the absolute truth but the word that I've
heard is that DEC is suspending shipments of Ultrix for the uVAX II
due to some memory problem that affects low-memory.   As most UNIX
hacks know, this is where the kernal resides.   This will also
affect the uVMesS users as well but the "kernal" for VMesS is in
high-memory while the user's code is in low.  Nicely enough, this is
where the user code gets loaded and DEC figures that this is
acceptable (to have the user code bomb due to h/w problems).

Is this your problem???

================================================================
                           _____
        	        |\/   o \    o
        -Rusty-         |   (  -<  O o     Where's the fish?
                        |/\__V__/

ARPA:   Haddock%TI-CSL.csnet@CSNet-Relay.arpa   or  Rusty@Maryland
CSNet:  Haddock@TI-CSL
USENET: {ut-sally, convex!smu, texsun, rice} ! waltz ! haddock


Brought to you by Super Global Mega Corp .com