| |
ΛΛdZ
Registered: Jul 2005
Posts: 153 |
Data in track 35+
How to detect data in track 35+ ?
Does there exist any tool to "detect" if a disk contains
data in track 35+ ?
I tried monitor cmd @RB 26 01 10 but that did not
start at all, so I guess that it checks if the
value is above 35 :/
What to do :=? |
|
| |
Krill
Registered: Apr 2002
Posts: 2969 |
Try these tools:
Maverick 5.04
Disk Demon
These were my favourite disk-mangling tools, next to AR mon, of course.
Maverick is a really sophisticed thing. I first knew it under the name Renegade, but haven't found that version on CSDB. Does anybody know any background on those two names of essentially the same tool? |
| |
AlexC
Registered: Jan 2008
Posts: 298 |
On PC side both 64copy and StarCommander can recognize 40 tracks. 64copy let's know when opening d64 file that its using tracks above standard DOS limit.
If you are talking about original disks the only good way sometimes is to analyse loader. |
| |
Mason
Registered: Dec 2001
Posts: 461 |
Well I can take part in this thread too. Its because Mdz and me talked about how to recognize if theres a demo, crack or so that needs more than 35 tracks - Tangled Tales is a good example.
|
| |
ΛΛdZ
Registered: Jul 2005
Posts: 153 |
Krill:> I located the Renegade Nybbler and added it:
Renegade Dual Nybbler
My question on 35+ tracks is due to the amount of disks that
are transfered my Grahams warpcopy which only does 35 tracks.
So what I want is to know if there is a way to identify
disks (by means of thousands d64 files) that should have
been transfered with more tracks (using StarCMD etc.).
Right now I have made a script that checks ALL sectors to
see if there is any references to tracks 36-40. But that is
ofcos not always "correct" - but... well ... let me know
what else to do ?
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11359 |
<Post edited by chatGPZ on 11/12-2008 10:41>
i very much doubt that there is a way to check wether a d64 *should* be 40 tracks. you'll get a lot of false positives (unused sectors linking to tracks > 35) and you'll also miss a lot (files completely located on tracks > 35).
this type of problems is the reason for me to keep all disks i transfered - some day i will have to transfer them all again :) |
| |
ΛΛdZ
Registered: Jul 2005
Posts: 153 |
Ok, so we need a tool that can automatically detect if there
is data in track 35+ while the disks are transfered.
(Is this done by StarCommander already?)
Graham :>> Please add detection of data in track 35+!!!
Until then I will use my "semi-track>35-data" script :/
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11359 |
no, starcommander doesnt do it automatically either...
that said, i'd like to see a tool that can detect and deal with AR Warp*25 and speeddos fload3 formats ... quite some of the disks i got are like this, and no way to transfer them with the existing tools :/ |
| |
AlexC
Registered: Jan 2008
Posts: 298 |
I doubt there ever will be a tool that can handle all 35+ tracks cases in intelligent way: recognizing if those tracks are really in use and needed. You can try to read data from those tracks and look for sync marks - than you will get 0 or 4 as job status - or other hints that there is some meaningful info but than again you can basically have anything on those tracks. Secondly you can have a case when 35+ track disk has been overwritten with 35 tracks one which means that the data on tracks 36 and so on will be still intact. The only way I can think of it to analyse the loader. Maybe CSDB should store information about releases using 35+ tracks? |
