Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. NTamd64] winusbcoinstaller. Friday, September 27, AM. Tuesday, October 1, PM. Run chkinf on the file as well d -- This posting is provided "AS IS" with no warranties, and confers no rights. Friday, September 27, PM. I have checked with chkinf there is no error in inf file, I cannot find setupapi. Please help. Saturday, September 28, AM. Thanks in advance.
Thanks a lot — this really saved the day after couple of hours installing and re-installing the drivers! In response to Rob above, just add a line [ClassInstall32] at the end of the file — that did the trick for me. Just wanted to send a HUGE thanks to you for that info! Been trying to sort out the problem with my mp3 player for ages and now its fixed! Thank you so much!!! Adding [ClassInstall32] in G Hi Jeremy, just sent you an email with regard to this blog posting..
Hope you have a moment to take a look, thanks, Mike. Thanks so much for this helpful info! This just ended two excruciating hours trying to get a printer to work. Each time I try, I receive the message: error 0xe Any suggestions? Hi all, Thanks for this great post. Peoples who are having same problem, but with vista, can do the following: 1- Open C:Windowsinf.
B: you have to obtain permission in order to edit the inf file located in C:Windowssystem32driverstorefilerepository. Search net for how to obtain that permission. Hassan, you are a life saver! Thank you very much. With your advice I was able to get my HP web-cam working with Vista again. Thanks again. But after the install has done new hardware found box comes up so i go threw the process of adding the new hardware and at the end it say can not find the the INF file.
I tryed your fix but there is so many INF entres in my Setupapi. I would of thrown this receipt printer against the wall before I figured this out myself. From what I can Google, this seems to be a "printer thing" and not necessarily a Canon thing. I can usually fix those HP printer things when those bunch of girls at HP through up their hands and suggest reinstalling XP.
Maybe somebody else will have some other good ideas. I know this part is boring, but I hope you will do it anyway: Please provide additional information about your system: Click Start, Run and in the box enter: msinfo32 Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste the information back here.
There will be some personal information like System Name and User Name , and whatever appears to be private information to you, just delete it from the pasted information.
There may also be clues in the Event Log and here is how to post them if that is the case: Look in the Event Viewer for clues around the time of the incident Here is a method to post the specific information about individual events. The most interesting logs are usually the Application and System.
Some logs may be almost or completely empty. Not every event is a problem, some are informational messages that things are working okay and some are warnings. No event should defy reasonable explanation. Each event is sorted by Date and Time. Errors will have red Xs, Warnings will have yellow!
Information messages have white is. Not every Error or Warning event means there is a serious issue. Some are excusable at startup time when Windows is booting.
Try to find just the events at the date and time around your problem. If you double click an event, it will open a Properties windows with more information. On the right are black up and down arrow buttons to scroll through the open events. The third button that looks like two pages on top of each other is used to copy the event details to your Windows clipboard.
When you find an interesting event that occurred around the time of your issue, click the third button under the up and down arrows to copy the details and then you can paste the details right click, Paste or CTRL-V the detail text back here for analysis.
To get a fresh start on any Event Viewer log, you can choose to clear the log backing up the log is offered , then reproduce your issue, then look at just the events around the time of your issue.
If the latter, you can roll back to a previous driver. You will probably have to uninstall and reinstall the drivers and software for the printer afterwards. If you are using an old CD, maybe it is now out of date since many MS updates may have been installed since your successful printer installation. There may also be clues in the Event Log and here is how to post them if that is the case:. Look in the Event Viewer for clues around the time of the incident.
Total Virtual Memory: 2. Gathering Event Log stuff. Otherwise, use the. How would I recognize one? Do I just get a new INF? If so, where? No offense taken. The message. And yes, that is what it says. There is. Try to. Can't take the printer with me so it is not the end of the world. It is not appearing here. Same failure, of course. Thanks for your help!
0コメント