It's what Mazze said:

"Vice doesn't evaluate the Workbench message. This means we need another approach."

You need to wait for Paolo to customize PoorX to work as a middleman between T64 and Vice.

OK, I updated to the latest nightly and I see the D64 file with a commodore logo now, YAY !
But clicking on it only starts VICE, autostart parameter does not seem to be fed to VICE.
Can anybody else test ? Is someting "fsked" up in my instalaton ?

Quote:

Ahahaha! GREAT! Ours is the first operating system that includes a official descriptor for C64 tape and disk images.

Haha Great, I sure will do that. I guess I have to wait until next nightly is released though.
:cheers:Thanks for the fix!

Quote:

Ah, great.

Quote:

I've added a datatype descriptor and an icon for D64/T64 files. Now you can fiddle

Quote:

That's why here at Icaros we have the PoorX tools. ;)

A PoorX tool is basically a C executable you can bind filetypes to. Their only goal is to take the path and the file name of the icon you bi-clicked, and pass it to a env variable, than call a shell script. This way I can easily write ONE scripts that does this:

- read the variable contents
- launch vice with a line like
vice:x64.exe $variable

That's not the only option. We have also a PoorX version that can use two variables: the path+filename one, and the extension. So I can create a script that, as like as PoorArcX does, launches the right emulator depending on the extension. But this would be an issue when more emus use the same extensions (a .d64 file can store Commodore 16 datas as well).

Icaros use PoorX also to open HTML files on disk with OWB, used it for opening PDF files, and so on. It was even used with the first release of MPlayer: since it couldn't open yet files directly, there was a PoorX helper. Even newer AmiBridge use it. I won't ever thank Krzysztof Smiechowicz enough for this wonderful piece of code, which helped me a lot, when you couldn't launch AROS script files with arguments.

@aerosaros
I don't believe it could. Maybe even a lot of Atari diehards would neglect Aros because it having Amiga roots

But I belive we as AROS users would love having datatypes for a lot of emulators just because it makes it easier to fiddle around with AROS. Isn't that what we really do at the moment (as users) fiddle around ? Trying to see if we can do in AROS what are used to do in Windows.

Do you think AROS could attract atari fans with an integrated atari emulator and C64 fans with an integrated C64 one?

Vice doesn't evaluate the Workbench message. This means we need another approach.

One has to create a script for every D/T64 file.
The content of the script is then something like
"vice:x64.exe <name of image>"

This scripts must get an icon with the default tool "c:iconx".

Quote:

Clarification for point 1: I was talking about AROS source tree path, not directories inside Icaros ;)