Yoghoo wrote on 2024-07-09, 11:33:

That is correct. You mounted another drive. C: is empty as all Dosbox-X files are on your Z: drive.

If your directory is not empty and you don't see them on C: then that is another problem though. Never tried it on Linux so can't help with that. I set nocachedir to true in the conf file btw as sometimes copied over files only showed up after a Dosbox-X restart.

Yes, DOSBox-X files are on virtual Z: drive, as they are in the case with original DOSBox, but the directory which I'm trying to mount as virtual C: drive is not empty and it seems that it is not accessible by the linux snap package version of DOSBox-X. There's no such a problem with original DOSBox, but is is installed from normal internet repo, not in software package like snap or flatpak.

The files in snap package installations can not be edited, added, deleted, replaced directly. Again, I'm avoiding this kind of software linux packages, but I can't find any (un)official repos for DOSBox-X to install it "the normal way".

Tried on Lubuntu 22.04.4.

analog_programmer wrote on 2024-07-09, 11:47:

Yes, DOSBox-X files are on virtual Z: drive, as they are in the case with original DOSBox, but the directory which I'm trying to […]
Show full quote

Yoghoo wrote on 2024-07-09, 11:33:

That is correct. You mounted another drive. C: is empty as all Dosbox-X files are on your Z: drive.

If your directory is not empty and you don't see them on C: then that is another problem though. Never tried it on Linux so can't help with that. I set nocachedir to true in the conf file btw as sometimes copied over files only showed up after a Dosbox-X restart.

Yes, DOSBox-X files are on virtual Z: drive, as they are in the case with original DOSBox, but the directory which I'm trying to mount as virtual C: drive is not empty and it seems that it is not accessible by the linux snap package version of DOSBox-X. There's no such a problem with original DOSBox, but is is installed from normal internet repo, not in software package like snap or flatpak.

The files in snap package installations can not be edited, added, deleted, replaced directly. Again, I'm avoiding this kind of software linux packages, but I can't find any (un)official repos for DOSBox-X to install it "the normal way".

Tried on Lubuntu 22.04.4.

Don't know if this applies to you but from https://github.com/flathub/com.dosbox_x.DOSBox-X:

Limitations
For security reasons, this Flatpak is sandboxed and only has access to the user's Home folder. You should place any files you need within DOSBox-X in that folder (or in a subfolder). Alternatively you can allow additional access with the override command. But note that this does not work for all directories as some (like /usr) have special restrictions. For instance, to allow access to /run/media where USB devices are typically mounted, run the following command:

flatpak override --filesystem=/run/media com.dosbox_x.DOSBox-X

Yoghoo wrote on 2024-07-09, 12:00:

Don't know if this applies to you but from https://github.com/flathub/com.dosbox_x.DOSBox-X: […]
Show full quote

Don't know if this applies to you but from https://github.com/flathub/com.dosbox_x.DOSBox-X:

Limitations
For security reasons, this Flatpak is sandboxed and only has access to the user's Home folder. You should place any files you need within DOSBox-X in that folder (or in a subfolder). Alternatively you can allow additional access with the override command. But note that this does not work for all directories as some (like /usr) have special restrictions. For instance, to allow access to /run/media where USB devices are typically mounted, run the following command:

flatpak override --filesystem=/run/media com.dosbox_x.DOSBox-X

Thank you! I've missed this info. I'll try to mount some subfolder in user's "Home" folder.

P.S. So, it is not a problem of the DOSBox-X software snap/flatpak package, but in general a problem with those type of installations. One more reason to not use these snaps/flatpaks at all 😀

P.S.2. The "Home" subfolder trick did not work 🙁

Yoghoo wrote on 2024-07-09, 12:00:

Don't know if this applies to you but from https://github.com/flathub/com.dosbox_x.DOSBox-X: […]
Show full quote

Don't know if this applies to you but from https://github.com/flathub/com.dosbox_x.DOSBox-X:

Limitations
For security reasons, this Flatpak is sandboxed and only has access to the user's Home folder. You should place any files you need within DOSBox-X in that folder (or in a subfolder). Alternatively you can allow additional access with the override command. But note that this does not work for all directories as some (like /usr) have special restrictions. For instance, to allow access to /run/media where USB devices are typically mounted, run the following command:

flatpak override --filesystem=/run/media com.dosbox_x.DOSBox-X

Ok, the solution for me turned out to be not to mount "/home/{mounted subdir}", but "/home/{USER}/{mounted subdir}". And it's pretty inconvenient, still better than nothing.

P.S. The problem was really due to software packages limitation. Working solution for DOSBox-X snap package in my case (with access to second HDD): "sudo snap connect dosbox-x:removable-media" and after this any directory on the second HDD can be mounted as DOSBox-X virtual HDD just like in the original DOSBox.

