Exe Tuner Plugin doesn't seem to work

[Beelzebub]

Ok
I did the following

* Extracted exetunerplugin.dll to the frey technologies\common directory

* Added the registry setting (for test purposes I changed the command to notepad.exe %channel%.)

* In sagetv, and set the tuner to constant, then selected the Exe Tuner plugin option.


When I change channels nothing happens, I would thing notepad would coming saying it can't open 232.txt or whatever channel I try to goto.

I did notice something strange in this line
mmc/sfir_dev_name=C\:\\Program Files\\Frey Technologies\\Common\\EXETunerPlugin.dll

Should there be a \ before the : in the path.

Oh yeah I'm using SageTV beta 1.48

[Narflex]

Double check you registry settings to make sure they're right.

Also, try selecting a different input (like composite or s-video) instead of constant channel, it should work either way, but it'd be good to rule out that as the problem.

[Beelzebub]

Yeah the reg setting are right and it doesn't work with s-vid, or composite

[HKEY_LOCAL_MACHINE\SOFTWARE\Sage\EXETunerPlugin]
"command"="notepad.exe %CHANNEL%"

I also tried c:\\windows\\notepad.exe %CHANNEL%
and
echo %CHANNEL% > sagechan.txt

nothing

[salsbst]

What about trying the absolute path to notepad.exe but not doubling up on the backslashes?

[Narflex]

Beelzebub, Post your Sage.properties file please.

[Beelzebub]

I upgraded to 1.4.10, and It works perfectly

Now I need to figure out how to get this to work with 2 boxs.

Maybe if you just put a letter in front channel stored in the %CHANNEL% var.

Something Like A237 for Source1 and B237 for source2. Then have a option in the advanced menu to turn it on and off.

[Narflex]

I wrote this awhile back. It should still work fine. It's similar to the standard EXETuner plugin, with 2 differences.

1. It uses this registry location:
HKLM\Software\Frey Technologies\Common\EXEMultiTunerPlugin

2. In the command value stored at the above location, any %DEVICE% strings will be replaced with the corresponding device_name property as specified in the Sage.properties file. device_name is configurable for each input for each card.

This should get you going. :)

If you want the source for the EXE(Multi)unerPlugin let me know. I freely give it out. :)

Thanks.

[snowman]

I have been using this (EXEMultiTunerPlugin) successfully for some time now with 2 dish sat boxes. In fact it is the only thing that has worked 100%. :goodjob: But in trying 2.1, it no longer calls any command placed in the registry. Since I cannot really use sageTv without tuning, I am back to 2.0.20. I just wanted to know if custom external tuning is being abandoned in favour of sage prefered tuner interfaces such as the usb-uirt, etc. I have checked the sage.properties file, and noted the changes, but can't imagine what I should change to make it work. It looks good the way it is. Any news on this is appreciated.

I wrote this awhile back. It should still work fine. It's similar to the standard EXETuner plugin, with 2 differences.

1. It uses this registry location:
HKLM\Software\Frey Technologies\Common\EXEMultiTunerPlugin

2. In the command value stored at the above location, any %DEVICE% strings will be replaced with the corresponding device_name property as specified in the Sage.properties file. device_name is configurable for each input for each card.

This should get you going. :)

If you want the source for the EXE(Multi)unerPlugin let me know. I freely give it out. :)

Thanks.

[snowman]

Just got news from another user saying that this still works! :clap: That's all I needed to know. I'll play around with it on a fresh install in a new partition for testing. The WAF has reached dangerously low levels lately and I fear a 'hammer incident' is close to occurring. The problem I have now is...will the machine get it, or will I... :gun:

[pengdahl]

exetunerplugin and multitunerplugin only work in 2.1 if you disable Sage running as a service. I've submitted a bug report about this - hopefully it'll get fixed.

[salsbst]

pengdahl has someone from Frey confirmed this? I would think that there are some things you can do in order to get it to work.

a) if not already, use a real user account with admin privileges
b) set "allow service to interact with desktop" in the services control panel
c) (if all else fails) play around with granting privileges to this user in the local security policy

Have you done all that?

[snowman]

Thanks for the replys. :goodjob:

I managed to get it working...well sort of working, by disabling sage as a service. I however got held up with the wifes' 'is it broken again?' barage and pulled the plug on 2.1 for now :gun:

After all I can't watch tv from the hospital :nono: (due to unexplained injuries inflicted during sleep :rolleyes2 )


But seriously...our baby is due this week and tv is not on anyones mind at the moment ;)

When things settle down, i'll take another stab at it.

Thanks again everyone! :goodjob: :coffee:

keith

[pengdahl]

pengdahl has someone from Frey confirmed this? I would think that there are some things you can do in order to get it to work.

No, I haven't gotten confirmation.

a) if not already, use a real user account with admin privileges

I did try this, but it didn't work.

b) set "allow service to interact with desktop" in the services control panel

Tried this too.

c) (if all else fails) play around with granting privileges to this user in the local security policy

Haven't tried this, as I stopped experimenting once I figured out how to make it work by turning off the service.

I ran into some other problems too when experimenting with running Sage as a service, such as needing to manually set the password in the services control panel before it would even run under a username, and the fact that it's unclear which configuration file is used when. I also had Sage behave very badly when I tried to get it to work with the USB-UIRT (it would slow down and take about 30 seconds to respond to the mouse or keyboard). I could try to replicate this behavior, but since I'm back to using the tuner plugin and girder to control my system, I moved on to other things.

[pengdahl]

ExeMultiTuner is now working with version 2.1 running as a service - after checking "Allow service to interact with desktop" in the services control panel. :clap:

[fullofnrg]

I want to use the exe turner plugin, and to run sage as a service. Which is fine, but the problem comes when I try to use UNC paths as well (because I have a network encoder).
Basically my problem occurs because I cannot enable 'Allow service to interact with the desktop' unless I use the 'Local System Account', but I cannot use the local system account because it cannot access UNC paths :-(.

I suspect the answer is that I can't run Sage as a service, but I was wondering if others had found a solution?

[BobPhoenix]

I want to use the exe turner plugin, and to run sage as a service. Which is fine, but the problem comes when I try to use UNC paths as well (because I have a network encoder).
Basically my problem occurs because I cannot enable 'Allow service to interact with the desktop' unless I use the 'Local System Account', but I cannot use the local system account because it cannot access UNC paths :-(.

I suspect the answer is that I can't run Sage as a service, but I was wondering if others had found a solution?


Don't know if this will work for you but what I did was create a special administrative account on my PC and changed SageTV service manager to use that account as it's logon account. Then I could use UNC paths.

BobP.

[fullofnrg]

Hi Bob,
Thanks for that. If I use a standard user, I can't use the 'interact with the desktop' option which is required for the USBUIRT and the exe tuner plugin to change the channel on my sky box. This option is only available for the local system account.

[BobPhoenix]

Hi Bob,
Thanks for that. If I use a standard user, I can't use the 'interact with the desktop' option which is required for the USBUIRT and the exe tuner plugin to change the channel on my sky box. This option is only available for the local system account.

Sorry have no other suggestions except maybe a support request to Frey is in order.

BobP.

[mostlyfodder]

dear frey,
*please* make it easier for us to set up the exetuner plugin. i've done it multiple times and here i am STILL screwing around with it, not able to get it to work, searching the forums for ancient threads. please make a wizard or something, many people are using this plugin i think. it's really frustrating.

[Wheemer]

I am using the EXETuner plugin together with HERemote, and I'm running Sage as a service. I have already checked the box to allow sage service to interact with the desktop.

However I get an exception error when trying to tune. Heremote apparently crashes and it want to send info to microsoft. I think this is because of the service mode, because I had it working fine without service.

Has this been resolved yet? Is there a fix anyone can recommend?

Thank You!

[Wheemer]

Just to confirm, the problem completely goes away when not in service mode.

[Wheemer]

Is there any fix for this? I really want to use service mode with UNC paths. HEremote crashes when I try since I can't click "interact with desktop" using my own service logon name. I can't even get girder's event to work....

Please, there has to be some sort of solution.

Thanks!

[salsbst]

I believe the EXE Tuner plugin can be made to run in service mode, but I don't think you would want to try to use Girder to change channels if you're running the service, since Girder doesn't run as a service. It might work if you stay logged in, though.

Anyway, sounds like the problem is with "HERemote", not SageTV.

[Wheemer]

Well the exetuner plugin is made to interface with an external tuning program, such as girder, heremote, etc... So If the exetuner works in service mode but will not allow interaction to these other non-service applications, then its safe to assume the exetuner plugin does not work in service mode. The only way to have it work is to enable the "interact with desktop" option under services. When you are using UNC paths to your recording directories you must run Sageservice under a network login capable user name. In doing so, you lose the option "interact with desktop".

So to sum up, the exetuner plugin does work with girder, heremote etc. Only when using the "localsystem(Default)" login. But you cannot use UNC paths.

This is not really a good solution in my opinion. With software like FireDaemon you can still allow "Interact with desktop" while using a login other than the default. A solution would be for the Sage Sevice Control to somehow implimant the same work around that FireDaemon uses, whatever that may be.

[Wheemer]

Narflex... I can't seem to get this Multi tuner plugin to work with heremote. The original works fine. Is there any reason you might think that it shouldn't work?

Besides the addition of the %DEVICE% option is there any other changes?

Thank You

[Wheemer]

I just tried to use it with girders event.exe and girder's receiving nothing... I've got the registry settings as you said, and I used the normal exetunerplugin registry settings as a guideline.

????

[Wheemer]

figured it out after a few searches on here... it was a problem with long file names in the registry... Had to us C:\PROGRA~1\HEREMO~1\HERemoteHelper.exe %DEVICE% -channel# %CHANNEL% Enter

To get Heremote to work

[Wheemer]

EDIT:

Look like I loose the function of this plugin once I change the device_name=StubDevice to anything else... Not sure what StubDevice is, but it somehow has to be there in order for it to work...

Isn't anyone reading this that has used the multituner plugin, seems like there's no feedback from other users...

[fullofnrg]

I still have the problem too, but due to time constraints I haven't done anything with it. I currently leave my computer on all the time. I was going to work around the problem by using sagewake instead of running Sage as a service.

[ciemat]

I have 2 tunners (1 PVR250 and 1 Plextor MP402).
I want to use Sage 2.1, ExeMultitunerplugin.dll and Girder 3.3 to manage channel changes in 2 Dish receivers.

:clap: I tested the combination with one tuner.
When Sage changes channels Girder recieves:
Device Name = STUBDEVICE
Channels = 123 (what ever channel was changed)

:confused: When I add the second tunner what Device Name will Sage send?
Is there a way to change the device names (like Device1, Device2, etc.)?
What will happen if Sage needs to change both tunners at same time?

:) Thanks in advanced...

[Theodor]

Look like I loose the function of this plugin once I change the device_name=StubDevice to anything else... Not sure what StubDevice is, but it somehow has to be there in order for it to work...
I was having the same problem, and I'm glad to report that I found a solution! :jump:

In the C:\Program Files\Frey Technologies\Common\RemoteCodes folder, you'll see a file called StubDevice.ir. I copied this file into 2 different files (DSTV1.ir and DSTV2.ir) and edited the contents to change StubDevice to DSTV1 (not sure whether the contents change is required, but I did it anyway). I then copied these files into the EXEMultiTunerPlugin subfolder that was already there. After this I edited the Sage.properties file and changed the device_name values to correspond with the 2 new IR files. That's it! :clap:

[puffyelms]

Would anyone be willing to share their gml file for girder that supports this multi tuner plugin configuration?

I have it working with a single tuner (using exetunerplgin.dll), but not sure how to use the %device% parameter within girder.

I have multiple tuners (mostly) working working with the multdcttunerplugin.dll (which bypasses girder), but it only works most of the time. I'd like to see if i could get girder working in this manner.

I'm also using serial cables to change the channel, but shouldn't matter what is used in the gml file, since i can change that part myself.

I've been sruggling with this for some time, thanks.
:confused:

[IncredibleHat]

I was having the same problem, and I'm glad to report that I found a solution! :jump:

In the C:\Program Files\Frey Technologies\Common\RemoteCodes folder, you'll see a file called StubDevice.ir. I copied this file into 2 different files (DSTV1.ir and DSTV2.ir) and edited the contents to change StubDevice to DSTV1 (not sure whether the contents change is required, but I did it anyway). I then copied these files into the EXEMultiTunerPlugin subfolder that was already there. After this I edited the Sage.properties file and changed the device_name values to correspond with the 2 new IR files. That's it! :clap:

When you say you edited the "device_name" values... how did you go about figureing out which one meant what? My sage.properties file, for a unit with only TWO tuner cards, has about 10 device_name entries in it after cryptic numbers groupings, and then ACTUAL device names after a different setting alltogether:

mmc/encoders/1642691032/1/0/device_name=
mmc/encoders/1642691032/2/0/device_name=
mmc/encoders/1642691032/2/1/device_name=
mmc/encoders/1642691032/3/0/device_name=
mmc/encoders/1642691032/3/1/device_name=
mmc/encoders/1642691032/video_capture_device_name=Hauppauge WinTV PVR PCI II Capture
mmc/encoders/1642691032/video_capture_device_num=0
mmc/encoders/551195575/1/0/device_name=
mmc/encoders/551195575/2/0/device_name=
mmc/encoders/551195575/2/1/device_name=
mmc/encoders/551195575/3/0/device_name=
mmc/encoders/551195575/3/1/device_name=
mmc/encoders/551195575/video_capture_device_name=Hauppauge WinTV PVR PCI II Capture
mmc/encoders/551195575/video_capture_device_num=1

Why can't sage simply send the "video_capture_device_num" INSTEAD of the name? Then also have a setting in here of "remote_code_file=StubDevice1.ir" etc?

Excuse my dreaming again... I tend to see 'simple solutions to simple problems'.

Main question is: what where do I change what so that multiple devices being tuned by sage will actually send the proper device code to the exemultitunerplugin ???

[IncredibleHat]

Well, nevermind my above question, because I cannot for the life of me even get ANY plugin to show up in the video source screen (neither the EXETuner, nor the MultiTuner).

I simply believe that these things are no longer functional in the latest versions of SageTV... because this topic is too friggen old with outdated and useless (lacking?) information. I dont even think it knows where to look in the registry anymore as "Frey Technologies" is a depreciated reg location for sagetv.

*sigh* ... man I so hate reading old threads hehe.

Once I get all this working for SageTV6 (I hope)... I will write a NEW GUIDE for people to use that isn't riddled with holes and inaccuracies.

[Alfiegerner]

I'm using the exemultituner plugin with version 6 with no problems. As far as getting it to show up in the video sources screen I'm pretty sure it was just a case of dropping the dll in the common folder.

[mostlyfodder]

Hi everyone,

After about a year away I'm firing up SageTV again. I've got everything working well except...

My USB UIRT won't recognize any IR commands from my DirecTV remote control (the red LED light on the UIRT works fine except when learning from the DirecTV remote.) The USB UIRT drivers are installed, batteries are all good, and the UIRT does pick up the IR signal from my Hauppagge remotes. But, when I'm at the SageTV config menu for 'source setup'. Sage doesn't recognize that I am pressing the DirecTV remote control buttons when I aim the remote at the UIRT...

Has anyone else had this problem? The problem seems to be with Sage accessing the device during learning mode... At all other times, the red LED's function properly. The device otherwise works fine (i.e. I can change menu selections using the Hauppage remote via commands sent to the USB UIRT.)
Please help. I've tried new and old USB UIRT drivers.

Go Bears!!


thanks,

-mostly fodder

[mostlyfodder]

ahhh some things haven't changed in the past year..

i solved my problem :) i tried holding the remote very close to the USB UIRT and it seems to be working at about 1 cm away.

[paxoman]

Hi again guys beening try to get the plugin Exemultitunerplugin to work so far i have got sage to send the commands to girder with payload1(device (StubDevice1 and StubDevice)) and payload2(channel) but now sure how to make the gml for girder

i have a gml that is working with exetunerplugin (works great thanks who ever i got that1 of :clap: ) here is the script

l = strlen(pld1);
for i = 1,l-1 do
s = strsub(pld1,i,i)
TriggerEvent("cable-motorola-"..s,18);
TriggerEvent("Global-Scripts-Pause",18,500);
end
s = strsub(pld1,l,l)
TriggerEvent("cable-motorola-"..s,18);
TriggerEvent("Global-Scripts-Pause",18,200);
TriggerEvent("cable-motorola-enter",18);
TriggerEvent("Global-Scripts-Pause",18,300);
TriggerEvent("cable-motorola-exit",18);

Now this is the script for the exemultitunerplugin witch i sort of made and need help with

u = strlen(pld1);
if (u == StubDevice1) then
l = strlen(pld2);
for i = 1,l-1 do
s = strsub(pld2,i,i)
TriggerEvent("cable-motorola-"..s,18);
TriggerEvent("Global-Scripts-Pause",18,500);
end
s = strsub(pld2,l,l)
TriggerEvent("cable-motorola-"..s,18);
TriggerEvent("Global-Scripts-Pause",18,200);
TriggerEvent("cable-motorola-enter",18);
TriggerEvent("Global-Scripts-Pause",18,300);
TriggerEvent("cable-motorola-exit",18);
end


if (u == StubDevice) then
l = strlen(pld2);
for i = 1,l-1 do
s = strsub(pld2,i,i)
TriggerEvent("cable1-motorola-"..s,18);
TriggerEvent("Global-Scripts-Pause",18,500);
end
s = strsub(pld2,l,l)
TriggerEvent("cable1-motorola-"..s,18);
TriggerEvent("Global-Scripts-Pause",18,200);
TriggerEvent("cable1-motorola-enter",18);
TriggerEvent("Global-Scripts-Pause",18,300);
TriggerEvent("cable1-motorola-exit",18);
end


so any help would b most welcome of if and 1 has a gml ready made that would b great too

[jpaddock3000]

OK, I'm somewhat new to the exemultituner plugin. I'm using firewire to change my channels on my cable box, but I want Sage to change the channels for me and I haven't been able to get it to work. I'm now at the newest version of Sage 6.4.8. I'm also running SageTV as a service.

My registry entry is as follows:
command=D:\Software\SageTV\Firewire\channelw.exe -f -a4 %DEVICE% %CHANNEL%

If I run this command from the command line, it changes the channel no problem.

My dll is located:
C:\Program Files\SageTV\Common

I have a file named 2.ir located:
C:\Program Files\SageTV\Common\RemoteCodes\EXEMultiTunerPlugin

Contents of 2.ir are:
2 38000 400 3

