Porting Page
Hey all, Derek asked if the C64 porting work I've been doing is based on source code or ROMS.
So, I've been working with disk images (.T64 and .D64, which emulators read). I'm trying to turn them into ROM images. My basic tactic is load them into an emulator and save snapshots of the memory. This is the minimal effort way ;) It will work easiest for games that load completely into RAM then never access the disk device again. So far, it looks like Master Type is the first candidate!
Disk Images
The .T64 and .D64 disk images encapsulate the binary images of the sectors on the original disk. The original disks are of a godforsaken filesystem from the 80s with half of the code on the disk drive and half in the Kernal. I don't think it's worth it in the scope of this project to emulate the 1541 disk drive.
Porting Progress
So far, we've got a lot of little bits and pieces running, preparing a range of porting and development tools. You can read more specifics here in my recent blog post.
So, I've been working with disk images (.T64 and .D64, which emulators read). I'm trying to turn them into ROM images. My basic tactic is load them into an emulator and save snapshots of the memory. This is the minimal effort way ;) It will work easiest for games that load completely into RAM then never access the disk device again. So far, it looks like Master Type is the first candidate!
Disk Images
The .T64 and .D64 disk images encapsulate the binary images of the sectors on the original disk. The original disks are of a godforsaken filesystem from the 80s with half of the code on the disk drive and half in the Kernal. I don't think it's worth it in the scope of this project to emulate the 1541 disk drive.
Porting Progress
So far, we've got a lot of little bits and pieces running, preparing a range of porting and development tools. You can read more specifics here in my recent blog post.
Views: 1
© 2012 Created by Daniel Rehn.
Powered by 
.
