Navigation
« 

Anonymous




Register
Login
« 
« 

Amiga Future

« 

Community

« 

Knowledge

« 

Last Magazine

The Amiga Future 158 will be released on the 5th September.

The Amiga Future 158 will be released on the 5th September.
The Amiga Future 158 will be released on the 5th September.

The Amiga Future 158 will be released on the 5th September.
More informations

« 

Service

« 

Search




Advanced search

Unanswered topics
Active topics
« 

Social Media

Twitter Amigafuture Facebook Amigafuture RSS-Feed [german] Amigafuture RSS-Feed [english] Instagram YouTube Patreon
« 

Advertisement

Amazon

Patreon

« 

Partnerlinks

DigiBoosterPro 2.21 - Crash in various weird ways when toggling 8bit/16bit

Support DigiBooster

Moderators: G.Frank, AndreasM

Post Reply
AiO
Grade reingestolpert
Grade reingestolpert
Posts: 4
Joined: 29.09.2022 - 14:35

DigiBoosterPro 2.21 - Crash in various weird ways when toggling 8bit/16bit

Post by AiO »

Hello,

I have an interesting problem. I run DigiBoosterPro 2.21 on my A4000D with CyberStormPPC and 060. The machine also has a PicassoIV+PalomaIV, X-Surf100+RapidRoad and I use a DelfinaLite audio card.

I've been struggling for quite some time with a weird crash-scenario that seems to have started with AmigaOS 3.2 and later 3.2.1... Maybe I have seen it at some point in the "before-time" too. But. Here we go:

I started worrying when I could not load my old XM/DBM modules into DigiBoosterPro. The MOD-files worked fine... Then i boiled it down to modules with 16bit samples, or just by loading 16bit samples without a module. Now I have the fastest way to fail - just clicking the "8bit"-button left of "STATUS" so that it turns into "16bit" triggers the problem in the same way.

What happens is that the mouse cursor get garbled, or sometimes it just flashes the power led and reboots, sometimes I get a recoverable alert, and sometimes software failure. :) Many ways to fail in other words.

