Need some help remembering (Amiga development environment related)

  • Thread starter Thread starter Boing3000
  • Start date Start date
Click For Summary

Discussion Overview

The discussion revolves around recalling a specific development environment for the Amiga computer, particularly one that was used after Commodore's demise. Participants share their memories and experiences related to the software, its features, and its performance, while seeking assistance in identifying it.

Discussion Character

  • Exploratory
  • Technical explanation
  • Debate/contested

Main Points Raised

  • One participant describes a development environment that resembled a frontend for gcc, generating object-oriented assembly similar to .NET runtime and MSIL.
  • Another participant shares their experience of using an 8086 C compiler on an Amiga, noting the slow compilation times and the use of emulation software.
  • There is a suggestion that the assembly code seen by the original poster was likely Motorola 68000 op codes, given the Amiga's architecture.
  • A later reply mentions the use of a RAM disk and questions the necessity of using an emulator for C development on the Amiga.
  • One participant recalls that the development environment included a Java bytecode interpreter that translated to their VPASM, which was reported to run faster than Java's own runtime.
  • Another participant expresses nostalgia and mentions the difficulty in finding the SDK online, suggesting it may be lost in their basement.

Areas of Agreement / Disagreement

Participants express varying recollections and interpretations of their experiences with the Amiga development environment. There is no consensus on the specific software being discussed, and multiple perspectives on the technical aspects and historical context are presented.

Contextual Notes

Some participants reference specific technical details and experiences that may depend on individual setups and configurations, leading to potential misunderstandings about the software's functionality and performance.

Boing3000
Gold Member
Messages
332
Reaction score
37
I was trying to remember some days ago, of a developing environment I installed once my Amiga back in the day.
It was after Commodore demise, and I remember to have been quite impressed.
The vague souvenir I have, is its looked like a frontend on gcc that generate some kind of oriented object assembly, not unlike .NET runtime an msil nowadays.
There was some nice demo bundled within it, a a quite impressive graphic stack.

If only I could remember the name !

Any hint would be greatly welcomed... thanks
 
Technology news on Phys.org
Boing3000 said:
I was trying to remember some days ago, of a developing environment I installed once my Amiga back in the day.
It was after Commodore demise, and I remember to have been quite impressed.
The vague souvenir I have, is its looked like a frontend on gcc that generate some kind of oriented object assembly, not unlike .NET runtime an msil nowadays.
There was some nice demo bundled within it, a a quite impressive graphic stack.

If only I could remember the name !

Any hint would be greatly welcomed... thanks
I had an Amiga back around '86. I did some C development on it, using an 8086 C compiler together with emulation software running on a 5 1/4" floppy (no hard drive on my machine). It was painfully slow, taking at least a minute to compile and the simplest C programs.

If you were seeing assembly code in your dev environment, I'm fairly certain that what you were seeing was Motorola 68000 op codes, as the underlying processor on the Amiga was the Motorola 68000 (and on later models, the Motorola 68032, I believe).
 
Boing3000 said:
I was trying to remember some days ago, of a developing environment I installed once my Amiga back in the day.
It was after Commodore demise, and I remember to have been quite impressed.
The vague souvenir I have, is its looked like a frontend on gcc that generate some kind of oriented object assembly, not unlike .NET runtime an msil nowadays.
There was some nice demo bundled within it, a a quite impressive graphic stack.

If only I could remember the name !

Any hint would be greatly welcomed... thanks
You're probably better off asking this question on an Amiga user's group website.

This wiki article might give you some tips about the various Amiga user's groups still out there:

https://en.wikipedia.org/wiki/Amiga
 
SteamKing said:
You're probably better off asking this question on an Amiga user's group website.

This wiki article might give you some tips about the various Amiga user's groups still out there:

https://en.wikipedia.org/wiki/Amiga
A good night sleep have done the trick. It was called Elate / Taos
Thanks !
 
Mark44 said:
I had an Amiga back around '86. I did some C development on it, using an 8086 C compiler together with emulation software running on a 5 1/4" floppy (no hard drive on my machine). It was painfully slow, taking at least a minute to compile and the simplest C programs.
You should have used the ram: disk :wink: Anyway why bothering using an emulator ?

Mark44 said:
If you were seeing assembly code in your dev environment, I'm fairly certain that what you were seeing was Motorola 68000 op codes, as the underlying processor on the Amiga was the Motorola 68000 (and on later models, the Motorola 68032, I believe).
No. I was seeing exactly this
term.jpg

Those guys had written the 68000 jit compiler, because their run time had trouble finding a hardware host. The Amiga was a dead man walking, but with enough people interested in genuinely genius technology.
I remember one of their may "talking point" was that they had a java byte code interpreter that would translate it into their VPASM which was actually running faster on their runtime that on a java's one...

Anyway, now I am going to find it an re-install it. It's nostalgia time !:biggrin:

Thank you.
 
Boing3000 said:
You should have used the ram: disk :wink: Anyway why bothering using an emulator ?
In fact, I think I was using a RAM disk. I was using an emulator because I was using a C compiler that ran on PC's.
Boing3000 said:
No. I was seeing exactly this
term.jpg
What you are showing in the screen shot above is not assembly code - this is a listing of files in a directory. The terminal you opened is running Unix or more likely, the Amiga version of Unix. The "ls" command displays a list of files in a directory
Boing3000 said:
Those guys had written the 68000 jit compiler, because their run time had trouble finding a hardware host. The Amiga was a dead man walking, but with enough people interested in genuinely genius technology.
I remember one of their may "talking point" was that they had a java byte code interpreter that would translate it into their VPASM which was actually running faster on their runtime that on a java's one...

Anyway, now I am going to find it an re-install it. It's nostalgia time !:biggrin:

Thank you.
 
Mark44 said:
In fact, I think I was using a RAM disk. I was using an emulator because I was using a C compiler that ran on PC's
Of course. I meant at least the Amiga was already abler to emulate a PC. Now, it is the other way round :cry:
I suppose you only had this C compiler. A native one would have made you very happy !

Mark44 said:
What you are showing in the screen shot above is not assembly code - this is a listing of files in a directory. The terminal you opened is running Unix or more likely, the Amiga version of Unix. The "ls" command displays a list of files in a directory
I never said it was assembly. It is the console of that SDK with some APP running. It was already cross platform at the time, I had the Amiga version.
Here is some generic description if you like. The virtual assembly (VP2 I think) looked like this.
vp.jpg

This morning I read this nice "insider" story about the whereabouts of this company.
But I can't find the SDK online. Maybe the CD is rotting somewhere in my basement. I'll try to dig it out.
 

Similar threads

Replies
6
Views
4K
Replies
2
Views
3K
Replies
60
Views
18K
  • · Replies 5 ·
Replies
5
Views
2K
  • · Replies 7 ·
Replies
7
Views
3K
  • · Replies 2 ·
Replies
2
Views
3K
  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 4 ·
Replies
4
Views
3K
Replies
14
Views
4K