Hi, I'm catching up on mail after a trip. (I'm posting this same reply on both discussions on E-maculation and 68kmla.)
I believe that "Dog Cow" is generally correct, though this may or may not apply specifically to Wizardy. Mini vMac does not emulate the disk hardware at low level, and so most copy protection schemes won't work with it. For that matter, I don't believe the standard disk image format can accurately contain all the information on most disks with copy protection. No matter what Mini vMac did, the needed information from the Master disk just isn't there on your disk image copy.
At step 3 you say that the application is satisfied, and asks for the original disk back. But my guess is that it is not satisfied, and just wants the original disk back to get access to the code to display an error message. If it was satisfied, it would be extremely incompetent copy protection.
As for why it is asking for the original disk back when it already has it, my guess would be that it tried to eject the disk using a low level method that Mini vMac doesn't support, since it was already trying to use low level access for verifying the copy protection.
In summary, emulating the paper clip ejection method is a possible feature for Mini vMac, but I don't expect it would help you at all here, assuming the copy protection was implemented at all competently.
You might want to try the MESS emulator, whose Macintosh emulation appears to emulate disk access at a lower level. But I don't expect it will help. As I said, I think the needed information just isn't there.
Some people had a hobby of breaking copy protection on Mac 68k programs. I don't know what the DMCA law would say about breaking the copy protection on software you own for your own use, for software that predates that law.
I believe that "Dog Cow" is generally correct, though this may or may not apply specifically to Wizardy. Mini vMac does not emulate the disk hardware at low level, and so most copy protection schemes won't work with it. For that matter, I don't believe the standard disk image format can accurately contain all the information on most disks with copy protection. No matter what Mini vMac did, the needed information from the Master disk just isn't there on your disk image copy.
At step 3 you say that the application is satisfied, and asks for the original disk back. But my guess is that it is not satisfied, and just wants the original disk back to get access to the code to display an error message. If it was satisfied, it would be extremely incompetent copy protection.
As for why it is asking for the original disk back when it already has it, my guess would be that it tried to eject the disk using a low level method that Mini vMac doesn't support, since it was already trying to use low level access for verifying the copy protection.
In summary, emulating the paper clip ejection method is a possible feature for Mini vMac, but I don't expect it would help you at all here, assuming the copy protection was implemented at all competently.
You might want to try the MESS emulator, whose Macintosh emulation appears to emulate disk access at a lower level. But I don't expect it will help. As I said, I think the needed information just isn't there.
Some people had a hobby of breaking copy protection on Mac 68k programs. I don't know what the DMCA law would say about breaking the copy protection on software you own for your own use, for software that predates that law.