fix(mingw): Version upgrade caused this to error

HRESULT not defined fixed by including windows header
refactor(dist): Config and .bat files
2026-09-15 03:45:09 -05:00 · 2024-02-25 09:30:53 +01:00 · 2024-02-25 09:30:53 +01:00 · 2024-02-25 09:30:53 +01:00 · 2024-02-25 09:30:53 +01:00 · 2024-02-25 09:30:53 +01:00
596 changed files with 15294 additions and 5291 deletions
--- a/.github/ISSUE_TEMPLATE/bug.md
+++ b/.github/ISSUE_TEMPLATE/bug.md
@@ -22,10 +22,11 @@ necessary -->
 <!-- Try running the game with a default configuration as well. If that also causes issues, please point that out here in the report. This might speed up the debugging process.-->

 <!--- Provide a detailed step by step description how to reproduce this issue -->
+
+1.
+1.
+1.
 1.
-2.
-3.
-4.

 ## Possible solution

@@ -35,11 +36,11 @@ necessary -->

 ### Bemanitools version(s) affected

-* <!--- Add one or multiple versions as a bullet list -->
+- <!--- Add one or multiple versions as a bullet list -->

 ### Game(s) and version(s) affected

-* <!--- Add one or multiple game versions as a bullet list -->
+- <!--- Add one or multiple game versions as a bullet list -->

 ### Log output

@@ -88,7 +89,7 @@ used if you altered it. -->

 ### APIs used

-* <!--- List all APIs you used as a bullet list, e.g. iidxio-keyboard, eamio-keyboard -->
+- <!--- List all APIs you used as a bullet list, e.g. iidxio-keyboard, eamio-keyboard -->

 ### OS version

@@ -96,7 +97,7 @@ used if you altered it. -->

 ### Hardware specs

-* CPU: <!--- Insert, e.g. Core i7 2600k 3.20ghz -->
-* RAM: <!--- Insert, e.g. 16 GB -->
-* GPU: <!--- Insert, e.g. Nvidia GeForce GTX 970, 4GB -->
-* Controllers/IO: <!--- Insert, e.g. DJ Dao RE over USB -->
+- CPU: <!--- Insert, e.g. Core i7 2600k 3.20ghz -->
+- RAM: <!--- Insert, e.g. 16 GB -->
+- GPU: <!--- Insert, e.g. Nvidia GeForce GTX 970, 4GB -->
+- Controllers/IO: <!--- Insert, e.g. DJ Dao RE over USB -->
--- a/.github/ISSUE_TEMPLATE/feature.md
+++ b/.github/ISSUE_TEMPLATE/feature.md
@@ -18,4 +18,4 @@

 ## Current blockers

-<!--- Describe any blockers that need to be resolved before implementing this feature -->
+<!--- Describe any blockers that need to be resolved before implementing this feature -->
--- a/.github/PULL_REQUEST_TEMPLATE/pull-request.md
+++ b/.github/PULL_REQUEST_TEMPLATE/pull-request.md
@@ -11,25 +11,31 @@
 ## Related Issue

 <!--- This project only accepts pull requests related to open issues -->
+
 <!--- If suggesting a new feature or change, please discuss it in an issue first -->
+
 <!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
+
 <!--- Please link to the issue here: -->

 ## How Has This Been Tested?

 <!--- Please describe in detail how you tested your changes. -->
+
 <!--- Include details of your testing environment, and the tests you ran to -->
+
 <!--- see how your change affects other areas of the code, etc. -->

 ## Checklist

 <!-- Make sure you covered all items, which apply, of the checklist below. -->
+
 <!-- Strikethrough items that do not apply and provide a brief description why. -->

-* [ ] Implemented (unit) test(s) which prove that the introduced changes are working as expected.
-* Tested with the following games:
-    * [ ] ... <!-- insert game name 1-->
-    * [ ] ... <!-- insert game name 2--->
-* [ ] Followed the developer (style) guidelines.
-* [ ] Updated existing doc of or add new doc to README file(s).
-* [ ] Updated development documentation.
+- \[ \] Implemented (unit) test(s) which prove that the introduced changes are working as expected.
+- Tested with the following games:
+  - \[ \] ... <!-- insert game name 1-->
+  - \[ \] ... \<!-- insert game name 2--->
+- \[ \] Followed the developer (style) guidelines.
+- \[ \] Updated existing doc of or add new doc to README file(s).
+- \[ \] Updated development documentation.
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,342 +1,420 @@
 # Release history
+
 Note for CI/CD: Ensure the version formatting in the sections is kept identical to the versions
 given in tags. The pipeline will pick this up and cuts out the relevant section for release notes.

-## 5.46
+## 5.49
+
 ### Features
-* feat(ddrio): Wrapper/shim library to drive another ddrio in a dedicated IO thread. Improves performance for highly IO
-  bound ddrio implementations, e.g. ddrio-p3io
-* feat(iidxiotest): bi2a-iidx support

 ### Fixes
-* fix(jb03/04): Missing XML in gamestart script
-* fix(jbhook1): Rotate error message box when screen is rotated
-* fix(jbhook1): Improve/fix automatic config/nvram fs initialization
+
+## 5.48
+
+### Features
+
+- feat(config): Add invert analog input option. Remark: The old configuration file format is
+  upgraded but downgrading is not possible anymore. The new saves are using a new filename and it
+  doesn't delete the old files, see `C:\Users\<YOUR_USERNAME>\AppData\Roaming\DJHACKERS`
+
+### Fixes
+
+## 5.47
+
+### Features
+
+N/A
+
+### Fixes
+
+- fix(ddr/p3ioemu): Handle unknown 2B command to fix DDR X IO errors
+- fix(ddr/p3io): Crash on all supported DDR games due to incorrect p3io message size validation
+- fix(geninput): Sony DualShock 4 not working
+
+## 5.46
+
+### Features
+
+- feat(ddrio): Wrapper/shim library to drive another ddrio in a dedicated IO thread. Improves
+  performance for highly IO bound ddrio implementations, e.g. ddrio-p3io
+- feat(iidxiotest): bi2a-iidx support
+
+### Fixes
+
+- fix(jb03/04): Missing XML in gamestart script
+- fix(jbhook1): Rotate error message box when screen is rotated
+- fix(jbhook1): Improve/fix automatic config/nvram fs initialization

 ## 5.45
+
 ### Features
-* feat(iidx 30): Added support
-* feat(ddr): Add ddrio implementation with P3IO driver backend
-* feat(ddr): Add p3io-ddr-tool for testing/debugging real P3IO devices with EXTIO
-* feat(ddr): Add testing tool for real EXTIO devices
-* feat(ddr): Add extio driver
-* feat(ddr): Add p3io driver
-* feat(iidx 20-26): New/fixed gfx up-/downscaling feature, old one was broken
-* feat(ddr): Vigem driver for ddrio
-* feat(iidx 25-30): The user can now set a custom camera device override of "SKIP" to leave that camera unassigned
+
+- feat(iidx 30): Added support
+- feat(ddr): Add ddrio implementation with P3IO driver backend
+- feat(ddr): Add p3io-ddr-tool for testing/debugging real P3IO devices with EXTIO
+- feat(ddr): Add testing tool for real EXTIO devices
+- feat(ddr): Add extio driver
+- feat(ddr): Add p3io driver
+- feat(iidx 20-26): New/fixed gfx up-/downscaling feature, old one was broken
+- feat(ddr): Vigem driver for ddrio
+- feat(iidx 25-30): The user can now set a custom camera device override of "SKIP" to leave that
+  camera unassigned

 ### Fixes
-* fix(iidx 09/10): Fix stretched BGAs on 1st and 3rd style videos
+
+- fix(iidx 09/10): Fix stretched BGAs on 1st and 3rd style videos

 ## 5.44
+
 ### Features
-* feat(doc): ezusb dev journal entry, 10th style ezusb boot up and security setup
-* feat(iidx 09/10): ezusb API call monitoring module and configuration flag
-* feat(iidx 19): Add back btools monitor check for iidxhook5
-* feat(iidx 9-19): Add configurable settings path hook. Redirect settings paths, i.e. `d/`, `e/` and
+
+- feat(doc): ezusb dev journal entry, 10th style ezusb boot up and security setup
+- feat(iidx 09/10): ezusb API call monitoring module and configuration flag
+- feat(iidx 19): Add back btools monitor check for iidxhook5
+- feat(iidx 9-19): Add configurable settings path hook. Redirect settings paths, i.e. `d/`, `e/` and
  `f/` drive "folders" to an arbitrary path on any partition, e.g. writable partition
-* feat(iidx 9/10): Improve commandline script for irbeat-patch 09 and 10, add interactive mode
+- feat(iidx 9/10): Improve commandline script for irbeat-patch 09 and 10, add interactive mode

 ### Fixes
-* fix(iidx 10): SQ-INIT error caused by incorrect security configuration
-* fix(iidx 9-24): Wire up coin input in ezusb1/2 IO emulation layer
-* fix(pnm 15-18): Fix IO buffer inconsistency causing random input misfiring
-* fix(jb 1-8): Fix IO buffer inconsistency causing random input misfiring
-* fix(iidx 9-24): Fix IO buffer inconsistency causing random input misfiring
-* fix(iidx 19): imagefs override strategy with local file redir. Required to enable monitor-check
-  on all chart files
-* fix(iidx 9-19): Code synchronization issue causing deadlock resulting in game hang/stuck on boot
-* fix(iidx 9-19): Fix broken settings path handling with mixed / and \
-* fix(iidx 27): Align disabled cam connection config defaults with 28/29
-* fix(inject): Fix missing forwarding of exit code
-* fix(inject): Getting stuck when game exits cleanly due to locked up debugger thread.
-* fix(iidx 18/19 CN): gamestart.bat creating dev/nvram and dev/raw folders
+
+- fix(iidx 10): SQ-INIT error caused by incorrect security configuration
+- fix(iidx 9-24): Wire up coin input in ezusb1/2 IO emulation layer
+- fix(pnm 15-18): Fix IO buffer inconsistency causing random input misfiring
+- fix(jb 1-8): Fix IO buffer inconsistency causing random input misfiring
+- fix(iidx 9-24): Fix IO buffer inconsistency causing random input misfiring
+- fix(iidx 19): imagefs override strategy with local file redir. Required to enable monitor-check on
+  all chart files
+- fix(iidx 9-19): Code synchronization issue causing deadlock resulting in game hang/stuck on boot
+- fix(iidx 9-19): Fix broken settings path handling with mixed / and \\
+- fix(iidx 27): Align disabled cam connection config defaults with 28/29
+- fix(inject): Fix missing forwarding of exit code
+- fix(inject): Getting stuck when game exits cleanly due to locked up debugger thread.
+- fix(iidx 18/19 CN): gamestart.bat creating dev/nvram and dev/raw folders

 ## 5.43
-* iidx29: (Officially) support IIDX CASTHOUR
-* Code structure maintenance
-* Various documentation improvements
+
+- iidx29: (Officially) support IIDX CASTHOUR
+- Code structure maintenance
+- Various documentation improvements

 ## 5.42
-* Bugfix: Fix diagonal texture tearing on IIDX 18 and 19 based games
-* Feature: Add support for IIDX Resort Anthem CN using iidxhook4-cn 
-* Feature/bugfix: Enable "nvidia fix" for iidxhook4, 5 and 5-cn. Should fix crashing on some/all
+
+- Bugfix: Fix diagonal texture tearing on IIDX 18 and 19 based games
+- Feature: Add support for IIDX Resort Anthem CN using iidxhook4-cn
+- Feature/bugfix: Enable "nvidia fix" for iidxhook4, 5 and 5-cn. Should fix crashing on some/all
  nvidia cards
-* Various minor fixes
+- Various minor fixes

 ## 5.41
-* Feature: Support pop'n music 15-18 using popnhook1
-* Feature: Support IIDX tricoro CN using iidxhook5-cn
-* Various documentation improvements
+
+- Feature: Support pop'n music 15-18 using popnhook1
+- Feature: Support IIDX tricoro CN using iidxhook5-cn
+- Various documentation improvements

 ## 5.40
-* Feature: Support DDR X and X2 US/EU using ddrhook1 including memory card emulation
-* Fix: sdvxhook2 crashing on some OS versions
-* Feature: Support sdvx generator lights in sdvxio
+
+- Feature: Support DDR X and X2 US/EU using ddrhook1 including memory card emulation
+- Fix: sdvxhook2 crashing on some OS versions
+- Feature: Support sdvx generator lights in sdvxio

 ## 5.39
-* jbhook3: Fix window mode, remove window frame option, add show cursor on window option
-* Code simplification and cleanup round plug modules
-* Code structure improvements p3io jubeat
+
+- jbhook3: Fix window mode, remove window frame option, add show cursor on window option
+- Code simplification and cleanup round plug modules
+- Code structure improvements p3io jubeat

 ## 5.38
-* sdvxhook2: Support sound voltex exceed gear
+
+- sdvxhook2: Support sound voltex exceed gear

 ## 5.37
-* jbhook1: Support jubeat (1) and ripples
-* jbhook2: Support jubeat knit and copious
-* jbhook3: Support jubeat saucer, prop, qubell, clan and festo
+
+- jbhook1: Support jubeat (1) and ripples
+- jbhook2: Support jubeat knit and copious
+- jbhook3: Support jubeat saucer, prop, qubell, clan and festo

 ## 5.36
-* iidxhook9: Support for IIDX28
-* Various bugfixes
+
+- iidxhook9: Support for IIDX28
+- Various bugfixes

 ## 5.35
-* Jubeat: Add jbio-p4io
-* Nostalgia: Add nostio-panb
-* Misc: Add wavepass support to aciodrv-icca (and eamio-icca)
-* Misc: Refactor aciodrv to support multiple devices using the same port (with aciomgr)
-* Misc: Fix d3d9ex windowed hook not behaving correctly (size/framed)
-* Misc: Fix docs not being included with release
-* Various bugfixes
+
+- Jubeat: Add jbio-p4io
+- Nostalgia: Add nostio-panb
+- Misc: Add wavepass support to aciodrv-icca (and eamio-icca)
+- Misc: Refactor aciodrv to support multiple devices using the same port (with aciomgr)
+- Misc: Fix d3d9ex windowed hook not behaving correctly (size/framed)
+- Misc: Fix docs not being included with release
+- Various bugfixes

 ## 5.34
-* IIDX: Support IO and card reader feature switches to disable emulation in iidxhook4-7
-* Jubeat: jbio implementation for magicbox hardware
-* Misc: Various documentation improvements
-* IIDX: Turntable multiplier (can also be used as inverted) for iidxhook9
-* IIDX: iidxhook9, add force screen resolution option to fix sometimes wrong auto res detection by
-iidx27 causing inaccurate/wrong refresh rates on monitor check
-* IIDX: iidxio BIO2 implementation -> Use BIO2 hardware with any iidxhook or other software
-supporting BT5's iidxio interface
-* IIDX: BIO2 exit hook, exit the game pressing Start P1 + Start P2, Effect and VEFX
-* launcher: Allow overriding service URL from command line
-* IIDX: vigem-iidxio, tool to allow using iidxio (ezusb, ezusb2 or bio2) to emulate XBOX controllers
-to play other non arcade games that support xinput, e.g. Lunatic Rave (note: Infinitas does not
-work with this since it only supports direct input)
+
+- IIDX: Support IO and card reader feature switches to disable emulation in iidxhook4-7
+- Jubeat: jbio implementation for magicbox hardware
+- Misc: Various documentation improvements
+- IIDX: Turntable multiplier (can also be used as inverted) for iidxhook9
+- IIDX: iidxhook9, add force screen resolution option to fix sometimes wrong auto res detection by
+  iidx27 causing inaccurate/wrong refresh rates on monitor check
+- IIDX: iidxio BIO2 implementation -> Use BIO2 hardware with any iidxhook or other software
+  supporting BT5's iidxio interface
+- IIDX: BIO2 exit hook, exit the game pressing Start P1 + Start P2, Effect and VEFX
+- launcher: Allow overriding service URL from command line
+- IIDX: vigem-iidxio, tool to allow using iidxio (ezusb, ezusb2 or bio2) to emulate XBOX controllers
+  to play other non arcade games that support xinput, e.g. Lunatic Rave (note: Infinitas does not
+  work with this since it only supports direct input)

 ## 5.33
-* iidxhook9: Support for IIDX27 
-* sdvxio-bio2: Driver for real sdvx5 cabinet IO hardware
-* vigem-sdvxio: Tool to allow using sdvxio (kfca or bio2) to emulate an xbox controller
-* Various bugfixes and refactoring for inject and launcher
+
+- iidxhook9: Support for IIDX27
+- sdvxio-bio2: Driver for real sdvx5 cabinet IO hardware
+- vigem-sdvxio: Tool to allow using sdvxio (kfca or bio2) to emulate an xbox controller
+- Various bugfixes and refactoring for inject and launcher

 ## 5.32
-* Various bugfixes
+
+- Various bugfixes

 ## 5.31
-* DDR: Fix p3io and extio lights not working / being swapped when using geninput
-* DDR: Add HDXS light support
-* DDR: Add 64 bit support
-* DDR: Add option to use COM4 as the p3io rs232 port instead of emulating (for use with acrealio etc.)
-* Jubeat: Add network adapter hook
-* Misc: Fix aciodrv sometimes hanging on boot (eamio-icca and sdvxio-kfca) 
+
+- DDR: Fix p3io and extio lights not working / being swapped when using geninput
+- DDR: Add HDXS light support
+- DDR: Add 64 bit support
+- DDR: Add option to use COM4 as the p3io rs232 port instead of emulating (for use with acrealio
+  etc.)
+- Jubeat: Add network adapter hook
+- Misc: Fix aciodrv sometimes hanging on boot (eamio-icca and sdvxio-kfca)

 ## 5.30
-* SDVX: sdvxhook2 headphone force and cursor confining config options
-* DDR: Add light support for SMX gen 4 pads
+
+- SDVX: sdvxhook2 headphone force and cursor confining config options
+- DDR: Add light support for SMX gen 4 pads

 ## 5.29
-* SDVX: Add option for monitor rotation
-* SDVX: Add option to allow overriding network adapter IP
-* IIDX: Add force display adapter and refresh rate configuration
-* SDVX: Allow specifying display adapter to open for d3d9ex hook
-* IIDX/SDVX camerahooks bugfix: Camera sometimes not detected on some older machines
+
+- SDVX: Add option for monitor rotation
+- SDVX: Add option to allow overriding network adapter IP
+- IIDX: Add force display adapter and refresh rate configuration
+- SDVX: Allow specifying display adapter to open for d3d9ex hook
+- IIDX/SDVX camerahooks bugfix: Camera sometimes not detected on some older machines

 ## 5.28
-* Improve documentation in various places
-* Automatic code formatting in build pipeline
-* Bugfix: Recursive config.bat script
-* Enable automatic building on pushes to master
-* Bugfix: Stop SDVX hanging on thankyou for playing
-* sdvx2: Support for Vivid Wave using sdvxhook2
-* sdvxio-kfca: Driver for real sdvx cabinet IO hardware
+
+- Improve documentation in various places
+- Automatic code formatting in build pipeline
+- Bugfix: Recursive config.bat script
+- Enable automatic building on pushes to master
+- Bugfix: Stop SDVX hanging on thankyou for playing
+- sdvx2: Support for Vivid Wave using sdvxhook2
+- sdvxio-kfca: Driver for real sdvx cabinet IO hardware

 ## 5.27
-* Various documentation updates regarding development and how to contribute
-* KFCA emulation accuracy fixes
-* Fix passthrough of serial calls when using real hardware (e.g. card reader passthrough IIDX25+/SDVX5+)
-* Add sdvxio-kfca driver to talk to real SDVX hardware
-* Refactor d3d9 hook module to improve maintainability. Also fixes upscaling not working on IIDX20+.
-* Remove d3d8 hook module to improve maintainability. Make old d3d8 based games, e.g. iidxhook1/2, use d3d9 instead.
-Requires usage of d3d8to9 wrapper library to use gfx patching features.
-* Add dev doc about IIDX rendering loops
-* Add an initial draft of an architecture document (will be worked on in iterations)
-* Refactor BIO2 emulation to make it re-usable by other games
+
+- Various documentation updates regarding development and how to contribute
+- KFCA emulation accuracy fixes
+- Fix passthrough of serial calls when using real hardware (e.g. card reader passthrough
+  IIDX25+/SDVX5+)
+- Add sdvxio-kfca driver to talk to real SDVX hardware
+- Refactor d3d9 hook module to improve maintainability. Also fixes upscaling not working on IIDX20+.
+- Remove d3d8 hook module to improve maintainability. Make old d3d8 based games, e.g. iidxhook1/2,
+  use d3d9 instead. Requires usage of d3d8to9 wrapper library to use gfx patching features.
+- Add dev doc about IIDX rendering loops
+- Add an initial draft of an architecture document (will be worked on in iterations)
+- Refactor BIO2 emulation to make it re-usable by other games

 ## 5.26
-* iidxio-ezusb: Reduce sleep time to Sleep(1) to avoid framerate issues on some versions of iidx.
-* Bugfix: iidx d3d9 games, mainly the newer ones iidx 20-25, freezing. Happened on boot, during song selection or during the song.
-* Bugfix: log_server_init deadlock on iidxhook4-7. This caused games like iidx24 to hang before even showing a render window.
-* iidxhook: Add feature to allow GPU based up-/downscaling of rendered frame. This gives
-you the possibility to upscale the resolution of old SD (640x480) games to your monitor's/TV's
-native resolution which can have a few advantages: better image quality if the monitor's upscaler
-is not doing a good job, especially on resolutions that are not a multiple of its native resolution;
-Reduce display latency if the upscaler is slow, avoid over-/underscan which cannot always be fixed
-entirely or at all (depending on your GPU and monitor model). See the iidxhook configuration file
-for the new parameters available.
-* Major readme cleanup. Add development documentation like style guide, guidelines, development setup.
+
+- iidxio-ezusb: Reduce sleep time to Sleep(1) to avoid framerate issues on some versions of iidx.
+- Bugfix: iidx d3d9 games, mainly the newer ones iidx 20-25, freezing. Happened on boot, during song
+  selection or during the song.
+- Bugfix: log_server_init deadlock on iidxhook4-7. This caused games like iidx24 to hang before even
+  showing a render window.
+- iidxhook: Add feature to allow GPU based up-/downscaling of rendered frame. This gives you the
+  possibility to upscale the resolution of old SD (640x480) games to your monitor's/TV's native
+  resolution which can have a few advantages: better image quality if the monitor's upscaler is not
+  doing a good job, especially on resolutions that are not a multiple of its native resolution;
+  Reduce display latency if the upscaler is slow, avoid over-/underscan which cannot always be fixed
+  entirely or at all (depending on your GPU and monitor model). See the iidxhook configuration file
+  for the new parameters available.
+- Major readme cleanup. Add development documentation like style guide, guidelines, development
+  setup.

 ## 5.25
-* Bugfix: iidx14 and 15 crashing on Windows 10
-* Bugfix: IO2 driver not using correct package sizes on reads/write -> iidxio-ezusb2.dll now working
-* Improve ezusb2-boot.bat script to handle flashing of IO2 firmware
-* Remove broken x64 builds of ezusb1/2 tools -> Just use the x86 tool versions instead
-(use the x64 versions of iidxio-ezusb.dll and iidxio-ezusb2.dll with iidx25)
-* iidxhook1-8: Allow floating point values for frame rate limiting, e.g. 59.95 (hz).
-* Improve timing with ezusb (C02) driver
+
+- Bugfix: iidx14 and 15 crashing on Windows 10
+- Bugfix: IO2 driver not using correct package sizes on reads/write -> iidxio-ezusb2.dll now working
+- Improve ezusb2-boot.bat script to handle flashing of IO2 firmware
+- Remove broken x64 builds of ezusb1/2 tools -> Just use the x86 tool versions instead (use the x64
+  versions of iidxio-ezusb.dll and iidxio-ezusb2.dll with iidx25)
+- iidxhook1-8: Allow floating point values for frame rate limiting, e.g. 59.95 (hz).
+- Improve timing with ezusb (C02) driver

 ## v5.24
-* Bugfix: iidxhook8 hangs very early on startup (race condition in log-server module)
+
+- Bugfix: iidxhook8 hangs very early on startup (race condition in log-server module)

 ## v5.23
-* Refactored configurion (file) handling for iidxhooks, RE-READ THE DOCUMENTATION.
-This gets rid of the "short cmd parameters", e.g. -w for windowed mode, and replaces
-them with full name parameters, e.g. -p gfx.windowed=true, which improves handling
-of configuration files/values. 
-* Add a lot of unit tests to the codebase
-* Refactored round plug security infrastructure, shared with IIDX and jubeat (1)
-* Move shared utility modules between iidxhook modules to a separate utilty module 'iidxhook-util'
-* Add experimental jubeat (1) support (buggy IO emulation) 
-* Various fixes to improve all iidxhooks when running on Windows 10
-* Bugfix: iidxio-ezusb getting stuck on newer Windows platforms
-* Update iidxhook docs, e.g. how to get old IIDX versions sync on Windows 10
-* Various documentation updates
-* Various code cleanup
-* Various other minor bugfixes
+
+- Refactored configurion (file) handling for iidxhooks, RE-READ THE DOCUMENTATION. This gets rid of
+  the "short cmd parameters", e.g. -w for windowed mode, and replaces them with full name
+  parameters, e.g. -p gfx.windowed=true, which improves handling of configuration files/values.
+- Add a lot of unit tests to the codebase
+- Refactored round plug security infrastructure, shared with IIDX and jubeat (1)
+- Move shared utility modules between iidxhook modules to a separate utilty module 'iidxhook-util'
+- Add experimental jubeat (1) support (buggy IO emulation)
+- Various fixes to improve all iidxhooks when running on Windows 10
+- Bugfix: iidxio-ezusb getting stuck on newer Windows platforms
+- Update iidxhook docs, e.g. how to get old IIDX versions sync on Windows 10
+- Various documentation updates
+- Various code cleanup
+- Various other minor bugfixes

 ## v5.22
-* Added a lot of documentation and readme stuff (READ IT!!11)
-* Re-numbering iidxhook implementations to make room for missing games
-* Support for IIDX 18 -> iidxhook4
-* Support for IIDX 19 -> iidxhook5
-* Support for IIDX 20 -> iidxhook6
-* A lot of code refactoring and cleanup
-* Refactor p3io emulation
-* Remove obsolete BT4 DDR stuff
-* iidxhook: Refactored software monitor check and bugfixes. You can use the
-auto monitor check to determine your machine's refresh rate or (new) set the
-refresh rate yourself in the configuration file, e.g. when you already have
-determined it using one of the newer IIDX games and want to skip that monitor
-check or if BT5's software monitor check doesn't work properly (e.g. on Win 7).
-* iidxhook1-3: Check if eamuse server is reachable and log a warning otherwise.
-This should make debugging invalid URLs or connection issues easier.
-* iidxhook: Revised ezusb and ezusb2 emulation layer. Translucent support
-removed, all IO emulation goes through BT5's iidxio interface.
-* iidxio: Add implementations for ezusb (C02 IO) and ezusb2 (IO2) hardware. This
-allows you to run _ANY_ IIDX game supported by BT5 either with real C02 or IO2
-hardware.
-* iidxhook: Remove translucent card reader feature. Again, to create a unified
-interface for _ALL_ versions, use the eamio-icca.dll if you want to run on 
-real ICCA (slotted or wavepass) readers. 
-* Various other bugfixes

-Again, read the various markdown (.md) readme files. We tried to document
-everything to the best of our knowledge. If you are missing something, please
-contribute by adding that information and submitting a patch to us.
+- Added a lot of documentation and readme stuff (READ IT!!11)
+- Re-numbering iidxhook implementations to make room for missing games
+- Support for IIDX 18 -> iidxhook4
+- Support for IIDX 19 -> iidxhook5
+- Support for IIDX 20 -> iidxhook6
+- A lot of code refactoring and cleanup
+- Refactor p3io emulation
+- Remove obsolete BT4 DDR stuff
+- iidxhook: Refactored software monitor check and bugfixes. You can use the auto monitor check to
+  determine your machine's refresh rate or (new) set the refresh rate yourself in the configuration
+  file, e.g. when you already have determined it using one of the newer IIDX games and want to skip
+  that monitor check or if BT5's software monitor check doesn't work properly (e.g. on Win 7).
+- iidxhook1-3: Check if eamuse server is reachable and log a warning otherwise. This should make
+  debugging invalid URLs or connection issues easier.
+- iidxhook: Revised ezusb and ezusb2 emulation layer. Translucent support removed, all IO emulation
+  goes through BT5's iidxio interface.
+- iidxio: Add implementations for ezusb (C02 IO) and ezusb2 (IO2) hardware. This allows you to run
+  _ANY_ IIDX game supported by BT5 either with real C02 or IO2 hardware.
+- iidxhook: Remove translucent card reader feature. Again, to create a unified interface for _ALL_
+  versions, use the eamio-icca.dll if you want to run on real ICCA (slotted or wavepass) readers.
+- Various other bugfixes
+
+Again, read the various markdown (.md) readme files. We tried to document everything to the best of
+our knowledge. If you are missing something, please contribute by adding that information and
+submitting a patch to us.

 ## v5.21
-* Camera hook for IIDX 25 (use any UVC webcam in-game), by Xyen
-* *deep breath* Source code release
+
+- Camera hook for IIDX 25 (use any UVC webcam in-game), by Xyen
+- *deep breath* Source code release

 ## v5.20
-* Support for the new IIDX 25 IO board (xyen)
-* New IO hook system with better multi-threading behavior
-* Add a replaceable "vefxio" backend dll for IIDX (xyen)
-* Card reader emulation can now be disabled in iidxhook (xyen)
-* Add jbhook (xyen, mon)
-* Add ddrhook (ported from Bemanitools 4 by mon)
-* Various ICCA emulation improvements (xyen, mon)
-* QoL improvements to config.exe (xyen, mon)
-* Other bug fixes (various contributors)
+
+- Support for the new IIDX 25 IO board (xyen)
+- New IO hook system with better multi-threading behavior
+- Add a replaceable "vefxio" backend dll for IIDX (xyen)
+- Card reader emulation can now be disabled in iidxhook (xyen)
+- Add jbhook (xyen, mon)
+- Add ddrhook (ported from Bemanitools 4 by mon)
+- Various ICCA emulation improvements (xyen, mon)
+- QoL improvements to config.exe (xyen, mon)
+- Other bug fixes (various contributors)

 ## a19
