[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Need help, 5.25 disks and IIgs



labelas@hotmail.com (Labelas Enoreth) wrote:

>Well, some of the files were copied from a mac onto a prodos disk, but
>they had been residing on a prodos drive on the mac. Others had been made
>right on the IIgs. I think a few of them had had improper file types when
>on the mac, so I used ctc to change them from 'TEXT BINA' to whatever the
>type was for the disk image, I think it was BINA though not sure, may have
>just been p<gibberish> and the type to pdos.

PC Exchange puts a resource fork on files whenever they move
from HFS to ProDOS.  Even if they are later moved from ProDOS
to ProDOS, if they had ever been on HFS first and moved with
PC Exchange, a resource fork will be placed.
 
>>      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.
>
>Well, if it weren't for the resource fork, mac stuff would probably be a
>lot less graceful to deal with. And easy to tweak. However, if the IIgs
>didn't really use it in any meaningful way than perhaps it would have been
>better off without it. But I know I use ResEdit on my Mac very often.

The IIGS makes extensive and VERY meaningful use of resource
forks, thank you.  There are plenty of resource editors on the
IIGS.  Without resource forks, GS/OS programs will be much
less graceful.
 
>>      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.
>
>Yeah, I'm using the right version of copier, I redownloaded it to make sure.
>As for the images, I thought DOS3.3 launcher wanted .do format images? not
>.po? Well, I'll check again. But I also tried imaging it right there with
>the copier prog as well...and for the filetype I used the copier utility
>to set the proper options and it gave it the correct filetype for me.

DOS 3.3 Launcher wants .po images.  .PO images of DOS 3.3
or DOS 3.3 compatible (Proto-DOS, etc.) disks.  The DOS 3.3
Copier produces .po images.