I can't make network work with Pcap or slirp. Because I noticed that 98SE and ME are running a little bit faster in DOSBox x instead of PCem (I don't use 86Box is very incompatible for me), I wanted to make some 3Dfx games testing.

Why is so difficult?

@JSO

Why is 86Box incompatible for you?

Many 3Dfx games are running with glitches and low fps. I experienced many crashes when I was installing drivers and etc. PCem for me is solid. Whatever build I had choose. From 386 to PII and from DOS, Windows 3.x to NT 3.1, NT 3.51, OS/2 2.1x, OS/2 Warp 3 and OS/2 Warp 4, Windows 9x, ME and 2000.

PCem and 86Box emulate a complete x86 PC, down to the individual hardware components. So that is why you will often experience more accurate and stable 3dfx emulation in PCem, especially if running Windows 95/98 games. 3dfx support in DOSBox-X is achieved through direct software emulation of a Voodoo card, or via hardware pass-through such as OpenGlide.

It sounds like you are not happy with the level of accuracy or performance using the software emulation mode, so you only have two choices. Try the same games with the hardware or pass-through 3dfx emulation mode - for which there are extensive instructions on the DOSBox-X website, or try another variant of DOSBox (i.e Staging, Pure) which use different code to emulate the Voodoo card in software. The problem with the latter is that support for Windows 95/98 will be more limited and unstable.

Just installed Dosbox-x on my XP system having hopes of playing Sierra's Front Page Sports Football Pro 95. Tried running it on D-fend but it always
crashes at halftime during a game so that led me to try another front end.

The game installs fine but when running the "hike.exe" I get this error saying can't run the game on a network. This system is "stand alone" not on
a network so can't see why that's coming up unless there's a network setting that's on by default in Dosbox-x? The other culprit could be I have the
game installed under D-fend in another directory however that's not mounted.

Sierra games can be finicky, up to this point I have only been able to get this game running on Pcem. Any thoughts or ideas would be a big help thanks!

buckeye wrote on 2024-10-28, 14:29:

Just installed Dosbox-x on my XP system having hopes of playing Sierra's Front Page Sports Football Pro 95. Tried running it on […]
Show full quote

Just installed Dosbox-x on my XP system having hopes of playing Sierra's Front Page Sports Football Pro 95. Tried running it on D-fend but it always
crashes at halftime during a game so that led me to try another front end.

The game installs fine but when running the "hike.exe" I get this error saying can't run the game on a network. This system is "stand alone" not on
a network so can't see why that's coming up unless there's a network setting that's on by default in Dosbox-x? The other culprit could be I have the
game installed under D-fend in another directory however that's not mounted.

Sierra games can be finicky, up to this point I have only been able to get this game running on Pcem. Any thoughts or ideas would be a big help thanks!

Tried running the game on regular dosbox latest version and it runs to a point. When the game reaches halftime it crashes to dos prompt with message
"palette.opp:27 error reading palette information". Apparently this is an error common with other sierra sports games running through dosbox.
This has something to do with copyright protection stuff but this is a legit copy but dosbox for whatever reason sets it off anyways.

Looking at other posts there is a mention of something called "TOUCH" which I have no clue what that is and searches have come come up empty so far.
Think I'm just going to run this game with PCEM or real hardware (Pentium 233mhz based is slowest I got) as this rabbit hole is getting too deep.

https://man7.org/linux/man-pages/man1/touch.1.html

No real fullscreen on dosbox-x. Need 640x480 60Hz for CRT monitor.

I don't know what I'm doing wrong but I can't get doxbox-x set to fullscreen mode.
What I'm trying to do is to get fullscreen at 640x480 60Hz to get as close as possible to the real game image on a PC of the time.
I know it's possible because with dosbox-stagging I get it without problem with this configuration:

I want to get it with dosbox-x because it is the only port that supports LFN which for me is a must.

Last version of dosbox-x
W10 at 1600x1200 85hz on a CRT monitor
I have tried changing the “fullresolution” parameter to all values, I have also tried all the possibilities of the “output” parameter. The only thing I get when I switch from windowed to full resolution is that the window changes a little bit in size (depending on the resolution I have set) and that the borders don't appear. If I match the resolution of fullresolution = 1600x1200 it obviously covers the whole screen, but I understand that as a frameless window, not as a full screen.

One of my configurations, I've tried many, many, many:

Could someone help me please?

Seems I can't get breadbox ensemble to work on DosBox-X.
went through the CD install process. Rebooted DosBox X and I get invalid font file in UserData/Font directory are all the files Berkeley through to Universi spread out through 17 font files. Te install also reported no error while it was installing.

Help 😀