Thread: WHDLoad 18.2
View Single Post
Old 09 January 2016, 13:03   #69
Registered User
Join Date: Oct 2009
Location: Germany
Posts: 1,971
What you can do is reading the WHDLoad History.txt file. Especially from V17.1 upwards. Compare your WHDLoad.prefs with the current one. There were some updates. With comparing and thinking you should be able to find the culprit. If that doesn`t help I would ask Wepl if he has a hint for you.
daxb is offline  
Page generated in 0.03894 seconds with 10 queries