What was the intention with the Commodore 128?Why does the Commodore C128 perform poorly when running CP/M?Can the two CPUs in a commodore 128 run at the same time?Can the two CPUs in a commodore 128 run at the same time?What was the end of line convention for text files on the 8-bit CommodoresWhy does the Commodore C128 perform poorly when running CP/M?What is the proper way to test the PSU output for a Commodore 128D?Getting started with CP/MGetting your Commodore VIC-20, 64 or 128 onlineCommodore VIC-20/64/128/16/Plus 4 floppy disk drive replacementPossible cause for C128 A/V output containing faintly coloured columns and failing shortly after?What was the most popular CP/M terminal type?How to add Final Cartridge III to VICE C64/128 Emulator
Good textbook for queueing theory and performance modeling
Why aren't rainbows blurred-out into nothing after they are produced?
Scam? Phone call from "Department of Social Security" asking me to call back
How would armour (and combat) change if the fighter didn't need to actually wear it?
What should I do if actually I found a serious flaw in someone's PhD thesis and an article derived from that PhD thesis?
Why do so many people play out of turn on the last lead?
Attacking the Hydra
Why won't the Republicans use a superdelegate system like the DNC in their nomination process?
Number in overlapping range
How can I find an old paper when the usual methods fail?
Heyawake: An Introductory Puzzle
How can I shoot a bow using Strength instead of Dexterity?
Some pads on a PCB are marked in clusters and I can't understand which one is which
If a person claims to know anything could it be disproven by saying 'prove that we are not in a simulation'?
Telephone number in spoken words
When did Bilbo and Frodo learn that Gandalf was a Maia?
Did Pope Urban II issue the papal bull "terra nullius" in 1095?
Is this bar slide trick shown on Cheers real or a visual effect?
Is it really Security Misconfiguration to show a version number?
What can I do to increase the amount of LEDs I can power with a pro micro?
How much can I judge a company based on a phone screening?
Does an Irish VISA WARNING count as "refused entry at the border of any country other than the UK?"
Escape Velocity - Won't the orbital path just become larger with higher initial velocity?
Solving pricing problem heuristically in column generation algorithm for VRP
What was the intention with the Commodore 128?
Why does the Commodore C128 perform poorly when running CP/M?Can the two CPUs in a commodore 128 run at the same time?Can the two CPUs in a commodore 128 run at the same time?What was the end of line convention for text files on the 8-bit CommodoresWhy does the Commodore C128 perform poorly when running CP/M?What is the proper way to test the PSU output for a Commodore 128D?Getting started with CP/MGetting your Commodore VIC-20, 64 or 128 onlineCommodore VIC-20/64/128/16/Plus 4 floppy disk drive replacementPossible cause for C128 A/V output containing faintly coloured columns and failing shortly after?What was the most popular CP/M terminal type?How to add Final Cartridge III to VICE C64/128 Emulator
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
The Commodore 128 had 2 CPUs, 2 video graphic chips, and 2 I/O systems/chips.
It had 3 modi: Commodore 64 mode, Commodore 128 mode and CP/M. The first shared one of each CPU/chip, the CP/M mode the other.
Was it the original intention to combine them? Or was it intended the way it was launched (two computers, or three in one case and that's it, simly said).
I wonder if they could get more out of all those peripherals.
cp-m commodore-128
add a comment |
The Commodore 128 had 2 CPUs, 2 video graphic chips, and 2 I/O systems/chips.
It had 3 modi: Commodore 64 mode, Commodore 128 mode and CP/M. The first shared one of each CPU/chip, the CP/M mode the other.
Was it the original intention to combine them? Or was it intended the way it was launched (two computers, or three in one case and that's it, simly said).
I wonder if they could get more out of all those peripherals.
cp-m commodore-128
add a comment |
The Commodore 128 had 2 CPUs, 2 video graphic chips, and 2 I/O systems/chips.
It had 3 modi: Commodore 64 mode, Commodore 128 mode and CP/M. The first shared one of each CPU/chip, the CP/M mode the other.
Was it the original intention to combine them? Or was it intended the way it was launched (two computers, or three in one case and that's it, simly said).
I wonder if they could get more out of all those peripherals.
cp-m commodore-128
The Commodore 128 had 2 CPUs, 2 video graphic chips, and 2 I/O systems/chips.
It had 3 modi: Commodore 64 mode, Commodore 128 mode and CP/M. The first shared one of each CPU/chip, the CP/M mode the other.
Was it the original intention to combine them? Or was it intended the way it was launched (two computers, or three in one case and that's it, simly said).
I wonder if they could get more out of all those peripherals.
cp-m commodore-128
cp-m commodore-128
asked 8 hours ago
Michel KeijzersMichel Keijzers
3671 silver badge10 bronze badges
3671 silver badge10 bronze badges
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
Was it the original intention to combine them?
No. The Z80 was not even part of the original design. It was added out of necessity to meet a "100% C64 compatible" claim of the original marketing. The C64 offered a CP/M expansion cartridge, which for some reason would not run correctly when inserted into early C128 prototypes. So about 2 months into a 5-month design cycle, the engineers decided to throw a Z80 CPU chip right onto the C128 motherboard.
Additional Information
Commodore History Part 5 - The C128 (YouTube video by The 8-Bit Guy)
Why does the Commodore C128 perform poorly when running CP/M? (detailed)
Upvoted and accepted; although the shortest answer, it answer my question best in the sense it was not the intention.
– Michel Keijzers
2 hours ago
add a comment |
The Commodore 128 was intended to be a fully-compatible, more professional, upgrade to the popular Commodore 64. The marketing called for addressing the most widely criticized shortcomings of the C64 that made it unsuitable in competing with more "professional"/business-oriented machines like the Apple //e and //c and the IBM clones.
C64 compatibility was essential. Additionally, the most requested features included:
80 column text mode for business/productivity applications. This necessitated two video chips since the VDC provided 80 column mode while the VIC-II provided C64 compatibility.
More addressable memory and CPU performance. This resulted in the C128 MMU and the two distinct operating modes for C64 and C128, which have different memory maps, different firmware, and allow different CPU clock speeds (1 MHz or 2 MHz).
Full C64 compatibility also implied working with the C64's Z80 add-on card to support CP/M. According to designer Bill Herd, it was not feasible to get this card working with the C128 because of the cards many timing hacks and power supply issues. That necessitated the second Z80 CPU in the C128 to support CP/M.
Improved floppy disk performance and capacity. This necessitated the additional "Burst" serial port mode and 1571 floppy drive upgrade, which also has a second mode to emulate the 1541.
You can see how the above features are all specifically called out in the advertising for the C128, pictured below.
So, the added hardware basically came from the designers meeting the marketing demands for the machine. It was also done in a rush, as was the case with most Commodore 8-bit machines. So they used the parts that mostly already existed, rather than taking more time to develop a "VIC-III" to support 80 columns and higher resolution, for example. The MMU was the only newly developed part specifically for the C128. The rest of the new stuff was firmware and peripherals.
Upvoted; nice history (and magazine article).
– Michel Keijzers
2 hours ago
add a comment |
The original intention was basically to have the functionality of two separate computers: a 6502-based system running Commodore's OS (with some features added beyond what the Commodore 64 offered, such as 80-column display and more memory) and a Z80-based system running CP/M. (These could not be used at the same time.) This is obviously cheaper than having two separate machines for the same functionality, since they can share a lot of hardware. It may or may not be more convenient depending on whether you actually wanted to use them at the same time, how much space you had on your desk, and so on.
From a distance it sounds like a good idea to try to use the CPUs and other dedicated hardware together, but in practice it's far more complex than is worthwhile. Consider that they shared the same memory subsystem and co-ordinating two CPUs sharing memory would have required both extra, fairly complex hardware, significant software changes (likely to both operating systems), and would probably have slowed memory access unless they added more or faster memory, either of which would have increased the cost. (If you want to get an idea of the complexities involved in even making both able to use the same memory and video display, have a look at the answers to this question.)
And yes, there was always at least one more CPU, another 6510 in the disk drive. (That was true from the PET systems onward.) That, too, is dedicated to its task and not shared with other parts of the system.
add a comment |
Was it the original intention to combine them? Or was it intended the way it was launched (two computers, or three in one case and that's it, simly said).
Basically yes. It was a sounding approach to get more revenue from an, at that time already ageing, 8 bit concept without investing much, while running a small risk of failure, as there was no risk of alienating existing customers
- New Customers could see it as a better 64 they always wanted to buy.
- Existing C64 customers could see an upgrade path without loosing all investment (read games) thy had spend.
Maybe most important
- Both got offered a more semi professional, output related usage.
Especially the later was important to bind customers growing out from playing with a (classic) home computer into every day productivity related computer use.
Despite all the work dedicated users have done, the C64 wasn't a real replacement on for professional PET series. Mostly due the lack of a good keyboard and an 80 character display. The 128 did offer both, and with CP/M as OS it could tap a great amount of existing productivity software - from word processing to databases and much more. While CP/M had as well past it's peak, it was still considered a good choice. Neither the PC nor DOS was as all mighty as it became a few years later.
I wonder if they could get more out of all those peripherals.
Not really as the 128 was for most part just a combination of existing enhancements for the C64 - adjusted for better integration, not anything really new.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "648"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fretrocomputing.stackexchange.com%2fquestions%2f12056%2fwhat-was-the-intention-with-the-commodore-128%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Was it the original intention to combine them?
No. The Z80 was not even part of the original design. It was added out of necessity to meet a "100% C64 compatible" claim of the original marketing. The C64 offered a CP/M expansion cartridge, which for some reason would not run correctly when inserted into early C128 prototypes. So about 2 months into a 5-month design cycle, the engineers decided to throw a Z80 CPU chip right onto the C128 motherboard.
Additional Information
Commodore History Part 5 - The C128 (YouTube video by The 8-Bit Guy)
Why does the Commodore C128 perform poorly when running CP/M? (detailed)
Upvoted and accepted; although the shortest answer, it answer my question best in the sense it was not the intention.
– Michel Keijzers
2 hours ago
add a comment |
Was it the original intention to combine them?
No. The Z80 was not even part of the original design. It was added out of necessity to meet a "100% C64 compatible" claim of the original marketing. The C64 offered a CP/M expansion cartridge, which for some reason would not run correctly when inserted into early C128 prototypes. So about 2 months into a 5-month design cycle, the engineers decided to throw a Z80 CPU chip right onto the C128 motherboard.
Additional Information
Commodore History Part 5 - The C128 (YouTube video by The 8-Bit Guy)
Why does the Commodore C128 perform poorly when running CP/M? (detailed)
Upvoted and accepted; although the shortest answer, it answer my question best in the sense it was not the intention.
– Michel Keijzers
2 hours ago
add a comment |
Was it the original intention to combine them?
No. The Z80 was not even part of the original design. It was added out of necessity to meet a "100% C64 compatible" claim of the original marketing. The C64 offered a CP/M expansion cartridge, which for some reason would not run correctly when inserted into early C128 prototypes. So about 2 months into a 5-month design cycle, the engineers decided to throw a Z80 CPU chip right onto the C128 motherboard.
Additional Information
Commodore History Part 5 - The C128 (YouTube video by The 8-Bit Guy)
Why does the Commodore C128 perform poorly when running CP/M? (detailed)
Was it the original intention to combine them?
No. The Z80 was not even part of the original design. It was added out of necessity to meet a "100% C64 compatible" claim of the original marketing. The C64 offered a CP/M expansion cartridge, which for some reason would not run correctly when inserted into early C128 prototypes. So about 2 months into a 5-month design cycle, the engineers decided to throw a Z80 CPU chip right onto the C128 motherboard.
Additional Information
Commodore History Part 5 - The C128 (YouTube video by The 8-Bit Guy)
Why does the Commodore C128 perform poorly when running CP/M? (detailed)
answered 7 hours ago
RichFRichF
4,92115 silver badges37 bronze badges
4,92115 silver badges37 bronze badges
Upvoted and accepted; although the shortest answer, it answer my question best in the sense it was not the intention.
– Michel Keijzers
2 hours ago
add a comment |
Upvoted and accepted; although the shortest answer, it answer my question best in the sense it was not the intention.
– Michel Keijzers
2 hours ago
Upvoted and accepted; although the shortest answer, it answer my question best in the sense it was not the intention.
– Michel Keijzers
2 hours ago
Upvoted and accepted; although the shortest answer, it answer my question best in the sense it was not the intention.
– Michel Keijzers
2 hours ago
add a comment |
The Commodore 128 was intended to be a fully-compatible, more professional, upgrade to the popular Commodore 64. The marketing called for addressing the most widely criticized shortcomings of the C64 that made it unsuitable in competing with more "professional"/business-oriented machines like the Apple //e and //c and the IBM clones.
C64 compatibility was essential. Additionally, the most requested features included:
80 column text mode for business/productivity applications. This necessitated two video chips since the VDC provided 80 column mode while the VIC-II provided C64 compatibility.
More addressable memory and CPU performance. This resulted in the C128 MMU and the two distinct operating modes for C64 and C128, which have different memory maps, different firmware, and allow different CPU clock speeds (1 MHz or 2 MHz).
Full C64 compatibility also implied working with the C64's Z80 add-on card to support CP/M. According to designer Bill Herd, it was not feasible to get this card working with the C128 because of the cards many timing hacks and power supply issues. That necessitated the second Z80 CPU in the C128 to support CP/M.
Improved floppy disk performance and capacity. This necessitated the additional "Burst" serial port mode and 1571 floppy drive upgrade, which also has a second mode to emulate the 1541.
You can see how the above features are all specifically called out in the advertising for the C128, pictured below.
So, the added hardware basically came from the designers meeting the marketing demands for the machine. It was also done in a rush, as was the case with most Commodore 8-bit machines. So they used the parts that mostly already existed, rather than taking more time to develop a "VIC-III" to support 80 columns and higher resolution, for example. The MMU was the only newly developed part specifically for the C128. The rest of the new stuff was firmware and peripherals.
Upvoted; nice history (and magazine article).
– Michel Keijzers
2 hours ago
add a comment |
The Commodore 128 was intended to be a fully-compatible, more professional, upgrade to the popular Commodore 64. The marketing called for addressing the most widely criticized shortcomings of the C64 that made it unsuitable in competing with more "professional"/business-oriented machines like the Apple //e and //c and the IBM clones.
C64 compatibility was essential. Additionally, the most requested features included:
80 column text mode for business/productivity applications. This necessitated two video chips since the VDC provided 80 column mode while the VIC-II provided C64 compatibility.
More addressable memory and CPU performance. This resulted in the C128 MMU and the two distinct operating modes for C64 and C128, which have different memory maps, different firmware, and allow different CPU clock speeds (1 MHz or 2 MHz).
Full C64 compatibility also implied working with the C64's Z80 add-on card to support CP/M. According to designer Bill Herd, it was not feasible to get this card working with the C128 because of the cards many timing hacks and power supply issues. That necessitated the second Z80 CPU in the C128 to support CP/M.
Improved floppy disk performance and capacity. This necessitated the additional "Burst" serial port mode and 1571 floppy drive upgrade, which also has a second mode to emulate the 1541.
You can see how the above features are all specifically called out in the advertising for the C128, pictured below.
So, the added hardware basically came from the designers meeting the marketing demands for the machine. It was also done in a rush, as was the case with most Commodore 8-bit machines. So they used the parts that mostly already existed, rather than taking more time to develop a "VIC-III" to support 80 columns and higher resolution, for example. The MMU was the only newly developed part specifically for the C128. The rest of the new stuff was firmware and peripherals.
Upvoted; nice history (and magazine article).
– Michel Keijzers
2 hours ago
add a comment |
The Commodore 128 was intended to be a fully-compatible, more professional, upgrade to the popular Commodore 64. The marketing called for addressing the most widely criticized shortcomings of the C64 that made it unsuitable in competing with more "professional"/business-oriented machines like the Apple //e and //c and the IBM clones.
C64 compatibility was essential. Additionally, the most requested features included:
80 column text mode for business/productivity applications. This necessitated two video chips since the VDC provided 80 column mode while the VIC-II provided C64 compatibility.
More addressable memory and CPU performance. This resulted in the C128 MMU and the two distinct operating modes for C64 and C128, which have different memory maps, different firmware, and allow different CPU clock speeds (1 MHz or 2 MHz).
Full C64 compatibility also implied working with the C64's Z80 add-on card to support CP/M. According to designer Bill Herd, it was not feasible to get this card working with the C128 because of the cards many timing hacks and power supply issues. That necessitated the second Z80 CPU in the C128 to support CP/M.
Improved floppy disk performance and capacity. This necessitated the additional "Burst" serial port mode and 1571 floppy drive upgrade, which also has a second mode to emulate the 1541.
You can see how the above features are all specifically called out in the advertising for the C128, pictured below.
So, the added hardware basically came from the designers meeting the marketing demands for the machine. It was also done in a rush, as was the case with most Commodore 8-bit machines. So they used the parts that mostly already existed, rather than taking more time to develop a "VIC-III" to support 80 columns and higher resolution, for example. The MMU was the only newly developed part specifically for the C128. The rest of the new stuff was firmware and peripherals.
The Commodore 128 was intended to be a fully-compatible, more professional, upgrade to the popular Commodore 64. The marketing called for addressing the most widely criticized shortcomings of the C64 that made it unsuitable in competing with more "professional"/business-oriented machines like the Apple //e and //c and the IBM clones.
C64 compatibility was essential. Additionally, the most requested features included:
80 column text mode for business/productivity applications. This necessitated two video chips since the VDC provided 80 column mode while the VIC-II provided C64 compatibility.
More addressable memory and CPU performance. This resulted in the C128 MMU and the two distinct operating modes for C64 and C128, which have different memory maps, different firmware, and allow different CPU clock speeds (1 MHz or 2 MHz).
Full C64 compatibility also implied working with the C64's Z80 add-on card to support CP/M. According to designer Bill Herd, it was not feasible to get this card working with the C128 because of the cards many timing hacks and power supply issues. That necessitated the second Z80 CPU in the C128 to support CP/M.
Improved floppy disk performance and capacity. This necessitated the additional "Burst" serial port mode and 1571 floppy drive upgrade, which also has a second mode to emulate the 1541.
You can see how the above features are all specifically called out in the advertising for the C128, pictured below.
So, the added hardware basically came from the designers meeting the marketing demands for the machine. It was also done in a rush, as was the case with most Commodore 8-bit machines. So they used the parts that mostly already existed, rather than taking more time to develop a "VIC-III" to support 80 columns and higher resolution, for example. The MMU was the only newly developed part specifically for the C128. The rest of the new stuff was firmware and peripherals.
edited 5 hours ago
answered 8 hours ago
Brian HBrian H
22.2k2 gold badges83 silver badges189 bronze badges
22.2k2 gold badges83 silver badges189 bronze badges
Upvoted; nice history (and magazine article).
– Michel Keijzers
2 hours ago
add a comment |
Upvoted; nice history (and magazine article).
– Michel Keijzers
2 hours ago
Upvoted; nice history (and magazine article).
– Michel Keijzers
2 hours ago
Upvoted; nice history (and magazine article).
– Michel Keijzers
2 hours ago
add a comment |
The original intention was basically to have the functionality of two separate computers: a 6502-based system running Commodore's OS (with some features added beyond what the Commodore 64 offered, such as 80-column display and more memory) and a Z80-based system running CP/M. (These could not be used at the same time.) This is obviously cheaper than having two separate machines for the same functionality, since they can share a lot of hardware. It may or may not be more convenient depending on whether you actually wanted to use them at the same time, how much space you had on your desk, and so on.
From a distance it sounds like a good idea to try to use the CPUs and other dedicated hardware together, but in practice it's far more complex than is worthwhile. Consider that they shared the same memory subsystem and co-ordinating two CPUs sharing memory would have required both extra, fairly complex hardware, significant software changes (likely to both operating systems), and would probably have slowed memory access unless they added more or faster memory, either of which would have increased the cost. (If you want to get an idea of the complexities involved in even making both able to use the same memory and video display, have a look at the answers to this question.)
And yes, there was always at least one more CPU, another 6510 in the disk drive. (That was true from the PET systems onward.) That, too, is dedicated to its task and not shared with other parts of the system.
add a comment |
The original intention was basically to have the functionality of two separate computers: a 6502-based system running Commodore's OS (with some features added beyond what the Commodore 64 offered, such as 80-column display and more memory) and a Z80-based system running CP/M. (These could not be used at the same time.) This is obviously cheaper than having two separate machines for the same functionality, since they can share a lot of hardware. It may or may not be more convenient depending on whether you actually wanted to use them at the same time, how much space you had on your desk, and so on.
From a distance it sounds like a good idea to try to use the CPUs and other dedicated hardware together, but in practice it's far more complex than is worthwhile. Consider that they shared the same memory subsystem and co-ordinating two CPUs sharing memory would have required both extra, fairly complex hardware, significant software changes (likely to both operating systems), and would probably have slowed memory access unless they added more or faster memory, either of which would have increased the cost. (If you want to get an idea of the complexities involved in even making both able to use the same memory and video display, have a look at the answers to this question.)
And yes, there was always at least one more CPU, another 6510 in the disk drive. (That was true from the PET systems onward.) That, too, is dedicated to its task and not shared with other parts of the system.
add a comment |
The original intention was basically to have the functionality of two separate computers: a 6502-based system running Commodore's OS (with some features added beyond what the Commodore 64 offered, such as 80-column display and more memory) and a Z80-based system running CP/M. (These could not be used at the same time.) This is obviously cheaper than having two separate machines for the same functionality, since they can share a lot of hardware. It may or may not be more convenient depending on whether you actually wanted to use them at the same time, how much space you had on your desk, and so on.
From a distance it sounds like a good idea to try to use the CPUs and other dedicated hardware together, but in practice it's far more complex than is worthwhile. Consider that they shared the same memory subsystem and co-ordinating two CPUs sharing memory would have required both extra, fairly complex hardware, significant software changes (likely to both operating systems), and would probably have slowed memory access unless they added more or faster memory, either of which would have increased the cost. (If you want to get an idea of the complexities involved in even making both able to use the same memory and video display, have a look at the answers to this question.)
And yes, there was always at least one more CPU, another 6510 in the disk drive. (That was true from the PET systems onward.) That, too, is dedicated to its task and not shared with other parts of the system.
The original intention was basically to have the functionality of two separate computers: a 6502-based system running Commodore's OS (with some features added beyond what the Commodore 64 offered, such as 80-column display and more memory) and a Z80-based system running CP/M. (These could not be used at the same time.) This is obviously cheaper than having two separate machines for the same functionality, since they can share a lot of hardware. It may or may not be more convenient depending on whether you actually wanted to use them at the same time, how much space you had on your desk, and so on.
From a distance it sounds like a good idea to try to use the CPUs and other dedicated hardware together, but in practice it's far more complex than is worthwhile. Consider that they shared the same memory subsystem and co-ordinating two CPUs sharing memory would have required both extra, fairly complex hardware, significant software changes (likely to both operating systems), and would probably have slowed memory access unless they added more or faster memory, either of which would have increased the cost. (If you want to get an idea of the complexities involved in even making both able to use the same memory and video display, have a look at the answers to this question.)
And yes, there was always at least one more CPU, another 6510 in the disk drive. (That was true from the PET systems onward.) That, too, is dedicated to its task and not shared with other parts of the system.
edited 7 hours ago
answered 8 hours ago
Curt J. SampsonCurt J. Sampson
2,7986 silver badges37 bronze badges
2,7986 silver badges37 bronze badges
add a comment |
add a comment |
Was it the original intention to combine them? Or was it intended the way it was launched (two computers, or three in one case and that's it, simly said).
Basically yes. It was a sounding approach to get more revenue from an, at that time already ageing, 8 bit concept without investing much, while running a small risk of failure, as there was no risk of alienating existing customers
- New Customers could see it as a better 64 they always wanted to buy.
- Existing C64 customers could see an upgrade path without loosing all investment (read games) thy had spend.
Maybe most important
- Both got offered a more semi professional, output related usage.
Especially the later was important to bind customers growing out from playing with a (classic) home computer into every day productivity related computer use.
Despite all the work dedicated users have done, the C64 wasn't a real replacement on for professional PET series. Mostly due the lack of a good keyboard and an 80 character display. The 128 did offer both, and with CP/M as OS it could tap a great amount of existing productivity software - from word processing to databases and much more. While CP/M had as well past it's peak, it was still considered a good choice. Neither the PC nor DOS was as all mighty as it became a few years later.
I wonder if they could get more out of all those peripherals.
Not really as the 128 was for most part just a combination of existing enhancements for the C64 - adjusted for better integration, not anything really new.
add a comment |
Was it the original intention to combine them? Or was it intended the way it was launched (two computers, or three in one case and that's it, simly said).
Basically yes. It was a sounding approach to get more revenue from an, at that time already ageing, 8 bit concept without investing much, while running a small risk of failure, as there was no risk of alienating existing customers
- New Customers could see it as a better 64 they always wanted to buy.
- Existing C64 customers could see an upgrade path without loosing all investment (read games) thy had spend.
Maybe most important
- Both got offered a more semi professional, output related usage.
Especially the later was important to bind customers growing out from playing with a (classic) home computer into every day productivity related computer use.
Despite all the work dedicated users have done, the C64 wasn't a real replacement on for professional PET series. Mostly due the lack of a good keyboard and an 80 character display. The 128 did offer both, and with CP/M as OS it could tap a great amount of existing productivity software - from word processing to databases and much more. While CP/M had as well past it's peak, it was still considered a good choice. Neither the PC nor DOS was as all mighty as it became a few years later.
I wonder if they could get more out of all those peripherals.
Not really as the 128 was for most part just a combination of existing enhancements for the C64 - adjusted for better integration, not anything really new.
add a comment |
Was it the original intention to combine them? Or was it intended the way it was launched (two computers, or three in one case and that's it, simly said).
Basically yes. It was a sounding approach to get more revenue from an, at that time already ageing, 8 bit concept without investing much, while running a small risk of failure, as there was no risk of alienating existing customers
- New Customers could see it as a better 64 they always wanted to buy.
- Existing C64 customers could see an upgrade path without loosing all investment (read games) thy had spend.
Maybe most important
- Both got offered a more semi professional, output related usage.
Especially the later was important to bind customers growing out from playing with a (classic) home computer into every day productivity related computer use.
Despite all the work dedicated users have done, the C64 wasn't a real replacement on for professional PET series. Mostly due the lack of a good keyboard and an 80 character display. The 128 did offer both, and with CP/M as OS it could tap a great amount of existing productivity software - from word processing to databases and much more. While CP/M had as well past it's peak, it was still considered a good choice. Neither the PC nor DOS was as all mighty as it became a few years later.
I wonder if they could get more out of all those peripherals.
Not really as the 128 was for most part just a combination of existing enhancements for the C64 - adjusted for better integration, not anything really new.
Was it the original intention to combine them? Or was it intended the way it was launched (two computers, or three in one case and that's it, simly said).
Basically yes. It was a sounding approach to get more revenue from an, at that time already ageing, 8 bit concept without investing much, while running a small risk of failure, as there was no risk of alienating existing customers
- New Customers could see it as a better 64 they always wanted to buy.
- Existing C64 customers could see an upgrade path without loosing all investment (read games) thy had spend.
Maybe most important
- Both got offered a more semi professional, output related usage.
Especially the later was important to bind customers growing out from playing with a (classic) home computer into every day productivity related computer use.
Despite all the work dedicated users have done, the C64 wasn't a real replacement on for professional PET series. Mostly due the lack of a good keyboard and an 80 character display. The 128 did offer both, and with CP/M as OS it could tap a great amount of existing productivity software - from word processing to databases and much more. While CP/M had as well past it's peak, it was still considered a good choice. Neither the PC nor DOS was as all mighty as it became a few years later.
I wonder if they could get more out of all those peripherals.
Not really as the 128 was for most part just a combination of existing enhancements for the C64 - adjusted for better integration, not anything really new.
edited 7 hours ago
answered 8 hours ago
RaffzahnRaffzahn
66.9k6 gold badges166 silver badges278 bronze badges
66.9k6 gold badges166 silver badges278 bronze badges
add a comment |
add a comment |
Thanks for contributing an answer to Retrocomputing Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fretrocomputing.stackexchange.com%2fquestions%2f12056%2fwhat-was-the-intention-with-the-commodore-128%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown