Increasing Java Heap on Windows 7 when using local admin

[razrsharpe]

Originally Posted by gplasky

If you run the utility from babgvant then right click on the utility and choose "Run as Administrator".

Gerry

ya that only works if UAC is off or the "Administrator" is the user that runs sagetv... When you do that that account is run with the "administrator" credentials and you won't have direct access to the virtualized ones for the non administrator. If you are using UAC you need to manually go find the address in the registry using the address in the post i linked to earlier....

[Taddeusz]

Ok, hunting down the VirtualStore settings fixed it. Now my SageTV Client shows it has 1GB available to it without having to run as an administrator.

[parkimar]

likewise - thanks razrsharpe and everyone else who posted !

Cheers

Mark

[bohan]

I have the similar problem on XP, this is how I fixed it:

Precondition: two accounts on system, "limited" (a limited user) and "root" (first administrator user)

1. Change the registry key using regedit or the tool, but make sure you run either tool as the first admin user (in my case "root").

2. run SageTVServiceControl as the "root".

3. change the service account to "root"

4. stop, disable, enable then start the service

5. on the same machine run the SageTV Client as "root", and check system messages (NOTE: !TRAP! NOTE: I kept hitting my head on the wall when running SageTV Client as "limited" and still seeing the 400MB max heap each time - I now realise this is the heap for the client only).

6. hope that helps. I realise the Win7/Vista issues have more to do with the system protection features causing the wrong hives to be read/changed, but perhaps this still some relevance.

[ProNoob]

Just confirming this worked for me too. I'm running SageTV as a service on Windows XP Pro SP3. I had to make the account, which SageTV is running under, an administrator to get SageTV to pick up the registry setting. This fixed some of the studdering I've been experiencing and OOM errors in the log.

I attribute the remaining studdering I'm experiencing when watching BD movies to WIFI. I find there's no studdering at all when using a network cable. Looks like I've found my next project: pulling cable.