I've got a client that has been running a Foxpro DOS application for
years and years, they're happy with it and they aren't going to change
or rewrite it. This client calls me about once a year when an index
goes off the rails. 30 minutes to get the file from the previous
night's backup, test and call it done for another year.
They just called me up with a new error. They're trying to print a
report and they're getting the message:
"Abnormal program termination: Stack Fault
CS: EIP = 000Fh: 000BF561h"
I've found this MicroSoft KB article:
http://support.microsoft.com/kb/843484 in regards to this message.
Yes, they run Windows XP for the most part, so that security update
seems to have done in some of their users, in some scenarios.
Any tips from the Foxpro DOS pros? Is it time to get them into some
sort of VM? Perhaps DOSBox? I haven't really started to dig into this
area of the program to see if I can determine which line of the code is
actually causing the problem. I thought I'd ask here to see if there is
some sort of memory allocation setting I can do at the startup of the
application.
TIA,
Kevin
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
