Oops! My bad. I hadn't intended to release that 'fix' but it snuck out with
the Blended Clip stuff. It seemed to work so I left it.
I don't understand that code but I think the problem has something to do
with the difference in where we expect to find the drivers in the dev versus
shipped binary releases. When I put up WinMe I would get the 'no hardware'
message because we don't keep dTVdrv.dll in the same directory as dTV.exe.
This seemed to fix it but I guess at the expense of our users.
Can you compile and run from source now? Or do you have to move copies of
some modules to the same directory as dTV.exe? Maybe I am just missing some
path variable or something.
> -----Original Message-----
> From: deinterlace-discuss-admin@...
> [mailto:deinterlace-discuss-admin@... Behalf Of
> Steven Grimm
> Sent: Tuesday, November 28, 2000 11:43 AM
> To: deinterlace-discuss@...
> Subject: [Deinterlace-discuss] "No suitable hardware" message
> It's not a Win2K issue; it happens to me on Win98 too. The culprit
> is this change to dTVdrv.cpp:
> < // strcpy(szDriverPath,pszDriverName); // <-- was this way
> < strcat(szDriverPath,pszDriverName); //
> <-- should it be this?
> > strcpy(szDriverPath,pszDriverName);
> Backing it out now. Yeah, I know it was probably intended to fix
> something, but it seems to be causing more problems than it's solving
> for users in the field, judging by the AVSForum feedback. So reverting
> to previous behavior seems like the thing to do.
> Deinterlace-discuss mailing list