-* iidx 17 support
-* Bugfix: forums.php?action=viewthread&threadid=51257&postid=1425861#post1425861
-* iidx 14-17: Improved monitor check and new monitor check screen which shows 
-the current frame rate instead of just a white screen
-* iidx 09-13: Improved monitor check (but still white screen when in progress. 
-d3d8 doesn't offer any text render out of the box)
-* iidxfx(2)-exit-hook: Switch off lights on shutdown
-* Various other bugfixes
+
+- iidx 17 support
+- Bugfix: forums.php?action=viewthread&threadid=51257&postid=1425861#post1425861
+- iidx 14-17: Improved monitor check and new monitor check screen which shows the current frame rate
+  instead of just a white screen
+- iidx 09-13: Improved monitor check (but still white screen when in progress. d3d8 doesn't offer
+  any text render out of the box)
+- iidxfx(2)-exit-hook: Switch off lights on shutdown
+- Various other bugfixes

 ## a18
-* Bugfix: forums.php?action=viewthread&threadid=51063
-* Various other bugfixes
+
+- Bugfix: forums.php?action=viewthread&threadid=51063
+- Various other bugfixes

 ## a17
-* IIDX 16 support
-* Fix broken debug output to file (for iidxhook1-3 and all games using launcher)
-* Improve debug output
-* Various minor bugfixes
+
+- IIDX 16 support
+- Fix broken debug output to file (for iidxhook1-3 and all games using launcher)
+- Improve debug output
+- Various minor bugfixes

 ## a16
-* Add tools.zip which contains various tools for development: ezusb IO related, 
-bemanitools API testing, acio related
-* Add documentation (.md files) for tools
-* Add iidxfx(2)-exit-hook.dll: Hook this using either inject or launcher 
-(depending on the game version) and exit the game by pressing Start P1 + Start 
-P2 + VEFX + Effect simultaneously
-* Bugfix iidxio API: 16seg not working on IIDX games with FX2 emulation
-* Bugfix iidxio API: return value of init call not getting checked in hook 
-libraries
-* SDVX input emulation fixes
-* Various other bugfixes
+
+- Add tools.zip which contains various tools for development: ezusb IO related, bemanitools API
+  testing, acio related
+- Add documentation (.md files) for tools
+- Add iidxfx(2)-exit-hook.dll: Hook this using either inject or launcher (depending on the game
+  version) and exit the game by pressing Start P1 + Start P2 + VEFX + Effect simultaneously
+- Bugfix iidxio API: 16seg not working on IIDX games with FX2 emulation
+- Bugfix iidxio API: return value of init call not getting checked in hook libraries
+- SDVX input emulation fixes
+- Various other bugfixes

 ## a15
-* Select best network adapter if having multiple
-* Add Felica card detection
-* Fix SDVX HID lighting
-* Fix IIDX FX2 deck lighting
+
+- Select best network adapter if having multiple
+- Add Felica card detection
+- Fix SDVX HID lighting
+- Fix IIDX FX2 deck lighting

 ## a13
-* iidx 15 (DJ Troopers) support
-* Fix BG video triangle seam on old games
-* New options handling: cmd args and options file
+
+- iidx 15 (DJ Troopers) support
+- Fix BG video triangle seam on old games
+- New options handling: cmd args and options file

 ## a11
-* Fix nVidia crash on GOLD
+
+- Fix nVidia crash on GOLD

 ## a10
-* Adds IO2 emulation for Gold
-* Add IO2 translucent mode for Gold ONLY atm (untested due to lack of hardware)
-* Random input bug resolved (also kinda untested, so maybe?)
+
+- Adds IO2 emulation for Gold
+- Add IO2 translucent mode for Gold ONLY atm (untested due to lack of hardware)
+- Random input bug resolved (also kinda untested, so maybe?)

 ## a09
-* Add IIDX 14 support
+
+- Add IIDX 14 support

 ## a08
-* Add experimental KFCA (SDVX PCB) support
-* Add Sound Voltex and BeatStream builds
+
+- Add experimental KFCA (SDVX PCB) support
+- Add Sound Voltex and BeatStream builds

 ## a07
-* Add IIDX 13 DistorteD support
-* Add option to use real card readers with IIDX 13
+
+- Add IIDX 13 DistorteD support
+- Add option to use real card readers with IIDX 13

 ## a06
-* Fixes bug in chart data loader interception code
+
+- Fixes bug in chart data loader interception code

 ## a05
-* Fix broken card reader emulation on Copula
-* Add monitor check/auto timebase for old IIDX games (9-12) -> refer to the 
-readme file on how to use it
+
+- Fix broken card reader emulation on Copula
+- Add monitor check/auto timebase for old IIDX games (9-12) -> refer to the readme file on how to
+  use it

 ## a04
-* Add software frame rate limiter for all D3D8 based games (-g option).
+
+- Add software frame rate limiter for all D3D8 based games (-g option).

 ## a03
-* Add support for IIDX 9-12
-* Translucent mode: Use real C02 EZUSB IO hardware
-* eamio-real.dll: Use real slotted or wave pass card readers
-* Setup guide, advanced features and FAQ: see readme file iidxhook1.md
+
+- Add support for IIDX 9-12
+- Translucent mode: Use real C02 EZUSB IO hardware
+- eamio-real.dll: Use real slotted or wave pass card readers
+- Setup guide, advanced features and FAQ: see readme file iidxhook1.md

 ## a02
-* Fonts are always correct irrespective of system locale! (Make sure you 
-install East Asian fonts tho)
-* No longer crashes shitty gaming mice that don't follow the USB spec! (will 
-backport this to bt4)
-* launcher.exe now has a UAC manifest! (because 2006 called and told me to get 
-with the fucking program)
+
+- Fonts are always correct irrespective of system locale! (Make sure you install East Asian fonts
+  tho)
+- No longer crashes shitty gaming mice that don't follow the USB spec! (will backport this to bt4)
+- launcher.exe now has a UAC manifest! (because 2006 called and told me to get with the fucking
+  program)

 ## a01
-* Initial Alpha, only supports IIDX 21 and 22 for now.
+
+- Initial Alpha, only supports IIDX 21 and 22 for now.
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,36 +1,39 @@
 # Contributing
+
 This document outlines different types of contributions and how YOU can help us to improve the
 project. Read it, as it provides guidelines that are there to help you and the maintainers.

 ## Reporting and discussions: Issues section on gitlab
+
 In order to avoid having to manage ongoing discussions and bug reports on different communication
-channels, e.g. forums, messangers or other closed groups, we ask everyone to treat the issue
-section on gitlab as the place to open their relevant discussions and bug reports regarding the
-project.
+channels, e.g. forums, messangers or other closed groups, we ask everyone to treat the issue section
+on gitlab as the place to open their relevant discussions and bug reports regarding the project.

 The maintainers of the project do not have the time nor motivation to micromanage on the various
-channels and enter all data here to have it collected. This is a simple task that *ANYONE* can do 
+channels and enter all data here to have it collected. This is a simple task that *ANYONE* can do
 allowing the maintainers and developers to spend their time on the codebase.

 ## Bug reports
+
 Follow these steps when reporting bugs to ensure you provide all information we *always* need and
 make your report valuable and actionable.

 1. On the bemanitools repository, go `Issues` on the left-hand sidebar.
 1. Use the search function to check if there is an already open issue regarding what you want to
-report
-    1. If that applies, read the open issue to check what's already covered regarding the bug
-    1. Provide additional information or things that are missing. Upload your log files,
-    screenshots, videos etc. Be careful to remove sensitive information like PCBIDs
-    1. Give a thumbs up to the issue to show you are interested/affected as well
+   report
+   1. If that applies, read the open issue to check what's already covered regarding the bug
+   1. Provide additional information or things that are missing. Upload your log files, screenshots,
+      videos etc. Be careful to remove sensitive information like PCBIDs
+   1. Give a thumbs up to the issue to show you are interested/affected as well
 1. If no existing issue avilable, create a new one
 1. Come up with a descriptive title
 1. **USE OUR BUG REPORTING TEMPLATE**: Pick it by selecting `Bug` on the `Description` section
 1. Follow the sections and their instructions provided by the template and fill them in. All fields
-are mandatory to provide a comprehensive report if not stated otherwise
+   are mandatory to provide a comprehensive report if not stated otherwise
 1. When finished, submit the issue

 ## Pull requests: bugfixes, new features or other code contributions
+
 Pull requests are welcome! May it be a merge request to an already known issue or a new feature that
 you consider as a valuable contribution, please open a MR.

@@ -47,37 +50,39 @@ that your contribution meets our standards. This is not meant to annoy people bu
 consistency that the project stays maintainable for everyone.

 Steps for contributing to the repository using a merge request:
+
 1. If you are new to git, take a bit of time to learn the basics which are very simple, e.g. Google
-for "git tutorial for non-programmers"
+   for "git tutorial for non-programmers"
 1. Fork the upstream repository (Fork button on the top right on the main page of the repository)
 1. You can start editing files like documentation easily inside gitlab which might be the prefered
-option for many non-coders
+   option for many non-coders
 1. Clone your fork to your local machine and start working on stuff
 1. Ensure you push your changes to your fork on gitlab
 1. When done, go to the `Merge Requests` section on the left sidebar of the upstream repository
 1. Hit the `New merge request` button
 1. Select the `master` branch as the source branch
 1. Select whatever branch you worked, likely `master` if you didn't change that, as the target
-branch
+   branch
 1. Hit `Compare branches and continue`
 1. Provide a descriptive title of what your change is about
 1. **USE OUR MR TEMPLATES**
-    1. If you submit a bugfix, use the `Bugfix` tempalte and fill in the sections
-    1. If you submit a new feature, use the `Feature` template and fill in the sections
+   1. If you submit a bugfix, use the `Bugfix` tempalte and fill in the sections
+   1. If you submit a new feature, use the `Feature` template and fill in the sections
 1. If you submit some minor fixes or documentation improvements, there is no template for that.
-Please provide a expressive description what you did and *why* you did that
+   Please provide a expressive description what you did and *why* you did that
 1. If any of your changes are tied to one or multiple issues, link them in the description
 1. When done, hit `Submit merge request`

 The maintainers will take a look at your submission and provide their feedback. The intention of
-this process is to ensure the contribution meets the quality standards. Please also see this is
-a learning opportunity, especially with your first contribution, if a lot of comments and change
+this process is to ensure the contribution meets the quality standards. Please also see this is a
+learning opportunity, especially with your first contribution, if a lot of comments and change
 requests are being made. The maintainers are open to discuss their suggestions/feedback if
 reasonable feedback is given back to them.

 Once all discussion is resolved and the involved maintainers approved your submission, it will be
 merged into master and also included in the next release.

-## Roadmap 
+## Roadmap
+
 No concrete roadmap or timeline exists. We want to continue adding support for new games as well as
