home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Elysian Archive
/
AmigaElysianArchive.iso
/
comm
/
portalx1.lha
/
Problems.Txt
< prev
next >
Wrap
Text File
|
1992-09-12
|
3KB
|
64 lines
Common PortalX problems, and their solutions.
---------------------------------------------
"I entered [Emacs] as my editor name, but when I try and write a message,
a little window appears on the Workbench screen that says 'Unknown
Command Emacs'".
Whatever editor you use, if you run PortalX from the Workbench,
you have to give the complete path to the editor in the PortalX
Set Editor window. For Emacs, under a standard 2.04 Workbench
setup, this would be 'Sys:Tools/Emacs'.
"There is garbage on one of my messages".
"Part of one message is repeated through all the ones after it".
Some line noise or other interruption occurred, and PortalX
didn't notice. Often this is because it is something that
only a human could notice - there is nothing technically
wrong with the data. There is nothing you can do about this.
PortalX is more susceptible to line noise than a normal
terminal program would be, since a single byte of line noise
can destroy an entire page, and possibly future pages. When
you are online and you see line noise, you generally hit
Ctrl-L or do something to clear the screen.
"PortalX occasionally gets 'stuck' when uploading a message".
This happens because sometimes during the end of a Zmodem
transfer, Telenet sends a string like "dte originated" right
in the middle of the message that Zmodem is sending saying
that the transfer has completed. This problem only seems
to happen while uploading, and generally just aborting the
session and trying again will fix it.
"PortalX is stuck, and the Online Status window says 'Unknown Command'".
This usually means you have asked PortalX to do something that
it cannot. One example would be asking to write a message into
a moderated Usenet newsgroup - you cannot do this, and PortalX
doesn't know that. If this happens, find the file in the Send
directory that is causing the problem (the Online Status window
tells you which file it is processing) and delete it.
"PortalX terminates the session as soon as it gets to Determining
Page Size".
This means PortalX doesn't understand the Portal top menu.
The most common causes are your having changed the dividing
string (normally "-----"), the Command: prompt, or your
dialing direct or calling in through Internet.
"What is the occasional 'dte originated' message in the modem status
window during a file transfer?"
I don't know why it is there, or quite what it means. It is
a Tymnet (or possibly Telenet) message, and you can usually
ignore it. Very rarely it will show up right in the middle of
a Zmodem file transfer termination, and the transfer will
not end correctly - in this case, just end the session and
call back.