Has anyone found out the resolution to this yet ? please !?
Something to do witht the "toggle bit" that isnt being translated propperly ?!

Cheers,
Mike

Mike,

I found that this happened when I had the remote IR speed set to "High" in
MCE setup. I changed it to "Normal" and everything worked perfectly.

Regards,

RoryD.

"Mike" <Mike@discussions.microsoft.com> wrote in message
news:1B733EA0-1B16-4FE7-9AFC-0596E47B43DD@microsoft.com...
> Has anyone found out the resolution to this yet ? please !?
> Something to do witht the "toggle bit" that isnt being translated
> propperly ?!
>
> Cheers,
> Mike
>

Cheers but i have tried this . and didnt work

"RoryD" wrote:

> Mike,
>
> I found that this happened when I had the remote IR speed set to "High" in
> MCE setup. I changed it to "Normal" and everything worked perfectly.
>
> Regards,
>
> RoryD.
>
> "Mike" <Mike@discussions.microsoft.com> wrote in message
> news:1B733EA0-1B16-4FE7-9AFC-0596E47B43DD@microsoft.com...
> > Has anyone found out the resolution to this yet ? please !?
> > Something to do witht the "toggle bit" that isnt being translated
> > propperly ?!
> >
> > Cheers,
> > Mike
> >
>
>
>

Try slightly adjusting the position of the IR blaster over the STB's IR
sensor and see if that helps.

Regards,«
--
Robert Schlabbach
e-mail: robert_s@gmx.net
Berlin, Germany

"Mike" <Mike@discussions.microsoft.com> wrote in message news:A3765048-50B9-44F1-ADFC-C7A2F238550F@microsoft.com...
> Cheers but i have tried this . and didnt work
>
> "RoryD" wrote:
>
> > Mike,
> >
> > I found that this happened when I had the remote IR speed set to "High" in
> > MCE setup. I changed it to "Normal" and everything worked perfectly.
> >
> > Regards,
> >
> > RoryD.
> >
> > "Mike" <Mike@discussions.microsoft.com> wrote in message
> > news:1B733EA0-1B16-4FE7-9AFC-0596E47B43DD@microsoft.com...
> > > Has anyone found out the resolution to this yet ? please !?
> > > Something to do witht the "toggle bit" that isnt being translated
> > > propperly ?!
> > >
> > > Cheers,
> > > Mike
> > >
> >
> >
> >

Robert Schlabbach wrote:
> Try slightly adjusting the position of the IR blaster over the STB's IR
> sensor and see if that helps.
> Regards,«

I have already mentioned this but I'll suggest it again.
(You never know..) I recognize this this problem with my
Samsung STB (not NTL box)

I changed to "I use the OK key to change channel" and then
fed a dummy IR code to represent "OK". Use another "junk"
remote for that. It worked. You get rid of leading zero's
that way.

kalev- wrote:
> Robert Schlabbach wrote:
>> Try slightly adjusting the position of the IR blaster over the STB's IR
>> sensor and see if that helps.
>> Regards,«
>
> I have already mentioned this but I'll suggest it again.
> (You never know..) I recognize this this problem with my Samsung STB
> (not NTL box)
>
> I changed to "I use the OK key to change channel" and then fed a dummy
> IR code to represent "OK". Use another "junk" remote for that. It
> worked. You get rid of leading zero's that way.

Here is another very recent post, off the green button
forum. This is similar to but NOT EXACT to what I had to do

