A.D.A. Amiga Demoscene Archive

I have installed Asm-One 1.48 on a "out of the box" Cloanto Amiga Forever 3.1 workbench.

There seems to be a fair share of resolution/screen size changing when starting Asm-one and when running a compiled source. It is better when not running Winuae in full-screen but there is still an amount of swicthing and quite a long time to for example exit from "demo" back to source.

What are the best settings for:
- winuae display settings
- workbench screen prefs
- asm-one screen prefs

I try not to run in full-screen mode at all, because all the clumsy mode switching is much worse than a little window resizing. Setting your window size for native modes to the same as your Workbench resolution also helps a lot. And I run Asm-Pro in the same resolution too.

Be sure to match the colour depth of your UAE window to that of the Windows desktop, that appears to make a big difference, and "play around" to get the best "filter" settings.

AFAIK the only way to completely avoid annoying switching is to run your assembler in a PAL screenmode.

I second Doom here, I also use UAE in windowed mode only as this is much less annoying than all the resolution switching in fullscreen mode.

Another question regarding Winuae. Sometimes when i compile something (with a, so no running just assembling), the AsmOne screen doesn't show any output (pass1,...) and goes completely grey. When i then click on the mousebutton, all i see is the menu but i can't do anything anymore and have to reset. I have lost quite a bit of typework due to that (lesson: always save before assembling).

It seems that asm-one has trouble handling the fact that you use a variable that is not declared (which is normal but it should just give a warning and not hang).

For example, uncheck the Uppercas = lowercase and type

lea screen,a0
...

Screen ds.b 200*40*8

or just the following case:
lea buffer,a0
...

bufer incbin sources:pic


Does anyone has the same problem?

I find that Asm-PRO is generally better than Asm-One. Both however have these bugs, and shitloads of them.

The bugs are different from version to version, and also depend on other parts of your setup, so you can try different versions, screenmodes, fonts, etc., and maybe you'll end up with a set of bugs you're comfortable with. And until you feel like rewriting the entire IDE, just learn to accept that that's how it works. ;)

Of course, undefined symbols causing crashes would be hard to live with. It happens here too, but only if I type an incorrect label with a "j" or "ad" command or some such.

Has anyone tried Font2raw with Winuae? The raw files it makes seem completely bogus. At first i thought it was something in my code but when i open the raw font files and compare them with the ones made on my Amiga, there are totally different...