[ernie001]

Tablet is a 3 yo Nook converted to Android 4.2.2 by CyanogenMod.
Desktop is 8 yo Pentium running XP SP3. For a while the tablet was recognized as drive h: when connected to serial port and I could drag files to it.
Earlier this year several XP updates were installed and tablet upgraded to
Android ver 4.3.1 . Now the tablet is not recognized, no matter which serial port I use. No h: appears in Windows "My Computer" nor can it be found with the Command Prompt. The XP system is running Nortons Internet Security, but this was running previously when the tablet's h: was recognized. Now turning Nortons off makes no difference. My camera is recognized when plugged into the serial port. Any ideas about what I can do ?

[KCAndroid1]

Between the XP updates and the Android updates, it's possible that your driver is no longer the right one. Might try a search and an update to that. You may get more than one choice and the answer isn't always obvious. For example, with my Nexus 5 on Windows 8.1, two drivers appear and the one called Nexus 5 is the wrong one.

[ernie001]

Thanks KCAndroid1, that's an excellent idea.
There are 4 root directories on my c: containing drivers. These contain dozens of subdirectories and hundreds of files. I can find nothing containing 'android'.
Searched my tablets files using a terminal emulator. Likewise nothing resembling a driver.
What would such drivers be called, where could they be found, and where should they be placed ? ernie

[sydneybush]

You can look for a more simple and effective way of fixing driver-related errors is by using a reliable and efficient Driver Update Tool. Such software can fix even the most obstinate driver errors in a matter of minutes.

[KCAndroid1]

You can look for a more simple and effective way of fixing driver-related errors is by using a reliable and efficient Driver Update Tool. Such software can fix even the most obstinate driver errors in a matter of minutes.

A driver update tool is a good idea.
I also have gotten good results by plugging the phone into the computer's USB, then opening the device manager in the windows control panel. From there you right click on the phone's icon (or whatever the computer calls your phone when it is connected via USB but not being read), which gives choices about searching the web and searching this computer.

[ernie001]

Solved & solution was surprising. Found link below
<censored by this friendly and helpful website> I can't post links...... : (
It's _ support.t-mobile. _ com/ _ docs/ _ DOC-4104

"computer cannot recognize or file transfer with USB device : Android"

This advised plugging cable into port on _back_ of the computer. I have been
using the front ports.
When connected in back the " New Hardware Wizard" opened. This recognized
that a device was attached, although not installed : listed as "Problem Device"
with error code 41. Nothing had happened when Nook connected to a front USB.
After several installation attempts and using Device Manager, the tablet became
installed as 'NookColor', a multimedia device. Previously it was recognized as
logical drive h: .
Now it can be opened from the desktop "Shortcut to My Computer" and its
regular and SD cards files accessed. Unfortunately the Command Line will not
open it. Neither > h: nor > NookColor nor > NookColor: access it. At any rate
it's usable.
I was astonished when I then plugged it into one of the front serial ports. Now it
works with these also.
Thanks to those who answered, Merry Christmas , ernie , central Texas

[KCAndroid1]

Weird, but not entirely surprising. It's as though the people writing the software have never seen the devices. Glad you're back in business.