Welcome, Guest. Please login or register.

Author Topic: AROS Status Update  (Read 3948 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show only replies by unusedunused
Re: AROS Status Update
« Reply #14 from previous page: November 22, 2005, 04:50:32 PM »
Thanks the installer work very good.I hope i get ok that the afa upload can change to lha,then i upload a new archive

But text is better change to that.when start in user-startup then new picture.datatype does not work

(set #startup "Do you want to add the required \"C:AfA_OS_Loader\" to your \"S:User-Startup\"?\n\n")
   (set #startup2 "If you run into any problems with the AfA_OS_Loader,or want use new picture.datatype try and ")
   (set #startup3 "move it to \"S:Startup-Sequence\", right before IPrefs and remove it from User startup.")
 

Offline fx

  • Sr. Member
  • ****
  • Join Date: Mar 2002
  • Posts: 347
  • Country: se
  • Gender: Male
    • Show only replies by fx
    • UHC Tools
Re: AROS Status Update
« Reply #15 on: November 22, 2005, 05:25:44 PM »
okay, I will change the text to say that right away! also if someone want to translate the current strings used in the installer to other languages that would be great, here is a textfile with the current strings.
Slightly bored and severly confused..
 

Offline Amigaz

  • Hero Member
  • *****
  • Join Date: Feb 2004
  • Posts: 1959
  • Country: se
  • Gender: Male
    • Show only replies by Amigaz
Re: AROS Status Update
« Reply #16 on: November 22, 2005, 09:00:10 PM »
It has stopped working here, it causes ramlib errors when executing programs and I get crashes when booting
Hope future releases will work better with other patches like for example Amiga Theme Experience which I'm using.
-------------------------------------------------------------------
Amiga 4000T - A3640 '040
Amiga 4000 - CS MKIII
Amiga 1200 - Blizzard 1230 MKIV
Amiga 1200 - Stock
Amiga CD32 - TF360
A bunch of ol' A500's
 

Offline jmbattle

  • Sr. Member
  • ****
  • Join Date: May 2005
  • Posts: 324
    • Show only replies by jmbattle
    • http://www.amigainabox.co.uk
Re: AROS Status Update
« Reply #17 on: November 23, 2005, 12:32:28 AM »
Wow, great stuff - antialiased fonts working well on my AIAB setup!

I had to disable the picture.datatype library as my truecolour backgrounds were not displaying correctly, however everything else is great!

Two questions - what is the distribution status of this package?  Would it be possible to use the truetype font rendering (and more) within the AIAB package?

Also, how might one add more TTF fonts?  I have attempted to use the ttf.library preferences manager to generate .otag and .font files, but no luck.

Cheers,
James
 

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show only replies by unusedunused
Re: AROS Status Update
« Reply #18 on: November 23, 2005, 12:38:25 PM »
>Hope future releases will work better with other patches like for example Amiga Theme Experience which I'm using.

For the ramlib error i guess it is a stack problem.every new complexer function patched or not need more stack.
If a program have stack set too low then you get crashes randomly.
If the coder of prog have set the stack to default 4096 bytes then risc is high that problems happen.
increase stack with the shell command help not on all programs.

On aminet is a tool stackattack.
This increase every stack when start early on startup-sequence.(stackattack addstack 1000) add 1000 bytes more stack
later AFA OS work with AROS execlibrary this is done intern.
The minimum stack is then set to 5000 bytes.
also many funcs do a verify that no illegal structure pointers are used and stop the program before it run amok.

But now problem is AROS use on same offset number that Kick3.1 have function exitintr a fnction    

I think there is no hope when you only wait for new versions.only with a more precise report i can look what happens because it is impossible to fix a
bug that i cant reproduce or the user can tell me whats wrong.Also i found out that it is important,that do NOT start
afa loader with run >nil:

when you send me your startup sequence and other tools you boot then i can make a install and look what happen
or maybe i see on startup-sequence whats wrong.


The status of AFA currenty is:

I have fixed now displaying 256 color images on true color screens ,in next release it should work in aiab.
also next release have a AA speedup and a slider to choose optimal AA settings.

Full Antialiasing give most time blur fonts no AA give pixelize fonts.you can then choose with a slider between it
also less AA give more speed.On 040 i remember a multiplication take 10 cycles an 060 it take 2 cycles.every pixel
take 3 muls so reduced AA give here lots speed increase too(i hope)

I release that next weekend

To make fonts you need a fontmanager that generater the .otag and .font file.This fioels can generate and use from MOS and AROS

I have done a project for the fontmanager from aros.but cant compile for 68k.MUI code is for me a mess,
because hooks are on every system diffrent.maybe a MUI expert can do that.the source have 2300 lines
In german anews Holger write he look for it(link from senex).maybe he get it working