|
Post by foxpropgmr on Oct 15, 2019 21:42:21 GMT 1
ok .... now that I'm buying licenses, you have to redouble your efforts on those Page Faults. lol
|
|
|
Post by Jos on Oct 15, 2019 22:12:46 GMT 1
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.
Jos
|
|
|
Post by foxpropgmr on Oct 16, 2019 1:51:37 GMT 1
Something's up with the keystroke handler.
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.
Walt
|
|
|
Post by Jos on Oct 16, 2019 7:19:45 GMT 1
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.
Jos
|
|
|
Post by foxpropgmr on Feb 16, 2020 23:27:56 GMT 1
Jos
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.
Walt
|
|
|
Post by Jos on Feb 17, 2020 22:48:56 GMT 1
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.
Jos
|
|
|
Post by foxpropgmr on Feb 18, 2020 6:18:29 GMT 1
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.
Who knew?
Walt
|
|
|
Post by demian on Oct 26, 2020 14:43:31 GMT 1
Hi Jos, we are currently testing vDos on 64b machines with a FoxPro app and we are getting Page Faults. We tried with differents size of sets of records according to the info found here without success.
We are using big DBFs tables with 1 million records or more but we get the same error without using Select statement...
Could you confirm us this error is solved in the registered vDos version? because we need to be sure before ask for the budget.
The version we are testing is from Febrary 2020.03.01.
Thanks
Damian
|
|
|
Post by Jos on Oct 26, 2020 15:36:27 GMT 1
Registered or not, vDos will work the same.
Until now only one reported Page Faults still occur in 2020.03.01. That has meanwhile been fixed, but so seems very specific: FoxProX addresses a virtual memory directory entry that wasn’t initialized by Phar Lap. vDos will then do that himself and use conventional memory for the involved data. I’ll send you the modified vDos.exe, though no real idea if that fixes your Page Fault issue.
Jos
|
|
|
Post by demian on Oct 30, 2020 13:15:56 GMT 1
Hi Jos, did you send me the modified vDos version you mentioned earlier or do I need to buy the registered one first?. Sorry if I didn't understood you. Regards Demian.
|
|
|
Post by Jos on Oct 30, 2020 14:13:08 GMT 1
As said, registration won't do anything towards the workings of vDos.
I sent you (dserp…@gmail.com) last Monday by wetransfer a copy of the modified vDos.exe. A note however: A Page Fault error doesn’t have to reflect a bug in the memory routines of vDos. The program could just pass on an invalid virtual memory address, like it could do a division by zero. Those are just two of the few CPU instructions that can be validated.
Jos
|
|
|
Post by demian on Nov 10, 2020 15:42:05 GMT 1
Hi Jos, I'm sorry to boder you again... I was out/disconnected all these days... Could you send it to me again? because the transfer has expired. Thanks
|
|
|
Post by foxpropgmr on Feb 7, 2021 2:38:34 GMT 1
Jos ....
Just wanted to comment on my recent experiences with vDos. I personally have been using vDos very heavily performing development compiles and testing. vDos is installed on many of my client's machines in production settings. I'm only running Foxprox.exe 2.6 on mostly Windows 10 machines. But vDos has performed perfectly for me and my clients are very happy as well.
Thanks, Jos, for the many many hours you've put into this product.
Walt
|
|
|
Post by chepito on Dec 6, 2022 8:24:15 GMT 1
Here is my very practical observation: The same application run from a folder whose name is 5 characters long and another folder whose name is 8 characters long. In the folder with length 5, many page faults. In the folder with length 8 no error The same application, I just renamed the folder. I repeated the same manifestation many times. I don't understand if this observation has any value, but I tested it and the experience repeats itself
|
|
|
Post by chepito on Dec 6, 2022 8:25:54 GMT 1
vDosPlus 2015.11.01 (build 2017.03.15)
|
|