Download Easy Driver Windows Xp 32 Bit

#1

Howdy everyone!

Without further ado, I humbly nowadays my souvenir to the community (and the #nookcolor irc aqueduct

)

This collection of scripts will automagically install:

NookColor USB ADB Drivers
The necessary adb_usb.ini file for adb to recognize the NookColor
A stripped-down re-create of the Android SDK, with merely the requirements for adb.exe
adb.exe is added to your %PATH% variable.

Tested on Windows 7 32/64, Windows Vista 32, Windows XP SP2/SP3

Now I realize not everyone wants the exercise-all end-all script, then there’s two versions: i that contains the drivers AND a cut down Android SDK, or the version that only installs the ADB commuter and the proper adb_usb.ini file.

Instructions for utilize with combo pack (please read!):

Download the combo pack
With your NookColor unplugged from your PC, run the nookcolor-easyADB.exe file and let it to excerpt to c:\
Follow the on-screen instructions and await until yous run into “All done!”
Plug in your NookColor, tell Windows non to use Windows Update, and allow it search your computer for the proper drivers.

Once the package has finished installing, and the drivers are installed, you can just open up a command prompt window and blazon:
If yous see your device’s series number listed, yous’re good to get!

Instructions for the driver-only pack:

Download the driver-only pack
Extract it somewhere on your PC (may I recommend c:\android-sdk-windows\usb_driver ?)
Run install.exe in the extracted folder and follow the onscreen prompts.

For those of y’all that would like, the source of the driver installer is contained in both downloads as install.au3. Commuter installation is achieved using dpinst.exe from the Windows Driver Evolution Kit.

Besides, to avoid any confusion, I am also known every bit IOMonster on IRC.

Okay now for the good stuff…

DOWNLOADS:

Combo Pack (all in one!):
http://legacyschool.the states.to/nookdev/nookcolor-easyADB.exe
Driver simply pack:
http://legacyschool.us.to/nookdev/nook-usb-installer.rar

Update:
0.2 version has been released. Should fix CPU compages errors when installing. I have also changed the download protection on my server, you should exist able to use download managers now.. simply keep it to a sane number of concurrent downloads by IP.

Troubleshooting:

Make sure you’re rooted

Sounds dumb, but trust me, it’s happened.
Brand sure you haven’t used ADBWireless and forgotten to disable it

Guilty hither. I spent a skilful half hour trying to figure out why it didn’t work on one of my Nooks until I realized that I had left ADBWireless on.
Cheque device manager for a “Nook” device, yous may just have to do an “update driver” on it

Just like information technology says, check for any devices labeled “Nook” or “USB Blended Device” with a VID of 2080
Uninstall ALL Nook-related devices in device manager

Check device manager for any USB devices (ordinarily USB Composite Device or USB Mass Storage) with a VID of 2080 and PID of 0002, uninstall ’em and unplug/replug your Nook.

Please note that this is a VERY initial build. It may not work for you under some circumstances, but on the few machines I’ve tried it on, it seemed to work for me. If you encounter any weird bugs, please permit me know- I’d love to know then I can prepare it.

(Every bit a side note, I really need to standardize my nomenclature for my driver pack..)

Terminal edited:
Jan 16, 2011

#2

excellent work, thank you

#4

dainty job…I had helped test information technology in the irc channel for ya. I def think this will be great for the customs now we just need something to root and and superuser. Anyway good chore

#5

Offset post. Wanted to allow you lot know it worked on my windows7 x64 motorcar perfectly fine. so much easier than the long way.

#6

I’thousand using Windows vii 32bit. I unzipped the driver pack, clicked install.exe, then it said something about non having a correct version of windows and to get windows 7 x86 or x64, so a window popped upwards saying it successfully installed. Assuming that it didn’t and using my extreme deduction skills, I opened DPInst.exe and it did information technology’s affair and installed fine. Don’t know what happened with install.exe but it works now. Thank you!

#7

Foreign… do you lot remember the exact text of the error?