I have been running this machine since the 90's and have _really_ enjoyed my DigiBoosterPro and now I'm sad :(

Another thing to note is that it works flawless on a ReAmiga1200 with TerribleFire1260 (with and without Delfina on the clock-port), and an old Amiga1200 with Blizzard1230IV with no sound card. Both running 3.2.1. I did some major re-installation of the A4000 when i switched from 3.1.4 (where DigiBooster worked) to 3.2.x... DigiBooster also worked fine when i was running 3.1, 3.5 and 3.9 as far as I can remember - But there is a vague memory of me seeing this problem at some point throughout the history of the machine. Somewhere along the way I also changed Ethernet card from Ariadne-II to X-Surf. But I DID run DigiBooster fine on the current HW-config before.

Any good pointers on how to resolve this problem? What does DigiBooster Pro 2.21 _do_ when i click that button!?

Weird thing.... I have made it a hobby of mine to have "Digital Twins" of my machines. Also here in an emulated version of my Amiga4000 (toccata-emulation) the 16bit stuff fscks-up big-time. So it should not be HW related. I've seen this on a couple of other virtual Amigas i use in FS-UAE too. While the digital twin of my ReAmiga1200 and Amiga1200 seem to work fine with DigiBooster too.

I'm out of ideas.... :(

Edit: I can run any other AHI player (Eagle/Hippo, even DigiBooster3 Demo, though being slow) without any issues. It's _just_ DigiBoosterPro 2.21 that makes this weird thing)

Kind regards,
AiO
daxb
AFF Profi
AFF Profi
Posts: 612
Joined: 10.11.2002 - 01:42

Re: DigiBoosterPro 2.21 - Crash in various weird ways when toggling 8bit/16bit

Post by daxb »

AiO wrote: 29.09.2022 - 15:11What does DigiBooster Pro 2.21 _do_ when i click that button!?
Start SnoopDos and/or other debug tools before you click the 8/16bit button. There is access to ahi.device and other AHI stuff. audio.device is also accessed but that shouldn't make problems. So I would check if the problem stays with different ahi.device versions and/or different audio modes and settings.

A switch from 8/16bit doubles/halves the memory usage. So there might be some maths going on and of course memory accesses. I guess there is no FPU involved.
AiO
Grade reingestolpert
Grade reingestolpert
Posts: 4
Joined: 29.09.2022 - 14:35

Re: DigiBoosterPro 2.21 - Crash in various weird ways when toggling 8bit/16bit

Post by AiO »

Thanks for you fast reply!
daxb wrote: 30.09.2022 - 11:25 Start SnoopDos and/or other debug tools before you click the 8/16bit button. There is access to ahi.device and other AHI stuff. audio.device is also accessed but that shouldn't make problems. So I would check if the problem stays with different ahi.device versions and/or different audio modes and settings.
Ok... I made SnoopDOS and CyberGuard dump logs to a RAD:-disk for speed, and persistence so I could recover them from a crash... Here are two scenarios:

1. Loading an .xm module I know work
SnoopDOS

Code: Select all

 Count Process Name       Action     Target Name                 Options Res.
 ----- ------------       ------     -----------                 ------- ----
 :
 :
 :
 6     DigiBoosterPro     *Open      dh2:moduler/released_module Read    OK  
 7     DigiBoosterPro     #FINDINPUT  22303B3,        0,  225F99 DH2     OK  
 8     DigiBoosterPro     #READ       807DCD4,  8CB1188,      62 DH2     OK  
 9     DigiBoosterPro     #END        807DCD4                    DH2     OK  
 10    DigiBoosterPro     *Lock      dh2:moduler/released_module Read    OK  
 11    DigiBoosterPro     #LOC_OBJEC        0,  231A782, FFFFFFF DH2     OK  
 12    DigiBoosterPro     #EXAM_OBJE  201F737,  233C45A          DH2     OK  
 13    DigiBoosterPro     #FREE_LOCK  201F737                    DH2     OK  
 14    DigiBoosterPro     *Open      dh2:moduler/released_module Read    OK  
 15    DigiBoosterPro     #FINDINPUT  22303B3,        0,  225F99 DH2     OK  
 16    DigiBoosterPro     #READ       807DCD4,  8E47900,    A21C DH2     OK  
 17    DigiBoosterPro     #END        807DCD4                    DH2     OK  
 18    DigiBoosterPro     *Open      ENV:Sys/ahi.prefs           Read    OK  
 19    DigiBoosterPro     #FINDINPUT  22303B3,  207588F,  21540F RAM     OK  
 20    DigiBoosterPro     #READ       22DCAC1,  8C69D00,         RAM     OK  
 21    DigiBoosterPro     #READ       22DCAC1,  8A2B124,         RAM     OK  
 22    DigiBoosterPro     #READ       22DCAC1,  8C69D00,         RAM     OK  
 23    DigiBoosterPro     #READ       22DCAC1,  8A2B988,         RAM     OK  
 24    DigiBoosterPro     #READ       22DCAC1,  8C69D00,         RAM     OK  
 25    DigiBoosterPro     #READ       22DCAC1,  8A465B8,       1 RAM     OK  
 26    DigiBoosterPro     #READ       22DCAC1,  8C69D00,         RAM     OK  
 27    DigiBoosterPro     #READ       22DCAC1,  8A46AFC,       2 RAM     OK  
 28    DigiBoosterPro     #READ       22DCAC1,  8C69D00,         RAM     OK  
 29    DigiBoosterPro     #READ       22DCAC1,  8A64ED4,       2 RAM     OK  
 30    DigiBoosterPro     #READ       22DCAC1,  8C69D00,         RAM     OK  
 31    DigiBoosterPro     #READ       22DCAC1,  8A813A4,       2 RAM     OK  
 32    DigiBoosterPro     #READ       22DCAC1,  8C69D00,         RAM     OK  
 33    DigiBoosterPro     #READ       22DCAC1,  8A813D4,       2 RAM     OK  
 34    DigiBoosterPro     #READ       22DCAC1,  8C69D00,         RAM     OK  
 35    DigiBoosterPro     #READ       22DCAC1,  8A81404,       2 RAM     OK  
 36    DigiBoosterPro     #END        22DCAC1                    RAM     OK
 :
 :
Nothing weird going on there, from what I can tell....

CyberGuard

Code: Select all

Alert !! Alert 81000005     TCB: 08D83560     USP: 08D875C8
Data: 08933738 08000010 00000000 11590A58 0000001F 0000002E 00000023 81000005
Addr: 08000000 08C5D320 08C5D290 08D45598 08D10326 08D10312 08000964 08D875C8
Stck: 00F81E92 00000000 08C71D5C 00F81EBE 08BAAE9C 00000009 00000190 08C58984
Stck: 08C5D324 08B4EA60 08CFE830 00000000 00000001 00000009 00000190 0000001F
Stck: 0000002E 00000023 00320000 FFFFFFFF 000006A0 08C71D5C 08D45598 08D10326
Stck: 08D10312 08C71A24 08CF7DFA 08CF202C 08CF1C22 00F967B4 00004000 44696769
Stck: 426F6F73 74657250 726F0000 00000000 00000000 00000000 00000000 00000000
Stck: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Stck: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Stck: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
----> $00f81e92: MOVE.L    A1,D1
----> $08c71d5c: ORI.B     #$00,D0
----> $00090000: ORI.B     #$00,(A7)+
----> $08c58984: ORI.B     #$00,D0
----> $08c5d324: BCLR      #$38,(A3)
----> $08cfe830: MOVEM.L   (A7)+,D0-D7/A0-A6
----> $00010000: SUB.B     D7,D7
----> $00090000: ORI.B     #$00,(A7)+
----> $001f0000: DC.W      $ffff
Name: "DigiBoosterPro"   
WORD-READ from 00000000                  PC: 00000000
USP:  08D875D0 SR: 0004 FLSW: 01428200 TCB: 08D83560
Data: 00000000 08C5A12C 00014E1C 00F81E92 00000005 00000000 0000000D 08D87608
Addr: 08000000 08C5A12C 08C522D0 08D83560 08D87644 08C5269E 08000964 08D875D0
Stck: 08C71D5C 00F81EBE 08BAAE9C 00000009 00000190 08C58984 08C5D324 08B4EA60
Stck: 08CFE830 00000000 00000001 00000009 00000190 0000001F 0000002E 00000023
Stck: 00320000 FFFFFFFF 000006A0 08C71D5C 08D45598 08D10326 08D10312 08C71A24
Stck: 08CF7DFA 08CF202C 08CF1C22 00F967B4 00004000 44696769 426F6F73 74657250
Stck: 726F0000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Stck: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Stck: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Stck: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
----> $08c71d5c: ORI.B     #$00,D0
----> $00090000: ORI.B     #$00,(A7)+
----> $08c58984: ORI.B     #$00,D0
----> $08c5d324: BCLR      #$38,(A3)
----> $08cfe830: MOVEM.L   (A7)+,D0-D7/A0-A6
----> $00010000: SUB.B     D7,D7
----> $00090000: ORI.B     #$00,(A7)+
----> $001f0000: DC.W      $ffff
Name: "DigiBoosterPro"   
LONG-READ from 00000034                  PC: 089C7A5E
USP:  08CD97CC SR: 0014 FLSW: 01010200 TCB: 08CD7798
Data: 00000000 0976ACB3 00000000 00000001 00000000 00000000 00000000 00000000
Addr: 00000000 08C3C788 00000000 08CD9830 00000000 08CD9870 08141BF0 08CD97CC
Stck: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Stck: 00000000 08CD7798 00000000 00000000 00000000 00000000 00010000 00000000
Stck: 00000000 08C636AC 00000000 00000000 00000000 00000000 00000000 00000000
Stck: 00000000 08C4CB50 08C4CB4C 05000000 000008C4 81000020 00000008 00E8FFFF
Stck: 08C48054 FF40FF71 542AA6E1 00038E16 08C48054 08C4F5A4 08CD9868 00000000
Stck: 08CD9864 00000000 00F967B4 00002000 646F7075 735F6C69 73746572 00000000
Stck: 00000000 00004B04 00007B38 00000000 00000000 00000000 00000000 00000000
Stck: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
----> $089c7a5e: MOVE.L    $0034(A0),-(A7)
----> $08cd7798: BTST      #$fe,D0
----> $00010000: SUB.B     D7,D7
Se comment below.

2. Just toggling 8bit to 16bit
SnoopDOS

Code: Select all

 Count Process Name       Action     Target Name                 Options Res.
 ----- ------------       ------     -----------                 ------- ----
 :
 :
 10    DigiBoosterPro     *Open      ENV:Sys/ahi.prefs           Read    OK  
 11    DigiBoosterPro     #FINDINPUT  23148CB,  207648F,  21F125 RAM     OK  
 12    DigiBoosterPro     #READ       2076991,  8C6EE0C,         RAM     OK  
 13    DigiBoosterPro     #READ       2076991,  8C5242C,         RAM     OK  
 14    DigiBoosterPro     #READ       2076991,  8C6EE0C,         RAM     OK  
 15    DigiBoosterPro     #READ       2076991,  8C52498,         RAM     OK  
 16    DigiBoosterPro     #READ       2076991,  8C6EE0C,         RAM     OK  
 17    DigiBoosterPro     #READ       2076991,  8C524C8,       1 RAM     OK  
 18    DigiBoosterPro     #READ       2076991,  8C6EE0C,         RAM     OK  
 19    DigiBoosterPro     #READ       2076991,  8C524EC,       2 RAM     OK  
 20    DigiBoosterPro     #READ       2076991,  8C6EE0C,         RAM     OK  
 21    DigiBoosterPro     #READ       2076991,  8C5254C,       2 RAM     OK  
 22    DigiBoosterPro     #READ       2076991,  8C6EE0C,         RAM     OK  
 23    DigiBoosterPro     #READ       2076991,  8C5257C,       2 RAM     OK  
 24    DigiBoosterPro     #READ       2076991,  8C6EE0C,         RAM     OK  
 25    DigiBoosterPro     #READ       2076991,  8C525AC,       2 RAM     OK  
 26    DigiBoosterPro     #READ       2076991,  8C6EE0C,         RAM     OK  
 27    DigiBoosterPro     #READ       2076991,  8C525DC,       2 RAM     OK  
 28    DigiBoosterPro     #END        2076991                    RAM     OK  
 :
 :
CyberGuard

Nothing produced.... So no hit, i guess. However it behaves strangely after (this time)


Both scenarios either garbled the mouse pointer, thew a Software Failure - And left the machine in an unstable state.


I'm thinking..... Reading the CyberGuard output in the loading of an XM-file. Stack usage? How much stack should DigiBoosterPro 2.21 need? Maybe I have too little. The default icon has 8192 bytes. Seems a bit low, but I don't know the inner workings of how the code is written.
A switch from 8/16bit doubles/halves the memory usage. So there might be some maths going on and of course memory accesses. I guess there is no FPU involved.
How about MMU? I'm running the Phase5 68060 and 68040 libraries (which I believe is correct) and then the mmulib from AmiNet mmu.library upon that. Maybe that's stupid?

EDIT: A side note: I managed to screenshot the DigiBooster screen using sgrab before and after toggle (even though sgrab crashed after saving the file to RAD:) i can see the "Free: " part of the top right info box change dramatically when toggling 8bit to 16bit, before it (the machine) starts misbehaving.

Before: 11409K
After: 10720K

So it does _something_ before it dies on me. Probably the doubling of the allocation of memory used for 8 v.s. 16 bit mode.
daxb
AFF Profi
AFF Profi
Posts: 612
Joined: 10.11.2002 - 01:42

Re: DigiBoosterPro 2.21 - Crash in various weird ways when toggling 8bit/16bit

Post by daxb »

The memory usage (Free, Used) will change when switching 8/16bit. That should be normal behaviour.

CPU libraries could be a problem. So if you use mmu.library, then you should also use its 680x0 CPU libraries and not mix with Phase5 libs. The MMULib installer should know CyberStormPPC.

About stack just test with higher values. I use StackAttack2 and therefore the stack is 32k. However, I guess its not a stack issue.

The SnoopDos log seems a bit short. While or after reading ahi.prefs it stops. Here it does some more things like loading audio modes, audio.device and some ENV variables.

Just in case. Don't rename DigiBooster and its directory. Don't copy DigiBooster somewhere.
AiO
Grade reingestolpert
Grade reingestolpert
Posts: 4
Joined: 29.09.2022 - 14:35

Re: DigiBoosterPro 2.21 - Crash in various weird ways when toggling 8bit/16bit

Post by AiO »

Yeah. I removed AUDIO from the DEVS:DOSDrivers. Probably explain that....

Hm... I have tried re-installing DigiBoosterPro and everything. But yes.... I will try to remove the MMULib stuff.... The original stuff from Phase5 should suffice.

I know I've been running the 68060.library from MMULib more-or-less successful at some point in history. Maybe that's an option too. Thanks for your input. I'll get back to you with a progress report.
AiO
Grade reingestolpert
Grade reingestolpert
Posts: 4
Joined: 29.09.2022 - 14:35

Re: DigiBoosterPro 2.21 - Crash in various weird ways when toggling 8bit/16bit

Post by AiO »

OK. Removing MMULib-stuff (all of it, i think) did not help either. Same symptoms.
daxb
AFF Profi
AFF Profi
Posts: 612
Joined: 10.11.2002 - 01:42

Re: DigiBoosterPro 2.21 - Crash in various weird ways when toggling 8bit/16bit

Post by daxb »

I would test: Rename/move the Phase5 library and install mmu.library and the CPU libraries. I would recommend to use the installer that is provided with the MMULib package because of you CyberstormPPC card. As far as I know (not sure) it needs some quirks workarounds and the installer knows it. If you system works with the MMULib stuff (the libraries) I would recommend to use its debug tools (MuForce, MuGuardianAngel, ...)instead of Cyberguard. OS 3.2 will install MMULibs by default as far as I know but the latest version you can get on Aminet.

However, if you use Phase5 libs or MMULibs you should check if your AHI installation is correct. You may investigate your working/not working systems for differences. That should help to find the cause of the problem. It seems your are more or less the only one with this DigiBoosterPro behaviour. At least I've never heard about it somewhere else.
Post Reply