tutorial needed on installing apps in DOSBox-X, making mounts persistent

[ssybesma]

Really having a tough time with this and I don't know why.

All mounts I create are wiped clean, no matter how I create them.

Does the DOSBox-X app detect mounts involving the drivez folder and disregard them after a reboot?

The mount exists in the *.conf file, but it's being ignored.

[ssybesma]

The word mount is saying it's a bad command.

Guess I need to go back to DOSBox...this thing is too buggy to use.

[joncampbell123]

What mount command are you using and what is it expected to do?

Remember that DOSBox-X forked from SVN a long time ago and there's plenty of divergence between the two branches, even though some SVN changes are ported over from time to time.

Perhaps you're relying on recent MOUNT behavior in SVN that DOSBox-X does not yet implement.

[rderooy]

Looking at some of your deleted comments. The Z-Drive is read-only and cannot be changed. This is the same with vanilla DOSBox.

DOSBox-X does provide some additional programs on the Z: drive, and there is a way to add your own small programs/utilities, which is documented on the wiki, but it is not meant to install whole applications or games to.

You want to create yourself a C: drive from a directory on your host harddisk drive. e.g.

mount c: c:\dosroot
c:

Assuming that your harddisk has a c:\dosroot directory, that directory will now be the virtual C: drive inside DOSBox-X. Once again, nothing special, it works the exact same way in vanilla DOSBox.

[ssybesma]

Hello Jon,

First...I'll give an overview of problems I ran into:

For some reason the mount command I was using successfully before suddenly gave an error.

I'm not in front of it now...it's very late and I need to sleep.

I suspect that Z: is utterly off limits (or any part of it, even the drivez folder) for mapping to C:

Trouble started when I assumed Z: was writeable. Quickly found it wasn't.

Then I tried to map the drivez folder to C: and that's when this problem started.

I will end up having to uninstall/reinstall DOSBox-X because I truly broke it after screwing with it too much.

I don't blame this on a programming bug.

Second...my ultimate goal:

What I really want to do that would solve all this problem:

I would love to be able to have the DOSBox OS files in the Z: drive and the installed apps folders on the same drive so that it behaves as if it were a real DOS machine with everything on C: drive

As if it were a VMware or Virtualbox DOS VM, in other words.

That may mean I have to somehow mirror unwritable Z: to writable C: then make C: bootable instead of Z:

Is that possible?

Steve Sybesma Brighton, CO

On 2021-09-02 00:17, Jonathan Campbell wrote:

What mount command are you using and what is it expected to do?

Remember that DOSBox-X forked from SVN a long time ago and there's plenty of divergence between the two branches, even though some SVN changes are ported over from time to time.

Perhaps you're relying on recent MOUNT behavior in SVN that DOSBox-X does not yet implement.

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/joncampbell123/dosbox-x/issues/2870#issuecomment-911244439 [2] https://github.com/notifications/unsubscribe-auth/AK7AT2ODVNPEC3XLBAU7ELLT74JGFANCNFSM5DH7SUXQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

[ssybesma]

Thank you Jon...yes I found out and got reminded. Writing to Z: is not allowed.

I outlined my goal in the last email I sent.

Re-installing at this point is no big deal since I just go started with it.

I do however expect mounted drives to be persistent...that was the very last problem I ran into before I threw up my hands in frustration.

Steve Sybesma

On 2021-09-02 00:29, Robert wrote:

Looking at some of your deleted comments. The Z-Drive is read-only and cannot be changed. This is the same with vanilla DOSBox.

DOSBox-X does provide some additional programs on the Z: drive, and there is a way to add your own small programs/utilities, which is documented on the wiki, but it is not meant to install whole applications or games to.

You want to create yourself a C: drive from a directory on your host harddisk drive. e.g.

mount c: c:\dosroot c:

Assuming that your harddisk has a c:\dosroot directory, that directory will now be the virtual C: drive inside DOSBox-X. Once again, nothing special, it works the exact same way in vanilla DOSBox.

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/joncampbell123/dosbox-x/issues/2870#issuecomment-911255347 [2] https://github.com/notifications/unsubscribe-auth/AK7AT2MHJTN4QBCUOWIYKTTT74KTXANCNFSM5DH7SUXQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

[rderooy]

Ohh and your trouble that it no longer finds the 'mount' command is because it is no longer in your PATH environment variable, since you changed the drive letter.

Run the command:

echo %PATH%
Z:\;Z:\SYSTEM;Z:\BIN;Z:\DOS;Z:\4DOS;Z:\Z:\DEBUG;Z:\TEXTUTIL

