How to debug USB drivers

I recently have a lot of kernel panics. I have discovered in the systemprofile/extensions that IODVDstoragefamily.kext has errors
a. com.apple.iokit.IOCDStorageFamily: No valid version of this dependency can be found
b. Kext has a kernel dependency prior to version 6.0 and CFBundleVersion does not match executable's MODULE_VERSION
After checking i found out that i use driver version 2.1.5. while my current OS (10.3.9) should use driver 2.1.7.
My questions:
1. Could this be one of the problems.
2. Is debuggin an option or is this not advisable for a newbee like me?
(see http://developer.apple.com/devicedrivers/download/usbdebug.html)
I cannot find the kernel panic log anymore otherwise I could have send it in the post.
Thanks in advance for the help
Elro

I still have some errors in the kext but this was not the problem. I found the problem was a broken/ pinched trackpad cable
See for the fix:
* http://www.posner.net/marc/projects/TiBook/TiBook.html
and * http://discussions.apple.com/thread.jspa?messageID=1145413&#1145413
Elro

Similar Messages

How To: Debug missing Drivers in MDT

The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
Please to NOT post questions from this thread, instead create a new thread.
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the
full OS
Step 1 - Try network connection again
It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
Step 2 - Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
Step 3 - Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
Install the driver package by:
  ○ Open the Device Manager (devmgmt.msc).
  ○ Find the network device in the list (ensure this is the wired device, not the wireless device)
  ○ Right click on "Properties" and click on the "Details" tab.
  ○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
      PCI\VEN_8086&DEV_1502&CC_020000
      PCI\VEN_8086&DEV_1502&CC_0200
  ○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
  ○ You should get a confirmation that the driver package was installed.
  ○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
Step 4 - Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
Step 5 - Run the full MDT installation
During installation MDT will perform the following:
  ○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
  ○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
  ○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
  ○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in
WinPE
Step 6 - Try the network connection again
(See above
Step 7 - Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
  ○ Try connecting to the Deployment Share:
  c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
  ○ Try pinging the Deployment Server:
  c:\> Ping.exe MDT.Corp.contoso.com
  ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
no devices are listed - Driver bad - Driver not installed.
  ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
Step 8 - Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
other method. Cross check your WinPE Driver Settings.
  ○ From within the MDT console, right click on the root of your Deployment Share and select properties.
  ○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
  ○ Your Network Drivers package must be in the "Selection Profile" if enabled.
Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals
http://live.sysinternals.com/Dbgview.exe tool.
  ○ Open up the MDT console.
  ○ Download and run the DbgView.exe tool.
  ○ Update the deployment share in question.
  ○ The DbgView tool should show what drivers were copied to each WinPE Image.
Other
Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment.
Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Further Help
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Include a short description of the problem. Including the Make/Mode if necessary.
Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
Copy your known good driver package (step 3 above) to OneDrive.
Copy the following log files to a public site like OneDrive and include the link:
  ○ PnpEnum.xml (from Client)
  ○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
  ○ c:\windows\inf\SetupAPI.*.log (from client)
  ○ %DeployRoot%\control\Driver*.xml
  ○ %DeployRoot%\control\SelectionProfile*.xml
  ○ %DeployRoot%\control\settings.xml (if problems in WinPE)
  ○ x:\windows\System32\WpeInit.log (if problems in WinPE)
  ○ If the MDT server is not including your driver package in WinPE include the DBGView log.
This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

OK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
JJ

How to Add USB Drivers to a Virtual Machine

Hi,
the documentation and also the "old" Sun Wiki always refers to the USBD.SY_ from the Windows XP Media.
We have a Windows 2008 R2 Server running on VMware ESXi with RDS and I don't get the USB redirection to work properly.
First of all, the driver of the utSrServerBus Device is not installed correctly (it seams to because of the Windows Driver Compatiblity Check). The Device hast a yellow warning "!" in the Device Manager and says (Code 52).
The driver was signed wrong or the file is corrupt. I've reinstalled it several times now. Watching the driver file (inf) properties I see that it is signed by Oracle (and by Versign).
I think this also leads to that the utSrServerPort is not installed.
The second idea is, that I don't use the "right" usbd.sys. Of course it was not possible to install the one from XP. Even from XP 64 bit.
According to: http://www.digi.com/support/kbase/kbaseresultdetl.jsp?id=1051 Windows 2008 R2 need the USBD.SY_ from its original media...
BUT: the file is already there...
Thanks a lot
Julian

hi, thanks! that's a nice trick ;-)
I've installed the SRWC Components from the SRSS 5.1.1 release. Components are Version 2.0.12.0.
USB redirection works. Is this a bug of the 2.4 components?`

Hi, my Ipod Schuffle (4 gen) dissapears from windows vista right after I execute Itunes, I've change the drive letter, erase temps in App data file, verified USB drivers, etc... Can someone guide on how to solve this?

Hi, my Ipod Schuffle (4 gen) dissapears from windows vista right after I execute Itunes, I've change the drive letter, erase temps in App data file, verified USB drivers, etc... Can someone guide on how to solve this?

If you want the shuffle to be always visible in Windows (outside of iTunes), you need to Enable disk use.
Select the shuffle in the iTunes sidebar, under DEVICES. Over to the right, select the Summary tab. You should see a checkbox that says Enable disk use. Check it and click Apply.
NOTE: If disk use is enabled, you have to Eject the shuffle in iTunes, BEFORE you physically disconnect it. If disk use is NOT enabled, you can disconnect the shuffle at any time, as long as iTunes is not doing something with it at that moment (such as syncing); the shuffle's light will then be blinking (to indicate DO NOT DISCONNECT).
So, unless you want to use the shuffle like a USB flash drive (carry random files on it), you may want to NOT Enable disk use.

64 Bit Windows7/8/8.1 USB drivers for Palm Desktop

Thanks to the great folks over at Aceeca.com (makers of NEW PalmOS Garnet devices), USB drivers for 64bit Vista, Windows 7, and Win 8 operating systems are available. There are many users reporting Palm Desktop 4.x is also working.
I have synced my TX to my Vista64 bit laptop, and Windows 8.1 HP Spectre X2 hybrid successfully via my USB cable.
The drivers are located here:
Aceeca Driver Downloads
Installation instructions (from Aceeca) for Windows 7 are included in the download.
Basic instructions:
1. Download the drivers and Extract them to the same folder. Remember the folder you extracted them to.
2. Try to HotSync your device. It will fail.
3. Open the Device Manager, and look for the Yellow Triangle next to either "Acceca" or "Palm Device" under "Other devices".
4. Right-click on the device, and choose "Update Driver Software".
5. Choose "Browse My Computer for Software" and direct it to the folder you extracted the Aceeca drivers to.
6. Choose "Next" at the driver file location window, and then tell it to "Always trust software from Aceeca Ltd." then click the "Install" button.
7. I received an error message (Vista64) that told me "The drivers were installed but the device couldn't be opened." I saw that my TX had timed out and went to sleep. I tried a HotSync and it worked!!!
Good luck!
NOTE: Palm Desktop 6.22 may only show Media and Install. Here's how to fix that:
If Palm Desktop 6.2.2 only shows Media and Install, try this: Right-click on the shortcut for Palm Desktop, then choose "Run as Administrator". The ther modules should appear.
To make Palm Desktop Run as Administrator every time in Windows 8/8.1:
Close Palm Desktop, if open. (This is a very important thing to always do when using 6.2.2 - it has been known to lose data when a computer is shut down without closing the program!)
Right Click on the Palm Desktop Icon in the Metro screen, then choose "Open File Location". You will now see the actual file for the shortcut.
Right-click on the "Palm Desktop" shortcut file, then Properties. Now pick the Compatibility Tab at the top.
At the bottom of the Compatibility Tab is a checkbox: "Run this Program as Administrator", Click OK .
Try opening Palm Desktop, all the parts should appear. You may see a box open when you close the program asking "Did the program run correctly?" I picked "Yes", and it's been working fine since then!
If you are using a much older PalmOS device and want to try using Palm Desktop 4.x, you will need this additional patch from Pimlico Software:
Palm HotSync Setup
WyreNut
Forum member bobboffin has added this post:
"After attempting your first HotSync and failing (as expected) you may be unable to find any trace of the device in Device Manager, making the next step quite difficult. This happened to me, and after some investigation I discovered the following tip that allows Device Manager to show hidden and non-present devices.
Open up Notepad and paste the following two lines into it:
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
start devmgmt.msc
Save it as SetDev.bat into My Documents.
Open My Documents in Windows Explorer and double click on SetDev.bat. Device Manager should open.
In the View menu select Show Hidden Devices.
You may now see under the Other heading the failed device with a yellow triangle against it.
You can now proceed to install the drivers per the instructions.
Note that the driver supports most Palm OS versions. I'm actually using an Aceeca Meazura 1000 ruggedized PDA running OS 4.1 --- bobboffin"
Hope this helps!
WyreNut
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!
This question was solved.
View Solution.

Thank you so much. I was thoroughly disappointed to see that the support telephone for paid support had been discontinued. I thought I would need to replace my (ancient but serviceable) Z22.
I followed the instructions listed here and am very happy to report that I completed a sync!
Thanks again.

Where are the USB drivers for my MSI board??

Got a new MSI board- VIA KM266 Pro + 8237 Chipset Based. I installed my new AMD 2300+, WIN XP, etc. I have a USB printer. Got everything installed, printed a test page, and then a document. Everything fine. THEN, I go to use my printer a few days later and it says "Printer not responding". So I troubleshoot, and then go into Device Manager and notice there are no USB devices installed. The new MSI board has 4 USB ports on it. The CD that came with the board has no USB drivers on it (I checked). WIN XP has no USB drivers. What is going on? How do I get the USB ports to work? Am I looking at it all wrong? Appreciate any help out there!

Quote
Stu: He started his thread saying "Got a new MSI board- VIA KM266 Pro + 8237 Chipset Based."
osnavi, that is true. after searching through MSI website, i think this is the board he is referring to, KM3M:
http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_detail.php?UID=611
sonic, what is your USB printer?

I've installed windows 7 with the help of bootcamp on my macbook pro 2011. Please help me how to install mac drivers for windows7 64 bit???

I've installed windows 7 with the help of bootcamp on my macbook pro 2011.
Please help me how to install mac drivers for windows7 64 bit???

You either download drivers from within Boot Camp Assistant and save to USB FAT disk, or you insert and use 10.6.x OS X DVD when in Windows and install and run the SETUP from there.
General Help:
Boot Camp 4.0, OS X Lion: Frequently asked question
http://support.apple.com/kb/HT4818
http://manuals.info.apple.com/en_US/boot_camp_install-setup_10.7.pdf
create a Windows support software (drivers) CD or USB storage media
http://support.apple.com/kb/HT4407
Installation Guide Instructions for all features and settings.
Boot Camp 4.0 FAQ Get answers to commonly asked Boot Camp questions.
Windows 7 FAQ Answers to commonly asked Windows 7 questions.
- support articles and tips, how to.
http://www.apple.com/support/bootcamp/
Macs that work with 64-bit editions of Microsoft Windows Vista and Windows 7
http://support.apple.com/kb/HT1846
Step 4: Install the Boot Camp Drivers for Windows
After installing Windows, install Mac-specific drivers and other software for Windows using your Mac OS X installation disc. The Mac OS X disc installs drivers to support Mac components, including AirPort,built-in iSight camera, the Apple Remote, the trackpad on a portable Mac, and thefunction keys on an Apple keyboard.
The Mac OS X disc also installs the Boot Camp control panel for Windows and theApple Boot Camp system tray item.
To install the Boot Camp drivers:
1 Eject the Windows installation disc.
2 Insert the Mac OS X disc. If the installer doesn’t start automatically, browse the disc using Windows Explorerand double-click the setup.exe file in the Boot Camp directory.
3 Follow the onscreen instructions.
If a message appears that says the software you’re installing has not passed Windows Logo testing, click Continue Anyway.
Windows that appear only briefly during the installation don’t require your input.
If nothing appears to be happening, there may be a hidden window that you mustrespond to. Check the taskbar and look behind open windows.
Important: Do not click the Cancel button in any of the installer dialogs.
4 After your computer restarts, follow the instructions in the Found New Hardware Wizard to update your software drivers (Windows XP only).
5 Follow the instructions for any other wizards that appear.
6 Check for updated Boot Camp drivers by using Apple Software Update or going to www.apple.com/support/bootcamp.
If You Have Problems Installing the Device Drivers
If it appears that the Boot Camp drivers weren’t successfully installed, try repairing them.
To repair Boot Camp drivers:
1 Start up your computer in Windows.
2 Insert your Mac OS X installation disc.
3 If the installer doesn’t start automatically, browse the disc using Windows Explorerand double-click the setup.exe file in the Boot Camp directory.
4 Click Repair and follow the onscreen instructions.
If a message appears that says the software you’re installing has not passed Windows Logo testing, click Continue Anyway.
If you need to reinstall specific drivers, you can install one driver at a time. For example,if your built-in iSight camera isn’t working, you can reinstall just the iSight driver.
Individual drivers are in the Drivers folder on the Mac OS X installation disc.

Windows 7 64bit & Aceeca USB Drivers & PdaNet

Has anyone been successful in using the Aceeca USB drivers with PdaNet 4.1.2 on Windows 7 64bit?
I believe this should work, but it doesn't. I have place two support messages into June Fabrics about this over the last two weeks and got no response. The June Fabrics FAQ says:
Does PdaNet support 64 bit system? On 64 bit Vista I received installation error "UpdateDriverForPlugAndPlayDevices err=-536870347".
PdaNet does not work on 64 bit system due to lack of 64 bit USB support from Palm's HotSync Manager.
My device is a Treo 755p. I can successfully HotSync via both bluetooth and USB/64bit-Aceeca on Windows 7 64bit. I have got a trial version of USBModem by Mobile-Stream.com to work for Internet tethering, but I just don't understand why PdaNet won't install given the installed Aceeca drivers and June Fabrics FAQ.
Post relates to: Treo 755p (Verizon)

>got a trial version of USBModem by Mobile-Stream.com to work
Can you provide a link to a detail description of how to get it to work -- I can't seem to do it.
Do you need the 20/month additional option from Verizon?

Installing LR 3.6 trashed all USB drivers; now installed LR3.5 won't open. Help!

Downloaded LR 3.6 yesterday. Installed. (To upgrade from LR 3.5). It damaged all USB drivers on my PC (XP Pro 32 bit). Still working with Dell tech support to resolve. Now installed LR 3.5 will not open. After system restore to day before yesterday, message that "Adobe AIR is damaged" . What is AIR??? How do I get LR back up & running right?

Adobe AIR is a cross-operating system runtime environment. Try downloading and installing it from here.
Beat

How to debug this error? trying to load excel file to Database

SSIS package "c:\users\asubedi\documents\visual studio 2012\Projects\Integration Services Project1\Integration Services Project1\PackageToLoadBuyerDedupe.dtsx" starting.
Information: 0x4004300A at BuyerDedupe, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC0209303 at PackageToLoadBuyerDedupe, Connection manager "Excel Connection Manager": The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
Error: 0xC001002B at PackageToLoadBuyerDedupe, Connection manager "Excel Connection Manager": The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. For more information, see http://go.microsoft.com/fwlink/?LinkId=219816
Error: 0xC020801C at BuyerDedupe, Excel Source [2]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at BuyerDedupe, SSIS.Pipeline: Excel Source failed validation and returned error code 0xC020801C.
Error: 0xC004700C at BuyerDedupe, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at BuyerDedupe: There were errors during task validation.
SSIS package "c:\users\asubedi\documents\visual studio 2012\Projects\Integration Services Project1\Integration Services Project1\PackageToLoadBuyerDedupe.dtsx" finished: Failure.
how to debug this issue?

Hi Arjunji,
The issue occurs because you have only 32-bit Microsoft ACE 12.0 OLEDB drivers installed, however, the package runs in 64-bit runtime mode which requires 64-bit drivers.
To avoid this issue, you need to either install the 64-bit
Microsoft Access Database Engine 2010 Redistributable or run the package in 32-bit runtime mode. To run the package in 32-bit runtime mode, in SSDT, you can set the Run64BitRuntime property of the IS project to False; in a SQL Server Agent job, you can
configure the SSIS Package Job step and check the “Use 32 bit run time” option.
In addition, please note that the 32-bit install file of Microsoft Access Database Engine 2010 Redistributable and the 64-bit one cannot be installed side by side on a single server. However, if your current ACE 12.0 OLE DB drivers are installed by 32-bit
Office suit, you can go ahead and install the 64-bit Microsoft Access Database Engine 2010 Redistributable.
Regards,
Mike Yin
TechNet Community Support

New ipad USB drivers for pc running on win7

Error message when downloading USB drivers for new iPad for win 7 (64 bits)

My husband's laptop which is at least 3 years older than mine has not problem with charging or recognizing my IPAD. So I don't think the USB ports have anything to do with this problem. What I see is that the PC wants to load MTP USB driver which fails. I have the Apple Mobile Device driver installed and activated. My computer does not see the IPAD but Itunes does. How do get the PC to recognize the apple mobile device driver before it tries to download the MTP USB driver? I am going to try the last suggestion from Diavonex to see if it will work. This is sounding more and more like a Windows problem. BTW both my and my husband's laptops are Dell so I might try looking there also. Wish I had an answer.

64-Bit USB Drivers: WHEN????????????

See message subject -- it's all there. Don't tell me about "Bluetooth" or "WiFi" workarounds. Tell me WHEN there will be 64-bit USB drivers.
Post relates to: Palm TX

I've finally solved the 64-bit USB Driver problem with my Palm T|X. I can now sync my PDA with WinXP Pro /x64 and Vista /x64 with no problems or by using funky work-arounds. Just plug it in to the USB port and away she goes -- recognized instantly!
How did I do it? Not with anything from Palm!
Bought an HP iPAQ 210 that runs under Windows Mobile Classic, version 6. Amazing how there's a 64-bit ActiveSync made for WinXP /x64. Does a number of things in addition to being able to sync using a USB cord . . . Bluetooth 2.0 (the T|X is the slower 1.0 or 1.1) . . . 802.11g (T|X is the slower 802.11b) . . . and it has a VGA 640x480 screen. Yes, it goes for a higher price than a T|X, but wouldn't even have been looking at other PDAs if there had been 64-bit WinXP and Vista drivers for it along with the loss of some features in the latest Palm Desktop (released finally for Vista). The T|X is a fine PDA, except . . . no 64-bit drivers . . . nothing about when they might appear . . . for years now . . . stone silence from Palm about it . . . and quite seriously, it's my sole reason for looking for a different PDA and dispensing with the T|X.

How to get USB ports work on Portege M400?

I am not able to get memory sticks, cameras and iPods recognized when plugged into the USB port of my M400.
I have updated all the windows software and all the drivers that I can find.
When a device is plugged in the found new hardware dialogue box comes up - but of course a driver is never found.
I have explored the forum extensively and tried deleting the USB driver in the hope that on reboot the drivers would reinstall correctly - they did not - in fact the system does not seem to be able to find the USB driver at all and I now get a lot of error messages and unknown hardware trying to install.
I have a 1 day old backup - an image done using Aronis true image - in trying to restore this I need to be able to boot from the CD ROM - this certainly does not happen with my current set up - how do I do this - presumably I have to change something in the BIOS - how do I access the BIOS - the manual is notably short on info here.
So two basic problems - how do I get the USB ports to work - it is definitely a problem with computer as everything works fine when I try these devices on other computers.
And get how do I get the CD ROM set up to boot from a bootable CD?
Thanks in advance for any suggestions - this has been an ongoing problem that is beginning to become rather vexing.
ian

Hi
First of all this is not a hardware problem but simply software issue.
I see you have tried to install different external USB devices. Most of these devices need special software which is always bundled with the device.
I dont know what you have installed and removed from the system but it looks like you have messed the whole OS.
In this case I would recommend installing the OS from the recovery CD.
To boot from the CD you have to insert the CD into the CD/DVD drive and press the F12 button immediately after notebook powering. This procedure should enable the booting menu from which you could choose the right boot device (ODD).
Note; the USB drivers are provided by Windows operating system.
Furthermore if you want to use your iPod you have to install the iTunes software! Without this software the iPod does not work!!!
Bye

Windows 8.1 Task Sequence is picking the wrong USB drivers

I have a Windows 8.1 task sequence that hasn't had any driver issues on all the other desktops I've tested. Except the HP Compaq 6000 Pro. None of the USB drivers are working correctly unless I select Update Driver Software -> Browse my computer for
driver software -> Let me pick from a list of device drivers on my computer then a list of 4 driver options appear. I can select any of them and they all work. I can't seem to figure out how to get it to select of those drivers by default. I've tried building
a driver package and also a capture with the correct drivers selected. Neither have worked. Does anyone have any suggestions?

Hi,
Please have a look on the following thread. It might give you some hints.
"use
http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d to 'grab' the drivers you've succesfully installed into your hardware and inject those to ConfigMgr. Create a driver package and use "Apply Driver Package" -step in your task sequence
with WMI conditions so that this driver package only applies on to the right make/model."
http://social.technet.microsoft.com/Forums/en-US/9094d303-d01d-44fa-801c-65578122c8bd/how-do-i-stop-windows-from-downloading-drivers-from-windows-updatewsus-during-operating-system?forum=configmanagerosd
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to Get HP Drivers After (DIY) Installing Windows?

Series: How to Re-Install Windows when you don't have the Recovery Discs
Intro: What is an ISO? Why is it used?
Step 1 - Get the ISO - ISO Download Links
Step 2 - Burn the ISO to a DVD or USB
Step 3 - What to do with the ISO DVD/USB? Change the Boot Order
Step 4 - What to do After Windows is Installed? How to Get HP Drivers?
Step 4 - What to do After Windows is Installed? How to get HP Driver?
Winodws is Installed, Now What?
Once the installation is complete, you'll need to go to your HP Driver Page and download all of your drivers. Your wireless function may not work automatically with a fresh install. You may have to plug an Ethernet cable into the computer and into your router to connect to the internet initially, until you have downloaded your wireless driver.
The best way to use the HP Driver Page, is by putting in your product number ('P/N' found on the HP label on the bottom of the computer) and click Go, rather than the 'Detect my product - Find Now' option. Without an HP Recovery Disc version of Windows, the 'Detect my product' option is not likely to work properly.
Another important note: If you had to go all the way into BIOS and change the Boot Order to the DVD drive (or USB), you'll have to go back into BIOS at your convenience and change the Boot Order back to booting from the internal Hard Drive first. If you used the F9 Boot Order Menu, it only changes the Boot Order temporarily, for that one power on iteration.
If you have any questions, create a new post (How to Create a New Post - Video), copy and paste it's link into a private message to me, and I will respond on your thread

Note down all the file names of the following queries first:
SELECT NAME FROM V$DATAFILE;
SELECT NAME FROM V$CONTROLFILE
SELECT NAME FROM V$TEMPFILE
SELECT VALUE FROM V$PARAMETER WHERE NAME = 'spfile'
If the last query doesn't show any file then copy $ORACLE_HOME/dbs/init<SID>.ora file.
After making the list in sqlplus issue:
SHUTDOWN IMMEDIATE
And now you can copy all of those files to some other location. Make sure you install same version of OS and Oracle to restore these files. It would be easy for you if you keep the same directory structure after reinstall and place all those files as they were earlier.
Daljit Singh

How to debug USB drivers

Similar Messages

Maybe you are looking for