To be picky, in the middle of 80s only the original Amiga existed and it was expensive. If you were young and had access to one, you typically obtained it through work, like you sold software before or had a small company with some kind of income. Around 1987 the Amiga 500 arrived.

The devs I knew at the time (me included) expanded the memory very early, typically to 2-4MB. The rest with 512K (few with 1MB) typically played games or ran existing software.

When the Amiga 2000 become more common (late eighties) there were 8MB memory boards for them.

Smaller software development could be done in 1MB and perhaps even 512K, but anything demanding required more memory. I did some simple assembly programming (not demos) in 1MB or less, but expanded memory to a couple of MBs in 1988 when I went for more demanding C programming.

I never even image that hw requirements were so high for that machine, mostly around '87. I had my 512KB fast ram expansion on 1990/91 and I never heard about Amiga with more of 1MB
BTW after knowing this fact I must reconsider everything about assembling even a simple demo

I'm trying to load some Coppershade demo (ex. tut30.s) that include resources which take up > 500 KB.

Tut30.s doesn't include any resources >500 KB!

Quote:

Originally Posted by fstarred

When compiling with asm one

Assembling you mean!

Quote:

Originally Posted by fstarred

my reserved workspace run out of memory; my system is A600 with 1MB of Ram, and when Asm one starts I can only increase the workspace storage up to 550 KB.

I can assemble Tut30.s on a bog standard 1 MB A500 using just 100 KB work space (ASM-One V1.05).

Quote:

Originally Posted by PeterK

Asm One seems to be a memory eater, it takes about 500 KB for itself.

And your assumption "seems to be" wrong! You should at least say which ASM-One version are you referring to! ASM-One 1.05 leaves 736K work space on a 1.3 A500 with external drive attached! That's definitely not using 500 KB for itself and hardly "memory eating" at all.

And your assumption "seems to be" wrong! You should at least say which ASM-One version are you referring to! ASM-One 1.05 leaves 736K work space on a 1.3 A500 with external drive attached! That's definitely not using 500 KB for itself and hardly "memory eating" at all.

Ok, I never use Asm One, but v1.48 is installed on my WinUAE OS 3.9 system with lots of memory. I did an "avail flush", started Asm One 1.48, it opened on a 800x600x2 screen, and then another "avail flush". The memory consumption was 10.6 MB and Asm One offered me a workspace of 10.000 kB. 117 kB are required for the screen.

Ok, I never use Asm One, but v1.48 is installed on my WinUAE OS 3.9 system with lots of memory. I did an "avail flush", started Asm One 1.48, it opened on a 800x600x2 screen, and then another "avail flush". The memory consumption was 10.6 MB and Asm One offered me a workspace of 10.000 kB. 117 kB are required for the screen.

800x600 screen is not a default setting and seeing that the thread starter works on an A600 with just 1 MB memory the newer ASM-One incarnations are not really suitable. They do need more memory but also offer a lot more features than the early versions. The early versions (up to 1.25 if memory serves me right) can be easily loaded from disk, work on 1.3 machines and allow to do stuff on 1 MB machines pretty easily.

Quote:

Originally Posted by meynaf

Are there configuration items that can change the used memory in a significant manner ?