As you can see in the above example the paths are pointing to the Z: drive only, and the mount command is in the SYSTEM directory, which can no longer be found. So either change the drive back to Z:, or change your PATH to point to the new location.

[rderooy]

If you want to make your mount commands persistent, such that when you restart DOSBox-X later, they are automatically mounted again, you need to add the commands to the [autoexec] section of your DOSBox-X config file.

Find the DOSBox-X conf file, edit it with a text editor and go to the bottom where you will find the [autoexec] section, now add something like this:

[autoexec]
mount c: c:\dosroot
c:

[ssybesma]

I will take some education from your emails and apply to when I redo everything over again.

Unless you know a way I can reset DOSBox-X to initial settings.

Yes, at one point I had made C: the Z: drive and switched back.

Funny though, simple things sometimes slide past me but I figure out how to install a DOS app having 3 disks using the swap.

Steve Sybesma

On 2021-09-02 00:36, Robert wrote:

Ohh and your trouble that it no longer finds the 'mount' command is because it is no longer in your PATH environment variable, since you changed the drive letter.

Run the command:

echo %PATH% Z:\;Z:\SYSTEM;Z:\BIN;Z:\DOS;Z:\4DOS;Z:\Z:\DEBUG;Z:\TEXTUTIL

As you can see in the above example the paths are pointing to the Z: drive only, and the mount command is in the SYSTEM directory, which can no longer be found. So either change the drive back to Z:, or change your PATH to point to the new location.

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/joncampbell123/dosbox-x/issues/2870#issuecomment-911262065 [2] https://github.com/notifications/unsubscribe-auth/AK7AT2PTXJN6BPQ65UYMQN3T74LNXANCNFSM5DH7SUXQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

[ssybesma]

That is actually what I did...I did put the mount command in the *.conf file.

But that didn't work because of something I did wrong probably with the drive letter switch from Z: to C: and back.

However, if you reply to my first email with the ultimate goal in mind, I would really love that.

I ultimately would like the OS and the app install folders on the same (writeable) drive C:

That means copying the contents of Z: to C: and making C: bootable...I think that is allowed.

Thank you!

Steve Sybesma

On 2021-09-02 00:44, Robert wrote:

If you want to make your mount commands persistent, such that when you restart DOSBox-X later, they are automatically mounted again, you need to add the commands to the [autoexec] section of your DOSBox-X config file.

Find the DOSBox-X conf file, edit it with a text editor and go to the bottom where you will find the [autoexec] section, now add something like this:

[autoexec] mount c: c:\dosroot c:

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/joncampbell123/dosbox-x/issues/2870#issuecomment-911270057 [2] https://github.com/notifications/unsubscribe-auth/AK7AT2NWRAXBTFJCGBMYIUTT74MM7ANCNFSM5DH7SUXQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

[rderooy]

The only place where DOSBox-X keeps settings is in the dosbox-x config file, which on windows is normally in the same folder as dosbox-x itself. You can delete the file, then start DOSBox-X, and run the following command to create a new one:

config -wcd

[rderooy]

As to making something bootable, what your thinking of will not work. DOSBox and DOSBox-X don't need you to make a drive bootable.

You can optimally boot (bootable) disk images (floppy or hdd) inside DOSBox-X, but that is only if you have an old 'booter' game, or if for some reason you want to run real MS or PC DOS inside DOSBox-X. Or if you want to try running Windows 95 or 98 inside DOSBox-X. But for normal DOS applications and games you really don't need to go to that hassle.

[ssybesma]

It's trying to put the CONF file under AppData where I really don't want it to be.

So I may just use Revo to get it out completely since I use that to trace the install.

Something got hosed with the default path.

It's puts it there regardless if I choose the C:\DOSBox-X folder where it used to be.

Steve

On 2021-09-02 00:58, Robert wrote:

The only place where DOSBox-X keeps settings is in the dosbox-x config file, which on windows is normally in the same folder as dosbox-x itself. You can delete the file, then start DOSBox-X, and run the following command to create a new one:

config -wcd

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/joncampbell123/dosbox-x/issues/2870#issuecomment-911283374 [2] https://github.com/notifications/unsubscribe-auth/AK7AT2LU4MO7TIP5NEMPOLDT74OAFANCNFSM5DH7SUXQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

[ssybesma]

Jon,

Before I say anything else...I realize nobody works for free, though you did put a lot of free time into this.

I'm convinced DOSBox-X is much better than old DOSBox and it's been a while since I used it.

I make mistakes sometimes because I'm hard-headed and want things to work how they were not intended to.

I intend to help you out a little because of the time you spent.

