Open Source Windows Installer

[jusjoken]

Originally Posted by nyplayer

Well it worked with the old exe and not the new exe. I have been using sageTV for a long time so believe me when I tell you that scenario works.

So is the environment variable set properly as a System EV ? That's the only thing I think that would be different between the exe's. The new one get's the license key from the EV.

[nyplayer]

Originally Posted by jusjoken

So is the environment variable set properly as a System EV ? That's the only thing I think that would be different between the exe's. The new one get's the license key from the EV.

This is the key I replaced my original key with My Sage Key

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Frey Technologies]
"LastInstallDir"="C:\\Program Files (x86)\\SageTV\\"
"SAGETVUSERKEY"="My Sage Key"

[tvmaster2]

Originally Posted by jusjoken

On the options page of the install there is a field to enter your license key...I guess if you do not enter it then there is no second chance except by manually adding the key to the environment variables as per the FAQ.

New users do not need this as keys are no longer available but for existing sage users someone could readd the REGISTER cmd and make it add the environment variable

k

hi. for us non-technical types, will this installer work equally as well with either 32 or 64 bit versions, and/or W7 or W10? I need to stay with 32 bit due to 1394 channel changing. thanks

[jusjoken]

Originally Posted by nyplayer

This is the key I replaced my original key with My Sage Key

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Frey Technologies]
"LastInstallDir"="C:\\Program Files (x86)\\SageTV\\"
"SAGETVUSERKEY"="My Sage Key"

That's not the correct location. I do cache the key there during the install but you need to go into control panel, System, Advance Settings, Environment Variables and create or update the key in there.

It is also found at the following location in the registry (where ALL environment variables are stored by windows)...

Under HKLM

SYSTEM\CurrentControlSet\Control\Session Manager\Environment

k

[jusjoken]

Originally Posted by tvmaster2

hi. for us non-technical types, will this installer work equally as well with either 32 or 64 bit versions, and/or W7 or W10? I need to stay with 32 bit due to 1394 channel changing. thanks

In theory yes. I would love it if someone tested that as so far I have only run it on a 64 bit windows OS....but it should work on 32 or 64 bit windows.

k

[nyplayer]

Originally Posted by jusjoken

That's not the correct location. I do cache the key there during the install but you need to go into control panel, System, Advance Settings, Environment Variables and create or update the key in there.

It is also found at the following location in the registry (where ALL environment variables are stored by windows)...

Under HKLM

SYSTEM\CurrentControlSet\Control\Session Manager\Environment

k

I wonder if that is due to UAC?

[Fuzzy]

Originally Posted by nyplayer

I wonder if that is due to UAC?

Not UAC - environment variables are not a registry feature - in fact, they pre-date windows entirely. Windows just chooses to store them in the registry for environment variables that are set on every boot.

[nyplayer]

A reboot fixed I .... it did update the environment variable .... I guess I had to reboot to load the newly added environment levels.

The only thing missing is the Java Heap great work.

Overall A++++

[Tiki]

Originally Posted by nyplayer

This is the key I replaced my original key with My Sage Key

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Frey Technologies]
"LastInstallDir"="C:\\Program Files (x86)\\SageTV\\"
"SAGETVUSERKEY"="My Sage Key"

OK, but is the environment variable set with the key? Sage v9 does not look in the registry. That registry entry is only used for Sage v7 or older.

V9 only looks for the environment variable to be set.

If using Windows 7, right-click on "Computer" and choose "Properties" (or go to the Control Panel and choose "System"). Then click "Advanced System Settings". Then "Environment Variables". There are 2 sets of variables: User and System. I assume this should be a system variable.

++++Edit++++
Never mind, I guess it took me too long to post as others already posted and you already figured this out.

[nyplayer]

Originally Posted by Tiki

OK, but is the environment variable set with the key? Sage v9 does not look in the registry. That registry entry is only used for Sage v7 or older.

V9 only looks for the environment variable to be set.

If using Windows 7, right-click on "Computer" and choose "Properties" (or go to the Control Panel and choose "System"). Then click "Advanced System Settings". Then "Environment Variables". There are 2 sets of variables: User and System. I assume this should be a system variable.

++++Edit++++
Never mind, I guess it took me too long to post as others already posted and you already figured this out.

