Disk \ ADF Compare

[BarryB]

Originally Posted by Radertified

I haven't tested it so maybe it already does this, but knowing what files are on the different tracks would be nice, assuming it's a DOS readable ADF.

It doesn't currently, but can you give an example of why that would be needed?

[Exodous]

This tool does nothing with the filesystem and it doesn't care about filesystems.

Unfortunately, writing an OFS/FFS aware filesystem parser is certainly more than can be knocked up in the couple of hours I've spent on this tool.

I do have a separate tool I've been working on since 2019 that does that (it dumps the block numbers as part of it's debugging routines), but it's very much at the command line dumping and debugging stage and far from even a beta release.

[Radertified]

Originally Posted by BarryB

It doesn't currently, but can you give an example of why that would be needed?

If I had 2 disks:

x.adf
x [a].adf

I compare them and it shows track 42 side 1 is different. I then check to see what's there and see a .info file has changed.

That's the only difference between the 2 disks so there's probably no point in keeping the [a] disk.

It would be for collections more than anything else.

Originally Posted by Exodous

This tool does nothing with the filesystem and it doesn't care about filesystems.

Unfortunately, writing an OFS/FFS aware filesystem parser is certainly more than can be knocked up in the couple of hours I've spent on this tool.

I do have a separate tool I've been working on since 2019 that does that (it dumps the block numbers as part of it's debugging routines), but it's very much at the command line dumping and debugging stage and far from even a beta release.

All good. I wasn't asking for it. I was just suggesting that there's always more that can be done

[twitek]

Originally Posted by Radertified

I compare them and it shows track 42 side 1 is different. I then check to see what's there and see a .info file has changed.

I use ADFren for that. But it's not comparing tracks, but files directly.


So for example let's say i have three versions of a disk. With ADFren i could see:
- disk 1 has an extra file called file_bbs.txt
- the readme.txt has a different CRC on all disks
- the other files are identical

[Radertified]

I also use ADFren for that. I asked about it loooong ago: http://eab.abime.net/showthread.php?p=770737

[BarryB]

Originally Posted by Radertified

If I had 2 disks:

x.adf
x [a].adf

I compare them and it shows track 42 side 1 is different. I then check to see what's there and see a .info file has changed.

That's the only difference between the 2 disks so there's probably no point in keeping the [a] disk.

It would be for collections more than anything else.

All good. I wasn't asking for it. I was just suggesting that there's always more that can be done

OK, I see your point, but as Exodus says this program only deals with ADF's at the track/block level.

[demoniac]

Originally Posted by Radertified

That's the only difference between the 2 disks so there's probably no point in keeping the [a] disk.

Unless x.adf was the modified disk and x [a].adf is the original.