MCE - TV plays 1 second then pauses 1/2 second, continuously
in [Hardware]
|
From: Robert on 21 Apr 2010 23:42 Changing the speed setting did fix it. It had me change channels 6 times to determine speed, and it couldn't keep up, so Media Center set it to slow. I went back and just said it worked on fast, and now the channels change correctly. Now everything is okay. "CSM1" wrote: > > Since you mentioned the posting in the middle of the post, I will put > this one at the top. > > I am glad you got it sorted. There are Windows remotes that work just in > Media Center XP 2005. A Vista Remote without the correction is a real > pain in the a... > > On the channel number, if you go through the Tuner and Remote set up > again, (you have to go three tries) and select the SLOW sending, you > will likely get rid of the extra numbers coming in. > > > > -- > CSM1 > http://www.carlmcmillan.com > > =?Utf-8?B?Um9iZXJ0?= <Robert(a)discussions.microsoft.com> wrote in > news:3D96371B-E59E-46E9-8D32-843C99BB72ED(a)microsoft.com: > > > [Your bottom posting is making this hard to read. Your reply is in > > the middle of older ones, both above it and below it. I'm accessing > > this from http://www.microsoft.com/windowsxp/expertzone/newsgroups, > > which is expecting top posting. People are going to have to scroll > > down to the middle of stuff (out of order) to see what I'm replying > > to. Don't blame me. I'm replying to the part below that starts "> As > > far as I know..."] > > > > I got a kick out of "Windows thinks your IR receiver is a Mouse." > > There > > is a different group titled "Mice and other pointing devices." The > > internet phone and Bose audio device are also in "Human Interface > > Devices" - and they are also in > > under "Universal Serial Bus Controllers" as "USB Composite Device." > > I wondered why the "eHome Infrared Transeiver" wasn't also in the > > USB > > section. There was one entry there that had a partial directory name > > rather then a device name. I then double checked the Google images > > again to get you a picture of the "genuine" remote (you asked if it > > was genuine) - it is here (very long link): > > http://www.newegg.com/Product/ImageGallery.aspx?CurImage=15-144-019- > S08 > > &SCList=15-144-019-S01%2c15-144-019-S02%2c15-144-019-S03%2c15-144-019- > S > > 04%2c15-144-019-S05%2c15-144-019-S06%2c15-144-019-S07%2c15-144-019- > S08% > > 2c15-144-019-S09&S7ImageFlag=2&Item=N82E16815144019&Depa=0&WaterMark=1 > & > > Description=Pinnacle%20MCE%20Remote%20Kit%20w%2f%20IR%20blaster% > 20Certi > > fied%20for%20Vista%208230-10019-81%20USB%202.0%20Interface > > > > I noticed the "Certified for Vista..." at the very top of the > > page. I > > have XP SP3 MCE 2005. The guy that built the computer put that > > Pinnacle Vista kit in my computer. I did some more research (product > > reviews), and found it had a problem with MCE 2005, and I eventually > > found a hack to make it work on MCE 2005 here: > > http://www.newegg.com/Product/ProductReview.aspx?Item=N82E16815144019 > > (the third entry down by Brandon) > > I added those two entries to the irbus.inf file, and then checked > > that > > USB entry (in Device Manager w/screwed up name) for a new driver, and > > POOF, it now says "eHome Infrared Receiver." So it is (was) in the > > USB section like you said it should be, and now it's fixed. It's also > > still in "Human Interface Devices" (the others I mentioned are also > > normally duplicated there). > > I then loaded up Media Center, and now I don't get that "IR > > Hardware not > > detected" error. YEAH! I went through setup okay. It didn't > > recognize the DirecTV remote, so I went through the manually learning > > process. > > I now can select channels with Media Centers guide listing - > > EXCEPT > > sometimes it screws up and sends 5527 instead of 527 (I see the > > numbers show up on the TV picture) or 5442 instead of 542 - which > > means it doesn't always change the channel right. So now I have a > > new, different problem, and will make a new post about that. Thanks > > for your help. > > > > > > "CSM1" wrote: > > > >> =?Utf-8?B?Um9iZXJ0?= <Robert(a)discussions.microsoft.com> wrote in > >> news:7067AB11-4888-4253-BDB6-B2E9B25FD407(a)microsoft.com: > >> > >> > It's interesting that your suggestion apparently fixed the OTHER > >> > problem. > >> > See below. > >> > It's listed under "Human Interface Devices" as "Microsoft eHome > >> > Infrared > >> > Transceiver." I uninstalled it, rebooted, and it invisibly > >> > reinstalled itself. I still get the "IR Hardware not detected" > >> > error. > >> > The Windows remote still works. I don't understand how Windows > >> > even > >> > knows if a simple cable that has nothing on it but an infrared led > >> > is even plugged into the IR Reciever. It is plugged in. (Maybe I > >> > should find another plug the same size, cut the wire, and hook the > >> > two wires together to see if Windows see the connection is closed.) > >> > I've tried putting the IR Blaster in front of the IR Receiver > >> > during "try again" to see if Windows wants to see it work - even > >> > though the instructions say nothing about doing that. > >> > There was a very fortunate and unexpected side effect to > >> > reinstalling > >> > the IR Tranceiver device - the pausing/skipping while watching TV > >> > in Media Center is now gone. I don't know how that solved that > >> > problem - I'm very skeptical of coincedences. > >> > So now two problems is reduced to one. If I can get the IR > >> > Blaster > >> > detected I will only have to program to record shows in one place. > >> > (Right now Media Center is set up for antenna - with one channel - > >> > 4.) > >> > >> As far as I know, Windows thinks your IR receiver is a Mouse. > >> > >> Human Interface Devices is for Mice in Device manager. > >> It should be in the USB devices. > >> > >> Are you sure that your IR receiver is a genuine Windows Media Center > >> IR Remote device. > >> > >> > >> -- > >> CSM1 > >> http://www.carlmcmillan.com > >> > >> > >> > > >> > "CSM1" wrote: > >> >> > >> >> I suggest that you open Device Manager and look for the IR > >> >> receiver. Then remove it and re-boot the computer. > >> >> > >> >> To open Device Manager, in Windows (Get out of the 10 foot > >> >> interface) press the Windows Key and the Pause/Break Key at the > >> >> same time. Click the Hardware tab, then click Device Manager > >> >> button. > >> >> > >> >> The IR receiver is located in the USB Controller branch. > >> >> Listed as eHome Infrared Receiver. > >> >> > >> >> If that entry is not in the Device manager, you do not have the IR > >> >> hardware installed. > >> >> > >> >> There is no extra software, the driver is built into the Media > >> >> Center Operation System. > >> >> > >> >> > >> >> -- > >> >> CSM1 > >> >> http://www.carlmcmillan.com > >> >> > >> >> > >> >> > > >> >> > > >> >> > "Curious" wrote: > >> >> > > >> >> >> Yes STB stands for Set Top Box > >> >> >> Since all transmissions from DirecTV are encrypted and there is > >> >> >> no tuner card available for a PC that will receive DirecTV > >> >> >> transmissions. MC is assuming that when you say that DirecTV > >> >> >> is your source that you are using a DirecTV STB which is why it > >> >> >> is looking for an IR blaster to control a directTV STB. > >> >> >> DirecTV did have a project to develop a PC based tuner card for > >> >> >> Windows but they cancelled the project over a year ago. > >> >> >> > >> >> >> "Robert" <Robert(a)discussions.microsoft.com> wrote in message > >> >> >> news:1632CFB5-24A2-47B0-9EF5-F0AC576C35D4(a)microsoft.com... > >> >> >> > Does STB = Set Top Box? (I looked it up w/Google.) > >> >> >> > What does this mean "> Were you using a STB and IR blaster > >> >> >> > with a cable STB?" > >> >> >> > Two set top box's? I wasn't using any. I had cable, and > >> >> >> > watched TV with Media Center. (The movie channels I > >> >> >> > subscribed to weren't scrambled, and I > >> >> >> > didn't have a box. I don't know how the cable company did > >> >> >> > that.) I was using > >> >> >> > the IR receiver, not the blaster. The IR receiver plugs into > >> >> >> > a USB port. As > >> >> >> > I said, the IR receiver still works, as I can select "try > >> >> >> > again" (to detect > >> >> >> > "IR hardware") WITH THE REMOTE. I never needed the IR > >> >> >> > blaster before - it was still in it's sealed package in the > >> >> >> > box. It is simple - a wire with the > >> >> >> > emitter in a little box (it's the "official" MCE one found in > >> >> >> > Google images). > >> >> >> > > >> >> >> > The links I read distinguished MCE 2002 and MCE 2005, saying > >> >> >> > the problem > >> >> >> > was just with MCE 2002; and a different problem w/MCE 2005 if > >> >> >> > you skipped SP2 > >> >> >> > and did SP1->SP3. > >> >> >> > > >> >> >> > > >> >> >> > "Curious" wrote: > >> >> >> > > >> >> >> >> MCE2005 is based on XP Pro 2002 and what you have is MCE2005 > >> >> >> >> running on a modified XP Pro OS 2002 SP3 system. > >> >> >> >> I understand that you had no problems until you tried to > >> >> >> >> reset up your system for a direct TV STB from using cable. > >> >> >> >> Were you using a STB and IR blaster with a cable STB? > >> >> >> >> If not I suspect I a hardware problem with the IR receiver > >> >> >> >> unit or it's driver? > >> >> >> >> > >> >> >> >> "Robert" <Robert(a)discussions.microsoft.com> wrote in message > >> >> >> >> news:D9952182-CE37-47F1-96B8-25F7F1E25F94(a)microsoft.com... > >> >> >> >> > I just read several of the links, and did two more > >> >> >> >> > searchs adding "IR > >> >> >> >> > hardware not detected" and "skipping." The extra searches > >> >> >> >> > match nothing > >> >> >> >> > relevant. > >> >> >> >> > The links mention problems with using SP3 with MCE 2002 > >> >> >> >> > (I have > >> >> >> >> > 2005), > >> >> >> >> > and with going from SP1 to SP3, skipping SP2. I had SP2 > >> >> >> >> > before. > >> >> >> >> > One of > >> >> >> >> > the > >> >> >> >> > links is a Microsoft website, they note these issues, and > >> >> >> >> > none others with > >> >> >> >> > SP3 w/Media Center. Also, I have used SP3 w/Media for > >> >> >> >> > several months with > >> >> >> >> > not problems. > >> >> >> >> > > >> >> >> >> > "Curious" wrote: > >> >> >> >> > > >> >> >> >> >> Robert, > >> >> >> >> >> I have not had any systems running XP for several years. > >> >> >> >> >> However, I have seen lots of reports of user's having > >> >> >> >> >> problems after installing SP3. > >> >> >> >> >> The following Bing search results may provide some help > >> >> >> >> >> in resolving your > >> >> >> >> >> problem. > >> >> >> >> >> > >> >> >> >> >> http://www.bing.com/search?q=xp+sp3 > >> >> +media+center&go=&form=QBLH&q > >> >> >> >> >> s=n&sk= > >> >> >> >> >> > >> >> >> >> >> "Robert" <Robert(a)discussions.microsoft.com> wrote in > >> >> >> >> >> message > >> >> >> >> >> news:96B70E85-E399-4680-8C34-AAD7F9C87361 > @microsoft.com... > >> >> >> >> >> > Since I don't have any other ideas, and two people say > >> >> >> >> >> > it will work anyway > >> >> >> >> >> > (non-supported chip) here it goes... downloaded... > >> >> >> >> >> > installed. > >> >> >> >> >> > > >> >> >> >> >> > The Windows XP Video Decoder Checkup Utility reports > >> >> >> >> >> > NVidia is the preferred > >> >> >> >> >> > driver (I didn't have to change it). > >> >> >> >> >> > > >> >> >> >> >> > There is no change. Uninstalled NVidia. Thanks for > >> >> >> >> >> > the idea. ** Any other ideas? ** Thanks. > >> >> >> >> >> > > >> >> >> >> >> > BTW: Here's what the website says: > >> >> >> >> >> > The page at: > >> >> >> >> >> > http://www.nvidia.com/object/dvd_decoder_1.02-223- > >> trial.htm > >> >> >> >> >> > l reads: > >> >> >> >> >> > ------------------------------- > >> >> >> >> >> > System Requirements > >> >> >> >> >> > > >> >> >> >> >> > * Windows XP Media Center Edition 2004/2005/2006 > >> >> >> >> >> > Update Rollup2, > >> >> >> >> >> > Windows > >> >> >> >> >> > XP Professional, or Windows XP Home Edition > >> >> >> >> >> > ... (SNIP) > >> >> >> >> >> > > >> >> >> >> >> > Graphics Chips Supported > >> >> >> >> >> > > >> >> >> >> >> > * NVIDIA GeForce 8 Series > >> >> >> >> >> > * NVIDIA GeForce 7 Series > >> >> >> >> >> > * NVIDIA GeForce 6 series > >> >> >> >> >> > * NVIDIA GeForce FX series > >> >> >> >> >> > * NVIDIA Quadro FX Series > >> >> >> >> >> > -------------------------------------- > >> >> >> >> >> > > >> >> >> >> >> > > >> >> >> >> >> > "Jaime" wrote: > >> >> >> >> >> > > >> >> >> >> >> >> No, the nVidia decoder has nothing to do with what > >> >> >> >> >> >> video card you have. > >> >> >> >> >> >> > >> >> >> >> >> >> The page > >> >> >> >> >> >> (http://www.nvidia.com/object/dvd_decoder_1.02-150- > >> >> trial.html > >> >> >> >> >> >> ) says > >> >> >> >> >> >> "chips supported" and it lists just the nVidia ones, > >> >> >> >> >> >> but the only requirements are: > >> >> >> >> >> >> > >> >> >> >> >> >> - Windows XP Media Center Edition 2004/2005/New BETA, > >> >> >> >> >> >> Windows XP Professional, or Windows XP Home Edition > >> >> >> >> >> >> - DirectX 9.0 or higher > >> >> >> >> >> >> - Windows Media Center or Windows Media® > >> >> >> >> >> >> Player 9.0 or higher for DVD > >> >> >> >> >> >> Playback > >> >> >> >> >> >> - DirectShow compatible software for MPEG-2 file > >> >> >> >> >> >> playback - A DirectX Video Acceleration (DXVA) > >> >> >> >> >> >> compatible graphics processor, > >> >> >> >> >> >> such
From: Robert on 21 Apr 2010 23:47 Thanks for you help. "Robert" wrote: > Changing the speed setting did fix it. It had me change channels 6 times to > determine speed, and it couldn't keep up, so Media Center set it to slow. I > went back and just said it worked on fast, and now the channels change > correctly. Now everything is okay. > > "CSM1" wrote: > > > > > Since you mentioned the posting in the middle of the post, I will put > > this one at the top. > > > > I am glad you got it sorted. There are Windows remotes that work just in > > Media Center XP 2005. A Vista Remote without the correction is a real > > pain in the a... > > > > On the channel number, if you go through the Tuner and Remote set up > > again, (you have to go three tries) and select the SLOW sending, you > > will likely get rid of the extra numbers coming in. > > > > > > > > -- > > CSM1 > > http://www.carlmcmillan.com > > > > =?Utf-8?B?Um9iZXJ0?= <Robert(a)discussions.microsoft.com> wrote in > > news:3D96371B-E59E-46E9-8D32-843C99BB72ED(a)microsoft.com: > > > > > [Your bottom posting is making this hard to read. Your reply is in > > > the middle of older ones, both above it and below it. I'm accessing > > > this from http://www.microsoft.com/windowsxp/expertzone/newsgroups, > > > which is expecting top posting. People are going to have to scroll > > > down to the middle of stuff (out of order) to see what I'm replying > > > to. Don't blame me. I'm replying to the part below that starts "> As > > > far as I know..."] > > > > > > I got a kick out of "Windows thinks your IR receiver is a Mouse." > > > There > > > is a different group titled "Mice and other pointing devices." The > > > internet phone and Bose audio device are also in "Human Interface > > > Devices" - and they are also in > > > under "Universal Serial Bus Controllers" as "USB Composite Device." > > > I wondered why the "eHome Infrared Transeiver" wasn't also in the > > > USB > > > section. There was one entry there that had a partial directory name > > > rather then a device name. I then double checked the Google images > > > again to get you a picture of the "genuine" remote (you asked if it > > > was genuine) - it is here (very long link): > > > http://www.newegg.com/Product/ImageGallery.aspx?CurImage=15-144-019- > > S08 > > > &SCList=15-144-019-S01%2c15-144-019-S02%2c15-144-019-S03%2c15-144-019- > > S > > > 04%2c15-144-019-S05%2c15-144-019-S06%2c15-144-019-S07%2c15-144-019- > > S08% > > > 2c15-144-019-S09&S7ImageFlag=2&Item=N82E16815144019&Depa=0&WaterMark=1 > > & > > > Description=Pinnacle%20MCE%20Remote%20Kit%20w%2f%20IR%20blaster% > > 20Certi > > > fied%20for%20Vista%208230-10019-81%20USB%202.0%20Interface > > > > > > I noticed the "Certified for Vista..." at the very top of the > > > page. I > > > have XP SP3 MCE 2005. The guy that built the computer put that > > > Pinnacle Vista kit in my computer. I did some more research (product > > > reviews), and found it had a problem with MCE 2005, and I eventually > > > found a hack to make it work on MCE 2005 here: > > > http://www.newegg.com/Product/ProductReview.aspx?Item=N82E16815144019 > > > (the third entry down by Brandon) > > > I added those two entries to the irbus.inf file, and then checked > > > that > > > USB entry (in Device Manager w/screwed up name) for a new driver, and > > > POOF, it now says "eHome Infrared Receiver." So it is (was) in the > > > USB section like you said it should be, and now it's fixed. It's also > > > still in "Human Interface Devices" (the others I mentioned are also > > > normally duplicated there). > > > I then loaded up Media Center, and now I don't get that "IR > > > Hardware not > > > detected" error. YEAH! I went through setup okay. It didn't > > > recognize the DirecTV remote, so I went through the manually learning > > > process. > > > I now can select channels with Media Centers guide listing - > > > EXCEPT > > > sometimes it screws up and sends 5527 instead of 527 (I see the > > > numbers show up on the TV picture) or 5442 instead of 542 - which > > > means it doesn't always change the channel right. So now I have a > > > new, different problem, and will make a new post about that. Thanks > > > for your help. > > > > > > > > > "CSM1" wrote: > > > > > >> =?Utf-8?B?Um9iZXJ0?= <Robert(a)discussions.microsoft.com> wrote in > > >> news:7067AB11-4888-4253-BDB6-B2E9B25FD407(a)microsoft.com: > > >> > > >> > It's interesting that your suggestion apparently fixed the OTHER > > >> > problem. > > >> > See below. > > >> > It's listed under "Human Interface Devices" as "Microsoft eHome > > >> > Infrared > > >> > Transceiver." I uninstalled it, rebooted, and it invisibly > > >> > reinstalled itself. I still get the "IR Hardware not detected" > > >> > error. > > >> > The Windows remote still works. I don't understand how Windows > > >> > even > > >> > knows if a simple cable that has nothing on it but an infrared led > > >> > is even plugged into the IR Reciever. It is plugged in. (Maybe I > > >> > should find another plug the same size, cut the wire, and hook the > > >> > two wires together to see if Windows see the connection is closed.) > > >> > I've tried putting the IR Blaster in front of the IR Receiver > > >> > during "try again" to see if Windows wants to see it work - even > > >> > though the instructions say nothing about doing that. > > >> > There was a very fortunate and unexpected side effect to > > >> > reinstalling > > >> > the IR Tranceiver device - the pausing/skipping while watching TV > > >> > in Media Center is now gone. I don't know how that solved that > > >> > problem - I'm very skeptical of coincedences. > > >> > So now two problems is reduced to one. If I can get the IR > > >> > Blaster > > >> > detected I will only have to program to record shows in one place. > > >> > (Right now Media Center is set up for antenna - with one channel - > > >> > 4.) > > >> > > >> As far as I know, Windows thinks your IR receiver is a Mouse. > > >> > > >> Human Interface Devices is for Mice in Device manager. > > >> It should be in the USB devices. > > >> > > >> Are you sure that your IR receiver is a genuine Windows Media Center > > >> IR Remote device. > > >> > > >> > > >> -- > > >> CSM1 > > >> http://www.carlmcmillan.com > > >> > > >> > > >> > > > >> > "CSM1" wrote: > > >> >> > > >> >> I suggest that you open Device Manager and look for the IR > > >> >> receiver. Then remove it and re-boot the computer. > > >> >> > > >> >> To open Device Manager, in Windows (Get out of the 10 foot > > >> >> interface) press the Windows Key and the Pause/Break Key at the > > >> >> same time. Click the Hardware tab, then click Device Manager > > >> >> button. > > >> >> > > >> >> The IR receiver is located in the USB Controller branch. > > >> >> Listed as eHome Infrared Receiver. > > >> >> > > >> >> If that entry is not in the Device manager, you do not have the IR > > >> >> hardware installed. > > >> >> > > >> >> There is no extra software, the driver is built into the Media > > >> >> Center Operation System. > > >> >> > > >> >> > > >> >> -- > > >> >> CSM1 > > >> >> http://www.carlmcmillan.com > > >> >> > > >> >> > > >> >> > > > >> >> > > > >> >> > "Curious" wrote: > > >> >> > > > >> >> >> Yes STB stands for Set Top Box > > >> >> >> Since all transmissions from DirecTV are encrypted and there is > > >> >> >> no tuner card available for a PC that will receive DirecTV > > >> >> >> transmissions. MC is assuming that when you say that DirecTV > > >> >> >> is your source that you are using a DirecTV STB which is why it > > >> >> >> is looking for an IR blaster to control a directTV STB. > > >> >> >> DirecTV did have a project to develop a PC based tuner card for > > >> >> >> Windows but they cancelled the project over a year ago. > > >> >> >> > > >> >> >> "Robert" <Robert(a)discussions.microsoft.com> wrote in message > > >> >> >> news:1632CFB5-24A2-47B0-9EF5-F0AC576C35D4(a)microsoft.com... > > >> >> >> > Does STB = Set Top Box? (I looked it up w/Google.) > > >> >> >> > What does this mean "> Were you using a STB and IR blaster > > >> >> >> > with a cable STB?" > > >> >> >> > Two set top box's? I wasn't using any. I had cable, and > > >> >> >> > watched TV with Media Center. (The movie channels I > > >> >> >> > subscribed to weren't scrambled, and I > > >> >> >> > didn't have a box. I don't know how the cable company did > > >> >> >> > that.) I was using > > >> >> >> > the IR receiver, not the blaster. The IR receiver plugs into > > >> >> >> > a USB port. As > > >> >> >> > I said, the IR receiver still works, as I can select "try > > >> >> >> > again" (to detect > > >> >> >> > "IR hardware") WITH THE REMOTE. I never needed the IR > > >> >> >> > blaster before - it was still in it's sealed package in the > > >> >> >> > box. It is simple - a wire with the > > >> >> >> > emitter in a little box (it's the "official" MCE one found in > > >> >> >> > Google images). > > >> >> >> > > > >> >> >> > The links I read distinguished MCE 2002 and MCE 2005, saying > > >> >> >> > the problem > > >> >> >> > was just with MCE 2002; and a different problem w/MCE 2005 if > > >> >> >> > you skipped SP2 > > >> >> >> > and did SP1->SP3. > > >> >> >> > > > >> >> >> > > > >> >> >> > "Curious" wrote: > > >> >> >> > > > >> >> >> >> MCE2005 is based on XP Pro 2002 and what you have is MCE2005 > > >> >> >> >> running on a modified XP Pro OS 2002 SP3 system. > > >> >> >> >> I understand that you had no problems until you tried to > > >> >> >> >> reset up your system for a direct TV STB from using cable. > > >> >> >> >> Were you using a STB and IR blaster with a cable STB? > > >> >> >> >> If not I suspect I a hardware problem with the IR receiver > > >> >> >> >> unit or it's driver? > > >> >> >> >> > > >> >> >> >> "Robert" <Robert(a)discussions.microsoft.com> wrote in message > > >> >> >> >> news:D9952182-CE37-47F1-96B8-25F7F1E25F94(a)microsoft.com... > > >> >> >> >> > I just read several of the links, and did two more > > >> >> >> >> > searchs adding "IR > > >> >> >> >> > hardware not detected" and "skipping." The extra searches > > >> >> >> >> > match nothing > > >> >> >> >> > relevant. > > >> >> >> >> > The links mention problems with using SP3 with MCE 2002 > > >> >> >> >> > (I have > > >> >> >> >> > 2005), > > >> >> >> >> > and with going from SP1 to SP3, skipping SP2. I had SP2 > > >> >> >> >> > before. > > >> >> >> >> > One of > > >> >> >> >> > the > > >> >> >> >> > links is a Microsoft website, they note these issues, and > > >> >> >> >> > none others with > > >> >> >> >> > SP3 w/Media Center. Also, I have used SP3 w/Media for > > >> >> >> >> > several months with > > >> >> >> >> > not problems. > > >> >> >> >> > > > >> >> >> >> > "Curious" wrote: > > >> >> >> >> > > > >> >> >> >> >> Robert, > > >> >> >> >> >> I have not had any systems running XP for several years. > > >> >> >> >> >> However, I have seen lots of reports of user's having > > >> >> >> >> >> problems after installing SP3. > > >> >> >> >> >> The following Bing search results may provide some help > > >> >> >> >> >> in resolving your > > >> >> >> >> >> problem. > > >> >> >> >> >> > > >> >> >> >> >> http://www.bing.com/search?q=xp+sp3 > > >> >> +media+center&go=&form=QBLH&q > > >> >> >> >> >> s=n&sk= > > >> >> >> >> >> > > >> >> >> >> >> "Robert" <Robert(a)discussions.microsoft.com> wrote in > > >> >> >> >> >> message > > >> >> >> >> >> news:96B70E85-E399-4680-8C34-AAD7F9C87361 > > @microsoft.com... > > >> >> >> >> >> > Since I don't have any other ideas, and two people say > > >> >> >> >> >> > it will work anyway > > >> >> >> >> >> > (non-supported chip) here it goes... downloaded... > > >> >> >> >> >> > installed. > > >> >> >> >> >> > > > >> >> >> >> >> > The Windows XP Video Decoder Checkup Utility reports > > >> >> >> >> >> > NVidia is the preferred > > >> >> >> >> >> > driver (I didn't have to change it). > > >> >> >> >> >> > > > >> >> >> >> >> > There is no change. Uninstalled NVidia. Thanks for > > >> >> >> >> >> > the idea. ** Any other ideas? ** Thanks. > > >> >> >> >> >> > > > >> >> >> >> >> > BTW: Here's what the website says: > > >> >> >> >> >> > The page at: > > >> >> >> >> >> > http://www.nvidia.com/object/dvd_decoder_1.02-223- > > >> trial.htm > > >> >> >> >> >> > l reads: > > >> >> >> >> >> > ------------------------------- > > >> >> >> >> >> > System Requirements > > >> >> >> >> >> > > > >> >> >> >> >> > * Windows XP Media Center Edition 2004/2005/2006 > > >> >> >> >> >> > Update Rollup2, > > >> >> >> >> >> > Windows > > >> >> >> >> >> > XP Professional, or Windows XP Home Edition > > >> >> >> >> >> > ... (SNIP) > > >> >> >> >> >> > > > >> >> >> >> >> > Graphics Chips Supported > > >> >> >> >> >> > > > >> >> >> >> >> > * NVIDIA GeForce 8 Series > > >> >> >> >> >> > * NVIDIA GeForce 7 Series > > >> >> >> >> >> > * NVIDIA GeForce 6 series > > >> >> >> >> >> > * NVIDIA GeForce FX series > > >> >> >> >> >> > * NVIDIA Quadro FX Series > > >> >> >> >> >> > -------------------------------------- > > >> >> >> >> >> > > > >> >> >> >> >> > > > >> >> >> >> >> > "Jaime" wrote: > > >> >> >> >> >> > > > >> >> >> >> >> >> No, the nVidia decoder has nothing to do with what > > >> >> >> >> >> >> video card you have. > > >> >> >> >> >> >> > > >> >> >> >> >> >> The page > > >> >> >> >> >> >> (http://www.nvidia.com/object/dvd_decoder_1.02-150- > > >> >> trial.html > > >> >> >> >> >> >> ) says > > >> >> >> >> >> >> "chips supported" and it lists just the nVidia ones, > > >> >> >> >> >> >> but the only requirements are: > > >> >> >> >> >> >> > > >> >> >> >> >> >> - Windows XP Media Center Edition 2004/2005/New BETA, > > >> >> >> >> >> >> Windows XP Professional, or Windows XP Home Edition
First
|
Prev
|
Pages: 1 2 3 4 5 6 Prev: sata1 dead : can I replace with sta2 hard drives ? Next: Win7 can't see XP Home printer |