| |
oziphantom
Registered: Oct 2014
Posts: 490 |
Disk Drive Tool
Are there any cmd line ( on windows ) tools that enable you to put data into sectors, or write files starting at a Track:Sector. OR a way to do it in c1541?
Ability to change the optimal interleave per file would be an added bonus. |
|
| |
tlr
Registered: Sep 2003
Posts: 1790 |
Maybe this: cc1541? |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
The python script I use to generate .d64s for my releases has those abilities internally, though they're not exposed as commandline parameters at the moment. It also starts with a blank .d64 rather than parsing an existing one.
I could clean it up a bit if nothing else is proposed, or you can grab the script as is if you're happy to make the changes yourself.
edit - tlr responded while I was writing my comment; but offer still stands of course :) |
| |
oziphantom
Registered: Oct 2014
Posts: 490 |
cc1541 has interleave but no write sector ability.
ChristopherJam - blank d64 is fine ;) |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
OK, I'll put a release together - probably tomorrow.
I'm guessing there may be more than one file with a requested starting track,sector? |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
Quote: cc1541 has interleave but no write sector ability.
ChristopherJam - blank d64 is fine ;)
As author of cc1541 I've never even considered that use case. :) Why do you need it? I'm curious!!
Also, the source code is available, it would be trivial to use it.
Nowadays I use the internal Booze-tools which has another disk-utility that's more tightly bundled with ByteBoozer and the Booze-loader. That tool doesn't have the functions you request either. |
| |
oziphantom
Registered: Oct 2014
Posts: 490 |
1571/1581 128 Boot Sectors. They must start at Track 1 Sector 0 for the 128, the 1571/1581 USR autoload files also have a set position. All the "sectors" used above must not have the PRG load address so are full 256 byte sectors.
Also I'm making the disks dual System, so there is a C64 version and a C128 version on the disk. The C64 version is Krill loaded and should have the standard interleave, but the 1571 does better with a 6 interleave ( I think it is six, need to look it back up). The C128 just gives a much better loading experience, and if I can patch the game to work on the 128 its just better.
I've been trying to get things compiling, Exomizer has a couple of changes I would like to make, but they are GCC, and I've tried getting them to cross-compile on my Linux VM but they don't. Sometimes I can get them to work on VS ( tass64 for example is now VS2015 compatible ) but when they use the "normal" getOpts its a sign they need the whole thing. Or in case of Exomizer Bison etc |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
Quoting JackAsserAs author of cc1541 I've never even considered that use case. :) Why do you need it? I'm curious!!
I've started placing the drive code for loaders into hardcoded block locations, then performing block-reads to load them into drive buffers. |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
Release done.
BakeDisk64 |
