I’m trying to figure out how to ride through several second glitches on DVDs, basically by making the buffers somewhere in the
pipeline larger. One place I’m looking at is near the DVD-drive. The target system is Windows 98 (could change to Me if that
helped).
First of all, I wrote a simple program to read the DVD as fast as possible, and to display cases where the response time from
the read exceeded some threshold (e.g., .5 seconds). I ran this on my W2K laptop, and got the behavior I’d expect (.8-1.3
second glitch at the layer change, infrequent and random .4-.8 delays). The
same program on Win98 gets a read error on the CSS protected files. Hence my first question: Why is
it not OK to give me the data on Win98 but it is on Win2K? Or does this have to do with the two DVD-drives?
If I run CDFS on Win98, I can adjust the caching & prefetch parameters, but apparently there aren’t any tunable parameters for
UDF?
Is it feasible to put some kind of filter driver in front of the DVD-ROM? (What do you call them on Win98?)
I currently pass “D:\VIDEO_TS” into the driver, and I could figure out how to insert another driver in front of the DVD-ROM. My
concern is that if I did that, the CSS stuff would get in the way, and make this approach a dead-end. This is for a real
product, and it has to play by whatever legal rules there are. Is something like a filter driver feasible or should I be
focusing on the alternatives?
Thanks,
-DH
Dave Harvey, System Software Solutions, Inc.
617-964-7039, FAX 208-361-9395, xxxxx@syssoftsol.com, http://www.syssoftsol.com
Creators of RedunDisks - Robust RAID 1 for embedded systems.
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com