|
Post by paul on Oct 23, 2018 22:50:33 GMT 1
Hi - newbie question here. Can I run vDOS in a window? Or only full-screen? Thank you!
|
|
|
Post by Jos on Oct 23, 2018 23:02:47 GMT 1
vDos always runs in a window, even if in 'full-screen' mode.
Jos
|
|
|
Post by paul on Oct 24, 2018 2:20:25 GMT 1
ahhh - yes, reading the help file alt-enter lets me see the minimise and maximise areas. Pleas accept my apology. I thought I had read the help file carefully.
Paul
|
|
ginahoy
Guest
|
Post by ginahoy on Mar 1, 2019 19:13:38 GMT 1
I believe this answers the question I was going to post, but maybe there's a solution?
I just installed vdos in Windows 10 to run DOS text-based program Managing Your Money (MYM). The vdos window window opens such that the bottom of the screen is hidden behind the Win10 task bar. Every time I open the program, I either have to manually adjust the window position, or I switch to full screen mode (yes, ALT-ENTER does make vdos full screen). My question: is there a way to force vdos to open in full-screen mode? If not, is there a way to adjust the opening position of the vdos window so it's not partially hidden? Thanks.
|
|
|
Post by Jos on Mar 1, 2019 19:27:26 GMT 1
Documented in config.txt:
REM Window REM ====== rem The default vDos window is centered and will cover about (max) 75% of the screen. rem This can be changed by WINDOW = [-][max percentage][,left-x-pos:top-y-pos] rem In text mode, the window has some extra blank space to the left and right, the minus sign will disable this. rem This would give you a full screen view. Mind, it's still a window (in disguise), so it won't obscure any Windows messages: rem WINDOW = 100 rem Alternatively, you can use Alt+Enter to switch to and back from full screen while the program is running.
The default 75% of the screen size and centered position won’t cause the Windows task bar to obscure part of the vDos window. So you would either have set: WINDOW = a too high percentage or WINDOW = percentage,left-x-pos:a too high y value
Jos
|
|
|
Post by ginahoy on Mar 1, 2019 20:21:32 GMT 1
Mar 1, 2019 11:27:26 GMT -7 Jos said: Documented in config.txt:The default 75% of the screen size and centered position won’t cause the Windows task bar to obscure part of the vDos window. So you would either have set: WINDOW = a too high percentage or WINDOW = percentage,left-x-pos:a too high y value Jos Thanks for prompt reply. I made no changes to those lines. The only line I changed in config was to remove hash mark to activate mouse support. The other lines are still 'commented' out. But at least now I know how to adjust the opening position. It would be helpful if you could tell me the default values for left-x-pos,top-y-pos. I have no idea what the range is, but if I know the defaults, I can trial-and-error from that. OTOH, I'd prefer vdos to open in 'true' full-screen mode. Is that not possible? Note that CTRL+ENTER apparently puts vdos in true screen mode on this machine, since the MYM date field appears in extreme right corner of the 16:9 screen. Given that, it would seem like there would be a config setting that would force this upon opening.
|
|
|
Post by Jos on Mar 1, 2019 20:54:50 GMT 1
No hash marks in config.txt, besides those in the COLOR = directive example. Can you post a copy of your config.txt file? Jos
|
|
|
Post by ginahoy on Mar 2, 2019 0:22:16 GMT 1
No hash marks in config.txt Sorry, I used the wrong word. I'm accustomed to using hash marks to tell script parsers to ignore a line. Anyway, I made no changes to config except to remove the 'rem' on the mouse line.
|
|
|
Post by Jos on Mar 2, 2019 0:48:43 GMT 1
Still confused by the vDos defaults seemingly not working. A copy of your config.txt file would help to clarify what's going wrong on your system...
Jos
|
|
|
Post by ginahoy on Mar 2, 2019 7:06:48 GMT 1
I've attached a zip file with startup files and screenshot. The taskbar is black, making it difficult to see the delineation between vdos window and taskbar, but if you look to the bottom right, you can see that the timestamp is behind the taskbar (below <Esc> Back up. vdos startup files.zip (366.49 KB)
|
|
|
Post by Jos on Mar 2, 2019 12:00:12 GMT 1
I see what’s going on, your monitor physical resolution is 1920x1080, but you use a scale factor of some 150%.
vDos will first size its window based on the physical resolution, then size it down until it actually fits the desktop (I probably have to look into logical scaling). Since the default window size is in percentages (75), in your situation even sized down, then centered, there’re no default left-x-pos and top-y-pos values.
For a full sized window you would use: WINDOW = 100
For a smaller one, start with something like: WINDOW = 50 Increase the percentage if the window is too small, eventually add positioning: WINDOW = 50,100:0 100 is the x-position in pixels from the left, 0 the y-position from the top.
Jos
|
|
|
Post by ginahoy on Mar 3, 2019 4:34:50 GMT 1
I see what’s going on, your monitor physical resolution is 1920x1080, but you use a scale factor of some 150%. Sorry, I should have mentioned that. Ok, I just set WINDOW = 100 and that causes vDos to open in full-screen mode, exactly what I want. Thanks! Since I have the MYM color scheme set to show a black background, I didn't realize there was a black border around the frame (produced by vDos?) to fill out the wide screen aspect ratio. I was mistaken in my earlier comment that the MYM timestamp appears at the extreme right corner of the screen (I'm sure you already knew that ;-) Now if I can figure out how to get the beep sounds to work! I run MYM on my Linux desktop under dosEmu and it has the same limitation, suggesting this is a MYM issue that cannot be resolved by the DOS emulator. Thanks again for the assist!
|
|
|
Post by Jos on Mar 3, 2019 7:25:10 GMT 1
The black border is indeed filled by vDos. The standard DOS beep should be generated, in the next version you have to put a sound file (beep.wav) in the vDos directory to get that beep. Probably MYM produces its own beep. If DOSEMU emulates the DOS PC more precisely, something else could cause the absence of the beep: Your PC’s don’t have an internal speaker anymore. Rerouting that to the multimedia system comes with a disadvantage. Instead of a modest beep, you’ll get a loud BEEP. Jos
|
|
|
Post by ginahoy on Mar 4, 2019 1:29:16 GMT 1
Your PC’s don’t have an internal speaker anymore.... Uh, yeah, that's probably it. My recently retired XP machine had an old-school motherboard-connected speaker. Likewise with my wife's 2004 vintage T42 Thinkpad, which also ran XP. THat's the one we just replaced with the Dell E5550. Of course MYM ran natively on both machines in DOS compatibility mode and the beep sounds went through the internal speaker. I never stopped to consider how old DOS programs generated audio (beeps), and that those sounds weren't routed to regular audio channels. I suppose a DOS emulator could intercept and reroute those calls, but as you said, it would require a volume adjustment, which I imagine could be set in the config file. Just thinking out loud... Fortunately MYM's functionality isn't dependent on the beep sounds. They're mostly used to signal an invalid keyboard selection, and to confirm success when reconciling accounts.
|
|
|
Post by johnswolter on Sept 9, 2019 20:50:56 GMT 1
For a smaller one, start with something like: WINDOW = 50 Increase the percentage if the window is too small, eventually add positioning: WINDOW = 50,100:0 100 is the x-position in pixels from the left, 0 the y-position from the top. Jos [Post Editing Error: -- Blank line deleted when editing Quotation, can't enter a replacement, suggest TAB at bottom of Quote to create comment new blank line, jsw] Note WINDOW syntax: WINDOW = percentage,left-x-pos:a too high y value 1.) %,x:y The comma is missing in the config.txt file 2.) No blank character allowed after the comma before the x:y position parameters 3.) Parameter values need more explanation & examples 4.) Check other config.txt for similar correction 5.) These corrections need to be done to current production distribution.
|
|