* Original message posted in: MUFFIN.
* Crossposted in: OS2, COMP-OS2-MISC.
Hello Vince.
ML> Something peculiar showing up in the available memory display:
ML> =-=-=-=-=-=-=-=-=-CUT-=-=-=-=-=-=-=-=-=-=-
[READOUT from BBS program "Maximus/2" v3.01's
"Version" menu command]
ML> Version: Compiled on Dec 29 1998 at 16:34:45 (WATCOM C/32 v10.60)
ML> Computer: AT-class, revision 2
ML> OS: OS/2 Version 4.52 (Conv.Pack 2, FP3)
ML> Memory: -2,116,820,992 bytes remain in heap
ML> =-=-=-=-=-=-=-=-=-CUT-=-=-=-=-=-=-=-=-=-=-
ML> What's happened here? I don't ever recall seeing a
ML> negative figure here before. Ideas?
VC> This relates to the limitations of the version (& fixpak
VC> level) of your copy of OS/2 that fixes limits to 2gb / 4gb
VC> (can't remember what one). I would suggest if it is
VC> important, i.e., you are also having problems with larger
VC> HDD etc, that you, 1. Backup your system then, 2. Update to
VC> the latest fixpak (15/16) for Warp v4 etc. If you are not
VC> using Warp v3 or v4, check what fixpaks are available and
VC> see what ones fix the HDD limitations on size.
I'm already at 4.52 (Conv. Pack 2) Fix Pak 3. As I said, this
is a recent development. It's always been a positive integer
prior to this. I'm also seeing problems with *DOS* programs
(e.g. PCopy) occasionally saying "insufficient disk space" and
asking to be redirected to a different disk. I tried
"V2GB.SYS", but that breaks 4DOS and Binkely v2.60DOS (I run
only 1 node under DOS (the "send" node) due to the complexity of
its batch file and no OS/2 equals to some of the programs that
the batch uses. The other 4 nodes run BTXE for OS/2... No
problems there.) I'm really puzzled.
Oh and BTW, I ran SpaceHog on the Maximus drive (c:) and it made
no difference in the figure. I'm at wits end on this one. The
BBS still works, but I've got a sneaky suspicion that something
is going wrong "under the hood".
Best regards,
Marc
P.S: I'm copying this message over to the OS/2 echo and one of
the OS/2 newsgroups.
--- timEd/386 1.10.y2k+
* Origin: Sursum Corda! BBS SysOp Point (1:396/45.1)
SEEN-BY: 633/267 270
@PATH: 396/45 106/2000 633/267
|