On 09-Okt-00, Fred Wright wrote:
> I had another thought on what might be happening here. I believe
> MiamiInit has some stuff to warn you about high baud rates on the
> native serial, especially when combined with high-bandwitdh native
> displays, due to the overrun problems. It's possible that it limits
> the baud rates it tries on serial.device based on concerns about
> overruns, while assuming that for third-party cards it can use
> higher rates providede that the driver accepts them. If the GVP
> setup (possibly including the modem itself) has a problem with high
> baud rates but still doesn't complain about them, then it might be
> that the reason the redirection case works better is that MiamiInit
> thinks it's dealing with the native serial and is more conservative
> about its baud rate choices.
That is a possible explanation. I can�t tell from coders view or what
MiamiInit is doing intern.
> 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
FILENAME="SYS:t/serlog.log", BUFFERSIZE=2048
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
c) in redirection-mode with GVPIOcontrol but using serial.device
MiamiInit dials out to my ISP.
Seems MiamiInit won�t do it with the serlog.device?
d) another test with other slprefs: and the serlog.device in
redirection-mode:
Current preferences are:
DEVICE="serial.device", UNIT=0, PRIORITY=0
FILENAME="SYS:t/serlog.log", BUFFERSIZE=2048
CMD_INVALID ON
CMD_RESET ON
CMD_READ ON
CMD_WRITE ON
CMD_UPDATE ON
CMD_CLEAR ON
CMD_STOP ON
CMD_START ON
CMD_FLUSH ON
SDCMD_QUERY OFF
SDCMD_BREAK ON
SDCMD_SETPARAMS ON
NOAPPEND
NOTIME
Nothing happens, serlog.log has zero bytes, errorcode=1 in MiamiInit.
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.
----- NEW SESSION -----
CMD_CLEAR: OK
SDCMD_SETPARAMS: OK
CtlChar: 0x11130000
RBufLen: 16384 byte
ExtFlags: 0x00000000
Baud: 115200
BrkTime: 250000�s
TermArray: 00 00 00 00 00 00 00 00
ReadLen: 8 bpc
WriteLen: 8 bpc
StopBits: 1
SerFlags: 0x00000080
CMD_WRITE: OK, 1 byte
CMD_WRITE: OK, 1 byte
CMD_WRITE: OK, 1 byte
CMD_READ: OK, 1 byte
[...]
CMD_READ: aborted, 0 byte
This is repeated four times in the log. But the errorcode of MiamiInit
is the same =1.
It seems when dialing with Miami(DX), serlog takes the speedrate from
the Hardware-settings. MiamiInit seems to try to dial always with
115200bps. All this in redirection-mode.
A last atempt without redirection-mode with MiamiInit using
gvpser.device was not succesful, it was in redirection-mode using
serial.device.
The G-Force sometimes really makes problems when I change some
settings like this or add or remove a device and reboot the machine. i
just want boot sometimes ;) ... sigh ... I love this Amiga....
Sorry if I was wasting bandwidth!
Regards
--
Andreas Meyer
--
http://home.wtal.de/MeineHomepage/
--
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
