Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Platinum Memory Problems... 2

Status
Not open for further replies.

keithlages

IS-IT--Management
Feb 7, 2002
35
US
One of my users continues to recieve error messages that Platinum is out of memory or needs to perform maintenance to continue. It's becoming more frequent and I'm not sure what to make of it. Is it something to do with DOS? Should I be loading dos in high memory or something?

' '''''''''''''''''''''''''
' '''''' Specs ''''''''''''
Platinum for Windows 4.7
Windows 2000 Proffesional SP3
1 GHZ P3
256 megs
20 gigs
100 full-duplex
' '''''''''''''''''''''''''

No other users on the system recieve these errors.

Anything I can try?
 
PFW 4.7 is a 16 bit program. The user is running out of memory because every time the user opens a window additional memory is allocated, but not given back to Windows. I would expect that person uses the system alot.

There was a patch (which it seems you have) which told the system after so many screen opens to preform a sort of memory refresh. The setting was in one of the ini files on the local pc (can't remember). It never seemed to me that the memory refresh worked that well.

Solution: Upgrade to version 4.8a, the first completely 32 bit PFW client. If you had maintenance you should have it lying around. Or if you wanted to spend more money you could upgrade to 5.11 (the latest). 5.11 also makes the PAS optional.

Good luck,

CJ

cjkaufman@dayspringenterprises.com
 
Thanks CJ,

I was thinking it was DOS related (16 bit anyway). Yeah this user is the most active with Platinum so iy makes sense.

Thanks for the help!

Keith
 
PFW 4.7 was written in a version of Visual Basic that was found to have a memory leak. When the developers discovered it and asked Microsoft to fix it, they were told to move up to the (then) latest version of VB befor they would fix it. You have a couple of choices -- upgrade to PFW 4.7i which was still using the older version of VB but had some added error-checking that would warn you earlier of a problem; re-boot your workstation on a regular basis (at least twice a day, but perhaps more often if you go in and out of screens often); or upgrade to PFW 4.8a or later which is in the newer version of VB.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top