|
|
Post by ck1402 on Apr 22, 2024 18:43:55 GMT 1
Hello Everyone,
We have migrated a FoxPro app over to vDOS and i am getting the following issues when users are typing in the program:
noticed is that when we are typing our notes it seems to stutter and delay us. Sometimes when we type it doesn’t register right away and then skips over the letters.
Anyone have these issues? This happens with both wired and wireless keyboards (i figured i would rule that out)
Thank You!
|
|
|
|
Post by Jos on Apr 22, 2024 19:02:24 GMT 1
You’re the first to mention this.
The only issue at this moment would be pasting text. FoxPro then drops characters due to its shadow internal keyboard buffer.
The upcoming release will have a fix, but that doesn’t relate to actually typing text.
Do you first load some TSR program or use an external FoxPro library?
Eventually anyway I can reproduce you issue?
Jos
|
|
|
|
Post by ck1402 on Apr 22, 2024 21:57:12 GMT 1
You’re the first to mention this. The only issue at this moment would be pasting text. FoxPro then drops characters due to its shadow internal keyboard buffer. The upcoming release will have a fix, but that doesn’t relate to actually typing text. Do you first load some TSR program or use an external FoxPro library? Eventually anyway I can reproduce you issue? Jos Is there a way to increase the keyboard buffer for vDos? We have the FoxPro buffer set to 40 and it currently holds about 128 keystrokes Is it possible it's not pulling that buffer over? These systems are running Windows 10 64bit |
|
|
|
Post by Jos on Apr 22, 2024 23:06:03 GMT 1
You could use an utility to increase the keyboard buffer.
But that doesn’t help at all. FoxPro will still move the keypresses from that buffer to that of its own.
When the latter is full, FoxPro continues to remove keypresses from the first, but then drop those.
Even if you would increase the actual buffer to a whopping 100,000 keypresses.
Don’t know how a buffer size of 40 relates to 128 keystrokes. I think the default is 32 (keystrokes).
You would be able to type that amount (32) of characters before FoxPro can attend (respond) to the first character in its buffer.
Just a global estimate: that requires 1,000-2,000 keypresses per second!
Jos
|
|
|
|
Post by ck1402 on Apr 23, 2024 18:25:56 GMT 1
Is there a way to increase the buffer size in vDos?
I tried increasing the overall system buffer and that did not help.
|
|
|
|
Post by Jos on Apr 23, 2024 19:21:38 GMT 1
You could look for a DOS (TSR) utility that implements a new keyboard buffer.
But as said, that won’t do anything since FoxPro will continue to empty the keyboard buffer the moment its shadow keyboard buffer is full.
No matter how large (or small) the actual keyboard buffer is.
Don’t know what the overall system buffer is supposed to be.
What version of vDos do you use?
Eventually start vDos with the log option (….\vDos.exe /log), then the program and submit the generated vDos.log file.
Jos
|
|
|
|
Post by Jos on Apr 28, 2024 22:01:25 GMT 1
If you’re wondering what this was about:
ck1402 ignored all my inquiries for more details to the reported issue.
She/he apparently doesn’t use vDos, but was fishing for a solution to a problem with another DOS emulator, possibly vDosPlus?
Jos
|
|
|
|
Post by ck1402 on Apr 29, 2024 22:25:40 GMT 1
If you’re wondering what this was about: ck1402 ignored all my inquiries for more details to the reported issue. She/he apparently doesn’t use vDos, but was fishing for a solution to a problem with another DOS emulator, possibly vDosPlus? Jos Hello,
This is incorrect and i have been working on getting the information for you. I have not ignored anything at all. I am not the developer who created the foxpro program in question and they have been away.
We ARE using vDOS and the version is: 20.23.5.1 I do not know how to use or program a TSR therefore i could not use that and when the developer of the FoxPro program they use is back i am going to work on further troubleshooting.
So far we have rolled this out on two systems and both of the systems are having the same issue as reported. As i get more information i will update this thread.
|
|
|
|
Post by Jos on Apr 30, 2024 6:20:38 GMT 1
I’m still sceptic: It took you almost a week to partially respond. And so far you would be the only one with this issue…
Jos
|
|
|
|
Post by ck1402 on Apr 30, 2024 12:41:03 GMT 1
I’m still sceptic: It took you almost a week to partially respond. And so far you would be the only one with this issue… Jos Being skeptic is fine. But there are things i am not able to do that you are asking for. So i have to wait till the developer is back to perform those tasks. Regardless if i am the only one reporting the issue. I came here for support. My initial request was to see if there was a way to increase the keyboard buffer in vDOS you replied back with using a third party utility/TSR and never answered with a "yes you can do it this way" or a "No you can't do that" since i do not have the ability to use the resource you suggested i have to wait for the person to return. |
|
|
|
Post by Jos on Apr 30, 2024 13:27:49 GMT 1
Besides my other questions, I told you twice that increasing the actual keyboard buffer size has no effect to FoxPro dropping characters.
If you still want to try that, you’ll have to search the Internet for an DOS utility to do so.
Jos
|
|
|
|
Post by ck1402 on Apr 30, 2024 13:45:40 GMT 1
The dev resource will be returning tomorrow. I will have them run the logging suggestion and report back. This was one of those situations where they said it was ready and didn't have a test group to go through the program. It was released and there are apparent issues that the dev didn't see or test for at the time. The program doesn't have any issues when we are running it with out vDos on a 32-bit machine. It only occurs when we are using vDos on the 64-bit machines (which is the reason for using vDOS and not re-write the whole program from scratch) The keyboard input lag is the only issue we have come across so far and when i reported it to the dev they said to increase the keyboard buffer or to inquire on how to. I have sent your replies over and i am waiting for a response once they return.
|
|
|
|
Post by ck1402 on May 2, 2024 19:48:03 GMT 1
Hello Jos, i saw this thread vdos.proboards.com/thread/506/keystrokes-paste-issuesIt would seem they are having similar issues as well in that thread where keystrokes are missed when typing at any speed. That is the current issue we are seeing as well. I dug a little deeper and tried setting the cpu priority of vDOS and that didn't help the situation either. You said you are working on a newer version when would that be getting released? Also is there a possibility of getting a previous version to test against to see if it's present in that? |
|
|
|
Post by Jos on May 2, 2024 20:53:49 GMT 1
That thread was about the 2021 version of vDos. I assume harryrogers was then the only one with typed characters being dropped. Pasting text is somewhat unrelated to typing. vDos did this as fast as a program would retrieve a character from the keyboard buffer. For instance WP 6.x manages this at some 4,000 cps while actually processing the input. No problem, but FoxPro has its own keyboard buffer and moves keystrokes to that. Certainly if the pasted text was longer than that buffer size, keystrokes got dropped. A higher CPU priority gives vDos only a marginal speed gain when it’s competing with other applications for the CPU’s attention. But you would need at least a speed gain in the order of 200% for FoxPro able to process the moved keystrokes. I apparently sent harryrogers Dezember 6 a later intermediate version. But he didn’t report back if that fixed his issues. An list of previous versions is at: www.vdos.info/sources.html. Jos |
|
