Quote:
|
Originally Posted by mindonstrike
Just guessing here but I believe those are wildcards. In other words the A,B,C etc, version of that particular drive model.
|
Sam, you are exactly right on this point.
Mike, MTUSUPPORT is on vacation. The problem you are having is clearly not expected behavior, and clearly not happening to others with the same drives. Thus, it is a VERY HARD to diagnose problem. The folks posting here are leading you through diagnosis questions, and you are cleary sharp yourself... and very capable. We appreciate your working with us.
This type of problem is RARELY solved overnight unless by accident someone stumbles on the answer. It is an abnormal condition related to your computer and your drives, again I say this as others aren't seeing your problem with the same MODEL Plextor drives.
I have asked our senior programmer who wrote this drive interface code in Hoster to take a look at whether the Plextor drive code, that are supposed to automatically switch to HARDWARE DECODE in the drive (versus SW decode in our software), to see if this might be causing the problem.
We are in a critical product development cycle and to remove our lead programmer from his assigned tasks is VERY COSTLY to MTU. Use your lite-on drive for now.
Why you? I'm at as much a loss as you are.
However, you are not forgotten or being ignored! I suggest you get one of your systems to a stable state so you can do any shows you need to, don't expect an immediate solution... which won't happen given the current facts, and let us do some research at MTU.
MTUSUPPORT will be back from vacation this coming Monday and I've already forwarded this thread to him for his review. I don't think he will have any new immediate ideas, but he will be our liason to you to try things for our programmer.