Differences

This shows you the differences between two versions of the page.

--- base:tools_for_putting_files_into_a_.d64_image [2017-03-14 15:11] – Add section about mkd64, which has many more features than the other tools. zirias
+++ base:tools_for_putting_files_into_a_.d64_image [2024-03-15 19:52] (current) – [cc1541] ftc
@@ Line 49: / Line 49: @@
 ====== cc1541 ======
-c1541 works fine for most purposes, but some of the better coders around says it is buggy, and thus there is also [[http://noname.c64.org/csdb/release/?id=69964|cc1541]]. cc1541 also supports some more advanced options which gives you better control over how the files are actually laid out onto the image. The available options goes like this:
+c1541 works fine for most purposes, but some of the better coders around says it is buggy, and thus there is also [[https://csdb.dk/search/?seinsel=all&search=cc1541&Go.x=0&Go.y=0|cc1541]]. The tool is actively maintained, provides many options to control the file layout on the disk, and is currently the only tool to create disk images for Krill's incredibly fast [[https://csdb.dk/release/?id=214786|Transwarp loader]].
-<code>
-Usage: cc1541 -niSsfw image.d64
--n diskname   Disk name, default='default'
--i id         Disk ID, default='lodis'
--S value      Default sector interleave, default=10
--s value      Next file sector interleave, after each file
-              the interleave value falls back to the default value set by -S
--f filename   Use filename as name when writing next file
--w localname  Write local file to disk, if filename is not set then the
-              local name is used. After file written filename is unset
--x            Don't split files over track 18 hole (default split files)
--t            Use track 18 to also store files (makes -x useless) (default no)
--4            Use tracks 35-40 with SPEED DOS formatting
--5            Use tracks 35-40 with DOLPHIN DOS formatting
-</code>
 ====== mkd64 ======
-When the flexibility of cc1541 still isn't enough, there's [[http://zirias.github.io/c64_tool_mkd64/|mkd64]] which takes a modular approach to creating the disk files, so you don't have to follow the default 1541 format at all. In fact, creation of a directory and block allocation map ist taken care of by a loadable module named "cbmdos". It also includes all sorts of tricks and tweaks possible with the 1541 format as well as a module providing some pre-made "separator" directory entries using graphical characters. The help pages for mkd64 itself and the cbmdos module look like this:
+Another flexible alternative is [[http://zirias.github.io/c64_tool_mkd64/|mkd64]] which takes a modular approach to creating the disk files, so you don't have to follow the default 1541 format at all. In fact, creation of a directory and block allocation map ist taken care of by a loadable module named "cbmdos". It also includes all sorts of tricks and tweaks possible with the 1541 format as well as a module providing some pre-made "separator" directory entries using graphical characters. The help pages for mkd64 itself and the cbmdos module look like this:
 <code>
-mkd64 1.3b help
+mkd64 1.4b help
 mkd64 supports four types of options. Single options trigger some immediate
@@ Line 137: / Line 120: @@
 </code>
 <code>
-mkd64 1.3b help
+mkd64 1.4b help
 * Module `cbmdos':
@@ Line 173: / Line 156: @@
 Example usage from an own project:
 <code>
-	mkd64 -mcbmdos -mseparators -odisks/demo.d64 \
+	mkd64 -odisks/demo.d64 \
-	  -d'C=64 WORKBENCH' -i'AMIGA' -R1 -Da0 -0 \
+          -mcbmdos -d'C=64 WORKBENCH' -i'AMIGA' -R1 -Da0 -0 \
-	  -fdemo_bootloader                    -proundtop        -S1      -w \
+          -mseparators \
+          -fdemo_bootloader                    -proundtop        -S1      -w \
 	  -fdemo_kickstart  -n'DEMO: AMIGADOS' -pfr -t19 -s0 -TU -S0 -i15 -w \
 	  -fdemo_amigados                      -pfrmid       -TU -S0 -i15 -w \