Skip to content
This repository was archived by the owner on Aug 23, 2025. It is now read-only.

Commit 1fafe0f

Browse files
authored
Update README.md
1 parent e630467 commit 1fafe0f

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

README.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,23 +17,21 @@ Same as for 86Box. Additionally, the following is required:
1717
* 86Box build 1799 or later (earlier builds don't support all the features the Manager expects)
1818
* .NET Framework 4.0
1919

20-
## How to use
20+
## Support
21+
If you have any issues, questions, suggestions, etc., please follow the [troubleshooting steps](https://github.com/86Box/86BoxManager/wiki/Troubleshooting-steps) or visit the official 86Box support channels on IRC and Discord (see the main 86Box repo for links). Lead developer, daviunic, is often idling there under the name Overdoze.
2122

23+
## How to use
2224
1. Download the desired build [here](https://github.com/86Box/86BoxManager/releases)
2325
2. Run `86Manager.exe`
2426
3. Choose the folder where `86Box.exe` is located (along with the roms folder) and a folder where your virtual machines will be located (for configs, nvr folders, etc.)
2527
4. Start creating new virtual machines and enjoy
2628

2729
## How to build
28-
2930
1. Clone the repo
3031
2. Open `86BoxManager.sln` solution file in Visual Studio 2017
3132
3. Make your changes
3233
4. Choose the `Release` configuration and `x86` platform/CPU
3334
5. Build the solution
3435
6. `86Manager.exe` is now in `Bin\x86\Release\`
3536

36-
Please see the wiki section for additional information for contributors.
3737

38-
## Support
39-
If you have any issues, questions, suggestions, etc., please follow the [troubleshooting steps](https://github.com/86Box/86BoxManager/wiki/Troubleshooting-steps) or visit the official 86Box support channels on IRC and Discord (see the main 86Box repo for links). Lead developer, daviunic, is often idling there under the name Overdoze.

0 commit comments

Comments
 (0)