Saturday, October 27, 2001, 9:10:28 PM, Allie wrote: ACM> It's reproducible here on my machine. Funny that I use the same ACM> monitor as Yuki Taga. ;-))
A decent monitor for the bucks, but the next one will definitely be flat panel. Here in Tokyo the prices for the larger sizes are starting to fall to within reason. I actually ended up with this because I had a PS 790 originally, which I had shipped from a US distributor. Wanted the PS 790 because it has a shorter 'footprint' than any other 19" monitor -- being only as deep as a standard 15", which puts the screen back about 3 inches farther from my eyes, and is quite comfortable. (The things we have to worry about in tiny Japanese homes.) ^_- But the red gun died about 30 months after I bought it (inside the warranty envelope, thank goodness), and since VS Japan didn't ever sell PS 790s in Japan (why, I don't know because they had a definite sales point for Japan, as I mentioned), VS Japan said they would ship me a PF 790 as a replacement. We ended up volleying 3 monitors back and forth (at their cost) before I got one I would accept. Whole experience has kind of soured me on VS, although I did (finally) end up with a decent monitor. (They don't send new, of course, as replacements, but reconditioned, and some of these have better specs than others.) LG>> So when TB! has finished its shutdown process, Windows can LG>> handle all the things that happened while it was busy. And one LG>> of this unhandled tasks is to display that "Close" tool tip. ACM> Watching how things occur, I tend to agree with your analysis. Agree. This is the best analysis of the problem I've seen. Glad to know it's not really a bug in TB. And figuring out my dialer problem in XP was easy. In Win2k I had called my connection 'AT&T Setsuzoku Service', and in XP I had called it ATT Setsuzoku Service. Making the edit in the XP registry key made the whole switch over really seamless. Not that it would have mattered too much anyway, because once I connect, I stay connected. So only the initial connect would have been affected, and only if I used TB to initiate it. About XP and PGP, however . . . (cause I know there is interest about that combo in this group), you may find some things don't work so well, especially any apps that want to use older versions of PGP, such as 2.6.x. For example, JBN2 is not going to run, ever, in XP. Apparently Quicksilver will, but if you are used to JBN, there is going to be a learning curve. I'm a bit surprised that JBN won't work in XP, as it works fine in Win2k, which has (or so I thought) the same restrictions on applications directly accessing the hardware layer that XP has. In fact, I would have thought since Win2k was a child of NT (really NT 5.0), and XP being a marriage of Win9x and NT, that, if anything, XP's restrictiveness in this area would be slightly less than Win2k's, because MS would still want to bring along a legacy app or two. But apparently this is not the case. Apps like JBN2 were really written for Win9x, and just happen to work in Win2k. But they apparently are never going to work in XP. So there are some surprises out there. PGP tray (6.5.8) seems to work, but on boot and on use there are 'warning' messages from XP. I refuse to use any PGP edition where source is not available for peer review. But I stray from the subject of TB! (^_-) Yuki ^_^ -- ________________________________________________________ Archives : http://tbudl.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] TBTech List: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Latest Vers: 1.53d FAQ : http://faq.thebat.dutaint.com
