Posts by Tobias

OK, well First of all switch the multimeter to the highest DC range it offers. If the probes are not fixed to the multimeter, connect the probes to ground (black one) and voltage input (red one) like in the picture. Stick the red one into the plug of the PSU, put the other (black) one on the outside of the plug. Make sure the two dont touch each other (that will make a short circuit and possibly destroy the PSU). Power on the PSU and read the measured voltage (should be around 12V). Now you can switch the range of the multimeter down to the smallest range that is still more than 12V to get a more accurate result. You can safely hold and touch the plug and probes in the process to make sure they dont make a short.

I'll make more pictures tomorrow that show what to measure in the C64R, need to remove a bit of the chaos around my desk first =)

That sounds doable then. Start with measuring the output voltage of your PSU when it is NOT connected to the C64R, it should be very close to 12V I can make a few pictures then that show a few points on the board and the expected voltage.

I understand that you want to fix it now, however "no green light, no response on the terminal.." means there isnt much we can do - the board isnt getting power (protection diode tripped). If you have a powersupply that works with other devices, and on the C64R it doesnt make the green LED light up, then you have already proved that

As said in PM, i dont have equipment for video conferencing, nor experience with any of the existing software/platforms. Jens is trying to set something up right now, but this will likely also still take a bit (and we still have to test if the bandwidth available to him is even good enough for this kind of thing).

Do you have a multimeter? I'd prefer to walk you through this using some pictures and written text - since then i can put it on the wiki for other people to see.

(just curious, where are you living anyway?)

indeed, that is likely the problem, an update will reset the settings (since those are on the same flash as the core)

My bet is really on a corrupted filesystem - since the amount of data the menu will write is fixed

9h is one release behind, see here

i havent heard about problems with this for a long time... are you sure the filesystem isnt damaged somehow? please try to reproduce it on a freshly formatted sd card.

"It's rather strange because this envelope is made of plastic!"

not strange at all... its an anti-static bag, which is conductive.

wow that is weird. good it finally worked

great, updated the wiki and list(s)

@robinsonb5: please let me know when you have set up a proper webpage, so i can update the wiki and the list in the forum

please lets not discuss copyright matters here. it will only attract the wrong people. i am with jens there... links to reputable sites like github are fine.

(i will delete parts of the discussion, no offence)

Na, it doesnt work even with the Stoat&Tim software. It must be somehow connected to the cartridge being in program mode or not, and the software expecting certain values in memory. When playing with this in VICE i could occasionally restart the software by loading a "crt file", but never reliably. gave up at some point

I have never managed to make this work also in VICE... somehow the Expert software doesnt like it - no idea why. Probably it also uses some memory locations in the regular C64 RAM, or something like that.

So, unfortunately, the answer is: it doesn't work

No, this can not be changed with a firmware update.

as a first step, find the pinout of the various ICs (CIA/CPU/VIC/SID) eg in c64-wiki ... and measure VCC, it should all be 5V. if that is OK, you may want to check the ICs in another C64 perhaps

My assumption would be its basically a HUB, so it should work. The complete lack of information on what it actually is seems a bit questionable though.

Please understand though that we can not guarantee anything for random products that we do not know

The address is correct (there is only one)-

Include a short note that explains the problem, and a reference to this thread. We can identify the board via the sticker on the board, indeed Including the power supply is a good idea, perhaps its just that that is faulty.

press a key on the terminal, then it will spit out some info. or just start the terminal before powering on the MK2

for a first check, i'd remove all the ICs, the board should power on (blinking LED) and you should see the remote control menu. if that works, try again with the ICs

Ok, i can reproduce it. I think this is related to the not-yet-perfekt emulation of VICII sprite collisions. Unfortunately there is nothing you can do about it, besides waiting until Peter fixed it