I migrated to OS X 10.11 the day after it was released and then hadn’t had a chance to play with it until today. A few years ago I made a small script to automate login on one of my machines. I put the script in the /usr/bin/ folder and all had been well. It turns out that Apple made a change to make the OS more secure. No longer does the ‘sudo’ command give you access to everything. Now if you try to put anything in /System/, /bin/, /usr/, or the /sbin/ folders even with sudo, you will be denied. Only an Apple signed file can be put in those directories. With the exception of /usr/local/ that is. You can find many fine articles on why, and how to disable this new feature, like this fine article at Ars Technica.

Knowing why doesn’t much help you should you find yourself in my position. I couldn’t remember exactly what was in the script. So I went looking for my trusty Time Machine backup. However Time Machine doesn’t provide an easy way to locate protected directories like the /usr/bin/ I eventually discovered I had put my script in. I was forced to do some Googling to find out that Apple moved files that were not supposed to be in those protected directories to a special folder.  Apple helpfully moved them to /Library/SystemMigration/History/Migration-{UUID from somewhere only Apple knows}/QuarantineRoot/{Then whatever folder it was under. In my case it was usr/bin/}.  Once I sudo copied my script over to /usr/local/bin I was able to run it again and all was well with the world again….. Until next year when Apple changes our world yet again. But hey, it’s still safer then Windows. At least as long as you don’t have Flash or Java. In that case you might as well just buy a PC.

Comments No Comments »

After seeing a post by the Retroist awhile ago I promptly forgot the link and went on my way. Later, when I was ready to change my wallpaper, I went back to his site to find this post. I was able to page through the many listings for ‘Wallpaper’ on his site to find this post. Along the way I found a different post that linked to a really cool image of the Atari logo. When I went to add this image to my home screen I found out it isn’t really easy to “Move and Scale” an image that doesn’t fit on the screen well. You can zoom in, but you can’t zoom out to get the entire image to fit on the screen. So I did a little looking and thanks to this website I was able to find out that I needed to make the image 744 X 1,392 pixels for the iPhone 5/c/s. With a little photoshop work I was able to make a pretty decent lock screen view of the logo. Maybe when I decide to change the home screen I will find either a good image of a “woody” 2600 or the stock joystick to fit under this logo. But until then, enjoy.

iPhoneLockScreenAtari

Thanks to Retro Justin @ http://www.boxing4free.com/retro/ for the original image.

P.S. To get this on your lock screen just open this link in Safari on your phone, and using the Share button Save Image. Then open Photos and choose Albums at the bottom and select Camera Roll. From there view your picture and press the Share button again and at the bottom select Use as Wallpaper. Then just select Set and Set Lock Screen and you are all done.

Comments No Comments »

That’s probably not entirely true. But thanks to the 8.3 update to iOS we either have to jailbreak our phones or go somewhere else for our retro gaming fixes on the go. At least that’s my interpretation. Prior to 8.3 there were two important apps on my iPhone that I could use to feel like a kid again.

Gridlee, which was yanked within hours of being posted on the app store, allowed me to play arcade games in an emulator called MAME. It was basically a MAME emulator that played one arcade game, Gridlee. From what I read the Gridlee game was licensed. I am not sure if MAME was. It’s attraction was that it was leaked that if you used an app like iFunbox you could drop Zip files with MAME compatible ROM’s in Gridlee’s Documents folder and voilà, Gridlee shows a MAME front end. And the best part of Gridlee, it was compatible with the iCade, also because I liked portability the iCade 8-Bitty. That was before Apple “figured out how to do controllers”. I wasn’t aware there were technical issues that needed to be solved. Console’s had solved those issues years ago. But you know Apple, they are the only ones that can bring great tech to the masses. Did you catch the sarcasm? Anywho, Apple yanked it from the App store but as long as iFunbox had access you were good to go. Even after Apple borked other ways apps downloaded content in iOS 8 Gridlee still worked. (My other favorite game Atari’s Greatest Hits which plays Atari 2600 games fell to this issue. To their credit, they did finally fix it. Thank you Atari!) Now it looks like Apple may have permanently taken access to that directory away. Making Gridlee unusable in any other iOS device I might get in the future.

