Welcome, Guest. Please login or register.

Author Topic: AFA Setup help - morelibspace  (Read 10512 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: AFA Setup help - morelibspace
« Reply #29 from previous page: May 26, 2007, 08:55:46 AM »
>Well, morelibspace should be after BlizKick to avoid excessive
>rebooting at power up (you should get 2 reboots then, instead of 3). In this case KEEPEXEC isn't required either.

morelibspace do no reboot when you dont use the parameter REBOOT.Only OS3.1 users must use REBOOT.

morelibspace add a resident module after load.When setpatch on OS > 3.1 do the reboot then after the reset in the
early bootphase at priority 70 it change the exec Funktion MakeLibrary.That Exec is not kill after every reset is a document AOS Feature.
Exec is only create when switch on the amiga, if the checksum is wrong or *exec\KickCheckSum is wrong.
And blitzkick seem support this with the Option.
makelibrary must patch so early because AOS create intuiton layer graphics etc libraries.
blitzkick seem use priority 0 (same as amiga rom update)or i am wrong ?.
When use priority 0 all system libraries are create and it is not possible to add new library functions to layer intuition graphics.

When blitzkick do exec not kill, then the Boot check for resident tags, find the morelibspace resident
and patch Makelibrary long time before blitzkick do any action.So all must work  

here is complete source in amiblitz.(pointers have always a * before.? is a address label

If FindResident_("morelibspace") Then End
memsize=?endresi-?begin+150+SizeOf .Resident
*kicktag.MemList=AllocMem_(memsize,$10001)
*resi.Resident=*kicktag+80
codemem.l=*resi+SizeOf .Resident
*kicktag\ml_Node\ln_Type=0;#NT_KICKMEM
*kicktag\ml_NumEntries=1
*kicktag\ml_ME\meu_Addr=*kicktag,memsize
*resi.Resident\rt_MatchWord=$4afc
*resi\rt_Flags=#RTF_COLDSTART
*resi\rt_Version=45,0,70
*resi\rt_Name=(?name-?begin)+codemem,(?name2-?begin)+codemem
*resi\rt_Init=codemem
*resi\rt_EndSkip=SizeOf .Resident;+(codemem+(?endresi-?begin +SizeOf .Resident))
*resi\rt_MatchTag=*resi
CopyMem_ ?begin,codemem,?endresi-?begin
*exec.ExecBase=execbase
*kicktag\ml_Node\ln_Succ=*exec\KickMemPtr
*exec\KickMemPtr=*kicktag
Poke.l *resi-4,*exec\KickTagPtr OR $80000000
Poke.l *resi-8,*resi
*exec\KickTagPtr=*resi-8
*exec\KickCheckSum=SumKickData_
CacheClearU_
If NumPars=1 AND Par$(1)="REBOOT" Then ColdReboot_
End

begin
MOVEM.l a0-a6/d0-d7,-(a7)
MOVE.l $4,a6
MOVE.l a6,a1
LEA newfunc(pc),a0
MOVE.l a0,d0
MOVE.l #-84,a0     ;makelibrary
JSR -420(a6)
LEA oldfunc(pc),a0
MOVE.l d0,(a0)
MOVEM.l (a7)+,a0-a6/d0-d7
RTS



newfunc
MOVEM.l d1/a1/a2/a3,-(a7)
CMP.l #1492,d0            ;diskfont
BEQ 'ok
CMP.l #134,d0             ;diskfont
BEQ 'ok
CMP.l #3150,d0            ;intuition library
BEQ 'ok
CMP.l #544,d0            ;graphics library
BEQ 'ok
CMP.l #46,d0            ;layers library
BEQ 'ok
CMP.l #348,d0           ;icon.library
BEQ 'ok
BRA 'skip
'ok
MOVEQ #0,d0
CMP.w #-1,(a0)
BNE 'dolong
MOVE.l a0,a2
ADDQ.w #2,a0
LEA funcs(pc),a1
'g1 CMP.w #-1,(a0)
BEQ 'em1
MOVE.w (a0)+,d1
EXT.l d1
ADD.l a2,d1
MOVE.l d1,(a1)+
ADDQ.l #1,d0
BRA 'g1
'em1 ADDQ.l #1,d0
LEA dummy(pc),a0
MOVE.l a0,(a1)+
CMP.l #350,d0
BNE 'em1
MOVE.l #-1,(a1)+
LEA funcs(pc),a0
BRA 'doit
'dolong


LEA funcs(pc),a1
'g2 CMP.l #-1,(a0)
BEQ 'em1
MOVE.l (a0)+,(a1)+
ADDQ.l #1,d0
BRA 'g2

'doit MOVE.l #10000,d0
'skip MOVEM.l (a7)+,a1/a2/d1/a3
MOVE.l oldfunc(pc),-(a7)
RTS
dummy: TRAP #0
       RTS
funcs: Ds.l 410
oldfunc: Dc.l 0
name: Dc.b "morelibspace",0
name2: Dc.b "morelibspace V45",0
Even
endresi

>What would be cool, is that all libraries of AFA_OS could be "ROMmable" modules, is this possible someday?

I dont know. blitzkick must support the increase of library space to have room for additional OS functions

for example AFA graphicslib support that functions but the original library creation code have no room for this functions in the library.that the functions can add is the job of morelibspace

SETFUNC(AndRegionRegionND,Graphics,GfxBase);
SETFUNC(CopyRegion,Graphics,GfxBase);
SETFUNC(NewRectRegion,Graphics,GfxBase);
SETFUNC(SetRegion,Graphics,GfxBase);
SETFUNC(ClearRegionRegion,Graphics,GfxBase);
SETFUNC(IsPointInRegion,Graphics,GfxBase);
SETFUNC(CreateRastPort,Graphics,GfxBase);
SETFUNC(FreeRastPort,Graphics,GfxBase);
}
 
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show only replies by Piru
    • http://www.iki.fi/sintonen/
Re: AFA Setup help - morelibspace
« Reply #30 on: May 26, 2007, 11:15:00 AM »
@bernd_afa
Quote
morelibspace do no reboot when you dont use the parameter REBOOT.Only OS3.1 users must use REBOOT.

Yes I noticed that.

Quote
morelibspace add a resident module after load.When setpatch on OS > 3.1 do the reboot then after the reset in the early bootphase at priority 70 it change the exec Funktion MakeLibrary.

Yes, that is obvious.

Quote
That Exec is not kill after every reset is a document AOS Feature. Exec is only create when switch on the amiga, if the checksum is wrong or *exec\KickCheckSum is wrong.

Or if the exec version changes. And this can happen when you use BlizKick.

Thus, to use it with BlizKick, there are couple of options:
1) Create BlizKick compatible version of the patch, so it can be used as a module. Just adding the resident structure inside the binary is enough.

