Working on getting my Sansa c250 connected and reading files under Windows XP.
2 potential issues when getting the “device cannot start” with a “code (10)”.
- The usb cable is too long. This is even more likely if you are connecting on a usb port in the front of you case since those are already extended from the motherboard to that point (depending on how long the extension cable is inside of the case). Then you are connecting to it with whatever cable you’re attaching the usb device with. If it’s a longer cable then chances are you are running into a physical limitation of the usb spec.
- driver issues. In the case of the Sansa c250 there are no drivers on sansa’s site. They rely completely on the drivers that come with windows XP. But, my issue was fixed by downloading and installing Windows Media Player 11. Not sure what is included with Media Player 11 that makes it work, but once it was installed it detected the Sansa c250 as an “MTP device” instead of a USB Mass Storage Device and it connected up without issue.
This doesn’t go along with this, but I’m just putting down my techinnincal stuff for the day. Here is a UNC path for creating a shortcut for the built-in scanning device that comes with Microsoft Office but is pretty much buried if you don’t know where to look for it.
"c:\program files\common files\microsoft shared\MODI\11.0\MSPSCAN.EXE" Black and white
You can include a profile name at the end of the path to the exe file as in the example above -> Black and white.
MSPSCAN stands for MicroSoftProScan… I guess. When you google it you get “Microsoft Office Document Scanning App”
Spent time on Rachelle’s PC at VWPlumbing. Has been running very slow. Problem turns out to be 100% CPU utilization by the “HP Network Devices Support” service. I was able to discover this by using sysinternal’s excellent tool – “Process Explorer” by Mark Russinovich. That service is only needed if you are printing to the device via the network and only for monitoring if new devices are added to the network? Not quite sure. Anyway, stopping and disabling it solved the problem. Here is a link to a thread on it.