|
|
Post by herman on Jun 3, 2019 12:59:51 GMT 1
Hello Jos,
Perhaps it is important to report it; during a test with my dBase 5 application (it was closed) and leave vDos open.
vDos 2019.05.01 freezes when approximately 5 minutes are not used and is sometimes difficult to get back on track.
I never had this problem with version 2018.05.01
Regards Herman
|
|
|
|
Post by Jos on Jun 3, 2019 13:25:21 GMT 1
Mentioned at the download page: “Will now go to hibernate after 5 minutes of continuous idle time.”.
vDos should awake on an external event like a key press, mouse move… You had to use the Task Manager to close vDos?
Jos
|
|
|
|
Post by herman on Jun 3, 2019 17:59:16 GMT 1
No, I didn't need that for that.
It turned out after alternate times that the Windows 10 x64 operating system on a
i5 3rd generation laptop had a lot of trouble getting it back on track,
so that you could place a command at the prompt.
The window itself gave no problems; it was a bit slower to get back up from the taskbar
|
|
|
|
Post by Jos on Jun 3, 2019 19:01:54 GMT 1
I tried it myself a few times, but didn’t notice a delay.
Isn’t it caused by the energy saving settings of your laptop?
Jos
|
|
|
|
Post by herman on Jun 3, 2019 19:34:09 GMT 1
There are no special settings made with this laptop.
Everything is a standaard setup with no special software or whatever and it is on the netpower
Herman
|
|
|
|
Post by Jos on Jun 3, 2019 19:38:57 GMT 1
OK, but what on another PC?
Jos
|
|
|
|
Post by herman on Jun 4, 2019 7:13:07 GMT 1
You must owe me that answer for a while, I do not have it here now and you will hear from me later
Herman
|
|
|
|
Post by richard on Jun 4, 2019 17:06:52 GMT 1
I'm not Herman, but I can verify that vDos 2019-05-01 freezes after about 5 minutes of idle time on a Win 7 Pro (64-bit) desktop. The DOS box turns gray and won't accept input. The only way I can shut it down is with Task Manager.
Richard
|
|
|
|
Post by Jos on Jun 4, 2019 17:24:09 GMT 1
Herman had a delay, didn’t need the Task Manager. I’m unable to reproduce either of the two situations, so we’ll have to wait for more reports…
Jos
|
|
|
|
Post by herman on Jun 10, 2019 17:42:51 GMT 1
Hallo Jos,
Didn't get this reproduced anymore, not even on another PC.
I suspect that the internal virus scanner was bothering things
Herman
PS. If it does happen again I will report it and try to detect the circumstances carefully
|
|
|
|
Post by andrew on Jul 18, 2019 18:15:19 GMT 1
Mentioned at the download page: “Will now go to hibernate after 5 minutes of continuous idle time.”. vDos should awake on an external event like a key press, mouse move… You had to use the Task Manager to close vDos? Jos
One question about this. Just to clarify.
With your hibernate after 5 minutes would that just be keystroke movements? So if some process is taking more then 5 minutes it could be possible to hibernate or is there a combination of low CPU use and no keystroke movement where this gets enabled.
As i've had reports of freezing but never asked them if they were present using the machine or not while running a long operation.
|
|
|
|
Post by Jos on Jul 18, 2019 19:18:55 GMT 1
vDos base mode is just to sleep, periodically releasing CPU time back to Windows. Still attending the DOS program, but at a low rate. When it detects the program becomes busy, that is accepts a keystroke, mouse action, writes to the screen, or does some file operation (read, write…), vDos will postpone sleep mode for some time (varies per action) and runs at 100%. If the program ‘signals’ it is busy during that time, sleep mode is further postponed. This way vDos will keep running at 100% until the program is considered inactive for some time (with file operations some 30 seconds).
When continuously in sleep mode for at least 5 minutes, hibernate kicks in. vDos will suspend further operation completely until it gets a notification of an external event from Windows, like a keystroke, mouse movement…
Jos
|
|
|
|
Post by smpettit on Jul 19, 2019 7:57:02 GMT 1
Hi there,
I'm working on a transition for multiple DataPerfect (dp26y) databases onto Windows Server 2019 (from Server 2003) and evaluating vDos as an option. I've only recently started this project so don't have old versions to compare against but I am finding that vDos locks up entirely and the window is there but ceases to respond. Sometimes the CPU is pegged, other times it sits idle. Either way killing vDos resolves the issue.
Is this likely related to the other reports in this thread/should I request the earlier versions to try, or is this unrelated and if so should I begin a separate thread and what other detail would be useful to help resolve this?
-Scott
|
|
|
|
Post by Jos on Jul 19, 2019 9:50:46 GMT 1
I haven’t encountered this myself, and had a look at the hibernate function, but don’t see how vDos could get stalled. I will do some testing, leaving programs alone for a while. Perhaps I’ll get then get it also since there’re now more reports on this.
I’ll send you the 2018.05.01 version by wetransfer.
Jos
|
|
|
|
Post by smpettit on Jul 19, 2019 12:26:09 GMT 1
Thank you Jos, I will test this and report back
|
|
