Pilote sonic solutions dla windows 7

I had a RTM version for Vista for business when this advertisement was posted. Now two months after the retail release Roxio can still stand behind the original advertisement "There is no support for Vista". After installing earlier versions of CD Creator I got blue screens. Who is at fault? It is Roxio's product and if it does not work as Microsoft has Vista working Roxio needs to fix the problem. For Vista any driver being loaded needs to be certified.

It is not a fix to go and uninstall an update Microsoft has released. This past weekend I looked at CD burners and Computers to see what software they were using. Every one had Nero 7. This tells me that Roxio and Sonic Record Now do not want to continue producing any more products for CD burning applications. Roxio has been my choice for burning software ever since I started to use CD Burners, but I am looking into other options.

I don't know what would possess you to transfer computers to Vista, this early in the release, but to me, it shows poor business judgment. And, a good goodbye to you, too. Man, that's a scary thought! But, if that's what you do for a living, he won't have to worry about losing his job I guess. He'll be very busy for a long time. When your own countrys transport group puts a embargo on using vist big news there in the USA id think this guy dosnt know what he is doing or he is a few beers short of a six pack??

Even our Importers, who bring in the OEM and OLP packs of vista are saying not to look at it in a busness prospect for at least 6 to 8 months as there is so much non application compadability??? And also if he wants to run EMC on pc's? It is not a fix to go and uninstall an update Microsoft has released I would be looking to MS to fix that problem. That one issue aside, there are many that have had success running EMC 9 on Vista.

This is my first post here, and most likely my last. I was going to ask for some help with the same problem that these guys are having, just a driver incompatibility issue that is not a Vista issue, but a Roxio driver issue.

It is obvious that the driver does not fully work with Vista. This makes it a Roxio driver issue. My hope was to find some support here, but from what I have read so far forum where people who ask how to resolve their problems are flamed for even having the audacity to ask such a question. The guy was only asking for advice, not a consortium of nerds coming down on him for his decisions.

They messed up the whole thing with a zero day patch to Vista. At the moment, Roxio and MS are working on a fix. They are also working to get the entire suite registered as Vista compatible and there will be a patch released once that happens. The decision was taken not to issue a patch, followed by another, followed by yet another until the entire thing was ready to go. In the meantime, remove Drag to Disc, using the control panel and that will cure the notice regarding the driver.

I think Roxio's suggestion to delete a Windows update is very unprofessional. They should issue a patch, not try to change someone else's software. I tried to do their Dell work-around , and that just deactivated drag-to-disc. How long has this issue been around? I have a very positive view of the EMC software, but Roxio is being very unprofessional in trying to pass the buck. It's been several months and the software is still not certified compatible with Vista???

Vista was released to the public on Januaray 30, I believe. Microsoft and Roxio are working together to overcome the problems caused by the bug that Microsoft put into Vista, just before, or after, it was released to the public.

Hopefully, Roxio's patch will come out next month, but I certainly hope it fixes more than Vista problems. I don't have Vista on my computers. I an on Windows 7 and I am getting the same thing posted here for Vista. Does anyone know a work around for this issue? I found the Roxio Driver Patch on there site and it fixed mine! It's the old Drag-to-Disc driver that Windows 7 objects to. That patch updates Drag-to-Disc so that Windows 7 stops objecting to the driver.

But it won't fix any other incompatibilities between Windows 7 and EMC 9, if there are any. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Windows Vista Applications. For compatibility of 3rd party applications, use the ACT forum. Sign in to vote. Looking for advice please.

Many thanks in advance. Friday, February 2, AM. Hi, I had the same problem with Vista Business Edition. Hope this helps. Monday, February 5, PM. Tuesday, February 6, PM. Monday, February 26, AM. I don't see Sonic as a program installed on my PC. What am I missing? Any help you can provide would be appreciated.

Wednesday, February 28, AM. Thursday, March 1, PM. Friday, March 2, AM. Saturday, March 3, AM. Wednesday, March 7, PM. Please help me find a update driver or a solution for the problem.

Thank you. Friday, March 9, PM. Saturday, March 10, PM. Friday, March 30, AM. Saturday, March 31, PM. If you download the file.

And run it. You can disable DLA without actually uninstalling it. It was a long time ago when I did this so if I am forgetting a step I apologize. I can remember the issues it gave me though. I couldn't install any kind of program that had multiple cd's unless DLA was disabled.

What a pain. I miss XP! I'd love to stop getting that to pop up, yet everything I've tried per solutions listed in the forums has not worked. In fact, there is no DLA listed in the properties area after clicking on the various drives! Any other ideas for me? It's funny, I just bought a new XPS M a couple days ago, and immediately got the same incompatability message just like everyone else.

So much for Dell testing systems before they ship, huh?? Anyway, I contacted Dell tech support about this live chat and they disabled one Vista update can't remember which one , and it completely got rid of the error message at startup.

So, in my particular situation, an update was the compatability issue, not the driver. Just to make sure this was the problem, I reinstalled the previously removed update after a day or two, and as expected, the error message came right back.