You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 5That is an excellent answer. And, it makes total sense. I guess Commodore wasn't as stupid as I thought they were. Too bad they didn't design a better PSU before they potted it. :-)cbmeeks– cbmeeks2017-08-07 17:22:07 +00:00Commented Aug 7, 2017 at 17:22
- 1The explanation I remember hearing at the time was it was done for safety reasons, maybe even specifically to get certification, and that the usual failure mode was that expansion and contraction would eventually crack the voltage regulator or break one of the connections.user722– user7222017-08-07 17:43:21 +00:00Commented Aug 7, 2017 at 17:43
- 1Even without overloading those C64 PSUs died regularly. I used to fix them by piggy-backing a new 7805 on and replacing the removed case bottom with a generous heatsink - did at least two dozen of them.Zac67– Zac672017-08-07 19:27:02 +00:00Commented Aug 7, 2017 at 19:27
- 4FYI, "CBM" is Commodore Business Machines.RBarryYoung– RBarryYoung2017-08-08 14:10:22 +00:00Commented Aug 8, 2017 at 14:10
- 2@RBarryYoung Thanks, but I know. If you are responding specifically to my internal quote note where I referred to "CP/M", I believe in that one instance Bil meant "CP/M cartridge" and not "CBM cartridge". The Z80 processor and other components within that cartridge would have added a noticeable load on the power supply, which in context is exactly what is being discussed at that point. FYI, Bil Herd is the lead engineer for the C= 128, and the one who decided to add the Z80 to its motherboard. So it makes sense that he would specifically reference the C64's CP/M cartridge.RichF– RichF2017-08-08 16:41:37 +00:00Commented Aug 8, 2017 at 16:41
| Show 7 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. ms-dos), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you