(sorry if it still doesn't help...)

----------
Fixed!

I would definitely recommend adding this "tip" to your
document. May not happen often but could be a lifesaver for
those that run into the problem I had...

After messing around and reading posts for 4 hours straight
I finally figured it out. I read an unrelated post that
stated press number zero then turn the remote away and press
number 1 ... This unrelated idea to turn the remote away
combined with a statement in the document in this post about
needing to get an identical signal to ensure no mistakes
made me try the following:

I thought about this for a moment and tried pressing 1 while
pointing at the ir receiver, then turning the remote away
from the ir receiver (actually pointed it in a sweatshirt to
make sure no signal was received) and pressing 1, then
turning the remote back at the ir receiver and pressing 1
again. It worked! Channel learned. I repeated this
process for all channels and not only did they get learned
but they now work flawlessly.

Somehow my remote must toggle between signals and mce could
not get a consistent signal to learn on consecutive
attempts. By covering up the remote I tricked mce into
getting a consistent signal. Still puzzled why the remote
does this as the STB works fine with MCE now sending a
constant signal (it did not learn the alternating signal so
it must just know the non alternating signal I taught it).

Thanks, Rob

Thankyou so much for replying, this is driving me completely insane,
at the moment MCE is sitting there with a clean install and fully updated
doing
absolutly nothing.

I have tried what was suggested before I rebuilt the machine and yes the
remote seems to learn just fine each button 1,2,3,4,5,6,7 etc etc.. but still
the issue was
still there..

But I will try it again tonight when i get home, hopfully the updates that
werent installed when i last tried it will have solved "a" issue..

I will let you know how it goes, I cant believe this is still causing so many
problems for people, simply not good enough!!

Normally I cant get enough of technology, but this is truley starting to
pi$$ me right off, its extreamly frustrating, and most replys i get from
various
forums/groups is "have you adjusted the ir repeat rate etc" !! you have any
idea how annoying that is !? its like, yes I have!! almost thousands of
times, including
very slighly via the registry as suggested my microsoft to solve this
problem (in one of there KB articles) which supprise supprise didnt solve
anthing ... siigh..

Sorry, moaning a little too much.. well im hoping it will be working tonight
and i can come back and share with everyone how exactly i did it, and then
can truley title a post "NTL Samsung 2100c repetative channel number -
SOLVED!!! "

Fingers crossed

BTW thanks everyone for trying, it is appreciated

Mike


"kalev-" wrote:

> kalev- wrote:
> > Robert Schlabbach wrote:
> >> Try slightly adjusting the position of the IR blaster over the STB's IR
> >> sensor and see if that helps.
> >> Regards,«
> >
> > I have already mentioned this but I'll suggest it again.
> > (You never know..) I recognize this this problem with my Samsung STB
> > (not NTL box)
> >
> > I changed to "I use the OK key to change channel" and then fed a dummy
> > IR code to represent "OK". Use another "junk" remote for that. It
> > worked. You get rid of leading zero's that way.
>
> Here is another very recent post, off the green button
> forum. This is similar to but NOT EXACT to what I had to do
>
> (sorry if it still doesn't help...)
>
> ----------
> Fixed!
>
> I would definitely recommend adding this "tip" to your
> document. May not happen often but could be a lifesaver for
> those that run into the problem I had...
>
> After messing around and reading posts for 4 hours straight
> I finally figured it out. I read an unrelated post that
> stated press number zero then turn the remote away and press
> number 1 ... This unrelated idea to turn the remote away
> combined with a statement in the document in this post about
> needing to get an identical signal to ensure no mistakes
> made me try the following:
>
> I thought about this for a moment and tried pressing 1 while
> pointing at the ir receiver, then turning the remote away
> from the ir receiver (actually pointed it in a sweatshirt to
> make sure no signal was received) and pressing 1, then
> turning the remote back at the ir receiver and pressing 1
> again. It worked! Channel learned. I repeated this
> process for all channels and not only did they get learned
> but they now work flawlessly.
>
> Somehow my remote must toggle between signals and mce could
> not get a consistent signal to learn on consecutive
> attempts. By covering up the remote I tricked mce into
> getting a consistent signal. Still puzzled why the remote
> does this as the STB works fine with MCE now sending a
> constant signal (it did not learn the alternating signal so
> it must just know the non alternating signal I taught it).
>
> Thanks, Rob
>

Guess what......................

Its STILL doesnt work

Someone... please..... Help !!!!

Cheers,
Mike


"Mike" wrote:

> Thankyou so much for replying, this is driving me completely insane,
> at the moment MCE is sitting there with a clean install and fully updated
> doing
> absolutly nothing.
>
> I have tried what was suggested before I rebuilt the machine and yes the
> remote seems to learn just fine each button 1,2,3,4,5,6,7 etc etc.. but still
> the issue was
> still there..
>
> But I will try it again tonight when i get home, hopfully the updates that
> werent installed when i last tried it will have solved "a" issue..
>
> I will let you know how it goes, I cant believe this is still causing so many
> problems for people, simply not good enough!!
>
> Normally I cant get enough of technology, but this is truley starting to
> pi$$ me right off, its extreamly frustrating, and most replys i get from
> various
> forums/groups is "have you adjusted the ir repeat rate etc" !! you have any
> idea how annoying that is !? its like, yes I have!! almost thousands of
> times, including
> very slighly via the registry as suggested my microsoft to solve this
> problem (in one of there KB articles) which supprise supprise didnt solve
> anthing ... siigh..
>
> Sorry, moaning a little too much.. well im hoping it will be working tonight
> and i can come back and share with everyone how exactly i did it, and then
> can truley title a post "NTL Samsung 2100c repetative channel number -
> SOLVED!!! "
>
> Fingers crossed
>
> BTW thanks everyone for trying, it is appreciated
>
> Mike
>
>
> "kalev-" wrote:
>
> > kalev- wrote:
> > > Robert Schlabbach wrote:
> > >> Try slightly adjusting the position of the IR blaster over the STB's IR
> > >> sensor and see if that helps.
> > >> Regards,«
> > >
> > > I have already mentioned this but I'll suggest it again.
> > > (You never know..) I recognize this this problem with my Samsung STB
> > > (not NTL box)
> > >
> > > I changed to "I use the OK key to change channel" and then fed a dummy
> > > IR code to represent "OK". Use another "junk" remote for that. It
> > > worked. You get rid of leading zero's that way.
> >
> > Here is another very recent post, off the green button
> > forum. This is similar to but NOT EXACT to what I had to do
> >
> > (sorry if it still doesn't help...)
> >
> > ----------
> > Fixed!
> >
> > I would definitely recommend adding this "tip" to your
> > document. May not happen often but could be a lifesaver for
> > those that run into the problem I had...
> >
> > After messing around and reading posts for 4 hours straight
> > I finally figured it out. I read an unrelated post that
> > stated press number zero then turn the remote away and press
> > number 1 ... This unrelated idea to turn the remote away
> > combined with a statement in the document in this post about
> > needing to get an identical signal to ensure no mistakes
> > made me try the following:
> >
> > I thought about this for a moment and tried pressing 1 while
> > pointing at the ir receiver, then turning the remote away
> > from the ir receiver (actually pointed it in a sweatshirt to
> > make sure no signal was received) and pressing 1, then
> > turning the remote back at the ir receiver and pressing 1
> > again. It worked! Channel learned. I repeated this
> > process for all channels and not only did they get learned
> > but they now work flawlessly.
> >
> > Somehow my remote must toggle between signals and mce could
> > not get a consistent signal to learn on consecutive
> > attempts. By covering up the remote I tricked mce into
> > getting a consistent signal. Still puzzled why the remote
> > does this as the STB works fine with MCE now sending a
> > constant signal (it did not learn the alternating signal so
> > it must just know the non alternating signal I taught it).
> >
> > Thanks, Rob
> >

Mike wrote:

> Guess what......................
> Its STILL doesnt work
> Someone... please..... Help !!!!
> Cheers,
> Mike

1) Mike, have you been successful in feeding in all the digits into MCE?
Including the zero and the OK key? (The IR-code learning phase)

2) Have you gotten the impression that the STB is a fairly recent and "fast"
model? Ie. if you press keys sequentially QUICKLY on the original remote
does the STB seem to keep up (in receiving the codes) with channel changes?
(This may seem like a *lame* question, but I have an older STB (not Samsung)
as well which cannot keep up. This may be for an unrelated - but there it
goes..

3) With the original remote: can you go to "channel one" (I'm assuming that
your channel line up has a channel on position one) by doing these
individual tests QUICKLY <-- press sequential keys on the remote QUICKLY.

What happens, do all of these tests succeed?

Test one Press: 1
Test two Press: 01
Test three Press: 001
Test four Press: 1 [OK button]

Hey Kalev, again thankyou for sticking this through man.

1) Yep I am successful in feeding all digits into MCE, only works if another
digit is pressed whilst pointing remote away from the reciever, then back
again.
This seems to work flawlessley.

