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

Re: Transfer From IIgs to PC Successful--Read Please



	<lurk-mode OFF>

   Bryan, since you have a Blue Disk I can save you a step in
transfering
files across. Peter Watson made an excellent NDA called MUG!. It was the
culmination of his MSDOS utilities for moving data and programs back and
forth from Apple2's and PC's. You should be able to get this from
Ground's
or Tarnover's sites. You can setup whether transfers are smart (ie.
detect
ascii and translate) or do a straight 8 bit transfer. It looks like the
HFS
on the GS side or the MAC tools on the PC side is introducing an error
along
these lines. Try MUG! it's much better than the hoops you are jumping
through
right now. BTW, to get a GS to see a disk formatted on a PC (win95 and
later)
you _must_ give the disk a volume name, this is funkiness with the MSDOS
FST on the GS side.

	Luck, tmyers.

Bryan Parkoff wrote:
> 
> Transfer From IIgs to PC Successful--Read Please
> 
>     I want to explain what I am doing while I try to determine why binary is
> not compatible between IIgs/Mac and PC.
>     I shrinked a whole 3.5" diskette within .SDK extension by using ShrinkIt
> v3.4.  I formatted HFS format on 1.44MB diskette through BlueDisk controller
> card before I copied .SDK on it.  I put it into my PC by using MacOpener
> program before I copied .SDK into FAT32 format.  I tried to nulib .SDK back
> to the original size, but nulib failed.
>     It is very clear that it has nothing wrong with nulib nor MacOpener.  In
> fact, ASCII 128-256 between Apple IIgs and PC are very different.  Some
> characters between ASCII 128-256 may be modified itself incorrectly while it
> is transferring.
>     I have to UUENCODE .SDK from Apple IIgs before it can be transferred to
> PC.  After it is transferred, I UUDECODED .SDK in FAT32 format.  Then, I did
> nulib .SDK back to the original size successfully.  I did check CRC checksum
> and the binary.  All of them are identifical.
>     It is all done without through Macintosh.  Please explain why ASCII
> 128-256 may be different while binary is supposed to be unchanged.  Please
> advise.
> 
> --
> 
> Yours Truly,
> 
> Bryan Parkoff
> BParkoff@satx.rr.com