response 1 of 32:

Feb 20 14:42 UTC 1994

If you're trying to transfer it to another person with the accent marks
intact, you're going to have to upload the .doc file as a binary file.
This file will not be readable by people on Grex.  If you want Grex folks
to be able to read the file while on-line upload the .txt file, but I
think you're going to lose the accents.

response 3 of 32:

Feb 20 23:16 UTC 1994

If you're going to send the binary file as email, you'll need to uuencode
it.

response 5 of 32:

Feb 20 23:53 UTC 1994

Unless you're a real kermit aficionado, you're probably better off
stickingg to zmodem.  Type "rz" here then start your upload.

Like srw says, if you're going to e-mail it, you're going to have to
uuencode it first, though.  The receiving party will have to have the
uudecode program.

response 7 of 32:

Feb 21 00:27 UTC 1994

Using kermit to upload a binary file isn't that tough. First you
log in to Grex using PC kermit like you (presumably) always do.
Then you start C-Kermit on Grex by saying "kermit". Then issue the
cammand "set file type binary" to C- Kermit, and then the command
"receive".

Now use esc C to put PC-Kermit back in command mode, then issue the
commands "set file type binary" and "send <yourfile>".
It has been a while since I used PC Kermit, but I think that's right.

Once your binary file has been uploaded to Grex, if you want to send
it via email, you need to uuencode it. If your file is named
foo.doc, then  say "uuencode foo.doc foo.doc >foo.doc.uu"
Yes you have to give the file name twice.

Then send the email beginning with a normal letter and append the
file foo.doc.uu to the end of your email (using the editor of your
choice).

If the recipient of your email uses unix, the uudecode program that
they will need is a given. On other types of machines (Macs, PCs,
mainframes, etc.) uudecode is probably available, but they might not
have it. You should ask.

I hope this helps.

-srw

response 9 of 32:

Feb 21 01:43 UTC 1994

Esc C?  It doesn't work!
All I get is "KERMIT READY TO RECEIVE" and then
"#N3"
I can't get it to so back to command mode.

response 11 of 32:

Feb 21 02:14 UTC 1994

Okay, I'll try but I'm not promising anything.
-]

response 13 of 32:

Feb 21 13:57 UTC 1994

Yes, it is configurable.  On my version of PC-Kermit (3.13) configured
as it came, the command is Control-] C.  And yes, escape is ctl-[,
so if you want it configured for that, you'll need to edit your
mskermit.ini file (I believe; suppose you could also do that while on
line just to try it out).  A "show term" from command mode (e.g.
where you end up right after Kermit runs) will tell you what the
escape-character is set to.  You can do a "set escape-char \027"
to set it to escape instead of ctrl-].

response 15 of 32:

Feb 21 17:05 UTC 1994

I think there's an easier plan than uploading the binary .DOC file
and uuencode and mail.  I use WordPerfect for Windows 5.1 and I can save
documents in Rich Text Format (RTF).  I'm fairly sure that grex and the
Internet would be able to treat an RTF file like a regular text file,
while the word processor of the person you're sending to would be able to
treat it as a word processor file.  RTF has worked pretty well when I
wanted to transfer files via disk between my word processor and MS Word
for the Mac.  I have not tried it for e-mail yet, however.

If RTF is not an option, you still should not have to uuencode the .DOC
file if the person you're sending to can use MINE.  I don't know much
about MINE, but it seems to be a way to mail binary files which you can
use via pine.

response 17 of 32:

Feb 21 20:55 UTC 1994

Considering the fact that I am using an Xmodem or Kermit, as those are my
only choices and the recipient is using a Mac (I'm using a Dell 486 SX with
Intel Inside), it would probably be better just to print out the damn file
and hand it to him.  However I will try the Xmodem upload, I do not want to
lose accents.

response 19 of 32:

Feb 21 22:43 UTC 1994

Hmm, I think I'll go with printing it out.
I still can't upload it worth dog shit.

response 21 of 32:

Feb 25 19:28 UTC 1994

Okay.  But the status bar never even begins to fill.  It just retries until
I give up.  And then I ^C.
Are you sure this is going to work when the recepient (ziggy) is using a Mac,
and I the sender am using a DELL 486 SX IBM clone?

response 23 of 32:

Feb 26 01:13 UTC 1994

Well I have a Mac, and I have MS Word for the Mac which can read
some PC Word documents, so I downloaded it to see if it would work.
It did not. The Mac Word would not recognize the format, so
it offered only to read it as plain text. I do not know why this
mismatch exists between MS Word on PCs and Macs, but I have seen it
before.

There is readable text there embedded in the control junk, but I
didn't read any of it. Vidar, I would recommend that if you want to
preserve the fancy characters you should export the document from MS
Word in "Rich Text format". But you also need to be sure that the
recipient has the fonts you are using. This may be too much of a
pain to go on with. It can be done though.

If the file were usable by a Mac, the next question I'd ask would be
whether the recipient logs into grex or not. If not, were you
planning to email it?