Sometimes it scans, find 22 channels and when done all works as it should.
Then after a while, the channels disappear.

Rescanning (the long scan) appears to work, (again 22 chans) but at the end
the channels are not tuned in right, switching up for example gives about
50 msec of the channel video and sound and then noise.

Is there some reason for this flakiness?

running XP Pro 512RAM
catalyst 7-94-03917m-011234c
mmc 8-7-0-0

once in a while it works perfectly.

Is there any software out there to help the tuner keep its settings? I've
had problems with the tuner in two computers. It seems to me it just needs
a small tweak to work.

Anyone know if there are driver improvements that especially concern the
tuner

Uzytkownik "BlueRinse" <brinse-(E-Mail Removed)> napisal w
wiadomosci news:vyped8ddfz9j$.(E-Mail Removed)...
> Sometimes it scans, find 22 channels and when done all works as it should.
> Then after a while, the channels disappear.
>
> Rescanning (the long scan) appears to work, (again 22 chans) but at the
end
> the channels are not tuned in right, switching up for example gives about
> 50 msec of the channel video and sound and then noise.

Known problem with DirectX 9.0b. See
http://www.rage3d.com/board/showthre...0&pagenumber=7

Rgrds
SZ

On Sat, 25 Oct 2003 19:36:37 +0200, Slawomir Zaboklicki wrote:

> Known problem with DirectX 9.0b. See
> http://www.rage3d.com/board/showthre...0&pagenumber=7
Thx, there's a lot to read there but I haven't seen one with the exact
problem I have. The tuner "works" on all functions ecept that it won't tune
after scanning. Further, channel surf works!

I just tried something: I entered a new channel, 550.55 and as soon as I
hit enter the channel was perfectly tuned (I just guessed the freq.)
However, as soon as I add the channel, the box comes back and says it finds
no signal. Re-entering 550.55 says "channel 23 is already tuned to that
frequency"

I'm going to post on that forum and see.

Any commens here are more than welcome!

"BlueRinse" <brinse-(E-Mail Removed)> wrote in message
news:1qsfvdkvwvse5.y66db1lbz8uj$.(E-Mail Removed)...
> On Sat, 25 Oct 2003 19:36:37 +0200, Slawomir Zaboklicki wrote:
>
> > Known problem with DirectX 9.0b. See
> >
http://www.rage3d.com/board/showthre...0&pagenumber=7
> Thx, there's a lot to read there but I haven't seen one with the exact
> problem I have. The tuner "works" on all functions ecept that it won't
tune
> after scanning. Further, channel surf works!
>
> I just tried something: I entered a new channel, 550.55 and as soon as I
> hit enter the channel was perfectly tuned (I just guessed the freq.)
> However, as soon as I add the channel, the box comes back and says it
finds
> no signal. Re-entering 550.55 says "channel 23 is already tuned to that
> frequency"
>
> I'm going to post on that forum and see.
>
> Any commens here are more than welcome!


The bottom line on the DirectX 9.0b problem is that it affects PAL, SECAM
and some non-USA NTSC tuners, BR. If you're not using DX 9.0b or you're
using a US NTSC tuner, then it would seem it can't be the problem; if you
are using DX 9.0b and and a PAL, SECAM or non-US NTSC tuner, it's probably
something to do with what's happening.

patrickp

On Sun, 26 Oct 2003 14:40:12 -0000, patrickp wrote:

> are using DX 9.0b and and a PAL, SECAM or non-US NTSC tuner, it's probably
> something to do with what's happening.

I can't believe I forgot to mention I am using PAL - stupid of me. But I
installed the .ax file of 9a and it worked once and then stopped. After it
stopped, it refused to even scen for channels and the screen no longer
showed noise but was white. I put the 9b one back. By the way, the dates on
the thread are from July I think. There still is no fix?

Channel surf works but tuning the channels does not. I have been posting on
the web board and we'll see if ATI chimes in. Maybe I should try 9.0?