That is ok no problem help is always appreciated.

[jusjoken]

Originally Posted by nyplayer

A reboot fixed I .... it did update the environment variable .... I guess I had to reboot to load the newly added environment levels.

The only thing missing is the Java Heap great work.

Overall A++++

So....should I set java heap to 0 with the installer since the exe do not?

[nyplayer]

Originally Posted by jusjoken

So....should I set java heap to 0 with the installer since the exe do not?

I personally prefer the equivalent of 300 (768) at the very least. Makes it easier on non techies... the best would be 400 (1024).

Especially if first Installing the Server for the first time 400 (1024) is the best.

[jusjoken]

Originally Posted by nyplayer

I personally prefer the equivalent of 300 (768) at the very least. Makes it easier on non techies... the best would be 400 (1024).

I have not checked the source but Fuzzy stated the IF there is NO setting in the registry OR if the setting is set to "0" then the default is used which is 768.

So if I set it to "0" and it uses the default then at least there is a value in the registry for someone to find and change.

Long term I suggest someone add a config somewhere in the product to adjust this directly.

k

[jusjoken]

Originally Posted by EnterNoEscape

As for the client installation which is what I was playing with, it appears to be working very well. Very nice. I hope we eventually get something that reads v9 on our splash screen, but that's probably not your problem. I know there was a thread full of suggestions; I don't know if it went anywhere.

Splash issue.... this is embedded in the Sage.jar file but I agree this really needs to be updated before I complete the installer....I just would not make sense to have the v9 installer launch the apps with a V7 splash screen.

I suggest...someone... other than me change the 3 splash screens attached here to something generic....with just the Sage TV logo and perhaps the version....something like...

SageTV (logo)
Version 9
By The SageTV Authors

The should match size and bit depth and type of those attached.

Long term IF we ever agree on something new we can change it.

Volunteers ?

k

[nyplayer]

Originally Posted by jusjoken

I have not checked the source but Fuzzy stated the IF there is NO setting in the registry OR if the setting is set to "0" then the default is used which is 768.

So if I set it to "0" and it uses the default then at least there is a value in the registry for someone to find and change.

Long term I suggest someone add a config somewhere in the product to adjust this directly.

k

I tried Increasing and decreasing the Java Heap and it still remained at 768 ... maybe the install SageTV9 is looking somewhere else.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\WOW6432Node\Frey Technologies\SageTV]
"JVMMaxHeapSizeMB"=dword:00000000

[jusjoken]

Originally Posted by nyplayer

I tried Increasing and decreasing the Java Heap and it still remained at 768 ... maybe the install SageTV9 is looking somewhere else.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Classes\VirtualStore\MACHINE\SOFTWARE\WOW6432Node\Frey Technologies\SageTV]
"JVMMaxHeapSizeMB"=dword:00000000

It's here on mine (V7 server)

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV]
"JVMMaxHeapSizeMB"=dword:00000400

[nyplayer]

Originally Posted by jusjoken

It's here on mine (V7 server)

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV]
"JVMMaxHeapSizeMB"=dword:00000400

Yeah I do not have that key ... I will wait for your next release. My test server is ok with 768 for now.

[stuckless]

Originally Posted by jusjoken

It's here on mine (V7 server)

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Frey Technologies\SageTV]
"JVMMaxHeapSizeMB"=dword:00000400

I don't know much about windows programming, but, the source code for this leads me to believe that Wow6432 is not part of the key.

https://github.com/google/sagetv/blo...cher.cpp#L1147

From the code it appears to default to 768mb, and if the JVMMaxHeapSizeMB key exists, it will use it, otherwise it will set it to 0.

It appears the full key would be
HKEY_LOCAL_MACHINE\SOFTWARE\Frey Technologies\SageTV

Unless the windows API is somehow injecting the Wow part there??

[wubdich]

The Wow6432Node registry part will be used if 32bit programms are running on 64bit OS: http://windowsitpro.com/systems-mana...egistry-subkey .

OS will transparently redirect the access from HKEY_LOCAL_MACHINE\SOFTWARE\<company>\<product> to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\<company>\<product> - no need for special codings in the 32bit programm.

[rnadeau]

Is this what you're looking for?