Opening the ESV Bible Audio Stopped Working after Windows 10 was upgraded

Page 1 of 1 (5 items)
This post has 4 Replies | 0 Followers

Posts 1
Michael P. Schloss | Forum Activity | Posted: Sat, Aug 29 2015 10:41 AM

35745.Logos Log Files.zip

Posts 25189
Forum MVP
Dave Hooton | Forum Activity | Replied: Sun, Aug 30 2015 5:41 PM

I presume you upgraded (somehow?) to Win 10 after 29 Aug as that log shows Windows 8 and no error. So tell us a bit more about the upgrade circumstances and the Logos problem. If necessary you should re-enable logging and resubmit logs showing the problem.

However, it must be asked why you have not also upgraded to Logos 6 (free) as that is supported and would likely eliminate the issue (or allow Faithlife Support to diagnose it).

Dave
===

Windows 10 & Android 8

Posts 8112
LogosEmployee

Dave Hooton:
that log shows Windows 8

It doesn't necessarily.

In Windows 8.1 and 10, the "GetVersionEx" OS function no longer actually returns the version of the OS (see https://msdn.microsoft.com/en-us/library/windows/desktop/Dn302074(v=VS.85).aspx) unless you know a "secret handshake" indicating that your program has been tested on that version of Windows. Since Logos 4 was never marked as compatible with Windows 8.1, it will never log a Windows version higher than 6.2 (Windows 8). Similarly, if Windows 11 ever comes out and someone tries to run Logos 5 on it, it will log the version as Windows 10 because it doesn't know the Windows 11 secret handshake (and Windows 10 is the highest one it knows).

Posts 8112
LogosEmployee

Like Dave, I'd also recommend the free Logos 6 update: https://www.logos.com/install 

Posts 25189
Forum MVP
Dave Hooton | Forum Activity | Replied: Mon, Aug 31 2015 1:50 PM

Bradley Grainger (Faithlife):
It doesn't necessarily. ...

Thanks, Bradley.

MS mumbo, jumbo again!

Dave
===

Windows 10 & Android 8

Page 1 of 1 (5 items) | RSS