103126 Views 9 Replies Latest reply: May 21, 2008 8:34 PM by ScofieldKid
Happy Dad, I get this error all the time and hate it because it is just a dead end for me.
For example, being able to have Windows XP, Vista, various distributions of Linux, and Mac OS X Tiger and Leopard all on one portable external drive would be very convenient, but I run into this error. I would like to know the cause of this, and what I can do to avoid this in the future.
MIDI Manager Errors
-250 midiNoClientErr no client with that ID found
-251 midiNoPortErr no port with that ID found
-252 midiTooManyPortsErr too many ports already installed in the system
-253 midiTooManyConsErr too many connections made
-254 midiVConnectErr pending virtual connection created
-255 midiVConnectMade pending virtual connection resolved
-256 midiVConnectRmvd pending virtual connection removed
-257 midiNoConErr no connection exists between specified ports
-258 midiWriteErr couldn't write to all connected ports
-259 midiNameLenErr name supplied is longer than 31 characters
-260 midiDupIDErr duplicate client ID
-261 midiInvalidCmdErr command not supported for port type
Message was edited by: Smokerz
Sorry that did not help me at all.
I reloaded Leopard from scratch (that takes a long time..) and I tried to open up my image file so try to pull of my data.
Still no luck!
Finder gives me the following warning.
The following disk images failed to mount
no mountable file systems
Any ideas anyone??
Just adding that I'm also having this problem.
"Could not validate source - error 254"
I'm trying to restore an ISO (slipstreamed XP CD) to an external USB drive, to save me from burning dozens of cd's getting it right.
I get the same error if I convert to DMG or CDR
I'm guessing it's because the image file system is not HFS?
Happy Dad, Is the external drive which contains your backup image FAT32 or HFS? If it's FAT32, this might be the cause of your problem. Some information may be lost about the DMG when stored on FAT32 (that is just a guess- i don't really know at all)
Smokerz, besides your reply being really unhelpful, all that information is for OS 9 and earlier, as is clearly stated in the link you gave.
Ah, I think I figured this one out.
What is going on here is the original is a VOLUME image.
So the source and destionation need to be VOLUMES, not he .dmg.
So... attach a drive, and use the original VOLUME of the .dmg,
not the .dmg itself as the source, and make the target a VOLUME as well.
I had both of these as partitions on an external USB 2.5" notebook drive.
That was split in half. Now I'm recovering the 1st volume to the 2nd half,
and it appears to be working now!