Jos Schaars

Not selecting or pasting (by mouse click) text in full screen mode is an exception. I probably found that logical since the vDos window occupies the whole screen. But you could have multiple monitors, do Alt+Tab, Alt+Enter, have a RDP session… I’ll have a second look at that, but it won’t be changed until the next version of vDos. So you’ll have to stick with your solution for now. Jos

The Are You Sure (Y/N)? message is neither displayed instantly with NTVDM. Your program first tries to produce some fancy warning signal. For this it hooks into the INT 8 interrupt, the servicing routine is a real mess. It uses several counters that would define the length and pitch of the tones to generate. It reads/writes to the PIT, PIC and keyboard controller. vDos doesn’t support that to the hardware level, and the servicing routine is just wasting away millions of instructions before it finally...

The home page of vDos.info states: "If you don't already use (still rely on) a DOS application, want to play/experiment with DOS, its command prompt, programs or games: Forget about vDos, it is not meant for you!" So you should already have a working copy of the program somewhere. However, if you installed vDos to C:\vDos: Windows: Create a subdirectory like Install (C:\vDos\Install). Copy the contents of both disks to there (overwritef iles is OK). Start vDos vDos command prompt: use a: c:\vdos\install...

DOS programs needs no installation. Just copy the directory(ies) from the old to the new PC. That way you also get any settings or data. Jos

No, just that Win+Ctrl+C/V don’t work anymore. See the Readme file for alternatives. Jos

Many DOS users are aged… I missed “ctrl-win-v”; that key combination is taken by Windows itself since the Fall update. So it won't work in previous vDos versions (or vDosPlus). Jos

For vDosPlus you would have to consult its forum. In general: vDos has a copy/paste buffer of its own, no size limit, and takes care of DOS/Windows character translation. Characters are very gently - one at a time and only if a DOS program accepts/requests input - made available to the DOS program. The BIOS keyboard buffer isn’t even a factor. In the latest vDos version a change was made to accommodate a Clipper library that maintains a keyboard buffer of its own that could overrun (a msihap of that...

Tracking down the origin of such a problem is often like finding a needle in an unstable haystack moving around. Because of user interaction and deviations in the system clock, the moment the problem surfaces is different each run. So first is to stabilize and minimize the haystack; find a good starting point from where there’s at least no user action anymore. Gladly with vDos that is fairly easy; the problem was with the second Esc key. Determine how the program gets that key by logging BIOS Int...