-old games (some of the old games supported by BT4 are not supported, yet).
+old games (some of the old games supported by BT4 are not supported, yet).
--- a/Dockerfile.build
+++ b/Dockerfile.build
--- a/Dockerfile.dev
+++ b/Dockerfile.dev
@@ -0,0 +1,21 @@
+FROM --platform=amd64 debian:11.6-slim@sha256:f7d141c1ec6af549958a7a2543365a7829c2cdc4476308ec2e182f8a7c59b519
+
+LABEL description="Development environment for bemanitools"
+
+# mingw-w64-gcc has 32-bit and 64-bit toolchains
+RUN apt-get update && apt-get install -y --no-install-recommends \
+    mingw-w64 \
+    mingw-w64-common \
+    make \
+    zip \
+    git \
+    clang-format \
+    python3-pip \
+ && rm -rf /var/lib/apt/lists/*
+
+RUN pip3 install mdformat
+
+RUN mkdir /bemanitools
+WORKDIR /bemanitools
+
+ENV SHELL /bin/bash
--- a/44
+++ b/44
@@ -13,8 +13,10 @@ BUILDDIR        ?= build

 builddir_docker 	  := $(BUILDDIR)/docker

-docker_container_name := "bemanitools-build"
-docker_image_name     := "bemanitools-build:latest"
+docker_build_container_name := "bemanitools-build"
+docker_build_image_name     := "bemanitools-build:latest"
+docker_dev_container_name := "bemanitools-dev"
+docker_dev_image_name     := "bemanitools-dev:latest"

 depdir                := $(BUILDDIR)/dep
 objdir                := $(BUILDDIR)/obj
@@ -41,8 +43,10 @@ FORCE:

 .PHONY: \
 build-docker \
+dev-docker \
 clean \
 code-format \
+doc-format \
 print-building \
 print-release \
 run-tests \
@@ -53,6 +57,7 @@ release: \
 print-release \
 clean \
 code-format \
+doc-format \
 all \
 run-tests

@@ -74,6 +79,10 @@ code-format:
 	$(V)echo "Applying clang-format..."
 	$(V)find src/main src/test -name '*.c' -o -name '*.h' | xargs clang-format -i -style=file

+doc-format:
+	$(V)echo "Applying mdformat on all docs..."
+	$(V)find . -name '*.md' | xargs mdformat --wrap 100
+
 run-tests:
 	$(V)echo "Running tests..."
 	$(V)./run-tests-wine.sh
@@ -83,21 +92,38 @@ version:
 	$(V)echo "$(gitrev)" > version

 build-docker:
-	$(V)docker rm -f $(docker_container_name) 2> /dev/null || true
+	$(V)docker rm -f $(docker_build_container_name) 2> /dev/null || true
 	$(V)docker \
 		build \
-		-t $(docker_image_name) \
-		-f Dockerfile \
+		-t $(docker_build_image_name) \
+		-f Dockerfile.build \
 		.
 	$(V)docker \
 		run \
 		--volume $(shell pwd):/bemanitools \
-		--name $(docker_container_name) \
-		$(docker_image_name)
+		--name $(docker_build_container_name) \
+		$(docker_build_image_name)
+
+dev-docker:
+	$(V)docker rm -f $(docker_dev_container_name) 2> /dev/null || true
+	$(V)docker \
+		build \
+		-t $(docker_dev_image_name) \
+		-f Dockerfile.dev \
+		.
+	$(V)docker \
+		run \
+		--interactive \
+		--tty \
+		--volume $(shell pwd):/bemanitools \
+		--name $(docker_dev_container_name) \
+		$(docker_dev_image_name)

 clean-docker:
-	$(V)docker rm -f $(docker_container_name) || true
-	$(V)docker image rm -f $(docker_image_name) || true
+	$(V)docker rm -f $(docker_dev_container_name) || true
+	$(V)docker image rm -f $(docker_dev_image_name) || true
+	$(V)docker rm -f $(docker_build_container_name) || true
+	$(V)docker image rm -f $(docker_build_image_name) || true
 	$(V)rm -rf $(BUILDDIR)

 #
--- a/Module.mk
+++ b/Module.mk
@@ -80,7 +80,7 @@ cflags          += \
 # Each AVS-dependent project should consume the earliest AVS import definition
 # that is still ABI-compatible with the real build its target links against.

-avsvers_32      := 1700 1603 1601 1508 1403 1304 1101 1002 803 0
+avsvers_32      := 1700 1603 1601 1508 1403 1306 1304 1101 1002 803 0
 avsvers_64      := 1700 1603 1601 1509 1508

 imps            += avs avs-ea3
@@ -91,6 +91,7 @@ include src/main/acioemu/Module.mk
 include src/main/aciomgr/Module.mk
 include src/main/aciotest/Module.mk
 include src/main/asio/Module.mk
+include src/main/avs-util/Module.mk
 include src/main/bio2drv/Module.mk
 include src/main/bio2emu-iidx/Module.mk
 include src/main/bio2emu/Module.mk
@@ -99,6 +100,7 @@ include src/main/bstio/Module.mk
 include src/main/camhook/Module.mk
 include src/main/cconfig/Module.mk
 include src/main/config/Module.mk
+include src/main/core/Module.mk
 include src/main/d3d9-util/Module.mk
 include src/main/d3d9exhook/Module.mk
 include src/main/ddrhook-util/Module.mk
@@ -323,6 +325,10 @@ $(zipdir)/iidx-18.zip: \
 		dist/iidx/config.bat \
 		dist/iidx/gamestart-18.bat \
 		dist/iidx/iidxhook-18.conf \
+		dist/iidx/launcher-18.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		dist/iidx/vefx.txt \
 		| $(zipdir)/
 	$(V)echo ... $@
@@ -354,6 +360,10 @@ $(zipdir)/iidx-19.zip: \
 		dist/iidx/config.bat \
 		dist/iidx/gamestart-19.bat \
 		dist/iidx/iidxhook-19.conf \
+		dist/iidx/launcher-19.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		dist/iidx/vefx.txt \
 		| $(zipdir)/
 	$(V)echo ... $@
@@ -370,6 +380,10 @@ $(zipdir)/iidx-20.zip: \
 		dist/iidx/config.bat \
 		dist/iidx/gamestart-20.bat \
 		dist/iidx/iidxhook-20.conf \
+		dist/iidx/launcher-20.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		dist/iidx/vefx.txt \
 		| $(zipdir)/
 	$(V)echo ... $@
@@ -407,6 +421,13 @@ $(zipdir)/iidx-21-to-24.zip: \
 		dist/iidx/iidxhook-22.conf \
 		dist/iidx/iidxhook-23.conf \
 		dist/iidx/iidxhook-24.conf \
+		dist/iidx/launcher-21.xml \
+		dist/iidx/launcher-22.xml \
+		dist/iidx/launcher-23.xml \
+		dist/iidx/launcher-24.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		dist/iidx/vefx.txt \
 		| $(zipdir)/
 	$(V)echo ... $@
@@ -425,6 +446,11 @@ $(zipdir)/iidx-25-to-26.zip: \
 		dist/iidx/gamestart-26.bat \
 		dist/iidx/iidxhook-25.conf \
 		dist/iidx/iidxhook-26.conf \
+		dist/iidx/launcher-25.xml \
+		dist/iidx/launcher-26.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		dist/iidx/vefx.txt \
 		| $(zipdir)/
 	$(V)echo ... $@
@@ -447,6 +473,13 @@ $(zipdir)/iidx-27-to-30.zip: \
 		dist/iidx/iidxhook-28.conf \
 		dist/iidx/iidxhook-29.conf \
 		dist/iidx/iidxhook-30.conf \
+		dist/iidx/launcher-27.xml \
+		dist/iidx/launcher-28.xml \
+		dist/iidx/launcher-29.xml \
+		dist/iidx/launcher-30.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		dist/iidx/vefx.txt \
 		| $(zipdir)/
 	$(V)echo ... $@
@@ -515,6 +548,10 @@ $(zipdir)/jb-03.zip: \
 		build/bin/indep-32/jbio.dll \
 		dist/jb/config.bat \
 		dist/jb/gamestart-03.bat \
+		dist/jb/launcher-03.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^
@@ -528,6 +565,10 @@ $(zipdir)/jb-04.zip: \
 		build/bin/indep-32/jbio.dll \
 		dist/jb/config.bat \
 		dist/jb/gamestart-03.bat \
+		dist/jb/launcher-03.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^
@@ -541,6 +582,10 @@ $(zipdir)/jb-05-to-07.zip: \
 		build/bin/indep-32/jbio.dll \
 		dist/jb/config.bat \
 		dist/jb/gamestart-04.bat \
+		dist/jb/launcher-04.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^
@@ -554,6 +599,10 @@ $(zipdir)/jb-08.zip: \
 		build/bin/indep-32/jbio.dll \
 		dist/jb/config.bat \
 		dist/jb/gamestart-04.bat \
+		dist/jb/launcher-04.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^
@@ -578,6 +627,10 @@ $(zipdir)/sdvx-01-to-04.zip: \
 		build/bin/indep-32/sdvxio.dll \
 		dist/sdvx/config.bat \
 		dist/sdvx/gamestart.bat \
+		dist/sdvx/launcher.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^
@@ -592,6 +645,10 @@ $(zipdir)/sdvx-05-to-06.zip: \
 		dist/sdvx5/config.bat \
 		dist/sdvx5/gamestart.bat \
 		dist/sdvx5/sdvxhook2.conf \
+		dist/sdvx5/launcher.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^
@@ -606,6 +663,10 @@ $(zipdir)/sdvx-05-cn.zip: \
 		dist/sdvx5/config.bat \
 		dist/sdvx5/gamestart-cn.bat \
 		dist/sdvx5/sdvxhook2-cn.conf \
+		dist/sdvx5/launcher-cn.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^
@@ -680,14 +741,18 @@ $(zipdir)/ddr-12.zip: \
 		build/bin/indep-32/geninput.dll \
 		dist/ddr/config.bat \
 		dist/ddr/gamestart-12.bat \
+		dist/ddr/launcher-12.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^

 $(zipdir)/ddr-13.zip: \
-		build/bin/avs2_1304-32/launcher.exe \
-		build/bin/avs2_1304-32/ddrhook2.dll \
-		build/bin/avs2_1304-32/unicorntail.dll \
+		build/bin/avs2_1306-32/launcher.exe \
+		build/bin/avs2_1306-32/ddrhook2.dll \
+		build/bin/avs2_1306-32/unicorntail.dll \
 		build/bin/indep-32/config.exe \
 		build/bin/indep-32/ddrio.dll \
 		build/bin/indep-32/ddrio-mm.dll \
@@ -696,11 +761,15 @@ $(zipdir)/ddr-13.zip: \
 		build/bin/indep-32/geninput.dll \
 		dist/ddr/config.bat \
 		dist/ddr/gamestart-13.bat \
+		dist/ddr/launcher-13.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^

-$(zipdir)/ddr-14-to-16.zip: \
+$(zipdir)/ddr-14-to-18.zip: \
 		build/bin/avs2_1508-32/launcher.exe \
 		build/bin/avs2_1508-32/ddrhook2.dll \
 		build/bin/avs2_1508-32/unicorntail.dll \
@@ -709,14 +778,26 @@ $(zipdir)/ddr-14-to-16.zip: \
 		build/bin/indep-32/eamio.dll \
 		build/bin/indep-32/geninput.dll \
 		dist/ddr/config.bat \
+		dist/ddr/gamestart-17.bat \
+		dist/ddr/gamestart-18.bat \
 		dist/ddr/gamestart-14.bat \
 		dist/ddr/gamestart-15.bat \
 		dist/ddr/gamestart-16.bat \
+		dist/ddr/gamestart-17.bat \
+		dist/ddr/gamestart-18.bat \
+		dist/ddr/launcher-14.xml \
+		dist/ddr/launcher-15.xml \
+		dist/ddr/launcher-16.xml \
+		dist/ddr/launcher-17.xml \
+		dist/ddr/launcher-18.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^

-$(zipdir)/ddr-16-x64.zip: \
+$(zipdir)/ddr-16-to-18-x64.zip: \
 		build/bin/avs2_1603-64/launcher.exe \
 		build/bin/avs2_1603-64/ddrhook2.dll \
 		build/bin/avs2_1603-64/unicorntail.dll \
@@ -725,7 +806,17 @@ $(zipdir)/ddr-16-x64.zip: \
 		build/bin/indep-64/eamio.dll \
 		build/bin/indep-64/geninput.dll \
 		dist/ddr/config.bat \
+		dist/ddr/gamestart-17.bat \
+		dist/ddr/gamestart-18.bat \
 		dist/ddr/gamestart-16.bat \
+		dist/ddr/gamestart-17.bat \
+		dist/ddr/gamestart-18.bat \
+		dist/ddr/launcher-16.xml \
+		dist/ddr/launcher-17.xml \
+		dist/ddr/launcher-18.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^
@@ -764,6 +855,11 @@ $(zipdir)/bst.zip: \
 		dist/bst/config.bat \
 		dist/bst/gamestart1.bat \
 		dist/bst/gamestart2.bat \
+		dist/bst/launcher-01.xml \
+		dist/bst/launcher-02.xml \
+		dist/shared/ea3-ident.xml \
+		dist/shared/ea3-license.xml \
+		dist/shared/ea3-service.xml \
 		| $(zipdir)/
 	$(V)echo ... $@
 	$(V)zip -j $@ $^
@@ -827,8 +923,8 @@ $(BUILDDIR)/bemanitools.zip: \
 		$(zipdir)/ddr-12.zip \
 		$(zipdir)/ddr-12-us.zip \
 		$(zipdir)/ddr-13.zip \
-		$(zipdir)/ddr-14-to-16.zip \
-		$(zipdir)/ddr-16-x64.zip \
+		$(zipdir)/ddr-14-to-18.zip \
+		$(zipdir)/ddr-16-to-18-x64.zip \
 		$(zipdir)/ddr-hwio-x86.zip \
 		$(zipdir)/ddr-hwio-x64.zip \
 		$(zipdir)/doc.zip \
--- a/README.md
+++ b/README.md
@@ -1,174 +1,189 @@
 # Bemanitools 5

-Version: `5.46`
+Version: `5.49`

 [Changelog](CHANGELOG.md)

 A collection of tools to run [various Bemani arcade games](#supported-games).

-Bemanitools 5 (BT5) is the successor to Bemanitools 4 which introduces a big code cleanup and support for newer games.
-BT5 uses a cleaner approach than BT4 did; specifically, all input and lighting is handled by emulating the protocols
-spoken by the real IO PCBs, instead of replacing chunks of game code like BT4. The benefits of this approach are a more
-authentic gameplay experience, and easier support for a broader range of releases from each game series.
+Bemanitools 5 (BT5) is the successor to Bemanitools 4 which introduces a big code cleanup and
+support for newer games. BT5 uses a cleaner approach than BT4 did; specifically, all input and
+lighting is handled by emulating the protocols spoken by the real IO PCBs, instead of replacing
+chunks of game code like BT4. The benefits of this approach are a more authentic gameplay
+experience, and easier support for a broader range of releases from each game series.

 ## Documentation
+
 Browse our [documentation](doc/README.md) as it might already cover various questions and concerns
 you are looking for or about to ask.

 ## Contributions and bug reporting
+
 [Read the dedicated CONTRIBUTING.md documentation](CONTRIBUTING.md).

 The tl;dr version and golden rules of the sections in the document:
-* **EVERYONE** can contribute, this is **NOT** limited to people coding
-* [Open an issue on gitlab for discussions, feature requests and bug reports](CONTRIBUTING.md#reporting-and-discussions-issues-section-on-github)
-* [ALWAYS report bugs as issues and ALWAYS use the available bug template](CONTRIBUTING.md#bug-reports)
-* [Everyone is allowed to submit changes which are not just limited to code by opening merge requests](CONTRIBUTING.md#pull-requests-bugfixes-new-features-or-other-code-contributions)
-* [Documentation improvements can and even should be contributed by non developers](CONTRIBUTING.md#pull-requests-bugfixes-new-features-or-other-code-contributions)
+
+- **EVERYONE** can contribute, this is **NOT** limited to people coding
+- [Open an issue on gitlab for discussions, feature requests and bug reports](CONTRIBUTING.md#reporting-and-discussions-issues-section-on-github)
+- [ALWAYS report bugs as issues and ALWAYS use the available bug template](CONTRIBUTING.md#bug-reports)
+- [Everyone is allowed to submit changes which are not just limited to code by opening merge requests](CONTRIBUTING.md#pull-requests-bugfixes-new-features-or-other-code-contributions)
+- [Documentation improvements can and even should be contributed by non developers](CONTRIBUTING.md#pull-requests-bugfixes-new-features-or-other-code-contributions)

 ## Supported games
+
 The following games are supported with their corresponding hook-libraries.

-* BeatStream
-    * BeatStream (`bst.zip`): bsthook
-    * BeatStream アニムトライヴ (`bst.zip`): bsthook
-* [Dance Dance Revolution](doc/ddrhook/README.md)
-    * Dance Dance Revolution X (`ddr-11.zip`): [ddrhook1](doc/ddrhook/ddrhook1.md)
-    * Dance Dance Revolution X2 (US/EU regions) (`ddr-12-us.zip`): [ddrhook1](doc/ddrhook/ddrhook1.md)
-    * Dance Dance Revolution X2 (JP region) (`ddr-12.zip`): [ddrhook2](doc/ddrhook/ddrhook2.md)
-    * Dance Dance Revolution 2013 (`ddr-14-to-16.zip`): [ddrhook2](doc/ddrhook/ddrhook2.md)
-    * Dance Dance Revolution 2014 (`ddr-14-to-16.zip`): [ddrhook2](doc/ddrhook/ddrhook2.md)
-    * Dance Dance Revolution A (`ddr-14-to-16.zip`): [ddrhook2](doc/ddrhook/ddrhook2.md)
-* [Beatmania IIDX](doc/iidxhook/README.md)
-    * Beatmania IIDX 9th Style (`iidx-09-to-12.zip`): [iidxhook1](doc/iidxhook/iidxhook1.md)
-    * Beatmania IIDX 10th Style (`iidx-09-to-12.zip`): [iidxhook1](doc/iidxhook/iidxhook1.md)
-    * Beatmania IIDX 11 IIDX RED (`iidx-09-to-12.zip`): [iidxhook1](doc/iidxhook/iidxhook1.md)
-    * Beatmania IIDX 12 HAPPY SKY (`iidx-09-to-12.zip`): [iidxhook1](doc/iidxhook/iidxhook1.md)
-    * Beatmania IIDX 13 DistorteD (`iidx-13.zip`): [iidxhook2](doc/iidxhook/iidxhook2.md)
-    * Beatmania IIDX 14 GOLD (`iidx-14-to-17.zip`): [iidxhook3](doc/iidxhook/iidxhook3.md)
-    * Beatmania IIDX 15 DJ TROOPERS (`iidx-14-to-17.zip`): [iidxhook3](doc/iidxhook/iidxhook3.md)
-    * Beatmania IIDX 16 EMPRESS (`iidx-14-to-17.zip`): [iidxhook3](doc/iidxhook/iidxhook3.md)
-    * Beatmania IIDX 17 SIRIUS (`iidx-14-to-17.zip`): [iidxhook3](doc/iidxhook/iidxhook3.md)
-    * Beatmania IIDX 18 Resort Anthem (`iidx-18.zip`): [iidxhook4](doc/iidxhook/iidxhook4.md)
-    * Beatmania IIDX 19 Lincle (`iidx-19.zip`): [iidxhook5](doc/iidxhook/iidxhook5.md)
-    * Beatmania IIDX tricoro CN (狂热节拍 IIDX 2) (`iidx-20-cn.zip`): [iidxhook5-cn](doc/iidxhook/iidxhook5-cn.md)
-    * Beatmania IIDX 20 Tricoro (`iidx-20.zip`): [iidxhook6](doc/iidxhook/iidxhook6.md)
-    * Beatmania IIDX 21 SPADA (`iidx-21-to-24.zip`): [iidxhook7](doc/iidxhook/iidxhook7.md)
-    * Beatmania IIDX 22 PENDUAL (`iidx-21-to-24.zip`): [iidxhook7](doc/iidxhook/iidxhook7.md)
-    * Beatmania IIDX 23 copula (`iidx-21-to-24.zip`): [iidxhook7](doc/iidxhook/iidxhook7.md)
-    * Beatmania IIDX 24 SINOBUZ (`iidx-21-to-24.zip`): [iidxhook7](doc/iidxhook/iidxhook7.md)
-    * Beatmania IIDX 25 CANNON BALLERS (`iidx-25-to-26.zip`): [iidxhook8](doc/iidxhook/iidxhook8.md)
-    * Beatmania IIDX 26 Rootage (`iidx-25-to-26.zip`): [iidxhook8](doc/iidxhook/iidxhook8.md)
-    * Beatmania IIDX 27 Heroic Verse (`iidx-27-to-30.zip`): [iidxhook9](doc/iidxhook/iidxhook9.md)
-    * Beatmania IIDX 28 BISTROVER (`iidx-27-to-30.zip`): [iidxhook9](doc/iidxhook/iidxhook9.md)
-    * Beatmania IIDX 29 CASTHOUR (`iidx-27-to-30.zip`): [iidxhook9](doc/iidxhook/iidxhook9.md)
-    * Beatmania IIDX 30 RESIDENT (`iidx-27-to-30.zip`): [iidxhook9](doc/iidxhook/iidxhook9.md)
-* [jubeat](doc/jbhook/README.md)
-    * jubeat (`jb-01.zip`): [jbhook1](doc/jbhook/jbhook1.md)
-    * jubeat ripples (`jb-02.zip`): [jbhook1](doc/jbhook/jbhook1.md)
-    * jubeat knit (`jb-03.zip`): [jbhook2](doc/jbhook/jbhook2.md)
-    * jubeat copious (`jb-04.zip`): [jbhook2](doc/jbhook/jbhook2.md)
-    * jubeat saucer (fulfill) (`jb-05-to-07.zip`): [jbhook3](doc/jbhook/jbhook3.md)
-    * jubeat prop (`jb-05-to-07.zip`): [jbhook3](doc/jbhook/jbhook3.md)
-    * jubeat qubell (`jb-05-to-07.zip`): [jbhook3](doc/jbhook/jbhook3.md)
-    * jubeat clan (`jb-08.zip`): [jbhook3](doc/jbhook/jbhook3.md)
-    * jubeat festo (`jb-08.zip`): [jbhook3](doc/jbhook/jbhook3.md)
-* [pop'n music](doc/popnhook/README.md)
-    * pop'n music 15 ADVENTURE (`popn-15-to-18.zip`) using [popnhook1](doc/popnhook/popnhook1.md)
-    * pop'n music 16 PARTY♪ (`popn-15-to-18.zip`) using [popnhook1](doc/popnhook/popnhook1.md)
-    * pop'n music 17 THE MOVIE (`popn-15-to-18.zip`) using [popnhook1](doc/popnhook/popnhook1.md)
-    * pop'n music 18 せんごく列伝 (`popn-15-to-18.zip`) using [popnhook1](doc/popnhook/popnhook1.md)
-* SOUND VOLTEX
-    * SOUND VOLTEX BOOTH (`sdvx-01-to-04.zip`): sdvxhook
-    * SOUND VOLTEX II -infinite infection- (`sdvx-01-to-04.zip`): sdvxhook
-    * SOUND VOLTEX III GRAVITY WARS (`sdvx-01-to-04.zip`): sdvxhook
-    * SOUND VOLTEX IV HEAVENLY HAVEN (`sdvx-01-to-04.zip`): sdvxhook
-    * SOUND VOLTEX Vivid Wave (`sdvx-05-to-06`): sdvxhook2
-    * SOUND VOLTEX EXCEED GEAR (`sdvx-05-to-06`): sdvxhook2
+- BeatStream
+  - BeatStream (`bst.zip`): bsthook
+  - BeatStream アニムトライヴ (`bst.zip`): bsthook
+- [Dance Dance Revolution](doc/ddrhook/README.md)
+  - Dance Dance Revolution X (`ddr-11.zip`): [ddrhook1](doc/ddrhook/ddrhook1.md)
+  - Dance Dance Revolution X2 (US/EU regions) (`ddr-12-us.zip`): [ddrhook1](doc/ddrhook/ddrhook1.md)
+  - Dance Dance Revolution X2 (JP region) (`ddr-12.zip`): [ddrhook2](doc/ddrhook/ddrhook2.md)
+  - Dance Dance Revolution X3 vs. 2ndMIX (`ddr-13.zip`): [ddrhook2](doc/ddrhook/ddrhook2.md)
+  - Dance Dance Revolution 2013 (`ddr-14-to-18.zip`): [ddrhook2](doc/ddrhook/ddrhook2.md)
+  - Dance Dance Revolution 2014 (`ddr-14-to-18.zip`): [ddrhook2](doc/ddrhook/ddrhook2.md)
+  - Dance Dance Revolution A (`ddr-14-to-18.zip`): [ddrhook2](doc/ddrhook/ddrhook2.md)
+  - Dance Dance Revolution A20 (`ddr-14-to-18.zip`): [ddrhook2](doc/ddrhook/ddrhook2.md)
+  - Dance Dance Revolution A20+ (`ddr-14-to-18.zip`): [ddrhook2](doc/ddrhook/ddrhook2.md)
+- [Beatmania IIDX](doc/iidxhook/README.md)
+  - Beatmania IIDX 9th Style (`iidx-09-to-12.zip`): [iidxhook1](doc/iidxhook/iidxhook1.md)
+  - Beatmania IIDX 10th Style (`iidx-09-to-12.zip`): [iidxhook1](doc/iidxhook/iidxhook1.md)
+  - Beatmania IIDX 11 IIDX RED (`iidx-09-to-12.zip`): [iidxhook1](doc/iidxhook/iidxhook1.md)
+  - Beatmania IIDX 12 HAPPY SKY (`iidx-09-to-12.zip`): [iidxhook1](doc/iidxhook/iidxhook1.md)
+  - Beatmania IIDX 13 DistorteD (`iidx-13.zip`): [iidxhook2](doc/iidxhook/iidxhook2.md)
+  - Beatmania IIDX 14 GOLD (`iidx-14-to-17.zip`): [iidxhook3](doc/iidxhook/iidxhook3.md)
+  - Beatmania IIDX 15 DJ TROOPERS (`iidx-14-to-17.zip`): [iidxhook3](doc/iidxhook/iidxhook3.md)
+  - Beatmania IIDX 16 EMPRESS (`iidx-14-to-17.zip`): [iidxhook3](doc/iidxhook/iidxhook3.md)
+  - Beatmania IIDX 17 SIRIUS (`iidx-14-to-17.zip`): [iidxhook3](doc/iidxhook/iidxhook3.md)
+  - Beatmania IIDX 18 Resort Anthem (`iidx-18.zip`): [iidxhook4](doc/iidxhook/iidxhook4.md)
+  - Beatmania IIDX 19 Lincle (`iidx-19.zip`): [iidxhook5](doc/iidxhook/iidxhook5.md)
+  - Beatmania IIDX tricoro CN (狂热节拍 IIDX 2) (`iidx-20-cn.zip`):
+    [iidxhook5-cn](doc/iidxhook/iidxhook5-cn.md)
+  - Beatmania IIDX 20 Tricoro (`iidx-20.zip`): [iidxhook6](doc/iidxhook/iidxhook6.md)
+  - Beatmania IIDX 21 SPADA (`iidx-21-to-24.zip`): [iidxhook7](doc/iidxhook/iidxhook7.md)
+  - Beatmania IIDX 22 PENDUAL (`iidx-21-to-24.zip`): [iidxhook7](doc/iidxhook/iidxhook7.md)
+  - Beatmania IIDX 23 copula (`iidx-21-to-24.zip`): [iidxhook7](doc/iidxhook/iidxhook7.md)
+  - Beatmania IIDX 24 SINOBUZ (`iidx-21-to-24.zip`): [iidxhook7](doc/iidxhook/iidxhook7.md)
+  - Beatmania IIDX 25 CANNON BALLERS (`iidx-25-to-26.zip`): [iidxhook8](doc/iidxhook/iidxhook8.md)
+  - Beatmania IIDX 26 Rootage (`iidx-25-to-26.zip`): [iidxhook8](doc/iidxhook/iidxhook8.md)
+  - Beatmania IIDX 27 Heroic Verse (`iidx-27-to-30.zip`): [iidxhook9](doc/iidxhook/iidxhook9.md)
+  - Beatmania IIDX 28 BISTROVER (`iidx-27-to-30.zip`): [iidxhook9](doc/iidxhook/iidxhook9.md)
+  - Beatmania IIDX 29 CASTHOUR (`iidx-27-to-30.zip`): [iidxhook9](doc/iidxhook/iidxhook9.md)
+  - Beatmania IIDX 30 RESIDENT (`iidx-27-to-30.zip`): [iidxhook9](doc/iidxhook/iidxhook9.md)
+- [jubeat](doc/jbhook/README.md)
+  - jubeat (`jb-01.zip`): [jbhook1](doc/jbhook/jbhook1.md)
+  - jubeat ripples (`jb-02.zip`): [jbhook1](doc/jbhook/jbhook1.md)
+  - jubeat knit (`jb-03.zip`): [jbhook2](doc/jbhook/jbhook2.md)
+  - jubeat copious (`jb-04.zip`): [jbhook2](doc/jbhook/jbhook2.md)
+  - jubeat saucer (fulfill) (`jb-05-to-07.zip`): [jbhook3](doc/jbhook/jbhook3.md)
+  - jubeat prop (`jb-05-to-07.zip`): [jbhook3](doc/jbhook/jbhook3.md)
+  - jubeat qubell (`jb-05-to-07.zip`): [jbhook3](doc/jbhook/jbhook3.md)
+  - jubeat clan (`jb-08.zip`): [jbhook3](doc/jbhook/jbhook3.md)
+  - jubeat festo (`jb-08.zip`): [jbhook3](doc/jbhook/jbhook3.md)
+- [pop'n music](doc/popnhook/README.md)
+  - pop'n music 15 ADVENTURE (`popn-15-to-18.zip`) using [popnhook1](doc/popnhook/popnhook1.md)
+  - pop'n music 16 PARTY♪ (`popn-15-to-18.zip`) using [popnhook1](doc/popnhook/popnhook1.md)
+  - pop'n music 17 THE MOVIE (`popn-15-to-18.zip`) using [popnhook1](doc/popnhook/popnhook1.md)
+  - pop'n music 18 せんごく列伝 (`popn-15-to-18.zip`) using [popnhook1](doc/popnhook/popnhook1.md)
+- SOUND VOLTEX
+  - SOUND VOLTEX BOOTH (`sdvx-01-to-04.zip`): sdvxhook
+  - SOUND VOLTEX II -infinite infection- (`sdvx-01-to-04.zip`): sdvxhook
+  - SOUND VOLTEX III GRAVITY WARS (`sdvx-01-to-04.zip`): sdvxhook
+  - SOUND VOLTEX IV HEAVENLY HAVEN (`sdvx-01-to-04.zip`): sdvxhook
+  - SOUND VOLTEX Vivid Wave (`sdvx-05-to-06`): sdvxhook2
+  - SOUND VOLTEX EXCEED GEAR (`sdvx-05-to-06`): sdvxhook2

 ## Auxiliary tooling
-* Bootstrapping
-  * [inject](doc/inject.md): Inject arbitrary hooking libraries into a target application process.
-  * [launcher](doc/launcher.md): Bootstrap Konami's AVS environment and launch a target application with arbitrary
-    injected hooking libraries. 
-* Beatmnia IIDX Ezusb IO board
-  * [ezusb-iidx-fpga-flash](doc/tools/ezusb-iidx-fpga-flash.md): Flash a binary blob with FPGA firmware to a target
-    ezusb FX IO board
-  * [ezusb-iidx-sram-flash](doc/tools/ezusb-iidx-sram-flash.md): Flash a binary blob with SRAM contents to a target
-    ezusb FX2 IO board
-* Exit hooks: Exit the game with a button combination using native cabinet inputs
-  * [iidx-ezusb-exit-hook](doc/tools/iidx-ezusb-exit-hook.md): For IIDX with ezusb IO
-  * [iidx-bio2-exit-hook](doc/tools/iidx-bio2-exit-hook.md): For IIDX with BIO2 IO
-  * [iidx-ezusb2-exit-hook](doc/tools/iidx-ezusb-exit-hook.md): For IIDX with ezusb FX2 IO
-* Bemanitools API testing: Tools for testing bemanitools API implementations
-  * [ddriotest](doc/tools/ddriotest.md): For [ddrio API](doc/api.md#io-boards)
-  * [eamiotest](doc/tools/eamiotest.md): For [eamio API](doc/api.md#eamuse-readers)
-  * [iidxiotest](doc/tools/iidxiotest.md): For [iidxio API](doc/api.md#io-boards)
-  * [jbiotest](doc/tools/jbiotest.md): For [jbio API](doc/api.md#io-boards)
-* DDR IO testing: Tools for testing hardware of a real DDR cabinet
-  * [p3io-ddr-tool](doc/tools/p3io-ddr-tool.md)
-  * [extiotest](doc/tools/extiotest.md)
-* [aciotest](doc/tools/aciotest.md): Command line tool to quickly test ACIO devices
-* config: UI input/output configuration tool when using the default bemanitools API (geninput)
-* ir-beat-patch-9/10: Patch the IR beat phase on IIDX 9 and 10
-* [mempatch-hook](doc/tools/mempatch-hook.md): Patch raw memory locations in the target process based on the provided
-  configuration
-* [pcbidgen](doc/tools/pcbidgen.md): Konami PCBID generator tool
-* [ViGEm clients](doc/vigem/README.md): Expose BT5 APIs as XBOX game controllers to play any games with real cabinet
-  hardware.
+
+- Bootstrapping
+  - [inject](doc/inject.md): Inject arbitrary hooking libraries into a target application process.
+  - [launcher](doc/launcher.md): Bootstrap Konami's AVS environment and launch a target application
+    with arbitrary injected hooking libraries.
+- Beatmnia IIDX Ezusb IO board
+  - [ezusb-iidx-fpga-flash](doc/tools/ezusb-iidx-fpga-flash.md): Flash a binary blob with FPGA
+    firmware to a target ezusb FX IO board
+  - [ezusb-iidx-sram-flash](doc/tools/ezusb-iidx-sram-flash.md): Flash a binary blob with SRAM
+    contents to a target ezusb FX2 IO board
+- Exit hooks: Exit the game with a button combination using native cabinet inputs
+  - [iidx-ezusb-exit-hook](doc/tools/iidx-ezusb-exit-hook.md): For IIDX with ezusb IO
+  - [iidx-bio2-exit-hook](doc/tools/iidx-bio2-exit-hook.md): For IIDX with BIO2 IO
+  - [iidx-ezusb2-exit-hook](doc/tools/iidx-ezusb-exit-hook.md): For IIDX with ezusb FX2 IO
+- Bemanitools API testing: Tools for testing bemanitools API implementations
+  - [ddriotest](doc/tools/ddriotest.md): For [ddrio API](doc/api.md#io-boards)
+  - [eamiotest](doc/tools/eamiotest.md): For [eamio API](doc/api.md#eamuse-readers)
+  - [iidxiotest](doc/tools/iidxiotest.md): For [iidxio API](doc/api.md#io-boards)
+  - [jbiotest](doc/tools/jbiotest.md): For [jbio API](doc/api.md#io-boards)
+- DDR IO testing: Tools for testing hardware of a real DDR cabinet
+  - [p3io-ddr-tool](doc/tools/p3io-ddr-tool.md)
+  - [extiotest](doc/tools/extiotest.md)
+- [aciotest](doc/tools/aciotest.md): Command line tool to quickly test ACIO devices
+- config: UI input/output configuration tool when using the default bemanitools API (geninput)
+- ir-beat-patch-9/10: Patch the IR beat phase on IIDX 9 and 10
+- [mempatch-hook](doc/tools/mempatch-hook.md): Patch raw memory locations in the target process
+  based on the provided configuration
+- [pcbidgen](doc/tools/pcbidgen.md): Konami PCBID generator tool
+- [ViGEm clients](doc/vigem/README.md): Expose BT5 APIs as XBOX game controllers to play any games
+  with real cabinet hardware.

 ## Pre-requisites

 ### Supported platforms
-Our main platforms are currently Windows XP and Windows 7 which are also the target platforms on the original hardware
-of those games. However, as it gets more difficult to get and maintain hardware comptible with Windows XP, this might
-change in the future. Many games also run on very recent Windows 10 builds but bear with us that it's hard to keep up
-with Windows updates breaking legacy software.
+
+Our main platforms are currently Windows XP and Windows 7 which are also the target platforms on the
+original hardware of those games. However, as it gets more difficult to get and maintain hardware
+comptible with Windows XP, this might change in the future. Many games also run on very recent
+Windows 10 builds but bear with us that it's hard to keep up with Windows updates breaking legacy
+software.

 ### Distribution contents
-Check the [list of supported games](#supported-games) to grab the right files for your game. BT5 also includes
-a *tools* subpackage (tools.zip) as well as the full source code (src.zip).

-You will find *.md files in various sub-packages that give you further instructions for setup, usage, error information
-or FAQ. We advice you to read them as your questions and concerns might already be answered by them. If not, let us
-know if there is any information that you consider helpful or important to know and should be added.
+Check the [list of supported games](#supported-games) to grab the right files for your game. BT5
+also includes a *tools* subpackage (tools.zip) as well as the full source code (src.zip).
+
+You will find \*.md files in various sub-packages that give you further instructions for setup,
+usage, error information or FAQ. We advice you to read them as your questions and concerns might
+already be answered by them. If not, let us know if there is any information that you consider
+helpful or important to know and should be added.

 ### Setup and dependencies
+
 Most (older generation) games were developed for Windows XP Embedded but should run fine on any
 consumer version of Windows XP. Newer versions of Windows, e.g. Windows 7, 8 and 10, should be fine
 as well. Some hooks also include fixes required to run the games on a more recent version.

 Depending on the game, you also need the following dependencies installed:

-* The 32-bit (x86) version of
+- The 32-bit (x86) version of
  [Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC Security Update](https://www.microsoft.com/en-sg/download/details.aspx?id=26999)
-* The 32-bit (x86) and 64-bit (x64) versions of
+- The 32-bit (x86) and 64-bit (x64) versions of
  [Microsoft Visual C++ Redistributable Packages for Visual Studio 2013](https://www.microsoft.com/en-sg/download/details.aspx?id=40784)
-* The [DirectX 9 End-User Runtimes (June 2010)](https://www.microsoft.com/en-us/download/details.aspx?id=8109)
+- The
+  [DirectX 9 End-User Runtimes (June 2010)](https://www.microsoft.com/en-us/download/details.aspx?id=8109)

-See also
-[bemanitools-supplement](https://www.github.com/djhackersdev/bemanitools-supplement/)
-for files.
+See also [bemanitools-supplement](https://www.github.com/djhackersdev/bemanitools-supplement/) for
+files.

 ## Development
+
 ### Building
+
 See the [development document](doc/development.md).

 ### Architecture
-A dedicate [architecture document](doc/architecture.md) outlines the architecture of Bemanitools and points out the most
-important aspects you should know before you get started with development.
+
+A dedicate [architecture document](doc/architecture.md) outlines the architecture of Bemanitools and
+points out the most important aspects you should know before you get started with development.

 ### API
+
 Please refer to the [API documentation](doc/api.md).

 ## Release process
+
 Please refer to the [dedicated documentation](doc/release-process.md).

 ## License
-Source code license is the Unlicense; you are permitted to do with this as thou wilt. For details, please refer to the
-[LICENSE file](LICENSE) included with the source code.
-
-
-
-
-

+Source code license is the Unlicense; you are permitted to do with this as thou wilt. For details,
+please refer to the [LICENSE file](LICENSE) included with the source code.
--- a/dist/bst/gamestart1.bat
+++ b/dist/bst/gamestart1.bat
@@ -1,10 +1,34 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\nvram\coin.xml copy prop\defaults\coin.xml dev\nvram\coin.xml
-if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin.xml
-if not exist dev\raw mkdir dev\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules

-launcher -K bsthook.dll -E prop/ea3-config-1.xml beatstream1.dll %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-01.xml %*
--- a/dist/bst/gamestart2.bat
+++ b/dist/bst/gamestart2.bat
@@ -1,10 +1,34 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\nvram\coin.xml copy prop\defaults\coin.xml dev\nvram\coin.xml
-if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin.xml
-if not exist dev\raw mkdir dev\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules

-launcher -K bsthook.dll -E prop/ea3-config-2.xml beatstream2.dll %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-02.xml %*
--- a/dist/bst/launcher-01.xml
+++ b/dist/bst/launcher-01.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config-1.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">16777216</heap_avs>
+                    <heap_std __type="u32">16777216</heap_std>
+                </boot>∂
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>beatstream1.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-server.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">bsthook.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/bst/launcher-02.xml
+++ b/dist/bst/launcher-02.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config-2.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">16777216</heap_avs>
+                    <heap_std __type="u32">16777216</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>beatstream2.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">bsthook.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/ddr/gamestart-12.bat
+++ b/dist/ddr/gamestart-12.bat
@@ -1,11 +1,42 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist conf\nvram mkdir conf\nvram
-if not exist conf\raw mkdir conf\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set COM_DIR=%CONTENT_DIR%\com
+set MODULES_DIR=%CONTENT_DIR%\modules

-regsvr32 /s k-clvsd.dll
-regsvr32 /s xactengine2_10.dll
+:: Register video codecs, e.g. required for background videos
+regsvr32 /s %COM_DIR%\k-clvsd.dll

-.\launcher.exe -K .\ddrhook2.dll .\ddr.dll %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-13.xml %*
+
+:: Unregister video codec to avoid conflicts with other/older video codecs crashing different
+:: game versions, e.g. DDR X
+regsvr32 /u /s %COM_DIR%\k-clvsd.dll
--- a/dist/ddr/gamestart-13.bat
+++ b/dist/ddr/gamestart-13.bat
@@ -1,11 +1,42 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist conf\nvram mkdir conf\nvram
-if not exist conf\raw mkdir conf\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set COM_DIR=%CONTENT_DIR%\com
+set MODULES_DIR=%CONTENT_DIR%\modules

-regsvr32 /s k-clvsd.dll
-regsvr32 /s xactengine2_10.dll
+:: Register video codecs, e.g. required for background videos
+regsvr32 /s %COM_DIR%\k-clvsd.dll

-.\launcher.exe -K .\ddrhook2.dll .\ddr.dll %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-13.xml %*
+
+:: Unregister video codec to avoid conflicts with other/older video codecs crashing different
+:: game versions, e.g. DDR X
+regsvr32 /u /s %COM_DIR%\k-clvsd.dll
--- a/dist/ddr/gamestart-14.bat
+++ b/dist/ddr/gamestart-14.bat
@@ -1,14 +1,44 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist conf\nvram mkdir conf\nvram
-if not exist conf\nvram\coin.xml copy prop\coin.xml conf\nvram\coin.xml
-if not exist conf\nvram\eacoin.xml copy prop\eacoin.xml conf\nvram\eacoin.xml
-if not exist conf\nvram\share-config.xml copy prop\share-config.xml conf\nvram\share-config.xml
-if not exist conf\raw mkdir conf\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set COM_DIR=%CONTENT_DIR%\com
+set MODULES_DIR=%CONTENT_DIR%\modules

-regsvr32 /s k-clvsd.dll
-regsvr32 /s xactengine2_10.dll
+:: Register video codecs, e.g. required for background videos
+regsvr32 /s %COM_DIR%\k-clvsd.dll
+regsvr32 /s %COM_DIR%\xactengine2_10.dll

-.\launcher.exe -K .\ddrhook2.dll .\mdxja_945.dll %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-14.xml %*
+
+:: Unregister video codec to avoid conflicts with other/older video codecs crashing different
+:: game versions, e.g. DDR X
+regsvr32 /u /s %COM_DIR%\k-clvsd.dll
+regsvr32 /u /s %COM_DIR%\xactengine2_10.dll
--- a/dist/ddr/gamestart-15.bat
+++ b/dist/ddr/gamestart-15.bat
@@ -1,14 +1,44 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist conf\nvram mkdir conf\nvram
-if not exist conf\nvram\coin.xml copy prop\coin.xml conf\nvram\coin.xml
-if not exist conf\nvram\eacoin.xml copy prop\eacoin.xml conf\nvram\eacoin.xml
-if not exist conf\nvram\share-config.xml copy prop\share-config.xml conf\nvram\share-config.xml
-if not exist conf\raw mkdir conf\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set COM_DIR=%CONTENT_DIR%\com
+set MODULES_DIR=%CONTENT_DIR%\modules

-regsvr32 /s k-clvsd.dll
-regsvr32 /s xactengine2_10.dll
+:: Register video codecs, e.g. required for background videos
+regsvr32 /s %COM_DIR%\k-clvsd.dll
+regsvr32 /s %COM_DIR%\xactengine2_10.dll

-.\launcher.exe -K .\ddrhook2.dll .\mdxja_945.dll %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-15.xml %*
+
+:: Unregister video codec to avoid conflicts with other/older video codecs crashing different
+:: game versions, e.g. DDR X
+regsvr32 /u /s %COM_DIR%\k-clvsd.dll
+regsvr32 /u /s %COM_DIR%\xactengine2_10.dll
--- a/dist/ddr/gamestart-16.bat
+++ b/dist/ddr/gamestart-16.bat
@@ -1,15 +1,44 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist conf\nvram mkdir conf\nvram
-if not exist conf\nvram\ea3-config.xml copy prop\eamuse-config.xml conf\nvram\ea3-config.xml
-if not exist conf\nvram\coin.xml copy prop\coin.xml conf\nvram\coin.xml
-if not exist conf\nvram\eacoin.xml copy prop\eacoin.xml conf\nvram\eacoin.xml
-if not exist conf\nvram\testmode-v.xml copy prop\testmode-v.xml conf\nvram\testmode-v.xml
-if not exist conf\raw mkdir conf\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set COM_DIR=%CONTENT_DIR%\com
+set MODULES_DIR=%CONTENT_DIR%\modules

-regsvr32 /s com\k-clvsd.dll
-regsvr32 /s com\xactengine2_10.dll
+:: Register video codecs, e.g. required for background videos
+regsvr32 /s %COM_DIR%\k-clvsd.dll
+regsvr32 /s %COM_DIR%\xactengine2_10.dll

-.\launcher.exe -H 33554432 -K .\ddrhook2.dll .\arkmdxp3.dll %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-17.xml %*
+
+:: Unregister video codec to avoid conflicts with other/older video codecs crashing different
+:: game versions, e.g. DDR X
+regsvr32 /u /s %COM_DIR%\k-clvsd.dll
+regsvr32 /u /s %COM_DIR%\xactengine2_10.dll
--- a/dist/ddr/gamestart-17.bat
+++ b/dist/ddr/gamestart-17.bat
@@ -0,0 +1,44 @@
+@echo off
+
+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
+cd /d %~dp0
+
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set COM_DIR=%CONTENT_DIR%\com
+set MODULES_DIR=%CONTENT_DIR%\modules
+
+:: Register video codecs, e.g. required for background videos
+regsvr32 /s %COM_DIR%\k-clvsd.dll
+regsvr32 /s %COM_DIR%\xactengine2_10.dll
+
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-17.xml %*
+
+:: Unregister video codec to avoid conflicts with other/older video codecs crashing different
+:: game versions, e.g. DDR X
+regsvr32 /u /s %COM_DIR%\k-clvsd.dll
+regsvr32 /u /s %COM_DIR%\xactengine2_10.dll
--- a/dist/ddr/gamestart-18.bat
+++ b/dist/ddr/gamestart-18.bat
@@ -0,0 +1,44 @@
+@echo off
+
+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
+cd /d %~dp0
+
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set COM_DIR=%CONTENT_DIR%\com
+set MODULES_DIR=%CONTENT_DIR%\modules
+
+:: Register video codecs, e.g. required for background videos
+regsvr32 /s %COM_DIR%\k-clvsd.dll
+regsvr32 /s %COM_DIR%\xactengine2_10.dll
+
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-18.xml %*
+
+:: Unregister video codec to avoid conflicts with other/older video codecs crashing different
+:: game versions, e.g. DDR X
+regsvr32 /u /s %COM_DIR%\k-clvsd.dll
+regsvr32 /u /s %COM_DIR%\xactengine2_10.dll
--- a/dist/ddr/launcher-12.xml
+++ b/dist/ddr/launcher-12.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">31457280</heap_avs>
+                    <heap_std __type="u32">31457280</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>ddr.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">ddrhook2.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/ddr/launcher-13.xml
+++ b/dist/ddr/launcher-13.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">31457280</heap_avs>
+                    <heap_std __type="u32">31457280</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>ddr.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">ddrhook2.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/ddr/launcher-14.xml
+++ b/dist/ddr/launcher-14.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">31457280</heap_avs>
+                    <heap_std __type="u32">31457280</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>mdxja_945.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">ddrhook2.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/ddr/launcher-15.xml
+++ b/dist/ddr/launcher-15.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">31457280</heap_avs>
+                    <heap_std __type="u32">31457280</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>mdxja_945.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">ddrhook2.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/ddr/launcher-16.xml
+++ b/dist/ddr/launcher-16.xml
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                    <file dst="/dev/nvram/testmode-v.xml" src="/prop/testmode-v.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">33554432</heap_avs>
+                    <heap_std __type="u32">1048576</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>arkmdxp3.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">ddrhook2.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/ddr/launcher-17.xml
+++ b/dist/ddr/launcher-17.xml
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                    <file dst="/dev/nvram/testmode-v.xml" src="/prop/testmode-v.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">33554432</heap_avs>
+                    <heap_std __type="u32">1048576</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>arkmdxp3.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">ddrhook2.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/ddr/launcher-18.xml
+++ b/dist/ddr/launcher-18.xml
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                    <file dst="/dev/nvram/testmode-v.xml" src="/prop/testmode-v.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">33554432</heap_avs>
+                    <heap_std __type="u32">1048576</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>arkmdxp3.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">ddrhook2.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/ea3-ident.xml
+++ b/dist/iidx/ea3-ident.xml
@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3_conf>
+    <soft>
+        <model __type="str">LDJ</model>
+        <dest __type="str">J</dest>
+        <spec __type="str">A</spec>
+        <rev __type="str">A</rev>
+        <ext __type="str">2022082400</ext>
+    </soft>
+</ea3_conf>
--- a/dist/iidx/eamuse-server.xml
+++ b/dist/iidx/eamuse-server.xml
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3>
+    <network>
+        <services>http://localhost</services>
+    </network>
+</ea3>
--- a/dist/iidx/gamestart-18.bat
+++ b/dist/iidx/gamestart-18.bat
@@ -1,14 +1,34 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist d mkdir d
-if not exist e mkdir e
-if not exist f mkdir f
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules

-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\nvram\coin.xml copy prop\defaults\coin.xml dev\nvram\coin.xml
-if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin.xml
-if not exist dev\raw mkdir dev\raw
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%

-launcher -K iidxhook4.dll bm2dx.dll --config iidxhook-18.conf %*
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-18.xml --config %BEMANITOOLS_DIR%\iidxhook-18.conf %*
--- a/dist/iidx/gamestart-19.bat
+++ b/dist/iidx/gamestart-19.bat
@@ -1,14 +1,34 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist d mkdir d
-if not exist e mkdir e
-if not exist f mkdir f
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules

-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\nvram\coin.xml copy prop\defaults\coin.xml dev\nvram\coin.xml
-if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin.xml
-if not exist dev\raw mkdir dev\raw
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%

-launcher -K iidxhook5.dll bm2dx.dll --config iidxhook-19.conf %*
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-19.xml --config %BEMANITOOLS_DIR%\iidxhook-19.conf %*
--- a/dist/iidx/gamestart-20.bat
+++ b/dist/iidx/gamestart-20.bat
@@ -1,10 +1,34 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\nvram\coin.xml copy prop\defaults\coin.xml dev\nvram\coin.xml
-if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin.xml
-if not exist dev\raw mkdir dev\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules

-launcher -K iidxhook6.dll bm2dx.dll --config iidxhook-20.conf %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-20.xml --config %BEMANITOOLS_DIR%\iidxhook-20.conf %*
--- a/dist/iidx/gamestart-21.bat
+++ b/dist/iidx/gamestart-21.bat
@@ -1,10 +1,34 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\nvram\coin.xml copy prop\defaults\coin.xml dev\nvram\coin.xml
-if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin.xml
-if not exist dev\raw mkdir dev\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules

-launcher -K iidxhook7.dll bm2dx.dll --config iidxhook-21.conf %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-21.xml --config %BEMANITOOLS_DIR%\iidxhook-21.conf %*
--- a/dist/iidx/gamestart-22.bat
+++ b/dist/iidx/gamestart-22.bat
@@ -1,10 +1,34 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\nvram\coin.xml copy prop\defaults\coin.xml dev\nvram\coin.xml
-if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin.xml
-if not exist dev\raw mkdir dev\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules

-launcher -K iidxhook7.dll bm2dx.dll --config iidxhook-22.conf %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-22.xml --config %BEMANITOOLS_DIR%\iidxhook-22.conf %*
--- a/dist/iidx/gamestart-23.bat
+++ b/dist/iidx/gamestart-23.bat
@@ -1,10 +1,34 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\nvram\coin.xml copy prop\defaults\coin.xml dev\nvram\coin.xml
-if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin.xml
-if not exist dev\raw mkdir dev\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules

-launcher -K iidxhook7.dll bm2dx.dll --config iidxhook-23.conf %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-23.xml --config %BEMANITOOLS_DIR%\iidxhook-23.conf %*
--- a/dist/iidx/gamestart-24.bat
+++ b/dist/iidx/gamestart-24.bat
@@ -1,10 +1,34 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\nvram\coin.xml copy prop\defaults\coin.xml dev\nvram\coin.xml
-if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin.xml
-if not exist dev\raw mkdir dev\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules

-launcher -K iidxhook7.dll bm2dx.dll --config iidxhook-24.conf %*
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-24.xml --config %BEMANITOOLS_DIR%\iidxhook-24.conf %*
--- a/dist/iidx/gamestart-25.bat
+++ b/dist/iidx/gamestart-25.bat
@@ -1,16 +1,34 @@
@echo off
-cd /d %~dp0

-if not exist dev mkdir dev
-if not exist dev\e mkdir dev\e
-if not exist dev\g mkdir dev\g
-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\raw mkdir dev\raw
-if not exist dev\raw\log mkdir dev\raw\log
-if not exist dev\raw\fscache mkdir dev\raw\fscache
+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session

-for /R prop\defaults %%D in (*.*) do (
-    if not exist dev\nvram\%%~nxD copy /y prop\defaults\%%~nxD dev\nvram
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
 )

-launcher -H 134217728 -K iidxhook8.dll bm2dx.dll --config iidxhook-25.conf %*
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
+cd /d %~dp0
+
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules
+
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-25.xml --config %BEMANITOOLS_DIR%\iidxhook-25.conf %*
--- a/dist/iidx/gamestart-26.bat
+++ b/dist/iidx/gamestart-26.bat
@@ -1,16 +1,34 @@
@echo off
-cd /d %~dp0

-if not exist dev mkdir dev
-if not exist dev\e mkdir dev\e
-if not exist dev\g mkdir dev\g
-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\raw mkdir dev\raw
-if not exist dev\raw\log mkdir dev\raw\log
-if not exist dev\raw\fscache mkdir dev\raw\fscache
+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session

-for /R prop\defaults %%D in (*.*) do (
-    if not exist dev\nvram\%%~nxD copy /y prop\defaults\%%~nxD dev\nvram
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
 )

-launcher -H 134217728 -K iidxhook8.dll bm2dx.dll --config iidxhook-26.conf %*
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
+cd /d %~dp0
+
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules
+
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-26.xml --config %BEMANITOOLS_DIR%\iidxhook-26.conf %*
--- a/dist/iidx/gamestart-27.bat
+++ b/dist/iidx/gamestart-27.bat
@@ -1,16 +1,34 @@
@echo off
-cd /d %~dp0

-if not exist dev mkdir dev
-if not exist dev\e mkdir dev\e
-if not exist dev\g mkdir dev\g
-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\raw mkdir dev\raw
-if not exist dev\raw\log mkdir dev\raw\log
-if not exist dev\raw\fscache mkdir dev\raw\fscache
+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session

-for /R prop\defaults %%D in (*.*) do (
-    if not exist dev\nvram\%%~nxD copy /y prop\defaults\%%~nxD dev\nvram
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
 )

-launcher -H 134217728 -B iidxhook9.dll bm2dx.dll --config iidxhook-27.conf %*
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
+cd /d %~dp0
+
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules
+
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-27.xml --config %BEMANITOOLS_DIR%\iidxhook-27.conf %*
--- a/dist/iidx/gamestart-28.bat
+++ b/dist/iidx/gamestart-28.bat
@@ -1,16 +1,34 @@
@echo off
-cd /d %~dp0

-if not exist dev mkdir dev
-if not exist dev\e mkdir dev\e
-if not exist dev\g mkdir dev\g
-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\raw mkdir dev\raw
-if not exist dev\raw\log mkdir dev\raw\log
-if not exist dev\raw\fscache mkdir dev\raw\fscache
+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session

-for /R prop\defaults %%D in (*.*) do (
-    if not exist dev\nvram\%%~nxD copy /y prop\defaults\%%~nxD dev\nvram
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
 )

-launcher -H 134217728 -B iidxhook9.dll bm2dx.dll --config iidxhook-28.conf %*
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
+cd /d %~dp0
+
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules
+
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-28.xml --config %BEMANITOOLS_DIR%\iidxhook-28.conf %*
--- a/dist/iidx/gamestart-29.bat
+++ b/dist/iidx/gamestart-29.bat
@@ -1,16 +1,34 @@
@echo off
-cd /d %~dp0

-if not exist dev mkdir dev
-if not exist dev\e mkdir dev\e
-if not exist dev\g mkdir dev\g
-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\raw mkdir dev\raw
-if not exist dev\raw\log mkdir dev\raw\log
-if not exist dev\raw\fscache mkdir dev\raw\fscache
+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session

-for /R prop\defaults %%D in (*.*) do (
-    if not exist dev\nvram\%%~nxD copy /y prop\defaults\%%~nxD dev\nvram
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
 )

-launcher -H 134217728 -B iidxhook9.dll bm2dx.dll --config iidxhook-29.conf %*
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
+cd /d %~dp0
+
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules
+
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-29.xml --config %BEMANITOOLS_DIR%\iidxhook-29.conf %*
--- a/dist/iidx/gamestart-30.bat
+++ b/dist/iidx/gamestart-30.bat
@@ -1,16 +1,34 @@
@echo off
-cd /d %~dp0

-if not exist dev mkdir dev
-if not exist dev\e mkdir dev\e
-if not exist dev\g mkdir dev\g
-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\raw mkdir dev\raw
-if not exist dev\raw\log mkdir dev\raw\log
-if not exist dev\raw\fscache mkdir dev\raw\fscache
+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session

-for /R prop\defaults %%D in (*.*) do (
-    if not exist dev\nvram\%%~nxD copy /y prop\defaults\%%~nxD dev\nvram
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
 )

-modules\launcher -H 134217728 -B iidxhook9.dll bm2dx.dll --config iidxhook-30.conf %*
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
+cd /d %~dp0
+
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules
+
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-30.xml --config %BEMANITOOLS_DIR%\iidxhook-30.conf %*
--- a/dist/iidx/launcher-18.xml
+++ b/dist/iidx/launcher-18.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">16777216</heap_avs>
+                    <heap_std __type="u32">16777216</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">iidxhook4.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-19.xml
+++ b/dist/iidx/launcher-19.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">16777216</heap_avs>
+                    <heap_std __type="u32">16777216</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">iidxhook5.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-20.xml
+++ b/dist/iidx/launcher-20.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">16777216</heap_avs>
+                    <heap_std __type="u32">16777216</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">iidxhook6.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-21.xml
+++ b/dist/iidx/launcher-21.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">16777216</heap_avs>
+                    <heap_std __type="u32">16777216</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">iidxhook7.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-22.xml
+++ b/dist/iidx/launcher-22.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">16777216</heap_avs>
+                    <heap_std __type="u32">16777216</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">iidxhook7.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-23.xml
+++ b/dist/iidx/launcher-23.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">16777216</heap_avs>
+                    <heap_std __type="u32">16777216</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">iidxhook7.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-24.xml
+++ b/dist/iidx/launcher-24.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">16777216</heap_avs>
+                    <heap_std __type="u32">16777216</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">iidxhook7.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-25.xml
+++ b/dist/iidx/launcher-25.xml
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">134217728</heap_avs>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">iidxhook8.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-26.xml
+++ b/dist/iidx/launcher-26.xml
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">134217728</heap_avs>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">iidxhook8.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-27.xml
+++ b/dist/iidx/launcher-27.xml
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">134217728</heap_avs>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <mounttable_selector __type="str">boot</mounttable_selector>
+                <mounttable>
+                    <vfs name="boot" fstype="fs" src="dev/raw" dst="/dev/raw" opt=""/>
+                    <vfs name="boot" fstype="fs" src="dev/nvram" dst="/dev/nvram" opt=""/>
+                </mounttable>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+    </hook_dlls>
+    <before_hook_dlls>
+      <dll __type="str">iidxhook9.dll</dll>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-28.xml
+++ b/dist/iidx/launcher-28.xml
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">134217728</heap_avs>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <mounttable_selector __type="str">boot</mounttable_selector>
+                <mounttable>
+                    <vfs name="boot" fstype="fs" src="dev/raw" dst="/dev/raw" opt=""/>
+                    <vfs name="boot" fstype="fs" src="dev/nvram" dst="/dev/nvram" opt=""/>
+                </mounttable>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+    </hook_dlls>
+    <before_hook_dlls>
+      <dll __type="str">iidxhook9.dll</dll>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-29.xml
+++ b/dist/iidx/launcher-29.xml
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">134217728</heap_avs>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <mounttable_selector __type="str">boot</mounttable_selector>
+                <mounttable>
+                    <vfs name="boot" fstype="fs" src="dev/raw" dst="/dev/raw" opt=""/>
+                    <vfs name="boot" fstype="fs" src="dev/nvram" dst="/dev/nvram" opt=""/>
+                </mounttable>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+    </hook_dlls>
+    <before_hook_dlls>
+      <dll __type="str">iidxhook9.dll</dll>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/launcher-30.xml
+++ b/dist/iidx/launcher-30.xml
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">134217728</heap_avs>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>bm2dx.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <mounttable_selector __type="str">boot</mounttable_selector>
+                <mounttable>
+                    <vfs name="boot" fstype="fs" src="dev/raw" dst="/dev/raw" opt=""/>
+                    <vfs name="boot" fstype="fs" src="dev/nvram" dst="/dev/nvram" opt=""/>
+                </mounttable>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+    </hook_dlls>
+    <before_hook_dlls>
+      <dll __type="str">iidxhook9.dll</dll>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/iidx/pcbid.xml
+++ b/dist/iidx/pcbid.xml
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3_conf>
+    <id>
+        <softid __type="str">0101020304050607083F</softid>
+        <pcbid __type="str">0101020304050607083F</pcbid>
+    </id>
+</ea3_conf>
--- a/dist/jb/ea3-ident.xml
+++ b/dist/jb/ea3-ident.xml
@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3_conf>
+    <soft>
+        <model __type="str">LDJ</model>
+        <dest __type="str">J</dest>
+        <spec __type="str">A</spec>
+        <rev __type="str">A</rev>
+        <ext __type="str">2022082400</ext>
+    </soft>
+</ea3_conf>
--- a/dist/jb/eamuse-server.xml
+++ b/dist/jb/eamuse-server.xml
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3>
+    <network>
+        <services>http://localhost</services>
+    </network>
+</ea3>
--- a/dist/jb/gamestart-03.bat
+++ b/dist/jb/gamestart-03.bat
@@ -1,11 +1,34 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\nvram\ea3-config.xml copy prop\ea3-config.xml dev\nvram\ea3-config.xml
-if not exist dev\nvram\coin.xml copy prop\defaults\coin.xml dev\nvram\coin.xml
-if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin.xml
-if not exist dev\raw mkdir dev\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules

-launcher -H 33554432 -K jbhook2.dll jubeat.dll -v
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-03.xml -v %*
--- a/dist/jb/gamestart-04.bat
+++ b/dist/jb/gamestart-04.bat
@@ -1,11 +1,34 @@
@echo off

+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
 cd /d %~dp0

-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\nvram\ea3-config.xml copy prop\ea3-config.xml dev\nvram\ea3-config.xml
-if not exist dev\nvram\coin.xml copy prop\defaults\coin.xml dev\nvram\coin.xml
-if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin.xml
-if not exist dev\raw mkdir dev\raw
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules

-launcher -H 33554432 -K jbhook3.dll jubeat.dll
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-04.xml %*
--- a/dist/jb/launcher-03.xml
+++ b/dist/jb/launcher-03.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">33554432</heap_avs>
+                    <heap_std __type="u32">33554432</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>jubeat.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">jbhook2.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/jb/launcher-04.xml
+++ b/dist/jb/launcher-04.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">33554432</heap_avs>
+                    <heap_std __type="u32">33554432</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>jubeat.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">jbhook3.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/jb/pcbid.xml
+++ b/dist/jb/pcbid.xml
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3_conf>
+    <id>
+        <softid __type="str">0101020304050607083F</softid>
+        <pcbid __type="str">0101020304050607083F</pcbid>
+    </id>
+</ea3_conf>
--- a/dist/sdvx/ea3-ident.xml
+++ b/dist/sdvx/ea3-ident.xml
@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3_conf>
+    <soft>
+        <model __type="str">LDJ</model>
+        <dest __type="str">J</dest>
+        <spec __type="str">A</spec>
+        <rev __type="str">A</rev>
+        <ext __type="str">2022082400</ext>
+    </soft>
+</ea3_conf>
--- a/dist/sdvx/eamuse-server.xml
+++ b/dist/sdvx/eamuse-server.xml
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3>
+    <network>
+        <services>http://localhost</services>
+    </network>
+</ea3>
--- a/dist/sdvx/gamestart.bat
+++ b/dist/sdvx/gamestart.bat
@@ -8,3 +8,38 @@ if not exist dev\nvram\eacoin.xml copy prop\defaults\eacoin.xml dev\nvram\eacoin
 if not exist dev\raw mkdir dev\raw

 launcher -K sdvxhook.dll soundvoltex.dll %*
+
+@echo off
+
+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session
+
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
+)
+
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
+cd /d %~dp0
+
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules
+
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher.xml %*
--- a/dist/sdvx/launcher.xml
+++ b/dist/sdvx/launcher.xml
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">16777216</heap_avs>
+                    <heap_std __type="u32">16777216</heap_std>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>soundvoltex.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">sdvxhook.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/sdvx/pcbid.xml
+++ b/dist/sdvx/pcbid.xml
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3_conf>
+    <id>
+        <softid __type="str">0101020304050607083F</softid>
+        <pcbid __type="str">0101020304050607083F</pcbid>
+    </id>
+</ea3_conf>
--- a/dist/sdvx5/ea3-ident.xml
+++ b/dist/sdvx5/ea3-ident.xml
@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3_conf>
+    <soft>
+        <model __type="str">LDJ</model>
+        <dest __type="str">J</dest>
+        <spec __type="str">A</spec>
+        <rev __type="str">A</rev>
+        <ext __type="str">2022082400</ext>
+    </soft>
+</ea3_conf>
--- a/dist/sdvx5/eamuse-server.xml
+++ b/dist/sdvx5/eamuse-server.xml
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3>
+    <network>
+        <services>http://localhost</services>
+    </network>
+</ea3>
--- a/dist/sdvx5/gamestart-cn.bat
+++ b/dist/sdvx5/gamestart-cn.bat
@@ -1,17 +1,34 @@
@echo off
-cd /d %~dp0

-if not exist dev mkdir dev
-if not exist dev\e mkdir dev\e
-if not exist dev\g mkdir dev\g
-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\raw mkdir dev\raw
-if not exist dev\raw\c.dest echo $null >> dev\raw\c.dest
-if not exist dev\raw\log mkdir dev\raw\log
-if not exist dev\raw\fscache mkdir dev\raw\fscache
+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session

-for /R prop\defaults %%D in (*.*) do (
-    if not exist dev\nvram\%%~nxD copy /y prop\defaults\%%~nxD dev\nvram
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
 )

-launcher -H 268435456 -K sdvxhook2-cn.dll soundvoltex.dll --config sdvxhook2-cn.conf %*
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
+cd /d %~dp0
+
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules
+
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher-cn.xml --config %BEMANITOOLS_DIR%\sdvxhook2-cn.conf %*
--- a/dist/sdvx5/gamestart.bat
+++ b/dist/sdvx5/gamestart.bat
@@ -1,16 +1,34 @@
@echo off
-cd /d %~dp0

-if not exist dev mkdir dev
-if not exist dev\e mkdir dev\e
-if not exist dev\g mkdir dev\g
-if not exist dev\nvram mkdir dev\nvram
-if not exist dev\raw mkdir dev\raw
-if not exist dev\raw\log mkdir dev\raw\log
-if not exist dev\raw\fscache mkdir dev\raw\fscache
+:: Game doesn't work properly when not run with administrator privileges
+>nul 2>&1 net session

-for /R prop\defaults %%D in (*.*) do (
-    if not exist dev\nvram\%%~nxD copy /y prop\defaults\%%~nxD dev\nvram
+if %errorlevel% neq 0 (
+    echo This script requires administrative privileges.
+    echo Please run the script as an administrator.
+    pause
+    exit 1
 )

-launcher -H 268435456 -K sdvxhook2.dll soundvoltex.dll --config sdvxhook2.conf %*
+:: Script expects to be located in a subfolder "bemanitools" in the root folder
+:: (contents/) next to the folders modules, data etc.
+cd /d %~dp0
+
+:: Script expects to be located in the root folder (contents/) next to the
+:: folders modules, data etc.
+set CONTENT_DIR=%CD%\..
+set BEMANITOOLS_DIR=%CONTENT_DIR%\bemanitools
+set MODULES_DIR=%CONTENT_DIR%\modules
+
+:: Keep that data vanilla, no need to copy these around anymore
+:: Just add them to the env PATH so launcher can find the libs and game executable
+:: Remark: This also requires admin privileges to propage correctly to launcher
+set PATH=^
+%MODULES_DIR%;^
+%BEMANITOOLS_DIR%;^
+%PATH%
+
+:: Current working dir is the game's root folder
+cd /d %CONTENT_DIR%
+
+%BEMANITOOLS_DIR%\launcher %BEMANITOOLS_DIR%\launcher.xml --config %BEMANITOOLS_DIR%\sdvxhook2.conf %*
--- a/dist/sdvx5/launcher-cn.xml
+++ b/dist/sdvx5/launcher-cn.xml
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">268435456</heap_avs>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>soundvoltex.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">sdvxhook2-cn.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/sdvx5/launcher.xml
+++ b/dist/sdvx5/launcher.xml
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<launcher version="1">
+  <bootstrap>
+    <selector __type="str">bemanitools_local_fs</selector>
+    <config kind="inline">
+      <config>
+        <startup>
+            <bemanitools_local_fs>
+                <default>
+                    <file dst="/dev/nvram/ea3-config.xml" src="/prop/eamuse-config.xml" />
+                    <file dst="/dev/nvram/coin.xml" src="/prop/coin.xml" />
+                    <file dst="/dev/nvram/eacoin.xml" src="/prop/eacoin.xml" />
+                </default>
+                <boot>
+                    <file>prop/avs-config.xml</file>
+                    <heap_avs __type="u32">268435456</heap_avs>
+                </boot>
+                <log>
+                    <level>info</level>
+                </log>
+                <eamuse>
+                    <file>/dev/nvram/ea3-config.xml</file>
+                </eamuse>
+                <component>
+                    <file>soundvoltex.dll</file>
+                    <param></param>
+                </component>
+            </bemanitools_local_fs>
+        </startup>
+      </config>
+    </config>
+  </bootstrap>
+  <ea3_ident>
+    <config kind="file">bemanitools/ea3-ident.xml</config>
+    <config kind="file">bemanitools/ea3-license.xml</config>
+  </ea3_ident>
+  <avs>
+    <config kind="inline">
+        <config>
+            <fs>
+                <root>
+                    <device __type="str">.</device>
+                </root>
+                <nvram>
+                    <device __type="str">dev/nvram</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </nvram>
+                <raw>
+                    <device __type="str">dev/raw</device>
+                    <fstype __type="str">fs</fstype>
+                    <option __type="str">vf=1,posix=1</option>
+                </raw>
+            </fs>
+        </config>
+    </config>
+  </avs>
+  <eamuse>
+    <config kind="file">bemanitools/ea3-service.xml</config>
+  </eamuse>
+  <hook>
+    <hook_dlls>
+        <dll __type="str">sdvxhook2.dll</dll>
+    </hook_dlls>
+    <before_hook_dlls>
+    </before_hook_dlls>
+    <iat_hook_dlls>
+    </iat_hook_dlls>
+  </hook>
+  <debug>
+    <remote_debugger __type="bool">0</remote_debugger>
+    <log_property_configs __type="bool">0</log_property_configs>
+  </debug>
+</launcher>
--- a/dist/sdvx5/pcbid.xml
+++ b/dist/sdvx5/pcbid.xml
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3_conf>
+    <id>
+        <softid __type="str">0101020304050607083F</softid>
+        <pcbid __type="str">0101020304050607083F</pcbid>
+    </id>
+</ea3_conf>
--- a/dist/shared/ea3-ident.xml
+++ b/dist/shared/ea3-ident.xml
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3_conf>
+    <soft>
+        <!-- USER TODO: Change these accordingly to match the specifications of the game and version you are running -->
+        <model __type="str">000</model>
+        <dest __type="str">A</dest>
+        <spec __type="str">A</spec>
+        <rev __type="str">A</rev>
+        <ext __type="str">1969032100</ext>
+    </soft>
+</ea3_conf>
--- a/dist/shared/ea3-license.xml
+++ b/dist/shared/ea3-license.xml
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3_conf>
+    <id>
+        <!-- USER TODO: Change accordingly to comply with your favorite eamuse service -->
+        <softid __type="str">0101020304050607083F</softid>
+        <pcbid __type="str">0101020304050607083F</pcbid>
+    </id>
+</ea3_conf>
--- a/dist/shared/ea3-service.xml
+++ b/dist/shared/ea3-service.xml
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="Shift-JIS"?>
+<ea3>
+    <network>
+        <!-- USER TODO: Change to your favorite eamuse service URL -->
+        <services>http://localhost</services>
+    </network>
+</ea3>
--- a/doc/README.md
+++ b/doc/README.md
@@ -4,31 +4,31 @@ This folder contains various types of documentation.

 Table of contents:

-* Game
-  * [Error codes](game-error-codes.md): List of bemani game specific error codes that you might
+- Game
+  - [Error codes](game-error-codes.md): List of bemani game specific error codes that you might
    encounter during boot or gameplay with troubleshooting information
-* Key tools
-  * [Inject](inject.md): Readme for one of BT5's key applications, `inject.exe`
-  * [Launcher](launcher.md): Readme for another one of BT5's key applications, `launcher.exe`
-  * [Tools](tools/README.md): Documentation for additional user and development tooling
-* Game hooks
-  * [ddrhook](ddrhook/README.md): Documentation relevant to `ddrhook` implementations
-  * [iidxhook](iidxhook/README.md): Documentation relevant to `iidxhook` implementations
-  * [jbhook](jbhook/README.md): Documentation relevant to `jbhook` implementations
-  * [popnhook](popnhook/README.md): Documentation relevant to `popnhook` implementations
-  * [sdvxhook](sdvxhook/README.md): Documentation relevant to `sdvxhook` implementations
-* Development
-  * [API](api.md): Available APIs and IO (hardware) implementations for BT5 and instructions how
-    to use them
-  * [Architecture](architecture.md): Outline of BT5's architecture, how things are designed and why
-  * [Development](development.md): Development environment, building, releasing, etc.
-  * [Developer documentation](dev/README.md): Various lose documentation/notes by developers
-  * [Tools](tools/README.md): Documentation for additional user and development tooling
+- Key tools
+  - [Inject](inject.md): Readme for one of BT5's key applications, `inject.exe`
+  - [Launcher](launcher.md): Readme for another one of BT5's key applications, `launcher.exe`
+  - [Tools](tools/README.md): Documentation for additional user and development tooling
+- Game hooks
+  - [ddrhook](ddrhook/README.md): Documentation relevant to `ddrhook` implementations
+  - [iidxhook](iidxhook/README.md): Documentation relevant to `iidxhook` implementations
+  - [jbhook](jbhook/README.md): Documentation relevant to `jbhook` implementations
+  - [popnhook](popnhook/README.md): Documentation relevant to `popnhook` implementations
+  - [sdvxhook](sdvxhook/README.md): Documentation relevant to `sdvxhook` implementations
+- Development
+  - [API](api.md): Available APIs and IO (hardware) implementations for BT5 and instructions how to
+    use them
+  - [Architecture](architecture.md): Outline of BT5's architecture, how things are designed and why
+  - [Development](development.md): Development environment, building, releasing, etc.
+  - [Developer documentation](dev/README.md): Various lose documentation/notes by developers
+  - [Tools](tools/README.md): Documentation for additional user and development tooling

 ## Further external documentation

-A list of external documentation that can be useful when dealing with bemanitools,
-supported data and hardware.
+A list of external documentation that can be useful when dealing with bemanitools, supported data
+and hardware.

-* [arcade-docs](https://github.com/Shizmob/arcade-docs): An open (to read and contribute) repository
+- [arcade-docs](https://github.com/Shizmob/arcade-docs): An open (to read and contribute) repository
  of arcade hardware and software documentation
--- a/doc/api.md
+++ b/doc/api.md
@@ -1,16 +1,16 @@
 # Bemanitools API

-Bemanitools introduces interfaces abstracting the IO hardware of many games. This is used to implement support for
-non-intended IO devices from simple keyboard support, standard gamecontrollers to custom IO boards or using real
-hardware with the games (e.g. support for real legacy hardware).
+Bemanitools introduces interfaces abstracting the IO hardware of many games. This is used to
+implement support for non-intended IO devices from simple keyboard support, standard gamecontrollers
+to custom IO boards or using real hardware with the games (e.g. support for real legacy hardware).

 For a list of already supported and included hardware by game, see the next section.

-The BT5 API separates main game IO hardware like buttons, turn tables, spinners, lights etc. (bstio, iidxio, ...) from
-eamuse hardware like 10-key pads and card readers (eamio).
+The BT5 API separates main game IO hardware like buttons, turn tables, spinners, lights etc. (bstio,
+iidxio, ...) from eamuse hardware like 10-key pads and card readers (eamio).

-If you want to write an implementation for your own custom piece of hardware, check out the SDK (*bemanitools*
-sub-folder) in the source code (src.zip).
+If you want to write an implementation for your own custom piece of hardware, check out the SDK
+(*bemanitools* sub-folder) in the source code (src.zip).

 ## Implementations

@@ -18,35 +18,35 @@ sub-folder) in the source code (src.zip).

 The following implementations are already shipped with BT5.

-* BeatStream
-    * bstio.dll (default): Keyboard, joystick and mouse input
-* Dance Dance Revolution
-    * ddrio.dll (default): Keyboard, joystick and mouse input
-    * [ddrio-p3io.dll](ddrhook/ddrio-p3io.md): DDR P3IO (Dragon PCB) + EXTIO hardware
-    * ddrio-mm.dll: Minimaid hardware
-    * [ddrio-smx.dll](ddrhook/ddrio-smx.md): StepManiaX platforms
-    * [ddrio-async](ddrhook/ddrio-async.md): Wrapper/shim library to drive another ddrio in
-      a dedicated IO thread
-* Beatmania IIDX
-    * iidxio.dll (default): Keyboard, joystick and mouse input
-    * [iidxio-bio2.dll](iidxhook/iidxio-bio2.md): BIO2 driver
-    * [iidxio-ezusb.dll](iidxhook/iidxio-ezusb.md): Ezusb (C02 IO) driver
-    * [iidxio-ezusb2.dll](iidxhook/iidxio-ezusb2.md): Ezusb FX2 (IO2) driver
-* jubeat
-    * jbio.dll (default): Keyboard, joystick and mouse input
-* pop'n music
-    * popnio.dll (default): Keyboard, joystick and mouse input
-* SOUND VOLTEX
-    * sdvxio.dll (default): Keyboard, joystick and mouse input
-    * [sdvxio-bio2.dll](sdvxhook/sdvxio-bio2.md): BIO2 driver
-    * [sdvxio-kfca.dll](sdvxhook/sdvxio-kfca.md): KFCA IO board driver
+- BeatStream
+  - bstio.dll (default): Keyboard, joystick and mouse input
+- Dance Dance Revolution
+  - ddrio.dll (default): Keyboard, joystick and mouse input
+  - [ddrio-p3io.dll](ddrhook/ddrio-p3io.md): DDR P3IO (Dragon PCB) + EXTIO hardware
+  - ddrio-mm.dll: Minimaid hardware
+  - [ddrio-smx.dll](ddrhook/ddrio-smx.md): StepManiaX platforms
+  - [ddrio-async](ddrhook/ddrio-async.md): Wrapper/shim library to drive another ddrio in a
+    dedicated IO thread
+- Beatmania IIDX
+  - iidxio.dll (default): Keyboard, joystick and mouse input
+  - [iidxio-bio2.dll](iidxhook/iidxio-bio2.md): BIO2 driver
+  - [iidxio-ezusb.dll](iidxhook/iidxio-ezusb.md): Ezusb (C02 IO) driver
+  - [iidxio-ezusb2.dll](iidxhook/iidxio-ezusb2.md): Ezusb FX2 (IO2) driver
+- jubeat
+  - jbio.dll (default): Keyboard, joystick and mouse input
+- pop'n music
+  - popnio.dll (default): Keyboard, joystick and mouse input
+- SOUND VOLTEX
+  - sdvxio.dll (default): Keyboard, joystick and mouse input
+  - [sdvxio-bio2.dll](sdvxhook/sdvxio-bio2.md): BIO2 driver
+  - [sdvxio-kfca.dll](sdvxhook/sdvxio-kfca.md): KFCA IO board driver

 ### Eamuse readers

 Eamuse hardware support is implemented separately:

-* eamio.dll (default): Keyboard and joystick input
-* eamio-icca.dll: Slotted/wave pass readers, required for old games with magnetic stripe cards
+- eamio.dll (default): Keyboard and joystick input
+- eamio-icca.dll: Slotted/wave pass readers, required for old games with magnetic stripe cards

 #### ICCA readers for IIDX and port config in device manager

@@ -55,24 +55,27 @@ communication with the readers will fail if the settings do not align with how t
 bemanitools wants to operate them.

 Use built-in ports on your mainboard if available but an external USB to serial port dongle also
-works. 
+works.

-* Assign `COM1` to the COM port the card readers are connected to.
-* Ensure that the following settings for the COM port you are going to use are 
-set
-  * BAUD rate 57600
-  * Data bits 8
-  * Parity None
-  * Stop bits 1
-  * Flow control None.
+- Assign `COM1` to the COM port the card readers are connected to.
+- Ensure that the following settings for the COM port you are going to use are set
+  - BAUD rate 57600
+  - Data bits 8
+  - Parity None
+  - Stop bits 1
+  - Flow control None.

 ## Development notes

-A DEF file for geninput.dll is included. To convert the DEF into an import library suitable for use with Visual C++, run
+A DEF file for geninput.dll is included. To convert the DEF into an import library suitable for use
+with Visual C++, run
+
 ```
 lib /machine:i386 /def:geninput.def
 ```
+
 from the Visual C++ command line. If you're using mingw then use dlltool:
+
 ```
 dlltool -d geninput.def -l geninput.a
-```
+```
--- a/doc/architecture.md
+++ b/doc/architecture.md
@@ -1,203 +1,239 @@
 # Bemanitools architecture
-This document gives you an overview of the architecture of Bemanitools (5). Why do we need this? This helps document the
-various design decisions and how everything comes together, in the end. At some point when things are evolving and other
-developers want to pick up the project, this might give them answers to why some things were done well or not so well.
-This allows them to iterate on the current design (document) to analyze if a change they want to apply might work out
-or not.

-Anway, enough preface...I guess you got the idea. This document will be split into several sections which address
-different aspects of the architecture.
+This document gives you an overview of the architecture of Bemanitools (5). Why do we need this?
+This helps document the various design decisions and how everything comes together, in the end. At
+some point when things are evolving and other developers want to pick up the project, this might
+give them answers to why some things were done well or not so well. This allows them to iterate on
+the current design (document) to analyze if a change they want to apply might work out or not.
+
+Anway, enough preface...I guess you got the idea. This document will be split into several sections
+which address different aspects of the architecture.

 ## The big picture
+
 TODO create a graphic that presents the key modules and ideas.

 ## Detouring library functions, IAT hooking
-One of Bemanitools's goals is to avoid patching of executables, libraries or any game data and instead rely on
-intercepting calls to libraries to patch bugs or introduce new features. To support a game on a non native platform
-transparently, e.g. your home desktop, this allows us to intercept I/O communication to emulate hardware or
-files/filesystem features the game expects to be available.

-We create a so called "hook library/hook.dll" which gets injected to the target process (the game) before the game
-runs any of its application code. This is well known by the terms of dll injection and will not be further discussed
-here (google it). The injected dll will replace the function addresses in the IATs to detour any calls to our own
-handler functions before, eventually, calling the real function. This way, we can intercept the call and do cool things.
+One of Bemanitools's goals is to avoid patching of executables, libraries or any game data and
+instead rely on intercepting calls to libraries to patch bugs or introduce new features. To support
+a game on a non native platform transparently, e.g. your home desktop, this allows us to intercept
+I/O communication to emulate hardware or files/filesystem features the game expects to be available.
+
+We create a so called "hook library/hook.dll" which gets injected to the target process (the game)
+before the game runs any of its application code. This is well known by the terms of dll injection
+and will not be further discussed here (google it). The injected dll will replace the function
+addresses in the IATs to detour any calls to our own handler functions before, eventually, calling
+the real function. This way, we can intercept the call and do cool things.

 These features are covered by the modules in the following subfolders in src/main:
-* hook: Essentially, this is capnhook: https://github.com/decafcode/capnhook. General tools for hooking Win32 API calls.
-* hooklib: Some additional helper modules to take care of specific issues in Bemanitools, e.g. rs232 related stuff for
-ACIO.
+
+- hook: Essentially, this is capnhook: https://github.com/decafcode/capnhook. General tools for
+  hooking Win32 API calls.
+- hooklib: Some additional helper modules to take care of specific issues in Bemanitools, e.g. rs232
+  related stuff for ACIO.

 Check the modules for details.

 ## Hooking and IRP
-IRP stands for "I/O request packet" and is a kernel mode structure used in Windows drivers for communication with the
-OS. The data structure describes an I/O request with parameters for that request avoiding function calls with large
-number of arguments to a driver.

-We make use of that "IRP pattern" by creating a flexible and maintainable abstraction layer for the following hooking
-modules:
-* iohook: Hook I/O (e.g. file) related calls
-* d3d9: Hook d3d9 graphics API calls
+IRP stands for "I/O request packet" and is a kernel mode structure used in Windows drivers for
+communication with the OS. The data structure describes an I/O request with parameters for that
+request avoiding function calls with large number of arguments to a driver.

-An IRP handler is implemented to handle selected IRP calls based on the specified operation type. IRP handlers can be
-chained which allows splitting up different features/interceptors to different functions and modules allowing you to
-create a clear structure. At the end of the forwarding chain, you the real API function that maps to the abstracted
-operation is called. However, a handler can decide at any time to not forward calls which allows you to implement
-emulation of access to selected files or I/O devices.
+We make use of that "IRP pattern" by creating a flexible and maintainable abstraction layer for the
+following hooking modules:
+
+- iohook: Hook I/O (e.g. file) related calls
+- d3d9: Hook d3d9 graphics API calls
+
+An IRP handler is implemented to handle selected IRP calls based on the specified operation type.
+IRP handlers can be chained which allows splitting up different features/interceptors to different
+functions and modules allowing you to create a clear structure. At the end of the forwarding chain,
+you the real API function that maps to the abstracted operation is called. However, a handler can
+decide at any time to not forward calls which allows you to implement emulation of access to
+selected files or I/O devices.

 Modules that make use of this:
-* iidxhook-util/d3d9
-* ezusb-emu/device
-* ezusb2-emu/device
-* acioemu/emu
+
+- iidxhook-util/d3d9
+- ezusb-emu/device
+- ezusb2-emu/device
+- acioemu/emu

 ## Bemanitools's hook libraries, let's glue everything together
-Bemanitools dlls to be injected into target game processes are refered to as "hook dlls" and come in different flavours
-targetting different games and often different versions of the same game (series), for example:
-* ddrhook: Hook dll for Dance Dance Revolution games
-* iidxhook1-8: Hook dlls for Beatmania IIDX, we are currently at 8 different implementations due to the various
-iterations the game went through, related to software and hardware.
-* sdvxhook: Hook dll for SoundVoltex series

-The following sub-sections will give you some brief insights on each hook implementation and what modules were used.
+Bemanitools dlls to be injected into target game processes are refered to as "hook dlls" and come in
+different flavours targetting different games and often different versions of the same game
+(series), for example:
+
+- ddrhook: Hook dll for Dance Dance Revolution games
+- iidxhook1-8: Hook dlls for Beatmania IIDX, we are currently at 8 different implementations due to
+  the various iterations the game went through, related to software and hardware.
+- sdvxhook: Hook dll for SoundVoltex series
+
+The following sub-sections will give you some brief insights on each hook implementation and what
+modules were used.

 ### bsthook
+
 TODO

 ### ddrhook
+
 TODO

 ### iidxhook
-IIDX went through so many hard- and software iterations, it's actually amazing that the development team(s) refactored
-and improved parts of the game and hardware with each iteration. However, when facing emulation and supporting
-compatibility to legacy OS platforms, it can't get any worse. On the bright side, IIDX helped shaping Bemanitools a lot
-and created a solid foundation other games can build on.

-Because of that, we have 8 iidxhook implementations supporting sometimes different software features/fixes and
-hardware. The following sub-sub-sections list the most relevant aspects and modules to point out common and different
-higher level features.
+IIDX went through so many hard- and software iterations, it's actually amazing that the development
+team(s) refactored and improved parts of the game and hardware with each iteration. However, when
+facing emulation and supporting compatibility to legacy OS platforms, it can't get any worse. On the
+bright side, IIDX helped shaping Bemanitools a lot and created a solid foundation other games can
+build on.

-Essentially, the main module file of each iidxhook implementation just glues the APIs of the modules it requires
-together. An additional configuration layer allows users to tweak some of the features.
+Because of that, we have 8 iidxhook implementations supporting sometimes different software
+features/fixes and hardware. The following sub-sub-sections list the most relevant aspects and
+modules to point out common and different higher level features.

-TODO go into some more detail about some differences in the hook modules, e.g. 18 to 19 look identical
-> but different AVS versions
+Essentially, the main module file of each iidxhook implementation just glues the APIs of the modules
+it requires together. An additional configuration layer allows users to tweak some of the features.
+
+TODO go into some more detail about some differences in the hook modules, e.g. 18 to 19 look
+identical -> but different AVS versions

 #### iidxhook1 (9-12)
-* Ezusb C02 I/O emulation
-    * Setupapi emulation
-    * Full security emulation with SRAM and round plugs
-    * Full serial emulation for magstripe card readers
-    * Full game essential I/O emulation
-* d3d8 patching and extended features (superseded by d3d9 hook module + d3d8to9 wrapper)
-* clock patching
-* Font patching for Japanese chars
-* Network related patches to enable eamuse to custom servers
-* Filesystem patches to detour E and F backup drives for settings
+
+- Ezusb C02 I/O emulation
+  - Setupapi emulation
+  - Full security emulation with SRAM and round plugs
+  - Full serial emulation for magstripe card readers
+  - Full game essential I/O emulation
+- d3d8 patching and extended features (superseded by d3d9 hook module + d3d8to9 wrapper)
+- clock patching
+- Font patching for Japanese chars
+- Network related patches to enable eamuse to custom servers
+- Filesystem patches to detour E and F backup drives for settings

 #### iidxhook2 (13)
-* Ezusb C02 I/O emulation
-    * Setupapi emulation
-    * Full security emulation with SRAM and round plugs
-    * Full game essential I/O emulation
-* ACIO ICCA card reader emulation, slotted readers
-* d3d8 patching and extended features (superseded by d3d9 hook module + d3d8to9 wrapper)
-* clock patching
-* Font patching for Japanese chars
-* Network related patches to enable eamuse to custom servers
-* Filesystem patches to detour E and F backup drives for settings
+
+- Ezusb C02 I/O emulation
+  - Setupapi emulation
+  - Full security emulation with SRAM and round plugs
+  - Full game essential I/O emulation
+- ACIO ICCA card reader emulation, slotted readers
+- d3d8 patching and extended features (superseded by d3d9 hook module + d3d8to9 wrapper)
+- clock patching
+- Font patching for Japanese chars
+- Network related patches to enable eamuse to custom servers
+- Filesystem patches to detour E and F backup drives for settings

 #### iidxhook3 (14-17)
-* Ezusb IO2 I/O emulation
-    * Setupapi emulation
-    * Full security emulation with SRAM and round plugs
-    * Full game essential I/O emulation
-* ACIO ICCA card reader emulation, slotted readers
-* d3d9 patching and extended features
-* Font patching for Japanese chars
-* Network related patches to enable eamuse to custom servers
-* Filesystem patches to detour E and F backup drives for settings
+
+- Ezusb IO2 I/O emulation
+  - Setupapi emulation
+  - Full security emulation with SRAM and round plugs
+  - Full game essential I/O emulation
+- ACIO ICCA card reader emulation, slotted readers
+- d3d9 patching and extended features
+- Font patching for Japanese chars
+- Network related patches to enable eamuse to custom servers
+- Filesystem patches to detour E and F backup drives for settings

 #### iidxhook4 (18)
-* Ezusb IO2 I/O emulation
-    * Setupapi emulation
-    * Full game essential I/O emulation
-* ACIO ICCA card reader emulation, slotted readers
-* d3d9 patching and extended features
-* Font patching for Japanese chars
-* Filesystem patches to detour E and F backup drives for settings
+
+- Ezusb IO2 I/O emulation
+  - Setupapi emulation
+  - Full game essential I/O emulation
+- ACIO ICCA card reader emulation, slotted readers
+- d3d9 patching and extended features
+- Font patching for Japanese chars
+- Filesystem patches to detour E and F backup drives for settings

 #### iidxhook4-cn (18 CN)
-* Ezusb IO2 I/O emulation
-  * Setupapi emulation
-  * Full security emulation with SRAM and round plugs
-  * Full game essential I/O emulation
-* d3d9 patching and extended features
-* Font patching for Japanese chars
-* Filesystem patches to detour E and F backup drives for settings
+
+- Ezusb IO2 I/O emulation
+  - Setupapi emulation
+  - Full security emulation with SRAM and round plugs
+  - Full game essential I/O emulation
+- d3d9 patching and extended features
+- Font patching for Japanese chars
+- Filesystem patches to detour E and F backup drives for settings

 #### iidxhook5 (19)
-* Ezusb IO2 I/O emulation
-    * Setupapi emulation
-    * Full game essential I/O emulation
-* ACIO ICCA card reader emulation, wave pass readers
-* d3d9 patching and extended features
-* Font patching for Japanese chars
-* Filesystem patches to detour E and F backup drives for settings
+
+- Ezusb IO2 I/O emulation
+  - Setupapi emulation
+  - Full game essential I/O emulation
+- ACIO ICCA card reader emulation, wave pass readers
+- d3d9 patching and extended features
+- Font patching for Japanese chars
+- Filesystem patches to detour E and F backup drives for settings

 #### iidxhook5-cn (20 CN)
-* Ezusb IO2 I/O emulation
-  * Setupapi emulation
-  * Full security emulation with SRAM and round plugs
-  * Full game essential I/O emulation
-* d3d9 patching and extended features
-* Font patching for Japanese chars
-* Filesystem patches to detour E and F backup drives for settings
+
+- Ezusb IO2 I/O emulation
+  - Setupapi emulation
+  - Full security emulation with SRAM and round plugs
+  - Full game essential I/O emulation
+- d3d9 patching and extended features
+- Font patching for Japanese chars
+- Filesystem patches to detour E and F backup drives for settings

 #### iidxhook6 (20)
-* Ezusb IO2 I/O emulation
-    * Setupapi emulation
-    * Full game essential I/O emulation
-* ACIO ICCA card reader emulation, wave pass readers
-* d3d9 patching and extended features
-* Font patching for Japanese chars
+
+- Ezusb IO2 I/O emulation
+  - Setupapi emulation
+  - Full game essential I/O emulation
+- ACIO ICCA card reader emulation, wave pass readers
+- d3d9 patching and extended features
+- Font patching for Japanese chars

 #### iidxhook7 (21-24)
-* Ezusb IO2 I/O emulation
-    * Setupapi emulation
-    * Full game essential I/O emulation
-* ACIO ICCA card reader emulation, wave pass readers
-* d3d9 patching and extended features
-* Font patching for Japanese chars
+
+- Ezusb IO2 I/O emulation
+  - Setupapi emulation
+  - Full game essential I/O emulation
+- ACIO ICCA card reader emulation, wave pass readers
+- d3d9 patching and extended features
+- Font patching for Japanese chars

 #### iidxhook8 (25-26)
-* ACIO BIO2 I/O emulation
-    * Setupapi emulation
-    * Full game essential I/O emulation
-* ACIO ICCA card reader emulation, wave pass readers
-* d3d9 patching and extended features
-* Font patching for Japanese chars
+
+- ACIO BIO2 I/O emulation
+  - Setupapi emulation
+  - Full game essential I/O emulation
+- ACIO ICCA card reader emulation, wave pass readers
+- d3d9 patching and extended features
+- Font patching for Japanese chars

 ### jbhook
+
 TODO

 ### popnhook
+
 TODO

 ### sdvxhook
+
 TODO

 ## The ezusb (emulation) stack
+
 TODO

 ## The ACIO (emulation) stack
+
 TODO

 ## BT5 API
+
 TODO

 ## AVS and launcher
+
 TODO

 ## Inject
-TODO
+
+TODO
--- a/doc/ddrhook/README.md
+++ b/doc/ddrhook/README.md
@@ -1,55 +1,49 @@
 # ddrhook

-ddrhook is a collection of hook libraries for "Dance Dance Revoluion" providing
-emulation and various patches to run these games on non BemaniPC hardware and
-newer Windows versions.
+ddrhook is a collection of hook libraries for "Dance Dance Revoluion" providing emulation and
+various patches to run these games on non BemaniPC hardware and newer Windows versions.

 The hook libraries must be bootstrapped either using [inject](../inject.md) or
-[launcher](../launcher.md) depending on the version you want to run. Further
-instructions are given in dedicated readme files for each ddrhook version
-(see below).
+[launcher](../launcher.md) depending on the version you want to run. Further instructions are given
+in dedicated readme files for each ddrhook version (see below).

 ## Versions

-ddrhook comes in a few different flavors. The game and its engine changed over
-the years. Some game versions might require patches/parameters enabled which
-others don't need or have different AVS versions. Here is the list of supported 
-games:
+ddrhook comes in a few different flavors. The game and its engine changed over the years. Some game
+versions might require patches/parameters enabled which others don't need or have different AVS
+versions. Here is the list of supported games:

-* [ddrhook1](ddrhook1.md): X, X2 (US/EU regions)
-* [ddrhook2](ddrhook2.md): X2 (JP region), X3 vs. 2ndMIX, 2013, 2014, A
+- [ddrhook1](ddrhook1.md): X, X2 (US/EU regions)
+- [ddrhook2](ddrhook2.md): X2 (JP region), X3 vs. 2ndMIX, 2013, 2014, A

-When building bemanitools, independent packages are created for each set of games
-which are ready to be dropped on top of vanilla AC data dumps. We recommend
-using pristine dumps to avoid any conflicts with other hardcoded hacks or
-binary patches.
+When building bemanitools, independent packages are created for each set of games which are ready to
+be dropped on top of vanilla AC data dumps. We recommend using pristine dumps to avoid any conflicts
+with other hardcoded hacks or binary patches.

 ## How to run

-To run your game with ddrhook, you have to use the inject tool to inject the
-DLL to the game process. `dist/ddr` contains bat scripts with all the
-important parameters configured. Further parameters can be added but might not
-be required to run the game with default settings.
-Further information on how to setup the data for each specific version are
-elaborated in their dedicated readme files.
+To run your game with ddrhook, you have to use the inject tool to inject the DLL to the game
+process. `dist/ddr` contains bat scripts with all the important parameters configured. Further
+parameters can be added but might not be required to run the game with default settings. Further
+information on how to setup the data for each specific version are elaborated in their dedicated
+readme files.

 ## Command line options

-Add the argument *-h* when running inject with ddrhook to print help/usage
-information with a list of parameters you can apply to tweak various things.
+Add the argument *-h* when running inject with ddrhook to print help/usage information with a list
+of parameters you can apply to tweak various things.

 ## ddrio API

-Available implementations that can be swapped out depending on which kind of
-IO hardware you want to use:
+Available implementations that can be swapped out depending on which kind of IO hardware you want to
+use:

-* `ddrio`: Default implementation supporting keyboard, mouse and USB
-game controllers
-* ddrio-mm: Support Minimaid custom interface
-* [ddrio-smx](ddrio-smx.md): Support for StepManiaX dance platforms
-* [ddrio-p3io](ddrio-p3io.md): P3IO + EXTIO driver implementation
-* [ddrio-async](ddrio-async.md): Wrapper/shim library to drive another ddrio in
-  a dedicated IO thread
+- `ddrio`: Default implementation supporting keyboard, mouse and USB game controllers
+- ddrio-mm: Support Minimaid custom interface
+- [ddrio-smx](ddrio-smx.md): Support for StepManiaX dance platforms
+- [ddrio-p3io](ddrio-p3io.md): P3IO + EXTIO driver implementation
+- [ddrio-async](ddrio-async.md): Wrapper/shim library to drive another ddrio in a dedicated IO
+  thread

 ## Unicorntail

--- a/doc/ddrhook/ddrhook1.md
+++ b/doc/ddrhook/ddrhook1.md
@@ -4,8 +4,8 @@

 The following games are supported with this hook library:

-* Dance Dance Revolution X
-* Dance Dance Revolution X2 (US/EU regions)
+- Dance Dance Revolution X
+- Dance Dance Revolution X2 (US/EU regions)

 The games must be bootstrapped using [inject](../inject.md).

@@ -13,90 +13,84 @@ The games must be bootstrapped using [inject](../inject.md).

 Ensure your folder with your unpacked data looks like this:

-* `conf`
-* `data`
-* `ddr`
-* `ddr_YYYYMMDDRR` where `YYYYMMDDRR` corresponds to different datecodes of
-  different versions. Multiple folders of these possible
+- `conf`
+- `data`
+- `ddr`
+- `ddr_YYYYMMDDRR` where `YYYYMMDDRR` corresponds to different datecodes of different versions.
+  Multiple folders of these possible

 `DDR.exe` files should be in `ddr` and `ddr_YYYYMMDDRR` folders.

-Unpack the distribution package `ddr-11.zip` into one of the folders containing
-a `DDR.exe` file. We recommend using the one with the latest datecode which
-denotes the latest version of the game including bugfixes etc.
+Unpack the distribution package `ddr-11.zip` into one of the folders containing a `DDR.exe` file. We
+recommend using the one with the latest datecode which denotes the latest version of the game
+including bugfixes etc.

-`gamestart-11.bat` as well as `ddrhook1.dll` are now expected to be located
-in the same folder as (one) `DDR.exe` file.
+`gamestart-11.bat` as well as `ddrhook1.dll` are now expected to be located in the same folder as
+(one) `DDR.exe` file.

 ## Running

-Run `gamestart-11.bat` as administrator. For the US version of the game, run
-`gamestart-11-us.bat` instead. This can be done by either by double
-clicking or running it from `cmd.exe`. The latter is recommended to have
-any debug output kept on screen after closing the game.
+Run `gamestart-11.bat` as administrator. For the US version of the game, run `gamestart-11-us.bat`
+instead. This can be done by either by double clicking or running it from `cmd.exe`. The latter is
+recommended to have any debug output kept on screen after closing the game.

-This will run [inject](../inject.md) with the `ddrhook1.dll`. On first run,
-if you don't have a conguration file, e.g. `ddr-11.conf`, available in the
-same folder, a default one will be created and the game exits. Simply re-run
-`gamestart-11.bat` again.
+This will run [inject](../inject.md) with the `ddrhook1.dll`. On first run, if you don't have a
+conguration file, e.g. `ddr-11.conf`, available in the same folder, a default one will be created
+and the game exits. Simply re-run `gamestart-11.bat` again.

 ## Configuration ddrhook

-The hook library can be configured via cmd arguments or a configuration file.
-The latter is generated (*ddr-11.conf* in the same directory) on the first 
-start of the game using the gamestart-XX.bat file. It contains default values
-for all available parameters and comments explaining each parameter. Please
-follow the comments when configuring your setup.
+The hook library can be configured via cmd arguments or a configuration file. The latter is
+generated (*ddr-11.conf* in the same directory) on the first start of the game using the
+gamestart-XX.bat file. It contains default values for all available parameters and comments
+explaining each parameter. Please follow the comments when configuring your setup.

-Add the argument *-h* when running gamestart-XX.bat 
-(e.g. *gamestart-XX.bat -h*) to print help/usage information with a list of 
-all available parameters. Every parameter can be either set as command line
-argument or using a configuration file.
+Add the argument *-h* when running gamestart-XX.bat (e.g. *gamestart-XX.bat -h*) to print help/usage
+information with a list of all available parameters. Every parameter can be either set as command
+line argument or using a configuration file.

-To set a parameter from the command line, just add it as an argument after
-the bat file like this
+To set a parameter from the command line, just add it as an argument after the bat file like this

 ```
 gamestart-11.bat -p gfx.windowed=true
 ```

-The syntax for the "key=value" is the same as in the config file. Make sure
-to have a pre-ceeding "-p" for every parameter added.
+The syntax for the "key=value" is the same as in the config file. Make sure to have a pre-ceeding
+"-p" for every parameter added.

-However, if a parameter is specifed in the configuration file and as a command
-line argument, the command line argument overrides the config file's value.
+However, if a parameter is specifed in the configuration file and as a command line argument, the
+command line argument overrides the config file's value.

 ## Configure USB memory cards and edit data

-You can setup actual USB thumb drives mapped to a drive letter, e.g. `E:\` for
-player 1 and `F:\` for player 2, or just have them point to any local directory,
-e.g. `usbmem_p1` and `usbmem_p2`.
+You can setup actual USB thumb drives mapped to a drive letter, e.g. `E:\` for player 1 and `F:\`
+for player 2, or just have them point to any local directory, e.g. `usbmem_p1` and `usbmem_p2`.

-Set-up your folder mappings in the
-[conf file or via command line args](#configuration-ddrhook) like follows:
+Set-up your folder mappings in the [conf file or via command line args](#configuration-ddrhook) like
+follows:

-* Enable USB memory data emulation: `ddrhook1.usbmem_enabled=true`
-* Set P1 USB memory data path pointing to local folder `usbmem_p1` next to `DDR.EXE`:
+- Enable USB memory data emulation: `ddrhook1.usbmem_enabled=true`
+- Set P1 USB memory data path pointing to local folder `usbmem_p1` next to `DDR.EXE`:
  `ddrhook1.usbmem_path_p1=usbmem_p1`
-* Set P1 USB memory data path pointing to local folder `usbmem_p2` next to `DDR.EXE`:
+- Set P1 USB memory data path pointing to local folder `usbmem_p2` next to `DDR.EXE`:
  `ddrhook1.usbmem_path_p1=usbmem_p2`
-* Have/create a subfolder called `DDR_EDIT` on any location/USB drive you want to use
-* Name your edit data file either `DDR_EDIT_J.DAT` (for JP version) or `DDR_EDIT_U.DAT`
-  (for US version) and place it in the `DDR_EDIT` directory.
+- Have/create a subfolder called `DDR_EDIT` on any location/USB drive you want to use
+- Name your edit data file either `DDR_EDIT_J.DAT` (for JP version) or `DDR_EDIT_U.DAT` (for US
+  version) and place it in the `DDR_EDIT` directory.

 For the example setup above, the full relative path of the edit file should be
 `usbmem_p1\DDR_EDIT\DDR_EDIT_J.DAT` for player 1.

-Note that USB memory cards are not detected by the game and the game stays
-silent about that if they do not contain edit data, your path mapping does not resolve
-or you misplaced or named your edit data file incorrectly.
+Note that USB memory cards are not detected by the game and the game stays silent about that if they
+do not contain edit data, your path mapping does not resolve or you misplaced or named your edit
+data file incorrectly.

 ## Grey and glitchy arrows

 This is a known issue with many GPUs, typically non-Radeon GPUs.

-There is currently not patch available in Bemanitools for that. We assume this is an
-issue with incompatible shader code.
+There is currently not patch available in Bemanitools for that. We assume this is an issue with
+incompatible shader code.

 There are solutions to hard-patch the code available elsewhere.

@@ -106,34 +100,32 @@ There are solutions to hard-patch the code available elsewhere.

 The game expects you have the `CLVSD.ax` file registered for decoding videos.

-Grab the `CLVSD.ax` file and go to *Start* > *Run* > enter `regsvr32 clvsd.ax` and
-execute. Make sure to run as Administrator, otherwise you will get errors due to
-invalid permissions.
+Grab the `CLVSD.ax` file and go to *Start* > *Run* > enter `regsvr32 clvsd.ax` and execute. Make
+sure to run as Administrator, otherwise you will get errors due to invalid permissions.

 ### Game crashes during boot

-If you have played a newer version of DDR, e.g. DDR 2014+, you might have the
-`k-clvsd.dll` codec registered which crashes DDR X and likely X2 (EU/US) as well.
+If you have played a newer version of DDR, e.g. DDR 2014+, you might have the `k-clvsd.dll` codec
+registered which crashes DDR X and likely X2 (EU/US) as well.

 Unregister `k-clvsd.dll`, e.g. `regsvr32 /u k-clvsd.dll`, and
 [registering `CLVSD.ax`](#issues-with-background-videos-not-working).

-Note that `CLVSD.ax` will likely hang any newer/more recent DDR versions on startup
-and require you to use the `k-clvsd.dll` that came with the respective version
-instead. See [this section](ddrhook2.md#video-codecs-for-background-videos) for
-further details.
+Note that `CLVSD.ax` will likely hang any newer/more recent DDR versions on startup and require you
+to use the `k-clvsd.dll` that came with the respective version instead. See
+[this section](ddrhook2.md#video-codecs-for-background-videos) for further details.

 ### Black screen/render window without a response

 This symptom might have many causes, here is a list of known issues and what can be done:

-* If not done already, try installing
+- If not done already, try installing
  [DirectX Redist (June 2010)](https://www.microsoft.com/en-us/download/details.aspx?id=8109)
-* If you have an integrated/second GPU, ensure it is disabled
-* External (USB) audio devices could cause issues. Ensure you are running on on-board/integrated
+- If you have an integrated/second GPU, ensure it is disabled
+- External (USB) audio devices could cause issues. Ensure you are running on on-board/integrated
  sound cards and unplug any external audio devices.
-* [Disable fullscreen optimizations](https://devblogs.microsoft.com/directx/demystifying-full-screen-optimizations/):
+- [Disable fullscreen optimizations](https://devblogs.microsoft.com/directx/demystifying-full-screen-optimizations/):
  Right click on `DDR.exe`, *Properties* > *Compatibility* > *Disable fullscreen optimizations*
-* Check if you can run `DDR.exe` without Bemanitools by simply launching it. It should at least
-  boot into a startup screen. If that isn't even possible, then it's likely not an issue with
+- Check if you can run `DDR.exe` without Bemanitools by simply launching it. It should at least boot
+  into a startup screen. If that isn't even possible, then it's likely not an issue with
  Bemanitools. Note that your data path needs to be `D:\HDX` for that to work though.
--- a/doc/ddrhook/ddrhook2.md
+++ b/doc/ddrhook/ddrhook2.md
@@ -4,25 +4,26 @@

 The following games are supported by this hook library:

-* Dance Dance Revolution X2 (JP region)
-* Dance Dance Revolution X3 vs. 2ndMIX
-* Dance Dance Revolution 2013
-* Dance Dance Revolution 2014
-* Dance Dance Revolution A
+- Dance Dance Revolution X2 (JP region)
+- Dance Dance Revolution X3 vs. 2ndMIX
+- Dance Dance Revolution 2013
+- Dance Dance Revolution 2014
+- Dance Dance Revolution A
+- Dance Dance Revolution A20
+- Dance Dance Revolution A20+

-Note that different builds of the same hook library are required to run the
-different versions. See different distribution packages, e.g. `ddr-12.zip`,
-`ddr-13.zip` etc.
+Note that different builds of the same hook library are required to run the different versions. See
+different distribution packages, e.g. `ddr-12.zip`, `ddr-13.zip` etc.

-Depending on the game version, earlier versions are bootstrapped using
-[inject](../inject.md) while later versions require [launcher](../launcher.md).
+Depending on the game version, earlier versions are bootstrapped using [inject](../inject.md) while
+later versions require [launcher](../launcher.md).

 ## Setup A20+

 ### Data and folder structure

-The following assumes you are using vanilla and unpacked/decrypted data. Copy/unpack the data
-to a destination of your choice. Expect to have the following root folder structure:
+The following assumes you are using vanilla and unpacked/decrypted data. Copy/unpack the data to a
+destination of your choice. Expect to have the following root folder structure:

 ```
 arkdata
@@ -33,10 +34,10 @@ modules
 prop
 ```

-* Copy the contents of `modules` to the root folder that the dll-files are next to the folders
+- Copy the contents of `modules` to the root folder that the dll-files are next to the folders
  `arkdata`, `com`, etc.
-* Unpack the contents of `ddr-14-to-16.zip` to the root folder. `luncher.exe` should be located
-  next to `arkdata`, `com` and all the dll-files
+- Unpack the contents of `ddr-14-to-16.zip` to the root folder. `luncher.exe` should be located next
+  to `arkdata`, `com` and all the dll-files

 #### Configuring eamuse settings

@@ -86,65 +87,62 @@ URL, further settings like ssl etc.

 ## Running

-Run `gamestart-XX.bat`, where `XX` corresponds to the version of the game you
-want to run, as administrator. For the US version of X2, run
-`gamestart-12-us.bat` instead. This can be done by either by double
-clicking or running it from `cmd.exe`. The latter is recommended to have
-any debug output kept on screen after closing the game.
+Run `gamestart-XX.bat`, where `XX` corresponds to the version of the game you want to run, as
+administrator. For the US version of X2, run `gamestart-12-us.bat` instead. This can be done by
+either by double clicking or running it from `cmd.exe`. The latter is recommended to have any debug
+output kept on screen after closing the game.

-This will run [inject](../inject.md) or [launcher](../launcher.md), depending
-on the version of the game, with the `ddrhook2.dll`. On first run, if you don't
-have a conguration file, e.g. `ddr-12.conf`, available in the same folder, a
-default one will be created and the game exits. Simply re-run `gamestart-XX.bat`
-again.
+This will run [inject](../inject.md) or [launcher](../launcher.md), depending on the version of the
+game, with the `ddrhook2.dll`. On first run, if you don't have a conguration file, e.g.
+`ddr-12.conf`, available in the same folder, a default one will be created and the game exits.
+Simply re-run `gamestart-XX.bat` again.

 ## Configure USB memory cards and edit data (DDR X2)

-You can setup actual USB thumb drives mapped to a drive letter, e.g. `E:\` for
-player 1 and `F:\` for player 2, or just have them point to any local directory,
-e.g. `usbmem_p1` and `usbmem_p2`.
+You can setup actual USB thumb drives mapped to a drive letter, e.g. `E:\` for player 1 and `F:\`
+for player 2, or just have them point to any local directory, e.g. `usbmem_p1` and `usbmem_p2`.

-Set-up your folder mappings in the
-[conf file or via command line args](#configuration-ddrhook) like follows:
+Set-up your folder mappings in the [conf file or via command line args](#configuration-ddrhook) like
+follows:

-* Enable USB memory data emulation: `ddrhook1.usbmem_enabled=true`
-* Set P1 USB memory data path pointing to local folder `usbmem_p1` next to `DDR.EXE`:
+- Enable USB memory data emulation: `ddrhook1.usbmem_enabled=true`
+- Set P1 USB memory data path pointing to local folder `usbmem_p1` next to `DDR.EXE`:
  `ddrhook1.usbmem_path_p1=usbmem_p1`
-* Set P1 USB memory data path pointing to local folder `usbmem_p2` next to `DDR.EXE`:
+- Set P1 USB memory data path pointing to local folder `usbmem_p2` next to `DDR.EXE`:
  `ddrhook1.usbmem_path_p1=usbmem_p2`
-* Have/create a subfolder called `DDR_EDIT` on any location/USB drive you want to use
-* Name your edit data file either `DDR_EDIT_J.DAT` (for JP version) or `DDR_EDIT_US.DAT`
-  (for US version) and place it in the `DDR_EDIT` directory.
+- Have/create a subfolder called `DDR_EDIT` on any location/USB drive you want to use
+- Name your edit data file either `DDR_EDIT_J.DAT` (for JP version) or `DDR_EDIT_US.DAT` (for US
+  version) and place it in the `DDR_EDIT` directory.

 For the example setup above, the full relative path of the edit file should be
 `usbmem_p1\DDR_EDIT\DDR_EDIT_J.DAT` for player 1.

-Note that USB memory cards are not detected by the game and the game stays
-silent about that if they do not contain edit data, your path mapping does not resolve
-or you misplaced or named your edit data file incorrectly.
+Note that USB memory cards are not detected by the game and the game stays silent about that if they
+do not contain edit data, your path mapping does not resolve or you misplaced or named your edit
+data file incorrectly.

 ## Troubleshooting and FAQ

 ### Video codecs for background videos

 For DDR 2014 and newer (maybe also earlier?), you need to register `k-clvsd.dll` and
-`xactengine2_10.dll` to make background videos work. These files are included with
-respective versions of the games.
+`xactengine2_10.dll` to make background videos work. These files are included with respective
+versions of the games.

-Run the following commands either from a command line (`cmd.exe`) or from 
-*Start* > *Run*. Adjust the path to files accordingly pointing to the correct files.
+Run the following commands either from a command line (`cmd.exe`) or from *Start* > *Run*. Adjust
+the path to files accordingly pointing to the correct files.

-* Register `regsvr32 D:\MDX\contents\k-clvsd.dll`
-* Register `regsvr32 D:\MDX\contents\xactengine2_10.dll`
+- Register `regsvr32 D:\MDX\contents\k-clvsd.dll`
+- Register `regsvr32 D:\MDX\contents\xactengine2_10.dll`

 The `gamestart-XX.bat` scripts should already take care of this by executing the listed commands
 when launched.

-Note: The one that comes with IIDX will hang DDR at startup. The opposite is not true:
-IIDX works just fine with this CLVSD.
+Note: The one that comes with IIDX will hang DDR at startup. The opposite is not true: IIDX works
+just fine with this CLVSD.

 ### Laggy audio

-If you're running on Windows XP, go to the sound devices control panel, select your
-sound card, click Advanced Options and turn Hardware Acceleration down to basic. This
-will make the audio much less laggy..
+If you're running on Windows XP, go to the sound devices control panel, select your sound card,
+click Advanced Options and turn Hardware Acceleration down to basic. This will make the audio much
+less laggy..
--- a/doc/ddrhook/ddrio-async.md
+++ b/doc/ddrhook/ddrio-async.md
@@ -1,29 +1,26 @@
 # Asynchronous proxy wrapper for other ddrio implementations

-This implementation of the Bemanitools API is not implementing support for any
-specific IO hardware. It is a proxy/shim library that loads another ddrio
-library, e.g. ddrio-p3io, and drives the entire backend in a dedicated IO
-thread. By implementing this behind the ddrio API, it is fully transparent to
-any existing application using it.
+This implementation of the Bemanitools API is not implementing support for any specific IO hardware.
+It is a proxy/shim library that loads another ddrio library, e.g. ddrio-p3io, and drives the entire
+backend in a dedicated IO thread. By implementing this behind the ddrio API, it is fully transparent
+to any existing application using it.

-The main benefit is the improved IO polling performance depending on how
-expensive the synchronous calls of the actual hardware are. For example,
-*ddrio-p3io* has very expensive write calls with ~12 ms duration while read
-calls take ~4 ms. Therefore, a full update cycle is already about as costly
+The main benefit is the improved IO polling performance depending on how expensive the synchronous
+calls of the actual hardware are. For example, *ddrio-p3io* has very expensive write calls with ~12
+ms duration while read calls take ~4 ms. Therefore, a full update cycle is already about as costly
 as rendering an entire frame (at 60 fps).

 ## Setup

-For hook libraries, i.e. ddrhookX, but likely applicable to 3rd party
-applications (consolidate their manuals).
+For hook libraries, i.e. ddrhookX, but likely applicable to 3rd party applications (consolidate
+their manuals).

-* Have `ddrio-async.dll` in the same folder as your `ddrhookX.dll`
-* Rename `ddrio-async.dll` to `ddrio.dll`
-* Pick another ddrio library as the backend of your choice, e.g. `ddrio-p3io.dl`
-  and put it next to the async `ddrio.dll`
-* Rename it to `ddrio-async-child.dll`, ddrio-async is looking for that filename
-  in the same folder
-* Ensure that your `gamestart.bat` actually injects the appropriate `ddrhook.dll`, for example:
+- Have `ddrio-async.dll` in the same folder as your `ddrhookX.dll`
+- Rename `ddrio-async.dll` to `ddrio.dll`
+- Pick another ddrio library as the backend of your choice, e.g. `ddrio-p3io.dl` and put it next to
+  the async `ddrio.dll`
+- Rename it to `ddrio-async-child.dll`, ddrio-async is looking for that filename in the same folder
+- Ensure that your `gamestart.bat` actually injects the appropriate `ddrhook.dll`, for example:

 ```bat
 inject ddrhook1.dll ddr.exe ...*
@@ -33,4 +30,4 @@ or

 ```bat
 launcher -K ddrhook2.dll arkmdxp3.dll ...*
-```
+```
--- a/doc/ddrhook/ddrio-p3io.md
+++ b/doc/ddrhook/ddrio-p3io.md
@@ -1,27 +1,29 @@
 # ddrio API implementation with DDR P3IO (Dragon) and EXTIO

-This implementation of BT5's ddrio API allows you to use the native DDR P3IO
-of a "Dragon PCB" plus the EXTIO with anything the ddrio API supports.
+This implementation of BT5's ddrio API allows you to use the native DDR P3IO of a "Dragon PCB" plus
+the EXTIO with anything the ddrio API supports.

-This is not required to run the actual games supporting the hardware natively.
-However, there are various 3rd party applications using the ddrio API where you
-might benefit from using actual SD cabinet hardware, e.g.
-[vigem-ddrio](../vigem/README.md).
+This is not required to run the actual games supporting the hardware natively. However, there are
+various 3rd party applications using the ddrio API where you might benefit from using actual SD
+cabinet hardware, e.g. [vigem-ddrio](../vigem/README.md).

 ## Setup

-For hooks, but likely applicable to 3rd party applications (consolidate their
-manuals).
+For hooks, but likely applicable to 3rd party applications (consolidate their manuals).
+
+- Driver: You must have the P3IO driver intalled on your system
+  - Driver from
+    [bemanitools-supplements](https://github.com/djhackersdev/bemanitools-supplement/blob/master/ddr/p3io/README.md)
+- Have `ddrio-p3io.dll` in the same folder as your `ddrhookX.dll`
+- Rename `ddrio-p3io.dll` to `ddrio.dll`
+- Ensure that your `gamestart.bat` actually injects the appropriate ddrhook dll, for example:

-* Driver: You must have the P3IO driver intalled on your system
-  * Driver from [bemanitools-supplements](https://github.com/djhackersdev/bemanitools-supplement/blob/master/ddr/p3io/README.md)
-* Have `ddrio-p3io.dll` in the same folder as your `ddrhookX.dll`
-* Rename `ddrio-p3io.dll` to `ddrio.dll`
-* Ensure that your `gamestart.bat` actually injects the appropriate ddrhook dll, for example:
 ```bat
 inject ddrhook1.dll ddr.exe ...*
 ```
+
 or
+
 ```bat
 launcher -K ddrhook2.dll arkmdxp3.dll ...*
-```
+```
--- a/doc/ddrhook/ddrio-smx.md
+++ b/doc/ddrhook/ddrio-smx.md
@@ -1,14 +1,30 @@
 # Using SMX pads with BemaniTools (DDR Ace and higher)
-If you are looking to use StepManiaX pads with DDR, these are supported **natively** for Gen 1 through Gen 5.(And theoretically beyond!) Steps and info below
+
+If you are looking to use StepManiaX pads with DDR, these are supported **natively** for Gen 1
+through Gen 5.(And theoretically beyond!) Steps and info below

 ## Step-by-Step
-1. Ensure that you have the latest `SMX.dll` copied to your contents folder. The easiest way to get this is to download and install the latest SMX Config program on [StepManiaX.com](https://data.stepmaniax.com/docs/SMXConfigInstaller-2020-04-03-01.exe). `SMX.dll`'s default install location is `C:\Program Files (x86)\SMXConfig`
-2. After bemanitools has been copied to your contents folder, rename the regular `ddrio.dll` to something like `ddrio-orig.dll`.
-3. Rename `ddrio-smx.dll` to `ddrio.dll`.
-4. Use the config tool to set up the usual stuff.(cards, network, etc.) Be sure to map menu, test, service, and start buttons to your keyboard or other controllers. You **cannot** map SMX panels as joystick inputs.
-5. Start the game. If everything works properly, the game will boot and your panels will light up when stepped on during gameplay and song selection.
+
+1. Ensure that you have the latest `SMX.dll` copied to your contents folder. The easiest way to get
+   this is to download and install the latest SMX Config program on
+   [StepManiaX.com](https://data.stepmaniax.com/docs/SMXConfigInstaller-2020-04-03-01.exe).
+   `SMX.dll`'s default install location is `C:\Program Files (x86)\SMXConfig`
+1. After bemanitools has been copied to your contents folder, rename the regular `ddrio.dll` to
+   something like `ddrio-orig.dll`.
+1. Rename `ddrio-smx.dll` to `ddrio.dll`.
+1. Use the config tool to set up the usual stuff.(cards, network, etc.) Be sure to map menu, test,
+   service, and start buttons to your keyboard or other controllers. You **cannot** map SMX panels
+   as joystick inputs.
+1. Start the game. If everything works properly, the game will boot and your panels will light up
+   when stepped on during gameplay and song selection.

 ## Important Things
-* Pad panel inputs (UDLR on P1 and P2) are mapped automatically. If you've purchased a single pad from StepManiaX, this jumper is installed and will set your pad to P2 by default. If you want to change to P1, you'll need to open up your pads and remove this jumper in the [MCU box](https://data.stepmaniax.com/docs/Stage%20-%20Gen%205%20Manual%20Rev1.pdf).
-* Panel colors set in the SMX config tool are not used. Colors are set internally by Bemanitools.
-* If you get a warning about setlights2 when starting the game, your `SMX.dll` is likely out of date. Make sure you've downloaded the latest version of the StepManiaX config tool from stepmaniax.com and have copied the `SMX.dll` to your contents folder.
+
+- Pad panel inputs (UDLR on P1 and P2) are mapped automatically. If you've purchased a single pad
+  from StepManiaX, this jumper is installed and will set your pad to P2 by default. If you want to
+  change to P1, you'll need to open up your pads and remove this jumper in the
+  [MCU box](https://data.stepmaniax.com/docs/Stage%20-%20Gen%205%20Manual%20Rev1.pdf).
+- Panel colors set in the SMX config tool are not used. Colors are set internally by Bemanitools.
+- If you get a warning about setlights2 when starting the game, your `SMX.dll` is likely out of
+  date. Make sure you've downloaded the latest version of the StepManiaX config tool from
+  stepmaniax.com and have copied the `SMX.dll` to your contents folder.
--- a/doc/ddrhook/unicorntail.md
+++ b/doc/ddrhook/unicorntail.md
@@ -17,11 +17,11 @@ A Chimera PCB however is different in many aspects to the Dragon PCB and require
 The Dragon's P3IO has two serial ports that the regular P3IOs do not, and one of these serial ports
 is used to communicate with the card readers. Note that these are actual serial ports driven
 directly by the P3IO microcontroller, these are NOT just passed through to the motherboard like the
-proprietary COM1 and COM2 connectors. 
+proprietary COM1 and COM2 connectors.

-Unicorn Tail intercepts serial port IO commands being sent to the P3IO and redirects them to a 
-COM4 in Windows instead, where two readers can be connected via the motherboard's RS232 port or 
-a usb RS232 adapter.
+Unicorn Tail intercepts serial port IO commands being sent to the P3IO and redirects them to a COM4
+in Windows instead, where two readers can be connected via the motherboard's RS232 port or a usb
+RS232 adapter.

 ## Drivers

@@ -33,11 +33,10 @@ HDD or grabbed from

 Using Device Manager in Windows, ensure the following COM ports are connected and setup.

-COM1: EXTIO
-COM4: Two readers
+COM1: EXTIO COM4: Two readers

-Windows is often poor about saving the COM port number, so ewf commit (if applicable) and 
-reboot after saving this setting to ensure it sticks.
+Windows is often poor about saving the COM port number, so ewf commit (if applicable) and reboot
+after saving this setting to ensure it sticks.

 ## Setup and run

@@ -48,8 +47,8 @@ e.g.:
 launcher.exe -H 33554432 -K unicorntail.dll arkmdxp3.dll %*
 ```

-If you want to use any ddrhook library in addition, you have to have the hooks in the right order
-to make everything work correctly, e.g.:
+If you want to use any ddrhook library in addition, you have to have the hooks in the right order to
+make everything work correctly, e.g.:

 ```shell
 launcher.exe -H 33554432 -K unicorntail.dll -K ddrhook2.dll arkmdxp3.dll %*
--- a/doc/dev/README.md
+++ b/doc/dev/README.md
@@ -1,3 +1,4 @@
 # Development documentation and notes
+
 This folder contains various lose documentation snippets created by the developers. These can be
-helpful as future reference.
+helpful as future reference.
--- a/doc/dev/device-list.md
+++ b/doc/dev/device-list.md
@@ -6,21 +6,20 @@

 Separate boxed unit containing with one card reader slot and pin key pad

- BeatmaniaIIDX DistorteD to Lincle: grey slotted readers hanging below the
-side speakers next to the monitor
- DDR SN 1/2: slotted readers red/black supernova cover mounted to the side of
-the cabinet next to the monitor (left and right)
+- BeatmaniaIIDX DistorteD to Lincle: grey slotted readers hanging below the side speakers next to
+  the monitor
+- DDR SN 1/2: slotted readers red/black supernova cover mounted to the side of the cabinet next to
+  the monitor (left and right)

 # ICCB

-Single card reader slot (no separate pin pad) built into the cabinet.
-Pin entry using game controls.
+Single card reader slot (no separate pin pad) built into the cabinet. Pin entry using game controls.

 - (First gen) Jubeat cabinets before replaced with wave pass readers

 # ICCC

-Single card reader wave pass unit without separate pin pad. Pin entry using
-game controls. Still supported by newer versions.
+Single card reader wave pass unit without separate pin pad. Pin entry using game controls. Still
+supported by newer versions.

- (Second gen) Jubeat cabinets with wave pass readers
+- (Second gen) Jubeat cabinets with wave pass readers
--- a/doc/dev/journal/2018-02-10-logging-breakdown-avs.md
+++ b/doc/dev/journal/2018-02-10-logging-breakdown-avs.md
@@ -2,75 +2,116 @@ Copy/pasted from chat with tau (2018/02/10):

 alright then. so for modern iidx.

-we want to do logging inside iidxhook and we also want to pass AVS-style log functions to iidxio which in turn passes them on to geninput in order for those to do logging too
+we want to do logging inside iidxhook and we also want to pass AVS-style log functions to iidxio
+which in turn passes them on to geninput in order for those to do logging too

-so iidxhook connects to the AVS log API: log_body_misc and friends, which I assume are invoked using a log_misc() macro in Konami's source code that adds some sort of module tag.
+so iidxhook connects to the AVS log API: log_body_misc and friends, which I assume are invoked using
+a log_misc() macro in Konami's source code that adds some sort of module tag.

 anyway yeah this we already know.

-libutil has four function ptrs: log_impl_misc and co. These are static variables which are statically initialized to some no-op functions. Except log_impl_fatal, whose implementation just calls libc abort()
+libutil has four function ptrs: log_impl_misc and co. These are static variables which are
+statically initialized to some no-op functions. Except log_impl_fatal, whose implementation just
+calls libc abort()

-at startup you call log_to_external(), supplying four function ptrs to wire these up to. As the name suggests, this causes Bemanitools libutil to talk to something that is compatible with the AVS log sink API.
+at startup you call log_to_external(), supplying four function ptrs to wire these up to. As the name
+suggests, this causes Bemanitools libutil to talk to something that is compatible with the AVS log
+sink API.

-alternatively you can log_to_writer(), which initializes Bemanitools to use its own, internal logging system, and you give it a log writer function that takes strings and writes them somewhere.
+alternatively you can log_to_writer(), which initializes Bemanitools to use its own, internal
+logging system, and you give it a log writer function that takes strings and writes them somewhere.

-So you have log sinks and you have log writers. The path is [application code] -> [log sink] -> [logging engine] -> [log writer]
-19:29
+So you have log sinks and you have log writers. The path is \[application code\] -> \[log sink\] ->
+\[logging engine\] -> \[log writer\] 19:29

-inside config.exe (or generally outside of modern AVS games) this path looks like [bemanitools application code] -> [log sinks passed across dlls] -> [bemanitools logging engine] -> [bemanitools log writer]
+inside config.exe (or generally outside of modern AVS games) this path looks like \[bemanitools
+application code\] -> \[log sinks passed across dlls\] -> \[bemanitools logging engine\] ->
+\[bemanitools log writer\]

-inside modern AVS game the path looks like [bt hook dll / bt iodev dll] -> [avs log_body_whatever log sinks] -> [avs logging engine] -> [launcher.exe log writer]
+inside modern AVS game the path looks like \[bt hook dll / bt iodev dll\] -> \[avs log_body_whatever
+log sinks\] -> \[avs logging engine\] -> \[launcher.exe log writer\]

-note that I tried to keep the log writer API consistent with the AVS log writer API but then Konami went and broke it repeatedly so now Bemanitools has its own stable log writer API. Launcher tracks the AVS log writer API, which breaks constantly, so that's not the same thing.
+note that I tried to keep the log writer API consistent with the AVS log writer API but then Konami
+went and broke it repeatedly so now Bemanitools has its own stable log writer API. Launcher tracks
+the AVS log writer API, which breaks constantly, so that's not the same thing.

 anyway that's the background story. Now for the details about IIDX in particular.

-up until about iidx19 we did things the obvious way: iidxhook would log_to_external() to hook into the AVS log sinks and then call those directly and all was well. Then one fine day I was given a IIDX19 data dump and tried running iidxhook and it crashed with a stack overflow. hmm.
+up until about iidx19 we did things the obvious way: iidxhook would log_to_external() to hook into
+the AVS log sinks and then call those directly and all was well. Then one fine day I was given a
+IIDX19 data dump and tried running iidxhook and it crashed with a stack overflow. hmm.

-the problem boils down to this: iidx19 AVS added those log timestamps. And for for whatever reason the AVS logging engine needs to access some mutexes and condition variables to make this work properly
+the problem boils down to this: iidx19 AVS added those log timestamps. And for for whatever reason
+the AVS logging engine needs to access some mutexes and condition variables to make this work
+properly

-but AVS of course in grand Konami tradition has its own threading and concurrency primitive API which wraps the Win32 API. tbf this is kind of understandable in some sense, because win32 actually did not have condition variables until Windows Vista! in 2006! seriously, I'm not kidding.
+but AVS of course in grand Konami tradition has its own threading and concurrency primitive API
+which wraps the Win32 API. tbf this is kind of understandable in some sense, because win32 actually
+did not have condition variables until Windows Vista! in 2006! seriously, I'm not kidding.

-there's all sorts of articles out there describing in fine detail how to use Win32's event objects to implement your own condition variables and the multitudinous pitfalls that this entails
+there's all sorts of articles out there describing in fine detail how to use Win32's event objects
+to implement your own condition variables and the multitudinous pitfalls that this entails

-but anyway one fun thing about the AVS concurrency API is that you can't actually use concurrency primitives unless you're calling that API from a thread launched using the AVS threading API
+but anyway one fun thing about the AVS concurrency API is that you can't actually use concurrency
+primitives unless you're calling that API from a thread launched using the AVS threading API

-and that's a problem in the case of iidxhook, because iidx is old as balls relatively speaking and its EZUSB driver code has I think two worker threads, which it launches using the MS libc's _beginthreadex() function
+and that's a problem in the case of iidxhook, because iidx is old as balls relatively speaking and
+its EZUSB driver code has I think two worker threads, which it launches using the MS libc's
+\_beginthreadex() function

-this in turn is a wrapper around the win32 CreateThread function, but it also boots up stdio on whatever new thread gets launched and basically is responsible for guaranteeing that the libc will operate correctly on the newly launched thread
+this in turn is a wrapper around the win32 CreateThread function, but it also boots up stdio on
+whatever new thread gets launched and basically is responsible for guaranteeing that the libc will
+operate correctly on the newly launched thread

-so yeah when you do windows programming, never call CreateThread, always call _beginthreadex. otherwise stuff will break. maybe.
+so yeah when you do windows programming, never call CreateThread, always call \_beginthreadex.
+otherwise stuff will break. maybe.

-point is, IIDX predates modern AVS so it just uses Windows threading directly. So, IIDX worker thread starts up, iidxhook does its thing, writes a log message, calls into AVS logging, which in turn grabs an AVS mutex, the implementation of which says "omg this isn't an AVS thread aaaaaa" and ... attempts to call back into the logging system to log this fact. whereupon a stack overflow condition proceeds in a predictable manner.
+point is, IIDX predates modern AVS so it just uses Windows threading directly. So, IIDX worker
+thread starts up, iidxhook does its thing, writes a log message, calls into AVS logging, which in
+turn grabs an AVS mutex, the implementation of which says "omg this isn't an AVS thread aaaaaa" and
+... attempts to call back into the logging system to log this fact. whereupon a stack overflow
+condition proceeds in a predictable manner.

-so, there are a few ways to deal with this problem. bemanitools 4 dealt with it in a fairly stupid way.
+so, there are a few ways to deal with this problem. bemanitools 4 dealt with it in a fairly stupid
+way.

 and very elaborate way too

-bt4 intercepted IIDX's calls to create Windows threads and then redirected those calls to go via the AVS threading API
+bt4 intercepted IIDX's calls to create Windows threads and then redirected those calls to go via the
+AVS threading API

 so now the worker threads are AVS threads and logging works as expected

-which is all well and good but the problem is that these threads are quite timing critical. it probably worked fine, but i didn't want to risk affecting those threads in a weird way and introducing latency and jitter. i wanted to keep the threading pristine and not mess with it just for the sake of diagnostic messages
+which is all well and good but the problem is that these threads are quite timing critical. it
+probably worked fine, but i didn't want to risk affecting those threads in a weird way and
+introducing latency and jitter. i wanted to keep the threading pristine and not mess with it just
+for the sake of diagnostic messages

 so bemanitools 5 uses the log server approach

-at an appropriate time, it creates its own AVS thread, the logging server. Since it is an AVS thread, it can call the AVS logging API
+at an appropriate time, it creates its own AVS thread, the logging server. Since it is an AVS
+thread, it can call the AVS logging API

 and then we have log_post_misc() and friends, implemented in log-server.c

-we initialize the Bemanitools logging system to log "externally" to those funcs and we also propagate those to iidxio.dll and eamio.dll which in turn pass them to geninput.dll
+we initialize the Bemanitools logging system to log "externally" to those funcs and we also
+propagate those to iidxio.dll and eamio.dll which in turn pass them to geninput.dll

 so what do log_post_misc and friends do

-they lock a "mailbox" using the win32 concurrency primitives and write the log severity and a pointer to the string to be logged into the mailbox, then signal the log server thread, again using win32 concurrency primitives
+they lock a "mailbox" using the win32 concurrency primitives and write the log severity and a
+pointer to the string to be logged into the mailbox, then signal the log server thread, again using
+win32 concurrency primitives

-then they do a synchronous wait for an acknowledgement from the logging server: since we're holding a string pointer, we cannot return until that string pointer has been consumed or it may be concurrently invalidated
+then they do a synchronous wait for an acknowledgement from the logging server: since we're holding
+a string pointer, we cannot return until that string pointer has been consumed or it may be
+concurrently invalidated

-so the log server wakes up, locks the mailbox, calls AVS log_body_misc() to write the log message, then once that returns it asserts a signal in the mailbox (again, win32 event object because lol what are condition variables) and releases the lock.
+so the log server wakes up, locks the mailbox, calls AVS log_body_misc() to write the log message,
+then once that returns it asserts a signal in the mailbox (again, win32 event object because lol
+what are condition variables) and releases the lock.

-the caller gets the signal, wakes up, and returns to whatever Bemanitools code is running on the IIDX IO worker thread that wanted to write a log message.
+the caller gets the signal, wakes up, and returns to whatever Bemanitools code is running on the
+IIDX IO worker thread that wanted to write a log message.

 end of essay.
-
-
--- a/doc/dev/journal/2019-07-29-c02-driver-on-w7-crash.md
+++ b/doc/dev/journal/2019-07-29-c02-driver-on-w7-crash.md
@@ -1,68 +1,86 @@
 # Follow-up (14th August 2019)
-After publishing this post-mortem, I got messaged by a user on sows who was able to shed some more light on this issue.
-The user was experiencing the same symptoms on a Win7 setup: blue screen once the firmware was flashed to the C02 IO.
-This user's solutions was to use the USB2 ports on the PC instead of the USB3 ones. This is good to know and kinda
-aligns with the weird things happening in the driver (see below).
+
+After publishing this post-mortem, I got messaged by a user on sows who was able to shed some more
+light on this issue. The user was experiencing the same symptoms on a Win7 setup: blue screen once
+the firmware was flashed to the C02 IO. This user's solutions was to use the USB2 ports on the PC
+instead of the USB3 ones. This is good to know and kinda aligns with the weird things happening in
+the driver (see below).

 # Post-mortem: C02 IO kernel module crash on Windows 7 (29th July 2019) by icex2
+
 ## Background
-The original ezusbsys.sys kernel module, which is required to run the C02 IO, was compiled for Windows XP 32-bit, only.
-There is a newer driver by Cypress, cyusb3.sys, which could be used to IO2 boards on newer Windows platforms, but does
-not work with the C02 IO in combination with Konami's propriatery firmware. Thus, it was not possible to run the C02 IO
-on anything than Windows XP 32-bit. But, with newer IIDX games running on Windows 7 64-bit, the C02 IO wasn't usable
-anymore. Leaving aside, that the newer games actually require a BIO2 board and do not support C02 nor IO2 boards
-anymore.
+
+The original ezusbsys.sys kernel module, which is required to run the C02 IO, was compiled for
+Windows XP 32-bit, only. There is a newer driver by Cypress, cyusb3.sys, which could be used to IO2
+boards on newer Windows platforms, but does not work with the C02 IO in combination with Konami's
+propriatery firmware. Thus, it was not possible to run the C02 IO on anything than Windows XP
+32-bit. But, with newer IIDX games running on Windows 7 64-bit, the C02 IO wasn't usable anymore.
+Leaving aside, that the newer games actually require a BIO2 board and do not support C02 nor IO2
+boards anymore.

 ## The goal
-I still wanted to use my cabinet with a C02 board on newer games which is possible with BT5 adding an emulation layer
-and an interface (iidxio). This IO interface can be used to implement a driver that talks to a real IO again. Thus,
-implementing a ezusb iidxio driver library, we can run newer games with an C02 IO as well.

-However, there was no ezusbsys.sys driver that works on newer platforms required to run the newer games. But, Cypress
-was nice and included the source code of the ezusbsys kernel module. With a few tweaks and a very recent version of
-visual studio, it was quite easy to build this driver for newer platforms, including Windows 7, 8 and 10 in both
-32-bit and 64-bit variants.
+I still wanted to use my cabinet with a C02 board on newer games which is possible with BT5 adding
+an emulation layer and an interface (iidxio). This IO interface can be used to implement a driver
+that talks to a real IO again. Thus, implementing a ezusb iidxio driver library, we can run newer
+games with an C02 IO as well.
+
+However, there was no ezusbsys.sys driver that works on newer platforms required to run the newer
+games. But, Cypress was nice and included the source code of the ezusbsys kernel module. With a few
+tweaks and a very recent version of visual studio, it was quite easy to build this driver for newer
+platforms, including Windows 7, 8 and 10 in both 32-bit and 64-bit variants.

 ## The problem
-But, when using this driver on certain combinations of newer hardware (max. 1-2 years old) and Windows 7, the kernel
-module might crash after the Konami C02 firmware got flashed to the ezusb board. The result was a bluescreen and reboot.

-However, the hardware was fine and the kernel module worked fine on another piece of hardware, the stock PC that was 
-used with iidx 20 to 24. However, this hardware is not powerful enough to run iidx 25 and newer without stuttering
-issues.
+But, when using this driver on certain combinations of newer hardware (max. 1-2 years old) and
+Windows 7, the kernel module might crash after the Konami C02 firmware got flashed to the ezusb
+board. The result was a bluescreen and reboot.
+
+However, the hardware was fine and the kernel module worked fine on another piece of hardware, the
+stock PC that was used with iidx 20 to 24. However, this hardware is not powerful enough to run iidx
+25 and newer without stuttering issues.

 ## The analysis/debugging
+
 Note: The full source code can be found in the bemanitools-supplement package.

 Setup:
-* Native hardware with Windows 7 that was crashing
-* Vmware with Windows 10 and Visual Studio 2019 to compile the kernel module. Target platform Windows 7 64-bit
-* Booting Windows 7 in test mode to allow unsigned kernel modules to run and with debug output turned on
-* dbgview on Windows 7 machine to get local kernel dbg output

-Because I wanted to stick to Windows 7 in the beginning (refer to the solution section), I started debugging the kernel
-module by enabling the debug message output that was already available in the code. However, since kernel debug message
-printing can be very delayed, the kernel could not print various messages before the kernel crashed.
+- Native hardware with Windows 7 that was crashing
+- Vmware with Windows 10 and Visual Studio 2019 to compile the kernel module. Target platform
+  Windows 7 64-bit
+- Booting Windows 7 in test mode to allow unsigned kernel modules to run and with debug output
+  turned on
+- dbgview on Windows 7 machine to get local kernel dbg output

-Thus, I started stripping the kernel module step by step to narrow down the possible spots causing the crash. After a
-few hours, I got the (first) issue tracked down:
+Because I wanted to stick to Windows 7 in the beginning (refer to the solution section), I started
+debugging the kernel module by enabling the debug message output that was already available in the
+code. However, since kernel debug message printing can be very delayed, the kernel could not print
+various messages before the kernel crashed.

-After the firmware was flashed, the device had to re-enumerate. When this happens, the function *Ezusb_PnPAddDevice*
-is called to create a new instance of the device. Since this kernel module is acting as a filter driver, it has to
-trap this call, and add a filter device before the real device in the device stack. Thus, each call to the ezusb device
-hits the filter device first and the filter device calls the real device after doing some magic.
+Thus, I started stripping the kernel module step by step to narrow down the possible spots causing
+the crash. After a few hours, I got the (first) issue tracked down:

-*Ezusb_PnPAddDevice* calls *Ezusb_CreateDeviceObject*. Afterwards, it checks the status of the call to 
-*Ezusb_CreateDeviceObject* and if successful, it tries attaching the device to the device stack. However, instead of
-using *IoAttachDeviceToDeviceStackSafe* it uses the unsafe variant *IoAttachDeviceToDeviceStack* which can lead to a
-race condition on newer Windows Systems. Furthermore, all initialization of further variables of the *deviceObject*
-needs to happen BEFORE doing that. Again, this is a race condition.
+After the firmware was flashed, the device had to re-enumerate. When this happens, the function
+*Ezusb_PnPAddDevice* is called to create a new instance of the device. Since this kernel module is
+acting as a filter driver, it has to trap this call, and add a filter device before the real device
+in the device stack. Thus, each call to the ezusb device hits the filter device first and the filter
+device calls the real device after doing some magic.
+
+*Ezusb_PnPAddDevice* calls *Ezusb_CreateDeviceObject*. Afterwards, it checks the status of the call
+to *Ezusb_CreateDeviceObject* and if successful, it tries attaching the device to the device stack.
+However, instead of using *IoAttachDeviceToDeviceStackSafe* it uses the unsafe variant
+*IoAttachDeviceToDeviceStack* which can lead to a race condition on newer Windows Systems.
+Furthermore, all initialization of further variables of the *deviceObject* needs to happen BEFORE
+doing that. Again, this is a race condition.
+
+Next issue: Once the kernel calls *Ezusb_StartDevice* -> *Ezusb_ConfigureDevice* ->
+*Ezusb_SelectInterfaces*, it tries to use *USBD_ParseConfigurationDescriptorEx* to get the interface
+from the configuration descriptor. However, that fails for some unknown reason. I checked the data
+structure and it is perfectly fine and everything is there. Thus, I wrote my own version
+*Ezusb_GetInterfaceFromConfigurationDescriptor* which does all the magic required to get this part
+fixed:

-Next issue: Once the kernel calls *Ezusb_StartDevice* -> *Ezusb_ConfigureDevice* -> *Ezusb_SelectInterfaces*, it tries
-to use *USBD_ParseConfigurationDescriptorEx* to get the interface from the configuration descriptor. However, that
-fails for some unknown reason. I checked the data structure and it is perfectly fine and everything is there. Thus,
-I wrote my own version *Ezusb_GetInterfaceFromConfigurationDescriptor* which does all the magic required to get this
-part fixed:
 ```
 PUSB_INTERFACE_DESCRIPTOR Ezusb_GetInterfaceFromConfigurationDescriptor(
 	IN PUSB_CONFIGURATION_DESCRIPTOR ConfigurationDescriptor
@@ -89,15 +107,17 @@ PUSB_INTERFACE_DESCRIPTOR Ezusb_GetInterfaceFromConfigurationDescriptor(
 }
 ```

-And next issue is just up ahead: Following the above, we have to call *Ezusb_USBD_CreateConfigurationRequestEx* to
-create a USB configuration request to set the interface we want to use. This is executed with a *Ezusb_CallUSBD* call
-which sends request to the real hardware. However, this request always fails. The call *IoCallDriver* inside 
-*Ezusb_CallUSBD* always returns an NTSTATUS code that is not documented anywhere (can't find the exact status code
-anymore, but once you get it, try to find it in the header file).
+And next issue is just up ahead: Following the above, we have to call
+*Ezusb_USBD_CreateConfigurationRequestEx* to create a USB configuration request to set the interface
+we want to use. This is executed with a *Ezusb_CallUSBD* call which sends request to the real
+hardware. However, this request always fails. The call *IoCallDriver* inside *Ezusb_CallUSBD* always
+returns an NTSTATUS code that is not documented anywhere (can't find the exact status code anymore,
+but once you get it, try to find it in the header file).

 At this point, I had to give up. I already wasted too many hours and this is clearly a dead end.

 ## The solution
-Once I realized that I got stuck with Windows 7 and I didn't want to buy (more) new hardware, I gave Windows 10 a try.
-Surprisingly, this solved all the issues and the kernel module runs fine. The C02 board is flashable without crashing
-and works with newer IIDX games.
+
+Once I realized that I got stuck with Windows 7 and I didn't want to buy (more) new hardware, I gave
+Windows 10 a try. Surprisingly, this solved all the issues and the kernel module runs fine. The C02
+board is flashable without crashing and works with newer IIDX games.
--- a/doc/dev/journal/2019-10-07-iidx-gfx-rendering-loops.md
+++ b/doc/dev/journal/2019-10-07-iidx-gfx-rendering-loops.md
@@ -1,25 +1,31 @@
 # Notes outlining some aspects of the DirectX calls which were required to know to implement a up-/downscaling feature
-As the title says, this outlines some aspects I needed to figure out in order to implement a up-/downscaling feature
-within the d3d9 hook module that works on all currently available IIDX versions (9 to 26).

-To analyze the rendering loops, I have used a tool called apitrace which traces the calls of many graphic APIs:
-https://github.com/apitrace/apitrace
+As the title says, this outlines some aspects I needed to figure out in order to implement a
+up-/downscaling feature within the d3d9 hook module that works on all currently available IIDX
+versions (9 to 26).

-Defintely recommended to quickly figure out what is going on regarding rendering. It also allows you to let you render
-parts of a scene after the application exited because it records all API calls and data passed to them.
+To analyze the rendering loops, I have used a tool called apitrace which traces the calls of many
+graphic APIs: https://github.com/apitrace/apitrace

-Anyway, considering the various iterations in (GPU) hardware the game had to undergo combined with weird quirks and
-"fixes" Bemanitools is undoing, I wouldn't have guessed that their rendering engine was nearly the same until IIDX 20.
-That's when they introduced SD/HD mode.
+Defintely recommended to quickly figure out what is going on regarding rendering. It also allows you
+to let you render parts of a scene after the application exited because it records all API calls and
+data passed to them.

-In this case, that's great news because I had to craft a solution that allows up-/downscaling the final frame to
-different resolutions (see the iidxhook-util/d3d9 module for more details about the feature).
+Anyway, considering the various iterations in (GPU) hardware the game had to undergo combined with
+weird quirks and "fixes" Bemanitools is undoing, I wouldn't have guessed that their rendering engine
+was nearly the same until IIDX 20. That's when they introduced SD/HD mode.
+
+In this case, that's great news because I had to craft a solution that allows up-/downscaling the
+final frame to different resolutions (see the iidxhook-util/d3d9 module for more details about the
+feature).

 But first, we need a breakdown of the render loop's most relevant parts for this:

 ## IIDX pre 20
-Using apitrace, we can see the following outline of a frame (not counting the first one that does a lot of setup in
-the beginning):
+
+Using apitrace, we can see the following outline of a frame (not counting the first one that does a
+lot of setup in the beginning):
+
 ```
 BeginScene
 Clear
@@ -31,12 +37,14 @@ Present

 No render target switching, simply render everything to the back buffer...plain and simple.

-Note: The viewport size is determined by the size returned by GetClientRect, wtf.
-Welp, no official Konmai seal of approval without that. ¯\_(ツ)_/¯
+Note: The viewport size is determined by the size returned by GetClientRect, wtf. Welp, no official
+Konmai seal of approval without that. ¯\_(ツ)\_/¯

 ## IIDX 20+
-Using apitrace, we can see the following outline of a frame (not counting the first one that does a lot of setup in
-the beginning):
+
+Using apitrace, we can see the following outline of a frame (not counting the first one that does a
+lot of setup in the beginning):
+
 ```
 BeginScene
 // tex1 is a render target texture with size 1280x720 (also in SD mode)
@@ -63,26 +71,30 @@ EndScene -> ErrInvalidCall return code
 Present
 ```

-This is quite a different flow to implement HD and SD mode but the solution to solve that particular problem is straight
-forward and easy to understand. This means that the game will always render in HD mode and only downscale the final
-frame to SD resolution for 640x480 output.
+This is quite a different flow to implement HD and SD mode but the solution to solve that particular
+problem is straight forward and easy to understand. This means that the game will always render in
+HD mode and only downscale the final frame to SD resolution for 640x480 output.

-Also, why the fuck do they call BeginScene and EndScene twice? Looks like they wanted to do this in two separate scenes
-for some reason. Checking the return values would have revealed to them that something's not right...lucky them that
-this code works nevertheless.
-Another Konmai seal of approval, a job well done. ¯\_(ツ)_/¯
+Also, why the fuck do they call BeginScene and EndScene twice? Looks like they wanted to do this in
+two separate scenes for some reason. Checking the return values would have revealed to them that
+something's not right...lucky them that this code works nevertheless. Another Konmai seal of
+approval, a job well done. ¯\_(ツ)\_/¯

 ## iidxhook's up-/downscaling solution
-The initial solution simply hooked into BeginScene and EndScene and let the game render to an intermediate render
-target texture. The texture was scaled according to the actual target frame buffer size before getting presented. This
-solution worked fine for pre IIDX 20 games but created a black screen on IIDX 20+.

-In order to avoid two different scaling flows, the final solution that works for both does the following:
-* Create a render target texture with native resolution and let the game render to it
-* Set the render target to that intermediate render target texture on BeginScene
-* Before Present
-    * Scale the intermediate render target texture to the back buffer
-    * Set the back buffer as the render target
-* Present frame
+The initial solution simply hooked into BeginScene and EndScene and let the game render to an
+intermediate render target texture. The texture was scaled according to the actual target frame
+buffer size before getting presented. This solution worked fine for pre IIDX 20 games but created a
+black screen on IIDX 20+.

-Just an outline which follows the actual implementation that you can find in the iidxhook-util/d3d9.
+In order to avoid two different scaling flows, the final solution that works for both does the
+following:
+
+- Create a render target texture with native resolution and let the game render to it
+- Set the render target to that intermediate render target texture on BeginScene
+- Before Present
+  - Scale the intermediate render target texture to the back buffer
+  - Set the back buffer as the render target
+- Present frame
+
+Just an outline which follows the actual implementation that you can find in the iidxhook-util/d3d9.
--- a/doc/dev/journal/2020-12-16-acio-bio2-iidx-package-dump.md
+++ b/doc/dev/journal/2020-12-16-acio-bio2-iidx-package-dump.md
@@ -1,21 +1,25 @@
 # ACIO BIO2 IIDX package dump
-Package dump excerpt of the init sequence of a original Konami IIDX BIO2 with sub IO connected.
-This was used to identify a missing piece of information that needs to be communicated to the BIO2
-for IIDX to initialize the sub IO correctly.
+
+Package dump excerpt of the init sequence of a original Konami IIDX BIO2 with sub IO connected. This
+was used to identify a missing piece of information that needs to be communicated to the BIO2 for
+IIDX to initialize the sub IO correctly.

 The dump was cut off after two polls as the sequence just keeps on repeating from that point on.

 ## Findings for problem to solve
-With the previous implemention of the BIO2 driver, which was created off references of SDVX KFCA,
-a BIO2 used with IIDX and the sub IO (to upgrade older C02, IO2 cabinets) connected didn't
-initialize properly. This resulted in no inputs/outputs other than 14 keys working.
+
+With the previous implemention of the BIO2 driver, which was created off references of SDVX KFCA, a
+BIO2 used with IIDX and the sub IO (to upgrade older C02, IO2 cabinets) connected didn't initialize
+properly. This resulted in no inputs/outputs other than 14 keys working.

 The problem identified was a different byte, exact meaning not known, that is sent in
 [exchange 4](#exchange-4-ac-io-cmd-clear). Instead of `0x3B` from the SDVX KFCA based
 implementation, it needs to be set to `0x2D`.

 ## Exchange 1: AC_IO_CMD_ASSIGN_ADDRS
+
 ### Write
+
 ```text
 AA 00 00 01 00 01 00 02

@@ -29,6 +33,7 @@ data: 00
 ```

 ### Read
+
 ```
 AA AA 00 00 01 00 01 01 03

@@ -43,7 +48,9 @@ AA: SOF
 ```

 ## Exchange 2: AC_IO_CMD_GET_VERSION
+
 ### Write
+
 ```
 AA 01 00 02 00 00 03

@@ -56,6 +63,7 @@ AA: SOF
 ```

 ### Read
+
 ```
 AA AA 81 00 02 00 2C 0D 06 00 00 ...

@@ -70,7 +78,9 @@ XX: checksum
 ```

 ## Exchange 3: AC_IO_CMD_START_UP
+
 ### Write
+
 ```
 AA 01 00 03 00 00 04

@@ -83,6 +93,7 @@ AA: SOF
 ```

 ### Read
+
 ```
 AA AA 81 00 03 00 01 00 85

@@ -97,7 +108,9 @@ AA: SOF
 ```

 ## Exchange 4: AC_IO_CMD_CLEAR
+
 ### Write
+
 ```
 AA 01 01 00 00 01 2D 30

@@ -111,6 +124,7 @@ AA: SOF
 ```

 ### Read
+
 ```
 AA AA 81 01 00 00 01 00 83

@@ -125,7 +139,9 @@ AA: SOF
 ```

 ## Exchange 5: BIO2_BI2A_CMD_WATCHDOG
+
 ### Write
+
 ```
 AA 01 01 20 00 02 00 00 24

@@ -139,6 +155,7 @@ AA: SOF
 ```

 ### Read
+
 ```
 AA AA 81 01 20 00 01 00 A3

@@ -153,7 +170,9 @@ A3: checksum
 ```

 ## Exchange 6: BIO2_BI2A_CMD_POLL
+
 ### Write
+
 ```
 AA 01 01 52 00 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 84

@@ -167,6 +186,7 @@ AA: SOF
 ```

 ### Read
+
 ```
 AA AA 81 01 52 00 2E 00 00 B0 00 F0 00 F0 F0 00 00 00 00 00 02 00 5F 11 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 F3

@@ -181,12 +201,15 @@ F3: checksum
 ```

 ## Exchange 7: BIO2_BI2A_CMD_POLL
+
 ### Write
+
 ```
 AA 01 01 52 00 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 84
 ```

 ### Read
+
 ```
 AA AA 81 01 52 00 2E 00 00 B0 00 F0 00 F0 F0 00 00 00 00 00 02 00 64 11 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 F8
-```
+```
--- a/doc/dev/journal/2023-04-03-d01-ezusb-io-boot-security.md
+++ b/doc/dev/journal/2023-04-03-d01-ezusb-io-boot-security.md
@@ -1,30 +1,29 @@
 # Beatmania IIDX 10th Style - D01 IO boot code and security init

-Date: 2023-04-03
-Author: icex2
+Date: 2023-04-03 Author: icex2

 Documenting decompiled and reverse engineered code snippets from the D01 JAE `bm2dx.exe`. These
 helped me figuring out the two different security boot modes the game supports.

-In summary, it supports booting with the C02 IO with a C02 black dongle and a D01 IO board with
-a D01 dongle. No other combination is valid because they didn't make sense back then. You either
-had an upgraded old style/twinkle cabinet to C02 (GEC02) or you bought a new dedicated cabinet
-(GQD01). With 10th style supporting the old C02 dongle, it appears that all owners of a C02 cabinet
-with IO board and C02 dongle received a free software update/HDD. This might make sense considering
-the short life span of C02 and the game being super buggy, especially in earlier/initial revisions.
+In summary, it supports booting with the C02 IO with a C02 black dongle and a D01 IO board with a
+D01 dongle. No other combination is valid because they didn't make sense back then. You either had
+an upgraded old style/twinkle cabinet to C02 (GEC02) or you bought a new dedicated cabinet (GQD01).
+With 10th style supporting the old C02 dongle, it appears that all owners of a C02 cabinet with IO
+board and C02 dongle received a free software update/HDD. This might make sense considering the
+short life span of C02 and the game being super buggy, especially in earlier/initial revisions.

 The game expects the following "configurations" from bemanitools:

-* Booting as upgraded C02 with free D01 upgrade
-  * `sec.boot_version=GEC02   `
-  * `sec.boot_seeds=0:0:1`
-  * `sec.black_plug_mcode=GEC02JAA`
-  * "D01 IO pin" on IO board not active
-* Booting as dedicated 
-  * `sec.boot_version=GEC02   `
-  * `sec.boot_seeds=0:1:1`
-  * `sec.black_plug_mcode=GQD01JAA`
-  * "D01 IO pin" on IO board ACTIVE
+- Booting as upgraded C02 with free D01 upgrade
+  - `sec.boot_version=GEC02   `
+  - `sec.boot_seeds=0:0:1`
+  - `sec.black_plug_mcode=GEC02JAA`
+  - "D01 IO pin" on IO board not active
+- Booting as dedicated
+  - `sec.boot_version=GEC02   `
+  - `sec.boot_seeds=0:1:1`
+  - `sec.black_plug_mcode=GQD01JAA`
+  - "D01 IO pin" on IO board ACTIVE

 All the above was derived from reading and understanding the documented code excerpts below.

@@ -286,4 +285,4 @@ int io_init_security()
  set_io_error_type(-1, aNgSecurity);
  return -1;
 }
-```
+```
--- a/doc/dev/journal/2023-04-13-iidx-24-gfx-upscaling.md
+++ b/doc/dev/journal/2023-04-13-iidx-24-gfx-upscaling.md
@@ -1,18 +1,17 @@
 # IIDX 24 GFX upscaling notes

-Date: 2023-04-15
-Author: icex2
+Date: 2023-04-15 Author: icex2

-Notes about my work on fixing the upscaling/downscaling feature of bemanitools for IIDX 20 to 26.
-I realized that the render backend changed significantly that the old method that worked fine
-doesn't work anymore.
+Notes about my work on fixing the upscaling/downscaling feature of bemanitools for IIDX 20 to 26. I
+realized that the render backend changed significantly that the old method that worked fine doesn't
+work anymore.

 The tool used in the screenshots is [apitrace](https://github.com/apitrace/apitrace).

 ## IIDX 24

 The GFX engine in IIDX from 20 to 26 has a changed render loop that includes built-in scaling to
-implement the SD and HD/HD* screen settings that are selectable in the operator menu
+implement the SD and HD/HD\* screen settings that are selectable in the operator menu

 ### Frame 0 - GFX init part

@@ -28,15 +27,15 @@ Start the scene and set the render target to the intermediate texture.
 ![](2023-04-13-iidx-24-gfx-upscaling/beginscene.png)

 After done drawing the scene, the intermediate texture is blended to the framebuffer. With a target
-2D plane having the size of the target resolution, the blending applies linear scaling to either
-up- or downscale the final image.
+2D plane having the size of the target resolution, the blending applies linear scaling to either up-
+or downscale the final image.

 ![](2023-04-13-iidx-24-gfx-upscaling/scaling.png)

 ## IIDX 10

-A recap of the old stuff, see also [my previous notes](2019-10-07-iidx-gfx-rendering-loops.md),
-as I had to look at everything again to properly understand the differences.
+A recap of the old stuff, see also [my previous notes](2019-10-07-iidx-gfx-rendering-loops.md), as I
+had to look at everything again to properly understand the differences.

 ### Frame 0 - GFX init part

@@ -47,11 +46,11 @@ buffer.

 ### Frame 1 - A clean main render path

-Beginning the scene excerpt. The viewport needs to match the target resolution to display the
-final image correctly.
+Beginning the scene excerpt. The viewport needs to match the target resolution to display the final
+image correctly.

 ![](2023-04-13-iidx-24-gfx-upscaling/beginscene10.png)

 Ending the scene excerpt, nothing fancy here, just swapping the back buffer.

-![](2023-04-13-iidx-24-gfx-upscaling/endscene10.png)
+![](2023-04-13-iidx-24-gfx-upscaling/endscene10.png)
--- a/doc/dev/journal/2023-05-28-ddr-p3io-driver-work.md
+++ b/doc/dev/journal/2023-05-28-ddr-p3io-driver-work.md
@@ -1,7 +1,6 @@
 # DDR p3io driver work, various notes

-Date: 2023-05-28
-Author: icex2
+Date: 2023-05-28 Author: icex2

 Notes about my work on writing a DDR P3io driver.

@@ -13,114 +12,116 @@ PCB breakout interfaces/connectors on the side of the boards.

 Descriptions assume cabinet hardware of an upgraded DDR "black SD cabinet"

-* `LINE OUT 1`: Primary audio out to amplifier
-* `LINE OUT 2`: N.C.
-* `RGB`: Video out to monitor, supports 15khz/31khz based on hardware switch for video freq/mode selection
-* `COM1`: Virtual com port that connects to the EXTIO
-* `COM2`: Virtual com port that connects to a pair of ICCA card readers
-* `LAN`: Network connection
-* `PWR`: 100V power in
-* `ANALOG`: N.C.
-* `PORT 1`: Lights output for cabinet lights, e.g. menu button lights, top header lights
-* `PORT 2`: N.C.
-* `DIPSW`
-  * `1`: ???
-  * `2`: On = force all sensor polling mode and allow running the game without an EXTIO
-  * `3`: ???
-  * `4`: On = force 15 khz monitor output
-* `PLUG 1`: Black dongle
-* `PLUG 2`: White dongle
+- `LINE OUT 1`: Primary audio out to amplifier
+- `LINE OUT 2`: N.C.
+- `RGB`: Video out to monitor, supports 15khz/31khz based on hardware switch for video freq/mode
+  selection
+- `COM1`: Virtual com port that connects to the EXTIO
+- `COM2`: Virtual com port that connects to a pair of ICCA card readers
+- `LAN`: Network connection
+- `PWR`: 100V power in
+- `ANALOG`: N.C.
+- `PORT 1`: Lights output for cabinet lights, e.g. menu button lights, top header lights
+- `PORT 2`: N.C.
+- `DIPSW`
+  - `1`: ???
+  - `2`: On = force all sensor polling mode and allow running the game without an EXTIO
+  - `3`: ???
+  - `4`: On = force 15 khz monitor output
+- `PLUG 1`: Black dongle
+- `PLUG 2`: White dongle

 ### P3IO GF/DM

-Descriptions assume usage of a P3IO from a GF/DM in a "chimera style PCB build" on an upgraded
-DDR "black SD cabinet"
+Descriptions assume usage of a P3IO from a GF/DM in a "chimera style PCB build" on an upgraded DDR
+"black SD cabinet"

-* `PWR`: 100V power in
-* `12V-OUT`: +12V out for external devices
-* `PORT 1`: Lights output for cabinet lights, e.g. menu button lights, top header lights
-* `PORT 2`: N.C.
-* `COM1`: To EXTIO
-* `COM2`: To card readers
-* `RGB`: Video out to monitor, supports 15khz/31khz based on hardware switch for video freq/mode selection
-* `LINE OUT 1`: Primary audio out to amplifier
-* `LINE OUT 2`: N.C.
-* `DIPSW`
-  * `1`:
-  * `2`: 
-  * `3`: 
-  * `4`: On = force 15 khz monitor output
-* `PLUG 1`: Roundplug black dongle
-* `PLUG 2`: Roundplug white dongle
+- `PWR`: 100V power in
+- `12V-OUT`: +12V out for external devices
+- `PORT 1`: Lights output for cabinet lights, e.g. menu button lights, top header lights
+- `PORT 2`: N.C.
+- `COM1`: To EXTIO
+- `COM2`: To card readers
+- `RGB`: Video out to monitor, supports 15khz/31khz based on hardware switch for video freq/mode
+  selection
+- `LINE OUT 1`: Primary audio out to amplifier
+- `LINE OUT 2`: N.C.
+- `DIPSW`
+  - `1`:
+  - `2`:
+  - `3`:
+  - `4`: On = force 15 khz monitor output
+- `PLUG 1`: Roundplug black dongle
+- `PLUG 2`: Roundplug white dongle

 ### P3IO DDR(X)

 Descriptions assume cabinet hardware of an upgraded DDR "black SD cabinet"

-* `PWR`: 100V power in
-* `USB`: USB memory card readers on cabinet
-* `PORT 1`: Lights output for cabinet lights, e.g. menu button lights, top header lights
-* `COM3-4`: Virtual COM ports
-  * COM3 (VCOM1): Pins 1,3,5 on connector -> To card readers
-  * COM4 (VCOM0): Pins 2,4,6 on connector -> N.C.
-* `PLUG`: Breakout to security round plugs (black and white dongles)
-* `COM1`: To EXTIO
-  * Pinout (pins left to right)
-    * 1: TXD1
-    * 2: RXD1
-    * 3: N.C.
-    * 4: N.C.
-    * 5: GND
-* `COM2`: N/A (light spires on black HD cabinet)
-  * Pinout (pins left to right)
-    * 1: TXD2
-    * 2: RXD2
-    * 3: GND
-* `RGB`: Video out to monitor, supports 15khz/31khz based on hardware switch for video freq/mode selection
-* `LINE OUT1`: Primary audio out to amplifier
-* `LINE OUT2`: N.C.
-* `LAN`: Network
-* `DIP SW`
-  * `1`:
-  * `2`: 
-  * `3`: 
-  * `4`: On = force 15 khz monitor output
+- `PWR`: 100V power in
+- `USB`: USB memory card readers on cabinet
+- `PORT 1`: Lights output for cabinet lights, e.g. menu button lights, top header lights
+- `COM3-4`: Virtual COM ports
+  - COM3 (VCOM1): Pins 1,3,5 on connector -> To card readers
+  - COM4 (VCOM0): Pins 2,4,6 on connector -> N.C.
+- `PLUG`: Breakout to security round plugs (black and white dongles)
+- `COM1`: To EXTIO
+  - Pinout (pins left to right)
+    - 1: TXD1
+    - 2: RXD1
+    - 3: N.C.
+    - 4: N.C.
+    - 5: GND
+- `COM2`: N/A (light spires on black HD cabinet)
+  - Pinout (pins left to right)
+    - 1: TXD2
+    - 2: RXD2
+    - 3: GND
+- `RGB`: Video out to monitor, supports 15khz/31khz based on hardware switch for video freq/mode
+  selection
+- `LINE OUT1`: Primary audio out to amplifier
+- `LINE OUT2`: N.C.
+- `LAN`: Network
+- `DIP SW`
+  - `1`:
+  - `2`:
+  - `3`:
+  - `4`: On = force 15 khz monitor output

 ## Python IO boards and differences

 ### P3IO DDR(X)

-* Connects to USB and actually enumerates as a USB device and not a virtual COM port
-* COM ports 1-4 on breakout of the PCB are being passed through as actual COM ports to the operating system
+- Connects to USB and actually enumerates as a USB device and not a virtual COM port
+- COM ports 1-4 on breakout of the PCB are being passed through as actual COM ports to the operating
+  system

 ### P3IO GF/DM

-* Connects to USB and actually enumerates as a USB device and not a virtual COM port
-* COM ports 1-2 on breakout of the PCB are just virtual COM ports
-* These do not show up as COM ports on the operating system
-* The game drives the COM ports through the main P3IO protocol with additional P3IO commands
-  to open, read, write and close these virtual COM ports
+- Connects to USB and actually enumerates as a USB device and not a virtual COM port
+- COM ports 1-2 on breakout of the PCB are just virtual COM ports
+- These do not show up as COM ports on the operating system
+- The game drives the COM ports through the main P3IO protocol with additional P3IO commands to
+  open, read, write and close these virtual COM ports

 ### P2IO DDR

-* Connects to USB and actually enumerates as a USB device and not a virtual COM port
-* COM ports 1-2 on breakout of the PCB are just virtual COM ports
-* These do not show up as COM ports on the operating system
-* The game drives the COM ports through the main P3IO protocol with additional P3IO commands
-  to open, read, write and close these virtual COM ports
-
+- Connects to USB and actually enumerates as a USB device and not a virtual COM port
+- COM ports 1-2 on breakout of the PCB are just virtual COM ports
+- These do not show up as COM ports on the operating system
+- The game drives the COM ports through the main P3IO protocol with additional P3IO commands to
+  open, read, write and close these virtual COM ports

 ## Pinout card reader P1 -> P2 mini din8 male to mini din8 male

-Port 1 2 and 3: 
+Port 1 2 and 3:

-* Pin 3: TX
-* Pin 4: GND
-* Pin 5 : RX
+- Pin 3: TX
+- Pin 4: GND
+- Pin 5 : RX

-Pin 3 and 5 need to be reversed inbetween readers 
-They are all the same, so your cable needs to bridge them over.
-A standard male to male mini din 8 cable does not do that.
+Pin 3 and 5 need to be reversed inbetween readers They are all the same, so your cable needs to
+bridge them over. A standard male to male mini din 8 cable does not do that.

 ### Pinout card reader stock cable s-sub9 to round pin9

@@ -135,16 +136,16 @@ dsub-9 female -> mini-din8 male

 Default or incorrectly configured?

-* `COM1` -> on mainboard
-* `COM2` -> COM2 on P3IO breakout
-* `COM3` -> ???
-* `COM4` -> COM1 on P3IO breakout
+- `COM1` -> on mainboard
+- `COM2` -> COM2 on P3IO breakout
+- `COM3` -> ???
+- `COM4` -> COM1 on P3IO breakout

 ## P3IO command init sequence on DDR 18

 From the ddrio-python23 library

-```text
+````text
 .data:1002D5D0 g_init_pakets   db 0AAh, 2, 0, 1, 29h dup(0); field_0.field_0
 .data:1002D5D0                                         ; DATA XREF: initialize_and_send_pakets+5↑o
 .data:1002D5D0                 db 0AAh, 2, 0, 2Fh, 29h dup(0); field_0.field_0
@@ -191,4 +192,4 @@ From the ddrio-python23 library
 // 29: get video freq
 // 5: set watchdog
 // 27: get cab type or dipsw
-```
+````
--- a/doc/development.md
+++ b/doc/development.md
@@ -1,50 +1,62 @@
 # Development
-This document is intended for developers interested in contributing to Bemanitools. Please read this document before
-you start developing.
+
+This document is intended for developers interested in contributing to Bemanitools. Please read this
+document before you start developing.

 ## Goals
-We want you to understand what this project is about and its goals. The following list serves as a guidance for all
-developers to identify valuable contributions for this project. As the project evolves, these gaols might do as well.

-* Allow running Konami arcade rhythm games, i.e. games of the Bemani series, on arbitrary hardware.
-    * Emulate required software and hardware features.
-    * Provide means to cope with incompatibility issues resulting from using a different software platform (e.g. version
-    of Windows). 
-* Provide an API for custom interfaces and configuring fundamental application features.
+We want you to understand what this project is about and its goals. The following list serves as a
+guidance for all developers to identify valuable contributions for this project. As the project
+evolves, these gaols might do as well.
+
+- Allow running Konami arcade rhythm games, i.e. games of the Bemani series, on arbitrary hardware.
+  - Emulate required software and hardware features.
+  - Provide means to cope with incompatibility issues resulting from using a different software
+    platform (e.g. version of Windows).
+- Provide an API for custom interfaces and configuring fundamental application features.

 ## Development environment
+
 The following tooling is required in order to build this project.

 ### Tooling
+
 #### Linux / MacOSX
-* git
-* make
-* mingw-w64
-* clang-format
-* wine (optional, for running tests or some quick testing without requiring a VM)
+
+- git
+- make
+- mingw-w64
+- clang-format
+- wine (optional, for running tests or some quick testing without requiring a VM)

 On MacOSX, you can use homebrew or macports to install these packages.

 #### Windows
+
 TODO

 ### IDE
-Ultimately, you are free to use whatever you feel comfortable with for development. The following is our preferred
-development environment which we run on a Linux distribution of our choice:
-* Visual Studio Code with the following extensions
-    * C/C++
-    * C++ Intellisense
-    * Clang-Format
+
+Ultimately, you are free to use whatever you feel comfortable with for development. The following is
+our preferred development environment which we run on a Linux distribution of our choice:
+
+- Visual Studio Code with the following extensions
+  - C/C++
+  - C++ Intellisense
+  - Clang-Format

 ### Further tools for testing and debugging
-* Debugger: Can be part of your reverse engineering IDE of your choice or stand-along like
-[OllyDbg](http://www.ollydbg.de/).
-* [apitrace](https://apitrace.github.io/): Trace render calls to graphics APIs like D3D and OpenGL.
-This tool allows you to record and re-play render calls of an application with frame-by-frame 
-debugging. Very useful to analyze the render pipeline or debug graphicial glitches.
+
+- Debugger: Can be part of your reverse engineering IDE of your choice or stand-along like
+  [OllyDbg](http://www.ollydbg.de/).
+- [apitrace](https://apitrace.github.io/): Trace render calls to graphics APIs like D3D and OpenGL.
+  This tool allows you to record and re-play render calls of an application with frame-by-frame
+  debugging. Very useful to analyze the render pipeline or debug graphicial glitches.

 ## Building
+
 Simply run make in the root folder:
+
 ```
 make
 ```
@@ -52,17 +64,20 @@ make
 All output is located in the *build* folder including the final *bemanitools.zip* package.

 Note about using `-j n` option on make: This is currently considered broken/unreliable. Expect to
-run into odd issues like randomly changing unresolved dependency errors. If you attempted this,
-run a `make clean` before running `make` again.
+run into odd issues like randomly changing unresolved dependency errors. If you attempted this, run
+a `make clean` before running `make` again.

 ### Release building
-A release build is a clean build including code formatting and testing. This can be executed by running the following
-command:
+
+A release build is a clean build including code formatting and testing. This can be executed by
+running the following command:
+
 ```
 make release
 ```

 ## Building with docker
+
 You can also build bemanitools using docker which avoids having to setup a full development
 environment if you are just interested in building binaries for the latest changes. Naturally, this
 requires you to have the docker daemon installed. Then, run the following command from the root
@@ -75,28 +90,35 @@ make build-docker
 Once completed successfully, the build output is located in the `build/docker` sub-folder.

 ## Creating releases
+
 For developers to create official releases with major and minor versioning:
+
 1. Ensure that all everything you want to have for this release is merged into master.
 1. Create a [changelog](CHANGELOG.md) based on aggregating and summerizing commit messages of
-whatever got added starting from the tag of the current version to the current head of master.
-Commit that changelog and push to master.
+   whatever got added starting from the tag of the current version to the current head of master.
+   Commit that changelog and push to master.
 1. Create a tag with the next version number, e.g. for 5.28:
+
 ```bash
 git tag v5.28
 ```
+
 1. Push the tag upstream:
+
 ```bash
 git push origin v5.28
 ```
+
 1. Wait for the CI pipeline to finish building the release and check if everything's ok.
 1. On GitLab, go to "Tags" in the repository, click on the commit ID below the tag in the list you
-just created.
+   just created.
 1. Click on the "Pipelines" tab and click on the download button on the right and on "Download
-release artifacts".
-1. Rename the downloaded zip to "bemanitools-v5.28.zip" and the replace v5.28 with the version
-you want to release.
+   release artifacts".
+1. Rename the downloaded zip to "bemanitools-v5.28.zip" and the replace v5.28 with the version you
+   want to release.
 1. Upload the release.
 1. For publishing the release, create a post with the following contents:
+
 ```
 v5.28
 <insert link to uploaded zip here>
@@ -108,53 +130,66 @@ Changelog copy-paste:
 ```

 ## Code formatting
+
 To apply our code style using clang-format, simply run the following command:
+
 ```
 make code-format
 ```

-Please also refer to the [section about](###Additional-code-style-guidelines) which cannot be covered using
-clang-format.
+Please also refer to the [section about](###Additional-code-style-guidelines) which cannot be
+covered using clang-format.

 ## Testing
-This still needs to be improved/implemented properly to run the unit-tests easily. Currently, you have to be on either
-a Linux/MacOSX system and run
+
+This still needs to be improved/implemented properly to run the unit-tests easily. Currently, you
+have to be on either a Linux/MacOSX system and run
+
 ```
 make run-tests
 ```
-This executes all currently available unit-tests and reports to the terminal any errors. This requires wine to be
-installed.
+
+This executes all currently available unit-tests and reports to the terminal any errors. This
+requires wine to be installed.

 ## Project structure
+
 Now that your setup is ready to go, here is brief big picture of what you find in this project.

-* build: This folder will be generated once you have run the build process.
-* dist: Distribution related files such as (default) configuration files, shell scripts, etc.
-* doc: Documentation for the tools and hooks as well as some development related docs.
-* src: The source code
-    * imports: Provides headers and import definitions for AVS libs and a few other dependencies.
-    * main: The main source code with game specific hook libraries, hardware emulation and application fixes.
-    * test: Unit tests for modules that are not required for hooking or the presence of a piece of hardware.
-* .clang-format: Code style for clang-format.
-* GNUmakefile: Our makefile to build this project.
-* Module.mk: Defines the various libraries and exe files to build for the distribution packages.
+- build: This folder will be generated once you have run the build process.
+- dist: Distribution related files such as (default) configuration files, shell scripts, etc.
+- doc: Documentation for the tools and hooks as well as some development related docs.
+- src: The source code
+  - imports: Provides headers and import definitions for AVS libs and a few other dependencies.
+  - main: The main source code with game specific hook libraries, hardware emulation and application
+    fixes.
+  - test: Unit tests for modules that are not required for hooking or the presence of a piece of
+    hardware.
+- .clang-format: Code style for clang-format.
+- GNUmakefile: Our makefile to build this project.
+- Module.mk: Defines the various libraries and exe files to build for the distribution packages.

 ## Code style and guidelines
-Please follow these guidelines to keep a consistent style for the code base. Furthermore, we provide some best practices
-that have shown to be helpful. Please read them and reach out to us if you have any concerns or valuable
-additions/changes.
+
+Please follow these guidelines to keep a consistent style for the code base. Furthermore, we provide
+some best practices that have shown to be helpful. Please read them and reach out to us if you have
+any concerns or valuable additions/changes.

 ### Clang-format
-The style we agreed on is provided as a clang-format file. Therefore, we use clang-format for autoformatting our code.

-You can use clang-format from your terminal but when using Visual Studio Code, just install the extension. Apply
-formatting manually at the end or enable the "reformat on save" feature.
+The style we agreed on is provided as a clang-format file. Therefore, we use clang-format for
+autoformatting our code.

-However, clang-format cannot provide guidance to cover all our style rules. Therefore, we ask you to stick to the 
-"additional" guidelines in the following sections.
+You can use clang-format from your terminal but when using Visual Studio Code, just install the
+extension. Apply formatting manually at the end or enable the "reformat on save" feature.
+
+However, clang-format cannot provide guidance to cover all our style rules. Therefore, we ask you to
+stick to the "additional" guidelines in the following sections.

 ### Additional code style guidelines
+
 #### No trailing comments
+
 ```
 // NOPE
 int var = 1; // this is a variable
@@ -165,11 +200,13 @@ int var = 1;
 ```

 #### Comment style
-* Use either // or /* ... */ for single line.
-* Use /* ... */ for multiline comments.
-* Use /* ... */ for documentation.
+
+- Use either // or /\* ... \*/ for single line.
+- Use /\* ... \*/ for multiline comments.
+- Use /\* ... \*/ for documentation.

 Examples:
+
 ```
 // single line comment
 int var = 1;
@@ -188,9 +225,12 @@ int func(int a, int b);
 ```

 #### Include guards
-Provide include guards for every header file. The naming follows the namespacing of the module and the module name.
+
+Provide include guards for every header file. The naming follows the namespacing of the module and
+the module name.

 Example for bsthook/acio.h file:
+
 ```
 #ifndef BSTHOOK_ACIO_H
 #define BSTHOOK_ACIO_H
@@ -201,11 +241,13 @@ Example for bsthook/acio.h file:
 ```

 #### Empty line before and after control blocks
+
 Control blocks include: if, if-else, for, while, do-while, switch

 Makes the code more readible with control blocks being easily visible.

 Example
+
 ```
 int var = 1;

@@ -217,7 +259,10 @@ printf("%d\n", var);
 ```

 #### Empty line at the start of blocks
-There are situations when you want to have an empty line at the start of the block to enhance readability, for example:
+
+There are situations when you want to have an empty line at the start of the block to enhance
+readability, for example:
+
 ```
 if (a && 
    b && 
@@ -227,6 +272,7 @@ if (a &&
 ```

 Here the assignment aligns with the conditions of the if-black making it hard to read. Better:
+
 ```
 if (a && 
    b && 
@@ -237,20 +283,22 @@ if (a &&
 ```

 #### Includes
-* Always keep all includes at the top of a header and source file. Exception: Documentation before include guards on
-header file.
-* Use *< >* for system-based includes, e.g. <stdio.h>.
-* Use *" "* for project-based includes, e.g. "util/log.h".
-* For project-based includes, always use the full path relative to the root folder (src/main, src/test), e.g. 
-"util/log.h" and not "log.h" when being in another module in the "util" namespace.
-* Sorting
-    * System-based includes before project-based includes
-    * Block group them by different namespaces
-    * Lex sort block groups
-    * Because windows header files are a mess, the sorting on system-based includes is not always applicable. Please add
-    a comment when applicable and apply the necessary order.
+
+- Always keep all includes at the top of a header and source file. Exception: Documentation before
+  include guards on header file.
+- Use *\< >* for system-based includes, e.g. \<stdio.h>.
+- Use *" "* for project-based includes, e.g. "util/log.h".
+- For project-based includes, always use the full path relative to the root folder (src/main,
+  src/test), e.g. "util/log.h" and not "log.h" when being in another module in the "util" namespace.
+- Sorting
+  - System-based includes before project-based includes
+  - Block group them by different namespaces
+  - Lex sort block groups
+  - Because windows header files are a mess, the sorting on system-based includes is not always
+    applicable. Please add a comment when applicable and apply the necessary order.

 Example for sorting