So I greatly appreciate your help and will let you know when I'm truly in need of help or when I'm just commenting.

You're only one person. Can't do it all.

Steve Sybesma Brighton, CO

On 2021-09-02 01:03, Robert wrote:

As to making something bootable, what your thinking of will not work. DOSBox and DOSBox-X don't need you to make a drive bootable.

You can optimally boot (bootable) disk images (floppy or hdd) inside DOSBox-X, but that is only if you have an old 'booter' game, or if for some reason you want to run real MS or PC DOS inside DOSBox-X. Or if you want to try running Windows 95 or 98 inside DOSBox-X. But for normal DOS applications and games you really don't need to go to that hassle.

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/joncampbell123/dosbox-x/issues/2870#issuecomment-911288817 [2] https://github.com/notifications/unsubscribe-auth/AK7AT2PCJRJ4ABMLD6AOSOLT74OV5ANCNFSM5DH7SUXQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

[ssybesma]

That must be by design...answered my own question.

That's where the new version of the installer put it.

Steve

On 2021-09-02 19:52, @.*** wrote:

It's trying to put the CONF file under AppData where I really don't want it to be.

So I may just use Revo to get it out completely since I use that to trace the install.

Something got hosed with the default path.

It's puts it there regardless if I choose the C:\DOSBox-X folder where it used to be.

Steve

On 2021-09-02 00:58, Robert wrote:

The only place where DOSBox-X keeps settings is in the dosbox-x config file, which on windows is normally in the same folder as dosbox-x itself. You can delete the file, then start DOSBox-X, and run the following command to create a new one:

config -wcd

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/joncampbell123/dosbox-x/issues/2870#issuecomment-911283374 [2] https://github.com/notifications/unsubscribe-auth/AK7AT2LU4MO7TIP5NEMPOLDT74OAFANCNFSM5DH7SUXQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

[ssybesma]

Hello Jon,

I've settled into using DOSBox-X as it was intended to be used.

I am having a problem with the old DOS game SimCity in the three versions it was released for DOS.

Edge Scrolling (that is the screen scrolls when the cursor is moved to the edge) does not work, but I have found it works in vanilla DOSBox.

So I'm trying a lot of things with differences between the DOSBox-X and DOSBox config files to see if I can figure it out.

If you have a notion of what it may be, let me know.

Thanks,

Steve Sybesma Brighton, CO

[joncampbell123]

Are you capturing the mouse (CTRL+F10)?

If the game is polling absolute mouse position, DOSBox-X can directly map the cursor position in the emulator window to the guest.

Can you try enlarging the window with aspect correction, and see if holding the mouse cursor in the black outer area just outside the DOS screen causes scrolling as needed?

[ssybesma]

Hello Jon,

My apologies.

I constructed the last email because nobody replied to the new post on this subject yet (2875).

Yes, that I am doing. The mouse is locked in the screen until I do Ctrl+F10 again.

I found that vanilla DOSBox does that so I figure that has to be done to make it work.

I have to find out how to enlarge window with aspect correction.

That could be the ticket.

Thank you Jon!!!

Please tell me how to donate to your work!

Steve Sybesma

On 2021-09-04 01:13, Jonathan Campbell wrote:

Are you capturing the mouse (CTRL+F10)?

If the game is polling absolute mouse position, DOSBox-X can directly map the cursor position in the emulator window to the guest.

Can you try enlarging the window with aspect correction, and see if holding the mouse cursor in the black outer area just outside the DOS screen causes scrolling as needed?

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/joncampbell123/dosbox-x/issues/2870#issuecomment-912924893 [2] https://github.com/notifications/unsubscribe-auth/AK7AT2LTM33FWIUQHS43GGDUAHBKHANCNFSM5DH7SUXQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

[ssybesma]

Hello Jon,

If Aspect under Render is what you refer to for aspect correction, I have a copy of vanilla DOSBox where edge scrolling works when that is set to False, so I have it that way. That makes me think it's not the 'belly button' I'm looking for.

Tough one.

Steve Sybesma

On 2021-09-04 01:39, @.*** wrote:

Hello Jon,

My apologies.

I constructed the last email because nobody replied to the new post on this subject yet (2875).

Yes, that I am doing. The mouse is locked in the screen until I do Ctrl+F10 again.

I found that vanilla DOSBox does that so I figure that has to be done to make it work.

I have to find out how to enlarge window with aspect correction.

That could be the ticket.

Thank you Jon!!!

Please tell me how to donate to your work!

Steve Sybesma

On 2021-09-04 01:13, Jonathan Campbell wrote:

Are you capturing the mouse (CTRL+F10)?

