|
Post by jamesb52 on Nov 6, 2023 8:43:32 GMT 1
I find vDOS useful for software development but one consequence is that I regularly crash my new ideas and can't move forward or backward. When I try to close my vDOS session by clicking the "X" in the upper right-hand corner of the vDOS window, vDOS beeps and says "One or More Files are Open". Then I have to reboot my entire system, which is tedious. Is there anyway to get around this? I can do this using DOSBox-X which will close crashed sessions, but DOSBox-X doesn't have the other vDOS goodies that make programming easy (especially the useful "copy & paste" tool), and compiling in DOSBox-X is incredibly s-l-o-w! I much prefer doing this work in a vDOS session.
Thanks! James
|
|
|
Post by Jos on Nov 6, 2023 11:17:59 GMT 1
I occasionally have the same ‘problem’ modifying vDos. But that didn’t tempt me to add some way to force close vDos.
I have a Task Manager shortcut handy at the taskbar. Click that, right click vDos, End task. You can also use Ctrl+Shift+Esc to start Task Manager.
Jos
|
|
|
Post by whathim on Nov 6, 2023 21:02:40 GMT 1
I too have come across this while developing my text editor to run under vDos. As Jos says, Task Manager is the way to kill the vDos task – no need to reboot.
Keith
|
|