So far as I can tell, from watching the message traffic going by, your only option is to upgrade to another OS, or downgrade to XP32.
I've successfully used Vista 64 and Windows 7 64. I believe Linux would also be an option. You may be able to run a VMWare virtual machine and do it. I've succeeded at that for another hardware product (non-Android, non- phone, but also running an embedded Java environment), who initially did not supply Vista 64-bit drivers. The VMWare USB support is surprisingly good and robust. (Surprising, since getting the interaction with the host OS right seems rather difficult to me, but it's flawlessly handled everything I've thrown at it -- disk drives, built-in SD card slots, mobile devices...). So if changing your OS (or using a different computer with a different OS) isn't a good option, it may well be worth your spending the time and effort to try it. If a VM works for you, and you don't want to pay for a Windows license for your VM -- once you've confirmed that it works in the VM, you could try it in a Linux VM. If you get it working in a VM, it'd be great if you came back here and posted your success. I've seen quite a few instances of this question -- in fact, more instances of this question than I've seen copies of XP 64 in the wild outside server rooms. Good luck! On May 25, 8:20 am, HLL <[email protected]> wrote: > Hay everyone, > > I Want to start developing for android and for some reason whatever I > do I can not make ADB show up my Nexus One. > > Both on and off in development mode > Both SD Mount and without SD Mount > Both With usb tethering on and off > > for all "adb devices"(windows XP64bit) show no device (service started > successfully, device recognized in Device Manager correctly). > > Tried reinstalling drivers, tried uninstalling drivers > completely(using 3rd party software) and reinstalling, tried different > versions of the usb driver (up to the one before the last - that came > with the 2.1 sdk) > NOTHING... > It seems online that this issue reoccurs on different devices, but all > of them seemed to solve with one of the above solutions, Which none > worked for me. > > It does not look like a hardware problem, because EVERYTHING else that > is USB'ed works correctly. > > Any non-already tried idea would be appreciated. > > Regards, > Hillel -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
