RWF07 wrote:
> HAve you tried recalibrating prior to the race? Another thought-- If you have
> a joystick driver like the presision pro you may try "unload/suspend" it from
> the tray down in the lower right corner. Hope this helps
> R. Faust
> aka Xducer
RF, i use a t-2 have deleted the cal file, aligned the t2 from nro, n2
and w-95 a bunch of times no help. enclosed is a e-mail i have sent to
TEN tech support 5 times now over the last 2 weeks. They have yet to
respond. So much for 24 hour response maybe they meant to say 24 days ?
T first i thought it was a latency problem but now i doubt it. never saw
the problem prior to the latest patch. ne help would be greatly
appreciated.
Subject:
RE: NASCAR2 on ten
Date:
Thu, 15 Jan 1998 10:57:41 -0800
From:
Hardware <[email hidden]>
To:
"'[email hidden]'" <[email hidden]>
Hello,
I imagine the TEN support staff is very busy at this time of year,
and I'm sorry you haven't heard back from them. Unfortunately, we
aren't involved with the technical aspects of their network enough to be
able to answer your questions. Please let us know if you need anything
else.
Steve/Tech Support
Quoted text (200 lines)
> -----Original Message-----
> From: Paul D. Yuknis [SMTP:[email hidden]]
> Sent: Wednesday, January 14, 1998 10:00 PM
> To: [email hidden]
> Subject: NASCAR2 on ten
> I have sent this e-mail to ten technical support several times over
> the
> last week, they have yet to respond. U folks have n e ideas ?
> Subject:
> NROS e mail followup (further info)
> Date:
> Mon, 12 Jan 1998 22:06:25 -0800
> From:
> "Paul D. Yuknis" <[email hidden]>
> To:
> [email hidden]
> CC:
> [email hidden]
> Here is some further info on my previous e-mail with more questions
> FOR NROS:
> 1. what ping value does mr. bandwidth require for forget it, good, and
> excellent ?
> 2. what criteria does reliability use ?
> 3. Iv'e seen these good ping values generate only a score of 14% in
> speed with mr. bandwidth, is the abyys server being overtaxed ?
> Here is a typical connection evaluation to abyss.ten.net from my
> system.
> packet size=56
> max ping = 339
> min ping = 215
> avg ping = 237
> in 99 tries, values do not change significantly no matter how many
> times
> i run it.
> Iv'e also ran a long histogram with the 4-net utility which samples
> much
> quicker than mr bandwidth and i had no spikes which i observe with the
> latency history provided on the TEN NROS client.
> previous email follows data
> 1) 56 bytes received from grizzly.ten.net. time = 218ms
> 2) 56 bytes received from grizzly.ten.net. time = 217ms
> 3) 56 bytes received from grizzly.ten.net. time = 231ms
> 4) 56 bytes received from grizzly.ten.net. time = 226ms
> 5) 56 bytes received from grizzly.ten.net. time = 230ms
> 6) 56 bytes received from grizzly.ten.net. time = 226ms
> 7) 56 bytes received from grizzly.ten.net. time = 231ms
> 8) 56 bytes received from grizzly.ten.net. time = 238ms
> 9) 56 bytes received from grizzly.ten.net. time = 223ms
> 10) 56 bytes received from grizzly.ten.net. time = 229ms
> 11) 56 bytes received from grizzly.ten.net. time = 238ms
> 12) 56 bytes received from grizzly.ten.net. time = 223ms
> 13) 56 bytes received from grizzly.ten.net. time = 228ms
> 14) 56 bytes received from grizzly.ten.net. time = 238ms
> 15) 56 bytes received from grizzly.ten.net. time = 224ms
> 16) 56 bytes received from grizzly.ten.net. time = 238ms
> 17) 56 bytes received from grizzly.ten.net. time = 223ms
> 18) 56 bytes received from grizzly.ten.net. time = 218ms
> 19) 56 bytes received from grizzly.ten.net. time = 219ms
> 20) 56 bytes received from grizzly.ten.net. time = 226ms
> 21) 56 bytes received from grizzly.ten.net. time = 227ms
> 22) 56 bytes received from grizzly.ten.net. time = 224ms
> 23) 56 bytes received from grizzly.ten.net. time = 219ms
> 24) 56 bytes received from grizzly.ten.net. time = 223ms
> 25) 56 bytes received from grizzly.ten.net. time = 238ms
> 26) 56 bytes received from grizzly.ten.net. time = 215ms
> 27) 56 bytes received from grizzly.ten.net. time = 218ms
> 28) 56 bytes received from grizzly.ten.net. time = 224ms
> 29) 56 bytes received from grizzly.ten.net. time = 228ms
> 30) 56 bytes received from grizzly.ten.net. time = 228ms
> 31) 56 bytes received from grizzly.ten.net. time = 224ms
> 32) 56 bytes received from grizzly.ten.net. time = 228ms
> 33) 56 bytes received from grizzly.ten.net. time = 223ms
> 34) 56 bytes received from grizzly.ten.net. time = 264ms
> 35) 56 bytes received from grizzly.ten.net. time = 222ms
> 36) 56 bytes received from grizzly.ten.net. time = 222ms
> 37) 56 bytes received from grizzly.ten.net. time = 224ms
> 38) 56 bytes received from grizzly.ten.net. time = 224ms
> 39) 56 bytes received from grizzly.ten.net. time = 223ms
> 40) 56 bytes received from grizzly.ten.net. time = 227ms
> 41) 56 bytes received from grizzly.ten.net. time = 223ms
> 42) 56 bytes received from grizzly.ten.net. time = 228ms
> 43) 56 bytes received from grizzly.ten.net. time = 223ms
> 44) 56 bytes received from grizzly.ten.net. time = 307ms
> 45) 56 bytes received from grizzly.ten.net. time = 218ms
> 46) 56 bytes received from grizzly.ten.net. time = 219ms
> 47) 56 bytes received from grizzly.ten.net. time = 293ms
> 48) 56 bytes received from grizzly.ten.net. time = 219ms
> 49) 56 bytes received from grizzly.ten.net. time = 224ms
> 50) 56 bytes received from grizzly.ten.net. time = 223ms
> 51) 56 bytes received from grizzly.ten.net. time = 228ms
> 52) 56 bytes received from grizzly.ten.net. time = 224ms
> 53) 56 bytes received from grizzly.ten.net. time = 226ms
> 54) 56 bytes received from grizzly.ten.net. time = 220ms
> 55) 56 bytes received from grizzly.ten.net. time = 219ms
> 56) 56 bytes received from grizzly.ten.net. time = 288ms
> 57) 56 bytes received from grizzly.ten.net. time = 233ms
> 58) 56 bytes received from grizzly.ten.net. time = 229ms
> 59) 56 bytes received from grizzly.ten.net. time = 238ms
> 60) 56 bytes received from grizzly.ten.net. time = 229ms
> 61) 56 bytes received from grizzly.ten.net. time = 224ms
> 62) 56 bytes received from grizzly.ten.net. time = 239ms
> 63) 56 bytes received from grizzly.ten.net. time = 228ms
> 64) 56 bytes received from grizzly.ten.net. time = 224ms
> 65) 56 bytes received from grizzly.ten.net. time = 264ms
> 66) 56 bytes received from grizzly.ten.net. time = 228ms
> 67) 56 bytes received from grizzly.ten.net. time = 218ms
> 68) 56 bytes received from grizzly.ten.net. time = 228ms
> 69) 56 bytes received from grizzly.ten.net. time = 224ms
> 70) 56 bytes received from grizzly.ten.net. time = 228ms
> 71) 56 bytes received from grizzly.ten.net. time = 223ms
> 72) 56 bytes received from grizzly.ten.net. time = 228ms
> 73) 56 bytes received from grizzly.ten.net. time = 223ms
> 74) 56 bytes received from grizzly.ten.net. time = 339ms
> 75) 56 bytes received from grizzly.ten.net. time = 238ms
> 76) 56 bytes received from grizzly.ten.net. time = 228ms
> 77) 56 bytes received from grizzly.ten.net. time = 252ms
> 78) 56 bytes received from grizzly.ten.net. time = 303ms
> 79) 56 bytes received from grizzly.ten.net. time = 298ms
> 80) 56 bytes received from grizzly.ten.net. time = 278ms
> 81) 56 bytes received from grizzly.ten.net. time = 221ms
> 82) 56 bytes received from grizzly.ten.net. time = 226ms
> 83) 56 bytes received from grizzly.ten.net. time = 224ms
> 84) 56 bytes received from grizzly.ten.net. time = 219ms
> 85) 56 bytes received from grizzly.ten.net. time = 228ms
> 86) 56 bytes received from grizzly.ten.net. time = 228ms
> 87) 56 bytes received from grizzly.ten.net. time = 228ms
> 88) 56 bytes received from grizzly.ten.net. time = 223ms
> 89) 56 bytes received from grizzly.ten.net. time = 223ms
> 90) 56 bytes received from grizzly.ten.net. time = 228ms
> 91) 56 bytes received from grizzly.ten.net. time = 223ms
> 92) 56 bytes received from grizzly.ten.net. time = 229ms
> 93) 56 bytes received from grizzly.ten.net. time = 222ms
> 94) 56 bytes received from grizzly.ten.net. time = 218ms
> 95) 56 bytes received from grizzly.ten.net. time = 234ms
> 96) 56 bytes received from grizzly.ten.net. time = 238ms
> 97) 56 bytes received from grizzly.ten.net. time = 228ms
> 98) 56 bytes received from grizzly.ten.net. time = 235ms
> 99) 56 bytes received from grizzly.ten.net. time = 219ms
> here is the previous email i sent for your reference:
> Subject:
> NROS (second try)
> Date:
> Mon, 12 Jan 1998 21:00:57 -0800
> From:
> "Paul D. Yuknis" <[email hidden]>
> To:
> [email hidden]
> CC:
> [email hidden]
> SECOND ATTEMPT TO TECH SUPPORT FIRST ONE HAD NO REPLY AFTER 5 DAYS
> username: p_yuknis
> intel p-166 mmx
> 32 meg ram
> 33.6 modem
> w-95 osr2
> thrustmaster T-2 wheel
> NASCAR2 (NROS)
> although i have a reliable, and stable ISP. and continuous pings
> (using
> 4-net latency history function) under 300. I see a lag of my controls.
> i.e. i hit the brake, and the car does not respond for 2 seconds. I
> have
> run NASCAR over IP with greater than 500msec reliably. This problem
> happens to me on the tens dialup service as well. In fact according to
> your "mr bandwidth" my ISP connection is better than your own dialup
> ???
> hurting 4 bandwidth r we ? This is a "wierd" sort of lag. The graphics
> r
> verry smooth only the controls r screwed up. I have realigned my T2
> wheel online, offline, and in w95 with no help.
> THE SYSTEM WORKS PERFECT OFFLINE
> I NEVER SAW THIS BEFORE THE PATCH
> I am a network administrator and programmer, please don't blame my ISP
> and forget about me. The ISP is at