The other casualty was Manomino’s C64 Emulator. It was a great little emulator based on Frodo for the iPhone. I kept waiting for an iPad version but sadly development stopped and due to licensing hassles it was eventually permanently pulled from the app store. I say permanently because it had been pulled once before. Apple didn’t like the fact that you could program BASIC on it. That capability was supposedly taken out. However, the version I have has the BASIC interpreter as a playable “game” in the library. And even without loading any games I can program in BASIC. With iFunbox you were able to load new games into the app and even add box art. I was even able to load and play “Impossible Mission”.

Alas, the days of playing Arcade and Commodore 64 games on the go appear to be over. Thanks a lot Apple. Well to be fair thanks should also go to the owners of Commodore and to all the content owners that refuse to do anything with their IP other then sue people who want to enjoy their creations. Even licensing it so that a game or group of games is only a buck or two has got to be a better way. So I leave you with the best parting words ever written:

“So long, and thanks for all the fish” – Douglas Adams, The Hitchhiker’s Guide to the Galaxy

 

Comments No Comments »

As you may have already read, a couple of weeks ago I set out to compile CGTerm for the Mac OS X 10.9. I was able to accomplish this and received some feedback that encouraged me to dig deeper. Some of the things I decided to add were an application icon and to “package it up” so that it was easier to download and install. Those were minor touches that didn’t need a lot of actual code.

The biggest issue, and one that I felt would keep people from even “calling” a BBS if they owned a Mac (PC owners seem to have plenty of other options without much work. Namely using a terminal program running inside WinVICE. With that you get all of the thrill of a BBS.) was the fact that CGTerm was hard coded to use positional key mapping. What that meant was that keys like the 9 key would map to the 9 key on the original C64. Meaning when you pressed Shift-9 you got the ) character. Not the ( character you were trying to type because that’s what your keyboard showed. You could change the key to any other key, but that still meant that shift and that new key would produce a ). You couldn’t move ) alone to some other key. That was a big show stopper in my book. Without having some kind of overlay on your keyboard how could you hope to remember what key to press. Especially when the games menu was accessed using ‘*’ and Shift-8 did the ( character and put you in the message board section. Which, knowing my luck, probably also used the ‘*’ character to get back to the main menu? How frustrating right?BBS Command Main Menu

Well I HAD to play my games. Nuke Em has been calling me back for years. I must vindicate America by beating Greenland. (I was thinking the same thing when I first played the game 20+ years ago. When did Greenland ever become either a Nuclear Power or was ever a big player in any war game?) So to do that I needed to be able to tell my ‘*’ key from my ‘)’ key. I tried many different ways to get that blasted ‘*’ key to map correctly. Finally I gave up and decided I needed to recode CGTerm to do symbolic key mapping.

Symbolic key mapping allows the user to to program each key, along with modifier keys like the C= key, short key, and control key, independantly. This way if I wanted shift-9 to put out ‘*’ and control-9 to put out ‘G’ I could. I don’t know why you would want to, you still would forget how to get to the dang games menu, but you could if you were feeling particularly plucky.

The old version of CGTerm required a .kbd file to be present or it would actually fail and you couldn’t even start it. Not helpful considering the fact that unless you had an installer that created the settings file (.cgtermrc) the app would create a settings file but wouldn’t load it. It would try to find a default keyboard file in the default location but if you knew where that was this wouldn’t be an issue in the first place. So I fixed that as well. If it can’t find the settings file it creates it and loads it at the same time. And if it can’t find a keyboard file it just assumes you are OK with using your keyboard just the way IBM (or Apple in this case) intended.