"BlueRinse" <brinse-(E-Mail Removed)> wrote in message
news:uezaa6w0hjwq$.(E-Mail Removed)...
> On Sun, 26 Oct 2003 14:40:12 -0000, patrickp wrote:
>
> > are using DX 9.0b and and a PAL, SECAM or non-US NTSC tuner, it's
probably
> > something to do with what's happening.
>
> I can't believe I forgot to mention I am using PAL - stupid of me. But I
> installed the .ax file of 9a and it worked once and then stopped. After it
> stopped, it refused to even scen for channels and the screen no longer
> showed noise but was white. I put the 9b one back. By the way, the dates
on
> the thread are from July I think. There still is no fix?
>
> Channel surf works but tuning the channels does not. I have been posting
on
> the web board and we'll see if ATI chimes in. Maybe I should try 9.0?


There's two fixes, BR, the official one from M$, which you can get at
http://www.microsoft.com/downloads/d...displaylang=en,
although M$ still don't warn potential DirectX 9.0b users of the problem,
and don't make the fix easy to find. Also, people have reported it's not
always successful.

The other, earlier, fix is from
http://www.mustafa.pwp.blueyonder.co.uk/fix.zip and seemingly usually works.

HTH patrickp

> There's two fixes, BR, the official one from M$, which you can get at
> http://www.microsoft.com/downloads/d...displaylang=en,
> although M$ still don't warn potential DirectX 9.0b users of the problem,
> and don't make the fix easy to find. Also, people have reported it's not
> always successful.
> The other, earlier, fix is from
> http://www.mustafa.pwp.blueyonder.co.uk/fix.zip and seemingly usually works.
Thanks for those Patrick.

The MS one doesn't change anything. The second one which appears to use the
same file as I tried from 9a (same date and size) made the tuner hang and
the system unstable. I am still looking for something that actually works
but I guess I shouldn't hold my breath. Maybe the card went bad.

On Mon, 27 Oct 2003 07:37:29 -0000, patrickp wrote:

> There's two fixes, BR, the official one from M$, which you can get at
> http://www.microsoft.com/downloads/d...displaylang=en,
> although M$ still don't warn potential DirectX 9.0b users of the problem,
> and don't make the fix easy to find.

Patrick, after trying both the fixes you mentioned, I gave up and
re-installed the "original" 9b file. To do this, I did a search for the
name on C: then I made up a batch file to copy the file to all those
locations figuring if that if any new versions came out I'd be ready.

Strangely enough, after using the above to put that driver back to 9b, I
decided (since it still didn't work) to go ahead and install the MS path.
After doing this and rebooting (even tho the MS patch doesn't tell you to)
the tuner now works, although I don't dare do a new channel scan. I hope it
continues to function since a card without a tuner would be less expensive.

At any rate, thanks much for the fix - I appreciate your help especially
since MS and AIT don't make it easy to find. Now le's hope MS doesn't break
it next update of DX!

"BlueRinse" <brinse-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Mon, 27 Oct 2003 07:37:29 -0000, patrickp wrote:
>
> > There's two fixes, BR, the official one from M$, which you can get at
> >
http://www.microsoft.com/downloads/d...displaylang=en,
> > although M$ still don't warn potential DirectX 9.0b users of the
problem,
> > and don't make the fix easy to find.
>
> Patrick, after trying both the fixes you mentioned, I gave up and
> re-installed the "original" 9b file. To do this, I did a search for the
> name on C: then I made up a batch file to copy the file to all those
> locations figuring if that if any new versions came out I'd be ready.
>
> Strangely enough, after using the above to put that driver back to 9b, I
> decided (since it still didn't work) to go ahead and install the MS path.
> After doing this and rebooting (even tho the MS patch doesn't tell you to)
> the tuner now works, although I don't dare do a new channel scan. I hope
it
> continues to function since a card without a tuner would be less
expensive.
>
> At any rate, thanks much for the fix - I appreciate your help especially
> since MS and AIT don't make it easy to find. Now le's hope MS doesn't
break
> it next update of DX!


Good to hear you've got it working, BR - I'd say that, for once, this one
isn't ATi's fault, though.

It's possible, I guess, that the M$ fix looks for the "original" DX 9.0bfile
to fix it, and since AIR you had replaced it, didn't run the fix. Then when
you restored it, it was able to.

patrickp