Rainer Zocholl wrote:

> (Frank Mabrey) 07.11.03 in /comp/unix/sco/misc:
>
> >I am building a server that has 4 gig of RAM using OpenServer 5.0.5.
> >The large amount of RAM is for I/O buffers for a DBMS.
>
> >I built a 6 gig swap area, thinking a smaller swap area might be
> >limiting how much ram the OS can see.
>
> >I boot with mem=1m-16m,16m-4092m/n/p to force OS to see all the RAM.
> >The message shows all the RAM is found.
>
> >Still the boot up messages tell me I have a
> >"mem: total = 787388k" with
> >"kernel = 18384k, user = 769004k"
>
> >Have I run into some kind of undocumented limit?
>
> Yepp.
>
> Long time ago there were patches to fix this rediculous/surprising limit
> (for a (once) hi-end OS).
> But SCO decided to withdraw them, stating that they (the patches)
> cause problems...

The patches were for OpenServer 5.0.0 and 5.0.2 only, and they _did_
cause problems, they weren't anywhere near as stable as 5.0.4. Starting
with OSR504 (shipped in mid-1997) OpenServer supports a full 4GB. (The
patches for 500/502 only supported 2GB). Why are you upset that you can
no longer get poorly functional patches for OSes that were superseded 6
1/2 years ago?

> To get arround it you have to upgrade to at least 5.0.6 AFAIK.

5.0.4. The original poster hasn't responded to my questioning his
version number, which should not be 5.0.5 if he's topping out at 768MB.

> But you stay fixed at a 2GB file size limit...

True.

> Maybe you like to have a look at "A.B.I." (see Tony's webpages)
> and can host you application under linux?
>
> Maybe it would be less "expensive" to migrade to Linux and Postgresql?
> And: What do think will happen to SCO next year?
> I remember very good that they once stopped development on
> OSR5 some time ago and resumed it with 5.0.7 mainly to introduce
> a new paying model...

OpenServer development has not stopped at any time in the last 10 years.
The company has had different ambitions for the OS and different numbers
of people working on it, but never stopped. Right now, development is
ramping up as we prepare to deliver the features promised at SCO Forum
2003.

>Bela<