Latest Version of Win7 Driver (4.2.0.2)

[Doug Proctor]

The latest version of Mosteks Win7 driver (4.2.0.2) appears to be working correctly now. I recommend downloading it from the drivers page and seeing if it solves any problems you might have been having with previous versions. One thing to be aware of regarding the new version is that automatic sync of GL cards has been disabled due to problems it was causing. Mostek is looking for a solution but there are no guarantees since Win7 itself is the root of the problem. Another issue is that the output gain is reversed on the rev. 3 (maybe 1 & 2 also, not tested) 8/24. This will be fixed in the next update.

The 4.1.x.x series does not work properly with the 8/24 so I'd advise deleting it from any driver file version backups to prevent the chance of accidentally installing it.

Let me know how the new version works for you if you would please.

Thanks

[Greg]

Hi, thanks for the update.

I deleted all the prior versions I could find, and installed this, but still get the error:

gadgetlabs_gui_64.exe - Application Error: The application was unable to start correctly (0xc000007b). Click OK to close the application.

The Windows 7 box is Windows 7 Ultimate, if that makes a difference. Maybe I need to reinstall Visual Studio?

Thanks

[Doug Proctor]

Maybe I need to reinstall Visual Studio?

That would be my first guess.

[Greg]

Maybe I need to reinstall Visual Studio?

That would be my first guess.

I just tried, and there is no change. I even have uninstalled Visual Studio and get the same error.

The system shows the "Test Mode, Windows 7, Build 7600" in the lower right, but every time I restart the computer I get the window: Do you want to let GadgetLabs run, and I click OK, and get the same error
gadgetlabs_gui_64.exe .... unable to start correctly (0xc000007b) , a conundrum.

[Greg]

In my SysWOW64 folder is the file gadgetlabs_asio_32.dll

should that be a gadgetlabs_asio_64.dll?

[Greg]

I really don't know much about 64 versus 32 bit drivers, but the following is set up after installing the driver:

C:\Windows\system32\gadgetlabs_asio_64.dll
C:\Windows\system32\gadgetlabs_gui_64.dll
C:\Windows\SysWOW64\gadgetlabs_asio_32.dll

It seems like 32-bit stuff is in the 64 -bit folder and vice versa. It apparently set this up automatically. Is this what is expected?

Thanks

[Doug Proctor]

http://s1207.photobucket.com/albums/bb471/mephitis/?action=view&current=Capture.jpg

Yes that is normal as the snip I uploaded shows. Did you run Command Prompt as an administrator when you did the "bcdedit /set TESTSIGNING ON" step?

[Greg]

Hmmm, Interesting. I don't have gadgetlabs_asio_32.dll in there

[Greg]

http://s1207.photobucket.com/albums/bb471/mephitis/?action=view&current=Capture.jpg

Yes that is normal as the snip I uploaded shows. Did you run Command Prompt as an administrator when you did the "bcdedit /set TESTSIGNING ON" step?

yes, it said it was successful. That would a good thing to add the install instructions

[Doug Proctor]

Did you type "bcdedit -set TESTSIGNING ON" or "bcdedit /set TESTSIGNING ON"? You have to use a /, - is incorrect. (according to several users and documentation I've checked, another needed correction). Either will return "completed successfully".


EDIT: Either - or / will work with the set switch. I've tried both to confirm this.

[Greg]

I did not use the -, so I redid it with the /
I uninstalled the drivers, cleaned the registry, reinstalled everything, even adding the gadgetlabs_asio_32.dll to the system32 folder since it wasn't automatically put there and it seemed to be expecting it as there were some items in my registry that seemed to point to them. I wasn't able to remove them. in PnpLockdownFiles, having Names like: %SystemPath%\system32\gadgetlabs_asio_32.dll

and got the same error

[Doug Proctor]

I can't think of anything else to suggest. You should contact Waldemar directly and see what he can suggest that you try next.

[Greg]

OK, thanks for going through it with me.

[USRFobiwan]

I really don't know much about 64 versus 32 bit drivers, but the following is set up after installing the driver:

C:\Windows\system32\gadgetlabs_asio_64.dll
C:\Windows\system32\gadgetlabs_gui_64.dll
C:\Windows\SysWOW64\gadgetlabs_asio_32.dll

It seems like 32-bit stuff is in the 64 -bit folder and vice versa. It apparently set this up automatically. Is this what is expected?

Thanks

The SysWOW64 directory is the 32bit driver directory of win7 64bit. So the file placement is correct this way. However since you are running a 64bit system. The file in de syswow64 is actually not needed (if your audio software is 64bit also)

What you can do is run this MS cleanup utility and see if you can uninstall this way. t may happen if you attempt to run a 64-bit application, but Windows finds only the 32-bit version of some dependent DLL.

so my first bet is to clean out the 32bit driver in the registery and rename/delete the 32bit files. Also it is wise to install the driver as administrator. (right click mouse run as admin)

[Greg]

I'm planning to do what you wrote this weekend, thanks.