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 does not work with D-Fend Reloaded (again) #641

Open
lwchkg opened this Issue Apr 1, 2018 · 12 comments

Comments

Projects
None yet
3 participants
@lwchkg

lwchkg commented Apr 1, 2018

I don't know what happened. What I've got is the dialog that says that DOSBox fails to start, nothing else.

I'd appreciate if you can tell me how to obtain a useful error log. :-)

@lwchkg

This comment has been minimized.

Show comment
Hide comment
@lwchkg

lwchkg Apr 1, 2018

Part 2: I wasn't naming the dosbox executable dosbox.exe. But changing it doesn't fix the problem.

So I make a program that dumps the command line and working directory and command line to a file. This is what I found:

"D:\d-fend\dosbox-x-20180316\DOSBOX.EXE" -CONF "C:\Users\lwchkg\AppData\Local\Temp\DOSBOX.CONF" -NOCONSOLE
D:\d-fend\dosbox-x-20180316

(The first line is the command line, the second is the working directory.)

And then I run the command in the cmd.exe... Viola, dosbox-x started correctly! So somehow the dosbox process created by D-Fend Reloaded is different from that created by cmd.exe...

lwchkg commented Apr 1, 2018

Part 2: I wasn't naming the dosbox executable dosbox.exe. But changing it doesn't fix the problem.

So I make a program that dumps the command line and working directory and command line to a file. This is what I found:

"D:\d-fend\dosbox-x-20180316\DOSBOX.EXE" -CONF "C:\Users\lwchkg\AppData\Local\Temp\DOSBOX.CONF" -NOCONSOLE
D:\d-fend\dosbox-x-20180316

(The first line is the command line, the second is the working directory.)

And then I run the command in the cmd.exe... Viola, dosbox-x started correctly! So somehow the dosbox process created by D-Fend Reloaded is different from that created by cmd.exe...

@joncampbell123

This comment has been minimized.

Show comment
Hide comment
@joncampbell123

joncampbell123 Apr 16, 2018

Owner

It seems like D-Fend expects the executable name to be dosbox.exe.

You can make it work by renaming dosbox-x.exe to dosbox.exe and then directing D-Fend Reloaded to point at it. Doesn't seem to have any issues so far.

Owner

joncampbell123 commented Apr 16, 2018

It seems like D-Fend expects the executable name to be dosbox.exe.

You can make it work by renaming dosbox-x.exe to dosbox.exe and then directing D-Fend Reloaded to point at it. Doesn't seem to have any issues so far.

@lwchkg

This comment has been minimized.

Show comment
Hide comment
@lwchkg

lwchkg Apr 16, 2018

Part 2: I wasn't naming the dosbox executable dosbox.exe. But changing it doesn't fix the problem.

I did the rename to see if that solves the problem. Unfortunately, it didn't. Maybe I can retry today.

lwchkg commented Apr 16, 2018

Part 2: I wasn't naming the dosbox executable dosbox.exe. But changing it doesn't fix the problem.

I did the rename to see if that solves the problem. Unfortunately, it didn't. Maybe I can retry today.

@lwchkg

This comment has been minimized.

Show comment
Hide comment
@lwchkg

lwchkg Apr 17, 2018

Confirmed... Here's the movie: https://youtu.be/xeBXnlMZeJw

lwchkg commented Apr 17, 2018

Confirmed... Here's the movie: https://youtu.be/xeBXnlMZeJw

@joncampbell123

This comment has been minimized.

Show comment
Hide comment
@joncampbell123

joncampbell123 Apr 17, 2018

Owner

Ah, yes.

Select a different video output driver and renderer, then it at least starts.

Owner

joncampbell123 commented Apr 17, 2018

Ah, yes.

Select a different video output driver and renderer, then it at least starts.

@lwchkg

This comment has been minimized.

Show comment
Hide comment
@lwchkg

lwchkg Apr 18, 2018

Somehow I managed to turn on logging for D-Fend. What I've got is the following message:

Logging: opened logfile 'logfile.txt' successfully. All further logging will go to that file.
DOSBox-X version 0.82.4
         0       MISC:Copyright 2002-2015 enhanced branch by The Great Codeholio, forked from the main project by the DOSBox Team, published under GNU GPL.
E_Exit: Can't init SDL directx not available

Anyway, I didn't manage to make startup work by changing my video output driver. I could select "Direct X" or "WinDIB", but what I've got is substitute "windib" into "directx" in the message.

lwchkg commented Apr 18, 2018

Somehow I managed to turn on logging for D-Fend. What I've got is the following message:

Logging: opened logfile 'logfile.txt' successfully. All further logging will go to that file.
DOSBox-X version 0.82.4
         0       MISC:Copyright 2002-2015 enhanced branch by The Great Codeholio, forked from the main project by the DOSBox Team, published under GNU GPL.
E_Exit: Can't init SDL directx not available

Anyway, I didn't manage to make startup work by changing my video output driver. I could select "Direct X" or "WinDIB", but what I've got is substitute "windib" into "directx" in the message.

@joncampbell123

This comment has been minimized.

Show comment
Hide comment
@joncampbell123

joncampbell123 Apr 18, 2018

Owner

Since D-Fend Reloaded is open source, it might be worthwhile to fork it and add support for DOSBox-X, then see if patches can be sent back to the main project.

EDIT: Hmm... source code is in Pascal (*.PAS). I don't have a toolchain for that. But, for someone who does, the project is open source!

Owner

joncampbell123 commented Apr 18, 2018

Since D-Fend Reloaded is open source, it might be worthwhile to fork it and add support for DOSBox-X, then see if patches can be sent back to the main project.

EDIT: Hmm... source code is in Pascal (*.PAS). I don't have a toolchain for that. But, for someone who does, the project is open source!

@lwchkg

This comment has been minimized.

Show comment
Hide comment
@lwchkg

lwchkg Apr 18, 2018

I see... that seems to be around an environment variable called "SDL_VIDEODRIVER". What are the valid values anyway?

lwchkg commented Apr 18, 2018

I see... that seems to be around an environment variable called "SDL_VIDEODRIVER". What are the valid values anyway?

@lwchkg

This comment has been minimized.

Show comment
Hide comment
@lwchkg

lwchkg Apr 18, 2018

Found the information: https://wiki.libsdl.org/FAQUsingSDL

Looks like for SDL 2.0, the only valid value for SDL_VIDEODRIVER is "windows". And for SDL 1, the valid value is "windib" ("directx" doesn't work for my computer here).

So I found a way to run dosbox-x with D-Fend Reloaded now. Anyway, the only sane value for SDL_VIDEODRIVER is not to set it, because setting that to anything will break some version of SDL. :-(

lwchkg commented Apr 18, 2018

Found the information: https://wiki.libsdl.org/FAQUsingSDL

Looks like for SDL 2.0, the only valid value for SDL_VIDEODRIVER is "windows". And for SDL 1, the valid value is "windib" ("directx" doesn't work for my computer here).

So I found a way to run dosbox-x with D-Fend Reloaded now. Anyway, the only sane value for SDL_VIDEODRIVER is not to set it, because setting that to anything will break some version of SDL. :-(

@lwchkg

This comment has been minimized.

Show comment
Hide comment
@lwchkg

lwchkg Apr 18, 2018

For the "Pascal" source, I guess we'll have the most luck with Delphi: https://www.embarcadero.com/products/delphi/starter. This is free for projects with revenue less than US1000. (5 users max)

lwchkg commented Apr 18, 2018

For the "Pascal" source, I guess we'll have the most luck with Delphi: https://www.embarcadero.com/products/delphi/starter. This is free for projects with revenue less than US1000. (5 users max)

@lwchkg

This comment has been minimized.

Show comment
Hide comment
@lwchkg

lwchkg Apr 25, 2018

D-Fend Reloaded is found to use an old version of ZLib (1.1.4). No good at all! And I don't know how to update it to the latest version.

I could change the reference to the ZLib to the one included in Delphi, but most likely it is just a slightly less outdated version os ZLib.

lwchkg commented Apr 25, 2018

D-Fend Reloaded is found to use an old version of ZLib (1.1.4). No good at all! And I don't know how to update it to the latest version.

I could change the reference to the ZLib to the one included in Delphi, but most likely it is just a slightly less outdated version os ZLib.

@lwchkg

This comment has been minimized.

Show comment
Hide comment
@lwchkg

lwchkg Apr 26, 2018

The ZLib in Embarcadero Delphi 10.2.3 turns out to be version 1.2.8. So I'm going the long route by compiling ZLib 1.2.11 from source.

lwchkg commented Apr 26, 2018

The ZLib in Embarcadero Delphi 10.2.3 turns out to be version 1.2.8. So I'm going the long route by compiling ZLib 1.2.11 from source.

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