+
 ```
 #include <stdio.h>
 #include <string.h>
@@ -264,25 +312,30 @@ Example for sorting
 ```

 ### Documentation
-In general, add comments where required to explain a certain piece of code. If is not self-explanatory about:
-* Why is it implemented like this
-* Very important details to understand how and why it is working that only you know
-* A complex algorithm/logic

-Make sure to add some comments or even an extended document. Avoid comments that explain trivial and obvious things
-like "enable feature X" before an if-block with a feature switch.
+In general, add comments where required to explain a certain piece of code. If is not
+self-explanatory about:

-Especially if it comes to reverse-engineering efforts, comments or even a separate document is crucial to allow others
-to understand the depths you dived into.
+- Why is it implemented like this
+- Very important details to understand how and why it is working that only you know
+- A complex algorithm/logic

-Any extended notes about documentation some hardware, protocol, reverse-engineering a feature etc. can be stored in
-the *doc/dev* folder and stay with the repository. Make good use of that!
+Make sure to add some comments or even an extended document. Avoid comments that explain trivial and
+obvious things like "enable feature X" before an if-block with a feature switch.
+
+Especially if it comes to reverse-engineering efforts, comments or even a separate document is
+crucial to allow others to understand the depths you dived into.
+
+Any extended notes about documentation some hardware, protocol, reverse-engineering a feature etc.
+can be stored in the *doc/dev* folder and stay with the repository. Make good use of that!

 #### Header files
-Document any enum, struct or function exposed by a header file. Documentation of static functions or variables in
-source modules is not required. Also provide documentation for the module.
+
+Document any enum, struct or function exposed by a header file. Documentation of static functions or
+variables in source modules is not required. Also provide documentation for the module.

 Example for my-namespace/my-module.h
+
 ```
 /**
 * Some example module to show you where documentation is expected.
@@ -323,22 +376,28 @@ int my_namespace_my_module_func(int a, int b);
 ```

 ### Naming conventions
-In general, try to keep names short but don't overdo it by using abbrevations of things you created. Sometimes this is
-not possible and we accept exceptions if there are no proper alternatives.
+
+In general, try to keep names short but don't overdo it by using abbrevations of things you created.
+Sometimes this is not possible and we accept exceptions if there are no proper alternatives.

 #### Namespacing
+
 The folder names use lower-case names with dashes *-* as seperators, e.g. *my-namespace*.

 #### Modules
-Header and source files of modules use lower-case names with dashes *-* as seperators, e.g. *my-module.c*, *my-module.h.

-The include guards contain the name of the namespace and module, see [here](#### Include guards).
+Header and source files of modules use lower-case names with dashes *-* as seperators, e.g.
+*my-module.c*, \*my-module.h.
+
+The include guards contain the name of the namespace and module, see \[here\](#### Include guards).

 Variables, functions, structs, enums and macros are namespace accordingly.

 #### Variables
-Snake-case with proper namespacing to namespace and module. Namespacing applies to static and global variables. Local
-variables are not namespaced.
+
+Snake-case with proper namespacing to namespace and module. Namespacing applies to static and global
+variables. Local variables are not namespaced.
+
 ```
 // For namespace "ezusb", module "device", static variable in module
 static HANDLE ezusb_device_handle;
@@ -348,7 +407,10 @@ int buffer_size = 256;
 ```

 #### Functions
-Snake-case with proper namespacing to namespace and module for all functions that are not hook functions.
+
+Snake-case with proper namespacing to namespace and module for all functions that are not hook
+functions.
+
 ```
 // For namespace "ezusb", module "device", static variable in module, init function
 void ezusb_device_init(...);
@@ -361,7 +423,9 @@ HANDLE my_CreateFileA(...)
 ```

 #### Structs
+
 Snake-case with proper namespacing to namespace and module.
+
 ```
 // For namespace "ezusb", module "device" ctx struct
 struct ezusb_device_ctx {
@@ -370,7 +434,9 @@ struct ezusb_device_ctx {
 ```

 #### Enums
+
 Snake-case with proper namespacing to namespace and module. Upper-case for enum entries
+
 ```
 // For namespace "ezusb", module "device" state enum
 struct EZUSB_DEVICE_STATE {
@@ -381,14 +447,18 @@ struct EZUSB_DEVICE_STATE {
 ```

 #### Macros
+
 Upper-case with underscore as spacing, proper namespacing to namespace and module.
+
 ```
 // For namespace "ezusb", module "device" vid
 #define EZUSB_DEVICE_VID 0xFFFF
 ```

 #### Multiple variable declarations
+
 Only one declaration per line which also avoids various errors, for example:
+
 ```
 // Nope
 char a, b, b;
@@ -402,25 +472,31 @@ char c;
 ```

 ### Testing
-We advice you to write unit tests for all modules that allow proper unit testing. This applies to modules that are not
-part of the actual hooking process and do not rely on external devices to be available. Add these tests to the
-*src/test* sub-folder.

-This does not only speed up your own development but hardens the code base and avoids having to test these things by
-running the real applications, hence saving a lot of time and trouble.
+We advice you to write unit tests for all modules that allow proper unit testing. This applies to
+modules that are not part of the actual hooking process and do not rely on external devices to be
+available. Add these tests to the *src/test* sub-folder.
+
+This does not only speed up your own development but hardens the code base and avoids having to test
+these things by running the real applications, hence saving a lot of time and trouble.

 ### Further best practices
-* Avoid external dependencies like additional libraries. Bemanitools is extremely self-contained which enables high
-portability and control which is important for implementing various "hacks" to just make things work.
-* If you see some module/function lacking documentation that you have to use/understand, add documentation once you
-figured out what the function/module is doing. This does not only help your future you but others reading the code.
-* Keep documentation and readme files up-to-date. When introducing changes/adding new features, review existing
-documentation and apply necessary changes.
+
+- Avoid external dependencies like additional libraries. Bemanitools is extremely self-contained
+  which enables high portability and control which is important for implementing various "hacks" to
+  just make things work.
+- If you see some module/function lacking documentation that you have to use/understand, add
+  documentation once you figured out what the function/module is doing. This does not only help your
+  future you but others reading the code.
+- Keep documentation and readme files up-to-date. When introducing changes/adding new features,
+  review existing documentation and apply necessary changes.

 ## Misc
-The core API interception code was ripped out, cleaned up a tiny bit and released on GitHub. BT5 will eventually be
-ported to use this external library in order to avoid maintaining the same code in two places at once.
+
+The core API interception code was ripped out, cleaned up a tiny bit and released on GitHub. BT5
+will eventually be ported to use this external library in order to avoid maintaining the same code
+in two places at once.

 https://github.com/decafcode/capnhook

-This too is a little rudimentary; it doesn't come with any examples or even a README yet. 
+This too is a little rudimentary; it doesn't come with any examples or even a README yet.
--- a/doc/game-error-codes.md
+++ b/doc/game-error-codes.md
@@ -27,9 +27,9 @@ N/A

 #### How to fix

-* Make sure your data is not set to read only, especially the dev folder.
-* Disable all network adapters other than the one used to connect to the Internet.
-* Check for hidden network adapters in Device Manager.
+- Make sure your data is not set to read only, especially the dev folder.
+- Disable all network adapters other than the one used to connect to the Internet.
+- Check for hidden network adapters in Device Manager.

 ## 5-1500 series errors

@@ -41,7 +41,7 @@ IO ERROR

 #### Known occurances

-* Pop'n Music 15
+- Pop'n Music 15

 #### How to fix

@@ -59,8 +59,8 @@ N/A

 #### How to fix

-* Check the integrity of the data you have, i.e. some files might be corrupted
-* Check your physical drive. Is it failing?
+- Check the integrity of the data you have, i.e. some files might be corrupted
+- Check your physical drive. Is it failing?

 ## 5-1501 series errors

@@ -76,9 +76,9 @@ N/A

 #### How to fix

-* Recopy Bemanitools.
-* For Reflec Beat, make sure you are not missing device.dll. (This seems to apply to some older
-version of bemanitools)
+- Recopy Bemanitools.
+- For Reflec Beat, make sure you are not missing device.dll. (This seems to apply to some older
+  version of bemanitools)

 ## 5-1502 series errors

@@ -90,13 +90,13 @@ BACKUP CHECK ERROR

 #### Known occurances

-* Pop'n'Music 21 Sunny Park
+- Pop'n'Music 21 Sunny Park

 #### How to fix

-* Give access to gamestart.bat and launcher.exe from Windows Firewall if enabled.
-* Make sure no antivirus software firewall is blocking access to those files.
-* Start gamestart.bat as Administrator.
+- Give access to gamestart.bat and launcher.exe from Windows Firewall if enabled.
+- Make sure no antivirus software firewall is blocking access to those files.
+- Start gamestart.bat as Administrator.

 ### 5-1502-0000

@@ -110,7 +110,7 @@ N/A

 #### How to fix

-* Make sure `/dev/` isn't read-only.
+- Make sure `/dev/` isn't read-only.

 ### 5-1502-0002

@@ -120,7 +120,7 @@ HDD READ ERROR

 #### Known occurances

-* GFDM V4
+- GFDM V4

 #### How to fix

@@ -132,7 +132,7 @@ Unknown

 #### Description

-USB I/O ERROR 
+USB I/O ERROR

 ##### FPGA WRITE ERROR

@@ -146,22 +146,22 @@ timeouts making this code prone to fail.

 #### Known occurances

-* IIDX
+- IIDX

 #### How to fix

 #### FPGA WRITE ERROR

-* Restart the game
-* Re-copy bemanitools
+- Restart the game
+- Re-copy bemanitools

 #### FW TRNS-OUT

-* Restart the game
-* Re-copy bemanitools
-* Running the process on high priority and with admin rights
-* If you attached a debugger, that might have messed with the timing and caused this. Try a
-different debugger or attach it later in the boot process
+- Restart the game
+- Re-copy bemanitools
+- Running the process on high priority and with admin rights
+- If you attached a debugger, that might have messed with the timing and caused this. Try a
+  different debugger or attach it later in the boot process

 ### 5-1503-0001

@@ -179,10 +179,10 @@ N/A

 #### How to fix

-* Check the integrity of the data you have, i.e. some files might be corrupted
-* If the data came in an archive format, try extracting it again with another application.
-* Make sure your game is up to date with the current data available.
-* Check your physical drive. Is it failing?
+- Check the integrity of the data you have, i.e. some files might be corrupted
+- If the data came in an archive format, try extracting it again with another application.
+- Make sure your game is up to date with the current data available.
+- Check your physical drive. Is it failing?

 ### 5-1503-0004

@@ -202,13 +202,13 @@ N/A

 Real hardware:

-* Check the USB cable between the PC and the IO board is okay.
-* Make sure the IO board is getting enough of a clean supply of power.
+- Check the USB cable between the PC and the IO board is okay.
+- Make sure the IO board is getting enough of a clean supply of power.

 Bemanitools:

-* Don't attempt to put your computer to sleep while playing rhythm games.
-* Change launcher.exe process priority to High when starting the game.
+- Don't attempt to put your computer to sleep while playing rhythm games.
+- Change launcher.exe process priority to High when starting the game.

 ### 5-1503-0006

@@ -222,7 +222,7 @@ N/A

 #### How do I fix it?

-* Recopy Bemanitools.
+- Recopy Bemanitools.

 ### 5-1503-0007

@@ -236,7 +236,7 @@ N/A

 #### How do I fix it?

-* Run the game using gamestart.bat, don't just drag and drop the game dll onto launcher.exe
+- Run the game using gamestart.bat, don't just drag and drop the game dll onto launcher.exe

 ### 5-1503-0008

@@ -246,7 +246,7 @@ FPGA Write error

 #### Known occurances

-* IIDX Tricoro
+- IIDX Tricoro

 Seen in Tricoro Omnimix RC1.

@@ -266,7 +266,7 @@ N/A

 #### How do I fix it?

-* Make sure your AC(real)IO board is on the correct COM port.
+- Make sure your AC(real)IO board is on the correct COM port.

 ## 5-1504 series errors

@@ -286,8 +286,8 @@ N/A

 Real hardware:

-* Make sure your readers are connected and powered on.
-* Check your serial cables are good.
+- Make sure your readers are connected and powered on.
+- Check your serial cables are good.

 ### 5-1504-0003

@@ -330,13 +330,13 @@ the game may take 1-3 minutes longer to boot as it regenerates backup data.

 #### Known occurances

-* Jubeat Ripples
+- Jubeat Ripples

 #### How do I fix it?

-* Check the integrity of the data you have, i.e. some files might be corrupted
-* If the data came in an archive format, try extracting it again with another application.
-* Check your physical drive. Is it failing?
+- Check the integrity of the data you have, i.e. some files might be corrupted
+- If the data came in an archive format, try extracting it again with another application.
+- Check your physical drive. Is it failing?

 ### 5-1505-0001

@@ -350,9 +350,9 @@ N/A

 #### How do I fix it?

-* Check the integrity of the data you have, i.e. some files might be corrupted
-* If the data came in an archive format, try extracting it again with another application.
-* Check your physical drive. Is it failing?
+- Check the integrity of the data you have, i.e. some files might be corrupted
+- If the data came in an archive format, try extracting it again with another application.
+- Check your physical drive. Is it failing?

 ### 5-1505-0002

@@ -371,9 +371,9 @@ N/A

 ##### Real hardware

-* There may be a coin stuck, check.
-* The coin mechanism may be stuck, check.
-* Don't hold down the coin line so long.
+- There may be a coin stuck, check.
+- The coin mechanism may be stuck, check.
+- Don't hold down the coin line so long.

 ### 5-1505-0006

@@ -387,9 +387,9 @@ N/A

 #### How do I fix it?

-* Check the integrity of the data you have, i.e. some files might be corrupted
-* If the data came in an archive format, try extracting it again with another application.
-* Check your physical drive. Is it failing?
+- Check the integrity of the data you have, i.e. some files might be corrupted
+- If the data came in an archive format, try extracting it again with another application.
+- Check your physical drive. Is it failing?

 ### 5-1505-0025

@@ -399,11 +399,11 @@ N/A

 #### Known occurances

-* Jubeat Saucer Fullfill
+- Jubeat Saucer Fullfill

 #### How do I fix it?

-* Disable excess network adapters
+- Disable excess network adapters

 ## 5-1506 series errors

@@ -419,7 +419,7 @@ The backup data is corrupted. Press the test button to re-initialize it.

 #### Known occurances

-* IIDX 15 (BACKUP DATA ERROR)
+- IIDX 15 (BACKUP DATA ERROR)

 #### How do I fix it?

@@ -442,7 +442,7 @@ This error may happen before the monitor check on IIDX.

 #### Known occurances

-* IIDX (version?)
+- IIDX (version?)

 #### How do I fix it?

@@ -460,8 +460,8 @@ N/A

 #### How do I fix it?

-* "Set" and save the clock date and time in the test menu
-* Recopy Bemanitools
+- "Set" and save the clock date and time in the test menu
+- Recopy Bemanitools

 ## 5-1507 series errors

@@ -509,7 +509,7 @@ LAMP CHECK ERROR

 #### Known occurances

-* Pop'n Music 20 Fantasia
+- Pop'n Music 20 Fantasia

 #### How do I fix it?

@@ -527,7 +527,7 @@ The original message in Japanese: 電源を再投入して下さい

 #### Known occurances

-* Pop'n Music 22 Lapistoria
+- Pop'n Music 22 Lapistoria

 #### How do I fix it?

@@ -551,12 +551,12 @@ N/A

 #### How do I fix it?

-* Restart your game.
-* Check if your computer is connected to the Internet at all.
-* Make sure the services URL is correct.
-* Disable all network adapters other than the one used to connect to the Internet. Alternatively,
-setting that adapter to have the highest affinity also works.
-* If none of the above work, reinstall a newer or older version of your network drivers.
+- Restart your game.
+- Check if your computer is connected to the Internet at all.
+- Make sure the services URL is correct.
+- Disable all network adapters other than the one used to connect to the Internet. Alternatively,
+  setting that adapter to have the highest affinity also works.
+- If none of the above work, reinstall a newer or older version of your network drivers.

 ### 5-2002-0000

@@ -570,7 +570,7 @@ N/A

 #### How do I fix it?

-* Make sure you're editing the right file for network configuration settings.
+- Make sure you're editing the right file for network configuration settings.

 ### 5-2002-0916

@@ -602,18 +602,18 @@ Press the service button to start the game.

 #### Known occurances

-* IIDX, probably all known versions
+- IIDX, probably all known versions

 #### How do I fix it?

 The original message is already telling you what is going on:

-* Check if your machine/pc has an internet connection
-* Check your firewall settings
-* Check that the server address is configured and correct in `iidxhook.conf` (old games) or
-`ea3-config.xml`
-* You can disable the network in the operator menu to just boot the game first. Note that this is
-not possible on any versions starting IIDX 20 (tricoro).
+- Check if your machine/pc has an internet connection
+- Check your firewall settings
+- Check that the server address is configured and correct in `iidxhook.conf` (old games) or
+  `ea3-config.xml`
+- You can disable the network in the operator menu to just boot the game first. Note that this is
+  not possible on any versions starting IIDX 20 (tricoro).

 ### 5-2002-2301

@@ -669,7 +669,7 @@ N/A

 #### How do I fix it?

-* Check that there is a valid PCBID in ea3-config.xml.
+- Check that there is a valid PCBID in ea3-config.xml.

 ### 5-2002-2400

@@ -698,19 +698,19 @@ N/A

 #### How do I fix it?

-* Check your services URL in `ea3-config.xml`. Make sure to remove any slash at the end of the URL
-and check for https/http.
-* If you are running Spada, ensure to use a service URL that supports that older game (check with
-your private server provider)
-* If you are running Tune Street, ensure to use a service URL that supports that older game (check
-with your private server provider)
+- Check your services URL in `ea3-config.xml`. Make sure to remove any slash at the end of the URL
+  and check for https/http.
+- If you are running Spada, ensure to use a service URL that supports that older game (check with
+  your private server provider)
+- If you are running Tune Street, ensure to use a service URL that supports that older game (check
+  with your private server provider)

 ### 5-2003-2404

 #### Description

-Malformed `<network>` section.  The `<network>` section in your `ea3-config.xml` file is malformed
-in some way.
+Malformed `<network>` section. The `<network>` section in your `ea3-config.xml` file is malformed in
+some way.

 #### Known occurances

@@ -758,15 +758,15 @@ N/A

 #### How do I fix it?

-Check if your `hosts` file has any DNS redirects to other private servers that might interfere
-with this
+Check if your `hosts` file has any DNS redirects to other private servers that might interfere with
+this

 ### 5-2016-0000

 #### Description

-"apsmanager" is a special eAM Participation system for Korean machines(XXX:K). This system
-is maybe not supported by private servers.
+"apsmanager" is a special eAM Participation system for Korean machines(XXX:K). This system is maybe
+not supported by private servers.

 #### Known occurances

--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
icex2	c369412f70	fix(mingw): Version upgrade caused this to error HRESULT not defined fixed by including windows header	2024-02-25 09:30:53 +01:00
icex2	26d1da8660	refactor(dist): Config and .bat files Move everything to new launcher.xml configuration files. Adjust the bootstrapping of launcher in the .bat files. Features such as copying the default props/ files to nvram are now handled by launcher. Using the PATH variable, bemanitools binaries can live in their own dedicated bemanitools/ subfolder next to props/ and modules/ now. All original binaries are expected to be kept in a modules/ folder like on stock data.	2024-02-25 09:30:53 +01:00
icex2	04310f49fd	refactor(launcher): Major re-work of launcher Kudos to Shiz for providing the groundwork for this. Fundamentally re-think how launcher operates and bootstrapping the games is managed and configured. This brings it significantly closer to how the original bootstrap is doing the job: launcher now utilizes the data (structures) provided by the bootstrap.xml configuration file. This creates compatibility with vanilla data dumps and original stock images. Note that bemanitools does not include any code or means to run DRM'd data, only decrypted. But, this allows users to keep decrypted dumps as stock as possible which means: * No copying around of property files anymore * Keep the modules/ folder with the binaries * Have bemanitools binaries separate in the data * No need to edit/customize the original configuration files A list of key features of the "new" launcher: * Boostrap games by following the configuration provided by stock game's bootstrap.xml files * Custom launcher.xml configuration file that adds further launcher configurable features, composability of bootstrap.xml configuration(s) as well as configuration overriding/stacking of selected types of configurations, e.g. eamuse config, avs-config. The latter eliminates the need for modifying stock config files in the prop/ folder * Unified logging system: launcher and AVS logging uses the same logger, all output can now be in a single file * Original features such as various hook types still available Due to the significant architectural changes, this also breaks with any backwards compatibility to existing launcher setups. Thus, users need to migrate by re-applying the new configuration format and migrating their config parameters accordingly. Further migration instructions and updated documentation will be provided upon release. Co-authored-by: Shiz <hi@shiz.me>	2024-02-25 09:30:53 +01:00
icex2	d72996c5d9	refactor(inject): Use new core thread and log modules Keep this a separate commit because this also removes inject's own logging engine and replaces it with the streamlined core API. The core API provides all the features of inject's own logging engine which also performed horribly. The entire logging operation was locked which included expensive operations that formatted the log messages and required memory allocations and copying around data. The core API's implementation at least only synchronizes the actual IO operations (though this can be improved further with an actual async logging sink, TBD)	2024-02-25 09:30:53 +01:00
icex2	5ac858e15d	chore: Delete old log and thread modules in util The log API stopped scaling already a while ago and needs considerable refactoring to consider the various use-cases that emerged since it was first created on alpha versions of bemanitools.	2024-02-25 09:30:53 +01:00
icex2	e4a221e15b	refactor: Entire code base, thread and log usage Boils down to: - Include headers - Reduce boiler plate with helpers - Swap out explicit usages with core API layer and ensure the right API is configured beforehand	2024-02-25 09:30:53 +01:00
icex2	ea835b32ee	refactor(api): Thread and log API Split files and add name spacing.	2024-02-25 09:30:53 +01:00
icex2	fb1442b734	feat: Add helper to set avs implementations Doesn't really reduce boiler plate but adds clarity with a more meaningful function name what the operation does.	2024-02-25 09:30:53 +01:00
icex2	87b7e53973	feat: Add core module This module contains the "core" (API) of bemanitools which includes an abstraction layer for threads and logging at this time. The threads API is very close to what util/thread already was with some structural enhancements which make it easier to understand and work with the API, I hope. Some additional helpers (-ext module) support in doing common tasks, e.g. setting up the thread API with other modules. The log(ging) part receives a major overhaul to address known limitations and issues with the util/log module: - Cleaner API layer - Separate sinks from actual logging engine - Sinks are composable - Improved and cleaner compatibility layer with AVS logging API Additional "extensions" (-ext modules) add various helper functions for common tasks like setting up the logging engine with a file and stdout sink. The sinks also improved significantly with the file sink now supporting proper appending and log rotation. Logging to stdout/stderr supports coloring of log messages which works across logging engines. Overall, this refactored foundation is expected to support future developments and removes known limitations at the current scale of bemanitools such as: - Reducing boiler plate code across hooks - Interop of bemanitools and AVS (and setting the foundation for addressing currently missing interop, e.g. for dealing with property structures without AVS) - Addressing performance issues in the logging engine due to incorrect interop with AVS	2024-02-25 09:30:53 +01:00
icex2	2e45f095ba	feat(avs-util): Add helper to translate property errors	2024-02-25 09:30:53 +01:00
icex2	e12cd63ba2	Fix(avs): Incorrect function signature After getting doubts, I looked this one up again on the assembly. The decompiled output confused me and no actual value is being returned there.	2024-02-25 09:30:47 +01:00
icex2	8804e667b3	feat(avs): Add property get and clear error functions Use these to improve error handling by allowing one to provide additional error information on property related operations.	2024-02-25 09:14:42 +01:00
icex2	f5b8af3f2a	feat(dev): Add a separate docker dev container Improve the development experience by providing an additional docker container that can be started and used as an interactive development environment. It provides all the tools and a stable environment for building (identical to the build container).	2024-02-25 09:14:42 +01:00
icex2	ab6c3fc8bc	fix(hook): Add missing hook_table_revert impl Allow hooks to cleanup when they are shut down.	2024-02-25 09:07:54 +01:00
icex2	7a56fab96e	fix(dist): Incorrect versioning for ddr distribution packages Apparently forgotten to get updated to reflect the currently supported versions correctly.	2024-02-25 08:51:25 +01:00
icex2	ce1a004bf6	fix(ddr): Add missing distribution files for 17 and 18 Even they are identical to 16, stick to the current scheme of copy-pasting them.	2024-02-03 10:29:10 +01:00
icex2	e72e38eda2	chore: Fix ordering of files in module.mk	2024-02-03 10:28:42 +01:00
icex2	e71373e718	fix(doc): Update list of supported ddr versions Apparently also forgotten to reflect currently supported games.	2024-01-31 22:47:14 +01:00
icex2	44cd2ba098	fix(dist): Incorrect versioning for ddr distribution packages Apparently forgotten to get updated to reflect the currently supported versions correctly.	2024-01-31 22:47:14 +01:00
icex2	f17a2d2044	feat/fix(avs/ddr): Support AVS 2.13.06 This one was missing and is the actual correct version used for ddr-13. 2.13.04 was compatible, thus far, but there isn't any guarantee that they are actually 100% compatible (only konmai knows...).	2024-01-31 22:47:14 +01:00
icex2	42f09417a0	feat(avs imports): Add lib export definitions of new AVS API functions Add all functions and their respective ordinals (and mangled names for documentation purpose) to all currently used AVS version.	2024-01-31 22:47:14 +01:00
icex2	dc16844bbb	feat(avs-api): Various improvements * Improve psmap types, taken from a private eamuse server backend which had more complete mappings. * Move psmap terminator to enum * AVS error type: Supports improving expressiveness of the API interface * Add more property node related functions Add more AVS file system related functions These were previously missing and are required for various file system related tasks such as iterating directory trees, reading and writing files through the AVS file system for the upcoming launcher rework. Note that the AVS API broke with some mode flags after version 2.13.06.	2024-01-31 22:47:14 +01:00
icex2	4fedf34d6b	feat: Add new module to scope avs related "utility" stuff Use this to share helpers or other extensions to the original avs API across modules. Start with including error codes to readable strings to improve velocity on AVS API error analysis.	2024-01-31 22:47:14 +01:00
icex2	06317d63e7	feat(util): Add func to check if running as admin user This has been a source of common error in the past. It is known that most, or even all, games run into various issues when not run with elevated privileges.	2024-01-31 22:47:14 +01:00
icex2	e2a6410461	chore: Apply code formatting	2024-01-31 22:47:14 +01:00
icex2	0a29e031ff	chore: Apply formatting to all markdown docs	2024-01-31 22:20:51 +01:00
icex2	0897a25174	feat(dev): Add markdown document formatting Apply a consistent style across all markdown documents. Use mdformat (https://github.com/executablebooks/mdformat) to achieve that. Improves maintainability and readability.	2024-01-31 22:20:51 +01:00
icex2	6efbf71c30	chore: Bump version to 5.49 to start next development cycle	2024-01-31 22:19:32 +01:00
icex2	e1008576ce	chore: Update changelog for release	2024-01-31 21:52:05 +01:00
icex2	f41cdba8b8	chore: Bump version to 5.48 to start next development cycle	2024-01-31 21:42:14 +01:00
ahnada	1379c1e11b	New filename (without version string) for the new save files	2024-01-31 21:40:22 +01:00
ahnada	d1525a98dd	Mapper serialization versioning Add a "BTMD" FOURCC + version in the beginning of the mapper data file. Is backwards compatible with the current data format.	2024-01-31 21:40:22 +01:00
ahnada	329d6a80a3	Properly save/load the new analog invert option	2024-01-31 21:40:22 +01:00
ahnada	f37f216c69	Add invert analog input option	2024-01-31 21:40:22 +01:00
icex2	bdf493d2fb	chore: Update changelog for 5.47 release	2024-01-29 22:08:28 +01:00
icex2	bec007d52a	fix(p3ioemu): Incorrect dispatching of unknown p3io commands Using ddrhook1, this caused DDR X to crash on startup when the P3io client sends the currently unknown command 2B. Handling it with the incorrect p3io command struct, any following reading attempts from the P3IO by the game fail. Handle the 2B case explicitly with a generic response that worked previously before the restructuring of the code. Apply the same to any further unknown commands with improved logging warning about this.	2023-11-30 20:33:36 +01:00
icex2	a177913bd6	fix(p3io): Off-by-one error on assert Buffers are allowed to have the exact size as the max defined P3IO buffer size. Cutting it short by one byte causes this to fail incorrectly when using the pure raw buffer structure	2023-11-30 20:33:36 +01:00
ahnada	0fdde8b32d	Allow generic HID devices with broken(?) outputs to still work as inputs. Fixes Sony DualShock 4 not working	2023-11-13 21:35:28 +01:00
ahnada	09b3a6c24a	Fix incorrect SetupDiGetClassDevs error checking	2023-11-13 19:37:29 +01:00
icex2	f8b2f5f40d	chore: Bump version to 5.47 to start next development cycle	2023-11-03 15:48:04 +01:00