What was the intention with the Commodore 128?Why does the Commodore C128 perform poorly when running...
Number of matrices with bounded products of rows and columns
My father gets angry everytime I pass Salam, that means I should stop saying Salam when he's around?
Reducing contention in thread-safe LruCache
Is there a way to make the "o" keypress of other-window <C-x><C-o> repeatable?
Are there categories whose internal hom is somewhat 'exotic'?
Have made several mistakes during the course of my PhD. Can't help but feel resentment. Can I get some advice about how to move forward?
Do living authors still get paid royalties for their old work?
Why don't politicians push for fossil fuel reduction by pointing out their scarcity?
What is bodily formation? Does it refer to the breath or the body?
Why is su world executable?
Are there any OR challenges that are similar to kaggle's competitions?
How could Tony Stark wield the Infinity Nano Gauntlet - at all?
When does The Truman Show take place?
Installing the original OS X version onto a Mac?
Vegetarian dishes on Russian trains (European part)
Quick destruction of a helium filled airship?
How to detect a failed AES256 decryption programmatically?
Designing a prison for a telekinetic race
My new Acer Aspire 7 doesn't have a Legacy Boot option, what can I do to get it?
Can the front glass be repaired of a broken lens?
Are there reliable, formulaic ways to form chords on the guitar?
Is "stainless" a bulk or a surface property of stainless steel?
Tabularx with hline and overrightarrow vertical spacing
Can I submit a paper computer science conference using an alias if using my real name can cause legal trouble in my original country
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
1
Not a real answer, but if you want to exhaustively research the Commodore 128, here are the players to google. Bil Herd: Designer & Hardware Lead, Dave Haynie: Intricate timing, PLA Emulator and DRAM, Frank Palaia: Z80 Integration and Ram Expansion, Fred Bowen: Programmer and Software Lead- Kernal & Monitor, Terry Ryan: Programmer- Basic V7 including structured language additions, Von Ertwine: Programmer- CPM - Also, this is a great article on hackaday from Bill Herd: hackaday.com/2013/12/09/…
– Geo...
2 days ago
@Geo... Thanks for that info ... I never expected so much to be available... The C128 was my first computer (and C128D second, because the first was 'lost during repair'). But to be honest, it was mostly in C64 mode.
– Michel Keijzers
2 days ago
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 Aug 15 at 16:01
Michel KeijzersMichel Keijzers
4372 silver badges14 bronze badges
4372 silver badges14 bronze badges
1
Not a real answer, but if you want to exhaustively research the Commodore 128, here are the players to google. Bil Herd: Designer & Hardware Lead, Dave Haynie: Intricate timing, PLA Emulator and DRAM, Frank Palaia: Z80 Integration and Ram Expansion, Fred Bowen: Programmer and Software Lead- Kernal & Monitor, Terry Ryan: Programmer- Basic V7 including structured language additions, Von Ertwine: Programmer- CPM - Also, this is a great article on hackaday from Bill Herd: hackaday.com/2013/12/09/…
– Geo...
2 days ago
@Geo... Thanks for that info ... I never expected so much to be available... The C128 was my first computer (and C128D second, because the first was 'lost during repair'). But to be honest, it was mostly in C64 mode.
– Michel Keijzers
2 days ago
add a comment |
1
Not a real answer, but if you want to exhaustively research the Commodore 128, here are the players to google. Bil Herd: Designer & Hardware Lead, Dave Haynie: Intricate timing, PLA Emulator and DRAM, Frank Palaia: Z80 Integration and Ram Expansion, Fred Bowen: Programmer and Software Lead- Kernal & Monitor, Terry Ryan: Programmer- Basic V7 including structured language additions, Von Ertwine: Programmer- CPM - Also, this is a great article on hackaday from Bill Herd: hackaday.com/2013/12/09/…
– Geo...
2 days ago
@Geo... Thanks for that info ... I never expected so much to be available... The C128 was my first computer (and C128D second, because the first was 'lost during repair'). But to be honest, it was mostly in C64 mode.
– Michel Keijzers
2 days ago
1
1
Not a real answer, but if you want to exhaustively research the Commodore 128, here are the players to google. Bil Herd: Designer & Hardware Lead, Dave Haynie: Intricate timing, PLA Emulator and DRAM, Frank Palaia: Z80 Integration and Ram Expansion, Fred Bowen: Programmer and Software Lead- Kernal & Monitor, Terry Ryan: Programmer- Basic V7 including structured language additions, Von Ertwine: Programmer- CPM - Also, this is a great article on hackaday from Bill Herd: hackaday.com/2013/12/09/…
– Geo...
2 days ago
Not a real answer, but if you want to exhaustively research the Commodore 128, here are the players to google. Bil Herd: Designer & Hardware Lead, Dave Haynie: Intricate timing, PLA Emulator and DRAM, Frank Palaia: Z80 Integration and Ram Expansion, Fred Bowen: Programmer and Software Lead- Kernal & Monitor, Terry Ryan: Programmer- Basic V7 including structured language additions, Von Ertwine: Programmer- CPM - Also, this is a great article on hackaday from Bill Herd: hackaday.com/2013/12/09/…
– Geo...
2 days ago
@Geo... Thanks for that info ... I never expected so much to be available... The C128 was my first computer (and C128D second, because the first was 'lost during repair'). But to be honest, it was mostly in C64 mode.
– Michel Keijzers
2 days ago
@Geo... Thanks for that info ... I never expected so much to be available... The C128 was my first computer (and C128D second, because the first was 'lost during repair'). But to be honest, it was mostly in C64 mode.
– Michel Keijzers
2 days ago
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
Aug 15 at 21:48
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 Bil 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.
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
Aug 15 at 21:48
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
Aug 15 at 21:48
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 Aug 15 at 16:57
RichFRichF
5,14116 silver badges38 bronze badges
5,14116 silver badges38 bronze badges
Upvoted and accepted; although the shortest answer, it answer my question best in the sense it was not the intention.
– Michel Keijzers
Aug 15 at 21:48
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
Aug 15 at 21:48
Upvoted and accepted; although the shortest answer, it answer my question best in the sense it was not the intention.
– Michel Keijzers
Aug 15 at 21:48
Upvoted and accepted; although the shortest answer, it answer my question best in the sense it was not the intention.
– Michel Keijzers
Aug 15 at 21:48
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 Bil 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.
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 Bil 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.
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 Bil 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 Bil 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 2 days ago
answered Aug 15 at 16:17
Brian HBrian H
22.4k2 gold badges83 silver badges190 bronze badges
22.4k2 gold badges83 silver badges190 bronze badges
add a comment |
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 Aug 15 at 17:17
answered Aug 15 at 16:15
Curt J. SampsonCurt J. Sampson
3,1729 silver badges37 bronze badges
3,1729 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 Aug 15 at 16:51
answered Aug 15 at 16:14
RaffzahnRaffzahn
67.1k6 gold badges166 silver badges278 bronze badges
67.1k6 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
1
Not a real answer, but if you want to exhaustively research the Commodore 128, here are the players to google. Bil Herd: Designer & Hardware Lead, Dave Haynie: Intricate timing, PLA Emulator and DRAM, Frank Palaia: Z80 Integration and Ram Expansion, Fred Bowen: Programmer and Software Lead- Kernal & Monitor, Terry Ryan: Programmer- Basic V7 including structured language additions, Von Ertwine: Programmer- CPM - Also, this is a great article on hackaday from Bill Herd: hackaday.com/2013/12/09/…
– Geo...
2 days ago
@Geo... Thanks for that info ... I never expected so much to be available... The C128 was my first computer (and C128D second, because the first was 'lost during repair'). But to be honest, it was mostly in C64 mode.
– Michel Keijzers
2 days ago