Don't use Daum. It is very old, very buggy and abandoned. Use vDos or vDosPlus for applications like Paradox.

I did start playing around in VDosPlus but when I try and run Paradox it tells me "Can't start Paradox: no directory specified for PDOXUSRS.net", I'm just not sure what configuration I'm missing. I didn't have to specify anything in DOSBox except for my mounted drives and running the paradox.exe file.

You could try DOSBox-X or dosbox-staging

I would suggest you to try DOSBox-X for this too. I am the developer of vDosPlus, but I have been mostly worked on DOSBox-X recently which has a lot of improvements.

Windows installer for the latest DOSBox-X 0.83.3: DOSBox-X-0.83.3-setup.exe

Thanks, I downloaded DOSBox-X and selected SDL1 during the install, when I run Paradox I get a Script error. When I click debug, I get "Run error: Expecting a value of LONG INTEGER type" and it refers to a line SETKEY -50 SETDIR "K:\\PDOX35" Play "RINIT". I have C: and K: mounted and see all of the files and Paradox does start but obviously it has issues with the script that needs to run. When I run the old original DOSBox 0.74 it will open up my PARADOX and run the script without any issues. Is there a setting I need to change in the configuration file?

Tried:
32 bit and 64 bit
SDL1 and SDL2
DOS Ver 5 and 7.10

I just tried to install and run Paradox 4.5 for DOS myself (downloaded from the Internet) in DOSBox-X 0.83.3 and it seems to run without issues, although I haven't thoroughly tested all its functions. Not sure if it is the same version you are using, but I think 4.5 is already the latest version for DOS.

Yes, I'm using 4.5, Paradox does load but I think when it calls on loading this script, that's when it throws the error "Run error: Expecting a value of LONG INTEGER type". I'm not to sure why the old DOSBox will run the script but this version throws an error, that's why I was thinking it may be a setting.

Perhaps you can give the exact steps to reproduce the issue.

Also, try with core=normal

Hi everyone, I wanted to thank you for all of the replies, I was finally able to get it working with DOSBox-X. It looks like I was fighting a Paradox issue and not a DOSBox issue, I think there was a file locked on the system that when it was closed out or became unlocked it allowed DOSBox, Paradox and the Paradox scripts to run the right way.

Thanks again!!

Aggro99 wrote on 2020-07-10, 20:37:

Hi everyone, I wanted to thank you for all of the replies, I was finally able to get it working with DOSBox-X. It looks like I was fighting a Paradox issue and not a DOSBox issue, I think there was a file locked on the system that when it was closed out or became unlocked it allowed DOSBox, Paradox and the Paradox scripts to run the right way.

Thanks again!!

I would call that paradoxical . 😀