So, does no one want the X1 version?
I definetly want the Xl version. (Or any other version for that matter. I'm still hoping to get a clean
dump of the disk image. If anyone has a PC88 version which has an MD5 signature of something other than 94a92e15ad909b7510dccca26128b54c
, please let me know.) Hopefully the level format is similar and I can reuse the level renderer codebase to generate a comparison set of images.
I appologize for not responding to your offer earlier. I was preoccupied with other stuff. I can't recall off-hand the RHDN rules on linking to ROMs. (Unlike many forum users (not anyone specifc, or even at this site, just in general) I read the rules when I joined, but the details escape me.) I know that requesting
links to ROMs in the ROM hacking forii is frowned apon. (Thus my request for a clean disk image may be taboo, but I think there's some leeway.) However, (unlike many sites), ROM sources is an allowable topic in the General forum. (There's even a dedicated thread, so I hear.)
What I suggest you do is re-read the forum rules. If if's absolutely forboden (that is
a word) to post the link here, go to the thread I mentioned above and post the link there. If posting ROM links (as opposed to requesting them) is allowable in the hacking forums, post the link here. I'm not the only one interested. Early in the thread, there was some interest in the Sharp version as well. One member in particular (I can't recall who and am too lazy to look) seemed to be a serious X1 fan and was disappointed to find that the image wasn't in his extensive collection.
In either case, PM me the link. It may be a distraction from the work at hand, but I'd really like to point my hexeditor at the port. BTW, (OT) can anyone recommend a good un*x or cross platform Sharp X1 emulator?
@Katatorian: Can you please update the source code if possible?
Sure, I can do that. I haven't really been keeping up on the source releases. This is because the intial one seemed to generate a lukewarm reception at best. Other than an aside concerning the custom level extractor, it didn't seem to garner any enthusiasm. Furthermore, there haven't been any requests for a second release until yours. (However, as I get my web hosting from my ISP, I have no download statistics, so I have no idea how many people actually grabbed the intial source release.)
Please be aware that the build enviroment is somewhat involved (especially for a Win32 user; un*x users, including those running OSX should have an easier time). The build process is automated using make. (GNU make specifically, but it should be reasonably portable across make variants, AFAIK.) Honestly, as a un*x freak, I (personally) can't imagine building a complex software project (and SMBS for NES has become moderately complex) without make (or an equivilant, like autotools, or Python's distutils), so I've got no
sympathy for those without a proper dev enviroment. "Thems tha breaks", as they say =_=
In addition to make, there a number of other dependancies for a fully automated build. The primary ones are as65 and ld65, which are part of the cc65 suite of 6502 (and relatives) development tools. While not the most popular NES assembler, as65 is (in all likelyhood) the single most powerful
freely availible and portable 6502 asm ever; Thus, it is my tool of choice. (As a side note, I was turned onto it by the famed (at least locally) Disch, who used it for his re-buildable dis-asm of Final Fantasy, my other (on hold) ROM hacking pursuit (at the moment).)
Beside the assembler and linker, you'll also need some standard file manipulation tools (cp, rm, dd). However, copy and delete on a MS system should work fine; Provided you edit the Makefile. dd is a bit trickier; I don't know off hand a Win32 equivilant, but I imagine any serious ROM hacker has something that's roughly equivilant. Additionally, you'll need a command line IPS patcher and (optionally) an NES emulator (for testing).
Finally, as you're already aware, the level extraction tool requires Python. While a final source release will likely include a Win32 stand-along executeable (created using py2exe), probably as a seperate package, I haven't gotten a proper cross-compilation eviroment set up at the moment (I don't run Windows and won't
That's a pretty heavy list of deps, but there are two cavetes that lessen the burden to the technically skilled. (Which one ought
to be if one's interested in the source code.) Firstly, all that stuff is only needed tor an automated
build. For most of it, a manual build could be accomplished with whatever ROM hacking tools one has on hand. Secondly, all the tools are open source and have been ported to all major (and many minor) plafforms, so they are readilly accessable.
The build processe has changed slitghtly since tha last release (streamlined mostly) and, as such, I should update the README, which hasn't been touched in weeks (or longer). Additionally, I've decided on a license for my personal source code contirbutions (i.e. the legal parts) and so should update that aspect of the documentation as well. While I'm at it, I may as well add a mini-HOWTO for building the package manually. All together, that entails a fair (but not major) ammount of documentation to be written. As you've requested a source release, I will provide one, but don't be surprized if it takes me a day or to to clean things up.
@Frantik: Can you give me the (Python-extracted) SMB levels with code for use in the source?
While I, clearly, can't speak for Frantik, I'm not sure he's got Py and is capable of generating level packages. That said, given the demand, I will release a level package coincident with the source package. (As I did shortly following the first one.)
Currenlty, there are (though it's not readily apparent) three "current" versions of the levels. The first (and primary) is those contained in the latest patches released by Frantik. Second is my own (very very minor) adjustments to those levels (well, one level, actually), which are present in the latest expanded build. Finally, there are any changes Frantik has implimented since the last release. (Although, those can be ignored as I doubt anyone will see them until they're released.)
When I do the source release, I'll include mine; Unless a new version shows up first.Well, that was pretty random, and (I'm sorry) really long (and, probably boring as well). G'night!