My install.exe runs DPInst.exe with the /q (quiet) switch, and then it shouldn’t take even given an error (fifty-fifty if there was a legit error message thrown past DPInst.exe).

Exercise you lot call up you had install.exe set for compatibility style? (cheque the properties for install.exe and perhaps DPInst.exe)

Thanks for the feedback! I certain hope this alleviates most of the headaches associated with installing ADB on Windows.

#8

The links are dead, can someone post them somewhere else?

#9

Fault when I install but information technology installs fine.

Information technology installed fine even though I got this message.

#x

EDIT::::

Ignore me – I missed uninstalling the USB device…

Worked perfectly THANK Yous!

Last edited:
Jan 13, 2011

#11

Information technology installed fine even though I got this bulletin.

Are you past chance running Windows vii 32-bit?

And as for the links beingness dead, try disabling your download manager. I come across people’southward download managers trying to do something like 20 concurrent downloads, and my server disallows that.

Terminal edited:
Jan 13, 2011

#12

Information technology installed fine even though I got this message.

Hullo, I did encounter this similar error every bit Rylynmila.
BTW, I am running WinXP SP2.

#xiii

Hm, that’south strange.. this worked on my XP SP2 machine, I wonder if information technology’southward possible that some machines study the compages differently..

I’ll brand a quick script that should let me figure this out easier. Information technology’s probably only an fault in my script’southward logic for deciding which version to apply.

#xiv

EDIT: Newly released version has been uploaded. This should fix the CPU architecture problems.

Ah, well, just found the culprit! My AutoIT script checks the architecture of the CPU itself, non the OS you’re running.

On the Windows XP machine I tried it on, the CPU itself is merely a 32-bit cpu (Athlon XP 3200+), therefore information technology reported it right.

I should take used @OSArch rather than @CPUArch in AutoIT. Oops.

I’ll make an updated version and release information technology later today.

Final edited:
Jan 13, 2011

#15

deceit seem to go this working on my 64 flake vista car.

installed fine, but adb devices shows cypher

#sixteen

cant seem to become this working on my 64 scrap vista automobile.

installed fine, but adb devices shows nada

When the installer came upwards, did it requite you any errors? Cheque the device managing director- you should have an entry for Android Phone -> Android Composite ADB Device.

If you do take that entry, endeavour running

                              adb kill-server then adb devices

and see what y’all get.

#17

When the installer came up, did it give you any errors? Bank check the device manager- y’all should have an entry for Android Telephone -> Android Composite ADB Device.

If you do have that entry, try running
                                adb impale-server and then adb devices
                              
and see what you go.

my married woman is using the NC right now, so i’ll give that a try when shes washed.

i have another question though. i already had adb installed for my phone, now i have information technology twice. tin can i combine the two?

#18

If y’all but want the ADB driver, only download the driver only pack.

If you had adb installed already, this will overwrite it if it’s installed to c:\android-sdk-windows.

#19

no luck with piece of cake adb

I take xp and followed the directions given in the commencement postal service in this thread for the combo pack. I at present have a lot of files in c:\android-sdk-windows\ but when I follow these directions (from Nook Devs) I practise not become the proper output…
“Start > Run > cmd > Enter
* cd\
* cd android-sdk-windows\platform-tools
* adb kill-server
* adb devices
If you get output that looks similar the following yous have succeeded:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

[YOUR NOOKCOLOR SN] device”

For my output, I get the first three lines just non the

[YOUR NOOKCOLOR SN] device

I looked in Device manager and do not meet anything virtually Android in there. I am obviously an android noob – can anyone aid me? Thank you

#20

Can’t wait to try this. Thanks!

I consider myself pretty proficient with electronics and computers simply I could never go ADB working on my Win7 64 PC no matter which set of instructions I followed. The benefit of this is that I’ve learned how to employ Root Explorer to accomplish a lot of things.

EDIT: This worked perfectly on my PC, although I wasn’t prompted to install any drivers. Guessing I had already done so previously trying to go this to piece of work. Thanks much!!

Last edited:
Jan 15, 2011

Download Easy Driver Windows Xp 32 Bit