3.1.4 version of diskdoctor

[Enchanter]

Hi there all,

Stupid question, how do you use the 3.1.4 version of diskdoctor to copy data from a failing floppy? I know its a CLI program, but I cannot find any details of the command line options to use and examples.

for instance, can I copy the data from a disk in df1: to a folder on my hard drive or ram drive, say ram:T/, if so, whats the command line for that?

thanks for any assistance.
I am sure I am missing something simple here!

[alexh]

If that disk is important to you, don't use "diskdoctor". It will attempt to repair the disk you're using.

Use a modern multi-pass imaging tool. Dump the current readable contents. Analyse the results to see which side where approx the errors are and then perhaps physically clean that area of the disk.

[thomas]

Originally Posted by alexh

If that disk is important to you, don't use "diskdoctor". It will attempt to repair the disk you're using.

That's not true. The 3.1.4 version is a complete rewrite. It's more like a modern version of DiskSalv, not comparable to the old DiskDoctor.

[Olaf Barthel]

Originally Posted by Enchanter

Hi there all,

Stupid question, how do you use the 3.1.4 version of diskdoctor to copy data from a failing floppy? I know its a CLI program, but I cannot find any details of the command line options to use and examples.

for instance, can I copy the data from a disk in df1: to a folder on my hard drive or ram drive, say ram:T/, if so, whats the command line for that?

That would be:

diskdoctor copy df1: ram:T/

You might want to tell Disk Doctor to check what's up with the disk first, though, to get an idea of what to expect:

diskdoctor examine df1:

Please note that examining the disk/partition is the default operating mode for the new Disk Doctor.

If you have it, I strongly recommend using Disk Doctor 2.161 from the AmigaOS 3.1.4.1 update since it fixes a significant (and hard to find!) bug in the program which might otherwise impact the usefulness of the program...

[Enchanter]

Originally Posted by Olaf Barthel

That would be:

diskdoctor copy df1: ram:T/

You might want to tell Disk Doctor to check what's up with the disk first, though, to get an idea of what to expect:

diskdoctor examine df1:

Please note that examining the disk/partition is the default operating mode for the new Disk Doctor.

If you have it, I strongly recommend using Disk Doctor 2.161 from the AmigaOS 3.1.4.1 update since it fixes a significant (and hard to find!) bug in the program which might otherwise impact the usefulness of the program...

Thanks, I tried that command and got:

5.Ram Disk:> diskdoctor copy df1: ram:T/
DiskDoctor: wrong number of arguments

I had previously performed an analysis using examine. Does DoskDoctor use this analysis or is it cosmetic for my benefit?

Where would I get the 3.1.4.1 update?
I purchased 3.1.4 from a reseller not directly from Hyperion.

Thanks for your reply.

[Daedalus]

You can still register it with Hyperion using the serial number on the ROM chips and you can download the update from there.

[Enchanter]

Hi again,
I also tried the command

diskdoctor copy from df1: to ram:T/

Which did run, however after the examination I received:

ERROR: Could not create destination directory "ram:T/" (object name invalid).

Best Regards,

[gulliver]

Originally Posted by Enchanter

Hi again,
I also tried the command

diskdoctor copy from df1: to ram:T/

Which did run, however after the examination I received:

ERROR: Could not create destination directory "ram:T/" (object name invalid).

Best Regards,

A wise man (not me) once said:

It's probably the trailing "/", which ram-handler misinterprets as trying to create a nameless directory in "RAM:".

[Enchanter]

Originally Posted by gulliver

A wise man (not me) once said:

It's probably the trailing "/", which ram-handler misinterprets as trying to create a nameless directory in "RAM:".

That did it.
thanks @gulliver

[gulliver]

Excellent.

Just thank Olaf who is the mastermind behind DiskDoctor.

[jostberg]

One of my partitions crashed as the computer froze while writing data to disk. Diskdoctor from 3.1.4.1 finds all files when examining but simply copies nothing to another disk.

Bitmap is wrong/invalid and the partition shows up as uninitialized on Workbench. File system is latest FFS from 3.1.4.1

Is there anything else to try?

[gulliver]

Please verify you used the correct arguments and options with DiskDoctor.