2) Instruct users to start the program after BlizKick, with REBOOT option.

Obviously the bugs listed still need to be fixed, too.

Quote
makelibrary must patch so early because AOS create intuiton layer graphics etc libraries.

If you want to patch the libraries to include new functions, then yes, obviously.

Quote
blitzkick seem use priority 0 (same as amiga rom update)or i am wrong ?

You are wrong. The BlizKick source code is included btw, you don't need to guess.

BlizKick can add any priority resident modules to system. It's just like expanding the ROM. BlizKick does not use KickTagPtr or KickMemPtr at all, either.

Quote
When blitzkick do exec not kill, then the Boot check for resident tags, find the morelibspace resident
and patch Makelibrary long time before blitzkick do any action.So all must work

It will work just fine. There will be two reboots though, but that is the only option (2) if you insist in not doing the simple thing and adding the resident structure.

Quote
here is complete source

The complete source is what I commented earlier. See the earlier post about the bugs.

Quote
>What would be cool, is that all libraries of AFA_OS could be "ROMmable" modules, is this possible someday?

I dont know. blitzkick must support the increase of library space to have room for additional OS functions

With BlizKick you could replace the whole ROM resident module with a new one, without need to patch anything. Then obviously there would be no need to increase any library function table.

If you don't want this, the easy step of adding the resident structure to the binary (+fixing the bugs) would make it BlizKick compatible.
 

Offline jmbattle

  • Sr. Member
  • ****
  • Join Date: May 2005
  • Posts: 324
    • Show only replies by jmbattle
    • http://www.amigainabox.co.uk
Re: AFA Setup help - morelibspace
« Reply #31 on: May 26, 2007, 12:38:55 PM »
I guess this means we won't be seeing a new version of AfA_OS released this weekend, huh Jan? ;)

Cheers,
James
x
 

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show only replies by unusedunused
Re: AFA Setup help - morelibspace
« Reply #32 on: May 26, 2007, 12:58:36 PM »
>If you don't want this, the easy step of adding the resident structure to the binary (+fixing the bugs) would make it BlizKick compatible.

