Easy - you use a different manager. WinBox messes directly with 86Box's internals and due to the fact it hasn't been updated in over 2 years now, it's been causing numerous problems, misleading people to believe they're actually bugs in 86Box itself.

Battler wrote on 2024-08-06, 18:17:

Easy - you use a different manager

Turns out it's not that easy. Can't seem to find any other manager for Windows...

What's the last line in the message?

Imgema wrote on 2025-01-03, 15:50:

Battler wrote on 2024-08-06, 18:17:

Easy - you use a different manager

Turns out it's not that easy. Can't seem to find any other manager for Windows...

What about 86Box Manager (https://github.com/86Box/86BoxManager)? Using that one myself.

86Box Manager is good. I used to use it too.

But now stopped using front-ends altogether. Using direct shortcuts with the --vmpath parameter. And I have created shortcuts on my desktop for the "systems" I use most often :

I'm using Debian as my main OS, but this should be easier for Windows users too.

Malik wrote on 2025-01-10, 03:22:

86Box Manager is good. I used to use it too.

But now stopped using front-ends altogether. Using direct shortcuts with the --vmpath parameter. And I have created shortcuts on my desktop for the "systems" I use most often :

I'm using Debian as my main OS, but this should be easier for Windows users too.

Hi,

I didn't find vmpath parameter in 86box help? It's a specific command line parameter for Linux?

Thanks

nico7550 wrote on 2025-02-06, 07:13:

Hi, […]
Show full quote

Malik wrote on 2025-01-10, 03:22:

86Box Manager is good. I used to use it too.

But now stopped using front-ends altogether. Using direct shortcuts with the --vmpath parameter. And I have created shortcuts on my desktop for the "systems" I use most often :

I'm using Debian as my main OS, but this should be easier for Windows users too.

Hi,

I didn't find vmpath parameter in 86box help? It's a specific command line parameter for Linux?

Thanks

The parameter should work in Windows too.

The first configuration made with 86Box will create a directory of the machine under the directory called VMS.
For example, if the 86box executable is in c:\86box, then the saved machine settings, say, a 386SX, would be saved in c:\86box\vms\386sx. (This last directory will be named by 86box based on the nvr/bios). The 86box.cfg will be saved on the path with the executable. Copy this cfg file into the 386sx directory.

To run this system directly, you would have to enter -> 86box --vmpath vms\386sx.

You can make many copies of the said 386sx directory and rename them each, like, Pentium, 486, etc.

Then you can run 86box --vmpath vms\486 or,
86box --vmpath vms\Pentium , etc.

So let's say you choose 486, the settings will still be from 386sx, but any change you made will be saved under the 486 directory. So by this, you can save and load multiple machine configurations, by running them individually.

nico7550 wrote on 2025-02-06, 07:13:

Hi, […]
Show full quote

Malik wrote on 2025-01-10, 03:22:

86Box Manager is good. I used to use it too.

But now stopped using front-ends altogether. Using direct shortcuts with the --vmpath parameter. And I have created shortcuts on my desktop for the "systems" I use most often :

I'm using Debian as my main OS, but this should be easier for Windows users too.

Hi,

I didn't find vmpath parameter in 86box help? It's a specific command line parameter for Linux?

Thanks

It's there on Windows as well, also known as -P - I personally use the short form.