I need help uploading a word for windows 6.0 document to Grex.  
the files is C:/WINWORD/BJORN/AD&D/VLADHEIM.DOC
                                         or .TXT (I saved it both ways)

Which one do I have to upload?  The document has alot of urs and o amulets
in it.  And a couple i's with /s over them, whatever those are called.
Hjelp.

32 responses total.

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.

Okay, I'll upload it as binary.  

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

Tell me the whole procude please, I no nothing about uploading.
Grex kicked me off twice when I attempted to use kermit.

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.

Still doesn't help much.  My modem always tells me it can't send,
and in turn tells me to check my protocol.

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

I'll try it.  I am using a windows program to log in though...

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.

Try Control-] C to get to command mode.  

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

I'm pretty sure that the command-escape character is configurable, and
varies.  (And escape is ctl-[, for what it's worth.)

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-].

But you're probably better off just changing the instructions I gave
you to correspond to your settings, which are more likely normal.
I told you I hadn't used PC Kermit in a while. That's a symptom. Sorry.

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.

rtf is indeed another option. The advantage of rtf is that it looks
like a plain text file, and can be uploaded and emailed as such. It contains
embeedded commands that control fonts, styles, sizes, etc. It may
tharefore meet vidar's needs. In general though, rtf is limited in 
comparison to native formats, because it doesn't handle grpahics
and some other bells, whistles, and gongs.

I wished I'd thought of it, and I'd recommend vidar try it.

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.

I'm sure you can upload a text or RTF file without Xmodem or Kermit.
You should be able to (at a unix prompt)

cat > fyle

where fyle is the unix filename.  Then do what my terminal program calls
an ascii upload (perhaps your terminal can send a text file using some
other command than upload, or perhaps you have to tell it that uploads
are text instead of binary) and after you've transmitted the file, use a
ctrl-d to tell cat that you're done.  

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

This response has been erased.

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?

Okay.  I've uploaded it.  Now what do I do with it?
(I know, read previous responses)

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?

No, I just planned for ziggy to download it.

It's not the problem with the fonts.  It's the problem with the ever changing
colour of text.  I guess Times Roman would be a better bet than Times New
Roman?

someone please explain this rtf to me? what does it do? for whom or what soft-
ware, for how many jelly beans? I have problems with wanting to send accents,
symbols and odd fonts, too.

I don't know nothin' about it.  All I knoe is that I'll have to change parts
of my document, before I re-upload it.  I'm going to delete it now...

This response has been erased.

I'm going to have to change the font.  I'll also have to counter some
text formatting.  Too bad, I find it easier to find a section by colour
of type rather than just bold heading.

I did a binary download, since it was a .doc file.

I might also need to do something to it during the next upload attempt.

I've uploaded it, again.  Now what?

Response not possible - You must register and login before posting.

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss