Double click the shortcut and Nothing

[ktwebb]

Just installed 1.4 (same problem with the beta) and it installs, accepts my key and so forth. Shortcut from the start menu or just double clicking the executable gives me an hourglass for about a second then nothing. I have a PVR-350 that works without problems with the WinTV 2000 software. I just paid 60 bucks for non functional software so any help is appreciated. I tried removing the WinTV software rebooting then reinstalling Sage. Didn't work. XP SP1 installed. Let me know if you need any more info to help because frankly, it's looking like a credit card charge refusal is forthcoming.

[fidget]

Originally posted by ktwebb
Just installed 1.4 (same problem with the beta) and it installs, accepts my key and so forth. Shortcut from the start menu or just double clicking the executable gives me an hourglass for about a second then nothing. I have a PVR-350 that works without problems with the WinTV 2000 software. I just paid 60 bucks for non functional software so any help is appreciated. I tried removing the WinTV software rebooting then reinstalling Sage. Didn't work. XP SP1 installed. Let me know if you need any more info to help because frankly, it's looking like a credit card charge refusal is forthcoming.

I'm glad to see that you tried to get assistance from the user community before making this post.

I will have to start by asking a few questions:
- What version of Java do you have installed?
- What is your computer configuration (CPU, chipset, memory)?
- When you installed the beta, what did the log file show?
- Did the demo have any problems? If you didn't try the demo, did you install 1.4 first and give it a try before installing the beta?
- Have you tried uninstalling the software, deleting the Frey Technologies directory and then reinstalling?

[ktwebb]

Originally posted by fidget
I'm glad to see that you tried to get assistance from the user community before making this post.

I will have to start by asking a few questions:
- What version of Java do you have installed?
- What is your computer configuration (CPU, chipset, memory)?
- When you installed the beta, what did the log file show?
- Did the demo have any problems? If you didn't try the demo, did you install 1.4 first and give it a try before installing the beta?
- Have you tried uninstalling the software, deleting the Frey Technologies directory and then reinstalling?

Java - 1.4.2
Athlon XP 1600, KT266, 512 DDR Kingston
Don't see a log file in the Frey dir. What's the log named?
No demo. Registered version and beta. Yes, tried 1.4 first.
No, not yet.

[ktwebb]

Update. Newest version of Java did the trick. You'd think they just might have put that in the troubleshooting guide. Oh well, as long as it works. Thanks for you help.

[fidget]

Originally posted by ktwebb
Update. Newest version of Java did the trick. You'd think they just might have put that in the troubleshooting guide. Oh well, as long as it works. Thanks for you help.

Along with the good of using a language like Java (ease of porting to other platforms) comes that pain of getting the correct runtime . My guess is that there is an incompatibility between the Java byte-code generated by the latest JVM and older ones.

In the Beta, you will find some files called sagetv_?.txt, where ? is a number between 0 and 3. When you start SageTV, it deletes sagetv_3.txt and moves the rest down one number (2->3, 1->2, 0->1) and creates a new sagetv_0.txt. The sagetv_0.txt file contains the logging information for the current execution. It is vital to capture this file when you get errors so that Frey can understand what was happening at that time.

[ktwebb]

Great. Let me ask you this. Is the beta worth swapping to right now?

[fidget]

Originally posted by ktwebb
Great. Let me ask you this. Is the beta worth swapping to right now?

In my opinion, yes. I really like the new UI. You get the UI on the S-Video out of the PVR-350 (be sure to get the latest drivers from shspvr.com).

[ktwebb]

Allright, I figured I had the latest drivers directly from their site. Windows reports driver version 1.17.390.22029, while the page you referenced lists 1.8.22020. That isn't jiving for me. Which is more current?