I would if I could, it already cost me hundreds of hours. Any software developer will require consistent reproducible scenarios. With those FoxProX Page Faults none (except one partially) so far. 99% of these errors should be fixed with the latest release. Mind, although virtual memory paging isn’t that complex, a detected fault with that scheme will mostly just reveal something not directly related already wrong. Millions of instructions before, only exposed due to more extensive checking with memory paging.
The other day I reported a page fault when I hit ALT+F to bring up a small window in a Foxpro app.
Today I was simply using the Foxpro program editor (Modi Comm) and using the arrow keys to move around in the file, and it locked up completely. Needed Task Manager to kill it.
Also ... sometimes when a file is closed and quickly reopened, a "File Access Denied" message appears; almost as if the closing operation takes too long and isn't finished by the time the reopen operation begins. Or maybe it's a delayed file unlock. This happened on a program file edit, close, then reopen. It happenes occasionally on a compile then run of the newly compiled file
No complaints. Just some observations. I love the potential of this product.
Last Edit: Oct 16, 2019 3:15:25 GMT 1 by foxpropgmr
It won’t be related to keystroke handling. FoxPro will become (real) active after that, not just idling in some loop.
Also "File Access Denied" would be a side-effect of something already going wrong. The file will first be opened with extended access rights (exclusively), at closing the file those don’t apply anymore. Like a DOS program, vDos runs fully sequentially. No action/instruction is performed before the previous one is completed.
I’ll have a look at quick opening/closing/reopening, but don’t expect being able to reproduce the "File Access Denied" error.
I did a couple of things. 1) I took some complexity out of some of my queries. And 2) I bought a "driver update" program that updated 18 of the drivers on my development laptop. I've been using this computer heavily since then adding new features to my software and vDos has performed admirably with no page faults.
For anyone still experiencing page faults, I would recommend fully updating their drivers and looking at complex queries if possible.
You could very well be the only one still encountering FoxProX Page Faults. Cleaning up the queries could have made a change. Hard to imagine updating drivers would actually contribute. In Windows (interface/API) perspective vDos is a rather uncomplicated program.
I knew something was up when pressing the touchpad right-mouse caused the pointer to jump around in Excel. Further, pressing and holding the Left-Alt key in Foxprox caused the help screen to pop up in the middle of my DOS program. I noticed that one of the drivers needing an update was the Synaptic driver for the touchpad. So I went for it. Both of the problems listed above disappeared and no page faults after heavy usage.