Preliminary VICE build for testing.

[orion70]

Warp mode seems to be very CPU-intensive: on my PC, some secs after Alt-W the motherboard fan speeds up to maximum. Maybe it's a RAM/CPU issue?

[Boray]

Warp mode seems to be very CPU-intensive: on my PC, some secs after Alt-W the motherboard fan speeds up to maximum. Maybe it's a RAM/CPU issue?

Isn't that what it's for? To run as fast as possible!

[orion70]

Yep, that's precisely why I wouldn't be surprised if the PC hangs with

all 4 drives emulated in true drive emulation and "Warp mode" enabled after a while (4/5 minutes) that I use another program

[Mike]

Here is the settings file:

Code: Select all

[...]

Would you be so kind to provide a download link instead of quoting this file in full?

Thanks,

Michael

[Boray]

Sure:
http://user.tninet.se/~jad615g/vice.ini

[nbla000]

Yep, that's precisely why I wouldn't be surprised if the PC hangs with

all 4 drives emulated in true drive emulation and "Warp mode" enabled after a while (4/5 minutes) that I use another program

Yes but I never noticed this problem with previous versions and if I try the same test with the latest official version I have no problems...

[Boray]

Yep, that's precisely why I wouldn't be surprised if the PC hangs with

all 4 drives emulated in true drive emulation and "Warp mode" enabled after a while (4/5 minutes) that I use another program

Yes but I never noticed this problem with previous versions and if I try the same test with the latest official version I have no problems...

There should not be any difference in the emulation depending on if you are using warp mode or not. It's just a speed difference.

[nbla000]

It's just a speed difference.

Yes but warp mode with 0% speed, 0 fps it's a little bit strange considering that I'm using other programs in my PC quite well in the same moment...

[rhurst]

... perhaps you pressed PAUSE, or it is time for a PC upgrade?

I've never seen it go 0% speed, 0 fps before... maybe you should make that into a poster, and sell it to collectors for $$ as a repro of a prototype.

Sorry, could not help myself.

[tlr]

New build: xvic-r22806-win32.zip

xvic changes:
- one more drive rotation clock overflow issue fixed. No more slow down.
- CRT emulation added for NTSC and others.
- various vdrive fixes.
- fixed build issue on big endian systems

Note: ColorGamma range changed. May need to set to 2200 manually.

[Mayhem]

Something's been broken in it... a lot of the PRG files autobooted through the Gamebase frontend now give errors when trying to load (complains about "file not found"). Version 2.2 works fine on that front, and this beta was also until this latest build.

[groepaz]

this is probably a result of the fixed (yes indeed) ascii to petscii conversion, which applies to (among other things) filenames ... if the filename contains characters that have no petscii equivalent, such as curly braces, then this conversion will fail.

to fix it, use proper filenames, or use the "copy to d64 before autostart" feature (inject to ram might or might not work aswell)

could you give an example or two? (ideally together with the log vice spits out)

[Mayhem]

It's definitely got nothing to do with the filenames; basically if I try running a PRG (whatever it is called) it fails, if it's a D64 it's fine. Maybe it's the way the GEMUS script has been attaching and running the game files in the past? But as I said, until this latest build of XVIC, everything was still fine.

Here's a log from this build of XVIC...

Extension memory enabled:
blk0
*** VICE Version 2.2.6 ***

Welcome to xvic, the free portable VIC20 Emulator.

Current VICE team members:
A. Boose, D. Lem, T. Biczo, A. Dehmel, T. Bretz, A. Matthies,
M. Pottendorfer, M. Brenner, S. Trikaliotis, M. van den Heuvel,
C. Vogelgsang, F. Gennari, H. Nuotio, D. Kahlin, A. Lankila.

This is free software with ABSOLUTELY NO WARRANTY.
See the "About VICE" command for more info.

Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\VIC20\kernal'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\VIC20\basic'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\VIC20\chargen'.
VIC20 kernal patched to 901486-07.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\PRINTER\mps803'.
Palette: Loading palette `C:\PROGRA~1\GameBase\WINVIC~1.3-B\PRINTER\mps803.vpl'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\PRINTER\nl10-cbm'.
Palette: Loading palette `C:\PROGRA~1\GameBase\WINVIC~1.3-B\PRINTER\mps803.vpl'.
NL10: Printer driver initialized.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\DRIVES\dos1541'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\DRIVES\d1541II'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\DRIVES\dos1570'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\DRIVES\dos1571'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\DRIVES\dos1581'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\DRIVES\dos2031'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\DRIVES\dos2040'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\DRIVES\dos3040'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\DRIVES\dos4040'.
Loading system file `C:\PROGRA~1\GameBase\WINVIC~1.3-B\DRIVES\dos1001'.
Drive: Finished loading ROM images.
Sound: Available sound devices: dx wmm dummy fs dump wav voc iff aiff soundmovie
Keyboard: Loading keymap `C:\PROGRA~1\GameBase\WINVIC~1.3-B\VIC20\win_pos.vkm'.
AUTOSTART: Autodetecting image type of `c:\gbgame\rezip\3DDOOL~1.PRG'.
Filesystem Image: Unknown disk image `c:\gbgame\rezip\3DDOOL~1.PRG'.
Tape: Error - Cannot open file `c:\gbgame\rezip\3DDOOL~1.PRG'
AUTOSTART: Loading PRG file `c:\gbgame\rezip\3DDOOL~1.PRG' with virtual FS on unit #8.
AUTOSTART: Resetting the machine to autostart '3ÄÄ

[groepaz]

It's definitely got nothing to do with the filenames

it does:

AUTOSTART: Loading PRG file `c:\gbgame\rezip\3DDOOL~1.PRG' with virtual FS on unit #8.
AUTOSTART: Resetting the machine to autostart '3ÄÄ

[Mayhem]

Someone has kindly pointed out that there is an option to send short filenames to the emulator in Gamebase, and it's on by default. Turning it off appears to solve this issue *phew*

Until I find some exceptions that is...!