DScaler Deinterlacer/Scaler

> 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);

I meant to say, the *fix* is to *make* that change to dTVdrv.cpp (backing
out the opposite change in the previous revision).

-Steve

Steve -

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.

- Tom

> -----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.
>
> -Steve
> _______________________________________________
> Deinterlace-discuss mailing list
> Deinterlace-discuss@...
> http://lists.sourceforge.net/mailman/listinfo/deinterlace-discuss
>

> ...
> 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.

I always run dTV.exe from the Release directory, which is where the build
process puts it.  The various support files including the DLL are there
too.  I don't think I ever had to manually move them there.

-Steve

Steve -

I'm running in the debug environment so my modules got put in the Debug
instead of Release directory, but the same logic should apply.  I'm not sure
how you make it work that way.  If I set the current working directory to
\dTVdev\dtv\ then I can't find the dTVdrv.vxd file without the questionable
fix I put it.  If I set the current working directory to \dTVdev\dtv\debug\
then it finds the vxd but does not find the channel.txt file.

I used CVS to make all this fresh about a month ago and this was where
things got put.  Do you have dTV.exe, dTVdrv.vxd, and channel.txt all in the
release directory?  Do you have to set a working directory in the VS6
workspace to make it work?

- Tom


> -----Original Message-----
> From: deinterlace-discuss-admin@...
> [mailto:deinterlace-discuss-admin@... Behalf Of
> Steven Grimm
> Sent: Tuesday, November 28, 2000 4:12 PM
> To: deinterlace-discuss@...
> Subject: Re: [Deinterlace-discuss] "No suitable hardware" message
>
>
> > ...
> > 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.
>
> I always run dTV.exe from the Release directory, which is where the build
> process puts it.  The various support files including the DLL are there
> too.  I don't think I ever had to manually move them there.
>
> -Steve
> _______________________________________________
> Deinterlace-discuss mailing list
> Deinterlace-discuss@...
> http://lists.sourceforge.net/mailman/listinfo/deinterlace-discuss
>