home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
1.32 X64 does not detect HD Homerun channels, 1.31 32-bit does
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="wiyosaya" data-source="post: 1296737" data-attributes="member: 145864"><p>Thanks to the team for working on this. I'll switch to x64 when it sounds like its reasonably stable and working.</p><p></p><p>I'm not sure this will help and someone will probably figure it out anyway, but I had something like this happen in my job. I have a .NET project that calls an unmanaged Fortran dll. Yes, Fortran. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite11" alt=":rolleyes:" title="Roll Eyes :rolleyes:" loading="lazy" data-shortname=":rolleyes:" /> IIRC, what was happening was that there was an X86 dll in the path that was being found instead of the proper x64 dll; essentially, there were paths to both, and the x86 dll was being found first for an x64 project. My .net project is also explicitly compiled as x64.</p><p></p><p>Unfortunately, some of the exceptions, like the "BadImageFormatException" that are thrown by .net do not point to what is actually causing the problem and it might take some digging to get to the "real" issue.</p></blockquote><p></p>
[QUOTE="wiyosaya, post: 1296737, member: 145864"] Thanks to the team for working on this. I'll switch to x64 when it sounds like its reasonably stable and working. I'm not sure this will help and someone will probably figure it out anyway, but I had something like this happen in my job. I have a .NET project that calls an unmanaged Fortran dll. Yes, Fortran. :rolleyes: IIRC, what was happening was that there was an X86 dll in the path that was being found instead of the proper x64 dll; essentially, there were paths to both, and the x86 dll was being found first for an x64 project. My .net project is also explicitly compiled as x64. Unfortunately, some of the exceptions, like the "BadImageFormatException" that are thrown by .net do not point to what is actually causing the problem and it might take some digging to get to the "real" issue. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
1.32 X64 does not detect HD Homerun channels, 1.31 32-bit does
Contact us
RSS
Top
Bottom