@Franko

060/50

i must note that aros exec is still four times slower as 3.1 exec on the same machine, at least what concerns the memory operations.

Last edited by wawa on 04-Apr-2013 at 04:21 PM.

@klx300r

Hey :) Thx for the interest in AspireOS.

Just released update 5 to codename:Revelation

www.aspireos.com

Direct link:

https://sites.google.com/site/arosaspireone/download-1/AspireOS_Revelation_Update5.zip?attredirects=0&d=1

Quote:

nikosidis wrote: @klx300r Hey :) Thx for the interest in AspireOS. Just released update 5 to codename:Revelation www.aspireos.com Direct link: https://sites.google.com/site/arosaspireone/download-1/AspireOS_Revelation_Update5.zip?attredirects=0&d=1

btw, this should be a news item here (unless i missed it?)

Last edited by klx300r on 04-Apr-2013 at 05:11 PM.

_________________
____________________________
c64-2sids, A1000, A1200T-060@50(finally working!),A4000-CSMKIII
! My Master Miggies- Amiga 1000 & AmigaOne X1000 !
mancave-ramblings
X1000 I BELIEVE

@wawa

you mean you tested the newest nightly Aros 68k and it is now twice as fast? Do you think it is worth to update Aros Vision to it? Or to create a new "light" version with Scalos as workbench replacement instead of wanderer? And what should be included there as a minimum? I use Ken Icons. Can I use them and are they shown correctly on real hardware?

@OlafS25

ive tested last nightles and so far i can tell its worth to update. you can compare for yourself, maybe the os is not 2x times faster in general, but it feels faster and membench confirms that new exec is 2 tims as fast in mem operation.

@wawa

Sounds like a real progress. I could (at least) create a "light" distribution for real hardware with minimum components. What should I include? And can I use Kens Icons? Are they shown correctly?

I used glowicons in the past (that looked not so good as kens icons)

Last edited by OlafS25 on 04-Apr-2013 at 10:09 PM.

@OlafS25

on rtg ken icons show correctly, i dont have aga attached just now but i suppose they are just color reduced. those which have blue unnecessary background are signed for instance "pzyco&sanny". anyway you can check for yourself under uae, you dont need a real amiga for that.

i dont exactly knwo what you need to include, have you included working selection of aros contributions? there is a number things that work, games, demos, network stack i believe, owb (i must check again)..

also as soon as time permits i will try to recompile gtk>mui, and some goodies, lets see how that works. but in general i would keep the light version snappy. especially try not to add ttf fonts at the moment.

@wawa

Quote:

wawa wrote: @Franko 060/50 i must note that aros exec is still four times slower as 3.1 exec on the same machine, at least what concerns the memory operations.

Hmmm... need to give it a wee try again on my Blizzard060/60Mhz to see how it compares to last time...

Hope they've sorted out the problem I was having though with it only loading the AROS kickstart image into chipmem though...

_________________

@Franko

Quote:

Hope they've sorted out the problem I was having though with it only loading the AROS kickstart image into chipmem though...

this have been sorted out long time ago afair.
now wait a little, lets see if krzysztof will be able to optimize a bit more.

@wawa

I will try to create a "classic" distribution this weekend. When someone wants to use RTG what does he need to do? Install Picasso96 completely or only parts of it?

@OlafS25

you have to add the p96 display drivers behind the bootstrap command, usually both *.chip and *.card file (along with a patch to them of course). that means it is alas very config specific. you could create some choice of startup sequences for most popular p96 supported zorro cards, or an installation script to modify the startup sequence either after recognizing a card or by manual choice (if you are able to do that, me probably not). i think this is nevertheless a temporary solution and may be replaced by by one more amigalike (sort of monitors) or autosensing at some point.

i will send you my s-s as reference later.

@wawa

ok thanx. I will do the first version this weekend. How many MB should it have (as ZIP) max?

@OlafS25

not more than 100 imho. when you tell the users they need 200mb for aros install, they start to complain how small 3.1 install was. they hardly realize what kind of goodies aros brings and also that a contemporary browser may easily be more than 10mb as executable. people may need to accustom slowly and be let discover the full advantages later on. initially its good to stick to essentials as much as possible.

I agree 100%

What prevented me to try AROS 68k much was that file size. It to ages to download, unpack and install.

With a beta OS like AROS, you will need to install, update quite often.

I also think that people that like to try AROS 68k know about Amiga and what they want regarding programs and games. At least additional packages should be made for those who want them, just like I did games in a seperate archive.

If possible you should try to make a version that have almost no programs in it and even take away stuff in the night builds like development tools. If you could get the file size below 50MB it would be great I think. This would at least give people a hint of if it runs or not and if their favorite amiga 68k software works at all with it.

Last edited by nikosidis on 05-Apr-2013 at 03:53 PM.

@nikosidis

50 MB is very low, but I will see what I can do. I will use a nightly and cut it down as far as possible. I think (as minimum) I would like to preinstall Scalos to replace Wanderer, integrate the new icon.library and include my (old) Glowicon-Set. And then I will see how much it is.

@nikosidis

yeah, id separate out all that parts, apps, libs, classes that are not updated anymore (most genuine amiga applications, many legacy mui classes and so on. these should be an optional download, that will be only necessary to download once. and this will be the essential part of the size of the distro. whatever is still updated is essentially the aros nightly, perhaps a part of the contrib and maybe few mui classes that are not included, those should be bound together ar a regularly updated core download.

for instance, what i do is i have a setup with many preinstalled genuine amiga 68k programs and overwritel it regularly with the content of new nightly, it doesnt affect those third party elements. i leave out startup sequence i have slightly modified to support my rtg, sometimes i enable things like decoration, user startup stays unaffected, and there is one mui setting i have to correct just by opening zune prefs and saving them.

thats all.

@wawa

my distribution is a little more complicated because I have heavily mixed AROS 68k and additional 68k components, partly replacing AROS 68k components (not many but some).

Last edited by OlafS25 on 05-Apr-2013 at 04:10 PM.

@OlafS25

I guess Wawa can help you with what you need to include and what you don't need. Just like Wawa said you should update with the MUI stuff that AROS don't have or is buggy etc. and take away what is not needed. ScaleOS as replacement to Wanderer and your selected iconset sound like a good idea.

Last edited by nikosidis on 05-Apr-2013 at 04:11 PM.

@OlafS25

olaf im sorry but you need to painfully keep track (list) of of your changes, otherwise you ll get lost. shouldnt be really problem for whole apps, as well as particular elements added. the bisggest problem are probably the icons, as they are all over the place.

not the size is importynt just now but (as this is a user distribution) order and dependability. when you have a list give it to me, ill make suggestions, then give mi the distro and ill test it.

@all

I have a first working version. Included is Scalos (preinstalled) and all what is needed for it. Icons are partially replaced with Glowicons. Additionally I have included Wazp3D. What should I add for minimum?

Below are 2 screenshots (RTG and PAL)