My properties file for the section that should matter:
mmc/encoders/551195576/1/0/available_channels=
mmc/encoders/551195576/1/0/brightness=116
mmc/encoders/551195576/1/0/contrast=121
mmc/encoders/551195576/1/0/device_name=
mmc/encoders/551195576/1/0/hue=128
mmc/encoders/551195576/1/0/last_channel=
mmc/encoders/551195576/1/0/provider_id=0
mmc/encoders/551195576/1/0/saturation=113
mmc/encoders/551195576/1/0/sharpness=63
mmc/encoders/551195576/1/0/tuning_mode=
mmc/encoders/551195576/1/0/tuning_plugin=
mmc/encoders/551195576/1/0/tuning_plugin_port=0
mmc/encoders/551195576/1/0/video_crossbar_index=0
mmc/encoders/551195576/1/0/video_crossbar_type=1
mmc/encoders/551195576/2/0/available_channels=
mmc/encoders/551195576/2/0/brightness=-1
mmc/encoders/551195576/2/0/contrast=-1
mmc/encoders/551195576/2/0/device_name=
mmc/encoders/551195576/2/0/hue=-1
mmc/encoders/551195576/2/0/last_channel=
mmc/encoders/551195576/2/0/provider_id=0
mmc/encoders/551195576/2/0/saturation=-1
mmc/encoders/551195576/2/0/sharpness=-1
mmc/encoders/551195576/2/0/tuning_mode=
mmc/encoders/551195576/2/0/tuning_plugin=
mmc/encoders/551195576/2/0/tuning_plugin_port=0
mmc/encoders/551195576/2/0/video_crossbar_index=0
mmc/encoders/551195576/2/0/video_crossbar_type=2
mmc/encoders/551195576/2/1/available_channels=
mmc/encoders/551195576/2/1/brightness=116
mmc/encoders/551195576/2/1/contrast=121
mmc/encoders/551195576/2/1/device_name=2
mmc/encoders/551195576/2/1/hue=128
mmc/encoders/551195576/2/1/last_channel=108
mmc/encoders/551195576/2/1/provider_id=962144708217
mmc/encoders/551195576/2/1/saturation=113
mmc/encoders/551195576/2/1/sharpness=63
mmc/encoders/551195576/2/1/tuning_mode=
mmc/encoders/551195576/2/1/tuning_plugin=C\:\\Program Files\\SageTV\\Common\\EXEMultiTunerPlugin.dll
mmc/encoders/551195576/2/1/tuning_plugin_port=0
mmc/encoders/551195576/2/1/video_crossbar_index=1
mmc/encoders/551195576/2/1/video_crossbar_type=2
mmc/encoders/551195576/3/0/available_channels=
mmc/encoders/551195576/3/0/brightness=-1
mmc/encoders/551195576/3/0/contrast=-1
mmc/encoders/551195576/3/0/device_name=
mmc/encoders/551195576/3/0/hue=-1
mmc/encoders/551195576/3/0/last_channel=
mmc/encoders/551195576/3/0/provider_id=0
mmc/encoders/551195576/3/0/saturation=-1
mmc/encoders/551195576/3/0/sharpness=-1
mmc/encoders/551195576/3/0/tuning_mode=
mmc/encoders/551195576/3/0/tuning_plugin=
mmc/encoders/551195576/3/0/tuning_plugin_port=0
mmc/encoders/551195576/3/0/video_crossbar_index=0
mmc/encoders/551195576/3/0/video_crossbar_type=3
mmc/encoders/551195576/3/1/available_channels=
mmc/encoders/551195576/3/1/brightness=-1
mmc/encoders/551195576/3/1/contrast=-1
mmc/encoders/551195576/3/1/device_name=
mmc/encoders/551195576/3/1/hue=-1
mmc/encoders/551195576/3/1/last_channel=
mmc/encoders/551195576/3/1/provider_id=0
mmc/encoders/551195576/3/1/saturation=-1
mmc/encoders/551195576/3/1/sharpness=-1
mmc/encoders/551195576/3/1/tuning_mode=
mmc/encoders/551195576/3/1/tuning_plugin=
mmc/encoders/551195576/3/1/tuning_plugin_port=0
mmc/encoders/551195576/3/1/video_crossbar_index=1
mmc/encoders/551195576/3/1/video_crossbar_type=3
mmc/encoders/551195576/audio_capture_device_index=-1
mmc/encoders/551195576/audio_capture_device_name=
mmc/encoders/551195576/audio_capture_device_num=0
mmc/encoders/551195576/audio_processor=
mmc/encoders/551195576/broadcast_standard=
mmc/encoders/551195576/capture_config=67600
mmc/encoders/551195576/default_device_quality=
mmc/encoders/551195576/delay_to_wait_after_tuning=0
mmc/encoders/551195576/device_class=DirectShow
mmc/encoders/551195576/dshow_tv_type=
mmc/encoders/551195576/encoder_merit=0
mmc/encoders/551195576/encoding_host=
mmc/encoders/551195576/forced_video_storage_path_prefix=
mmc/encoders/551195576/last_cross_index=1
mmc/encoders/551195576/last_cross_type=2
mmc/encoders/551195576/live_audio_input=
mmc/encoders/551195576/never_stop_encoding=false
mmc/encoders/551195576/video_capture_device_name=Hauppauge WinTV PVR PCI II Capture
mmc/encoders/551195576/video_capture_device_num=2
mmc/encoders/551195576/video_encoding_params=DVD Standard Play
mmc/encoders/551195576/video_processor=

Any help would be greatly appreciated.

Thank you

[mscdex]

i am having the same problem as jpaddock3000 BUT i am able to change channels on sage in service mode about 4 times before it stops working. I can still change channels from command line.

[Midwestfarmer]

I wrote this awhile back. It should still work fine. It's similar to the standard EXETuner plugin, with 2 differences.

1. It uses this registry location:
HKLM\Software\Frey Technologies\Common\EXEMultiTunerPlugin

2. In the command value stored at the above location, any %DEVICE% strings will be replaced with the corresponding device_name property as specified in the Sage.properties file. device_name is configurable for each input for each card.

This should get you going. :)

If you want the source for the EXE(Multi)unerPlugin let me know. I freely give it out. :)

Thanks.


Narflex could you please post the source code for this plugin. I would like to update / simplify for my needs. THanks.

[Midwestfarmer]

I never got the source. Any chance still ?

[jchiso]

Does the EXEMultiTuner plugin work with 64-bit Windows 8?

[wbarber69]

it should, I use it for http tuning and have used it on 64 bit but I didn't like 64 bit for my server so I reverted back to 32.

[jchiso]

it should, I use it for http tuning and have used it on 64 bit but I didn't like 64 bit for my server so I reverted back to 32.

Thanks for the confirmation. It does work under 64-bit Windows 8, but you have to place the registry command in a different location (the "Wow6432Node" folder). I was not aware of that ...

[wbarber69]

sounds right