User Tools

Site Tools


base:tools_for_putting_files_into_a_.d64_image

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
base:tools_for_putting_files_into_a_.d64_image [2017-03-14 15:19]
zirias [mkd64] fix example for v1.4
base:tools_for_putting_files_into_a_.d64_image [2020-10-08 11:47] (current)
claus [cc1541]
Line 49: Line 49:
 ====== cc1541 ====== ====== 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/release/?id=196448|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 go like this:
  
 <code> <code>
-Usage: cc1541 -niSsfw image.d64+*** This is cc1541 version 3.2 built on Oct  8 2020 ***
  
--n diskname   Disk name, default='default+Usage: cc1541 -niwfoVTPONlBMmdtuxFSseErbc45gqvh image.[d64|d71|d81] 
--i id         Disk ID, default='lodis' + 
--S value      Default sector interleave, default=10 +-n diskname   Disk name, default='cc1541'. 
--s value      Next file sector interleave, after each file +-i id         Disk ID, default='00 2a'.
-              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 -w localname  Write local file to disk, if filename is not set then the
-              local name is used. After file written filename is unset +              local name is used. After file written, the filename is unset. 
--           Don't split files over track 18 hole (default split files+-f filename   Use filename as name when writing next file, use prefix # to 
--t            Use track 18 to also store files (makes -x useless) (default no) +              include arbitrary PETSCII characters (e.g. -f "START#a0,8,1"). 
--4            Use tracks 35-40 with SPEED DOS formatting +-o            Do not overwrite if file with same name exists already. 
--5            Use tracks 35-40 with DOLPHIN DOS formatting+-V            Do not modify image unless it is in valid CBM DOS format. 
 +-T filetype   Filetype for next file, allowed parameters are PRG, SEQ, USR, REL 
 +              and DEL. For DEL, the input file is ignored. Default is PRG. 
 +-P            Set write protect flag for next file. 
 +-O            Set open flag for next file. 
 +-N            Force creation of a new directory entry, even if a file with the 
 +              same name exists already. 
 +-l filename   Write loop file (an additional dir entry) to existing file to 
 +              disk, set filename with -f. 
 +-B numblocks  Write the given value as file size in blocks to the directory for 
 +              the next file. 
 +-M numchars   Hash computation maximum filename length, this must 
 +              match loader option FILENAME_MAXLENGTH in Krill's Loader. 
 +              Default is 16. 
 +-m            Ignore filename hash collisions, without this switch a collision 
 +              results in an error. 
 +-d track      Maintain a shadow directory (copy of the actual directory without 
 +              a valid BAM). 
 +-t            Use dirtrack to also store files (makes -x useless) (default no)
 +-u numblocks  When using -t, amount of dir blocks to leave free (default=2). 
 +-x            Don't split files over dirtrack hole (default split files). 
 +-F            Next file first sector on a new track (default=0). 
 +              Any negative value assumes aligned tracks and uses current 
 +              sector + interleave. After each file, the value falls back to the 
 +              default. Not applicable for D81. 
 +-S value      Default sector interleave, default=10. 
 +              At track end, reduces this by 1 to accomodate large tail gap. 
 +              If negative, no special treatment of tail gap.  Not applicable for 
 +              D81. 
 +-s value      Next file sector interleave, valid after each file. 
 +              At track end, reduces this by 1 to accomodate large tail gap. 
 +              If negative, no special treatment of tail gap. 
 +              The interleave value falls back to the default value set by -S 
 +              after the first sector of the next file. Not applicable for D81. 
 +-e            Start next file on an empty track (default start sector is 
 +              current sector plus interleave). 
 +-E            Try to fit file on a single track. 
 +-r track      Restrict next file blocks to the specified track or higher. 
 +-b sector     Set next file beginning sector to the specified value. 
 +              Not applicable for D81. 
 +-c            Save next file cluster-optimized (d71 only). 
 +-4            Use tracks 35-40 with SPEED DOS BAM formatting. 
 +-5            Use tracks 35-40 with DOLPHIN DOS BAM formatting
 +-g filename   Write additional g64 output file with given name. 
 +-q            Be quiet. 
 +-v            Be verbose. 
 +-h            Print this commandline help.
 </code> </code>
- 
 ====== mkd64 ====== ====== mkd64 ======
  
-When the flexibility of cc1541 still isn't enough, there'[[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> <code>
base/tools_for_putting_files_into_a_.d64_image.1489501169.txt.gz · Last modified: 2017-03-14 15:19 by zirias