|
Post by harrya on Nov 16, 2023 22:02:33 GMT 1
I have a large dos program that runs great under Vdos. When I include "SET COMSPEC=C:\WINDOWS\SYSTEM32\CMD.EXE" in the Autoexec.txt, the program starts but I need to click on the screen in order to enter commands. If I remark out the "set comspec", when the progam starts I can immediately enter commands. With the "set comspec" in, it appears that my program starts and then restarts. Is there a way to included the "set comspec" but be able to enter commands without having to click on the program first?
|
|
|
Post by Jos on Nov 16, 2023 22:42:12 GMT 1
Why do you need the command line processor set to CMD.EXE?
Never thought of this kind of SET COMSPEC usage. It's normally a DOS program, by default the built-in emulated one.
CMD.EXE is however a Windows program, so runs in its own window, outside that of vDos. And ‘steals’ the focus when actually started.
Jos
|
|
|
Post by harrya on Nov 20, 2023 18:02:36 GMT 1
I need the cmd.exe processor to run batch files that don't run correctly under 4dos. Is there a way to return the focus to the screen without having to click on it? Is there a command I can put in autoexec.txt? Or any other ideas?
|
|
|
Post by Jos on Nov 20, 2023 19:43:55 GMT 1
When a program exits, Windows normally returns the focus to the program that lost it. No idea why that then isn’t vDos. You could peek with task switcher (Alt+Tab) which program got it instead (the one to the left of the newly selected)?
Jos
|
|
|
Post by martin on Nov 20, 2023 20:02:32 GMT 1
Don't know how you use the COMSPEC variable in vdos with your Windows-programs. But probabaly SET COMSPEC=CMD HIDE C:\WINDOWS\SYSTEM32\CMD.EXE will do the job. From vDos command line, it opens Windows cmd.exe without stealing focus (if you enter %comspec% in vDos...)
HTH
Martin
|
|