Welcome, Guest. Please login or register.

Author Topic: AROS Status Update  (Read 3954 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show all replies
Re: AROS Status Update
« on: November 21, 2005, 01:55:59 PM »
when above message come then you have not start the afa_loader.

download the archive from 20.nov this work without assign

BTW: If someone can write a installerscript and want help on AFA it is nice when he write a installer script.but currently you must copy files by hand

short install and test without risc is.(No files are overwritten)
copy in the afa_OS dir the fonts dir to your bootpartiton.
copy afa_os libs dir to your bootpartition libs dir
copy the dir afa_os_libs to your bootpartition.The folder ois create automatic when you do it from WB

no go in the dir c: of the afa OS archive.doubleclick on afa_loader.Now it should work.in fontreq there are Fonts vera mono Vera sans.This are truetpye fonts and work with antialiasing in every app.if something fail look on snoopdos what the loader want do

If you show in scout the libraries there should be another diskfont.library graphics.library with pri 1 in the system

If you want use AFA on startup then you can copy afa_loader to your c: dir and add in startup-sequence

in this sheme

....
c:adddatatypes
c:afa_loader   <-----new entry
c:iprefs
........

if your system really dont boot with AFA a left mousbutton hold on boot skip afa initialation.

also if you add
c:afa_loader MOUSESTART

then afa work only if you press and hoild down left mousebutton during boot
 

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show all replies
Re: AROS Status Update
« Reply #1 on: November 21, 2005, 05:04:04 PM »
Thats great if you can make a installer.Hope to get it working on your system
adding to startup sequence should only a option.maybe this can add later

Thanks for your precise report.Your file place look ok.

Have you use the afa_os_loader from that archive ?
 
AFA_OS_20_nov_05.zip-  
 
And you get no requester that volume AFA_OS: is miss ?

The old loader from the user archive work only with the assign.only the new loader work in the way
you test.If you get no volume requester then it should work.the loader work so that it first check a dir in sys:afa_os_libs
If he dont find it,he check for afa_os: dir or assign

If not you can start each file in afa_os_libs folder.first start afa_system_lib.exe.
then start diskfont_lib.exe and graphics_lib.exe

then it should work and we must find out wy the loader do this not.
 

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show all replies
Re: AROS Status Update
« Reply #2 on: November 22, 2005, 09:05:20 AM »
Ah execute bit is problem,on the page can currently only upload .zip.I ask if this can change that support
lha too.

BTW: is speed of truetype usabable or is it too slow to be usefull.
It can speedup,by only calc this values with a alpha value difrent 0 or 255.(most values on fonts are transparent)

but it cost develop time which maybe better use in the current state of AFA when teh text speed is usefull
to add more features
 

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show all replies
Re: AROS Status Update
« Reply #3 on: November 22, 2005, 12:26:18 PM »
@fx many thanks for doing that,i download and test it soon

for speedup,i look what can do,when switch the JIT on winaue off this seem same speed as 040 25 so i can see

yes if you have patches the loader must start behind that or the patches patches the afa funcs in the new libs away

Only Limit when you start behind c:iprefs then the new picturdatatype cant use

But i see now that 256 color iff backgroundpictures dont work

So best for new picture datatype is use truecolor backgroundpictures for now.The color reduction of AROS picture
datatype is not very good so when use truecolor pics and 256 color WB give too not very good quality.
If this a limit,because you want 8 bit WB,best remove new picturedatatype out of the
afa_os_libs dir
 

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show all replies
Re: AROS Status Update
« Reply #4 on: 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 unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show all replies
Re: AROS Status Update
« Reply #5 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