Can you please show me a blitzkick compatible source that can use with loadresident ?.In the blitzkick archive i see nothing.  
Because i cant test on my classic, i can then only copy the source of resident structure in morelibspace
and modify it and send a tester with blitzkick to test and hope it work ;-)

>(+fixing the bugs) would make it BlizKick compatible.

Only bug maybe possible is reentrant, my point of few was that , that always the ramlib task call makelibrary.
so that must not reentrant.

I have now change code that a task switch is disable with forbid so other task must wait.so it should be rock solid ;-)
others you told as  bugs are only limits.
 
Have you ever see a library that come near 250 Functions ?.

I see AROS libs and they are far far awy from the limit.
Or should i better increase the Limit to 1000 Functions ?.

Cost only 6000 bytes more memory.
 

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show only replies by unusedunused
Re: AFA Setup help - morelibspace
« Reply #33 on: May 26, 2007, 12:59:49 PM »
>I guess this means we won't be seeing a new version of >AfA_OS released this weekend, huh Jan? ;)

morelibspace in not very important, can maybe later release.
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show only replies by Piru
    • http://www.iki.fi/sintonen/
Re: AFA Setup help - morelibspace
« Reply #34 on: May 26, 2007, 01:29:21 PM »
Quote
Can you please show me a blitzkick compatible source that can use with loadresident ?


Like I've explained twice already, just a regular resident tag like in any library/device:

Code: [Select]
#include <exec/nodes.h>
#include <exec/resident.h>

void Init(void);

struct Resident res =
{
    RTC_MATCHWORD,
    &res,
    &res + 1,
    RTF_COLDSTART,
    1,
    NT_UNKNOWN,
    70,
    &quot;whatever&quot;,
    &quot;whatever 1.0 (26.5.2007)\r\n&quot;,
    Init
};

void Init(void)
{
}


Regarding the bugs you don't consider bugs: Well it's your choice. IMO those are potentially fatal bugs, but if you don't see them as such, I can't possibly force you to fix them.

Regarding number of functions in a library: Yes I've seen a library with more than 250 functions. Arbitrary limitations suck: Just because you don't know of a library with x functions doesn't mean that such a thing can't exist. It's good coding practice to be ready for unexpented, and don't blow up the whole system when the unexpected arrives. This is especially true when patching OS functions, since then you have no control of the potential input.
 

Offline itix

  • Hero Member
  • *****
  • Join Date: Oct 2002
  • Posts: 2380
    • Show only replies by itix
Re: AFA Setup help - morelibspace
« Reply #35 on: May 26, 2007, 03:06:11 PM »
Quote

Have you ever see a library that come near 250 Functions ?.

I see AROS libs and they are far far awy from the limit.
Or should i better increase the Limit to 1000 Functions ?.


Many libraries ported from Linux can easily have few hundred functions. glib.library for MorphOS has about 950 functions :-P

My Amigas: A500, Mac Mini and PowerBook
 

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show only replies by unusedunused
Re: AFA Setup help - morelibspace
« Reply #36 on: May 26, 2007, 04:43:39 PM »
>Many libraries ported from Linux can easily have few hundred functions. glib.library for MorphOS has about 950 functions

thats an reason i understand, but luckily 68k use clib2 OS4 use too, thats linker libs.also most linux libs are linker libs.
Also the library expand code is only execute when a library have this pos size.

CMP.l #1492,d0            ;diskfont
BEQ 'ok
CMP.l #134,d0             ;diskfont
BEQ 'ok
CMP.l #3150,d0            ;intuition library
BEQ 'ok
CMP.l #544,d0            ;graphics library
BEQ 'ok
CMP.l #46,d0            ;layers library
BEQ 'ok
CMP.l #348,d0           ;icon.library
BEQ 'ok
BRA 'skip

I get the idea to check if the function number is lower 200.
If a library with more functions than 200 really fit the pos size it is sure that it is not 1 of this ROM libraries that should enhance.
this should be really 100% safe or i am wrong ?.

The reason wy i must check for pos size is that it is the only indicator of library size.The AOS ROM diffrent librariey  versions have same pos size.
only differ in function size.

Check if the ROM library is large enough to fit new AROS code is Job of the AFA module.
 
 

Offline jmbattle

  • Sr. Member
  • ****
  • Join Date: May 2005
  • Posts: 324
    • Show only replies by jmbattle
    • http://www.amigainabox.co.uk
