|
Post by harryrogers on Mar 3, 2020 10:43:42 GMT 1
One quirk I've just come across with the latest version. If the WINDOW command is used in the config.txt to create a full screen (WINDOW = 100) then use of the down arrow causes the app to minimise. I replicated this behaviour on on 2 machines
|
|
|
Post by Jos on Mar 3, 2020 11:33:55 GMT 1
Oops, in full screen vDos has no caption bar with a system menu. No system menu (and minimize entry) causes Windows to ignore Win+Dn. To make Win+Dn behavior consistent, I added code to do that in full screen. But forgot to check for the Win key being down.
Fixed, I'll notify in this thread when vDosSetup is updated. Probably a second unrelated fix will follow.
Jos
|
|
|
Post by harryrogers on Mar 3, 2020 12:06:05 GMT 1
Thanks - that's good service!
All the best
|
|
|
Post by Jos on Mar 3, 2020 21:41:31 GMT 1
I just now updated vDosSetup.
Jos
|
|
|
Post by harryrogers on Mar 4, 2020 9:02:43 GMT 1
Many thanks Jos - I'll give it a go now. Just a note, if others have an issue running the install - Our antivirus (AVG Business 19.7.3103) breaks the install (without any notification on its part!) when I run the vDos setup program I get 'ShellExecuteEx failed code 299. Only part of a ReadProcess Memory or WriteProcessMemory request was completed' - Temporarily disabling the AV allows install to run normally - All the best
|
|
|
Post by Jos on Mar 4, 2020 9:15:15 GMT 1
I noticed AVG is no longer among the scan engines of virustotal.com (0 detections out of 72 scans). Just now submitted a false positive report to AVG. Though if I recall correctly, AVG isn’t that responsive with those reports.
Jos
|
|
|
Post by harryrogers on Mar 4, 2020 9:19:50 GMT 1
That seems to be running nicely now, thanks. [We have used AVG for many years and it's undoubtedly become more troublesome recently. When our contract is up I'll look elsewhere.]
|
|
|
Post by Jos on Mar 4, 2020 19:44:45 GMT 1
I got a response of AVG:
Thank you for contacting AVG.
Please accept our apologies for the inconvenience caused. The detection by AVG was incorrect and was removed in a recent AVG update, please wait at least 24 hours.
If the detection persists, please reply to this e-mail and: ...
Jos
|
|