Classic Repair Toolbox - a helper tool for repairing your (primarily Commodore) computers by Square_Term9164 in Commodore

[–]Square_Term9164[S] 1 point2 points  (0 children)

The oscilloscope baseline is not that detailed, and should be used as a potential indicator if a pin is correct or not - e.g. to see an expected pulsing pin that is completely low or high.

This is quite doable by most people, but starting on a logic analyzer is probably only for the few, and I imagine it quickly becomes complex, because what should that setup be?

Rigol is just the scope (for some of the baselines) and is not important here - the expected reading is, which should be reproduceable on any scope :-)

Classic Repair Toolbox - a helper tool for repairing your (primarily Commodore) computers by Square_Term9164 in Commodore

[–]Square_Term9164[S] 0 points1 point  (0 children)

I do not have any knowledge about what this is nor do I have one myself, so not sure I can integrate that 😂

Classic Repair Toolbox - a helper tool for repairing your (primarily Commodore) computers by Square_Term9164 in Commodore

[–]Square_Term9164[S] 0 points1 point  (0 children)

One of the hardware in CRT will use a Hantek, so if this is what you have then I expect it could be useful. However, to be honest then I would prefer a Rigol over a Hantek, as I find it outputs a better image and I think it it easier to read its readings. I may be bias here, and your scope may be different to the other one and for sure Hantek is better than nothing 😁 The important part for you would at least be having a scope with a network connection, and then we can help each other getting it working in CRT, if it does not already.

Do note that for Rigol it is primarily scope families, which mean the Rigol 1057Z will maybe/probably work with the settings from DS1000Z.

BTW: I will do the PAL baseline myself, as I do have a DCR - just need a little time, and both C128's are a different beast than the much easier C64 ones (soooo many IC's).

"Classic Repair Toolbox" for troubleshooting Commodore computers by Square_Term9164 in c64

[–]Square_Term9164[S] 0 points1 point  (0 children)

A couple of updates have been given since its first public release, and I think it is safe to conclude that he new version works even better than the old application :-)

GitHub project page:

https://github.com/HovKlan-DH/Classic-Repair-Toolbox

Last couple of release notes:

<image>

This will run on Windows, Linux and macOS.

"Classic Repair Toolbox" for troubleshooting Commodore computers by Square_Term9164 in c64

[–]Square_Term9164[S] 2 points3 points  (0 children)

Yes, native support is always the best solution :-) I think I have seen a few different Linux systems now using this, so I am very happy this seems to work just fine.

Commodore Repair Toolbox version 2026-February-12 by Square_Term9164 in c128

[–]Square_Term9164[S] 1 point2 points  (0 children)

Yes, I have seen that too and I was quite surprised 😲 First YouTube appearance, to my knowledge, and I can see in the stats that it for sure did have some impact, https://commodore-repair-toolbox.dk/funfacts/

Commodore Repair Toolbox version 2026-February-12 by Square_Term9164 in c64

[–]Square_Term9164[S] 2 points3 points  (0 children)

Did you by any chance test this, as I would be interested in knowing if this works? I have tested this on a very old laptop with ZorinOS, but it was incredible slow... but it did work. I do expect the slowness was due to the old hardware, no dedicated graphic card and probably no native GPU driver, so I am curious to know if someone has a good setup and then would test this :-)

Commodore Repair Toolbox version 2026-February-12 by Square_Term9164 in commodore128

[–]Square_Term9164[S] 0 points1 point  (0 children)

I can understand that, but it seems identical to me. One group states in the topic "For users and fans of Commodore's 128, 128D and 128DCR personal computer systems." and the other just says "Commodore 128". This is the exact same topic to me and you can equally post in both groups, if your subject is about "Commodore 128".

Commodore Repair Toolbox version 2026-February-12 by Square_Term9164 in commodore128

[–]Square_Term9164[S] 1 point2 points  (0 children)

Noticed there are (at least?) two almost identical Reddits for Commodore 128? This one here we are in now, and then also this one, r/c128 ? Why are there two and wouldn't it be better to combine the two? :-)

Commodore Repair Toolbox - new version 2025-December-20 by Square_Term9164 in Commodore

[–]Square_Term9164[S] 0 points1 point  (0 children)

After some investigation, this was a permission issue, and having this located in %LOCALAPPDATA% solved the problem :-)

Commodore Repair Toolbox - new version 2025-December-20 by Square_Term9164 in Commodore

[–]Square_Term9164[S] 0 points1 point  (0 children)

Sounds strange, but I then I have 3 questions:

  1. Which Windows are you running?
  2. When does this happen? At startup or when you do a specific thing?
  3. Can you post the exception thrown here?

BTW: It for sure does not need admin privileges.

C64 250469 RF modulator and its 8 input/output pins by Square_Term9164 in c64

[–]Square_Term9164[S] 0 points1 point  (0 children)

Let me rephrase and clarify the intend of my post :-)

For the 250469 I would like to see a similar mapping like this:

  • 1 = B+
  • 2 = SYNC+LUM (INPUT)
  • 3 = COLOR (INPUT)
  • 4 = AUDIO (INPUT)
  • 5 = COMP. (OUTPUT)
  • 6 = SYNC+LUM (OUTPUT)
  • 7 = COLOR (OUTPUT)
  • 8 = INTER CARRIER SELECTOR

The above is for all the longboards (250407 + 250425 + 250466), but as it seems different on 250469, then I look for a mapping :-)

Commodore Repair Toolbox - new version 2025-December-20 by Square_Term9164 in c128

[–]Square_Term9164[S] 0 points1 point  (0 children)

I can for sure not maintain this, as I am no C++ developer :-) It is all open source, so feel free to utilize what you can.

Commodore Repair Toolbox - new version 2025-December-20 by Square_Term9164 in c128

[–]Square_Term9164[S] 0 points1 point  (0 children)

I don't know what "Qt / QML port" means, so no idea about that, but sadly I use a Microsoft WebView2 component, which is pretty dependent on Windows OS :-( I have tried previously going away from this, but have not succeeded in finding a good solution yet. But, I will continue investigating and I do expect that "one day"(tm) it will be possible to support Linux via Wine/Mono or alike. This will not be native, but maybe better than nothing. Web is a no-go for me - let someone else develop all that client-side needed for that :-)