Although I've been wondering if this is to do with this so called "toggle
bit" how do i know at which state it should be learned ?
eg. when i first start to learn the code how would i know when i press the
first digit if the toggle bit is set to a binary 0 or a binary 1, do you
think it would need to be learnt as always toggle bit of "0" (off). hard to
explain to you see where im coming from though ? I guess maybe by removing
the batterys for a while then trying, i could be sure the toggle bit will be
reset. Do you think this would matter or aslong as the code is the same
regardless weather the toggle bit is on or off it will be ok ?

2) The STB is new, i was with the engineer when he was unpacking it from
its packaging, and the channels change without problems when its remote is
used,
in fact i cant get it to go wrong no matter how fast i press the channel
numbers.
It seems really responsive. Ive also adjusted the timing vaules in the
registry to make it throw out ir signals very fast and it will accepts !!
although of course it doesnt when theres a repetative number involved

3) NTL starts from channel 101 here in the UK (101 being BBC1).
Ive never actually experienced the leading zero problem as there is
always a minimum of three characters and as it starts from 101 there
is no space for a zero at the begining, the STB has 3 characters for
displaying channels.

Sorry Kalev, but do you use the Samsung 2100c stb yourself ? or do you know
anyone that has actually managed to get it to work with MCE ? i cant
remember if ive asked you this before ive noticed a lot of
threads are apearing in various forums regarding this same issue, and the only
solution is always "Dumped NTL and went with sky" or "Dumped MCE and went
with TIVO" !

