Oh no! Where's the JavaScript?
Your Web browser does not have JavaScript enabled or does not support JavaScript. Please enable JavaScript on your Web browser to properly view this Web site, or upgrade to a Web browser that does support JavaScript.

EmuV0

Last updated on 2 days ago
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 10 days ago
deadwood will always have to be used from Shell, or is integration into AROS planned for the future?

On AROS One, I will see if I can create a small script so that the user only needs a simple click to start 32-bit applications.

Of course, Hollywood applications that still do not work well will not be included in the distribution.
D
deadwoodAROS Dev
Posted 10 days ago
I was thinking about tigher integration earlier, but I don't know if it makes sense anymore, so scripts are the way to go for now. Definatelly nothing will change with that for the next 3-6 months. I might revisit that in future - hard to say.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 10 days ago
OK, thank you, I just wanted to understand!

At the moment, as mentioned previously, Emuv0 does not work well with the native VMware video card. A solution to this problem is expected.

I noticed a strange problem with the Hollywood programme ‘Calendar&Clock’. The first time you run it, it works fine, but if you run it again, exit from the programme you get the error shown in the screenshot.
You do not have access to view attachments
N
ntromansSenior Member
Posted 9 days ago

AMIGASYSTEM wrote:

@AMIGASYSTEM - deadwood will always have to be used from Shell, or is integration into AROS planned for the future?

On AROS One, I will see if I can create a small script so that the user only needs a simple click to start 32-bit applications.

Of course, Hollywood applications that still do not work well will not be included in the distribution.
#

From the shell you can just set an alias in user-startup, e.g.

alias hw emuv0-pc hollywood:system/hollywood

From any shell you can then just use the alias with any necessary arguments, e.g.

hw -compile "ram:test" -exetyoe "AROS" ram:test.hws

For Wanderer, I haven't tried this yet but I think it should work:

  • Convert the program's icon into a project icon.
  • Set emuv0-pc as the tool
  • Set the CLI tooltype


As mentioned I haven't actually tried this yet and I'm not sure how other tooltypes will be handled, but I'll give it a go tonight.

Cheers,
Nigel.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 9 days ago

ntromans wrote:

@ntromans

From the shell you can just set an alias in user-startup, e.g.

alias hw emuv0-pc hollywood:system/hollywood

From any shell you can then just use the alias with any necessary arguments, e.g.

hw -compile "ram:test" -exetyoe "AROS" ram:test.hws

For Wanderer, I haven't tried this yet but I think it should work:

  • Convert the program's icon into a project icon.
  • Set emuv0-pc as the tool
  • Set the CLI tooltype


As mentioned I haven't actually tried this yet and I'm not sure how other tooltypes will be handled, but I'll give it a go tonight.

Cheers,
Nigel.

On AROS One, I want to prevent users from using the Shell, as some users may not be experienced in using it, and it can be cumbersome.

The best solution is to run it directly from the icon on the Wandarar, practically in a transparent way where the user simply has to click.

Setting CLI in Tooltypes is not good because, as mentioned, some apps may require many parameters. The best solution is to use a normal ‘WB’ Project Icon with the c:IconX tool. See the short video example attached:

https://www.youtu...Y1URwXRWb0
N
ntromansSenior Member
Posted 9 days ago

AMIGASYSTEM wrote:

@AMIGASYSTEM -

ntromans wrote:

@ntromans

From the shell you can just set an alias in user-startup, e.g.

alias hw emuv0-pc hollywood:system/hollywood

From any shell you can then just use the alias with any necessary arguments, e.g.

hw -compile "ram:test" -exetyoe "AROS" ram:test.hws

For Wanderer, I haven't tried this yet but I think it should work:

  • Convert the program's icon into a project icon.
  • Set emuv0-pc as the tool
  • Set the CLI tooltype


As mentioned I haven't actually tried this yet and I'm not sure how other tooltypes will be handled, but I'll give it a go tonight.

Cheers,
Nigel.

On AROS One, I want to prevent users from using the Shell, as some users may not be experienced in using it, and it can be cumbersome.

The best solution is to run it directly from the icon on the Wandarar, practically in a transparent way where the user simply has to click.

Setting CLI in Tooltypes is not good because, as mentioned, some apps may require many parameters. The best solution is to use a normal ‘WB’ Project Icon with the c:IconX tool. See the short video example attached:

https://www.youtu...Y1URwXRWb0


Yes, I've been experimenting and it looks like there's no simple way to do it. I was hoping you could 'force' the required parameters into the icon via a little Hollywood program but it seems whilst it can read parameters it cannot set them. Processicon did a bit better but as you have mentioned the icon refused to convert to a project one.

