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: ProFox@leafe.com
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/51DAD711.5020609@cullytechnologies.com
** 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.
On Mon, Jul 8, 2013, at 04:13 PM, Kevin Cully wrote:
> 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.
>
> Any tips from the Foxpro DOS pros? Is it time to get them into some
> sort of VM?
You could try a VM but running what? Unless you want to source MS-DOS
6.22 or Windows 3.11?
> Perhaps DOSBox?
DosBOX will certainly run FPD, but I would have concerns over printing,
and if it's a networked application then forget it as DosBOX doesn't
have any TCP/IP stack support.
>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.
The usual MEMLIMIT settings will apply in CONFIG.FP
_______________________________________________
Post Messages to: ProFox@leafe.com
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/1373297024.26230.140661253181090.1AB1F996@webmail.messagingengine.com
** 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.
I found this
http://support.microsoft.com/kb/114465
and
http://www.daniweb.com/hardware-and-software/microsoft-windows/windows-nt-20
00-xp/threads/10761/problem-trying-to-run-old-fortran-based-program-in-win-x
p
Not sure if it's the answer
Al
-----Original Message-----
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"
_______________________________________________
Post Messages to: ProFox@leafe.com
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/022a01ce7bef$f2d57a40$d8806ec0$@com
** 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.
What product was produced by using the Lahey Fortran compiler?
________________________________
From: Kevin Cully <kcully@cullytechnologies.com>
To: profoxtech@leafe.com
Sent: Monday, July 8, 2013 11:13 AM
Subject: [FPD] Abnormal program termination
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: ProFox@leafe.com
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/51DAD711.5020609@cullytechnologies.com
** 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.
_______________________________________________
Post Messages to: ProFox@leafe.com
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/1373298694.49690.YahooMailNeo@web122306.mail.ne1.yahoo.com
** 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.
On 8 July 2013 16:13, Kevin Cully <kcully@cullytechnologies.com> wrote:
> 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"
It could still be a corrupt index.
--
Paul
_______________________________________________
Post Messages to: ProFox@leafe.com
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/CADwx0++GZBkPH_Ce9Uc2KqVFbOaSDALxCCKc2yBM3ipngxU7nQ@mail.gmail.com
** 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.
Very true in that when this report is run as one person: no problem.
When run as another: problem.
I think I need to roll up my sleeves and try to track down which program
is being run, and see if I can determine what is going on. I didn't
write this thing, so it is a mystery to me.
On 07/08/2013 12:24 PM, Paul Hill wrote:
> On 8 July 2013 16:13, Kevin Cully <kcully@cullytechnologies.com> wrote:
>> 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"
> It could still be a corrupt index.
>
_______________________________________________
Post Messages to: ProFox@leafe.com
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/51DAE867.7090305@cullytechnologies.com
** 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.
No clue, but I don't believe that it was Foxpro for DOS.
On 07/08/2013 11:51 AM, Michael Madigan wrote:
> What product was produced by using the Lahey Fortran compiler?
>
_______________________________________________
Post Messages to: ProFox@leafe.com
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/51DAE893.70801@cullytechnologies.com
** 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.
I'll definitely try out the CONFIG.FP. I would be quite pleased if this
was a simple, magic bullet. I'll let you know one way or the other.
On 07/08/2013 11:23 AM, Alan Bourke wrote:
> The usual MEMLIMIT settings will apply in CONFIG.FP
_______________________________________________
Post Messages to: ProFox@leafe.com
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/51DAE8D5.9020408@cullytechnologies.com
** 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.
Author: Christof Wollenhaupt
Posted: 2013-07-08 12:02:25 Link
Hi Kevin,
Sudden program terminations have for us all been data or hardware
related... It's usually a corrupt index or memo file. On the hardware side
it's mostly a thermal issue.
I've last tried DOSbox a few months ago. We have a performance test in our
application that does a number of typical FoxPro operations, mainly a
combination of performing calculations and SEEK operations. DOSbox was over
100 times slower than a Windows XP machine both running on the same host
computer.
--
Christof
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
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/CAL4QJhg297bKvnJq5HYWZ6sA4w9vV=k6Hh3xtTkwTDa7rtcNPg@mail.gmail.com
** 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.
At 08:23 2013-07-08, Alan Bourke <alanpbourke@fastmail.fm> wrote:
>On Mon, Jul 8, 2013, at 04:13 PM, Kevin Cully wrote:
> > 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.
> >
> > Any tips from the Foxpro DOS pros? Is it time to get them into some
> > sort of VM?
>
>You could try a VM but running what? Unless you want to source MS-DOS
>6.22 or Windows 3.11?
>
> > Perhaps DOSBox?
>
>DosBOX will certainly run FPD, but I would have concerns over printing,
>and if it's a networked application then forget it as DosBOX doesn't
>have any TCP/IP stack support.
Vanilla DOSBox does not have printing, but there is a version
that does. TCP/IP is being done somehow by some gamers.
More importantly, DOSBox is intended for games. The authors
have made that abundantly plain over the years. Until recently, I
used it for years to run WordStar and had no problems -- I then found
VDE and have not had to use DOSBox for months now -- but do not count
on any support.
DOSBox is somewhat slow. This did not show up with using
WordStar, but I have some 16-bit utilities that I wrote and running
on faster hardware but under Windows 7 and DOSBox, one program took
15 times longer to run than under native XP.
[snip]
Sincerely,
Gene Wirchenko
_______________________________________________
Post Messages to: ProFox@leafe.com
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/
** 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.