Amiblitz3 programs on OCS Amiga 500

[AmiNju]

Originally Posted by Honitos

I patched the memlib to use simple AllocMem/FreeMem-routines.
That should work on kick1.x-machines again.

But it is not a solution as the more modern memory pooling should be used when the os makes it available. Maybe I could add an os-checking and let the lib use both technologies.

Please try the patched AcidLibs first, and tell my if your common sources still work on kick1/kick2/kick3.

This would be very nice, when AB3 will produce Games/Apps for 68K OCS v1.3 too, so I could move from BB2 to AB3.

[fabbroz]

nope with patched AcdiLibs
How can i help you?

Originally Posted by Honitos

I patched the memlib to use simple AllocMem/FreeMem-routines.
That should work on kick1.x-machines again.

But it is not a solution as the more modern memory pooling should be used when the os makes it available. Maybe I could add an os-checking and let the lib use both technologies.

Please try the patched AcidLibs first, and tell my if your common sources still work on kick1/kick2/kick3.

[Honitos]

Originally Posted by fabbroz

nope with patched AcdiLibs
How can i help you?

Maybe there are other problems with kick1.3 in other libs.


For now, I just patched the memlib (internal use) and the bitmaplib.
If your game is still crashing, it may be due to a bug in another lib.


Does the game crash with the UAE-CPU-Setting "More compatible" ?

Does it work with Kick2.0?

[Honitos]

Originally Posted by AmiNju

This would be very nice, when AB3 will produce Games/Apps for 68K OCS v1.3 too, so I could move from BB2 to AB3.

I am on my way to solve this problem. You could help by investigating the roots of your crashes.


If the program crashes right at startup before executing the first sourceline, it is something in the initcode of a lib.


If it crashes while running, try to check with command/function let the machine crash.

[fabbroz]

yes it crash in both cases..
and crash on Real Amiga500 KS1.3


on real A1200 with KS3.1 it works fine.
can't have an real KS2.0 machine..

Originally Posted by Honitos

Maybe there are other problems with kick1.3 in other libs.


For now, I just patched the memlib (internal use) and the bitmaplib.
If your game is still crashing, it may be due to a bug in another lib.


Does the game crash with the UAE-CPU-Setting "More compatible" ?

Does it work with Kick2.0?

[fabbroz]

it crash on startup...
i try to understand it too, writing an AD HOC program..

Originally Posted by Honitos

I am on my way to solve this problem. You could help by investigating the roots of your crashes.


If the program crashes right at startup before executing the first sourceline, it is something in the initcode of a lib.


If it crashes while running, try to check with command/function let the machine crash.

[fabbroz]

Ok mate i've found *one* problem (mine)

BitMap 0,320,200,3
InitCopList 0,44,256,$03,8,8,0
DisplayBitMap 0,0
PalRGB 0,0,0,0,0
DisplayPalette 0,0



;CRASH only HERE ON KS1.3
;the rest (without this) works fine on KS1.3!!!


If LoadTrackerModule(0,"assets/mod.stage1")
  ;GetPatternPosition %1100
EndIf

If StartTracker(0)
 ; ModuleSampleName$ 0,2
EndIf
;END CRASH

BLITZ
CreateDisplay 0

While Joyb(0)=0
    VWait
    BitMapOutput 0
    Locate 2,2:Print "BITMAP TEST OK..."
Wend
End

Originally Posted by fabbroz

yes it crash in both cases..
and crash on Real Amiga500 KS1.3


on real A1200 with KS3.1 it works fine.
can't have an real KS2.0 machine..

[Honitos]

Ok thanks for that info, I am going to look into the trackerlib this weekend. Maybe I find out, what the problem is with kick1.3!

[fabbroz]

maybe i found the problem...
on my game, i've make a LUT of SIN/COS/ATAN etc...

when i use that on my testcode, it crash...
so, i think it could be SIN/COS/ATAN etc routines that use yet FPU.


could be?



hope to help you.

Originally Posted by Honitos

Ok thanks for that info, I am going to look into the trackerlib this weekend. Maybe I find out, what the problem is with kick1.3!

[Honitos]

Originally Posted by fabbroz

maybe i found the problem...
on my game, i've make a LUT of SIN/COS/ATAN etc...

when i use that on my testcode, it crash...
so, i think it could be SIN/COS/ATAN etc routines that use yet FPU.


could be?



hope to help you.

Would you mind to provide me a short source example, that uses the mentioned LUT so I can reproduce the problem?

[fabbroz]

here

Originally Posted by Honitos

Would you mind to provide me a short source example, that uses the mentioned LUT so I can reproduce the problem?

[Honitos]

Sorry, I need an source example from AB3 with just a short code example, that crashes on a 68000.

It would be very hard to debug your executable and find out with Basic routine affected the crash....

[Honitos]

I found the bug that let fabrizios test code crash on a 68000:

an=360
Dim _sin(an)
Dim _cos(an)
For i=0 To an-1
    _sin(i)=i
    _cos(i)=i
Next

The DIM command had been patched to allow more that 65535 entries in an array. But unfortunately it was patched by an asmcommand that is only available on 68020+.
So I added code to use different asm routines for arrays smaller than 65536 to use 68000-friendly code.

That means every use of DIM was a cause of an immediately crash on an A500!

That is fixed now.

[Honitos]

Originally Posted by fabbroz

Ok mate i've found *one* problem (mine)

BitMap 0,320,200,3
InitCopList 0,44,256,$03,8,8,0
DisplayBitMap 0,0
PalRGB 0,0,0,0,0
DisplayPalette 0,0



;CRASH only HERE ON KS1.3
;the rest (without this) works fine on KS1.3!!!


If LoadTrackerModule(0,"assets/mod.stage1")
  ;GetPatternPosition %1100
EndIf

If StartTracker(0)
 ; ModuleSampleName$ 0,2
EndIf
;END CRASH

BLITZ
CreateDisplay 0

While Joyb(0)=0
    VWait
    BitMapOutput 0
    Locate 2,2:Print "BITMAP TEST OK..."
Wend
End

I found the reason for the crash here, too !
It is simple: the ciatrackerlib is limited to Kick2.0+ as it used os-functions only available with Kick2.0....
As I do not have the source of the lib (I found it here: http://aminet.net/package/dev/blitz/CIATrkrLib), I am not able to fix that :-( Maybe someone could ask the author to release the latest source.



Or maybe you could use another trackerlib?

[MickGyver]

Originally Posted by Honitos

I found the reason for the crash here, too !
It is simple: the ciatrackerlib is limited to Kick2.0+ as it used os-functions only available with Kick2.0....
As I do not have the source of the lib (I found it here: http://aminet.net/package/dev/blitz/CIATrkrLib), I am not able to fix that :-( Maybe someone could ask the author to release the latest source.



Or maybe you could use another trackerlib?

Yes, don't bother trying to "fix" that library. There is a better library available now, the converted pt library by phx.

P.S. Thanks Honitos for all the splendid work you are doing with Amiblitz3!

[Honitos]

Ok, but is the ptlib already part of the AB3-package?

Funny question from the maintainer itself, I know, but I am not familiar with all the libs, as I concentrated myself on the IDE for the past weeks...

[E-Penguin]

phx's library certainly works on an A500

[MickGyver]

Originally Posted by Honitos

Ok, but is the ptlib already part of the AB3-package?

Funny question from the maintainer itself, I know, but I am not familiar with all the libs, as I concentrated myself on the IDE for the past weeks...

Hmm, I converted a newer version of the phx library to Blitz but there might be some problems using it with Amiblitz 3.7. You can read more (and download the source) here: http://eab.abime.net/showpost.php?p=...9&postcount=64

[Honitos]

I am going to check that lib, when I fixed the kick1.3 compatibility with

arraylib
linklistlib

I want to see FType on A500 compiled with AB3!

[fabbroz]

Yeahhh!!!!!!

Originally Posted by honitos

i am going to check that lib, when i fixed the kick1.3 compatibility with

arraylib
linklistlib

i want to see ftype on a500 compiled with ab3!