Just so I’m no longer hijacking @zmetzing’s 6502 BASIC thread… (I’m sure I’ll need that too someday!*)
To @Bill, @urbite, and @denzuko who have expressed interest, and anyone else who says they want in, I’ll probably start up a private BitBucket account if you all have the inclination to take a stab at decoding a few bytes’ worth of the machine code that lived on this device (there’s 10K total to go through!). Perhaps we could coordinate on exactly what lines we’ll try just to avoid duplicating work. The end goal is to get it into a state where someone who’s familiar with say C++ or Java could easily tell what’s going on at a high level, making sense of all the Boolean logic & jumps going on.
To your comment on Zach’s thread, Dwight: sorry today’s viruses are not as entertaining to disassemble as in the days of old. I think they’re all written by opportunistic teen & pre-teen punks who don’t care to put much creativity in them anymore, except for the ones that are sitting on the firmware of your hard drive that you’ll never notice (i.e. the super-scary ones).
I’ll post more here when new news develops.
P.S.* Actually this page details what would have been used originally, instead of 6502 BASIC: TGOL language
Yeah, I was gonna make a comment akin to “you might have to squint your eyes a tad to actually see the technology they talk about on that page” They seem to adore their 3D-rendered swimsuit models throughout that whole site…
nope those guys just download or buy copies with stolen credit cards from the original authors. whom of which spend their days google dorking howtos on botnets and “crackz” while only caring about stealing credit cards or hosting accounts to add into their botnet. So the whole lot of them have no creativity.
Knowing my luck, this would end up being me but the more the merrier
In any case once you get the BitBucket setup and have a few images ready I’ll start the dissection and post up notes on a documentation branch then send a pull request.
Found a few resources that may help everyone on the project:
Or you can use a Fluke 9010A with the appropriate CPU pod to search the memory map from $0000 to $FFFF and let it discover the RAM and ROM ranges. It will list out the ranges when finished.
I have one in my shop. Once you have the memory map for RAM/ROM done you can spend your time on decoding the memory mapped I/O space.
Go ahead and sign up there for access, I suppose, and I’ll add you. A DIS6502 workspace has been saved, along with the disassembly work I’ve already done (which is being converted into Wiki form). There’s also a schematic of the MPU.
(I’m sure I’ll need that too someday!*)
I think they’re all written by opportunistic teen & pre-teen punks who don’t care to put much creativity in them anymore, except for the ones that are sitting on the firmware of your hard drive that you’ll never notice (i.e. the super-scary ones).
