[comp.sys.m6809] Help

mdk@cblpf.ATT.COM (x5693) (10/08/87)

Hello everyone,
I need some help.  I have tried downloading the uuencoded 'ar' file several
times and everytime I try to uudecode it, I get an error message stating:
     Short file
     Error 010
I use Cer-Comp's DatapackIII+ as my terminal software, so the files
originally get put onto an RSDOS diskette.  The first time I transferred
the 'ar' file from the RSDOS disk to my OS9 disk using TRSCOPY.  After I
transferred the file I ran uudecode on it (this is the latest uudecode version
with the added 644 in the scanf line).  I have also edited the original 'ar'
file to include the 'begin ar 644' line at the top.  Uudecode runs for a while
and I get about half a decoded file (the original file length was $4000 bytes,
the decoded file is $2EEC bytes long).  finally, I tried to edit the file to
see if some mystery characters had been picked up through the download.
TSEDIT did show question marks (?) in front of each line.  Of course TSEDIT
couldn't edit the whole file at once, it was too large for the buffer.

I have checked the uudecode file and I don't see anything wrong with it.
There was also a strip program in a recent Rainbow magazine that would
strip line feeds from programs downloaded through DESKMATE.  I compiled the
strip program, ran it, and output from it said that it stripped 6 control
characters from the 'ar' file, but I still can't get the darn thing to
decode.

Has anyone else had these problems, and what have you done about it?  I
would really like to use the patch programs to use TSEDIT on an 80 column
window.

Thanks for any help anyone can render.

Mike King
..!ihnp4!cbosgd!cblpf!mdk



-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Oh, now you gone and squashed my favorite 'beatles'!
                                                      -The Doctor
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

houser@mcnc.org (Kevin Dan Houser) (08/10/88)

       I'm still having problems creating a bootfile on my 40trk DS drives
for MultiVue. Seems that the header of WindInt in the bootfile os9gen
creates is bogus, although sometimes I get other bogus modules instead.
However, the windint module in the MODULES directory has a good HEADER.
I've tryed putting Init at the end of the bootlist and other arrangements
of the list, but no dice.
     Also does anyone know of a patch for TRSCopy or have a program they
could email me that will allow me to transfer RSDOS and OS9 text files
back and forth? Seems Like it doesn't work on my 40tr/DSDD system.

One more! --whew-- Do I need the Level 1 assembler to compile my
pascal programs to machine code? I've heard that the Pascal P-Code is
incompatible with the Level 2 assembler. 

This stuff drives me nuts at times, and Microware isn't to swooft about
updates or patches with their software.

And again, anyone out there upgraded a CoCo 3 to 1 Meg of bankswitchable
ram that is compatible/useable under OS9 Lvl 2?

 
@@  @@  |  @@  @@  @@  |  @@  @@  |  @@  @@  @@  |  @@  @@  |  @@  @@  @@  |    @@  @@  |  @@  @@  @@  |  @@  @@  |  @@  @@  @@  |  @@  @@  |  @@  @@  @@  |    @@  @@  |  @@  @@  @@  |  @@  @@  |  @@  @@  @@  |  @@  @@  |  @@  @@  @@  |    |   |   

es@polari.UUCP (Erich Sweaney) (03/02/90)

Hi. I recently saw the message that talked about subcribing the CoCo Sig, bu Usenet. We'll I typed subscribe coco, and it gave me a error, like unknown user, so I tyoed subscribe coco Erich Sweaney and that still did not work? Does any know how? or can help me? Thank you..

    

hpn@attcc.UUCP (03/04/90)

>Hi. I recently saw the message that talked about subcribing the CoCo Sig, bu Usenet. We'll I typed subscribe coco, and it gave me a error, like unknown user, so I tyoed subscribe coco Erich Sweaney and that still did not work? Does any know how? or can help me? Thank you..

   
What you did wrong was sending your commands to COCO@pucc.princeton.edu .
The right thing to do is to send to LISTSERV@pucc.princeton.edu
subscribe Coco Eric Sweaney

Huy Nguyen
p.s. whenever sending a command to *any* listserver, make sure you send to
listserv@wherever.etc.etc, not the listname.  When you sent your subscription
request to COCO@pucc.princeton.edu, everyone on the List got a copy of it.(Really gets on a persons nerve when soemeone does that, but just make sure you don't do it too often (you get BLUE *flames* :)