CCS64 Forum

The new version also froze after the 3rd start

Here's what I do and how I can reproduce the problem:

I unzip the CCS64 distrubtion file to a folder "CCS64 V3.9.2.zip" and start ccs64.exe close it after a few seconds and start it again and again. Usually latest within 5 trials CCS64 will start to respond slow or even crash.
With CCS64 v3.9.1 I ...

v3.9.2 causes issues for me while v3.9.1 works fine on a 64bit Windows 10 PC.

Already several times I noticed CCS64.exe crashing with following error:
"C64 Emulator for Win32/DirectX V9 has stopped working"

The about Windows of v3.9.2 lists following issues for those cases:
DirectInput Init FAILED ...

For me CCS64-2005.exe doesn't work fine but at least it won't crash like CCS64.exe
Not all keys pressed on the keyboard will be detected if you type too fast.

/Michael

I haven't started CCS64 for a few weeks but since today I don't manage to use it anymore.
After e.g. pressing ALT+O the display freezes and the emulator doesn't react anymore.
Still it's possible to access the top menu with the mouse and change the language for example.
Only way to end the program ...

The "replace files" method is what I'm using today but it really is not straight forward and simple as in VICE where you can specify the ROMs with a command line paramter.
Could that be a feature for the next CCS64 version as well? :wink:

Still I wonder what the "Rom Set" option in CCS64 is about ...

After starting CCS64 and pressing ALT+O there is an option listed for "Rom Set".
Is this option intended to toggle between the included ROMs and an alternative set?
If so, how can this function be utilized/activated?

Thanks in advance for any hint,
Michael

Is there a special reason for not including the latest kernal (rev.3) in the installation package of CCS64 v3.1?

Ciao,
Michael

RFBcsa wrote:I tried saving the entire ram (0000-FFFF).
It contains 65535 bytes (0-65534).
Where is the missing byte?

To get the missing byte use '10000' as end address!

Ciao,
Michael

I noticed a graphic glitch in a loading screen when loading the TAP image with CCS64 v3.1 but I cannot see this glitch when loading it with WinVICE v1.20.

Here's the CCS64 screenshot (take a look at the last letter of the word 'LIMITED'):
http://www.gb64.com/files/Espionage_CCS64 ...