Im shocked as it seems Microsoft dont seem to care that this is happening,
if they
are really serious about moving "PC's into living rooms" etc etc they really
need to get their act together and iron out ALL of these problems.

Before I got this dreaded STB i was happy to recommend MCE to everyone, but
now Its just not possible, ive had to explain to at least 5 of my coleuges
that have NTL and these samsung 2100c boxes thats theres no point as it just
doesnt work!!
so thats 5 CAL's thats arnt going to be brought from MS.

Do the guys at Microsoft actually bother reading these posts do you think ?

Cheers Kalev,
Mike


"kalev-" wrote:

> Mike wrote:
>

> > Guess what......................
> > Its STILL doesnt work
> > Someone... please..... Help !!!!
> > Cheers,
> > Mike
>
> 1) Mike, have you been successful in feeding in all the digits into MCE?
> Including the zero and the OK key? (The IR-code learning phase)
>
> 2) Have you gotten the impression that the STB is a fairly recent and "fast"
> model? Ie. if you press keys sequentially QUICKLY on the original remote
> does the STB seem to keep up (in receiving the codes) with channel changes?
> (This may seem like a *lame* question, but I have an older STB (not Samsung)
> as well which cannot keep up. This may be for an unrelated - but there it
> goes..
>
> 3) With the original remote: can you go to "channel one" (I'm assuming that
> your channel line up has a channel on position one) by doing these
> individual tests QUICKLY <-- press sequential keys on the remote QUICKLY.
>
> What happens, do all of these tests succeed?
>
> Test one Press: 1
> Test two Press: 01
> Test three Press: 001
> Test four Press: 1 [OK button]
>
>
>

Mike wrote:
> 1) Yep I am successful in feeding all digits into MCE, only works if
> another digit is pressed whilst pointing remote away from the reciever,
> then back again. This seems to work flawlessley.

I *think* I only had to do the: "move remote away first" -procedure with the
"zero" and the "OK". As far as "Missing digits" go (as your subject line
says) I fixed with a junk "OK" transmission at the end.


> Although I've been wondering if this is to do with this so called "toggle
> bit" how do i know at which state it should be learned ?

Yeah, I hear you, dunno. (Maybe I *was* just lucky)
If you look at your subject line - does the STB specifically miss the last
digit if digits repeat? ...may be worth pondering. (= Is the error that the
last digit gets nuked for "some" reason? Or is it always the first? <-
knowing this could help.

> I guess maybe by
> removing the batterys for a while then trying, i could be sure the toggle
> bit will be reset. Do you think this would matter or aslong as the code is
> the same regardless weather the toggle bit is on or off it will be ok ?

Don't have an answer. I think that you *are* close at cracking this and you
need to figure out a way to trick the STB somehow. What the STB expects vs.
the IR-blasting capabilities/limitations of MCE. I'm thinking that you
don't have a speed issue at all. (= a hunch)

> 3) NTL starts from channel 101 here in the UK (101 being BBC1).
> Ive never actually experienced the leading zero problem as there is
> always a minimum of three characters and as it starts from 101 there
> is no space for a zero at the begining, the STB has 3 characters for
> displaying channels.

