Alaska Software Inc. - Windows 10 (1709) xBase fatal error
Username: Password:
AuthorTopic: Windows 10 (1709) xBase fatal error
Nestor G. TorresWindows 10 (1709) xBase fatal error
on Mon, 11 Dec 2017 12:41:30 +0200
Hi Guys

was running my xBase 1.9 app on Windows 10 (1703) and everything works 
fine. Then along comes Windows update (1709) and application crashes 
with a fatal error.

FATAL ERROR LOG
Not recoverable Error!
SYS Thread-ID: 856
Module: EH
Error Codes: EH: 900 Sub: 0(0) OS: 0 XPP: 0
Call Stack of Thread 1 (856):
Call Stack of GUI Thread (1112):
File: C:\TVHS\PGM\VHS00000.exe
TimeStamp: 20171211 10:12
End of FATAL ERROR LOG.

I do not know what the above is trying to tell me....can anyone assist.

Kind regards
Nestor
Jim LeeRe: Windows 10 (1709) xBase fatal error
on Mon, 11 Dec 2017 19:16:50 +0100
this is PDR  6904
Alaska have a Hotfix

if you run 125% Scaleing try 100% or 150%
if it does not work try change DRIVER settings e.g. 1920x1024 -> 1200x960
Nestor G. TorresRe: Windows 10 (1709) xBase fatal error
on Tue, 12 Dec 2017 06:08:30 +0200
On 2017/12/11 20:16, Jim Lee wrote:
> this is PDR  6904
> Alaska have a Hotfix
> 
> if you run 125% Scaleing try 100% or 150%
> if it does not work try change DRIVER settings e.g. 1920x1024 -> 1200x960

Jim Thank you so much....I had to roll back to 1703 at my customer site. 
And I have paused the updates....I will give this a try when my 
customers business slows down after Christmas..

Again this very much appreciated.
Kind regards
Nestor
James LoughnerRe: Windows 10 (1709) xBase fatal error
on Tue, 12 Dec 2017 18:17:38 -0500
On 12/11/2017 11:08 PM, Nestor G. Torres wrote:
> On 2017/12/11 20:16, Jim Lee wrote:
>> this is PDR  6904
>> Alaska have a Hotfix
>>
>> if you run 125% Scaleing try 100% or 150%
>> if it does not work try change DRIVER settings e.g. 1920x1024 -> 1200x960
> 
> Jim Thank you so much....I had to roll back to 1703 at my customer site. 
> And I have paused the updates....I will give this a try when my 
> customers business slows down after Christmas..
> 
> Again this very much appreciated.
> Kind regards
> Nestor

Note that latest 2.0 versions are also fixed for this problem