In composing this blog post I ran into an issue trying to download files. I guess I have more work to do with default file paths. But at least I can play my Nuke Em. My original post on compiling CGTerm for Mac has the current .DMG image if you want to download and run my version of CGTerm. I have included the source code at the bottom of this post should you want to compile it for PC or another platform. If you decided to do that drop me a line. I would be happy to link to your compile so others can enjoy BBS’s on as many platforms as can be made available.

Here is the new source code: CGTerm 1.8 Source Code

Comments 3 Comments »

Ok, so I finally did it. Back in 2011 when OS X Lion debuted I went looking for a good way to get back into BBSing. I have missed the long hours spent in front of the keyboard trying to get a game mod working on my board. Funny thing is, those were fun times. But I didn’t see it that way when I was doing it. In fact as I recall I think I felt like I was trying to get a high score in the game of ‘Blood Pressure’ back then. Of course when you are 16 you don’t care about silly little things like cardiac arrest.

Anyway, I had just bought my first Mac after the family PC died. I was just learning about OS X and had installed Lion. Lion turned out to be a mess. But that’s a WHOLE other post. I had been trying to figure out why Lion kept crashing so when I downloaded CGTerm  and it wouldn’t work I was mad but I had bigger fish to fry. After I fixed what Apple broke, I went to Google to find the answer to my CGTerm problem. Doesn’t Google have all of the answers for everything? And with Apple being so popular I knew for sure someone had figured out the black magic needed to run run this or connect to a BBS from my Mac. But alas it was not to be.

As it turns out, the only version I was able to find that was compiled was for PowerPC. So I decided to figure out how to compile it for the Mac. But that turned out harder then making Lion work as it should. So I did what any good IT person does, I gave up. Well that’s not entirely true. I just turned my attention to getting Color64 to run in an emulator. Which I was mostly successful at.

Eventually I decided I didn’t have enough quests er I mean open projects. I needed at least one more. So I decided I would learn to program iOS. I couldn’t get websites to run the way a giant team with millions of dollars and years of experience to so I figured programming for the phone natively would be easier right? Well sort of….

I had just enough knowledge to cause some real damage so I decided to throw the source code into XCode to see what I got. After messing with the code a ton I was finally able to get something that could be placed in the Application folder and wouldn’t crash on launch. It doesn’t have a native installer because I don’t have the $99 a year per platform Apple needs to keep from going bankrupt. But if you download the zip file and follow the instructions at the beginning of the Read Me file you should be able to start dialing BBS’s.

I wasn’t able to test upload and download and I had to make some changes to the source so it wasn’t so confusing when you saved .SEQ files. And it appears that the person that programmed this originally has abandoned it as it was out of date in 2011 and the website still has some failed links. But I updated the default configuration file to include the address of real working BBS’s and tested them all. So if you have any questions, feel free to email me. I would be happy to help where I can so we can get more people using these BBS’s. One day I hope I can get a terminal program going for iOS.

Just in case it wasn’t clear from this posts title but this compile should run on any system 10.9 or greater. It would work on 10.7 but I couldn’t force it go below 10.9. And besides, who is running anything earlier the n 10.9 now anyway? Now if only I could get Nuke ‘Em running again……

 

UPDATE (2-9-2015): Zip file was removed. In it’s place is a disk image file with CGTerm v 1.8. Download the DMG file and open. Then move CGTerm.app over the link to your Applications folder. Also be sure to move the SDL.Framework folder to link to your Library/Frameworks folder. See my post on fixing bugs in CGTerm for more information on changes made to v 1.8 and the source code for the changes.

CGTerm.dmg

Comments 7 Comments »

If you are like me, you might have wanted to dive back into the wonderful world of BBS’s but have come up short on walk through’s or posts. Most discussions simply point to another URL that is sort of like your question but not exactly. Only to have the answer point you to another URL and another and before you know it you have jumped down too many rabbit holes and crashed Chrome.