You "told" MCE that your STB uses 3 digits? (thinking..)
How does the STB react if you enter 101[OK] ? Does the STB freak out with
an OK at the end? Or is this "a proper transmission" The STB stays happy?

How about 0101 or 00101 entered quickly? Leading zeros are OK? (Yes I know
you said the STB uses 3 digits, but the point is to see if there's a way to
get past the problem - bypass any "toggle" issue. In this case an initial
code *or* an ending code from MCE might help.)
It would be interesting to know.

To repeat:
Perhaps you can trick the STB "toggling" by feeding it something in front or
behind. (This may not be perfect science -- perhaps even wrong - but all
you want is for the darn STB and MCE to change channels properly.)

As a follow up, one idea is to test: "I use 4 digits" and see how the STB
reacts. (Yes, I know you said it only uses 3.) Still wrong? but it responds
differently?

I'm going down this path since a) I still think there's a chance to fool
your STB into accepting the MCE IR codes. b) For some reason I think it's a
similar problem with other Samsung STBs -- even though they *are*
different when sold into different regions (= I have a hard time believing
that their IR modules have to be *so* very different) If, they are
built/designed during the same time-period.

> Sorry Kalev, but do you use the Samsung 2100c stb yourself?

No, but I do also have a "new" Samsung STB for DVB-C for the swedish market
DCB-9401Z. ("9401" are available in a a ton of different localized
versions) I also had to "fool it" to work with MCE codes. A "IR-toggling
problem" I had as well. I got away with it though. I still have a hunch
that there's way you can fix it.

> Im shocked as it seems Microsoft dont seem to care that this is happening,
> if they
> are really serious about moving "PC's into living rooms" etc etc they
> really need to get their act together and iron out ALL of these problems.

I feel for you!

Hi guys I have been watching this post with interest as I to have ntl
(smt2100c) and a media center that will not do double digits, i have tried
everything you have already posted including the reg hack from microsoft all
to no avail. i have also tried other progs such as media portal etc to learn
the remote into the mce blaster again still no good so I have decided that
it is the C$$p set top box that just will not see the double digits from the
blaster.
Before the samsung i had a pace box from ntl which worked great untill it
blew up now im stuck with a box that does not change the channel right.

anyway just wanted to say you are not on your own and if someone has the
answear then come on help all us samsung ntl user out.
regards basky.

"kalev-" wrote:

