MediaPortal 1.7.0 Final We are very happy to present you the final version of MediaPortal 1.7.0 today. This release includes a number of new features and bug fixes. Please report any problems in the bug reporting sections of the forum. Highlights of this release Many of the changes in this release are things that you might not notice at first, but they are designed to improve the stability of MediaPortal moving forwards for the next few releases. Using SkinSettings/Expressions Skin Settings and Expressions are really powerful. Skin designers are going to be doing some amazing things with them in the near future. We have already been testing a home screen editor entirely within the MediaPortal GUI. Look for this in Area 51 very soon. Separate the WindowsPlugins to individual files This is one for the developers. Since MediaPortal started, the core plugins (My Videos, My Music, My Pictures, etc.) have been stored in a single file called WindowsPlugins.dll. This means that a lot of code has been loaded that isn’t always needed. Also, making a change to one plugin often resulted in another plugin developing a new bug. We can’t carry on like that, so the plugins are now in their own self-contained files. This will make things more stable and easier to fix/improve in future. Attention: This change made us ‘bump’ the plugin subsystems, so there is a chance you need an updated plugin to be compatible with the 1.7.0 Release. 1.7 Pre Release compatible plugins will still work fine with this release. Enhancements to the TV and Video OSDs TV recording thumbs and comskip markers were not properly shown in the TV and Video Info OSDs. This is fixed. Improvements to the Installer You probably have the LAV Filters package installed to get the best quality playback of most video files, and TitanExtended installed to provide skin files for your plugins. The installer correctly detects the installed version, and only offers to install these if a newer version is available. Wake On LAN MediaPortal can now wake your server if it is in sleep mode and you want to access your files. Add MediaInfo For Files in the Background We use a code library called MediaInfo to obtain certain information about video files when you play them. This information can be displayed by MediaPortal. Up to now, it has only been possible to obtain this information when you actually play a file. With this release, we have added a setting to allow all files to be scanned in the background. This is turned off by default, so check out the documentation for changes to see where this setting is and how to enable it. We also updated the library to v0.7.67. Full list of changes You can review the complete change log for MP 1.7.0 by using the link below: Changelog: MediaPortal Documentation of new features can be found at the following link: What’s new for MediaPortal 1.7.0 Compiled Plugin related changes Community Plugin Developers should have a look at the following page to find out about the changes which will effect their extensions. Some of these changes are mandatory to become 1.7.0 compatible: changes which affect plugins Additional Information: TVE3 Code freeze At the moment we are working hard on releasing a new version of our TVEngine – which is called TVE3.5. Development is still in early stage and some features are missing. To make a release of this happen in the future we have to put our current TVEngine (TVE3) on code freeze. This means only critical issues will get fixed. Everything else will have to wait for a TVE3.5 release. When we think it is ready for public testing you will find a testbuild in our Area51 forum part. Since we have limited resources we are not able to give you a specific release date. It is ready when it is ready! We’ll hope you understand that. Thanks! Installation, Upgrade, Download and Feedback Installation With MediaPortal 1.6.0 we switched to .NET4 so you need to make sure you have .NET4 installed on your computer (not needed if you are on Windows 8 because it comes with .NET4, but you NEED the .NET 3.5 features enabled!). Otherwise you are not able to install MediaPortal and the installer just quits. Download-Link: Microsoft .NET Framework 4 (Standalone Installer) Aside from that when doing a clean installation of 1.7.0 there is nothing else special to worry about. Upgrade Upgrading from 1.2.x, 1.3.0 Alpha/Beta/RC/Final, 1.4.0, 1.5.0, 1.6.0 and 1.7 Pre Release to 1.7.0 All MediaPortal 1.2.x, 1.3.0 Alpha/Beta/RC/Final, 1.4.0, 1.5.0, 1.6.0 and 1.7 Pre Release installations can be upgraded to 1.7.0, without losing your settings. Plugins: If you are running MediaPortal 1.6.0 or earlier , then it is possible that some of your previously installed plugins will be shown as incompatible after the upgrade to 1.7.0 ! Whether or not a plugin is incompatible depends on the MediaPortal subsystems the plugin uses. Skins: Warning ! Due to the new features and changes introduced in 1.4.0 , none of the 1.3.x skins are compatible with 1.7.0 ! Please contact the author of the skin you use for further information and updates. Upgrading Extensions: The easiest way to upgrade your extensions is by launching the MediaPortal Extension Installer , and let it check for updated versions. However this only works for extensions that use our MPEI system. If the author of the extension releases it as a stand alone installer, you must contact them for an updated version. Upgrading from 1.2.0 Alpha or earlier to 1.7.0 All MediaPortal installations starting with 1.1.0 RC1 can be upgraded to 1.7.0, without losing your settings. If you are running MediaPortal 1.2.0 Alpha or earlier, then none of your extensions (plugins and skins) will work after the upgrade to 1.7.0! You must update your extensions after the upgrade! So, please make sure that 1.7.0 compatible versions of your extensions are available before you start the upgrade! General note about Upgrades Manually stop TV-Service! On some systems our installer is not able to update the TV-Server installation because its files are locked or the service can not be stopped. For upgrades to 1.7.0 we recommend that you manually stop the TV-Service and make sure, via Windows Task Manager (enable the “all users” option), that the TvService.exe process is really gone before starting to upgrade. Custom TV-Service properties If you manually changed the properties of the TV-Service (like restart on error options) , then you must redo these changes after the upgrade. The installer is not able to save and restore your custom service properties when it installs the new version of the TV-Service. Feedback Bugs If you think you found a bug then please post a detailed report in our Bug Reports Forum . Make sure your report includes all the required information . Incomplete reports will be removed to keep the forum clean. Download Finally – the download. We hope that you took the time to read this release news entirely because it includes vital information about the major changes. If you would like to support MediaPortal, we would be happy to receive a small donation ! The Team wishes you a lot of fun with this new release! .::. Download – MediaPortal 1.7.0 Final .::. :: Post a Comment ::
NFC, or Near-Field Communication , is useful for all sorts of things , but you can also use it to lock or unlock your PC when you sit down to work. The Electrodog Show , over at Instructables, shows us how do set it up. Read more… 
itwbennett (1594911) writes “When Jose Vildoza’s father became the victim of ransomware, he launched his own investigation. Diving into CryptoDefense’s code, he found its developers had made a crucial mistake: CryptoDefense used Microsoft’s Data Protection API (application programming interface), a tool in the Windows operating system to encrypt a user’s data, which stored a copy of the encryption keys on the affected computer. Vildoza and researcher, Fabian Wosar of the Austrian security company Emsisoft, collaborated on a utility called the Emsisoft Decrypter that could recover the encrypted keys. In mid-March Vildoza had launched a blog chronicling his investigation, purposely not revealing the mistake CryptoDefense’s authors had made. But Symantec then published a blog post on March 31 detailing the error.” Read more of this story at Slashdot. 
