> Yeah, that was the first thing I tried (kill-server), but adb will get > started again automatically, so that doesn't help. I'd also tried > deleting adb.exe from tools\ in the hope it would'nt get started, but > then I can't even bring up the SDK/AVD manager to do the update. Also, > blindfold: deleting the platforms\android-1.6 is really not a solution > because you're just avoiding dealing with the 1.6 update. Bottom line, > I don't believe there's still a solution to updating from 1.6 r1 to > 1.6 r2. This is on Vista 64 bit. Anyone?
Here's a procedure I used for grabbing the previous ADT update on Vista 32-bit, where $SDK is the directory you installed the SDK into: 1. Copied $SDK\tools to $SDK\snicklefritz 2. Changed the relevant environment variables (e.g., PATH) to point to $SDK\snicklefritz instead of $SDK\tools 3. Started up the SDK/AVD Manager from the $SDK\snicklefritz copy 4. Ran the update 5. Changed the environment variables back to point to $SDK\tools 6. After confirming the new $SDK\tools seemed happy, deleted $SDK\snicklefritz That was for a slightly different problem than the one you're reporting, so I'm not sure if this will actually help you, but I just like writing "snicklefritz". ;-) -- Mark Murphy (a Commons Guy) http://commonsware.com Android App Developer Books: http://commonsware.com/books.html -- 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
