XP SP2 Traveler install: Error 2 in SetupOpenInfFile

[bnoble]

I've talked about this issue to two technicians at MOTU, both of whom have been considerably less-than polite and/or helpful. Here's the email that I sent:

Traveler: Firmware version 1.05
Laptop: Toshiba Satellite M45-S359, 2.0Ghz Centrino, 1Gig RAM
OS: XP Pro SP2
FireWire chipset: Texas Instruments
Installation package: SETUPFW3.5.3.2

I've attempted the installation of the MOTU software numerous times, each time getting the attached error message. I've gone back to restore points from long before I had the Traveler, tried again, same results. I've tried installing as a different user (as per one of your technicians), same results.

When the installation completes, despite the error, and restarts, I give it a try. The results: The device is seen about half the time in Winamp, is sometimes seen in the "Sound, video, and game controllers" section of my Device Manager, is never recognized by Sonar 5.0 or Adobe Audition 1.5.

Suggestions?

-Ben

I'm going to try a few things when I get home, including manually copying the MotuBus.inf file from the InstallMotuBus directory to my system32\drivers\ directory, reverting to XP SP1, and/or installing the Update for Windows XP (KB885222) package, the last of which supposedly helps with IEEE 1394 (FireWire) performance.

Any other suggestions y'all?

-Ben

[bnoble]

In case anyone else has the same problems I did, the fix (for me) was as follows:

Restore to a point before any MOTU software installation.
Uninstall any previous IEEE 1394 Audio/MIDI interface drivers/software.

1.) Install both KB904412 and KB885222
http://support.microsoft.com/kb/904412/
http://support.microsoft.com/kb/885222/

Set xp-AntiSpy (http://xp-antispy.org/) to the "System default" setting.

Reinstall. Voilà!

MOTU+Windows=ADVENTURE!

[qo]

I love it when people followup with solutions like this. Thanks bnobel.

[Jidis]

MOTU+Windows=ADVENTURE!

...So THAT'S what this is!

I feel much better about it now.

Maybe they can license the Digi ad, or whatever it was, with the guy getting ready to jump into the canyon. Oh wait, didn't he have a hang glider or parachute or something?

[danasti]

In case anyone else has the same problems I did, the fix (for me) was as follows:

Restore to a point before any MOTU software installation.
Uninstall any previous IEEE 1394 Audio/MIDI interface drivers/software.

1.) Install both KB904412 and KB885222
http://support.microsoft.com/kb/904412/
http://support.microsoft.com/kb/885222/

Set xp-AntiSpy (http://xp-antispy.org/) to the "System default" setting.

Reinstall. Voilà!

So, how is everything working out for you now?. Is it working for you in all of your programs such as internet, flash, winamp, windows media, system sounds? Do you have it hooked up for 5.1 sound or know if that works?

Anyway thanks for coming back and following up! It means alot to everyone!

Dan

MOTU+Windows=ADVENTURE!

[danasti]

Set xp-AntiSpy (http://xp-antispy.org/) to the "System default" setting.

I wonder if this had anything to do with it. Security software tends to always be a screwing something up.

[bnoble]

Set xp-AntiSpy (http://xp-antispy.org/) to the "System default" setting.

I wonder if this had anything to do with it. Security software tends to always be a screwing something up.

Yeah, unfortunately I'll never know. I made all of the aforementioned modifications in one fell swoop. I don't know the MOTU installer process very well, but if it requires ActiveX for any reason (ugh), the xp-AntiSpy would have blocked that action, yo.

@qo: No problem. I hate it when an answer is left unstated on a message board. I hope my input helps someone else, someday.

@Jidis: Heh, well, you have to look on the bright side of things. I'll have to admit, there was enough frustration there for a couple of days to warrant my contemplation of an exchange with the vendor for an RME product.

"Tech Support" still hasn't returned my email, and I'm getting concerned about what the future has in store for me, should I encounter any future problems. Whatever, adventure it is. I have more faith in my own troubleshooting skills than the two dimwits I spoke to on the phone.

This is one of those situations where a manufacturer should consider taking the Windows logo off the freakin' box. If you're an OS9/OS X specific manufacturer, just own up to it. That'd be fine. My heart would go on.

[bnoble]

Dan,

Sorry, didn't see the majority of your questions.

Yep, it's working swimmingly, three days without a hitch. Winamp seems to want to keep defaulting to the ADAT out for some reason, but I'll figure that out eventually. Don't have any 5.1 equipment in proximity, but I doubt that it would be much of a problem getting that all situated.

Cheers,

-Ben