RonCam

I worked-around one problem by installing Windows' native driver for ATI Radeon-compatible cards, then changing that to the bwc driver, before rebooting. Now the models box was populated with the 5000 series, and I selected the right one. I could see the bwc driver files being installed. But the unpleasant surprise came on reboot, as it proceeded only to the point when Windows began to load. I suspect something crashed windows as the screen blanked momentarily and then the boot started again. So, back to the drawing board ... Is there anything that would be helpful to blackwingcat to work around this? P.S.: Going beyond my question, please let me know if you see anything wrong with the way I'm going about this, since ... many others are reporting success in running their 5000-series boards under Win2K. Am I doint anything different??

Hi blackwingcat, hope you are still watiching the thread. I have not seen this question answered earlier. I have expanded your driver file ati5k2k1.zip, hoping to run an ASUS EAH5450 SILENT PCIE2. I first followed instructions from elsewhere on the 'net to completely clean my system of the old (Sapphire Radeon X300) ATI driver/software remnants. My system is Windows 2000 Professional SP4+. When following your directions to install your modified driver, while in the Upgrade Device Driver Wizard, I am seeing an extra screen not mentioned, causing a problem: Select the manufacturer and model of your hardware ... followed by an empty box titled 'Models:' Seems the user is supposed to select an entry shown inside this box and since a selection from an empty box is not possible, the 'Next' button is non-functional. So I can't get past this to complete the driver installation. There is a 'Have Disk' button here, as well, but if I enter the same information as you previously told us to do, that is accepted, but it loops back to this same screen, from which there is no exit. What can I do to complete the installation of your driver? I feel I am so close, yet so far ... Thanks for your driver and for your help.

I see. You are saying, Gears is specific to each browser, and the installer you have developed for Windows 2000 is for the Gears/Chrome combination, not for the others. So, you are saying, not to bother with Gears for my exising MSIE6+ installation, but instead install Gears/Chrome (and get a second, but newer, browser at the same time). I think I have understood correctly? I will work on your Gears/Chrome/for Win2K installation as my next project. At the moment I am working with the developer of Sandboxie (Ronen Tzur) to get one small bug, that appeared under Windows 2000, out of the most recent beta build. IMO, Windows 2000 running under Sandboxie has better protection and security on the Internet, than does Vista. Then, when all is running well, I will turn to getting Gears. Thanks so much for sharing your efforts for others who appreciate, and want to continue with Windows 2000!! RonCam

Thanks very much, win2000, for your reply! To make sure I understood accurately, here are my questions and your replies, with my understanding added in square brackets, where needed: No, I didn't install it yet, I was waiting for your advice and to find out if it is possible. B) Reply: I see. You are saying if Gears is to work with Windows 2000, it must be only through the Gears/Chrome installation. You are saying, even though IE6+ is already on my system, just installing Gears, alone, will not work under Windows 2000. I was confused because the Gears download page appears (am I mistaken in this?) to be offering Gears as a separate installation. I have it open now in another window, using the Google Japanese -> English translation. I think before I do anything, given the quality of the translation, I should first post my understanding of what you are saying here, for your approval!

Google Gears?? I know this is now included with Chrome, but isn't it still possible to install it separately? Can't find any reference to someone who has done this on Windows 2000 Pro. Any advice on this point? Thanks, RonCam .