> Mike wrote:
> > 1) Yep I am successful in feeding all digits into MCE, only works if
> > another digit is pressed whilst pointing remote away from the reciever,
> > then back again. This seems to work flawlessley.
>
> I *think* I only had to do the: "move remote away first" -procedure with the
> "zero" and the "OK". As far as "Missing digits" go (as your subject line
> says) I fixed with a junk "OK" transmission at the end.
>
>
> > Although I've been wondering if this is to do with this so called "toggle
> > bit" how do i know at which state it should be learned ?
>
> Yeah, I hear you, dunno. (Maybe I *was* just lucky)
> If you look at your subject line - does the STB specifically miss the last
> digit if digits repeat? ...may be worth pondering. (= Is the error that the
> last digit gets nuked for "some" reason? Or is it always the first? <-
> knowing this could help.
>
> > I guess maybe by
> > removing the batterys for a while then trying, i could be sure the toggle
> > bit will be reset. Do you think this would matter or aslong as the code is
> > the same regardless weather the toggle bit is on or off it will be ok ?
>
> Don't have an answer. I think that you *are* close at cracking this and you
> need to figure out a way to trick the STB somehow. What the STB expects vs.
> the IR-blasting capabilities/limitations of MCE. I'm thinking that you
> don't have a speed issue at all. (= a hunch)
>
> > 3) NTL starts from channel 101 here in the UK (101 being BBC1).
> > Ive never actually experienced the leading zero problem as there is
> > always a minimum of three characters and as it starts from 101 there
> > is no space for a zero at the begining, the STB has 3 characters for
> > displaying channels.
>
> You "told" MCE that your STB uses 3 digits? (thinking..)
> How does the STB react if you enter 101[OK] ? Does the STB freak out with
> an OK at the end? Or is this "a proper transmission" The STB stays happy?
>
> How about 0101 or 00101 entered quickly? Leading zeros are OK? (Yes I know
> you said the STB uses 3 digits, but the point is to see if there's a way to
> get past the problem - bypass any "toggle" issue. In this case an initial
> code *or* an ending code from MCE might help.)
> It would be interesting to know.
>
> To repeat:
> Perhaps you can trick the STB "toggling" by feeding it something in front or
> behind. (This may not be perfect science -- perhaps even wrong - but all
> you want is for the darn STB and MCE to change channels properly.)
>
> As a follow up, one idea is to test: "I use 4 digits" and see how the STB
> reacts. (Yes, I know you said it only uses 3.) Still wrong? but it responds
> differently?
>
> I'm going down this path since a) I still think there's a chance to fool
> your STB into accepting the MCE IR codes. b) For some reason I think it's a
> similar problem with other Samsung STBs -- even though they *are*
> different when sold into different regions (= I have a hard time believing
> that their IR modules have to be *so* very different) If, they are
> built/designed during the same time-period.
>
> > Sorry Kalev, but do you use the Samsung 2100c stb yourself?
>
> No, but I do also have a "new" Samsung STB for DVB-C for the swedish market
> DCB-9401Z. ("9401" are available in a a ton of different localized
> versions) I also had to "fool it" to work with MCE codes. A "IR-toggling
> problem" I had as well. I got away with it though. I still have a hunch
> that there's way you can fix it.
>
> > Im shocked as it seems Microsoft dont seem to care that this is happening,
> > if they
> > are really serious about moving "PC's into living rooms" etc etc they
> > really need to get their act together and iron out ALL of these problems.
>
> I feel for you!
>

basky wrote:
> Hi guys I have been watching this post with interest as I to have ntl
> (smt2100c) and a media center that will not do double digits, i have tried
> everything you have already posted including the reg hack from microsoft all
> to no avail.

A question:
Will it still not see double digits if you set MCE to "4
digits"? (or does the problem at least "change" ?)

no kalev,
its still the same does not make any difference if you use 4 digits or 3 or
2 or if i use an ok/enter after the numbers it just will not see 2 digits
together?????

"kalev-" wrote:

> basky wrote:
> > Hi guys I have been watching this post with interest as I to have ntl
> > (smt2100c) and a media center that will not do double digits, i have tried
> > everything you have already posted including the reg hack from microsoft all
> > to no avail.
>
> A question:
> Will it still not see double digits if you set MCE to "4
> digits"? (or does the problem at least "change" ?)
>

Basky, Hi there sorry still no luck from my side either

Kalev, hey mate not been around this weekend hence the
lack of moaning/posting I also went through your suggestions
and got the same results as basky, this is a nightmare

Ive heard reports that it is actuallly Microsofts implementation of the RC5/6
protocol ?, do you/anyone know if this is true ?

I will try this all again tonight, again with removing the batters from the
remote RE: my suggestion few posts ago... about resetting the toggle bit
back to
its default state.. whatever that maybe ..."0"? !.

something ive been thinking about :
At home I have a light switch that uses IR to turn on and
off and dim the bulb. by "tapping" the button on the remote it turns
the light on and off, by pressing and holding the button down it dims the
light, Im thinking that to so this using the same button on the remote, it
must use the so called "toggle bit" do you think im right ? my dodgy learning
remote seemed to learn this code without issues and works flawlesly so im
thinking
i might try and learn the ntl remote using this learning remote control and
feeding the newley learned codes into MCE using the universal remote instead
of the samsung remote... humm the more i write this the more it doesnt make
sense lol..

Ahhh sod it i need to grab at straws !! just need this to work!!

Maybe ive said something that will jog someones memory etc..

Hope you guys had a nice weekend.

