[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Sun to Mac to //c and back
- Subject: Re: Sun to Mac to //c and back
- From: shack@deimos.frii.com (Randy Shackelford)
- Date: 1996/08/31
- Newsgroups: comp.sys.apple2, comp.emulators.apple2
- Organization: Front Range Internet, Inc, Fort Collins, Colorado
- References: <507993$2qv@Germany.EU.net> <507pv7$s38@darla.visi.com>
In article <507pv7$s38@darla.visi.com>, Nathan Mates <nathan@visi.com> wrote:
>In article <507993$2qv@Germany.EU.net>,
>Joerg Heitkoetter <jh@Germany.EU.net> wrote:
>>Then I start Fetch on my Mac and transfer the files to a ProDOS 720K
>>disk; great I think and move the disk over to the //c and voila
>>the disk is readable; but--the files have type $00 not SYS and TXT
>>as expected; ok I thought, let's bload the files and bsave them with the
>>appropriate type; but this doesn't seem to work; it's
>>always WRONG FILE TYPE (load, bload, run, exec, whatever);
Actually BASIC gives FILE TYPE MISMATCH since that's the closest it can get to
ProDOS 8's unsupported storage_type error
> Shoulda noticed this before; the problem (as email conversations
>seems to have turned out) comes down to 3 letters: M-A-C. Idiot box
>****ing insisits on adding resource forks to files, making them
>unreadable under ProDOS 8.
If a file has no resource fork, copying it to a ProDOS disk doesn't add one;
I just verified this on my Powerbook. I took a copy of Appleworks on a 3.5 disk
and copied all the files to my Powerbook's RAM disk, then put in a blank ProDOS
disk and copied 'em to it. Appleworks ran fine off this disk.
> I am > < (fingers about 1/8" apart) close to actually recommending
>that people wishing to download stuff to Apple IIs AVOID Macintoshes
>completely. In the FAQ. This is because of their BONEHEADED and
>UNNECESSARY inisistence on adding resource forks.
Doing so would be propagating an inaccuracy, something you've been railing
against so much lately. I have my workstation equipped //e and my IIgses
networked with my Macs, and I can transfer files under ProDOS 8 and they
work slicker than snot.
> When something appears to do what you want, but prevents you from
>actually doing it, that is worse than not supporting it directly. If
>it's going to trip up far more people than will benefit, I'm going to
>recommend against such things.
What say you get off your Mac hating high horse and help find a solution?
Didn't I see someone saying here not long ago that any file with with a
certain file type/creator combo can be copied to a ProDOS disk without
making the file an extended storage type file? I never worried about finding
out since I never use sneakernet. If you can set the type such that the
files copy properly, end of problem, correct?
Failing that, I have a ProDOS 8 program I wrote for my own use which can read
an extended file's data fork and write its data into a standard file. I also
have an unfinished program for deleting extended files under ProDOS 8. Last
I worked on it, it worked except for causing the blocks_used field of the
volume directory header on the affected disk to be off by one.
--
Randy Shackelford US Air Force officer
shack@frii.com and Apple aficionado