C64 OS is a new operating system for your Commodore 64 that gives it a whole new set of sophisticated tools with a powerful and unified user interface.
This channel features many short raw videos, grouped into playlists by topic, that show the development progress and status of C64 OS. Many of these videos go back a few years to when I started the project. Originally many of these were tweeted, but now they're being uploaded to RU-vid so they are more easily discoverable.
For all more information about C64 OS, visit the official website: www.c64os.com. There you will also find my blog with over 100 posts, the Commodore 8-bit buyer's guide, and other C64 projects and information.
I gave two full presentations to Commodore Users Europe, those videos are on RU-vid and can be found here:
Presentation #1: From June 2021: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-8nUosmUcckU.html
Presentation #2: From June 2022: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-PFcJOl2dgcU.html
Please review the FAQ in the appendix of the C64 OS User’s Guide (online version) for hardware compatibility details. www.c64os.com/c64os/usersguide/appendices#faq
I don't believe I claimed otherwise. The video shows exactly what is in the description. Matrix images in CGFX format require an REU and the Image Viewer Application in C64 OS, version 1.04 or higher.
There isn’t yet a text editor proper for C64 OS. There are non-editing text views, like the one showing the Wikipedia content. And there is a single line input field and a multi-line input field. The text input for moving the cursor and making text selections and copying and pasting to from the clipboard are more influenced by the macOS AppKit, with some C64-specific conventions. There is very limited memory, so, some keyboard commands that I would have liked to include had to be left out. In a a proper text editor though, good cursor navigation from the keyboard is a priority.
C64 OS has been able to run on a U64 and U64 Elite and a MiSTer since day one. These are almost (if not exactly) 100% compatible Commodore 64 implementations. However, like any other C64, you still need to connect to them a compatible mass-storage device. You can read about the minimum requirements here: www.c64os.com/c64os/gettingstarted/ But, yes, I've done all my demos at World of Commodore using an Ultimate64. Very convenient, because its HDMI port connects directly to the projector. And there are numerous C64 OS users who are using a MiSTer.
Will it ever come for systems with just a 1541? I'm sure that the majority of C64 users don't have an SD2IEC, but either an original 1541/71/81, a Pi1541 or the 1541 Ultimate for emulating the drive.
Nope! It will most certainly never, ever run from a 1541, 1571, or 1581 disk drive. C64 OS is an operating system. It’s over a megabyte minimum install, and absolutely requires subdirectory support. It’s also well over 1000 files organized in a tree of around 50 subdirectories. So, time to move up in the world and buy a “hard drive” for your C64. If you actually care about this stuff. Otherwise, just play games and be happy. 😉
@@c64os "If you actually care about this stuff." No, I don't care about C64 OS if it cannot be run from a 1541/71/81. I have an Ultimate 64, and, in fact, I program for the C64, don't play games much.
Sorry if my response was flippant. But I’ve had to answer the same question so many times. And then I often get back that I’m an idiot or my work sucks because I haven’t been able to make it work from a floppy disk. Here’s the FAQ. c64os.com/c64os/usersguide/appendices#faq And if it’s not for you, then, it’s not for you. But, no, it will never run from a 1541/1571/1581.
i have almost finished my dream c64 setup. 3 drives(2 real and one pi1541), c2n, printer, fm radio, wifi cartridge, kff cart. just missing the REU, its more expensive than the whole setup i have so far :D i would love to try this out if i ever get an REU :D thanks for the video, its some great content!
Just an FYI, C64 OS does not require an REU. It can make use of one for fast app switching and for faster more efficient screen redraws, but it's not a requirement. The sole requirement (besides the minimum input of a joystick) is a storage device with C64-native support for subdirectories. You can read more about the minimum requirements here: www.c64os.com/c64os/gettingstarted/
Yes! It certainly is cool! :) I need to digg into C64OS docs as I would love it working with RR-Net MK3 on Chameleon plugged to my C64. Maybe I could write a driver for that
The only problem with RR-Net, ETH64, and other ethernet solutions, is that they don't handle the TCP/IP. The C64 OS networking is a layer that runs on top of various networking hardware, but the minimum requirement from the networking hardware is that it must provide a single streaming TCP/IP socket.
Sounds like that would be fun. But it's not "next" on the list. :) Only reason is because there are still so many other things we need. Like chatting and messaging with our fellow humans, for a start.
Nice video. Enjoyed watching it. Glad you like my case design. Probably my favorite design I've ever done. The metal threaded things in the plastic are called "heatsets" and they're made of brass. The front panel of the case slots in exactly the same way as the back does. The reason it's a little tighter is because there's a bit more material that goes into the slot, plus I made the tolerance a little tighter on the front panel because I never expected it to be removed. Whereas the back panel I did expect it to be removed and replaced from time to time. The drive mechanism, as actually new old stock. Each FD-4000 that I sell gets a brand new, never before used drive. In fact, all of the components on the PCB are either new or NOS parts. The wires that power the drive and lead to the switch are silicon sheathed wire with very fine strands. I chose this wire because I expect users to go into the drive from time to time, and didn't want the wiring to ever break. This type of wire is very resistant to breaking and wear. When I created this drive, I created it to last. I hope you have many many years of enjoyment! COREi64
Thank you for those clarifications. And thanks also for the amazing work you're doing, I hope every Commodore 8-bit fan on Earth takes advantage of what you're building over there at COREi64!
Today a REU (RAM Expansion Unit) is very affordable - or at least a compatible rebuild. Back in the day, those were really expansive. But back then, people would have used GEOS - which even ran without a REU to some extend. GEOS is a simple "Windows-like" OS, which featured a powerful word editor among other things. An essential difference is that C64OS uses Textmode, instead of Graphics-Mode. I guess, companies like Commodore struggled to market their actually not that bad solutions. Partly probably because people considered Commodores to be more of a toy.
Congrats on taking the FD-4000. The missing square chip is the one used in the FD-2000 instead of the larger one used in the FD-4000. In the latest revision the RTC is included with the motherboard. I guess using this drive for demos would be more useful than the 1541... 4 MHz ... 😁👍🏻
All correct on the missing square chip. The other major difference between the FD-2000 and the FD-4000, as you suggested, is the CPU on an FD-2000 is a 2Mhz 65C02 whereas the FD-4000 uses a 4MHz 64C02. The jumper block beside the 34p ribbon cable exists for configuring the PCB to either FD-4000 or FD-2000 mode. And I decided to go back to the cleaned and re-routed non-integrated RTC PCB for all builds because I decided that I didn't want SMD parts on the board from a maintenance perspective. Although it initially was a fun idea to integrated it, I ultimately wanted it to be completely serviceable (with it being entirely socketed) and more in line with the original design concept.
@@8BitResurgence Ahh... the RTC board has an SMD component... yes, clever idea to make it a module, socketed and serviceable. All around, fantastic work.
My pi1541 was built with the screen mounting similarly in mind so had the right female pin headers. That is a neat hack though that I will have to keep in mind.
That is some SERIOUS tape, and a SERIOUS watch tan (with some minor phaser fire near the strap zone)! Wait wait… did you say, “Core Eye Ninety Five”? It took me For-Ev-Vah to remember the name of Thomas’ company. It’s BONKERS spelling. Haha!! I’m right behind you, Gregory. Can’t wait to get mine later this month. (I’m literally counting down the days)
Haha. Yeah, at the start of the video I said COREi64 correctly, then later I brain farted and said i95, which is the name of the interstate highway that comes nearest to me. I put that note and apology in the video description.
AmigaLove, I'm almost finished your drive. Plan on shipping yours out in a couple days. I'll be sending it express so you won't have to wait too long for it!
Cool to see that from all angles. You definitely need a “Slice” ceramic blade safety cutter for those boxes. $6-$10 USD on Amazon. 😅 I think it would be cool to see a real-time full boot of C64 OS, with no REU fast restart, from this floppy drive. After that a REU fast restart would be neat.
What if instead of waiting for the entire section to be loaded and rendered all at once... It could instead load a smaller portion of text from the Wikipedia section, then it loads another portion of the same section, and repeat that until it reaches the end of the section, from the top to bottom of course. It could make glancing at sections, and the loading process more easy to digest for the user.
I think that what you're suggesting is more or less what it already does. Of a big article, it already breaks it down into rather small chunks, the chunks that come between the H2's and H3's, and only downloads a few paragraphs of text. When you click a heading from the table of contents it then downloads just that section. 2400 baud is just not very fast. It would be tricky to render only part of what has been downloaded while more of it is being downloaded, because the string is changing length and new memory is being allocated, etc. But don't worry, there are numerous other pieces of networking hardware for the C64 that are much faster than 2400 baud. We'll see much better results when using, say, a Link232 (@ 33.6Kbps).
I believe you are attributing more capability to the hardware than is warranted. :) The C64 is from 1982. The VIC-II is not capable of performing any computational tasks, it just outputs pixels to the screen according to the data in memory. And, although the 6502 could in theory take a kind of model or 3D representation of the object and render it with dithering, etc., practically speaking, it would take forever. Although less impressive, this is accomplished by using a Mac to render a 3D model and rotate it to various angles and degrees and extract frames from those points of view. This is 8 perspectives around the object, (360/8 = 45deg, so rotate 45deg take another image, rotate 45deg take another image, etc., all the way around) and then 5 angles; dead on, two angles up, and two angles down, and all 8 perspectives around at each angle. So 5 angles x 8 perspectives = 40 still images. The images are then rendered to multi-color bitmaps using conversion tools running on the Mac, and the image data is then packed together into a custom file format with a header that describes the data. You can read more about it here: c64os.com/post/imageformats
4:54 2400 baud slow as molasses, just like the original 1984 experience 😂 Just kidding man, great job in bringing a multitasking OS to an 8-bit home computer that still manages to amaze old timers like me.
9:00 does it work with languages that use another alphabet like Russian or languages that have a lot of accents on letters like Spanish because most old computers fail at that
@@c64os Such a great project (your work as a whole on c64os). I don't have a system to run it on in working order at the moment but I do enjoy following with daydreams of using it in the near future.
