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

SimFarm: Cannot save game, "Not enough disk space free" #3419

Closed
2 tasks done
driver1998 opened this issue Apr 18, 2022 · 4 comments
Closed
2 tasks done

SimFarm: Cannot save game, "Not enough disk space free" #3419

driver1998 opened this issue Apr 18, 2022 · 4 comments
Labels

Comments

@driver1998
Copy link
Contributor

driver1998 commented Apr 18, 2022

Code of Conduct & Contributing Guidelines

  • I agree to follow the code of conduct and the contributing guidelines.

Have you checked that no other similar bug report(s) already exists?

  • I have searched and didn't find any similar issues.

What operating system(s) this bug have occurred on?

Windows 10 19044 x64, Windows 11 Insider 22598 ARM64

What version(s) of DOSBox-X have this bug?

after 0.83.0, only tested MSVC x64 and ARM64 builds

Describe the bug

Start a game and try to save, the game reports "Not enough disk space free".
simfarm_000

This is broken since 0.83.0 (0.83.0 itself works), I have only tested MSVC x64 and ARM64 releases.

Expected behavior

It should save correctly.
simfarm_000

Steps to reproduce the behaviour

  1. Install the game from disk images on archive.org: https://archive.org/details/000543-Simfarm. Install target (C:) is mounted as folder.
  2. Start a new game
  3. Try to save

Used configuration

No response

Emulator log

No response

Additional context

No response

@driver1998 driver1998 added the bug label Apr 18, 2022
@rderooy
Copy link
Contributor

rderooy commented Apr 18, 2022

Try limiting the amount of disk space reported by using the -freesize option during mount.

e.g.,

mount c . -freesize 32

The above command will mount the current working directory as the C: and report a maximum of 32MB of free space.

@driver1998
Copy link
Contributor Author

It does work after limiting the disk space, so I guess this is some overflow happened in the game then.
Why it worked in 0.83.0 (and normal DOSBox 0.72) though...

@driver1998
Copy link
Contributor Author

Looks like it is limited to 256MB before, and unlimited by default now, so this is expected.
Closing the issue.

@rderooy
Copy link
Contributor

rderooy commented Apr 18, 2022

Some DOS programs can handle larger disk sizes then others. But your right in that some kind of overflow most likely happens.

For late era dos programs 256 free is not enough, and for early programs it can already be too much. So there is not a golden setting.

Another thing that DOSBox-X handles a little different is that in regular DOSBox you always have 256MB available, even if you create new files and there is not actually that much disk space available on the drive (disk full or nearly full). While in DOSBox-X it will take the actual available disk space into account, so if you specify -freesize 256 and there is actually only 100MiB available, you will see 100MiB free, not 256.

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

No branches or pull requests

2 participants