Hello,

Os : Windows 7 06.01 Build 07600
Computername : SALON (3038Mb) 
Xbase 1.9-355 Hotfix 1..36 installed.
Now and then receives the fatal error as below:

Suggestions are welcome.
Regards,
Jack Duijf



FATAL ERROR LOG 
System-Error
SYS Thread-ID: 640 
Module: MOM
Error Codes: EH: 4 Sub: 1455(5af) OS: 1455 XPP: 40
Call Stack of Thread 1 (640):
XBPSTATIC(422)
DC_XBPSTATICSUPER(22)
DC_XBPSTATIC(136)
@DC_GETLIST@I@READGUI(1831)
DC_READGUI(103)
DC_WAITON(603)
SY_DC_WAITON(4)
SALONNET(1059)
MAIN(33)
Call Stack of GUI Threa d (836):
File: C:\Program Files (x86)\SalonNet\SalonNet.EXE
TimeStamp: 20101011 08:23
End of FATAL ERROR LOG.

Jack,

>Now and then receives the fatal error as below:

>SYS Thread-ID: 640 
>Module: MOM
>Error Codes: EH: 4 Sub: 1455(5af) OS: 1455 XPP: 40
>Call Stack of Thread 1 (640):
>XBPSTATIC(422)

I can't tell why you would get that error (at least not why you would 
get it at that point in your program), but the general cause is quite 
obvious:

>Error Codes: EH: 4
This means Xbase++ Sub-system Error Code: 4, which means an OS Error.

>Sub: 1455(5af)
This means OS Error Code: 1455 (or 0x5AF), which is: 
"The paging file is too small for this operation to complete."

>OS: 1455
Same as above.

>XPP: 40
This means Xbase++ General Error Code: 40, which (also) means OS Error.

I would try to increase the size of your paging file -- and make it at 
least the same size as the installed RAM or 3 GB, which ever is less --
so that the OS can swap some memory out, when needed. 

But because Xbase++ can use at the most about 800 MB of RAM (in addition
to the memory used by the OS, Xbase++ runtime and your executables), you
should very seldom see that kind of error, at least when the OS default 
settings for virtual memory (or the PageFile size) are used.

Andreas

Andreas Gehrs-Pahl
Absolute Software, LLC

phone: (989) 723-9927
email: Andreas.GP@Charter.net
       Andreas_Gehrs-Pahl@EJusticeSolutions.com
       Andreas@DDPSoftware.com
web:   http://www.Aerospace-History.net

Hello Andreas,

Thanks for the explanation.
I am just puzzeled how to comunicate this to the customer (a absolute 
end-user with just enough experience to manage my programm).
I am wondering if i can see this comming.
Now my app shows a warning at startup if there is less then 512Mb installed, 
or it runs almost out of diskspace.
It would be nice to inform the end-user to increase the paging file (and 
instruction show to dom that) before the app crashes.

Suggestions are welcome.

Regards,
Jack Duijf


"Andreas Gehrs-Pahl" schreef in bericht 
news:1as5buxrmszxm.twxxcecm0hs8$.dlg@40tude.net...
> Jack,
>
>>Now and then receives the fatal error as below:
>
>>SYS Thread-ID: 640
>>Module: MOM
>>Error Codes: EH: 4 Sub: 1455(5af) OS: 1455 XPP: 40
>>Call Stack of Thread 1 (640):
>>XBPSTATIC(422)
>
> I can't tell why you would get that error (at least not why you would
> get it at that point in your program), but the general cause is quite
> obvious:
>
>>Error Codes: EH: 4
> This means Xbase++ Sub-system Error Code: 4, which means an OS Error.
>
>>Sub: 1455(5af)
> This means OS Error Code: 1455 (or 0x5AF), which is:
> "The paging file is too small for this operation to complete."
>
>>OS: 1455
> Same as above.
>
>>XPP: 40
> This means Xbase++ General Error Code: 40, which (also) means OS Error.
>
> I would try to increase the size of your paging file -- and make it at
> least the same size as the installed RAM or 3 GB, which ever is less --
> so that the OS can swap some memory out, when needed.
>
> But because Xbase++ can use at the most about 800 MB of RAM (in addition
> to the memory used by the OS, Xbase++ runtime and your executables), you
> should very seldom see that kind of error, at least when the OS default
> settings for virtual memory (or the PageFile size) are used.
>
> Andreas
> -- 
> Andreas Gehrs-Pahl
> Absolute Software, LLC
>
> phone: (989) 723-9927
> email: Andreas.GP@Charter.net
>       Andreas_Gehrs-Pahl@EJusticeSolutions.com
>       Andreas@DDPSoftware.com
> web:   http://www.Aerospace-History.net

If they are hitting swap they have far too many processes running. Tell
them to close some Windows some times. Something is consuming memory and
most likely a browser and or email client is left running and god knows
what else. Tell them they need to go on a program diet and not have so
many running at one time.

Jim




On 10/16/2010 10:23 AM, Jack Duijf wrote:
> Hello Andreas,
> 
> Thanks for the explanation.
> I am just puzzeled how to comunicate this to the customer (a absolute
> end-user with just enough experience to manage my programm).
> I am wondering if i can see this comming.
> Now my app shows a warning at startup if there is less then 512Mb
> installed, or it runs almost out of diskspace.
> It would be nice to inform the end-user to increase the paging file (and
> instruction show to dom that) before the app crashes.
> 
> Suggestions are welcome.
> 
> Regards,
> Jack Duijf
> 
> 
> "Andreas Gehrs-Pahl" schreef in bericht
> news:1as5buxrmszxm.twxxcecm0hs8$.dlg@40tude.net...
>> Jack,
>>
>>> Now and then receives the fatal error as below:
>>
>>> SYS Thread-ID: 640
>>> Module: MOM
>>> Error Codes: EH: 4 Sub: 1455(5af) OS: 1455 XPP: 40
>>> Call Stack of Thread 1 (640):
>>> XBPSTATIC(422)
>>
>> I can't tell why you would get that error (at least not why you would
>> get it at that point in your program), but the general cause is quite
>> obvious:
>>
>>> Error Codes: EH: 4
>> This means Xbase++ Sub-system Error Code: 4, which means an OS Error.
>>
>>> Sub: 1455(5af)
>> This means OS Error Code: 1455 (or 0x5AF), which is:
>> "The paging file is too small for this operation to complete."
>>
>>> OS: 1455
>> Same as above.
>>
>>> XPP: 40
>> This means Xbase++ General Error Code: 40, which (also) means OS Error.
>>
>> I would try to increase the size of your paging file -- and make it at
>> least the same size as the installed RAM or 3 GB, which ever is less --
>> so that the OS can swap some memory out, when needed.
>>
>> But because Xbase++ can use at the most about 800 MB of RAM (in addition
>> to the memory used by the OS, Xbase++ runtime and your executables), you
>> should very seldom see that kind of error, at least when the OS default
>> settings for virtual memory (or the PageFile size) are used.
>>
>> Andreas
>> -- 
>> Andreas Gehrs-Pahl
>> Absolute Software, LLC
>>
>> phone: (989) 723-9927
>> email: Andreas.GP@Charter.net
>>       Andreas_Gehrs-Pahl@EJusticeSolutions.com
>>       Andreas@DDPSoftware.com
>> web:   http://www.Aerospace-History.net 
>

Hello Jack,
take a look at GlobalMemoryStatus and GlobalMemoryStatusEx in MSDN.
Best regards,
Michael


<Jack Duijf> wrote in message 
news:4c3478b7$66558134$b60ff@news.alaska-software.com...
> Hello Andreas,
>
> Thanks for the explanation.
> I am just puzzeled how to comunicate this to the customer (a absolute 
> end-user with just enough experience to manage my programm).
> I am wondering if i can see this comming.
> Now my app shows a warning at startup if there is less then 512Mb 
> installed, or it runs almost out of diskspace.
> It would be nice to inform the end-user to increase the paging file (and 
> instruction show to dom that) before the app crashes.
>
> Suggestions are welcome.
>
> Regards,
> Jack Duijf
>
>
> "Andreas Gehrs-Pahl" schreef in bericht 
> news:1as5buxrmszxm.twxxcecm0hs8$.dlg@40tude.net...
>> Jack,
>>
>>>Now and then receives the fatal error as below:
>>
>>>SYS Thread-ID: 640
>>>Module: MOM
>>>Error Codes: EH: 4 Sub: 1455(5af) OS: 1455 XPP: 40
>>>Call Stack of Thread 1 (640):
>>>XBPSTATIC(422)
>>
>> I can't tell why you would get that error (at least not why you would
>> get it at that point in your program), but the general cause is quite
>> obvious:
>>
>>>Error Codes: EH: 4
>> This means Xbase++ Sub-system Error Code: 4, which means an OS Error.
>>
>>>Sub: 1455(5af)
>> This means OS Error Code: 1455 (or 0x5AF), which is:
>> "The paging file is too small for this operation to complete."
>>
>>>OS: 1455
>> Same as above.
>>
>>>XPP: 40
>> This means Xbase++ General Error Code: 40, which (also) means OS Error.
>>
>> I would try to increase the size of your paging file -- and make it at
>> least the same size as the installed RAM or 3 GB, which ever is less --
>> so that the OS can swap some memory out, when needed.
>>
>> But because Xbase++ can use at the most about 800 MB of RAM (in addition
>> to the memory used by the OS, Xbase++ runtime and your executables), you
>> should very seldom see that kind of error, at least when the OS default
>> settings for virtual memory (or the PageFile size) are used.
>>
>> Andreas
>> -- 
>> Andreas Gehrs-Pahl
>> Absolute Software, LLC
>>
>> phone: (989) 723-9927
>> email: Andreas.GP@Charter.net
>>       Andreas_Gehrs-Pahl@EJusticeSolutions.com
>>       Andreas@DDPSoftware.com
>> web:   http://www.Aerospace-History.net
>

Hello Michael,

Thanks for the suggestion.
It's usefull info. I could try to inplement this in my "Monitor thread", and 
give advance warning if the paging files reach 80% of its capacity.

Regards,
Jack Duijf


"Michael Hoffmann" schreef in bericht 
news:37ec4d2$7df576b1$e319@news.alaska-software.com...
> Hello Jack,
> take a look at GlobalMemoryStatus and GlobalMemoryStatusEx in MSDN.
> Best regards,
> Michael
>
>
> <Jack Duijf> wrote in message 
> news:4c3478b7$66558134$b60ff@news.alaska-software.com...
>> Hello Andreas,
>>
>> Thanks for the explanation.
>> I am just puzzeled how to comunicate this to the customer (a absolute 
>> end-user with just enough experience to manage my programm).
>> I am wondering if i can see this comming.
>> Now my app shows a warning at startup if there is less then 512Mb 
>> installed, or it runs almost out of diskspace.
>> It would be nice to inform the end-user to increase the paging file (and 
>> instruction show to dom that) before the app crashes.
>>
>> Suggestions are welcome.
>>
>> Regards,
>> Jack Duijf
>>
>>
>> "Andreas Gehrs-Pahl" schreef in bericht 
>> news:1as5buxrmszxm.twxxcecm0hs8$.dlg@40tude.net...
>>> Jack,
>>>
>>>>Now and then receives the fatal error as below:
>>>
>>>>SYS Thread-ID: 640
>>>>Module: MOM
>>>>Error Codes: EH: 4 Sub: 1455(5af) OS: 1455 XPP: 40
>>>>Call Stack of Thread 1 (640):
>>>>XBPSTATIC(422)
>>>
>>> I can't tell why you would get that error (at least not why you would
>>> get it at that point in your program), but the general cause is quite
>>> obvious:
>>>
>>>>Error Codes: EH: 4
>>> This means Xbase++ Sub-system Error Code: 4, which means an OS Error.
>>>
>>>>Sub: 1455(5af)
>>> This means OS Error Code: 1455 (or 0x5AF), which is:
>>> "The paging file is too small for this operation to complete."
>>>
>>>>OS: 1455
>>> Same as above.
>>>
>>>>XPP: 40
>>> This means Xbase++ General Error Code: 40, which (also) means OS Error.
>>>
>>> I would try to increase the size of your paging file -- and make it at
>>> least the same size as the installed RAM or 3 GB, which ever is less --
>>> so that the OS can swap some memory out, when needed.
>>>
>>> But because Xbase++ can use at the most about 800 MB of RAM (in addition
>>> to the memory used by the OS, Xbase++ runtime and your executables), you
>>> should very seldom see that kind of error, at least when the OS default
>>> settings for virtual memory (or the PageFile size) are used.
>>>
>>> Andreas
>>> -- 
>>> Andreas Gehrs-Pahl
>>> Absolute Software, LLC
>>>
>>> phone: (989) 723-9927
>>> email: Andreas.GP@Charter.net
>>>       Andreas_Gehrs-Pahl@EJusticeSolutions.com
>>>       Andreas@DDPSoftware.com
>>> web:   http://www.Aerospace-History.net
>>
>
>

That was the idea.
Best regards,
Michael