Creative ASIO warning

if you have uninstalled all of the creative and soundblaster software using the WINDOWS CONTROL PANEL and are still getting this message, then you'll probably have to edit the registry in order to stop the message. but I'm not sure exactly what you need to edit out to get it to stop. you'd probably have to go to a creative forum and ask them.

Checked Control Panel and found "Creative Driver" - but I couldn't delete it because windows couldn't find the install )or something like that)

I downloaded the registry cleaner and ran it. It created a list with over 1000 members - I deleted it. Everything seems to be working, but I'm still getting the ASIO warning.

I tried rebooting - I got a strange message about installing trayapps - deleted it through task manager - but I'm not sure this is related.

Still got the ASIO warning - but everything else seems to work.

I think I'm done playing with the registry. I was able to fix the trayapp problem (found it on my HP printer disk) but then I got an unhandled exception which required restoring some of the registry items I had deleted. In any case, deleting all that stuff didn't make a difference.

I think it has something to with my Audigy card being OEM and probably with elements permanently locked into the system somehow. I think I can live with this.

ORIGINAL: RWJames

I think it has something to with my Audigy card being OEM and probably with elements permanently locked into the system somehow. I think I can live with this.

No, that is not the case (with ANY soundcard)...

Have you gone to Options-->Audio-->Drivers and deselected (unchecked) all the boxes that relate to SoundBlaster or Creative Audio?

How did you remove the soundcard and its software? (What "uninstall" function did you use?) If you uninstalled the device improperly that's why Control Panel won't let you uninstall it again!

You may need to uninstall SONAR, do a System Restore/Recovery to get the SB card back online so you can properly remove it, then reinstall SONAR so it will only see the M-Audio soundcard.

There is no reason you should have to "live with" a permanent error message everytime you open SONAR. In fact, it is most undesirable as there could be underlying artifacts related to the error that may create more problems! Get it fixed and be done with it.

I found a Soundblaster Audigy program in the the Control Panel software list and removed that... I found some Creative folders in the HP/Audio/Drivers directory and deleted those - no change.

In the middle of all this I clobbered Sonar and had to uninstall and install again.

I did a search for file names with ASIO in it and found a couple of possibilities

C:\WINDOWS\system32\ctasio.dll and ctedasio.dll

Do either of those look like they might be from Creative? They are duplicated in backup directories and a few temp directories.

Should I delete one - or both?

There is also a deltasio.dll which I assume is for my M Audio Delta 44

Sorry... here are the answers

ORIGINAL: papa2004
Have you gone to Options-->Audio-->Drivers and deselected (unchecked) all the boxes that relate to SoundBlaster or Creative Audio?

The only drivers listed are for my M Audio (I either deleted the Creative entries previously, or they were omitted when I re-installed Sonar)

ORIGINAL: papa2004
How did you remove the soundcard and its software? (What "uninstall" function did you use?) If you uninstalled the device improperly that's why Control Panel won't let you uninstall it again!

I used the Control Panel - Remove Software feature. Everything is gone from that list now.

ORIGINAL: papa2004
You may need to uninstall SONAR, do a System Restore/Recovery to get the SB card back online so you can properly remove it, then reinstall SONAR so it will only see the M-Audio soundcard.

I would like to hold this as a very last resort. It sounds like a lot more trouble than it's worth.

ORIGINAL: papa2004
There is no reason you should have to "live with" a permanent error message everytime you open SONAR. In fact, it is most undesirable as there could be underlying artifacts related to the error that may create more problems! Get it fixed and be done with it.

I can appreciate the potential hazard, and quite honestly I hadn't considered it.

I've tried everything I can within Sonar - unless there is something else I don't know about.

So do you think deleting the dll files would do the trick?

ORIGINAL: papa2004

If there are absolutely NO references to Creative or Soundblaster drivers in SONAR's audio drivers menu it should not be looking for any or creating any error messages.

You should be able to safely delete any files that refer to Creative or Soundblaster. I've about decided that SONAR isn't looking for a Creative file, but some remnant of Soundblaster is...Until you completely rid your system of all things "Creative" you're probably going to contine to have the problem.

so I should be safe deleting ctasio.dll in the system32 directory? Can I (or should I) leave it in the backup or temp directories?

ORIGINAL: Fog

ORIGINAL: RWJames

so I should be safe deleting ctasio.dll in the system32 directory? Can I (or should I) leave it in the backup or temp directories?

i normally rename files , and put a Z in front..

and then use the ccleaner thing again, registry bit , but that's entirely up to you.

as for sonar, I had 2 cards plugged in .. would always default to one, so unticking the first one allowed me to tick the second one.

That's a good idea (renaming) - I'll try that. (Note: I recently retired as a mainframe systems programmer, and that was a trick I used a lot - but all that has been purged from my memory )

As for keeping two cards in - I had considered that, but I had read here that Soundblaster doesn't play well with others and won't let anyone else be the default. So I just removed it.

Glad you were able to resolve the issues...