Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dosbox-x always opens in window mode when launched from a batch file #2810

Open
Focus78 opened this issue Aug 18, 2021 · 7 comments
Open

Dosbox-x always opens in window mode when launched from a batch file #2810

Focus78 opened this issue Aug 18, 2021 · 7 comments

Comments

@Focus78
Copy link

Focus78 commented Aug 18, 2021

A reply would be nice?

@joncampbell123
Copy link
Owner

This is Windows, correct?

DOSBox-X.exe is a graphical application, so Windows will always launch it as it's own window and detach it from the command line. If it were compiled as a command line application, it would work, but then running from the desktop would also bring up a console window.

@Focus78
Copy link
Author

Focus78 commented Aug 18, 2021

What?

Can you just fix this so that "fullscreen = true" in the config file actually functions correctly?

Of fix the SDL2 soundfont problem since this behaviour does not take place in the build...

Either would solve the problem.

@maron2000
Copy link
Contributor

maron2000 commented Aug 18, 2021

Hi, I started dosbox-x from a simple batch file test.bat and it started in full screen mode.
Are there any difference in setting or procedure with yours?
I tested on Windows SDL1, and SDL2 both 32-bit.
(I believe you prefer 32-bit version, but would you specify which OS and version you tried if it isn't the case)

Edit: I tested 64bit versions (Windows SDL1, SDL2), and same result.

test.bat

dosbox-x

conf file

fullscreen        = true      #changed from default false to true
fulldouble        = true      #changed from default false to true (may not affect the result though)
fullresolution    = desktop   #default value

@Focus78
Copy link
Author

Focus78 commented Aug 19, 2021

joncampbell123 already stated that he was able to replicate the problem but has since done nothing about it.

I'm not going to repeat the same process all over again. You can ask him for details or see the other report if you have an unlimited amount of time on your hands to test what's already been verified.

@maron2000
Copy link
Contributor

maron2000 commented Aug 19, 2021

Oh, this was a duplicate of #2643?
I read it and understood that this is a compatibility issue of Windows SDL1 version and GlovePIE.
Please correct me if anything is wrong, or if you have any other software having the same issue in mind.

@maron2000
Copy link
Contributor

I managed to install GlovePIE 0.45 and confirmed the phenomenon.
It seems that if you wait to GlovePIE to completely launch before starting DOSBox-X, it works.
(So maybe not only GlovePIE but launching other software as well)

The example below waits for 2 seconds, you are free to tune it.
It worked for me, so it's worth trying. Hope it helps.

start piefree -test.pie
timeout /t 2
start dosbox-x -set fullscreen=true

@Focus78
Copy link
Author

Focus78 commented Aug 20, 2021

@maron2000

I can confirm that "timeout /t X" added to the batch file produces the expected behavior. Now why it's necessary or why joncampbell123 brushed it off when it ended up being such a simple workaround is another story...

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants