Page 1 of 1

Now I've done it! UU_IRSAGE.DLL broken

PostPosted: Sun Jan 11, 2004 4:21 pm
by Guest
Now I've done it (or MS has).

Everything was working fine with regard to "uu_irsage.dll" plugin for Sage until I let the MS "Updater" install a security fix for the MS Java VM. This fix was noted by MS as un-installable. I guess I was supposed to have apriori knowledge that it would break "uu_irsage.dll".

I uninstalled Sun Java 1.4.1_03 and installed the latest 1.4.1_06 to no avail. The Sage "hs_err.....log" reads in short:

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x255254B0
Function=[Unknown.]
Library=D:\Multimedia\SageTV\Common\uu_irsage.dll

NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.

If I rename uu_irsage.dll to defeat it, Sage will run (but ofcourse no USB UIRT control). How the heck to back out of this? Thanks MS.

DFA

uu_irsage.dll Broken

PostPosted: Sun Jan 11, 2004 5:07 pm
by Guest
Some more info:

OS is W2K, SP3.

I installed other security patches as well but think the MS Java VM update is to blame but not 100% necessarily. I would think that SP4 would have these fixes I installed rolled up into it as well. So, may not be an isolated issue as time goes on.

DFA

One more thing (like Colombo would say)

PostPosted: Sun Jan 11, 2004 5:18 pm
by Guest
USB UIRT seems to be working fine by itself. Girder recognizes it and the UIRT responds to any IR signal with normal flashing red light.

Problem appears specific to Sage UU_IRSAGE.DLL and related to MS fixe(s).

DFA

PostPosted: Sun Jan 11, 2004 5:58 pm
by Guest
Case Closed .... Call off the dogs:

I went throgh Sage setup and chose new device for the USB UIRT and reprogrammed the codes again. I had hand deleted the original file that had been earlier created (SA3100HD.ir) thus creating a new one. This took care of it, gosh knows why. But evrything OK again.

Anyone else running into this error is advised to try this.

DFA

PostPosted: Sun Jan 11, 2004 8:16 pm
by jrhees
Thanks for solving your own problem :)

I haven't a clue either as to what was happening...

However, I've seen *much* stranger things happen to PC's after installing MS updates!

-Jon