Re: Need help, 5.25 disks and IIgs

[Rubywand <rubywand@swbell.net>]

Labelas Enoreth writes ...
> 
> Ok, here's the problem. I can't seem to get any disk imaging programs to
> work on my IIgs. DSK2FILE will write the image back to disk with no
> complaints, but the resulting disk breaks into the monitor right after it
> boots. Asimov reports a GS/OS error, of, I believe $4B when trying to
> write an image back to disk (It doesn't even begin to read or write).
> DOS33Copier either starts to boot the disk and hangs on the loading
> screen, or immediately resets. And this happens with both .dsk images I've
> had on my HD from various downloads in the past, and disks that I had just
> imaged right before. I never had this problem on the IIe card, so I
> wondered if there's something different in the IIgs setup to break this.
> Does anyone have any advice? The setup is a IIgs rom01 with 1 5.25, 2 3.5,
> 1 Apple External HD...1.5mb of RAM...GS/OS 6.0.1...


004B (ProDOS Error $4B, ...)-  is an "unsupported (or incorrect) storage
type" error. This error seems often to indicate that a file claims to have a
resource fork but does not. Sometimes a file transfer involving a Mac results
in this sort of corruption.

     When you consider all of the bother and wasted time due to resource
forks, there is no way whatever advantage they were supposed to offer will
ever come remotely close to compensating. Like most kludges, the resource
fork was a bad idea.

     Regarding DOS 3.3 Launcher and associated programs like Copier, if you
use a disk image created by some other utility, it must have ProDOS sector
ordering and filetype User#1. Something else which may snag a former IIe user
is that you need to use a different version of Copier when you move to the
IIgs.

     Finally, just in case you forgot, the target diskette for Asimov or
DSK2FILE needs to be 16-sector formatted-- e.g. INITed under DOS 3.3.



Rubywand