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
Input / Output interfaces
Mini Display
Support for Futaba DM140GINK
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="rsbrux" data-source="post: 1228479" data-attributes="member: 49539"><p>understood</p><p></p><p>I understand your misgivings, and I have considered using WIndows 10. In fact, I got the Intel Compute Stick mentioned in my system specs with Windows 10 preinstalled in order to play around with it. However, I have many reasons for preferring Windows 7, which I will be happy to share with you in another post. Unfortunately, my reasons appear irrelevant, in view of the results described below. If Windows 7 is not viable, I would still prefer Windows 8.1 to Windows 10, if that is an option</p><p></p><p>Unfortunately, no joy {:-(</p><p>The results were sobering, to say the least. To avoid cluttering up this post, I have attached a text file describing the various error messages received, including the text from their "details" panes.</p><p></p><p>Is it still worthwhile to do any of this, given the failure to install CIC?</p><p></p><p>P.S. I was able to start CIC, which again displayed a window containing sub-elements, as well as a dialog offering an update, before crashing with another .NET unhandled exception.</p><p>The link in your post installed v2.2.10; the update offered was v2.2.11. After restarting CIC, I succeeded in clicking the update button before it crashed. This appeared to perform the update and peresented a Windows Firewall dialog asking me to allow the new version (which I did). Now starting CIC shows a window with the newer version number. However, the new version also produces an immediate .NET unhandled exception. I am running .NET Framework 4.6.1 because of known problems reoprted against later versions.</p><p></p><p>P.P.S. The problems I reported were apparently due to installing and running CIC in an RDP session. After uninstalling, rebooting, reinstalling and updating, it now appears stable (at least running locally). I will proceed with the HID SW.</p></blockquote><p></p>
[QUOTE="rsbrux, post: 1228479, member: 49539"] understood I understand your misgivings, and I have considered using WIndows 10. In fact, I got the Intel Compute Stick mentioned in my system specs with Windows 10 preinstalled in order to play around with it. However, I have many reasons for preferring Windows 7, which I will be happy to share with you in another post. Unfortunately, my reasons appear irrelevant, in view of the results described below. If Windows 7 is not viable, I would still prefer Windows 8.1 to Windows 10, if that is an option Unfortunately, no joy {:-( The results were sobering, to say the least. To avoid cluttering up this post, I have attached a text file describing the various error messages received, including the text from their "details" panes. Is it still worthwhile to do any of this, given the failure to install CIC? P.S. I was able to start CIC, which again displayed a window containing sub-elements, as well as a dialog offering an update, before crashing with another .NET unhandled exception. The link in your post installed v2.2.10; the update offered was v2.2.11. After restarting CIC, I succeeded in clicking the update button before it crashed. This appeared to perform the update and peresented a Windows Firewall dialog asking me to allow the new version (which I did). Now starting CIC shows a window with the newer version number. However, the new version also produces an immediate .NET unhandled exception. I am running .NET Framework 4.6.1 because of known problems reoprted against later versions. P.P.S. The problems I reported were apparently due to installing and running CIC in an RDP session. After uninstalling, rebooting, reinstalling and updating, it now appears stable (at least running locally). I will proceed with the HID SW. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Input / Output interfaces
Mini Display
Support for Futaba DM140GINK
Contact us
RSS
Top
Bottom