Maybe I should take a step backwards and describe my problem, and what I want to achieve.
1) I have recently created a boot floppy for my SOL20+Morrow controller combo. I created this disk using SYSGEN.
As I move forward and populate the disk with programs, I wanted to be able to make a quick duplicate in case something goes wrong. (I do have a master floppy with just CP/M on it of course as an ultimate backup).
2) This is where it gets tricky as I'm not sure whats happening. I have some floppies for an IMSAI. I don't yet have the machine as it's in transit, on it's way to me. However I wanted to back up the disks I have, as I only have a single copy of each. In the mix I only 2 floppies labelled 'IMSAI CP/M 2.2 (128)', and backing these up to some new disks would be high priority. I'd hate to loose them as I'd then have to start from scratch ,boot strapping the IMSAI, and creating a new boot floppy.
I could probably use PIP to do this though.
Having said that, when I do a DIR listing on the two disks labelled 'IMSAI CP/M 2.2 (128)' I am unable to see anything. The SOL just seems to freeze up. If I do a DIR listing on the other IMSAI floppies (the ones NOT labelled CP/M), I am able to see the contents, and copy and launch them.
Trying to boot from one of the IMSAI CP/M disks also does nothing, and again everything seems to hang with the drive LED stuck in the READ state as before.
So basically I can't yet get anything off these disks. I wanted to try a COPY program in the hopes it would work in backing up these disks.
So that's where I was as of last night. I'm not sure what this all means. Maybe the two CP/M disk are bad, but that seems very unlikely considering all the other disks look good, either that or I'm just very unlucky.
One other thought is that the CP/M disks are in a format that my drive can not read, and is different from the other IMSAI program disks...just conjecture.
Any thoughts on why this should be?
Thanks again
Phil