problems for Danes and stable patches and Hauppauge remote - Page 2

sbp · 2006-08-14, 17:43

HI I tried that yesterday on my HTPC computer which actually contain the PVR150 card. No change in behavior.

I can reproduce the error on my other computer (with no Tv-card present) - actually these last logs were from this computer. So it is reproducible that enabeling the Hauppauge remote causes a crash. But enabeling the MCE remote does not.
Even on a computer with no remote or Tv-card present.

So I don't think that Hauppauge drivers are causing these problems.

Steen

ronilse · 2006-08-14, 18:29

Hi,
You are using Windows XP (pro or home) with SP2 & all updates?

PS, Steen log on to irc again.

Regards
Roy

[XStream] · 2006-08-14, 19:27

I have the exact same problem on my parents new htpc.
Only major difference in hardware would be that this is a Nova-T PCI and a sidekick Comro T200a.

I have verified software as noted below

*XP Pro sp2 with all update, just checked with windowsupdate
*Latest directx, just did a manual download and installation, dont know if it actually updated anything though
*Updated with the latest drivers from the link you suggested.

Can't verify the version of the ir-software but it should be the latest version and configuration doesnt say anything about it being old.

After a restart the problem persists.

I have previously tried reinstalling windows.

One thing that i noted is that my nova-t chip says 90003 LF whereas all hauppauge pictures i've seen say just 90002. They do say 90xxx on the driver page though but what could that LF be?

I've been trying to find a manufacturing date with no luck. We bought it just a week ago from a major Swedish online shop so im pretty sure its fairly new.

Just for the sake of it i uploaded all three relevant log to http://pastebin.team-mediaportal.com/10373

Cheers

[XStream] · 2006-08-14, 21:13

I tried to have a go at the source but with little luck. The mshtml assembly seems to be pretty crucial and the provided update can only be run if you already have office 2003 installed. i'll see if i try again later, right now i'm kinda frustrated and tired of the whole thing so i'm gonna take a break.

mPod · 2006-08-14, 21:35

Quote:

Originally Posted by [XStream

]I tried to have a go at the source but with little luck. The mshtml assembly seems to be pretty crucial and the provided update can only be run if you already have office 2003 installed. i'll see if i try again later, right now i'm kinda frustrated and tired of the whole thing so i'm gonna take a break.

Install the .Net 2.0 SDK to get the mshtml stuff.

[XStream] · 2006-08-14, 21:55

Was pretty sure that came with vs.net. downloading right now, gonna take me a while. Don't count on me solving this though, my degree in c# is 3,5 years old and i haven't coded anything worth mentioning for about 2.

Cheers

mPod · 2006-08-14, 22:03

Well, we're a bit stuck at the moment, so it would be good if you could help out, as you suffer from that problem. As said, it only happens on swedish and danish XPs, so we can't reproduce and debug it.

What also would help is if you guys could try to find out WHICH REV after 0.2 release brought up the problem by trying out older SVN builds for 0.2. I'd start with the first one and test all others after that one by one. If we know WHEN the error came in, we know where to search.

[XStream] · 2006-08-14, 22:11

That might be a point i've never thought of. I do run a swedish xp on this system instead of an english one as i usually do. it really doesnt matter so i could just install an english one and try that.
however, im a bit too much of a team player so i'll try to do what i can within the time frame i have. my parents are getting kinda anxious to try out their new machine.

i'll begin with uninstalling mp and remove the dir and then install again and work my way up through the svn right away.

[XStream] · 2006-08-14, 22:41

The problem first occurs in mediaportal-svn-07-15-2006--01-01-Rev9503.rar

I've followed this routine:
1. Install clean mediaportal 0.2, default settings on everything but mce and hauppauge remote
2. Extract svn on top of mediaportal
3. Open configuration and close again by pressing Ok
4. Open mediaportal
5. Verify that remote works

Repeat 2-5

[XStream] · 2006-08-14, 23:01

I've done som builds trying to find the exact spot and some more details. I cannot seem to get vs.net to show me what line the actual exception is thrown at.
Although i guess knowing at what point the problem occured and that it has to do with remotes really should get us pretty far.

2006-08-14, 22:03	#17 (permalink)
mPod Retired Team Member Join Date: Jan 2005 Location: Berlin Age: 34 Posts: 2,086 Thanks: 0 Thanked 3 Times in 3 Posts Country: My System	Well, we're a bit stuck at the moment, so it would be good if you could help out, as you suffer from that problem. As said, it only happens on swedish and danish XPs, so we can't reproduce and debug it. What also would help is if you guys could try to find out WHICH REV after 0.2 release brought up the problem by trying out older SVN builds for 0.2. I'd start with the first one and test all others after that one by one. If we know WHEN the error came in, we know where to search. __________________ Bad news from the stars... We cannot give any support without a properly filled support template and a full mediaportal.log pasted here. Before you ask...

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Hauppauge MCE remote trouble	fod	General Support	6	2007-01-07 23:42
Hauppauge PVR-USB2 remote causing HCWhelper to crash	Cronos	General Support	4	2006-08-03 21:42

