On Wed, 11 Oct 2000, Andreas Meyer wrote:
> On 09-Okt-00, Fred Wright wrote:
>
> > If this is true it should exhibit the same problem running through
> > serlog, since the issue would be not that MiamiInit sees
> > "gvpser.device" but rather that it sees something which *isn't*
> > "serial.device" (or one of the known serial.device replacements).
>
> I made some tests with serlog and MiamiInit:
>
> a) in the section devices I was choosing "other" and then
> serlog.device unit 0. Serlog is using gvpser.device.
> In the modem-section I was choosing my WiseCom 56K and in a second
> atempt "other" and a speed with V.2/K56Flex/V.90
> In both cases I got an error-message from MiamiInit errorcode=1 and
> the serlog-logfile in sys:t was zero.
>
> b) now with redirection-mode enabled and serlog using serial.device.
> Same result as above! serlog-logfile is zero.
>
> Current preferences are:
> DEVICE="serial.device", UNIT=0, PRIORITY=0
It may not work properly with the priority set to 0. I usually use 2.
> FILENAME="SYS:t/serlog.log", BUFFERSIZE=2048
I usually log to a RAM: file (e.g. T:serlog.log) to avoid interposing disk
accesses. This may also avoid unexpected blocking.
> CMD_INVALID ON
> CMD_RESET OFF
> CMD_READ ON
> CMD_WRITE ON
> CMD_UPDATE OFF
> CMD_CLEAR OFF
> CMD_STOP ON
> CMD_START ON
> CMD_FLUSH OFF
> SDCMD_QUERY OFF
> SDCMD_BREAK ON
> SDCMD_SETPARAMS ON
> NOAPPEND
> NOTIME
I usually enable all commands, except it's sometimes necessary to exclude
SDCMD_QUERY (mainly just with things like Fusion that call it constantly).
> Don´t ask me what is going on... I just made another test with
> MiamiInit and serlog.device and now I got a serlog.log in sys:t.
[...]
> CMD_WRITE: OK, 1 byte
>
> CMD_WRITE: OK, 1 byte
>
> CMD_WRITE: OK, 1 byte
>
> CMD_READ: OK, 1 byte
I usually use the HEXDUMP option to see the actual characters.
Fred Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
