Demo Reboots Windows on Program Exit

[JasonJoel]

Downloaded the demo, and so far am mostly liking it.

One thing though. Although the program will view video fine, record fine, play back video fine - when I close the program (close it completely, not just minimize it) my computer Reboots!

I've tried two different Hauppage PVR 250 drivers, it did it on both.

The same hardware has been use 24/7 recording with the PVR 250 for months, so I don't THINK it is a weird incompatibility with the card, etc.

Any thoughts?

Jason

System Specs:
ECS K75SA
Athlon XP 1800+
WinXP Pro
Hauppage WinTV PVR-250
ATI All-in-Wonder 7500 AGP

[Narflex]

You're most likely using Java verions 1.4.1_01. That's a known bug in java on XP. 1.4.1_02 is out and it supposedly has that bug fixed. 1.4.0 definitely does not have that bug (this was confirmed in testing awhile back).

If you need more information on how to tell what version you have go to DOS and type:
java -version

as long as you haven't modified your Java settings in the registry; that'll give you the current version of Java installed

Thanks,

[JasonJoel]

I'll check when I get home...

I did a clean install of WinXP, etc last night - so I SHOULD have the latest Java version (whatever existed as of last night).

But I'll double check. Thanks.

Jason


Originally posted by Narflex
You're most likely using Java verions 1.4.1_01. That's a known bug in java on XP. 1.4.1_02 is out and it supposedly has that bug fixed. 1.4.0 definitely does not have that bug (this was confirmed in testing awhile back).

If you need more information on how to tell what version you have go to DOS and type:
java -version

as long as you haven't modified your Java settings in the registry; that'll give you the current version of Java installed

Thanks,

[Mark Lamutt]

Jason - the Java runtimes aren't automatically installed in the XP installation. You'll probably have to install them separately.

[edmc]

> the Java runtimes aren't automatically installed in the XP
> installation. You'll probably have to install them separately.

This was certainly true when I first installed a Beta version (build 43 or 44). Is this still true? I thought that somewhere about the time of RC1 that the Installer had been upgraded to ensure that the necessary Java JVM/Libraries where present (and install them if not).

[Mark Lamutt]

I wasn't talking about the Sage installation - Jason had said that he had just done a reinstall of XP, so he thought the most current java runtimes were installed with that. :)

[JasonJoel]

No.. I know that Sun Java is not installed with XP. I should have been more clear about what I was saying.

Before installing SageTV, I went to java.com and installed Sun's JAVA client from there. So I would think I have the 'latest' version of Sun's JAVA runtimes. But I'll double check when I get home.

That should clear it up.

Jason


Originally posted by Mark Lamutt
I wasn't talking about the Sage installation - Jason had said that he had just done a reinstall of XP, so he thought the most current java runtimes were installed with that. :)

[JasonJoel]

Yes, I was using 1.4.1_01. I'm D/Ling 02 now.

Strange, depending on where you go on Sun's site, some of the pages list 1.4.1_01 as the newest version, some list 02 as the newest version.

I guess that is how I ended up with the 01 version!

Jason


Originally posted by Narflex
You're most likely using Java verions 1.4.1_01. That's a known bug in java on XP. 1.4.1_02 is out and it supposedly has that bug fixed. 1.4.0 definitely does not have that bug (this was confirmed in testing awhile back).

If you need more information on how to tell what version you have go to DOS and type:
java -version

as long as you haven't modified your Java settings in the registry; that'll give you the current version of Java installed

Thanks,

[Narflex]

Let us know if it works. This'll be confirmation of 1.4.1_02 fixing that bug.

[JasonJoel]

Installing Sun Java 1.4.1_02 fixed the problem. It was indeed a bug in 1.4.1_01.

THANKS!

Jason


Originally posted by Narflex
Let us know if it works. This'll be confirmation of 1.4.1_02 fixing that bug.