PS if anyone else is having this issue please dont just
watch this post grow, have your say, maybe, just maybe
Microsoft might see this is a big problem and do something
about it ! or at least point us in the right direction

Many thanks,
Mike


"basky" wrote:

> no kalev,
> its still the same does not make any difference if you use 4 digits or 3 or
> 2 or if i use an ok/enter after the numbers it just will not see 2 digits
> together?????
>
> "kalev-" wrote:
>
> > basky wrote:
> > > Hi guys I have been watching this post with interest as I to have ntl
> > > (smt2100c) and a media center that will not do double digits, i have tried
> > > everything you have already posted including the reg hack from microsoft all
> > > to no avail.
> >
> > A question:
> > Will it still not see double digits if you set MCE to "4
> > digits"? (or does the problem at least "change" ?)
> >

Mike,
sorry mate but i have already tried the uni remote thing i have a all in one
that learns the set top box remote codes great then i tried to put that
remote into media center, makes no differance at all
I still think it is something to do with the samsung box using a different
code for the second digit, I have also tried using the old remote that come
with my first stb which was a pace and again it will change the stb ok but
not if you learn it into media center
pass i,m lost i have tried every trick in the book to get this going and
none of them work something will have to go and at the moment it looks like
its going to be ntl!!!


"Mike" wrote:

> Basky, Hi there sorry still no luck from my side either
>
> Kalev, hey mate not been around this weekend hence the
> lack of moaning/posting I also went through your suggestions
> and got the same results as basky, this is a nightmare
>
> Ive heard reports that it is actuallly Microsofts implementation of the RC5/6
> protocol ?, do you/anyone know if this is true ?
>
> I will try this all again tonight, again with removing the batters from the
> remote RE: my suggestion few posts ago... about resetting the toggle bit
> back to
> its default state.. whatever that maybe ..."0"? !.
>
> something ive been thinking about :
> At home I have a light switch that uses IR to turn on and
> off and dim the bulb. by "tapping" the button on the remote it turns
> the light on and off, by pressing and holding the button down it dims the
> light, Im thinking that to so this using the same button on the remote, it
> must use the so called "toggle bit" do you think im right ? my dodgy learning
> remote seemed to learn this code without issues and works flawlesly so im
> thinking
> i might try and learn the ntl remote using this learning remote control and
> feeding the newley learned codes into MCE using the universal remote instead
> of the samsung remote... humm the more i write this the more it doesnt make
> sense lol..
>
> Ahhh sod it i need to grab at straws !! just need this to work!!
>
> Maybe ive said something that will jog someones memory etc..
>
> Hope you guys had a nice weekend.
>
> PS if anyone else is having this issue please dont just
> watch this post grow, have your say, maybe, just maybe
> Microsoft might see this is a big problem and do something
> about it ! or at least point us in the right direction
>
> Many thanks,
> Mike
>
>
> "basky" wrote:
>
> > no kalev,
> > its still the same does not make any difference if you use 4 digits or 3 or
> > 2 or if i use an ok/enter after the numbers it just will not see 2 digits
> > together?????
> >
> > "kalev-" wrote:
> >
> > > basky wrote:
> > > > Hi guys I have been watching this post with interest as I to have ntl
> > > > (smt2100c) and a media center that will not do double digits, i have tried
> > > > everything you have already posted including the reg hack from microsoft all
> > > > to no avail.
> > >
> > > A question:
> > > Will it still not see double digits if you set MCE to "4
> > > digits"? (or does the problem at least "change" ?)
> > >

basky wrote:

> Mike,
> sorry mate but i have already tried the uni remote thing i have a all in
> one that learns the set top box remote codes great then i tried to put
> that remote into media center, makes no differance at all
> I still think it is something to do with the samsung box using a different
> code for the second digit,


Sorry guys....
I suppose I was *really* lucky with my Samsung STB. I just read a bit more
on the subject, aka: "parity-bit". Obviously very bad news for any learning
remote not just MCE..

Here an idea:
Does the STB support "favorite lists"? (Mine does)
In that case: make a favorite channel-list including channels of your
choice, jumping over channel numbers that you assign that includes
repeating digits...with some luck maybe that's possible.