If the game is polling absolute mouse position, DOSBox-X can directly map the cursor position in the emulator window to the guest.

Can you try enlarging the window with aspect correction, and see if holding the mouse cursor in the black outer area just outside the DOS screen causes scrolling as needed?

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/joncampbell123/dosbox-x/issues/2870#issuecomment-912924893 [2] https://github.com/notifications/unsubscribe-auth/AK7AT2LTM33FWIUQHS43GGDUAHBKHANCNFSM5DH7SUXQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

[ssybesma]

Hello Jon,

Last point...

When I set Aspect=True under Render, the window size doesn't change at all, so has to be something else.

Unless you're thinking of another way to do that.

Another thing I noticed, DOSBox does not have a black border around the game window at all but edge scrolling still works.

Steve Sybesma

On 2021-09-04 01:50, @.*** wrote:

Hello Jon,

If Aspect under Render is what you refer to for aspect correction, I have a copy of vanilla DOSBox where edge scrolling works when that is set to False, so I have it that way. That makes me think it's not the 'belly button' I'm looking for.

Tough one.

Steve Sybesma

On 2021-09-04 01:39, @.*** wrote:

Hello Jon,

My apologies.

I constructed the last email because nobody replied to the new post on this subject yet (2875).

Yes, that I am doing. The mouse is locked in the screen until I do Ctrl+F10 again.

I found that vanilla DOSBox does that so I figure that has to be done to make it work.

I have to find out how to enlarge window with aspect correction.

That could be the ticket.

Thank you Jon!!!

Please tell me how to donate to your work!

Steve Sybesma

On 2021-09-04 01:13, Jonathan Campbell wrote:

Are you capturing the mouse (CTRL+F10)?

If the game is polling absolute mouse position, DOSBox-X can directly map the cursor position in the emulator window to the guest.

Can you try enlarging the window with aspect correction, and see if holding the mouse cursor in the black outer area just outside the DOS screen causes scrolling as needed?

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/joncampbell123/dosbox-x/issues/2870#issuecomment-912924893 [2] https://github.com/notifications/unsubscribe-auth/AK7AT2LTM33FWIUQHS43GGDUAHBKHANCNFSM5DH7SUXQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

[joncampbell123]

aspect=true instructs DOSBox-X to maintain the aspect ratio.

You should be able to resize the main window, and when doing so, the screen should retain it's aspect ratio within the window.

DOSBox-X is the only fork I'm aware of where the window is resizeable, rather than just the fixed size set by the emulator.

I'm sorry for the lack of response, my professional work takes higher priority at this time. I'm being asked to improve video/audio recording functions of the software I work on at work so clients can record more of the high definition video they work with all the time. Nobody wants to record plain MPEG files anymore, and nobody likes TS files when they do live Zoom meetings because Adobe Premiere doesn't handle the recordings that well, so, rewrite in progress.

I have a Patreon account here: https://www.patreon.com/thegreatcodeholio

[ssybesma]

OK, that appears not to work. DOSBox uses False in any case for Aspect= setting.

My last idea I'm about to try is simply to temporarily use the CONF file from DOSBox where we know edge scrolling DOES work. If that is not the solution, then it has to do with the program possibly...have not thought of any other ideas yet.

I totally understand about your time...paid jobs maintains the roof, keeps you fed and clothed and this doesn't.

I don't expect anyone to work for free.

I will happily donate to your Patreon site, and when you have time later among all the other people asking for help, you may choose to revisit this at your convenience. It's an interesting problem.

Thank you Jon!

Steve Sybesma

On 2021-09-04 10:53, Jonathan Campbell wrote:

aspect=true instructs DOSBox-X to maintain the aspect ratio.

You should be able to resize the main window, and when doing so, the screen should retain it's aspect ratio within the window.

DOSBox-X is the only fork I'm aware of where the window is resizeable, rather than just the fixed size set by the emulator.

I'm sorry for the lack of response, my professional work takes higher priority at this time. I'm being asked to improve video/audio recording functions of the software I work on at work so clients can record more of the high definition video they work with all the time. Nobody wants to record plain MPEG files anymore, and nobody likes TS files when they do live Zoom meetings because Adobe Premiere doesn't handle the recordings that well, so, rewrite in progress.

I have a Patreon account here: https://www.patreon.com/thegreatcodeholio

-- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].

Links:

[1] https://github.com/joncampbell123/dosbox-x/issues/2870#issuecomment-913004280 [2] https://github.com/notifications/unsubscribe-auth/AK7AT2I5Z77JS4AQM5CKIXDUAJFG7ANCNFSM5DH7SUXQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub