NTVDM problem with XP-FPD26

[tilltek]

Running Microsoft Foxpro 2.6 for dos in XP has worked for me for over 12 months but I'm now getting the following...
The NTVDM CPU has encountered an illegal instruction.
C5:8ae0 IP:0074 OP:c4 ff ec 72 00 Choose 'Close' to terminate the application.
|Close||Ignore|
Any ideas what this might be?
My virus checker is up to date.
Ken F

 

[rob444]

What has changed in the XP configuration?
NTVDM = NT Virtual Device Manager.
Look for changes you made just before foxpro started acting like this.

Rob.

 

[tilltek]

Thanks Rob, but I don't think I have changed anything.
A few further details for you.
I have over 150 near identical FPD26 apps out in the field. They run 486 up with WFWG to XP. All have (my) identical code.
A user phoned me yesterday with a similar problem to the one above.

One of my fxp modules allows a store to enter stock into my POS system.
This store, on entering the product code "BWT02", were faced with a restart. That is, the computer (Win98) did a Ctrl, Alt, Del as soon as they pressed Enter.
Entering "BWT01, BWT03 or in fact any other code worked fine.
I went over to the store and put in a "wait window "" timeout .2" before, during and after the bit of code that searched for "BWT02" and that fixed it.

What the.........

 

[rob444]

I understand.

I do not think that this is a Foxpro error of some kind.

Check if the settings of the application are identical to your "standard settings" of the application in the specific windows environment.

I mean the proporties of the application you run by clicking on a icon on the desktop.

Rob.

 

[tesar]

Tilltek,
NT Virtual Dos Machine with very fast computers do problems.
(Although i have NT, 2GHz and FoxPro 2.0, similarly...)
For example I forced replace simpler
"copy TO g:\myfile.dbf"
with
"copy to d:\myfile.dbf
use
flush
copy FILE d:\myfile.dbf to g:\myfile.dbf"
Although function is same, first failed, second is good.
Similarly print, i must print to local .txt file into spool
(thanks Ramani for your tip and Peter Lerup for PrintFile !)
Tesar

 

[tilltek]

Thanks Tesar. While the NTVDM problem is on a 1200 AMD, the "shutdown" problem is on a 486 which has worked for three years so I dont think CPU speed is the problem.
There might be some sort of memory problem.
But why on entering one code only?
I have checked and re-built indexes.
I plan to try "tame.exe" but any other suggestions would be appreciated.
Ken F

 

[4954]

hi all,

i want to share some experience in xp/2k envirement .

1: files setting and VM setting

-> winnt\system32\config.nt / autoexec.nt

2: lack of memory / higher cpu utliztion

DOs program running on 2k/xp platform would face
this situation. it caused by o/s listen to the NTVM
keyboard response.

some utility could adjust their listening frequence
to lower down the cpu.

keybd.exe from citrix.com (search the knowledge base)
-> this one help me to run fox apps on
terminal server for more than 100 users.

whatever p4/p3 cpu.

 

[tilltek]

Fournine Fivefour, I'll look into it. I'm trialing Tame and so far so good.
Ken F

 

[DSummZZZ]

tilltek,

Did you just reindex the tables or recreate the indexes from scratch? Many times REINDEX doesn't cure the corruption. Make sure you delete the .CDXs and rebuild them to rule that scenario out.
Also, make sure you get rid of all .TMP files and do a SCANDISK/DEFRAG.


Dave S.