jmazzy

Ksarul and I confirmed the fit of the sample TI chassis screws I received. They do fit perfectly so I finally got around to ordering a bunch last month. To make these screws easier for enthusiasts to find and access in the future, I've shipped most of them off to arcadeshopper, and he has made them available here at arcadeshopper.com.

Despite the brief window I had to participate, I enjoyed meeting you and the others, as well as learning about other people's personal history with the TI and the projects they have in the works. Thanks again for organizing.

I live on the northside of Chicago, just a couple of miles south of Evanston. Looking out the window now, and it seems like very meager snow by Chicago standards, although even a little snow can create transportation delays. The ground is warm enough that it probably won't stick around for long. Local hourly forecast shows it tapering off around 5-6PM Central. The good news is tomorrow's local forecast seems precipitation-free and is sunnier and well-above freezing temps after 10AM. Hope schedules move along without too much delay for everyone. Travel safely.

Thank you for all of your organizing and coordinating around this event. I've been tied-up these past couple of months and absent from posting but have been watching the event updates here. I hope to get in a little time there on Friday, if nothing else to put faces with names. I'd also like to pitch in on a few things, including equipment and transportation. I'll private msg you and couple others about what I had in mind. Looking forward to it!

No worries. Thanks for the update.

I've been curious, too: any updates on PEB-based TIPI's?

Looks sharp! Kudos.

Looking forward to it, also.

👍 Thanks much!

Assuming the originally scheduled time hasn't changed, it's 9PM Eastern. See you all then.

So I figured out the issue I was having logging in to MYTI99.COM and found a workaround. Looking forward to tomorrow night's chat.

No worries. I tried most of the pages listed under "Sample Web Sites". They all work fine, even the chat application. This gave me the idea to test several MYTI99.COM pages similarly, observing the various URL's carefully. In the process, I was able to identify the exact URL/path to the chat function, and so long as my login credentials are appended to it, it works just fine: www.myti99.com/gc2.pl?u=screen name&p=PIN In a nutshell, it looks like the host name resolution via your server is fine (thank you again for the fix), although something still isn't quite right on the MYTI99.COM server specifically related to the account login page ( www.myti99.com/account.pl?a=showLoginForm&rurl=www.myti99.com&u=screen name&p=PIN ) But it's easy enough to circumvent that issue by simply typing in the exact chat URL with login credentials, as I noted above. So I'm all set. 👍

Although the name resolution appears to work, I receive an error message ("HTTP error when retrieving page") when I try that URL:

Thanks for the tip. I double-checked: my UDS-10 is currently set for Auto increment source port ON. So I guess that's not the issue. I should mention, too, that my UDS-10 and network equipment haven't changed at all since the time everything was working just fine back in May. So it seems likely to be either a residual issue on Stuart's server (which does the host name lookup, as I understand it) or something on the MYTI99.COM server.

Thanks, Stuart. I've just tested it again. There's still an issue, although it looks like we're making progress. Here's what I'm seeing: I start the browser and type-in the URL 'www.myti99.com' - the name resolution works: I get to the MYTI99.com welcome page. Then I click 'Log In', and I get to the login page. I type-in my screen name and password, then click 'Log In', and then receive the msg 'Login Successful'. All good. But then when I click 'Continue', the banner at the bottom reads 'Resolving IP address...' for several seconds and then fails with 'Error - host name not recognised'. (Screen shot below.) I do remember reading in an earlier post that something was changed to prevent the URL from revealing the user's screen name and PIN. I suspect whatever problem we're seeing here may be a side-effect of that change. Any thoughts? Or is this something for Corey?