Re: AFA Setup help - morelibspace
« Reply #37 on: May 27, 2007, 10:17:58 PM »
Just as Jan suggested, a new version has just been released:

http://amidevcpp.amiga-world.de/afa_binarie_upload.php

I'm off to test it now. ;)

Cheers,
James
x
 

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show only replies by unusedunused
Re: AFA Setup help - morelibspace
« Reply #38 on: May 28, 2007, 08:15:32 AM »
Yes 3.96 is release and too new morelibspace.

I hope now it work in blitzkick with that code...

If FindResident_("morelibspace") Then End
memsize=?endresi-?begin+150+SizeOf .Resident
*kicktag.MemList=AllocMem_(memsize,$10001)
*resi.Resident=*kicktag+80
codemem.l=*resi+SizeOf .Resident
*kicktag\ml_Node\ln_Type=0;#NT_KICKMEM
*kicktag\ml_NumEntries=1
*kicktag\ml_ME\meu_Addr=*kicktag,memsize
*resi.Resident\rt_MatchWord=$4afc
*resi\rt_Flags=#RTF_COLDSTART
*resi\rt_Version=45,0,70
*resi\rt_Name=(?name-?begin)+codemem,(?name2-?begin)+codemem
*resi\rt_Init=codemem
*resi\rt_EndSkip=SizeOf .Resident;+(codemem+(?endresi-?begin +SizeOf .Resident))
*resi\rt_MatchTag=*resi
CopyMem_ ?begin,codemem,?endresi-?begin
*exec.ExecBase=execbase
*kicktag\ml_Node\ln_Succ=*exec\KickMemPtr
*exec\KickMemPtr=*kicktag
If *exec\KickTagPtr
Poke.l *resi-4,*exec\KickTagPtr OR $80000000
End If

Poke.l *resi-8,*resi
*exec\KickTagPtr=*resi-8
*exec\KickCheckSum=SumKickData_
CacheClearU_
If NumPars=1 AND Par$(1)="REBOOT" Then ColdReboot_
End

;#include          ;example from Piru for blitzkick comaptible
;#include
;
;void Init(void);
;
;struct Resident res =
;{
;    RTC_MATCHWORD,
;    &res,
;    &res + 1,
;    RTF_COLDSTART,
;    1,
;    NT_UNKNOWN,
;    70,
;    "whatever",
;    "whatever 1.0 (26.5.2007)\r\n",
;    Init
;};
;
;void Init(void)
;{
;}




ROMTag:   Dc.w  #RTC_MATCHWORD  ; UWORD RT_MATCHWORD
          Dc.l  ROMTag          ; APTR  RT_MATCHTAG
          Dc.l  ROMTag+1        ; APTR  RT_ENDSKIP
          Dc.b  #RTF_COLDSTART  ; UBYTE RT_FLAGS
          Dc.b  1               ; UBYTE RT_VERSION
          Dc.b  #NT_UNKNOWN     ; UBYTE RT_TYPE
          Dc.b  70              ; BYTE  RT_PRI
          Dc.l  name            ; APTR  RT_NAME
          Dc.l  name2           ; APTR  RT_IDSTRING
          Dc.l  begin           ; APTR  RT_INIT

begin
MOVEM.l a0-a6/d0-d7,-(a7)
MOVE.l $4,a6
MOVE.l a6,a1
LEA newfunc(pc),a0
MOVE.l a0,d0
MOVE.l #-84,a0     ;makelibrary
JSR -420(a6)
LEA oldfunc(pc),a0
MOVE.l d0,(a0)
MOVEM.l (a7)+,a0-a6/d0-d7
RTS



newfunc
MOVEM.l d1/a1/a2/a3,-(a7)
JSR -$84(a6)
CMP.l #1492,d0            ;diskfont
BEQ 'ok
CMP.l #134,d0             ;diskfont
BEQ 'ok
CMP.l #3150,d0            ;intuition library
BEQ 'ok
CMP.l #544,d0            ;graphics library
BEQ 'ok
CMP.l #46,d0            ;layers library
BEQ 'ok
CMP.l #348,d0           ;icon.library
BEQ 'ok
BRA 'skip
'ok
MOVE.l d0,d0store
MOVE.l a0,a0store
MOVEQ #0,d0
CMP.w #-1,(a0)
BNE 'dolong
MOVE.l a0,a2
ADDQ.w #2,a0
LEA funcs(pc),a1
'g1 CMP.w #-1,(a0)
BEQ 'em1
MOVE.w (a0)+,d1
EXT.l d1
ADD.l a2,d1
MOVE.l d1,(a1)+
ADDQ.l #1,d0
BRA 'g1
'em1 ADDQ.l #1,d0
LEA dummy(pc),a0
MOVE.l a0,(a1)+
CMP.l #350,d0
BNE 'em1
MOVE.l #-1,(a1)+
LEA funcs(pc),a0
BRA 'doit
'dolong
LEA funcs(pc),a1
'g2 CMP.l #-1,(a0)
BEQ 'em1
MOVE.l (a0)+,(a1)+
ADDQ.l #1,d0
CMP.l #300,d0             ; failsave libs over 300 Slots are no romlib dont increase
BEQ 'wrong
BRA 'g2
'wrong
 MOVE.l d0store,d0
 MOVE.l a0store,a0
 BRA 'skip
