Re: Who actually started adding the .exe extension to Amiga programs?
category: offtopic [glöplog]
I've wondered the same. I think it's maybe users wanting to mark the executables same way as with Dos.
Linux wasn't a popular thing when Amiga was still relevant for larger audience, so maybe people were not used to permission bits like nowadays. I mean people of course used Unixes in universities etc. but it was not popular at homes. But it's just my theory, would be great to hear other takes on this.
And sorry, I've been using too much Slack. In Slack you can start forum threads directly from oneliners. It's pretty cool.
Linux wasn't a popular thing when Amiga was still relevant for larger audience, so maybe people were not used to permission bits like nowadays. I mean people of course used Unixes in universities etc. but it was not popular at homes. But it's just my theory, would be great to hear other takes on this.
And sorry, I've been using too much Slack. In Slack you can start forum threads directly from oneliners. It's pretty cool.
Maybe one could decrunch all archives in scene.org and find the earliest use of .exe ? Not sure how to find out the earliest use. For me it was always to make it easy to see which one in this jumple of files is the one that runs the demo. Sometimes you'd get tripped and there would a script with some assigns and other stuff that you should have run instead though.
Hey hot multimedia. Thanks for picking the topic up here. You‘re probably right. Let‘s see if we find out here.
wasnt it also a thing on AMIGAAA to put the extension in front of the filename?
mod.obviously
Lots of modules were named mod.*.*
But I think it was merely a convention, OS didn't specify anything about them
While we're at it... who invented the ".xex" extension on Atari? And is it pronounced "zex" as my mind-voice renders it?
I always pronounce it the only good way the letter X can be
"ksehks". I will never agree for X being pronounced as "zee"... Also it's "zed-ecks", not "zee-ecks" for you spectrumers ;p
Anyway, I think it was invented for Altirra?
"ksehks". I will never agree for X being pronounced as "zee"... Also it's "zed-ecks", not "zee-ecks" for you spectrumers ;p
Anyway, I think it was invented for Altirra?
I pronounce "Xanadu" as "zanadu", so it'd be silly to pronounce the X any other way, at the start of a word or name.
I always hated the "mod.*" way of naming Amiga music modules, it was always a pain having to rename the file to put the .mod at the end, and programs that relied on filename extensions like TypeStats would be f'ed up by them, too.
As for MS-DOS-like filename extensions, I'm glad I use them now. They are a lot easier to determine what the file type actually is, and is not reliant on icons like AmigaDOS to determine what the file actually contains. Yes, I know the filetype information is stored in a header inside the file itself, but that's not much use when viewing the files in DOpus or something.
I always hated the "mod.*" way of naming Amiga music modules, it was always a pain having to rename the file to put the .mod at the end, and programs that relied on filename extensions like TypeStats would be f'ed up by them, too.
As for MS-DOS-like filename extensions, I'm glad I use them now. They are a lot easier to determine what the file type actually is, and is not reliant on icons like AmigaDOS to determine what the file actually contains. Yes, I know the filetype information is stored in a header inside the file itself, but that's not much use when viewing the files in DOpus or something.
Wouldn't .hunk be more suitable for Amiga's executable files? Also .CMD would be less associated to Microslop (and more associated to CP/M ...even though also Windows uses it for batch files).
I vote for .runme
.runmebabyonmoretime
Would be super interesting to draw a function of time graph on how many releases there are every year that have an .exe on the .adf. Wish I had time for everything. Also sounds like an icky crawling job to get the data.
Quote:
Also sounds like an icky crawling job to get the data.
1. Get the prods metadata from data.pouet.net
2. Get the actual data by rsyncing from pouet-mirror.sesse.net
3. You now have the data
I've collected over a thousand Amiga demos from the early days of the platform, all three chipsets and from 68000-68060, and I can filter them by their use of ".exe" as a search parameter. Give me a day, and I'll have link lists you can browse through at your leisure posted here. As I've just checked, there are hundreds.
