-23 Error In Disk Copy 6.5b13

[pmj]

I've recently made some backups using the ASR method described here and it seems to work fine.

However, the drive I back up has recently crept over 2GB in size and since then I don't seem to be able to use the ASR method, using Disk Copy 6.5b13 it doesn't complete the image and throws up a "-23" error in the checksum box.  I'm doing everything as before.

What do I need to change in the settings to get around this now the drive is larger?  Apologies if it's covered somewhere here already.

[pmj]

So after some more tests, it seems Disk Copy will let me make a functional Read/Write image of the drive, but attempting to create a Read-Only or Read-Only-Compressed version for the ASR process results in the -23 error code.

I also can’t convert the Read/Write image to Read Only / Compressed version as a subsequent step.  It looks like it’ll let me do it using Shrinkwrap but with a warning that data maybe lost.

Drive has 2.03GB of data on it, I thought this version of Disk Copy was fine up to around 4GB?

Does any of this suggest what the problem might be?

[teroyk]

What format is your drive where you try make that image...remember that pen drives are normally in Microsoft FAT format and it doesn't support files over 2 GB.

[pmj]

Everything is in HFS+ format, and that hasn't changed since the drive I'm backing up went over 2GB.

Basically I'm backing up the main drive that has the OS, Applications, Systems Folder etc to an external Firewire drive using Disk Copy which isn't part of the volume I'm backing up as per the ASR instructions.  As I mentioned, all that seems to have changed is the drive I'm backing up has more stuff on it than before.

[Jubadub]

Could you explain or link me to what the "ASR method" is? Personally, I have successfully created image backups of my drives that were even as big as 120GB~160GB with the latest version of Disk Copy, which IIRC is the one you are using. Never had any issues. Though it's been so long since I last did that, I forgot the details of my process.

[pmj]

Could you explain or link me to what the "ASR method" is? Personally, I have successfully created image backups of my drives that were even as big as 120GB~160GB with the latest version of Disk Copy, which IIRC is the one you are using. Never had any issues. Though it's been so long since I last did that, I forgot the details of my process.

http://macos9lives.com/smforum/index.php/topic,1839.0.html

Using these:

http://macos9lives.com/smforum/index.php/topic,1822.0.html

[OS923]

Don’t use Disk Copy above version 6.3.3.

[pmj]

Don’t use Disk Copy above version 6.3.3.

Ah, what difference does that make?  Again, sorry if that's covered somewhere but thought 6.5b13 was the one for larger volumes (2GB+) ?

Just tried using 6.3.3 and get "(152) the folder is too large to be imaged (more than 2GB of data)"

[Jubadub]

I know many reasons to use 6.5b13, but zero reasons to use 6.3.3. Some people are skeptical or uncomfortable, because it's labelled as beta software. Again, no issues. Certainly not any issues that aren't already present in 6.3.3 and earlier, anyway. (Note: 6.5b13 is PPC-only, so 68k System 7 ~ OS 8.1 users have no other option, but to use an earlier version.)

But perhaps I'm wrong. Do you know something to be problematic with 6.5b13 that we don't know of, @OS923?

[pmj]

As far as I can glean, the -23 error indicates:

openErr                 
Requested read/write permission doesn't match driver's open permission, or Attempt to open RAM serial Driver failed

This doesn’t mean a whole lot to me, can anyone put it into more noob-ish terminology so I can look for a fix?

[pmj]

Small bit of progress with this, ran the drive I'm trying to back up through Disk Warrior which returned some errors (creation dates and text encodings mostly) and since fixing these and rebooting I can now use Disk Copy 6.5b13 to create a Read-Only-Compressed image with valid checksums and that ASR can see and restore.

Trying to create a Read-Only image of the same drive still fails with the -23 error, but at least there's some progress.

[OS923]

Do you know something to be problematic with 6.5b13 that we don't know of, @OS923?

I remember that I tried it and that I was so spooked that I deleted it right away.

[pmj]

No more progress with this, can anyone suggest what the -23 error is being caused by so I can look for a fix?

[DieHard]

Yes... Apple Disk Copy v6.5b13 is the correct version to use

Try increasing the memory for both Finder and diskcopy

Reference here: http://macos9lives.com/smforum/index.php/topic,3003.msg41577.html#msg41577

[pmj]

Yes... Apple Disk Copy v6.5b13 is the correct version to use

Try increasing the memory for both Finder and diskcopy

Reference here: http://macos9lives.com/smforum/index.php/topic,3003.msg41577.html#msg41577

Thanks for those!

Tried doubling the available memory for both as you described but still getting -23, do these settings seem adequate for what I'm trying to do?

[pmj]

This is how I have Finder set, should the "Min size" be altered at all?

[DieHard]

From the famous "Sunrise Report" wich is now deleted from the Web, so I got a copy from the wayback time machine...

Actually, you can leave the memory requirements to Login, Panels, Classic, Classic Support, and Classic Support UI under OS9 as they are. To increase the memory size of OS9.2.2 System and the Finder:

1. Make a copy of OS9.2.2 System and Finder to the desktop and use ResEdit to open the two files.

2. In the System file, add an extra 100,000 bytes to the SIZE resources number -16472 and -16471 in the Preferred memory size box. While the System file is still opened in ResEdit and you are looking at all the SIZE resource, choose Get Info Resource under the Resource menu of ResEdit. Put a tick in the boxes that say "purgeable", "protected", and "preload". Do it for all SIZE resources. Save the file and quit from ResEdit.

3. In the Finder, you can be relatively generous in the Preferred memory size box of the SIZE resource. Add an extra 1,000,000 bytes. While the Finder file is still opened in ResEdit and you are looking at the SIZE resource, choose Get Info Resource under the Resource menu of ResEdit. Put a tick in the boxes that say "purgeable", "protected", and "preload". Save the file and quit from ResEdit.

4. Move the old Finder and System in the System Folder to the trash. Move the new modified files to the appropriate locations in the System Folder. DO NOT DELETE THE OLD FILES AS YOU MAY NEED THEM IF ANYTHING SHOULD GO WRONG.

5. If you have done it right to this point, the System Folder should show it is active and ready for you to restart using the system software inside.

Note: the "Sunrise Report" was a little anti Mac OS 9.2.2 (the guy was in love with Mac OS 8.6) , and most of it can be ignored IMO

[pmj]

Thanks for posting this, very useful.  The changes haven’t got rid of the -23 problem sadly but general performance seems improved.