Leaderboard

Nope, I am having no problems. Time is 6:55 PM here. This is on a Windows Me VM on MS Virtual PC 2k4 on a win2k host:

Good to know, its working fine now..

Oh, yeah, I did install those! That's what got me from the "This page cannot load" screen to the Windows Update error. It was late, and I forgot to mention that. But, it's all moot now, as somehow I managed to get it to work! Apparently I was almost there. I needed only to install a couple of cumulative IE6 updates (I forget the KB numbers; the laptop I had the VM on died this morning, so I have to wait until I've copied everything off its drive to check what they were), and then everything just worked! A .NET update (1.1 SP1) complained and wouldn't install at first, but I retried it and it installed fine the second time. Now I have to find the post-EOL updates and install those! c

For anyone that's using AeroGlass with Chrome Browser (v76+) configured to startup with windows and run in the background, you've probably noticed that the required command line switch --disable-windows10-custom-titlebar is NOT remembered at startup time. Unfortunately, if you manually edit the ChromeAutoLaunch registry key, it will get overwritten every time Chrome exits. To address this issue, I created a simple AutoHotkey script that is run 'on login' as a Scheduled Task that automatically adds the necessary startup switch to the required 'ChromeAutoLaunch...' registry key (which has a custom suffix for different users). I also added a 2nd useful switch --save-page-as-mhtml as well. The compiled script, source code, task scheduler (xml) import file, and installation instructions can all be found at this Link. Cheers, -JT

http://letmegooglethat.com/?q=aero+glass+machine+id

It seems that this is a problem on BigMuscle's host website (it may be blocking access for iP adresses on some locations). If we could contact him, he would fix/explain this for us...

1:33AM here, 10:33PM in Redmond, I may have just played my last checkers game... it all depends WHEN on 31 july MS shuts it down, if i get to play again when i wake up. ...if they even remember to.

I just saw the edits to your posts and although I just paved over my sandbox, @tomasz86 has tested some of the post-258.96 drivers already: 261.19 works perfectly for me, but it seems that 306.81 may do fine with a couple files copied over from an older release. 306.81 supports up to the GeForce GTX 650 Ti/GTX 680! edit: then I read some more and heard about potential instability and reliance on unofficial updates. Nothing is for sure unless someone with a 500/600 series GeForce + > 4 GB RAM comes forward

I checked the code, they just changed the command line parameter for disabling custom title bar. The correct parameter in newer Chromium browsers is -disable-windows10-custom-titlebar The decision is made in chrome/browser/win/titlebar_config.cc.