I don't know exactly what Dave's having a
problem with, but from his
images, I could extract files using 22Disk with no problems at all.
The definition I used was CRO4.
Hi Chuck,
Exactly what version of 22disk were you using?
Is it the newer version 2.x that you mentioned earlier?
The version I am trying to use is 1.44 shareware. I am
using the CRO4 definition. I've never actually used 22disk
before, but I think I've got it right - here is a transcript
of an attempt to copy files from the diskette:
------------------------------------------------------------------------
C:\22DISK>cdir b:
CDIR Ver. 1.44-Oct 31 1996, Copyright 1996, Sydex. All rights reserved.
THIS IS AN UNREGISTERED COPY--SEE DOCUMENTATION FOR DETAILS.
Enter 1-4 character disk format type, or ENTER alone for list - cro4
Cromemco CDOS - DSDD 48 tpi 5.25" format
* WARNING! * Two files found to use same diskette block
-- You may be using the wrong disk definition
Block: 0003, File: FRAME2.PIX
B0:FRAME1.MAP B0:FRAME1.PIX B0:FRAME2.PIX
142K free on drive B:
C:\22DISK>ctod b:*.* d:
CTOD Ver. 1.44-Oct 31 1996, Copyright 1996, Sydex. All rights reserved.
THIS IS AN UNREGISTERED COPY--SEE DOCUMENTATION FOR DETAILS.
Enter 1-4 character disk format type, or ENTER alone for list - cro4
Cromemco CDOS - DSDD 48 tpi 5.25" format
Copying B0:FRAME1.MAP to D:FRAME1.MAP
Copying B0:FRAME1.PIX to D:FRAME1.PIX
Error reading diskette B: (Cyl 1, Side 1, Sect 1):
Sector not found
Enter R - retry operation, A - abort program, I - ignore error
Error reading diskette B: (Cyl 1, Side 1, Sect 1):
Sector not found
Enter R - retry operation, A - abort program, I - ignore error
Error reading diskette B: (Cyl 1, Side 1, Sect 1):
Sector not found
Enter R - retry operation, A - abort program, I - ignore error
C:\22DISK>
------------------------------------------------------------------
A little more information which may or may not be relevant:
Mike Stein reproduced one of the ImageDisk images and use his
Cromemco system to read the files and transfer them via serial
cable to the PC (thanks Mike!) - The three files I received from
him were:
FRAME1.MAP - 128 bytes
FRAME1.PIX - 88576 bytes
FRAME2.PIX - 9984 bytes
I sent these files to the author of the graphics program that
is supposed to have originated them, and he things they should
be bigger. He says the .MAP should be 768 bytes, and that the
.PIX files should be much larger - they are 512x512x256 color
images with RLE encoding, which means they could be up to 256k.
As seen above 22disk reports 143k free on a 400k disk, quick
math shows over 150k unaccounted for - There will of course
be some overhead, but not that much ... but with the cross
linked files reported, I don't know if the 143k free number
can be trusted.
Then, I dug out an XT and got it up and running (man I had
forgotten the pain involved in getting a hard drive working
on an XT)...
UNIFORM works on this machine, and I am able to extract the
same three files from the same disk.
I get FRAME1.MAP and FRAME2.PIX exactly the same size
and content as the files Mike sent to me - FRAME1.PIX
comes out at only 6144 bytes in size, although it
appears to be the same content as the first 6144 bytes
of Mikes file.
So it would appear that UNIFORM has issues as well.
Dave
--
dave06a (at) Dave Dunfield
dunfield (dot) Firmware development services & tools:
www.dunfield.com
com Collector of vintage computing equipment:
http://www.classiccmp.org/dunfield/index.html