| |
Dano
Registered: Jul 2004
Posts: 230 |
Anyone knows what happened to vice.pokefinder.org?
Seems like there is no new build on http://vice.pokefinder.org/ since the 08.05.2017.
I already mailed them but did not get a reply back.
Anyone knows what's up with the site? I guess it's the only site to get daily builds of the latest WinVice? |
|
... 76 posts hidden. Click here to view all posts....
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11335 |
on windows? on linux this works here |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Strange, I built Gtk3VICE-x64 on Win10 with msys2 and managed to make the monitor window hang once by doing `i 0800 d000` and then resizing the window and attempting to scroll up.
Any attempt after that results in normal behaviour, I can scroll up to $3410, which appears to be the size of the VTE buffer (ie ~ 1000 lines), it doesn't scroll up after that.
I assume this also works with POKE2,2:SYS2 ? Makes for quicker testing. |
| |
Raistlin
Registered: Mar 2007
Posts: 656 |
I get some odd crashes in the Monitor on Windows... if I can get the code compiling I can take a look at the cause... it seems to happen when I switch to other apps (eg. Visual Studio) and switch back. Sometimes if i’ve been viewing memory (eg M 8000) then as i switch back to Vice I see that the memory output has highlighting 100% red ... and then it crashes.
Can’t easily give repro steps other than this so i’ll myself sometime soon. |
| |
Count Zero
Registered: Jan 2003
Posts: 1916 |
I am getting the crash under Windows 7 with the latest nightly r35622 still. The window resize is not even required - using the slider always leads to a crash here.
PS: and yes - crashes with POKE2,2:SYS2 as well. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11335 |
is it actually related to CPU JAM? |
| |
Count Zero
Registered: Jan 2003
Posts: 1916 |
No :)
ALT+H for monitor, "i 0800 d000", then use the slider. Crashes always. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Nightly builds also fails on my Win10 box with `i 0800 d000`, but it works when setting `bank ram`. I get a lot of non-ascii tokens in the monitor with the $a000+ stuff even causing the monitor to output some text with a red background.
On 64-bit Gtk3VICE, these non-ascii tokens are properly replaced with normal ascii tokens ('.' for non-ascii).
So somehow the 32-bit build doesn't properly translate the data into printable characters and vte fails. |
| |
Dano
Registered: Jul 2004
Posts: 230 |
out of curiosity.. is there any benefit on having a 64bit version of vice instead of the 32bit?
would be nice if the site had the 64bit version then aswell. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11335 |
the benefit is that a single nightly build works on all windows (more or less =P). you should be glad anyone gives a damn to even provide this. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Count zero:
Try setting LC_ALL=C, that appears to "solve" the problem. When using msys2 you can use `LC_ALL=C src/x64`, on Windows with cmd.exe you'll have to use `set LC_ALL=C` before running x64.exe.
So now we need to find a way to set the proper charset inside VICE, ie avoid Gtk3 using Unicode/UTF-8. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 - Next |
