[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Disk images-- ShrinkIt .sdk on dsk's
Supertimer writes ...
>
> Rubywand <rubywand@swbell.net> wrote:
>
....
> > Most .sdk files are automatically compressed at the time of creation
> >because this saves space. Something around 80k is a fairly common size.
> >Nearly any compressed .sdk file of a 140k disk will fit on a 140k disk
> >image.
> >
> > Suppose you are running AppleWin (or some other emu) and have a disk
> >image which contains an .sdk file in 'Drive 1'. Can it be unshrinked to a
> >target disk image in 'Drive 2'?
> >
> > On a real Apple II, of course, there would be no problem. ShrinkIt
> >3.4 would unshrink the .sdk file to the target diskette. Will this work
> >on any current emu? If it will and there are ways to get the .sdk files
> >onto dsk's, then there would be a way for emu users to access nearly
> >everything in 5.25" .sdk files.
>
> Well, it does work, at least under XGS. I once .sdk compressed an 800k
> IIGS disk containing a 5.25" .sdk on that disk. I used NuLib to create an
> 800k disk image from that 800k .sdk. Then I mounted the disk image in
> XGS. It showed up in the emulated IIGS Finder (very slowly, I might add).
> Running 8-bit ShrinkIt from Finder under XGS, one could then extract the
> 5.25" .sdk file inside the 800k disk image onto a blank 5.25" disk image.
>
> But why would you do this? I mean, I only did it because the smaller
> .sdk happened to be on the 3.5" disk I was imaging. Normally, why not
> use NuLib to change the 5.25" .sdk file into a .dsk and be done with it?
>
> Emu users should just use NuLib to convert .sdk archives into .dsk. It
> saves the step of moving the .sdk file into a disk image!
Except, NuLib will not (as far as I know) work with ShrinkIt .sdk files
which include compression-- which is pretty nearly all .sdk files.
Just tried something like your experiment. Instead of 800k stuff, only
140k 5.25" dsk's were involved. The emu used was AppleWin.
ShrinkIt 3.4 had no difficulty shrinking a 140k dsk and placing the
resulting whole-disk .sdk file on a dsk in Drive 2.
And, ShrinkIt had no problem unshrinking the new .sdk file to a target dsk
in Drive 2. (The target dsk can be ProDOS or DOS 3.3 and does not need to be
blank because ShrinkIt formats the target dsk.)
So, if there is a way to put .sdk files on dsk, it looks like emu users
can access nearly all .sdk files by just using ShrinkIt to unshrink them to dsk
form.
Rubywand