#888 Can't open SID settings.

[e5frog]

I can't open "SID settings" in the official release "Version 3.0 (win32 x86 mingw)" on my Windows XP SP3 computer I get an error window with thtis header: "VICE Error!"
And this exact message:
"An unexpected error occurred. Recieved signa 11 ()."
When clicking OK it quits x64.

I have simply installed 3.0 to it's own folder in the program folder.

This one works fine: "Version 2.4 (win32 x86 mingw)"

A recent report on lemon64.com says a guy using OSX has the same problem.

Is WinVICE dependent on any particular new programs, dll files or whatever that 2.4 doesn't?

/ Fredric

[e5frog]

I have an AMD opteron 180 CPU.

[compyx]

I can't reproduce this behaviour using a Windows XP SP3 VM. I've tried the "official" 3.0a x86 release, a recent nightly build, and a version I compiled myself a couple of days ago.

Could you try (in a terminal): x64.exe -default
That will start x64.exe without reading the config file.

[e5frog]

Tried to run it from cmd "x64.exe -default", gives same error if clicking "SID settings", didn't think it was a config problem as I have made no config, just started it as it downloaded.

I have deleted the installation and downloded it again, but it's the same.
Path to installation is: c:\program\WinVICE-3.0a-x86

Maybe problem lies in one of the dll-files - in combination with my computer, the 2.4 has no dll-files at all. I'm thinking mostly in case I have some other version of any of these in a windows-folder and that is used - and not working instead of the ones in the folder.

[compyx]

I think VICE uses the DLL's in its own directory, rather than any DLL's in system32 or wherever, but I could be wrong.

Could you perhaps download a recent nightly build from http://vice.pokefinder.org/ and see if the problem is in one of those as well?

[e5frog]

The same error message occurs when entering SID settings in vsid.exe, x64.exe, x64dtv.exe, x64sc.exe, x128.exe, xcbm2.exe, xcbm5x0.exe and xscpu64.exe

The "signal 11 ()" must mean something, can't be a general error message?

Oddly... after going through all these and have them crash, I started x64.exe again - while still having xscpu64.exe running with the error message - going into SID settings works, no problem. Even if I close the crashed xscpu64.exe I could still return into SID settings in the x64.exe that I opened while the error message was showing.

So solution is to run one, crash it, and then start another - how handy. Not that I need to change SID settings much.

[compyx]

Okay, so we've determined the bug is also present in current trunk. The signal 11 is a segmentation fault, which can mean many things, but shouldn't happen obviously.

The 'running one emu, crashing it and using another emu' seems again to indicate some illegal memory accesses, perhaps in a shared lib.

I'll try to figure this out, but I'm not a Windows hacker at all.

Thanks for testing!

[e5frog]

Trying nightly build "WinVICE-3.0-x86-r33051", no problem there. But who knows what else doesn't work or was left in the middle of editing at the time of compilation?

[compyx]

Well, there's always a small risk of regressions. We don't actually keep a stable branch and a dev branch like some projects do, we don't have the manpower.

Even the 3.0a was built from current trunk. So my advise would be to use a nightly that works, and from time to time check out a new one (installing in Desktop or wherever, and if that works properly, replace the old nightly.

You can track our progress using the 'Summary' item here on the project page, if there are any commits that might fix a bug you've run into, give a new version a try.

And if you encounter any bugs, please post them here, this is where the devs check bugs, only some of us hang out on Lemon or CSDb or any other forum/website.

[gpz]

closing, the windows UI is dead and will get replaced by the GTK3 port soon. you may want to use the SDL port for the time being if the problem persists