2006-08-14, 17:43	#11 (permalink)
sbp Portal Member Join Date: Aug 2006 Location: Auning Posts: 130 Thanks: 0 Thanked 0 Times in 0 Posts Country:	HI I tried that yesterday on my HTPC computer which actually contain the PVR150 card. No change in behavior. I can reproduce the error on my other computer (with no Tv-card present) - actually these last logs were from this computer. So it is reproducible that enabeling the Hauppauge remote causes a crash. But enabeling the MCE remote does not. Even on a computer with no remote or Tv-card present. So I don't think that Hauppauge drivers are causing these problems. Steen

2006-08-14, 18:29	#12 (permalink)
ronilse Portal Tester Join Date: Jul 2005 Posts: 3,386 Thanks: 23 Thanked 99 Times in 84 Posts Country: My System	Hi, You are using Windows XP (pro or home) with SP2 & all updates? PS, Steen log on to irc again. Regards Roy

2006-08-14, 19:27	#13 (permalink)
[XStream] Portal Member Join Date: Aug 2006 Location: Behind you... scared? Posts: 27 Thanks: 0 Thanked 0 Times in 0 Posts	I have the exact same problem on my parents new htpc. Only major difference in hardware would be that this is a Nova-T PCI and a sidekick Comro T200a. I have verified software as noted below XP Pro sp2 with all update, just checked with windowsupdate Latest directx, just did a manual download and installation, dont know if it actually updated anything though *Updated with the latest drivers from the link you suggested. Can't verify the version of the ir-software but it should be the latest version and configuration doesnt say anything about it being old. After a restart the problem persists. I have previously tried reinstalling windows. One thing that i noted is that my nova-t chip says 90003 LF whereas all hauppauge pictures i've seen say just 90002. They do say 90xxx on the driver page though but what could that LF be? I've been trying to find a manufacturing date with no luck. We bought it just a week ago from a major Swedish online shop so im pretty sure its fairly new. Just for the sake of it i uploaded all three relevant log to http://pastebin.team-mediaportal.com/10373 Cheers

2006-08-14, 21:13	#14 (permalink)
[XStream] Portal Member Join Date: Aug 2006 Location: Behind you... scared? Posts: 27 Thanks: 0 Thanked 0 Times in 0 Posts	I tried to have a go at the source but with little luck. The mshtml assembly seems to be pretty crucial and the provided update can only be run if you already have office 2003 installed. i'll see if i try again later, right now i'm kinda frustrated and tired of the whole thing so i'm gonna take a break.

2006-08-14, 21:55	#16 (permalink)
[XStream] Portal Member Join Date: Aug 2006 Location: Behind you... scared? Posts: 27 Thanks: 0 Thanked 0 Times in 0 Posts	Was pretty sure that came with vs.net. downloading right now, gonna take me a while. Don't count on me solving this though, my degree in c# is 3,5 years old and i haven't coded anything worth mentioning for about 2. Cheers

2006-08-14, 22:11	#18 (permalink)
[XStream] Portal Member Join Date: Aug 2006 Location: Behind you... scared? Posts: 27 Thanks: 0 Thanked 0 Times in 0 Posts	That might be a point i've never thought of. I do run a swedish xp on this system instead of an english one as i usually do. it really doesnt matter so i could just install an english one and try that. however, im a bit too much of a team player so i'll try to do what i can within the time frame i have. my parents are getting kinda anxious to try out their new machine. i'll begin with uninstalling mp and remove the dir and then install again and work my way up through the svn right away.

2006-08-14, 22:41	#19 (permalink)
[XStream] Portal Member Join Date: Aug 2006 Location: Behind you... scared? Posts: 27 Thanks: 0 Thanked 0 Times in 0 Posts	The problem first occurs in mediaportal-svn-07-15-2006--01-01-Rev9503.rar I've followed this routine: 1. Install clean mediaportal 0.2, default settings on everything but mce and hauppauge remote 2. Extract svn on top of mediaportal 3. Open configuration and close again by pressing Ok 4. Open mediaportal 5. Verify that remote works Repeat 2-5

2006-08-14, 23:01	#20 (permalink)
[XStream] Portal Member Join Date: Aug 2006 Location: Behind you... scared? Posts: 27 Thanks: 0 Thanked 0 Times in 0 Posts	I've done som builds trying to find the exact spot and some more details. I cannot seem to get vs.net to show me what line the actual exception is thrown at. Although i guess knowing at what point the problem occured and that it has to do with remotes really should get us pretty far.