Ananan :
It was very odd (my old keyboard is just a generic Dell from an older system).
I actually forgot to mention that after I plugged it in for the first time my mouse stopped working. So I had to reboot. After a few tries with no success to get the mouse working I went back to my old keyboard and the mouse worked again (after a reboot).
So I unplugged my old keyboard while the PC was on and plugged in the Eclipse; the driver installation started and I was finally able to click on it to continue.
It couldn't find any drivers for the Saitek. Seemed weird but by this time I was pretty fed up and plugged my old keyboard back in. It looked for drivers for the old keyboard and couldn't find any either. I tried everything - my version of XP apparently no longer had any sort keyboard driver in its driver database. I don't know what happened.
So I finally ended up doing a system restore to get my drivers back. I'm not plugging that damn keyboard in again. I'm going to go ahead and exchange it for the same model and try again.
One more note - the button that changes the backlight color didn't work. Could be another sign this particular one is defective.
firstly, I've used hundreds of keyboards... I'm a computer tech, and for some reason, people feel absolutely compelled to bring in their keyboards and mice when we do repairs...
I've personally used Logitech Keyboards in my home on my 4 machines for about 4 years (gaming/file server, arcade/console emulator, personal gaming machine, and at-home repair station for repairing friend's computers)...
I have to tell you that the simple logitech keyboards and mice are awesome! they work like a charm... but the more complicated the keyboards get, the worse it becomes... I personally used the LX300 wireless keyboard/mouse combination (mouse was replaced with an MX1000 because the receivers worked off the same signal)... with the newer logitech drivers, half of their products aren't even supported... it's ridiculous because I had a top of the line product that just simply wouldn't work to full functionality (MX1000 mouse was no longer being detected... it was after a few years of usage, but it was all driver issues)... I could take the mouse, install the drivers onto a new machine, or a machine that didn't previously have the drivers, and it would work fine... once it auto-updated drivers, the mouse was no longer detected in SetPoint...
One day, I finally got fed up... I need all the extra mouse buttons for gaming (11 buttons on that mouse, each one had a purpose in UT2K4 and Age of Series)... I went out and contemplated the G15, or the Saitek II (I like gaming in the dark, too)... I came home and did tons of research and found that both were about equal in terms of performance, reviews, etc... my final decision came when i started researching new MICE... logitech G7, or Microsoft Habu (a Razor branded mouse)... the logitech G7 returned related results on bluetooth products, and then hthe researched turned bad... all the reviews for their bluetooth products were horrible (albeit the G7 and G15 aren't bluetooth)... but there were so many complaints about logitech's drivers breaking after a while that I decided to turn a cheek and try the eclipse II... it was a lot cheaper, and I liked the fact that it DIDN'T have the stupid logitech-proprietary "Function" keys (which become a big annoyance if you need to access one of the regular F-keys and don't know which mode you're in and you accidentally bring up MS Word and Excel at the same time while you're in the middle of a full-screen frag-fest...)
I've been using my Eclipse II keyboard for about 3 months now without a problem... I was surprised that there was no driver disk in the box, and actually considered returning it for one WITH a disk, until I read the manual and realized there was no disk provided... I plugged it in, it was recognized immediately, and I've never had a problem since...
My advice, return your eclipse II for one that's not defective, and live happily ever after... logitech drivers are horrid... that's my 2 cents