ASMPro 1.18 on A500/A600?

[Antiriad_UK]

Hi,

All my development at the moment is for A500 OCS. I'm editing in visual studio code in Windows and then flicking into an A500+ config (just for extra chip ram/slow ram and Kickstart 2.0 nicer environment) to assemble and test (WINUAE warp mode is great). Then finally a A500 OCS 512K chip + 512K slow for final exe checks.

The only assemblers I can get working in this config are ASMTwo, ASMOne 1.20 and Devpac 3.18. I wanted to give ASMPro 1.18 a try but I can't find an A500/OCS-ish configuration that runs. They all say they need KS 2.x but I'm getting these results:

I've set all the preference files to No FPU/68000 etc.

ASMPro
A500+ with KS2.04+WB2, crash on startup
A600 with KS2.05+WB2, crash on startup
A500+ with KS3.1+WB3, loads ok, but crashes during assembling
A1200 config, works.

ASMOne 1.48 won't even start without the config having a 68020

Am I missing a special config to get these to work or is ASMOne 1.20/Devpac 3 the best option for what I'm doing?

[Bruce Abbott]

Asm-Pro 1.18 has source code, but it appears to be based on a buggy disassembly of some ancient program, and the source is very poorly documented. I wouldn't trust it.

Devpac is 3 is system friendly and stable. Just don't try to load very large source files into its editor (it won't crash, but gets pretty messed up). I use CED and ProASM for editing and assembling now, but I still use Monam for debugging.

[Don_Adan]

Originally Posted by Antiriad_UK

Hi,

All my development at the moment is for A500 OCS. I'm editing in visual studio code in Windows and then flicking into an A500+ config (just for extra chip ram/slow ram and Kickstart 2.0 nicer environment) to assemble and test (WINUAE warp mode is great). Then finally a A500 OCS 512K chip + 512K slow for final exe checks.

The only assemblers I can get working in this config are ASMTwo, ASMOne 1.20 and Devpac 3.18. I wanted to give ASMPro 1.18 a try but I can't find an A500/OCS-ish configuration that runs. They all say they need KS 2.x but I'm getting these results:

I've set all the preference files to No FPU/68000 etc.

ASMPro
A500+ with KS2.04+WB2, crash on startup
A600 with KS2.05+WB2, crash on startup
A500+ with KS3.1+WB3, loads ok, but crashes during assembling
A1200 config, works.

ASMOne 1.48 won't even start without the config having a 68020

Am I missing a special config to get these to work or is ASMOne 1.20/Devpac 3 the best option for what I'm doing?

Yes, ASMOne 1.20 or Devpac 3 or Phxass are the best for kick 2.0 (68000). I runned higher versions of asmone and asmone pro on 68000, but i dont like these assemblers. Perhaps you must have stored correct config file in S: to run these assemblers. Use SnoopDos or DosTrace to check, what is missing.

[StingRay]

Originally Posted by Antiriad_UK

Am I missing a special config to get these to work or is ASMOne 1.20/Devpac 3 the best option for what I'm doing?

I think (from memory) I used ASM-One up to V1.25 on a 1.3 machine back in the day (TM), the newer versions won't run on such config anymore.

Originally Posted by Bruce Abbott

Asm-Pro 1.18 has source code, but it appears to be based on a buggy disassembly of some ancient program, and the source is very poorly documented. I wouldn't trust it.

ASM-Pro is based on a disassembled version of ASM-One which has then been improved. The source is indeed quite a mess and almost impossible to maintain.

[Antiriad_UK]

I always used Devpac back in the day. But I like some of the features of AsmOne since I watched Photon's tutorials. I'm sticking with AsmOne 1.20 for now. But I've been playing with the visual studio code plugin that uses Vasm and allows really nice debugging and I think I'll move to that next project.

[StingRay]

Originally Posted by Antiriad_UK

I always used Devpac back in the day.

Like most other UK coders. Rest of the world used ASM-One or one of its many derivates.

[NorthWay]

Asm-Pro, Asm-One and whatnot are, AFAIK, non-authorized hacks of the K-Seka assembler. Might not be much left of the original, much as my grandfather's beautiful axe that my father replaced the blade on and which I replaced the shaft of, but if you start from the original and go one by one on the mods you'll see the red thread.

Myself, I have used ArgAsm (yep, have it on my shelf here), Macro68 (real solid that one), and since then Barfly. Can't beat BDebug IMO.

[StingRay]

Originally Posted by NorthWay

Asm-Pro, Asm-One and whatnot are, AFAIK, non-authorized hacks of the K-Seka assembler.

ASM-One is not a SEKA hack and since ASM-Pro is based one ASM-One it is not a SEKA hack either. ASM-One was coded from scratch by Promax (source is available), before coding ASM-One he did various modifications to SEKA though.

[Bruce Abbott]

Originally Posted by StingRay

Like most other UK coders. Rest of the world used ASM-One or one of its many derivates.

I started with the Metacombo assembler. Then I got AssemPro, which came with a nice book called "Amiga Machine Language" from Abacus. Several years later I got Hisoft Devpac 2, which I thought was heaven because it was 5 times faster than AssemPro and never crashed!

[oRBIT]

I'd *love* a new assembler for AmigaOS, something like AsmOne/Pro but without the bugs and with more modern features. Anyone up for the task?

Sorry, offtopic.

[kamelito]

There's AsmTwo by Photon, but it is aimed at 68000 only IIRC.

[TCD]

Didn't want to start a new thread, but there is an update for AsmPro: http://aminet.net/package/dev/asm/ASMPro1.19.lha

Update for the ASM-Pro package, includes latest executable.

This release fixes a number of KS2.x, 68000/010, and FPU compatibility
issues, as well as a large number of other issues (over 60 bugfixes in
total, see the history file for details). You can run it on KS2.04+
and 68000 based systems again.
Code has been cleaned up and optimized (over 2600 micro optimizations,
and a number of subroutines rewritten), resulting in 15KB reduction of
the executable size and a smaller memory footprint overall.

Additions (detailed description available in the history file):
1. WX command to enable short code and data hunks (code+bss, data+boss)
2. ADDBP directive to add a breakpoint from the source code
3. Command line history jump by 10 lines, don't store repeated lines
4. Macro symbol parameter \<symbol> and \<$symbol> (vasm style)
5. Assembly elapsed time