Midi-fighter utility problem [FIXED: 2012/05/01]
Home :: MIDIfighter Resources and Discussion :: Midi-fighter utility problem [FIXED: 2012/05/01]Reply
Midi-fighter utility problem [FIXED: 2012/05/01] Posted on: 29.04.2012 by Jeramy Bajraktarevic So the other day when I checked my email I was surprised to see that the MF3D was released. I instantly jumped on the opportunity to pre-order. Excited about my upcoming week, I downloaded the MF utility and tried to start it up...and this is what I get: "The application was unable to start correctly (0xc000007b). Click OK to close the application." I installed the application a second time...third time...and each time I get the same message.My heart sunk. How can I use my new 3D without the utility?? Here's some info: Windows 7 64 Bit. No USB devices attached. I don't actually own a Midi-fighter (yet) All, or at least most, of my drivers are up to date...as far as I know. Some one please help | |
Joseph Hausbeck 06.05.2012 |
Originally Posted by Quarent!ne
(assuming you installed to default path) 1. Open the folder "C:\Program Files\DJTechTools\Midi Fighter Utility\driver\x86" 2. Copy the file "libusb0_x86.dll" 3. Open the folder "C:\Program Files\DJTechTools\Midi Fighter Utility" 4. Paste the file you just copied. 5. Delete or backup-and-remove the existing file "libusb0.dll" in this folder. 5a. Rename the recently pasted file "libusb0_x86.dll" to mirror the recently removed file "libusb0.dll" YOU WIN. Hope that helps to clear up any confusion the not-so-tech-savvy peeps may have run into. |
Stefani Addams 04.05.2012 |
Originally Posted by Quarent!ne
Yeah just went to C:\Program Files\DJ Techtools\Mdi Fighter Utiltity\ ... and did the file replacement you mentioned. woot woot |
Ada Matzkin 04.05.2012 |
Originally Posted by Quarent!ne
however you call this simple lol... i woulda never figured this out in a million years on my own. i had to scratch my head just to figure out what the hell you were talking about but ... it works like a charm now . thank you! |
Adolf Hit 18.05.2012 | Hey Guys - Just an FYI, I fixed the installer today so this will not be an issue on future versions. |
Francie Gindin 08.05.2012 | Many thanks!!!! |
Janie Olide 08.05.2012 | Genius, TY! |
Joseph Hausbeck 06.05.2012 |
Originally Posted by Quarent!ne
(assuming you installed to default path) 1. Open the folder "C:\Program Files\DJTechTools\Midi Fighter Utility\driver\x86" 2. Copy the file "libusb0_x86.dll" 3. Open the folder "C:\Program Files\DJTechTools\Midi Fighter Utility" 4. Paste the file you just copied. 5. Delete or backup-and-remove the existing file "libusb0.dll" in this folder. 5a. Rename the recently pasted file "libusb0_x86.dll" to mirror the recently removed file "libusb0.dll" YOU WIN. Hope that helps to clear up any confusion the not-so-tech-savvy peeps may have run into. |
Denna Gorenc 04.05.2012 | This worked for me also. Thank you. |
Stefani Addams 04.05.2012 |
Originally Posted by Quarent!ne
Yeah just went to C:\Program Files\DJ Techtools\Mdi Fighter Utiltity\ ... and did the file replacement you mentioned. woot woot |
Adolf Hit 04.05.2012 | Hey guys, The installer is supposed to check which version of OS you are using and install the correct driver based on that. I suspect that the installer is no detecting 64 bit versions of windows 7 correctly in some cases. Im in New Zealand (Sup Jesse !) for the next two weeks but ill look into fixing this as soon as I return. In the mean time Ill create a PDF for support which outlines the fix above, and sticky it on this community . Thanks |
Latoria Kavulich 04.05.2012 | bump for the windows 64 fans |
Ada Matzkin 04.05.2012 |
Originally Posted by Quarent!ne
however you call this simple lol... i woulda never figured this out in a million years on my own. i had to scratch my head just to figure out what the hell you were talking about but ... it works like a charm now . thank you! |
Jeramy Bajraktarevic 02.05.2012 | It's really strange o_O |
Kimberly Lewark 01.05.2012 | So whats the cause of this - 32bit version of libusb shipped for 64bit windows? This something you can fix in the installer, Midifidler? |
Adolf Hit 01.05.2012 | Sorry to hear about your troubles - glad you got it sorted in the end! |
Charleen Ketchen 01.05.2012 | Ok got it after a few time thanks Quarent!ne!! Im not tech swav but i got THANKS!!! Come on 3D!! |
Paul Abraham 01.05.2012 | Quarent!ne's method worked for me, thank you. I was starting to freak out about not being able to play with my 3D |
Charleen Ketchen 01.05.2012 | Its says my MF Utility Setup is version 0.0.0.0. when I download it it's a Binary File if thats right? Totally lost.....PLEASE HELP! I should have my MF3D today or tomorrow & would like to try it out Thanks ! |
Charleen Ketchen 01.05.2012 | Still nothing!!.....Have downloaded multiple time from Midifighter.com & from a previous post saying" Utility Updated 3/21/12" I tried replacing the files like Quarent!ine but I still get the same message, I just opened up file location on the MFU icon on my desktop. I cannot get this to work correctly, is it something I'm missing? |
Jeramy Bajraktarevic 01.05.2012 | I FIXED IT!!! Wow it was so obvious. The problem was lying in the libusb0.dll. All I had to do was replace the libusb0.dll in the root folder with the one in driver/x86 (libusb0_x86.dll), then renamed it! All that trouble for such a simple fix! |
Jeramy Bajraktarevic 30.04.2012 | Nothing man. I've tried downloading multiple times, repaired my .NET 4.0 framework, ran a virus scan and still nothing! This is proper irritating |
Charleen Ketchen 30.04.2012 | Same here Am I Missing something?!? I have downloaded it numerous times and its says version 0.0.0.0. & I am getting the same message when i try to open the utility, I ordered my 3D this morning so kinda in the same boat as Quarent!ne, I'm goin to Midifghter.com to download it. Do I need to install the drivers in the drivers folder?!? please help |
Adolf Hit 01.05.2012 | Hey Dude - Can you try downloading the utility again and installing the new version. Windows 7 64 bit should be fine |
<< Back to MIDIfighter Resources and DiscussionReply