vDos 7MAY2019 - Minimized window start up (vDosMinimize.exe)

[steve]

The seems to be a minor problem caused by the latest update to W10.

I have a DOS data backup program which is started automatically as a background task when W10 reboots. The batch file invokes a vDos environment (using vDosMinimize.exe) which then runs the data backup program.
 
Before the latest W10 backup, when the vDos icon on the task bar was clicked, a 'normal' vDos screen would be displayed. Now a tiny vDos window (about 10mm by 10mm) is displayed. I have to click on the title bar and change the font size to have the window displayed properly. Subsequent minimize and maximize work as expected. If I stop the vDos environment and then restart it again (using the same batch file) the errant behaviour repeats.

Neither CONFIG.TXT, nor AUTOEXEC.TXT, nor the data backup program have been modified recently. The vDos being invoked is the May 2019 version.

I suspect there is some unintended interaction between the latest W10 update and vDosMinimize.exe (which was not issued or supported by Jos).

I am reporting this behaviour just in case others have noticed anything unusual with the recent W10 update.  If so please let me know.

Cheers,
Steve

[Jos]

I never heard of vDosMinimize. And would advice you to use a genuine Windows program to create a backup.
That will be a lot faster and more secure. No only for some DOS data, but preferably for your whole Windows system.

The tiny vDos window will of course be caused by vDosMinimize, not compatible with Windows 10? So I don’t think upgrading to vDos 2022.05.01 will help.

Jos

[steve]

Hi Jos,

Thank you for your response.

vVosMinimize is a compiled script file (See emendelson's message in vdos.proboards.com/post/2705). It has been working perfectly under W10 for over a year now. I think the latest w10 update has changed the resulting vDos windows appearance.

Your comments about using a genuine Windows program are very valid, however I will remain using the DOS based program as it was designed specifically for the bespoke database - (a) it selectively copies churning data every minute and less volatile data every hour; (b) it verifies the data for corruption; (c) it maintains a live grandfather, father, son copy of the database; (d) it has been tried and tested for 6 years now.

If I cannot find a workaround then it is no big deal, I reported it here just in case the W10 update has any other unexpected side-effects.

Cheers,
Steve

[Jos]

Perhaps Edward Mendelson can figure out why that script behaves different now.

Jos

[emendelson]

It works here under Windows 11. Did you follow the instructions?

"Place it in the same folder with vDos.exe; create a shortcut to it that runs minimized; or use "start /min vDosMinimize.exe" at the Windows command line."

The easiest way is to use it is to create a shortcut to vDosMinimize.exe and make sure that the properties of the shortcut show "Minimized" as the selection in the "Run" field. And if the shortcut is not in the same folder with vDos.exe and vDosMinimize.exe, make sure that "Start in" specifies the folder where those files are.