Normal
OK, an update.Thanks for the tip regarding the restart settings option.I was aware of that, and had it disabled already.I made some progress and actually got MediaPortal 2.2 pre-release to fully startup.I had noticed that Windows update has updated my Nvidia cards drivers.As a test, I changed the drivers to use the basic Windows display drivers from Windows itself.MediaPortal starts normally and works fine.It would appear that the issue I am encountering with MediaPortal 1.21 and 1.22 pre-release, is actually Nvidia driver related.My working MediaPortal 1.20 Final drive image uses much older NVidia drivers than what the Windows Update installs.As a test, I updated my working MediaPortal 1.20 Final config using Windows Update, and it updated the display drivers to latest WHQL ones, which is a few revisions behind the latest available. It broke the startup again.I changed the display drivers to use Microsoft basic drivers, and MediaPortal starts loading again fine.Yes, will send some logs, but it seems to be NVidia driver related.
OK, an update.
Thanks for the tip regarding the restart settings option.
I was aware of that, and had it disabled already.
I made some progress and actually got MediaPortal 2.2 pre-release to fully startup.
I had noticed that Windows update has updated my Nvidia cards drivers.
As a test, I changed the drivers to use the basic Windows display drivers from Windows itself.
MediaPortal starts normally and works fine.
It would appear that the issue I am encountering with MediaPortal 1.21 and 1.22 pre-release, is actually Nvidia driver related.
My working MediaPortal 1.20 Final drive image uses much older NVidia drivers than what the Windows Update installs.
As a test, I updated my working MediaPortal 1.20 Final config using Windows Update, and it updated the display drivers to latest WHQL ones, which is a few revisions behind the latest available. It broke the startup again.
I changed the display drivers to use Microsoft basic drivers, and MediaPortal starts loading again fine.
Yes, will send some logs, but it seems to be NVidia driver related.