@Dwyloc
Quote:
If you mean the graphics corruption on the Sam boards, that was caused by an uninitialized hardware register. It had nothing to do with slowing down graphics.

@salass00
I think you should email joerg directly.

@phoenixkonsole
Quote:
That's great news.

@kolla
Quote:
That is incorrect. It is a new shell.kmod (minor fixes), console.device.kmod, con-handler.kmod and a new Console prefs program if you want to be pedantic about things.

Quote:
Collectively many just label it "The Shell" and it doesn't hurt much from an end user point of view.

@ChrisH
The X1000 and the Sam460ex were both running beta flavours of AmigaOS 4.1 with all sorts of features enabled which have not shipped yet.

I suppose you could say it was a "leak" but if we really wanted to keep it all secret the boxes wouldn't have been running a beta versions. Nice to see some people were paying attention.

Underneath, the OS has been improved as well but those changes are always much more difficult to visualize like the USB 2.0 support.

@ChrisH
Quote:
There are lies, damned lies and statistics.

@Mrodfr
I think we all realize you are excited but please do some research before asking questions and trust the developers to do the right thing.

@all
We really don't need to tell Rogue and Hans how to do their jobs so lets leave the AROS stuff to aros-exec.org from now on. Thanks.

@amigakit
Moved to Amiga General forum (it always shows on the front page).

@ChrisH
There was a lot of important news and road map info. that seems to have been completely missed.

I plan to rectify the situation in the next couple of days with a show report.

@djrikki
Great effort!

I love to see people putting in the effort instead of just talking about doing things. Kudos.

@Mrodfr
Did you try sending an email to ACube?

@fingus
Quote:
Compositing per se does not consume memory. The 3D eye candy effects consume the memory due to the way the layers (i.e. windows) are implemented. I can utilize the underlying IGraphics->Composite() function without having the 3D effects active at all. They are not one in the same.

Blaming "compositing" for memory issues is a common misconception started by the GUI prefs labels. The GUI prefs have since been rearranged and relabeled to try and remedy this misconception.

@samo79
A very good way to kill a software project is with bad communication. This one is not off to a good start if you hope somebody will communicate with you when you have their direct email address handy.

http://www.it-cortex.com/Stat_Failure_Cause.html
http://www.projectperfect.com.au/info_it_projects_fail.php
http://www.slideshare.net/bstaud/six- ... ject-failure-presentation
http://www.networkcomputing.com/data- ... to-it-project-failure.php

and on and on.

Next time, just email the guy.

@fastbit66
I think you should email ACube and ask them directly.

@samo79
Why not email joerg directly and ask for the sources?

@TSK
Note you can check application IDs with Ranger as well.

@jahc
Congrats! I'm looking forward to what you do with the Amiga SDK on that new box...

@MickJT
Quote:
I think you worry too much...

@Chris
I just uploaded a new version of ListDynDep to OS4Depot. It will now print the SONAME along with the dependencies. This should make it a bit easier to figure out which files will be picked up by your executables.

Please let me know if you find it useful.

@angelheart
I have a copy of Amiga Programmer's Guide to ARexx here. I'm the original owner and it is in very good shape. Maybe we can make a deal. I'm sending you a private email.