Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in - nap
CSDb User Forums


Forums > CSDb Discussions > C-64 formatting program which supports multiple disk drives simultaneously and has proper error checking
2010-03-19 05:20
vedos
Account closed

Registered: Jul 2003
Posts: 33
C-64 formatting program which supports multiple disk drives simultaneously and has proper error checking

Can anyone recommend me a good disk formatting program for C-64 (I'm using 1541 and 1541-II drives) which supports multiple disk drives (preferrably simultaneously) and has a proper disk error detection (as far as I've understood eg. Action Replay MK VI's format doesn't check for disk errors). The speed isn't that important. I just want to format working disks. :)
2010-03-19 08:29
Krill

Registered: Apr 2002
Posts: 2969
If speed is not an issue, just use the built-in format:
openN,8,15,"n:disk,id"
where N can be at least any number between 0 and 15, and the 8 is obviously the drive number.

This command immediately returns, so you can issue it multiple times on multiple connected drives. Just increase N with every invokation.

However, before re-using an N, you need to
close N
I don't know how well this does error-check on disks, but you can get no better format than the ROM routines, which are that slow for a reason. (And you can always use a tool like Disk Checker to check) :)
2010-03-19 12:38
hevosenliha

Registered: Sep 2008
Posts: 48
I guess this is just me, but I've always had problems using the built in formatter, on 1541, 1541-II and Excellerator+ (and that drive was brand new...)

The disks simply just don't work reliably when formatted with the built in... When formatted with some turbo formatter I've had no problems what so ever.

The latest utility I've used is from alpha flight, but I don't think it can be used on multiple drives...
2010-03-19 20:22
Skate

Registered: Jul 2003
Posts: 494
Action Replay's format command (@n) always worked for me. And I find it early to check disk at format level. Copy whatever you want, then make an error check with a tool like which Krill suggested.
2010-03-19 21:37
vedos
Account closed

Registered: Jul 2003
Posts: 33
Quote: If speed is not an issue, just use the built-in format:
openN,8,15,"n:disk,id"
where N can be at least any number between 0 and 15, and the 8 is obviously the drive number.

This command immediately returns, so you can issue it multiple times on multiple connected drives. Just increase N with every invokation.

However, before re-using an N, you need to
close N
I don't know how well this does error-check on disks, but you can get no better format than the ROM routines, which are that slow for a reason. (And you can always use a tool like Disk Checker to check) :)


In which way this reports if there are errors during format? I'd like a program which could be used to format using 2 to 4 disk drives at once. Does anyone know if such program exists?
2010-03-19 22:41
chatGPZ

Registered: Dec 2001
Posts: 11360
Quote:
Action Replay's format command (@n) always worked for me.


uh yeah, because it does no error checking whatsoever. AR even formats a slice of bread =)

if you want a reliably formatted disk, DONT use AR to format (and avoid most other fastformatters too). either use the cbm dos one (which indeed does all necessary error checking) or the one from grahams TFR (which is a bit faster, and still has verify)
2010-03-20 00:18
Skate

Registered: Jul 2003
Posts: 494
@Groepaz: did you read my message to the end? I say it's not necessery to make an error check until you finish copying your files. quick format, copy, then check for errors. even if your disk is damaged but your files are not covering that track/sector, hell with that error.
2010-03-20 05:10
Oswald

Registered: Apr 2002
Posts: 5086
I hate to say it, but groppie is kinda right here :)
2010-03-20 13:22
SIDWAVE
Account closed

Registered: Apr 2002
Posts: 2238
Fast Hack'em, worked since 1985
2010-03-20 13:39
Krill

Registered: Apr 2002
Posts: 2969
Quote: Fast Hack'em, worked since 1985

Which version are you referring to? I found none which has a multi-drive formatter.
2010-03-21 04:10
chatGPZ

Registered: Dec 2001
Posts: 11360
Quote:
Groepaz: did you read my message to the end? I say it's not necessery to make an error check until you finish copying your files. quick format, copy, then check for errors. even if your disk is damaged but your files are not covering that track/sector, hell with that error.


its not that easy unfortunately. as long as you are never going to write again to that disk, then everything is fine. (thats why many people dont remember AR fastformat as problematic). the problems arise whenever you are going to write something to the disk.... because:

a proper format routine as a first step determines how many bit cells can be written to a track in one rotation (the duration of a bit cell it can write is fixed, but the rotation speed is not). now it calculates the number of padding bytes that must be used to fill the various gaps on the track. many fastformatters skip this step completely and use hardcoded values for an assumed rotation speed of 300rpm. (and this is what saves a lot of time, its not the verify of actual written blocks - that can be done in a single additional rotation).

and this is why omitting the above eventually becomes a problem:

assume you ar fast-formatted a disk on a drive that spins slightly slower than 300rpm. the consequence would be that all gaps are slightly shorter on the medium than they should be. now you put this disk into a drive which is slightly faster than 300rpm.... you can read the disk fine, no problem. but when writing to the disk all hell breaks lose: when writing a block, the drive looks for the sector header, and when the sector is found waits until the data block comes by, switches to write mode and then writes out a full block. due to the analog nature of the media (rotation speed is not fixed) the actual physical area on disk which represents this written sector doesnt always perfectly match the old same sector, but "moves back and forth" a bit - thats why the padding gaps between data blocks and sector headers exist. now remember, the drive we are using is a bit too fast, and this very gap is a bit too short. what eventually happens now is that the data block overwrites the sync mark before the following sector header - resulting in that sector beeing unreadable (sector header not found).

and thats why a proper format routine is win :)
 
... 15 posts hidden. Click here to view all posts....
 
Previous - 1 | 2 | 3 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
ccr/TNSP
Guests online: 65
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Coma Light 13  (9.7)
4 Edge of Disgrace  (9.6)
5 Mojo  (9.6)
6 The Demo Coder  (9.6)
7 What Is The Matrix 2  (9.6)
8 Uncensored  (9.6)
9 Comaland 100%  (9.6)
10 Wonderland XIV  (9.6)
Top onefile Demos
1 Layers  (9.6)
2 Party Elk 2  (9.6)
3 Cubic Dream  (9.6)
4 Copper Booze  (9.6)
5 Libertongo  (9.5)
6 Rainbow Connection  (9.5)
7 Onscreen 5k  (9.5)
8 Morph  (9.5)
9 Dawnfall V1.1  (9.5)
10 It's More Fun to Com..  (9.5)
Top Groups
1 Performers  (9.3)
2 Booze Design  (9.3)
3 Oxyron  (9.3)
4 Nostalgia  (9.3)
5 Triad  (9.2)
Top Original Suppliers
1 Derbyshire Ram  (9.7)
2 Fungus  (9.3)
3 Black Beard  (9.2)
4 Baracuda  (9.2)
5 hedning  (9.1)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.053 sec.