Jump to content
  • 0

Ok, where is the Vista DLA patch already?


phil8400

Question

I have read the posts as well as John's comments that this is only a improperly flagged driver and that EMC9 works properly regardless. (here)

 

Now we have a Dell OEM DLA patch, but nothing official from Roxio and no mention of an ETA for the non-Dell version(s). To this, add the glaring "Windows Launch Partner" promotion.

 

So, I ask respectfully...where the <expletive deleted> is the fix already?

Link to comment
Share on other sites

9 answers to this question

Recommended Posts

Have you posted that to the Microsoft forum?

 

In the meantime, perhaps you could try the Dell patch - it may or may not work but there's only one way to find out

 

I will try the Dell patch. This said, I'm sure you won't disagree with me when I say that Roxio should have something for us non-Dell customers by now. I can't imagine Microsoft dragging their feet on something like a simple clerical error. Perhaps MS have to re-certify the driver, but Roxio has to build and issue the new files. This shouldn't have to take this long.

Link to comment
Share on other sites

It's fairly common knowledge at this stage that it was a MS zero day update that caused the problem - perhaps you should enquire on the MS forum when THEY are going to fix it

 

Incorrect. I am well aware or the zero day update. However the fix will come from Roxio, not Microsoft.

Link to comment
Share on other sites

Incorrect. I am well aware or the zero day update. However the fix will come from Roxio, not Microsoft.

Not necessarily. A "fix" may come from either Roxio/Sonic or Microsoft, since it was a Microsoft error that caused the problem, depending on what solution they work out between them. It is clearly stated in the the thread you linked to, and the thread that links to, and in the KB article regarding it, that the problem was caused by a "clerical" error on Microsoft's end.

Link to comment
Share on other sites

Not necessarily. A "fix" may come from either Roxio/Sonic or Microsoft, since it was a Microsoft error that caused the problem, depending on what solution they work out between them. It is clearly stated in the the thread you linked to, and the thread that links to, and in the KB article regarding it, that the problem was caused by a "clerical" error on Microsoft's end.

 

Agreed. Now let's get the 'fix' out already. It's been long enough.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Guest
This topic is now closed to further replies.
×
×
  • Create New...