sjuktstarkgrogg wrote:I hear some mixed opinions whether it's better to do it directly on an Atari Emulator on PC and then test them out on the machine or do the entire coding on the Atari ST.

What's "better"? Only you can say that. Sure, it's "better" (faster, easier) to code everything using vasm or gcc or whatever with Eclipse on top and some emulator for debugging. But is it more fun? You'll have to figure that out yourself. Personally I enjoy doing it the old school way. However, I do cheat: Back in the day when I was playing around with DEGAS, STOS, Devpac etc I only had a single computer with 1Mb RAM and a single floppy. Now I have 12Mb RAM, mass storage and graphics card which speeds up the process considerably. However, if I had more money I could have had the same setup in 1990 so I don't feel bad about it

Wow! Do you actually have 12Mb of RAM for your ST? I thought 4Mb was the maximum!? (I just ordered myself a 4Mb upgrade for my STe)You have a good point actually, I completely see the immense charm of creating everything on that good old hardware and just make it run.. I've been creating chiptunes on old game consoles for a good while and I only compose on real hardware! One of the biggest obstacles for me is time, so I'd really want to be able to get to know demo-coding when I'm stand by at work or when I have a couple of hours to spare during the evenings... I carry my laptop with me everywhere, so it's probably gonna be on that one I start out learning how to code for the ST. Then I could take out my great STe during the weekend and try out my code on it.

Do you work with a SD solution such as Ultrasatan for cross platform demo programming ?...or how do most of the demo creators out there approach demo programming in 2017 ? - Cause I bet I'm not the only one that don't have the luxury of being able to code on real hardware everyday(?).

I have two machines with MonSTer cards, one Mega and one STE. Both have 8Mb alt-RAM in addition to the original 4Mb. The STE also have an ET4000 graphics card. In addition to the 8Mb alt-RAM the MonSTer card also has flashable TOS-ROMs and two IDE interfaces. I use IDE->SD adapters in both these machines. With Hatari on Linux I can simply move the SD-card from the Atari to the laptop and use it as a disk in Hatari. Not sure if this is possible with Windows - I remember trying it a few years ago but could not find a way to do it.

Does someone knows which options to use with vasm to assemble DRI linkable object files that can be linked by Pure C to build an executable ?=> this means having an equivalent output to use of Devpac 2 with "program type = DRI linkable"

metalages wrote:Does someone knows which options to use with vasm to assemble DRI linkable object files that can be linked by Pure C to build an executable ?=> this means having an equivalent output to use of Devpac 2 with "program type = DRI linkable"

vasm (vlink) supports Atari DRI but only for executables. You can always contact Frank and ask him for separate object files support, there's non-zero chance he will do it for you.

metalages wrote:Does someone knows which options to use with vasm to assemble DRI linkable object files that can be linked by Pure C to build an executable ?=> this means having an equivalent output to use of Devpac 2 with "program type = DRI linkable"

vasm (vlink) supports Atari DRI but only for executables. You can always contact Frank and ask him for separate object files support, there's non-zero chance he will do it for you.

Ok Franck told me it would be no problem to add support for dri if he had the dri specs which is not the case. Do you know if someone has that or if people who have developed devpac or pure c can be contacted ?

metalages wrote:Ok Franck told me it would be no problem to add support for dri if he had the dri specs which is not the case. Do you know if someone has that or if people who have developed devpac or pure c can be contacted ?

Best you can do is to compile a few object files with various elements (external references, symbol names etc) and send them to him. It wont be a quick process but we have together debugged many things like that -- where do you think Atari / FreeMiNT support comes from. :)