Resolved-Workaround: initialization Error!
#11
Hey. I tested again all builds
OK: 504, 511, 512 (512 this my mistake)
Error: 521, 539, 540, 544, 546

Sponsored links

#12
(04-05-2016, 01:01 AM)turtleli Wrote: Could you also test the AppVeyor build when I merged the PR (just to rule out a buildbot issue)? https://ci.appveyor.com/api/buildjobs/nh...ppVeyor.7z

And can any other Windows 7 x64 users also tell me whether they experience issues with these builds or not.

No luck with that one either. I have also confirmed that 512 is the first non-working build. 511 works fine for me.
#13
(04-05-2016, 01:47 AM)AlexVS Wrote: Hey. I tested again all builds
OK: 504, 511, 512 (512 this my mistake)
Error: 521, 539, 540, 544, 546
(04-05-2016, 02:05 AM)CK1 Wrote: No luck with that one either. I have also confirmed that 512 is the first non-working build. 511 works fine for me.

???? So which is it? 512 or 521?

If it happens to be a general Windows 7 issue then I'll have to revert the changes and attempt a take 2 later (I hope not).
#14
Not sure what AlexVS meant, but to reiterate
  • 511 is the last working build
  • 512, 521, and Appveyor build 518 all do not work
#15
(04-05-2016, 02:53 AM)turtleli Wrote: ???? So which is it? 512 or 521?

If it happens to be a general Windows 7 issue then I'll have to revert the changes and attempt a take 2 later (I hope not).

#16
Win 7 SP1 x64 here, couldn't replicate.

v1.5.0-dev-521-g7736c90 works
pcsx2-v1.5.0-dev-518-g16ef7ca-master-783-vs2015-Win32-AppVeyor.7z works
v1.5.0-dev-512-g7f3f6e9 works
[Image: newsig.jpg]
#17
@AlexVS:

Can you please copy the ini folder from a working version to a non working version? The same for the portable.ini.
Maybe it is just an issue with the FirstTimeWizzard...
#18
(04-05-2016, 11:15 AM)willkuer Wrote: @AlexVS:

Can you please copy the ini folder from a working version to a non working version? The same for the portable.ini.
Maybe it is just an issue with the FirstTimeWizzard...

I tried replacing the method. It helps only exchange GS plugin on version of the 511 for example. As I think the problem is in the new version of the GS plugin
#19
You could run dependency walker on this file and look for obvious missing but required dll files...
#20
(04-05-2016, 01:08 PM)willkuer Wrote: You could run dependency walker on this file and look for obvious missing but required dll files...

All updates are installed several times, everything is checked, but the plugin still wants something Wacko




Users browsing this thread: 1 Guest(s)