Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Insufficient Memory in Windows Server 2000
Message
De
06/09/2002 11:05:41
 
 
À
23/07/2002 23:02:43
Information générale
Forum:
Visual FoxPro
Catégorie:
FoxPro 2.x
Divers
Thread ID:
00681492
Message ID:
00697546
Vues:
19
>>My client is running a FPW2.6 app on a Windows 2000 Server using Citrix. There are other servers using WIN NT4 and Citrix running the same app. These have no problems.
>>
>>On the Win 2000 server, after a while, we get an error messagebox from Windows 2000 - "Insufficient Memory" and the NTVDM shuts down. This error is at system level so FPW26 error trapping does not come in.
>>
>>The worst part is that after this happening on one remote computer's sessions, ALL the other sessions running on that server are corrupt and come up with weird errors and have to be shut down as well. What this means is that the corruption in one NTVDM is affecting other sessions on that server.
>>
>>Setting the CONFIG.FPW file to
>>
>>MEMLIMIT=70,8096,20000
>>
>>seems to reduce the frequency of the problem, but the problem still persists.
>>
>>Does anyone know of or has heard of this problem? Any Fix?
>
>Just a SWAG, but try keeping max memory to 16000 or less:
MEMLIMIT=70,8096,16000
>

Al,

I've seen situations with some video cards that required the cut to be below 16000 for the third parameter; in theory, it could be as high as 17600 if your video card allows you to use the lower 32K of the video memory address space. The specifics change when EMS is used for the NTVDM; it's almost always better to use 2.6 Extended Edition with DPMI with WTS.

>Also, if it's being started by a shortcut on the user's desktop, set the memory settings to be 16MB max of either DPMI or XMS memory, and NO EMS.
>

You don't have to start the app with a shortcut to adjust the memory settings; right-click on a DOS or Win16 executable and select properties, and you can create a .PIF that will be fired in preference to the executable even by command line or explorer clicking; a .PIF will be selected in preference to a default executable extension (.EXE, .BAT, .COM and .CMD at least) if the file extension is omitted from the command line, or if the file is click-opened.

>Also do a search here on Citrix, there are lots of threads with info on patches/settings etc. that may help.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform