onlyrasel Posted November 12, 2010 Share Posted November 12, 2010 I'm getting getting errorrun-time error '13'Type mismatch Link to comment Share on other sites More sharing options...
Sp0iLedBrAt Posted November 12, 2010 Share Posted November 12, 2010 I'm getting getting errorrun-time error '13'Type mismatch Same here with DriverBackup2183.exe. mscomctl.ocx (v.6.1.97.86) is present in WINDOWS\system32 and registered.No problems with driverbackup79.exe, though. Link to comment Share on other sites More sharing options...
IcemanND Posted November 12, 2010 Author Share Posted November 12, 2010 Now that's interesting. I thought I had the same search logic in both versions. The error message is due to it not finding one of the files for a driver, unfortunately I don't have this issue with any of my machines so it is hard to troubleshoot which file causes this issue, or which place in the logic.Normally if you back up the drivers 1 or two at a time it will work until you hit the driver causing the problem.If you don't have mscomctl.ocx it won't even launch. Link to comment Share on other sites More sharing options...
Sp0iLedBrAt Posted November 12, 2010 Share Posted November 12, 2010 (edited) Noted. I'll do them one at a time and report back.Edit: It has failed for every individual (Non-Microsoft) driver installed. Some drivers are in the NLDRV folder from nLite, but they have also been identified and offered for backup thanks to the .inf files. One driver that was not recognized was for the web cam.Cheers Edited November 12, 2010 by Sp0iLedBrAt Link to comment Share on other sites More sharing options...
onlyrasel Posted November 13, 2010 Share Posted November 13, 2010 Sorry I forget one thing. I already backup my drivers on my old pc with DriverBackup2183.exe. configuration Intel 865GBF, Intel 2.80 HT, 1GB Ram. Nvidia MX4000, etc. It worked fine. Link to comment Share on other sites More sharing options...
alphaniner Posted November 28, 2010 Share Posted November 28, 2010 (edited) I found a MS KB with the file required to run v2.1.83 and extracted the files to system32. But registering any of them manually fails and the program still doesn't run. Win7x64 Professional. Any advice?The older version is a complete bust, it crashes with a script error on the very first driver. Edited November 28, 2010 by alphaniner Link to comment Share on other sites More sharing options...
ricktendo Posted November 28, 2010 Share Posted November 28, 2010 (edited) Try copying it in syswow64 and registering it, if that fails put it in the same dir as the programBTW the tool does not work so well backing up drivers on x64 machines Edited November 28, 2010 by ricktendo64 Link to comment Share on other sites More sharing options...
alphaniner Posted November 28, 2010 Share Posted November 28, 2010 Try copying it in syswow64 and registering it, if that fails put it in the same dir as the programBTW the tool does not work so well backing up drivers on x64 machinesThanks, putting it in sysWOW64 did the trick. I'll keep your warning in mind. I'm mostly interested in seeing what drivers I have in use.Also, thanks for your video tutorials on WAIK. It was a mention of those videos from the driverpacks.net forum that got me started in all this. Link to comment Share on other sites More sharing options...
ricktendo Posted November 28, 2010 Share Posted November 28, 2010 On Windows 7 if you go to the %WinDir%\System32\DriverStore\FileRepository folder and sort it by date you could back up pretty much every driver you need Link to comment Share on other sites More sharing options...
ALSHAIMAA Posted December 20, 2010 Share Posted December 20, 2010 Thank you Link to comment Share on other sites More sharing options...
Sp0iLedBrAt Posted January 13, 2012 Share Posted January 13, 2012 I should report that recently v.0.79 has been reported as a virus (Win32:Malware-Gen) by Avast! 6 Free. I already sent out a "false positive" report, but you should do something as well.Cheers Link to comment Share on other sites More sharing options...
DosProbie Posted April 14, 2013 Share Posted April 14, 2013 Why don't you just add an exception for it in your virus app to turn that off..I should report that recently v.0.79 has been reported as a virus (Win32:Malware-Gen) by Avast! 6 Free. I already sent out a "false positive" report, but you should do something as well.Cheers Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now