Too many rabbit holes huh?

Too many rabbit holes huh?

Here is a quick rundown on tools to connect to a BBS or diagnose if the owner has yanked his board yet again or if the issue is not knowing how to connect.

First of all we need an IP address for the board. Most boards listed will have a Domain Name. However most boards are run on home connections which may not be static. Recently the popular Dyn DNS service chose to stop offering free accounts. Which means a few BBS’s may have been knocked offline. So before beginning it might be useful to run down the IP first. If you can’t get the IP you may have to dig to see if the name changed or they simply gave up. I use PING to find the IP of systems I want to call.

We are only sending 1 packet as we just want to see the IP. There are other ways to look up the IP but getting to know PING is a good idea. In this case the server at 64vintageremixbbs.dyndns.org won’t return a ping packet. That’s perfectly normal. It doesn’t mean his BBS is offline. It just means that the server either isn’t responding to pings or a firewall has blocked that port. The only real way is to try to connect.

Let’s first try to connect directly from the terminal window. Mac/Linux/Windows can all use Telnet.

We are giving telnet the domain name (you can also put in the IP directly here) and telling it to connect on port 6400. Most BBS’s are hosted on an empty port. Commodore 64 BBS’s frequently use port 6400. So if the BBS you are trying to connect to doesn’t list a port, try 6400. Once you are connected, your terminal will tell you what the ‘Escape character’ is. In my case it was ‘^]’. Which, not being familiar with these commands meant Control Key and ]. That gets me into the place where I can issue command like  quit to close and exit or  close to just close and stay in telnet.

One thing to remember with telnet is that the implementations I have run across all default to ‘Line Mode’. What this means is that they don’t send anything until you hit the Enter key. Old school BBS’s used ‘Character Mode’ meaning they sent any keypress as soon as it was typed. So if the BBS you are calling is behaving weird or not responding they likely are expecting Character mode. Type your control keys and at the telnet prompt change modes with  mode character I ran into that while trying to write a Telnet server to act like a Color64 BBS. Commodore BBS’s were not intended to run on the Internet and don’t issue any commands or detect modes.

If the BBS you are trying to reach is on or compatible with Commodore 64 I would recommend using a terminal program. The best native terminal program I have found is CGTERM. It appears to have been abandoned as the Mac binary doesn’t seem to run with OS X 10.7 and above and I wasn’t able to find enough information to compile it. If someone has compiled it I would be happy to put it on my blog as I love using this on Linux. I haven’t used actual Commodore hardware to connect to a BBS over the Internet but I have used software in Vice to connect. But that’s a post for a different day. Let me know if you have any questions. I want as many users back on BBS’s as I can!

UPDATE (1-22-2015): I was able to compile CGTerm to run on a Mac in OS X 10.9 or greater. See my post here for more details and the download.

Comments No Comments »

OK, so I am going to go geeky and deep on this one. But as part of my Color64 BBS project I needed to use a WebSocket proxy tunnel to the Color64 BBS software. It turns out Ubuntu isn’t up to the newest version of Apache. A little Googling and I came across this post.

The only problem is that it’s on someone else’s blog, which means I might forget where I found it should my server crash. 🙂 And the code for the exact steps need to be altered. So here goes with the modified steps for Apache 2.22:

Edit: Ubuntu may have upgraded Apache to allow for WebSocket Proxies. So I am simply posting this as a reference at this point until I update and confirm that these steps aren’t needed.

Comments No Comments »

Finally! I have been searching, and searching, and searching for a way to put an instance of the Color64 BBS online for some time now. My goal really was to be able to play Nuke Em again. Unfortunately after scouring the Internet I haven’t been able to find any mods for Color64. The only mods I have been able to find were for Image BBS. As I was never an Image BBS Sysop, they only interest me as to make a conversion of the game play.

Not finding any original mods didn’t dampen my desire to run a Color64 BBS again. Several people are doing that but they are either using a real Commodore 64 or a few of them are running them on an emulator hosted in Windows on winVICE. After trying to learn servers and web programming on the Windows environment years ago I gave up when I wasn’t able to pay Microsoft thousands of dollars or rent space on a web server that had enough permissions to actually learn something. I moved over to a Mac. Even Apple wanted to charge a premium for their web server though. Even if it wasn’t the thousands Microsoft wanted it was still too much considering Apple now wants you to upgrade every year and charge you for upgrading the web server software.

Enter Linux. Since most of the world is running on Linux with other part running Microsoft I figured I would give that a try. And I was very impressed with the capabilities. No longer did I need an expensive license to learn and host a website. Or to remotely manage my system at home. I could even run a trusty Commodore again.

But I digress. The moral of the story is that I found out how to get Color64 working VICE 2.4 with Ubuntu 12.04.4 Linux. The hack I put into place should work with winVICE on Windows as well as Mac. I haven’t tested on these platforms so don’t quote me. The hack involves replacing one file in the VICE source code and compiling.

Steps to running Color64:

  1. Download tcpser. Tcpser serves as the bridge between VICE and the Internet. Once again, thank you Jim Brain for such a wonderful piece of software.
  2. Next download the VICE source code. I used version 2.4 but with some modifications I am sure newer or older versions will work.
  3. Expand the tarball to your Desktop or other directory.
  4. Replace the rs232.c file in src/rs232drv/ with this modified version. I have commented out the one changed line and commented the inserted two functions and one variable. The changes were found from modified files at gcns.com.
  5. Now when in the root of the VICE folder, Configure, Make, and install the VICE source code.

    Should you make any mistake or if you need to start over, you can uninstall by going to the same root of the folder in VICE and uninstalling VICE.

    There is another nice tutorial at the Ubuntu Forums that has helped in figuring out how to compile and install VICE.

    • When compiling on x86 I had no problems. When compiling on an x64 system I had to make a link in order for VICE to find the kernal. I am sure there is a configure option needed I just didn’t find it when I made this post. Until then if VICE complains that it can’t find the kernal use this command.
  6. Assuming the build and install process went well, we now need to invoke tcpser. Tcpser will act as the modem taking calls from the internet and putting them on the rs232 port in VICE. Open a terminal and invoke it with this command.

    If you would like a little more information about tcpser and how this works with VICE, see this post.
  7. Now we need to setup VICE to communicate with tcpser. I like to run VICE from a command window so I can watch the output and any errors that might come up. Either way we need to make the following changes to settings under the RS232 settings menu:
    • Turn on “Userport RS232 emulation”
    • Select “1200 baud” under “Userport RS232 baud rate”. (This can be changed in the middle of a session without a rest. Just remember that the speed tcpser reports can’t.)
    • Under “Userport RS232 device” select “Exec process”.
    • Under “Program name to exec…” type  | nc localhost 25232 (Be sure to include the pipe “|” char at the begining. This command will send all input and output normally being sent to/from the VICE userport to “localhost” (if you have issues you can use the IP of the machine tcpser is running on. Normally localhost is an alias for 127.0.0.1) on port 25232. This is the IP and port of tcpser, our “virtual modem” interface.
  8. Once we have VICE and tcpser setup we need to attach the BBS software to drive 8 and run setup. Make sure to uncheck “True drive emulation” under the “Drive settings” menu. That will speed up operation of the board a ton. You can get a copy of the Color64 disks here. All of the documentation I have read states that the author (Greg Pfountz) has released  the software into the public domain. Thank you Greg. It’s refreshing to see a copyright holder allow us to keep the software alive. The best way I know of to avoid the dreaded disk swap is to take all of the software on the D64 disks and put them in one D81. Right now the best way I know of is to use Style’s DirMaster. It only works on Windows. Hopefully in a little bit I will be able to update this to add an online tool I am working on that will let you do that and more. It will really be helpful for Sysops.
  9. Next we need to run the setup. I suggest if you haven’t run Color64 before, or if you are like me and haven’t run it since before my kids were born, that you read the manual. The best manual I was able to find was here.
  10. I won’t go into the settings much in this post, maybe in another post I will detail them. But for now the important changes are to these settings:
    • ‘Normal or Inverted hook’ = n
    • ‘User bit 32 = High Speed’ = y
    • ‘Use ‘AT’ modem commands’ = n (Very important. It appears that without this the BBS will always try to start at 300 baud. We want to run at 1200 baud. Either way, the BBS uses AT commands.)
  11. Once setup is run it’s time to start it up. Settings will automatically load the board if you allow it. Once it’s setup we need to make a few ‘adjustments’ before it will accept calls hands free.
    • First we need to use a terminal to connect. See this post for more information on connecting from Telnet or CGTerm.
    • Watch the connection as you connect. You will see a screen like this. Bad Connection
    • The garbage above Last Caller indicates the speed isn’t right. Switch the Userport RS232 baud rate to 300, you should see a ring message where the garbage was. Then you should see a ‘connect 1200’ message and your terminal will show junk. Now you change the Userport RS232 baud rate back to 1200 and you should be good to go.
    • If it still won’t connect at 300 or you didn’t start the BBS with 1200 you should reset everything. Close and reload tcpser. Then do a hard reset on VICE and load the BBS again.
  12. The final step is to forward the 6400 (or whatever port you set -p to in step 6.) port on your router to the computer running tcpser.

Now tell the world that yet another Commodore BBS rises from the grave! You can start by going to Commodore BBS Listings or post an announcement on the Lemon64 forums. And by all means, please let me know to!!!

Comments 16 Comments »

Recently I decided that I wanted to run another Color64 BBS. I don’t have any of my Commodore hardware nor do I have room in the junk room my wife calls my “office”. So I went looking for a way to emulate it. I needed to use what I had around me. Which in this case was a machine I had running Vista that was flaky. So I put Linux on it. Low and behold, the issues I had with Windows disappeared. That and suddenly I had access to software that wasn’t easy to setup in Windows.

People kept telling me that others had run a BBS in emulators but I wasn’t able to find hardly any information on how to do it. The only information I found was how to hook a real C64 up to a PC or how to use a hacked version of VICE on Windows machines. Both ways referred to using a program called “tcpser” with some commands you had to go on blind faith that they would work. They didn’t explain those commands. Tcpser on Linux has a man page, but there are still mysteries on how to use it properly with an emulator. So let me explain what I have found out.

This information should work for all versions of tcpser. My examples will be with Ubuntu 12.04 distribution of Linux. First we need to download it. Ubuntu bundles everything we need for it. Just use  sudo apt-get install tcpser

Next we run the command in a terminal window. The window has to stay open the whole time the BBS is running. Unless you detach the process with something like tmux. But that’s something for a different day. 🙂

Let me explain what this command is doing. It doesn’t seem to be documented well enough for a newbie to understand it well. 🙂

  • -v 25232   This is the port tcpser will present a virtual modem to VICE on. In this case we chose 25232. This can be any port as long as it is free.
  • -p 6400   Tells tcpser what port to listen for incoming “calls” on. In this case we chose 6400. Once again, it can be any open port that other services aren’t using. This is the port the caller will be connecting to.
  • -tSs  Activates the S & s Trace flags. This is entirely optional. The ‘S’ is to put modem output to stdout. The ‘s’ sends modem input to stdout.
  • -l 7 This is the logging level. In this case we chose the most verbose of 7 just to see how it works. You can also choose 0 which is the default of no logging, or 1 which only shows fatal errors. Those three levels were the only I could find in the documentation.
  • -i "k0"  This is the initialization string. It takes most of the commands in the Hayes ‘AT’ command set. In this case we are only setting flow control to none. If the BBS software doesn’t know how to answer an incomming call (I don’t know why it wouldn’t. But you never know right. 🙂 ) you could also put “s0=1” to answer on the first ring.
  • -s 1200  This will report the incoming call as 1200 baud all of the time. Make sure VICE is set to that baud rate. If not you will get Frame Errors and probably be frustrated as to why this doesn’t work.
  • -N "/tmp/noanswer.txt"  This command points to a text file that will be sent to the caller if the software on the receiving port fails to issue the  ata command. Make sure tcpser has permissions to read this file. I chose /tmp/ as everyone should have access to that folder. You might want to chose /etc or /var though.
  • -B "/tmp/busy.txt"  Points to a text file to be sent if the server is already taking a call. This way someone trying to access your board knows at least that you are up and haven’t crashed or abandoned your hobby. The same permissions and folder warnings apply for this as the -N command above.

Armed with this information you should be able to set up your “modem” to either call other BBS’s or setup your own BBS. If you discover my settings to be wrong or have new insight I overlooked please add it to the comments or send me an email. It took some time for me to figure out how to use tcpser correctly, hopefully this will save someone just a little time.

Comments 5 Comments »

I miss running a BBS. That was back when you actually felt like YOU controlled the computer, not the other way around. These days even programmers don’t understand why the computer is acting up. It seems to take a village of IT people just to run a word processor.

That’s not how it always used to be. Back in the 90’s when I ran a BBS with Color64 on a Commodore 64 it only took one person to run the whole show. Not that it was a big show or very long running. Mine was canceled after about two years. And for good reason, it wasn’t very interesting. I didn’t have much software available to download and I wasn’t able to locate a ton of BBS ‘doors’ as they were called to play games on. Though I had a few.

My absolute favorite was called Nuke Em. In Nuke Em you played as a country and had to buy various parts of missiles and build a missile stockpile. Once you had a stock pile the only logical and fun thing to do is nuke your enemies. While that sounds more like real life now, back then it was fun. Like when as a boy I played ‘War’. Now days if my son asked to play ‘War’ I wouldn’t let him for fear that he would be shot by accident by the police. Not that police are wrong mind you, they just have a very tough job. And when they make mistakes, that’s all you hear about for a week on the news.

Anyways, back to the BBS, I also wasn’t able to generate much conversations on my board either. Considering that I maybe had 25 members that only wanted to download software I guess that shouldn’t have surprised me. But boy did I have grandiose dreams for that board. So I have been looking for a way to run Color64 again.

I don’t really have room or access to run a real C64. But even if I did it seems that the only instructions on the Internet today seem to require using a Windows system as the interface to the net. And since I am not made out of money I am using what I have available, an old PC I thought was dead running Linux. And I can’t seem to find ANYWHERE for step by step to run Color64 on VICE and get it to pick up the line when someone ‘calls’ in.

So I am doing the next best thing. Writing software to emulate the experience for me. Which is a HUGE undertaking. One of the issues is terminal emulation. Commodore computers used a customized keyboard to display text in a different way then other computers. This allowed them to have graphics in text. (See the homepage for an example.) Even HTML won’t do that as easily as the Commodore did.

Another issue with terminal emulation is nobody sits still. How much time do you spend in front of a laptop or desktop vs a phone or tablet? I spend a lot of time with a laptop but that’s at work. To really have fun I need to be able to access the BBS from a tablet or phone. That means emulate the experience of sitting behind my Commodore 64 in HTML so I can use my iPad to play those games. That’s a tough order. But one I might be able to accomplish by the time my kids emulate the XBox 360 to relive their youth like I am doing with the Atari 2600 now. So check back from time to time. Hopefully I will be able to post links to this project so everyone can experience those two Mountain Dew fueled years close to how I did. (Minus the heart problems I am sure all of that caffeine I drank will cause. And late nights spent fixing a door to work.)

Comments No Comments »