====== How to make multi-game disks ======

Vinny Mainolfi provided this info on the fb group page regarding how to make your own multi-game disks:

--------------------

__From Vinny__:

**__Making your own C64Mini Multi Disks__**:

  * Download **FIBR** from http://csdb.dk/release/?id=162390
    * (this is the small menu file that needs to go at the start of every disk you build)
  * Download **DIRMASTER** from http://csdb.dk/release/?id=148169
  * Install and run on your PC
  * Select: **Disk** / **New** / **D81 * **
  * Drag **FIBR.PRG** that you downloaded above, into the disk you have just started, so that it's ALWAYS the first file on your disk.
  * Grab some **.PRG** game files from the Net and drag them into your newly created disk
  * Save the disk on you DESKTOP
  * Go to desktop and change file extension from .D81 to **.D64**
  * Rename file to **THEC64-drive8.D64**
  * Put file on USB Stick
  * Plug into C64Mini
  * Turn on C64Mini and load **AlleyKat**
    * __GI NOTE__: Not all games in the carousel activate the fastloader+d81/d82 support (read more about it [[fastloader_d82_image_support|here]])
    * So to play it safe, select either **Alleykat** or **Avenger**.
  * Press **MENU** button on joystick
  * Open **BASIC**
  * Type: **LOAD"*",8,1** and press **ENTER** / **RETURN** button
  * Type: **RUN** and press **ENTER** / **RETURN** button
  * Use joystick to select a game and press **FIRE** to load

** * ** image could be .d64, .d71, .d80, .d81, d82 - nevertheless it has to be renamed to .d64 (THEC64-drive8.D64).\\ .d80 and .d82 are of greatest size (0,5 and 1MB), but it could lead to some compatibility problems (e.g. if needed to save to disk), so it is recommended to use .d81 instead (it is 0,8MB).\\
It is not problem of TheC64 Mini but it is same at C64 and emulators - .d80 and .d82 are disk-images of quite different disk drives then others "regular" units. 
===== Paul Smallman's walkthrough video =====

Paul provided a walkthrough video on how to create multi-game disks. More info here:

  * https://www.facebook.com/groups/209280506324242/permalink/241797509739208/
  * https://www.youtube.com/watch?v=7N1HKLMnMEk

===== Using NAV =====

Darko mentioned further details on NAV. I haven't had a chance to give it a try, but will share his details here:

> after this procedure, done once, user does not have to use keyboard anymore to load games/disk content. Everything is driven from joystick/mouse and very nice gui. You don't need a Fibr anymore (but it won't hurt - it is compatible afaik).
> There are "secret options" also, some very advanced and useful (for most users is enough to know that they could change bkg pattern with "@£" ; "@help" for help).
> Link is
> [[http://is.gd/nav96]]
> This is Alan Reed aka HowlinAl aka Redjac official page.

===== Using Auto-Menu =====

D. Judland aka iadoremy64 made detailed [[https://istilladoremy64.chorusgrove.com/doku.php?id=blog:2018-10-23|The How-To]] for Auto-Menu at his blog.\\
Auto-Menu is simple utility  by Shawn Ort, published in issue #45 of Loadstar.


===== Multi-game menu tools =====

A few people have made mention of the multi-game menu system tools they use to prepare such disks. I've compiled a list of the ones mentioned so far:

  * [[http://csdb.dk/release/?id=162390|FIBR]]
  * [[https://csdb.dk/release/?id=19120|Turbo Menu Maker]]
  * [[https://csdb.dk/release/?id=115764|NAV]]
  * [[https://istilladoremy64.chorusgrove.com/lib/exe/fetch.php?media=media:d64:automenu.d64|Auto-Menu]]

List of numerous disk-menu tools:

  * [[http://commodore.software/index.php?option=com_jdownloads&view=category&catid=29&Itemid=126|Disk Menus]]  at commodore.software