'doit MOVE.l #10000,d0
'skip MOVEM.l (a7)+,a1/a2/d1/a3
MOVE.l a3,-(a7)
;MOVE.l oldfunc(pc),-(a7)
MOVE.l oldfunc(pc),a3
JSR (a3)
MOVE.l (a7)+,a3
JSR -$8a(a6)
RTS
dummy: TRAP #0
       RTS
funcs: Ds.l 410
oldfunc: Dc.l 0
d0store: Dc.l 0
a0store: Dc.l 0
name: Dc.b "morelibspace",0
name2: Dc.b "morelibspace V45",0
Even
endresi
 

Offline jmbattle

  • Sr. Member
  • ****
  • Join Date: May 2005
  • Posts: 324
    • Show only replies by jmbattle
    • http://www.amigainabox.co.uk
Re: AFA Setup help - morelibspace
« Reply #39 on: May 28, 2007, 02:03:54 PM »
Bernd, thank you for the new release.

I have just updated my AIAB installation (previously using AfA_OS v3.95), yet for some reason using v3.96 diskfont_lib.exe, the system does not boot completely.

I have tried disabling patches, including MCP, VisualPrefs etc. without success.  However, reverting back to v3.95 diskfont_lib.exe, the system boots correctly.

May I therefore ask what has changed with this file between v3.95 and v3.96?

I have uploaded an archive to http://aiab.emuunlim.com/r10.5/!bleedingedge/ and would appreciate your suggestions as to why I am experiencing issues.

Kind regards,
James
x
 

Offline CoolitTopic starter

  • Sr. Member
  • ****
  • Join Date: Feb 2005
  • Posts: 267
    • Show only replies by Coolit
Re: AFA Setup help - morelibspace
« Reply #40 on: May 28, 2007, 03:00:43 PM »
I have the same problem jmbattle, if I change the diskfont_lib.exe back to the 3.95 version it works fine.

Another side effect of this problem is if you launch AFA_OS after workbench has loaded, it will launch (without AA fonts though) but if you try to change the font with the font prefs it hangs.

I've still to test the new morelibspace for Blizkick compatibility.
[color=0066FF]The System:[/color][/u]

A1200/DBOX - B1260/SCSI/198MB Mediator/Voodoo5500/SB128/100NIC/SpiderII FAST ATA Mk3/SCSI Adapter/PC KEY - IDE DVD/SCSI CDRW/80GB IDE HDD/9GIG 10k SCSI HDD - 3.1 ROMS/OS 3.9 - Logitech KB + MX1000 Mouse
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show only replies by Piru
    • http://www.iki.fi/sintonen/
Re: AFA Setup help - morelibspace
« Reply #41 on: May 28, 2007, 03:13:44 PM »
@bernd_afa

Hm, it looks like you made a mistake when translating the C code to assembler:
Code: [Select]
Dc.l ROMTag+1 ; APTR RT_ENDSKIP
is wrong, it should be:

Code: [Select]
Dc.l ROMTag+RT_SIZE ; APTR RT_ENDSKIP

The actual amount added doesn't matter much, as long as it's >0, even and within the module. If it can be arranged easily, it should point to the end of this particular module.

Odd endskip is rather bad, as it causes further modules to be missed (and crashes 68000/68010).
 

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show only replies by unusedunused
Re: AFA Setup help - morelibspace
« Reply #42 on: May 28, 2007, 03:20:35 PM »
the diskfont fix is done for a function that used only by fixfonts.I see less chance that the fix make problems.
 
I test AIAB several times before and have no problems or boot crashes.I use all AFA libs i release (included icon zune and intuition.library)
I dont know what scalos you have and additional Fonts you use.maybe there is newer aiab ?.I use latetest from HP with JIT addon.