Cheers,
Nigel.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 9 days ago
On AROS 32/64, you cannot modify/force a project icon on an executable file.

This is both good and bad. AROS uses an automatic feature that adapts the icon to the file, whereas on Amiga OS you can do this yourself.

My method is the most natural one used in the Amiga environment!
N
ntromansSenior Member
Posted 9 days ago

AMIGASYSTEM wrote:

@AMIGASYSTEM - On AROS 32/64, you cannot modify/force a project icon on an executable file.

This is both good and bad. AROS uses an automatic feature that adapts the icon to the file, whereas on Amiga OS you can do this yourself.

My method is the most natural one used in the Amiga environment!


I've just found a way to dio it - use an AmigaOS3 icon. I copied one of my AmigaOS def_ icons to becomr the icon for a 32 bit program (a Hollwood one) and it stayed a project icon. With a tool of emuv0-pc and tooltype cli, the program launced immediately from the icon. So, if you don't need any other toolytypes., this is a neat way to do it.

Cheers,
Nigel.

P.S. I may have a solution to use tooltypes too, but that remains to be tested.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 9 days ago
Check the icon properties carefully because it is impossible for AROS on a binary to have a design icon.
Bear in mind that I create my icons on Amiga OS 3.9 BB4 AfA OS and they are all native designs, but then on AROS they are
transformed according to the file type.
N
ntromansSenior Member
Posted 9 days ago

AMIGASYSTEM wrote:

@AMIGASYSTEM - Check the icon properties carefully because it is impossible for AROS on a binary to have a design icon.
Bear in mind that I create my icons on Amiga OS 3.9 BB4 AfA OS and they are all native designs, but then on AROS they are
transformed according to the file type.


Try the attached zip...

Cheers,
Nigel.

P.S. I couldn't find anything on AROS 64 bit which would set the icon image, I had to go back to good old IconEdit on OS3.1.
You do not have access to view attachments
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 9 days ago
Okay, yours is an old Amiga Glow Icon, which is different from the modern, multicoloured DualPNG icons. With DualPNG icons, you cannot associate a Project icon with a Binary.

Even native AROS icons allow you to use a Project icon for Binaries. I cannot explain why this is not possible with DualPNG icons.
N
ntromansSenior Member
Posted 9 days ago

AMIGASYSTEM wrote:

@AMIGASYSTEM - Okay, yours is an old Amiga Glow Icon, which is different from the modern, multicoloured DualPNG icons. With DualPNG icons, you cannot associate a Project icon with a Binary.

Even native AROS icons allow you to use a Project icon for Binaries. I cannot explain why this is not possible with DualPNG icons.


Yes, as noted I needed to use AmigaOS IconEditor to make it. So the choice is full colour icons but needing an extra script or lower colour icons that work directly.

Cheers,
Nigel.

P.S. It struck me that the choice of icon for Hollywood is clever - the black and white clapperboard looks good in all icon formats.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 9 days ago
Okay, I have my own set of icons that I created myself. Furthermore, DualPNG icons have an attractive and modern look, and you cannot use icons created by others in a distribution without proper authorisation!
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 9 days ago

AMIGASYSTEM wrote:

@AMIGASYSTEM - OK, thank you, I just wanted to understand!

At the moment, as mentioned previously, Emuv0 does not work well with the native VMware video card. A solution to this problem is expected.

I noticed a strange problem with the Hollywood programme ‘Calendar&Clock’. The first time you run it, it works fine, but if you run it again, exit from the programme you get the error shown in the screenshot.


If you run it twice, you get the same error with the ‘Omanko’ application.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 8 days ago
@ntromans

I made a short video showing how AROS behaves with DualPNG icons. In the video, you can see that OS3.2 also has some problems with DualPNG icons.
You do not have access to view attachments
D
deadwoodAROS Dev
Posted 7 days ago
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 6 days ago
Omanko and Calendar&Clock Ok work well

ZuPaPlayer crashes when you press the Stop button, freezing the system and sometimes even VMware.
D
deadwoodAROS Dev
Posted 6 days ago
I know about ZuPaPlayer issues. Best to remove that software from distribution.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 6 days ago
OK, I'll remove it from the ZuPaPlayer distribution. It's a shame, as it was the only MOD player that could be used as a tool in the Mod File Icon Tooltypes.
AMIGASYSTEMAMIGASYSTEMDistro Maintainer
Posted 4 days ago
LilCalendar crashes if you try to change the colours in the Palette. Furthermore, if you set the mode to ‘Limpid’, it cannot be dragged so that you can save it in the desired position.
You can view all discussion threads in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot start on a poll in this forum.
You cannot upload attachments in this forum.
You cannot download attachments in this forum.