DSVD & N2 - Help!

I can't seem to get Nascar 2 to connect at a baud rate greater than 19200. In Nascar 1 I used 38400 with my Hayes DSVD Accura modem and everything worked great, voice and data. Now with nascar 2 at 19200 the latency is something like .24 and the field goes in and out on the calling machine making it undrivable. In the modems.cfg file it states you can enter baud rates to 38400, which I have, but back inside N2 it always only shows 19200 as the fastest rate. Someone please help, I purchased the DSVD modem strictly for Nascar Racing, and now that N2 is out I'm unable to race via modem and DSVD. thanks, barry PS: I tried Nascar 1 at 19200, and the latency is the same I'm experiencing in N2.

Quoted text (23 lines)

>I can't seem to get Nascar 2 to connect at a baud rate greater >than 19200. In Nascar 1 I used 38400 with my Hayes DSVD Accura >modem and everything worked great, voice and data. Now with nascar >2 at 19200 the latency is something like .24 and the field goes in >and out on the calling machine making it undrivable. >In the modems.cfg file it states you can enter baud rates to >38400, which I have, but back inside N2 it always only shows >19200 as the fastest rate. >Someone please help, I purchased the DSVD modem strictly for >Nascar Racing, and now that N2 is out I'm unable to race via >modem and DSVD. >thanks, >barry >PS: I tried Nascar 1 at 19200, and the latency is the same I'm >experiencing in N2.

What's your initialization string look like? I use the USR DSVD vi modem, and the following string works well with it: AT&F1^M~~~&K0-SSE=1^M We get latencies of around .16 to .18 using DSVD, around .11 or so without DSVD. Dave (davids) Sparks Late Night League http://www.sequoia-dev.com/Hawaii/latenite.html

Quoted text (9 lines)

>I can't seem to get Nascar 2 to connect at a baud rate greater >than 19200. In Nascar 1 I used 38400 with my Hayes DSVD Accura >modem and everything worked great, voice and data. Now with nascar >2 at 19200 the latency is something like .24 and the field goes in >and out on the calling machine making it undrivable. >In the modems.cfg file it states you can enter baud rates to >38400, which I have, but back inside N2 it always only shows >19200 as the fastest rate.

Barry - we set the max baud rate in the configuration screens to 19200 because a lot of machines have problems trying to establish connections *at all* at higher baud rates. We were getting a lot of reports from beta testing of machines that couldn't make connections, but it turned out that when they were limited to 19200 they could connect fine. I'm pretty sure the workaround you described - manually editing your .cfg file to specify a higher baud rate - will work, if you feel you get better performance that way. I also suspect you could figure out a modem init string which will give you a better connection and lower latency with a 19.2K or 9600 serial port setting, if you work with the modem a bit. If you figure out a good combo for you Hayes DSVD modem, could you post it here so other users can benifit from your experience? Thanx... Charlie Heath Papyrus

Don't know about the Hayes modem, but this works for US Robotics Sportster DSVD's: MODEM U.S. Robotics Sportster DSVD INIT AT&F1^M~~~AT&K0-SSE=1^M PREFIX ATDT SUFFIX ^M BAUD 38400 Just cut and paste into your MODEMS.CFG file. Got a 31.2K connect with a .13 latency. USR requires error correction enabled to do DSVD Charlie

Quoted text (34 lines)

>>I can't seem to get Nascar 2 to connect at a baud rate greater >>than 19200. In Nascar 1 I used 38400 with my Hayes DSVD Accura >>modem and everything worked great, voice and data. Now with nascar >>2 at 19200 the latency is something like .24 and the field goes in >>and out on the calling machine making it undrivable. >>In the modems.cfg file it states you can enter baud rates to >>38400, which I have, but back inside N2 it always only shows >>19200 as the fastest rate. >Barry - we set the max baud rate in the configuration screens to 19200 because >a lot of machines have problems trying to establish connections *at all* at >higher >baud rates. We were getting a lot of reports from beta testing of machines >that couldn't >make connections, but it turned out that when they were limited to 19200 >they could >connect fine. >I'm pretty sure the workaround you described - manually editing your .cfg >file to >specify a higher baud rate - will work, if you feel you get better >performance that >way. I also suspect you could figure out a modem init string which will >give you a >better connection and lower latency with a 19.2K or 9600 serial port >setting, if you >work with the modem a bit. If you figure out a good combo for you Hayes >DSVD modem, >could you post it here so other users can benifit from your experience? >Thanx... >Charlie Heath >Papyrus