| |
tlr
Registered: Sep 2003
Posts: 1714 |
Which assemblers do you/did you use for coding?
I thought this might be interesting.
I'll start:
I started out with Hesmon, and later switched to Handics VICMON.
Never did anything major in this. Just learnt how stuff was working.
Later I bought a copy Oasis Machine Lightning (which was bought up by Ocean and turned into Laser Genious)
I used Machine Lightning for all demos I did in the 80's. Cost a shitload of money.
It's line oriented (like basic) which sucks a bit, but has very good macro facilities.
I had a quick stint with Macrofire V1.0 but thought it was cryptic.
I started using dasm as soon as I got an Amiga.
Kept on using dasm when I switched to a linux system.
I have recently started using Kick Assembler 2.12 in combination with dasm and make (under linux). |
|
... 82 posts hidden. Click here to view all posts....
|
| |
Walt
Registered: May 2004
Posts: 47 |
When I started in about 1987 i learned the OP code values and wrote code in data lines.
Some time later I got a real machine code monitor program (never had any kind of cartridge, except for a simple disk speedup one I created myself) that helped a lot.
Finally in the end of 1989 got Turbo Assembler, that was a very big improvement. Made a version where I modified the assemble to file function to send the file over the parallel port to another C64 which had a very small receive program running. Maximum memory realized and no more crashes on the assembly machine :)
These days it is Kick Assembler, Notepad++ and NPPExec for starting the assembler and running VICE :) |
| |
Martin Piper
Registered: Nov 2007
Posts: 634 |
Mostly MSDevStudio or Notepad++ for me, with batch files to build everything. F7 is usually setup to run the build batch file and Ctrl+F7 is used to run Vice+net monitor+build output D64/CRT/PRG |
| |
spider-j
Registered: Oct 2004
Posts: 445 |
Quoting KrillKeep it like that, it's the elite way. =)
Not exactly: The "elite way" is to never have to open a terminal because it already *is* open – always ;-)
Anyway: I don't see why typing "make" in a terminal (or usually arrow up and enter – which are 2 keys – 3 if we also count ALT+TAB) gives some people a more "oldschool experience" than hitting 1 key in a text editor that will run "make". It's both pretty modern I think :-) |
| |
Krill
Registered: Apr 2002
Posts: 2843 |
Quoting spider-jI don't see why typing "make" in a terminal (or usually arrow up and enter – which are 2 keys – 3 if we also count ALT+TAB) gives some people a more "oldschool experience" than hitting 1 key in a text editor that will run "make". It's both pretty modern I think :-) It's not about "oldschool" (IDEs aren't a new invention - OG Turbo Assembler was a rudimental IDE, after all), but about separation of concerns.
Text editor does this one thing, and does it well.
Shell or whatever terminal thingy for actual execution/debugging.
If a full-blown IDE is your thing, fine, as long as you don't mind random stalls when typing. =) |
| |
Dr. TerrorZ
Registered: Oct 2013
Posts: 11 |
tl;dr : ca65, AVI, sublime-text
In early days I tried to write my own "assembler" using BASIC. These were simple INPUT loops which took in the handful opcodes I could understand.
Around 1990 I learned some more 6502 with the Action Replay VI monitor.
At some point I came across Rodnay Zaks' 6502 book and the C64 Reference manual, these inspired me to learn a little more during the mid-1990s. I could do conditions, loops and even copied an interrupt routine from somewhere.
In the 2000s there were a number of false starts with trying to learn more 6502 and cross-compilation, with internet materials at hand. I just couldn't find the time to do it properly.
2013 onwards I used cc65 to do a combination of c and assembler. With each project the amount of assy increased and eventually ditched the c. I still use the ca65 assembler from that package as I became familiar with it.
As editor I use Sublime Text, it helps manage different parts of the source. It does a poor job with 6502 syntax highlighting but it's enough.
I still sometimes play with the Action Replay monitor. Tried catridge-based TASM, but could no longer get into that. |
| |
spider-j
Registered: Oct 2004
Posts: 445 |
Quoting KrillIf a full-blown IDE is your thing, fine, as long as you don't mind random stalls when typing. =)
For me I found that geany (https://geany.org/) is the best compromise between text editor and IDE. It's a little bigger than the mentioned notepad++ and sublime (still smaller that vscode) and it's not less performant in "just typing text" than gedit (which I used for quite a while).
Afair sublime and vscode are more bloated than geany even if they call themselves only "editors".
Of course I also would not want to go eclipse or net beans or whatever. I have already coded a couple of lines in geany before those would even have started up :-) |
| |
Peacemaker
Registered: Sep 2004
Posts: 243 |
SMON+ |
| |
Monte Carlos
Registered: Jun 2004
Posts: 351 |
@spider: ... or some giga or turbo Nazi ass(hole) |
| |
DanPhillips
Registered: Jan 2003
Posts: 30 |
With a little help from Martin Piper...
Laser Genius v1.6L by David Hunter, used to make Armalyte/Deadlock.
Split into 5 or 6 files and linked using jump tables.
Using an expert cart/action replay to load up the game and patch the part that was being worked on.
~2 minute iteration loop. We used to wonder how anyone could wait 20 minutes for a compile...Now with UE5 it seems to be the way.
Cheers
Dan |
| |
Fungus
Registered: Sep 2002
Posts: 617 |
Oh wow you used Laser Genius? Surprising. I figured you cross assembled from Amiga or something.
Did anyone use TSDS? |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 - Next |