Also have you add in your  startup sequence  morelibspace ?
if use morelibspace on OS3.1 need a reboot.

;---Start the "Full Boot" option...
morelibspace REBOOT
c:setpatch >nil:                  
 

Offline unusedunused

  • Sr. Member
  • ****
  • Join Date: Nov 2005
  • Posts: 479
    • Show only replies by unusedunused
Re: AFA Setup help - morelibspace
« Reply #43 on: May 28, 2007, 03:34:37 PM »
>The actual amount added doesn't matter much, as long as it's >0, even and within the module.
>If it can be arranged easily, it should point to the end of this particular module.

thanks for your help

I get that too in mind and i think if this work blitzkick use the filesize.

I modify now my code endresi is the label at end of code.but release soon is not important ?

ROMTag:   Dc.w  #RTC_MATCHWORD  ; UWORD RT_MATCHWORD
          Dc.l  ROMTag          ; APTR  RT_MATCHTAG
          Dc.l  endresi         ; APTR  RT_ENDSKIP
          Dc.b  #RTF_COLDSTART  ; UBYTE RT_FLAGS
          Dc.b  45              ; UBYTE RT_VERSION
          Dc.b  #NT_UNKNOWN     ; UBYTE RT_TYPE
          Dc.b  70              ; BYTE  RT_PRI
          Dc.l  name            ; APTR  RT_NAME
          Dc.l  name2           ; APTR  RT_IDSTRING
          Dc.l  begin           ; APTR  RT_INIT


You told a simple resident structur for libraries is enough.But a library look diffrent to your example

Here is library code.But i see here too end of code is use (EndOfLib)

ROMTag:   Dc.w  #RTC_MATCHWORD  ; UWORD RT_MATCHWORD
          Dc.l  ROMTag          ; APTR  RT_MATCHTAG
          Dc.l  EndOfLib        ; APTR  RT_ENDSKIP
          Dc.b  #RTF_AUTOINIT   ; UBYTE RT_FLAGS
          Dc.b  #VERSION        ; UBYTE RT_VERSION
          Dc.b  #NT_LIBRARY     ; UBYTE RT_TYPE
          Dc.b  0               ; BYTE  RT_PRI
          Dc.l  LibName         ; APTR  RT_NAME
          Dc.l  LibId           ; APTR  RT_IDSTRING
          Dc.l  InitStuff       ; APTR  RT_INIT

LibName:  !LIBRARYNAME
.LibId:    Dc.b  "own.library 1.6 (16/02/2000)",0
          Even  ; was ds.w 0 - you can use Even with ASM only progs, seems to work OK

InitStuff:Dc.l  SizeOf.LibraryBase  ; Structure size
          Dc.l  Functions           ; Jump table address
          Dc.l  LibBaseData         ; Information for the initialization
          Dc.l  InitRoutine         ; Own initialization routine

Functions:Dc.l  r_Open      ; Open routine address
          Dc.l  r_Close     ; Close routine address
          Dc.l  r_Expunge   ; Expunge routine address
          Dc.l  r_Null      ; ** Reserved **
.functiontable
          Dc.l  r_First     ; First user routine address
          Dc.l  r_second    ;second user routine in basic
          Dc.l  -1          ; Table ends

 

Offline CoolitTopic starter

  • Sr. Member
  • ****
  • Join Date: Feb 2005
  • Posts: 267
    • Show only replies by Coolit
Re: AFA Setup help - morelibspace
« Reply #44 on: May 28, 2007, 03:37:24 PM »
@bernd_afa
I stripped out all the additional fonts that I had added and tried with only the default fonts that came with AFA_OS, still the same problem with diskfont.

I've tested morelibspace with blitzkick and it's not working unfortunately, is this problem related to the code that Piru highlighted?

@Piru or bernd_afa
Do I need to pass any special arguments to blizkick? and should I position the C:morelibspace before setpatch or after blizkick? (I know there was some talk about this earlier).

Thanks :-)
[color=0066FF]The System:[/color][/u]

A1200/DBOX - B1260/SCSI/198MB Mediator/Voodoo5500/SB128/100NIC/SpiderII FAST ATA Mk3/SCSI Adapter/PC KEY - IDE DVD/SCSI CDRW/80GB IDE HDD/9GIG 10k SCSI HDD - 3.1 ROMS/OS 3.9 - Logitech KB + MX1000 Mouse