Re: DOS 3.3 Image Does Not Work on XGS

["Bryan Parkoff" <BParkoff@satx.rr.com>]

Thank you for the information.  I appreciate your help but the problem is
still not resolved.

    Greater than 7 bit means 128-255 characters are not compatible between
Apple IIgs and PC.  It looks like that MacBinary or HexMac have corrected
the conversion.

    Let me straighten by step to step.

1. Shrink DOS 3.3 Image from 5.25 floppy drive (Apple II) using ShrinkIt
v3.4
2. Copy DOS.SDK from GS/OS v6.0.1 to MS-DOS using MUG 1.0.1 (Peter Watson's
software) through BlueDisk controller (From ///SSH Systeme) that is in
binary.
3. After copying, it stopped working using binary.

If I convert from binary to ASCII and redo step 1-3 above, it works!
If I use original software of Peter Watson (Not Mug, but in Text mode), both
binary and ASCII work fine after copying using gmcopy command (gmcopy
DOS.SDK .d5)

Nulib v3.25 failed to unshrink DOS.SDK into DOS.Dsk if the format is binary.
It unshrinked successfully using ASCII.

I SUSPECT Apple IIgs' UUENCODE and PC's UUENCODE are incompatible because
the version is probably old.  Can you please provide me the latest version
of UUENCODE for both Apple IIgs and PC.  I prefer to use MS-DOS UUENCODE
while Apple IIgs' NDA is fine.

If UUENCODE is not necessary, please provide me another option for better
transfer.

Thanks very much...

Bryan Parkoff
BParkoff@satx.rr.com


"Charlie" <charlied@NOSPAMbboard.com> wrote in message
aje9g60d4s@enews2.newsguy.com">news:aje9g60d4s@enews2.newsguy.com...
>
> "Bryan Parkoff" <BParkoff@satx.rr.com> wrote in message
> news:GWt69.144059$6Z1.6426797@bin6.nnrp.aus1.giganews.com...
> > Charlie,
> >
> >     It is necessary to convert from binary to ASCII because NuLib will
fail
> > to unshrink Image.  I have noticed that several bytes (>7 bit) are
modified
> > while transferring from GS/OS to MS-DOS.  I do not understand why, but
ASCII
> > remained (<7 bit) unchanged.
> >     I used Kegs32, but it failed to boot DOS 3.3.  I believe that DOS
3.3
> > has different sectors in order while ProDOS has sequence sectors in
order.
> > Emulator attempts to read DOS 3.3 using seqence sectors in order before
> > machine language breaks and dumps register status.  Please advise.
> >
>
> I have never had a problem with Nulib (version 3.24) accepting binary
files.
>
> I also don't understand why you would have the high bit change when
> transferring files unless your software is automatically translating it
for
> you. I use the Transfer program that came with a PC Transporter in my
Apple
> IIgs. It has an option for translating files but I never use that.
>
> By the way I have no problem at all with Kegs32r3 booting DOS 3.3 (.dsk)
> images. It is true that DOS 3.3 used a different sector ordering than
ProDOS
> but that makes no difference to the emulator.
>
> Also if you must use a .2mg disk image it is important that the conversion
from
> .dsk to .2mg be done correctly.  I am unaware of any software for the PC
(there
> is ADFS for the MAC) that will convert a DOS ordered .dsk image to 2mg.
Are
> you doing the conversion yourself?
>
> Charlie
>
>
>
>
>