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

Re: Update on //c to PC file transfer saga... (kinda long...)



Dean Petters wrote:

<snip>

>so now i have the two connected.  using hyperterminal set at 300 baud, 
>8-n-1, i start attempting to transfer over DOS3.3.  the first several 
>lines transfer fine but then i start getting linefeeds and markers 
>(remember the inverted L discussion?).  i think the problem was 
>two-fold.  first, i wasn't using a delay between the characters.  i had 
>a delay of 400 ms between lines, but added a 100 ms delay between 
>characters.  I also at this time got a hint from Bill @ GarberStreet 
>Enterprises about how to start up the machine.  i had been using a 
>ProDOS startup-disk and then exiting to the ]-prompt.  Instead, he said 
>to turn the machine on and when the 'no operating system' error 
>appeared, hit <ctrl>-reset to get into basic.  I'm not sure which of 
>these solved the problem, but when i tried it with these two changes, it 
>worked.  it took about 30 minutes to get DOS3.3 over to teh //c.  i then 
>created the dos startup disk.  then i used the same procedure to get ADT 
>over.  i was a happy camper!
>
>i had downloaded a copy of z-link and moved it over to the //c.  I had 
>nothing but trouble with this at first.  I'm not sure whether it is a 
>problem with z-link or if it's with my cable, but if i start z-link with 
>the cables connected between computers, the screen on the //c goes 
>blank.  if they aren't connected, it works fine even after the cables 
>are connected.  another problem i ran into was that z-link couldn't read 
>the disks i wanted to transfer the data off of.  it was so frustrating i 
>asked for other telecom programs.  again, Bill @ GarberStreet 
>Enterprises came thru with a disk image of some modem utilities.  during 
>this process, i did a directory on the source disks and realized that 
>those disks were formatted in DOS3.3.
>
>"maybe" i thought to myself, "z-link can't read dos33 disks..."  sure 
>enough, i transferred the files to a prodos disk and now am transferring 
>files!!!
>
>The disks i'm transferring have about 30 files each and i don't have a 
>way to print out the names of the files.  so the finder in z-link was 
>very nice.  i can scroll thru the list of names and copy one at a time. 
>  I'm able to transfer at speeds of up to 4800 with no trouble (i've not 
>gone higher mainly because i had problems earlier with higher speeds and 
>since the  files are small, the time difference is minimal).  most of 
>the time during the downloads is taken up with 'waiting for NAK'.  I'm 
>using Xmodem (Ymodem would not work).
>
>I've also found that to get the system to work best, i have to do a 
>software disconnect and reconnect (from the PC/hyperterminal end) 
>between each download.  not a big deal, but it is one more step.  I also 
>have to type in the name of the file since Xmodem doesn't transfer teh 
>filename.  oh well...
>
>so now i'm copying files all over the place.  the downside is that since 
>these files are so small, i'm spending most of my time in setting up the 
>transfer rather than in the actual moving of the files.  oh welll.... 
>maybe someone out there knows of a program that will allow you to select 
>multiple files to upload from the //c to the PC... (Agate only goes from 
>PC to //c).  or better yet, all files from a disk...
>
>So again, thanks to everyone here for your outstanding help! 
>Specifically, Bill @ GarberStreet Enterprises and Paul Grammens for all 
>of your help!  if we ever meet, i'm buying!

Congratulations on solving your problems and finding a way.  ;-)

You could greatly simplify your process by transferring whole disk
images of the disks you are interested in to the PC using ADT.

Then you could use CiderPress (Andy McFadden's great software)
to copy the DOS 3.3 files to PC files.  This would involve much less
setup and interaction on your part.

-michael

Check out amazing quality 8-bit Apple sound on my
Home page:  http://members.aol.com/MJMahon/