PDA

View Full Version : M-Audio Firewire Solo Software Problem

rhcp_rob
03-23-2008, 05:54 AM
Hi all,

I got my FireWire Solo last summer and all has been working fine. Occasionally, however, the mixing software would refuse to open. The icon in my Start bar would show up, but whenever you tried to select it, nothing would appear. Quite bizarre, but I was able to fix it by simply re-installing my FireWire Solo. However, its recently done it again, and despite several re-installations the problem persists - the drivers have installed fine and the device works well with the default settings, but Im not able to open the panel software to change any of these settings. Has anyone had this problem before? My PC specs are:

Dell Inspiron 530
Vista Home Premium 32bit
Intel Core 2 4400 @ 2GHz
2046mb RAM

Any and all help is greatly appreciated.

-Rob
TechKnowledgy
03-24-2008, 10:55 AM
Can you open the M-Audio control panel from the Windows Control Panel? Do you get an error?
rhcp_rob
03-25-2008, 01:21 PM
Can you open the M-Audio control panel from the Windows Control Panel? Do you get an error?

Hi - thanks for replying.
The same thing happens when I open it straight from the control panel - the programme 'opens' but doesnt show. There's no error message either.
-Rob
TechKnowledgy
03-26-2008, 01:22 PM
I think I've heard of this issue on XP, and would assume it's the same thing on Vista. The Fix was to delete the "WindowLayout" folder in the mafwcpl (M-Audio FireWire control Panel) folder from the registry. You may want to contact M-Audio on that one. If you don't know what you're doing, you can really mess up your system if you start messing with the registry.
rhcp_rob
03-27-2008, 02:22 AM
I think I've heard of this issue on XP, and would assume it's the same thing on Vista. The Fix was to delete the "WindowLayout" folder in the mafwcpl (M-Audio FireWire control Panel) folder from the registry. You may want to contact M-Audio on that one. If you don't know what you're doing, you can really mess up your system if you start messing with the registry.

Awesome! That seemed to do the trick. I made a backup of that registry folder just in case anything goes wrong in the future, but for now the problem is solved. Thanks ever so much for all your help mate - I owe ya one!
-Rob