Has anyone ever try burning data by using WRITE12 command under Vista
If enabling UseStreamingWrite12 under Vista ( Ver. 5483 in my case ) and burning data, the CPU would
abnormally goes quite high ( 60% ~ 80%).
Using TaskInfo to check CPU usage, it shows that "Interrupt time placeholder" consumes over 50%~60% CPU.
If using WRITE10 command, the CPU usage would normally below 10%.
Any suggestion to handle this CPU usage issue
StreamingWrite12 Problem in Vista
kalle vanska
Dear Henry,
Thanks for your reply.
I have tried uninstalling the network card driver, but the issue still existed.
From the documentation of IMAPIv2, there is a function called IDiscRecorder2Ex::raw_SendCommandSendDataToDevice().
In fact, I used this function to send WRITE12 command to write random data onto the disc.
However, as I started to send raw data to disc, the CPU usage would burst up.
This testing procedure is for your reference. You might have a little experiment with this raw_SendCommandSendDataToDevice() function.
I'm wondering if this is OS problem (Vista) because sending WRITE10 command through raw_SendCommandSendDataToDevice() is totally fine.
Thanks for your effort again.
William
Maddog C
Dear Henry,
I have tested sending READ12 command in Vista.
And I found that the CPU also bursted up as the WRITE12 case.
So it seems like stream read/write operations in Vista would have this wired issue.
William
Lawrence Kok
Hi William,
We have looked through the code, and much to our embarassment, we found that we failed to actually provide support for StreamingWrite12 == VARIANT_TRUE. This is to say, our code actually doesn't change its behavior at all if this is set to true. Unfortunately, it's too late for RTM to add this support, but we will look to fix this to at least report an error if anyone attempts to set this value to true.
As for your CPU utilization issue: There were a number of reports (my test box being one of them) where an "interrupt storm" would occur during normal use of the machine. In my case, it was the network card driver causing the problem. Other cases are being followed up on currently. So, although this issue is not directly related to IMAPIv2, I do know that it's getting a lot of attention (interrupt storms are 100% unacceptable in Windows).
I'm sorry that our team doesn't have a method to help you track this particular issue down more reliably. I would suggest filing a bug via the beta program.
Hope that's useful,
Henry Gabryjelski
Liam .net
Dear David,
Thanks for your effort.
Wait for your update.
Rizzlers