Windows7 and MOTU drivers

[RWNorman]

I've read both threads about this problem, and I'm still sitting here with an inoperable system if I try to boot on today's date, regardless of the day.

So I went back and did some research. Lots of research. Lots and lots of research. Unfortunately I can only come up with the same work-around that has been presented here.

I can't believe I'm going to say this, but this is one problem I cannot resolve. The situation of resetting your BIOS date is untenable because you don't have time/date stamps sufficient to do your jobs.

The concept of resetting your BIOS date to boot is untenable even if you can reset your date via Windows, because you then have to remember to change your date if you reboot.

I've tried to look at all the aspects of this situation, and tested each one, and yet I find nothing that allows a Windows system to boot on the current date with any of these drivers. Now that's just me, and a lot of you have said "change your system date backwards" but no one has said they can boot with the current date, no matter whether it is Win732, Win764 or either version of Vista.

Some of the things I have noticed is that the MOTU drivers don't register correctly in the driver properties, regardless of which one, and the dates of install don't necessarily match what you might have just installed. There's also a parameter for "First Install" that might be a date prior to the "back dated install".

None of these things make sense. So I remembered that one person, on a different thread, had mentioned that he'd simply rolled back a Microsoft update, which to my research said it was probably .Net 4.0 Runtime, so I went back and uninstalled that. I could then install the 6.1.9.5 driver and it saw all the devices, but wouldn't work to produce audio.

Then again, once I uninstalled these drivers, the driver property box never gave up that particular install. In otherwords, I have uninstalled 6.1.9.5 and removed my card, installed the 3/22/2010 drivers, and the properties of the driver were still the same. 6.1.9.5 or whatever.

I hate problems without solutions, so would everybody here who had the problem relay it to this forum specifically in the manner they suggest works, so that I might continue with my problem determination? My wife, a veteran of 40 years of programming says it is a malicious code, but if it is on the bios of the cards, then it would have to be close to ten years old because it would be on both the PCI424 and the PCIe424. If it is in the driver itself, then it wouldn't be on drivers from a couple of years ago. Or if it is, then it would be a long standing malicious code designed to bring down MOTU cards, which is exactly what happened.

Now if it is not malicious code than it could be unobservable but still bad coding, or perhaps some piece of test code stuck into the driver to see what debugging said about it.

My point is that I have tried every permutation I can think of and still the best I can get is to change my date, install 3/22/2010 drivers, reboot, install the card, and change my date to realtime.

This is not an acceptable solution, and if I'm getting it wrong, then someone write down exactly what they did, EXACTLY, and post it here so I can check against my list to see if I missed something.

There has to be a real solution, and I am bound and determined to find it.

Roger W. Norman
SirMusic Studio

[RWNorman]

I can't believe that so many people have read the post and yet no one is coming up with any solutions.

I have been changing my system date virtually every four days in order to reboot. It works, but it is not workable. There is no reason for me to have to reboot my system in front of a client and change the date, often having to reboot multiple times.

The question I am asking is whether anyone whom uses this method actually has been able to reboot with the current date, yet no one has taken the time to answer.

If I had an answer then I would know that I need to look more seriously at the problem.

This cannot be the answer.

[1nput0utput]

I had the same symptom as you before I updated to the new version of the PCI-424 driver: Windows wouldn't start if the PCI-424 card was installed in the computer. The new driver fixed it for me.

Sometimes the driver properties dialog in the Device Manager doesn't accurately show the version number because the registry may have cached an older value. Here's what I would do to fix your system:

1. If you have changed the date and time in Windows, set them to the proper values.
2. If you have changed the date and time in the motherboard BIOS, restart the computer, enter the BIOS settings, and set the proper date and time.
3. Shut down the computer, and remove the PCI-424 card.
4. Turn on the computer, start Windows, open the Control Panel. In Windows 7, go to the Programs section, and choose the uninstall option. Uninstall MOTU PCI Audio Drivers package.
5. After that's finished, go to %windir%\system32\drivers. Look for a file named motuaw.sys or motuaw64.sys. If that file exists, delete it.
6. Download the current PCI-424 driver installer for your version of Windows (either 32-bit or 64-bit) from motu.com.
7. Extract the installer from the ZIP archive, and run the installer program.
8. After the installer finishes, shut down the computer and reinstall the PCI-424 card.
9. Turn on the computer, and start Windows. When the PCI-424 card is detected, Windows should associate the hardware with the new drivers that were just installed.
10. Confirm that the drivers are working properly by opening the MOTU PCI Audio Console program. You should be able to change the various driver and interface settings.
11. Restart the computer and confirm that Windows starts normally without hanging.