Windows 64 bit Installer news

[wnjj]

Originally Posted by Tiki

Since my last post I also tried a repair install of Sage (didn't help), and a complete uninstall (and deleted the leftover Sage folder), followed by a fresh re-install with the USBUIRT attached. Also didn't help.

I also downloaded the driver from the USBUIRT website. It appears to be the same version that Sage installed, but I went to Device Manager and told it to update driver to this one anyway. This also made no difference.

How does Sage detect the USBUIRT?

I attached the debug logs in case it helps (running in service mode, so included Sage Client log too). I don't see anything odd in them.

If you reinstalled the drivers from their website, it's likely the 64-bit driver DLL got blown away. The issue is the drivers from their site place the 32-bit DLL incorrectly into the Windows\System32 directory. The 64-bit version of uuirtdrv.dll which needs to be installed there is only available from the SageTV installer (or my post referenced below).

Can you try the manual install I posted here: https://forums.sagetv.com/forums/sho...&postcount=191

You should copy your .ir file(s) over from your 32-bit setup so you need not have to set it all up again.

There must be something missing in the installer flow.

SageTV detects the port simply by being able to call into the driver which in turn opens the device.

[SHS]

Originally Posted by Tiki

Since my last post I also tried a repair install of Sage (didn't help), and a complete uninstall (and deleted the leftover Sage folder), followed by a fresh re-install with the USBUIRT attached. Also didn't help.

I also downloaded the driver from the USBUIRT website. It appears to be the same version that Sage installed, but I went to Device Manager and told it to update driver to this one anyway. This also made no difference.

How does Sage detect the USBUIRT?

I attached the debug logs in case it helps (running in service mode, so included Sage Client log too). I don't see anything odd in them.

Can you check on this
C:\Program Files\SageTV\Common\uu_irsage.dll 445 KB (456,192 bytes) size should be.
C:\Windows\System32\uuirtdrv.dll 278 KB (284,672 bytes) size should be.

[wnjj]

Originally Posted by SHS

Can you check on this
C:\Program Files\SageTV\Common\uu_irsage.dll 445 KB (456,192 bytes) size should be.
C:\Windows\SysWOW64\uuirtdrv.dll 278 KB (284,672 bytes) size should be.

SysWow64 is the 32-bit DLL. What do you have in System32?

[Tiki]

Originally Posted by wnjj

If you reinstalled the drivers from their website, it's likely the 64-bit driver DLL got blown away. The issue is the drivers from their site place the 32-bit DLL incorrectly into the Windows\System32 directory. The 64-bit version of uuirtdrv.dll which needs to be installed there is only available from the SageTV installer (or my post referenced below).

Can you try the manual install I posted here: https://forums.sagetv.com/forums/sho...&postcount=191

You should copy your .ir file(s) over from your 32-bit setup so you need not have to set it all up again.

There must be something missing in the installer flow.

SageTV detects the port simply by being able to call into the driver which in turn opens the device.

What I downloaded from the USBUIRT website today was just a driver (there was no installer, just 3 files in an amd64 folder and 4 files in an i386 folder). I "installed" it manually by going to the device manager and pointing it to the amd64 folder. This was one of the very last things I tried, so don't know that it had any effect.

In any case, I will copy the files from that post and report back shortly.

[wnjj]

Also, if you create a file (even a blank one) with the name 'UU_LOG.ENABLE' in the SageTV main directory (where the .exe is), it will enable logging when you go to select the USB-UIRT as the tuner plugin. A file called 'uuirtlog.txt' will show up.

One other note. The fact that you see 'USB-UIRT Transceiver' listed means the correct 64-bit uu_irsage.dll is in the Common directory. It, in turn will try to load the 64-bit uuirtdrv.dll from Windows\System32.

[SHS]

Originally Posted by wnjj

SysWow64 is the 32-bit DLL. What do you have in System32?

Wrong folder fix that above post LoL

[wnjj]

Originally Posted by Tiki

What I downloaded from the USBUIRT website today was just a driver (there was no installer, just 3 files in an amd64 folder and 4 files in an i386 folder). I "installed" it manually by going to the device manager and pointing it to the amd64 folder. This was one of the very last things I tried, so don't know that it had any effect.

In any case, I will copy the files from that post and report back shortly.

Yeah. Those files are the .dll and .sys files that get installed based the .inf file that USB devices reference to install drivers. In that .inf, it directs the system to copy the 32-bit uuirtdrv.dll into both System32 and SysWow64.

[SHS]

Originally Posted by Tiki

What I downloaded from the USBUIRT website today was just a driver (there was no installer, just 3 files in an amd64 folder and 4 files in an i386 folder). I "installed" it manually by going to the device manager and pointing it to the amd64 folder. This was one of the very last things I tried, so don't know that it had any effect.

In any case, I will copy the files from that post and report back shortly.

You have over write those with the ones in that zip that wnjj posted so look like this
C:\Program Files\SageTV\Common\uu_irsage.dll 445 KB (456,192 bytes) size should be.
C:\Windows\System32\uuirtdrv.dll 278 KB (284,672 bytes) size should be.

[SHS]

Originally Posted by wnjj

Yeah. Those files are the .dll and .sys files that get installed based the .inf file that USB devices reference to install drivers. In that .inf, it directs the system to copy the 32-bit uuirtdrv.dll into both System32 and SysWow64.

Windows doesn't like that as can be come very pickee so it best to copy it over wnjj

[Tiki]

Originally Posted by Tiki

What I downloaded from the USBUIRT website today was just a driver (there was no installer, just 3 files in an amd64 folder and 4 files in an i386 folder). I "installed" it manually by going to the device manager and pointing it to the amd64 folder. This was one of the very last things I tried, so don't know that it had any effect.

In any case, I will copy the files from that post and report back shortly.

OK, Lots to report. First, those files were both different from what the Sage installer gave me (using SageTVSetupx64_9.2.0_beta_1.104.exe). I attached a text file with my notes about the differences. This sounds like the Beta installer doesn't have the correct USBUIRT files.

Second, after copying these files, as you suggested, Sage recognized the USBUIRT as an IR Receiver and it worked correctly.

Third, it still won't let me use the USBUIRT as a transmitter.

Several years back (I think when Vista came out), there was a problem with the USBUIRT drivers where they could not be used as both a transmitter and receiver at the same time due to changes in the Windows driver model (the drivers had worked in XP, but were broken by Vista). They had to update the driver to allow it to work as both a transmitter and receiver simultaneously. I wonder if this old problem has returned?

I will try to disable the remote and see if the blaster starts working again and report back.

[Tiki]

Originally Posted by Tiki

OK, Lots to report. First, those files were both different from what the Sage installer gave me (using SageTVSetupx64_9.2.0_beta_1.104.exe). I attached a text file with my notes about the differences. This sounds like the Beta installer doesn't have the correct USBUIRT files.

Second, after copying these files, as you suggested, Sage recognized the USBUIRT as an IR Receiver and it worked correctly.

Third, it still won't let me use the USBUIRT as a transmitter.

Several years back (I think when Vista came out), there was a problem with the USBUIRT drivers where they could not be used as both a transmitter and receiver at the same time due to changes in the Windows driver model (the drivers had worked in XP, but were broken by Vista). They had to update the driver to allow it to work as both a transmitter and receiver simultaneously. I wonder if this old problem has returned?

I will try to disable the remote and see if the blaster starts working again and report back.

OK, I confirmed that if I changed the remote control to "none", it would allow me to configure the Colossus tuner to use the USBUIRT as a blaster. And, once I set the Colussus to use the USBUIRT, I could not longer enable the USBUIRT as a remote receiver - so this driver doesn't seem to allow simulatneous usage.

Also, even though I could now select the USBUIRT transmitter to blast channels for the Colossus, I could not get it to work. I am using the same IR file from my 32-bit Sage installation, but my cable box doesn't register any activity and I don't see the red light blink on the USBUIRT when I try to change channels or even test IR codes through Sage.

I think I'm at a dead end for now. If you have other ideas for me to try, please let me know.

[wnjj]

Originally Posted by Tiki

OK, I confirmed that if I changed the remote control to "none", it would allow me to configure the Colossus tuner to use the USBUIRT as a blaster. And, once I set the Colussus to use the USBUIRT, I could not longer enable the USBUIRT as a remote receiver - so this driver doesn't seem to allow simulatneous usage.

Also, even though I could now select the USBUIRT transmitter to blast channels for the Colossus, I could not get it to work. I am using the same IR file from my 32-bit Sage installation, but my cable box doesn't register any activity and I don't see the red light blink on the USBUIRT when I try to change channels or even test IR codes through Sage.

I think I'm at a dead end for now. If you have other ideas for me to try, please let me know.

I found this post (https://forums.sagetv.com/forums/sho...91&postcount=2) which I think is the Vista issue you referred to. Are you running in service mode? It sounds likes both at once is a no-go on Win7 or above.

[wnjj]

Originally Posted by wnjj

I found this post (https://forums.sagetv.com/forums/sho...91&postcount=2) which I think is the Vista issue you referred to. Are you running in service mode? It sounds likes both at once is a no-go on Win7 or above.

This post (https://forums.sagetv.com/forums/showthread.php?t=50013) said Jon fixed the DLL at least in beta back then. The problem is that DLL is 32-bit. I would have hoped the 64-bit one I got from Jon directly was also "fixed" but only he would know. If you can show both transmit & receive work when not running in service mode, that would help to confirm this is the issue.

[Tiki]

Originally Posted by wnjj

This post (https://forums.sagetv.com/forums/showthread.php?t=50013) said Jon fixed the DLL at least in beta back then. The problem is that DLL is 32-bit. I would have hoped the 64-bit one I got from Jon directly was also "fixed" but only he would know. If you can show both transmit & receive work when not running in service mode, that would help to confirm this is the issue.

I’ll have to re-Test in non-Service mode tomorrow. I have to put my old server back together now.

John definitely fixed this so it works with 32-bit Sage running in Windows 7 (64 bit).

[wnjj]

Originally Posted by Tiki

I’ll have to re-Test in non-Service mode tomorrow. I have to put my old server back together now.

John definitely fixed this so it works with 32-bit Sage running in Windows 7 (64 bit).

If you get some time, can you also try installing the beta 32-bit version? If that one works but the 64-bit doesn't that's a clue. If beta 32-bit doesn't, try copying uu_irsage.dll from your working system into the Common directory. This is on the off chance that something needed changed in the SageTV source to accommodate this.

[jusjoken]

Originally Posted by Tiki

OK, Lots to report. First, those files were both different from what the Sage installer gave me (using SageTVSetupx64_9.2.0_beta_1.104.exe). I attached a text file with my notes about the differences. This sounds like the Beta installer doesn't have the correct USBUIRT files.

I believe the differences in the Common folder file were just when each of us built that file - unlikely they had different content but would need the files themselves to compare.

This has me most concerned....

Originally Posted by Tiki

uuirtdrt.dll in c:\windows\system32 directory

original:
2.7.00 (7/27/2012)

new:
2.6.9.9 (1/11/2019)

The 2.6.9.9 is the 64bit driver. The 2.7.0.0 is the 32bit one. The installer has both and attempts to copy the 64bit one OVER the 32bit one. Obviously this failed. I believe it also failed for JustFred but in all my testing it works so we need to figure out why the copy sometimes fails. Likely something to do with Microsoft iron hand on the system32 folder but install logs would help as it may indicate why it failed the copy.

Install logs are found in \user\UserName\AppData\Local\Temp and will have odd temp type names but they will have a name similar to "SageTV(x64)_20190112071704_000_SageTVSetupMSI.log"

k

[jusjoken]

Relating to the failed copy of the USBUIRT 64bit driver. I had a log from JustFred and as it failed on his as well I reviewed those logs and see....

MSI (s) (EC:6C) [12:50:55:531]: Executing op: ActionStart(Name=CopyUSBUIRTDRVtoSystem,,)
MSI (s) (EC:6C) [12:50:55:531]: Executing op: CustomActionSchedule(Action=CopyUSBUIRTDRVtoSystem,ActionType=3073,Source=BinaryData,Target=WixQuietExec,CustomActionData="C:\Windows\system32\xcopy.exe" "C:\Program Files\SageTV\redist\usbuirt\amd64\uuirtdrv.dll" "C:\Windows\Sysnative\" /q /y /c /r /i )
MSI (s) (EC:B0) [12:50:55:531]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI83E9.tmp, Entrypoint: WixQuietExec
WixQuietExec:  File creation error - Cannot create a file when that file already exists.
WixQuietExec:  
WixQuietExec:  Unable to create directory - C:\Windows\Sysnative

Clearly the xcopy command failed on his system.

I know what the issue is now as c:\windows\sysnative is an alias on 64bit system that points to c:\windows\system32 ONLY from 32bit apps. This is provided as if a 32bit app uses c:\windows\system32 then Windows will actually use c:\windows\syswow64.

However, from a 64bit app c:\windows\sysnative is not valid so the installer is actually copying the 64bit driver to a real (not virtual) folder called c:\windows\sysnative

So...long story short I need to determine how to make the xcopy in the 64bit MSI installer run in 32bit CMD rather than 64bit.


k

[Tiki]

Originally Posted by jusjoken

I believe the differences in the Common folder file were just when each of us built that file - unlikely they had different content but would need the files themselves to compare.

This has me most concerned....

The 2.6.9.9 is the 64bit driver. The 2.7.0.0 is the 32bit one. The installer has both and attempts to copy the 64bit one OVER the 32bit one. Obviously this failed. I believe it also failed for JustFred but in all my testing it works so we need to figure out why the copy sometimes fails. Likely something to do with Microsoft iron hand on the system32 folder but install logs would help as it may indicate why it failed the copy.

Install logs are found in \user\UserName\AppData\Local\Temp and will have odd temp type names but they will have a name similar to "SageTV(x64)_20190112071704_000_SageTVSetupMSI.log"

k

I backed up the Sage directory after the first install, so still have the old uu_irsage.dll (let me know if you need me to send it), but I did not save the original uuirtdrt.dll file in the windows/system32 directory. I see there is also a SageTV/redist/usbuirt directory in my backup and could send you its contents if that is useful.

Just so you know, this was a fresh install on a clean system, so there should not have been any old files for the installer to copy over. Unless you mean that the installer first installs the 32-bit file and then attempts to copy the 64-bit version over the top?

I found the install logs. Since I ran the installer multiple times now (original install, repair install, uninstall, re-install...) there are several logs. Also there are at least 2 logs for each run of the installer (the 1st run had 3 logs, one for Java). I zipped all of them.

[jusjoken]

Originally Posted by Tiki

I backed up the Sage directory after the first install, so still have the old uu_irsage.dll (let me know if you need me to send it), but I did not save the original uuirtdrt.dll file in the windows/system32 directory. I see there is also a SageTV/redist/usbuirt directory in my backup and could send you its contents if that is useful.

Just so you know, this was a fresh install on a clean system, so there should not have been any old files for the installer to copy over. Unless you mean that the installer first installs the 32-bit file and then attempts to copy the 64-bit version over the top?

I found the install logs. Since I ran the installer multiple times now (original install, repair install, uninstall, re-install...) there are several logs. Also there are at least 2 logs for each run of the installer (the 1st run had 3 logs, one for Java). I zipped all of them.

No need...i know the issue now. Hopefully fixed soon.

k

[Tiki]

Originally Posted by Tiki

I backed up the Sage directory after the first install, so still have the old uu_irsage.dll (let me know if you need me to send it), but I did not save the original uuirtdrt.dll file in the windows/system32 directory. I see there is also a SageTV/redist/usbuirt directory in my backup and could send you its contents if that is useful.

Just so you know, this was a fresh install on a clean system, so there should not have been any old files for the installer to copy over. Unless you mean that the installer first installs the 32-bit file and then attempts to copy the 64-bit version over the top?

I found the install logs. Since I ran the installer multiple times now (original install, repair install, uninstall, re-install...) there are several logs. Also there are at least 2 logs for each run of the installer (the 1st run had 3 logs, one for Java). I zipped all of them.

Oops, forgot the attachment.

In any case, it looks like I have the same error in my log when trying to copy the file over that you pointed out a few minutes ago.