|
Grex > Coop6 > #41: Grex is now running sendmail 8.6.9 | |
|
| Author |
Message |
| 7 new of 106 responses total. |
nephi
|
|
response 100 of 106:
| 
Feb 25 06:39 UTC 1995 |
Umm, what do you mean by "find the right menu item to recieve a
file via windows terminal"?
|
ajax
|
|
response 101 of 106:
|
Feb 25 06:54 UTC 1995 |
I just checked on my laptop, and what you should do is go
to the Settings menu, pick Binary Transfers, and select Kermit.
Then, after you give the kermit command on Grex, go to the
Transfers menu, and choose Receive Binary File. Then cross
your fingers and, if it's a big file, go make a sandwich.
|
srw
|
|
response 102 of 106:
|
Feb 25 08:26 UTC 1995 |
Thanks Rob. I was on a Mac, and didn't have the details handy.
|
popcorn
|
|
response 103 of 106:
|
Feb 25 13:22 UTC 1995 |
<set geek-speak mode on>
If the files are text files, you might want to use ASCII transfer and not
Binary mode. Unix systems use linefeeds at the end of each line of a text
file; DOS machines use a carriage-return *and* a linefeed. If you use
Kermit in text mode to send a text file, it will automatically do the
translations of end-of-line characters for you, which makes it a lot easier
to read the files on the system you send them to. If the files are zipped
or compressed in some way, you need to use binary mode in order to be able
to uncompress them, and Kermit won't do end-of-line character
translations.
<set geek-speak mode off>
|
srw
|
|
response 104 of 106:
|
Feb 25 18:15 UTC 1995 |
Ok, that's all true, but hardly a big deal. If you try to type a unix
text file that came from dos and wasn't "fixed" it will lack <cr>s, so
you will get
each line appearing
like this and so it will be
hard to read.
but you can read such a file into nearly any editor on a dos/windows
system, and then write it out again and it will have <cr>s.
Also there are programs written to fix this up after the fact.
|
steve
|
|
response 105 of 106:
|
Feb 25 18:35 UTC 1995 |
Grex is now running sendmail 8.6.10. This new version plugs up a
possible security hole.
|
lilmo
|
|
response 106 of 106:
|
Feb 25 19:08 UTC 1995 |
Interesting how that comment seems out of place ... :-)
|