My text editor program cannot see EMS memory
Nov 26, 2021 23:03:59 GMT 1
Post by whathim on Nov 26, 2021 23:03:59 GMT 1
Ok, we have something to go on. If I understand correctly, you managed to create a PB executable containing the POPUP SLEEP USING statement and when run it gave “Error 5 at pgm-ctr: 300” under both vDos and NTVDM.
I’ve just written and compiled a minimal TSR in PowerBASIC for DOS. When run from a Command Prompt on my Windows XP (32-bit) machine it works perfectly. However, when run under vDos on my Windows 10 (64-bit) machine it fails with “Error 5 at pgm-ctr: 354”.
The details:
I’ve attached the source code (Popup.bas) and the executable (Popup.exe) of my minimal TSR test program. Run it once – nothing visible happens. Press its popup hot-key combination, Ctrl-Alt, to pop it up – it displays the unallocated bytes of EMS. Press Esc to terminate and uninstall it, or press any other key to pop it down – it restores the screen.
I have a desktop shortcut on my Windows XP (32-bit) machine that launches a windowed Command Prompt. Screenshots of the Properties of this shortcut are given in the attached MS Word document, “Command Prompt.docx”. My minimal TSR test program runs perfectly in this Command prompt. Note that EMS is not enabled for this Command Prompt and so the TSR should be swapping to file – I have confirmed this is the case by simultaneously observing the swap directory.
When I run the same TSR test program under vDos on my Windows 10 (64-bit) machine it fails with “Error 5 at pgm-ctr: 354”, which resolves, as before, to: POPUP SLEEP USING EMS, SwapSwap$
I do hope there are some clues in all this regarding why the PowerBASIC popup executable is failing in vDos.
Please get back if I should check anything else.
Attachment Deleted
I’ve just written and compiled a minimal TSR in PowerBASIC for DOS. When run from a Command Prompt on my Windows XP (32-bit) machine it works perfectly. However, when run under vDos on my Windows 10 (64-bit) machine it fails with “Error 5 at pgm-ctr: 354”.
The details:
I’ve attached the source code (Popup.bas) and the executable (Popup.exe) of my minimal TSR test program. Run it once – nothing visible happens. Press its popup hot-key combination, Ctrl-Alt, to pop it up – it displays the unallocated bytes of EMS. Press Esc to terminate and uninstall it, or press any other key to pop it down – it restores the screen.
I have a desktop shortcut on my Windows XP (32-bit) machine that launches a windowed Command Prompt. Screenshots of the Properties of this shortcut are given in the attached MS Word document, “Command Prompt.docx”. My minimal TSR test program runs perfectly in this Command prompt. Note that EMS is not enabled for this Command Prompt and so the TSR should be swapping to file – I have confirmed this is the case by simultaneously observing the swap directory.
When I run the same TSR test program under vDos on my Windows 10 (64-bit) machine it fails with “Error 5 at pgm-ctr: 354”, which resolves, as before, to: POPUP SLEEP USING EMS, SwapSwap$
I do hope there are some clues in all this regarding why the PowerBASIC popup executable is failing in vDos.
Please get back if I should check anything else.
Attachment Deleted