As title say since the installation of the update 3 i can't be able to "test" the BoingBall screensaver, if i try to click on "Use" in ScreenBlanker Prefs my Amiga will freeze instantanely.
@samo79
I just tried test in the screensavar prefs on my SAM Flex 800 and the BoingBall screensaver works. Clicking use doesn't cause any problems. However, it was already an active module on my system. I tried moving it to inactive and selected use. When I reopened the screensaver prefs, test no longer works; it just goes to a black screen and returns. I moved the BoingBall module back to active and tried use and save but test no longer worked. I had to select save with BoingBall active and reboot to get it working again. I noticed that I still had the screen preferences for the BoingBall module set to 1024 16bit because i never updated it since getting a bigger monitor. I also notice that the BoingBall screensaver got ugly with Update3. The bouncing ball gets lines through it like the image movement isn't properly synchronized with the display. Something has apparently gone wrong with BoingBall when running Update3.
xenic wrote:@samo79
I just tried test in the screensavar prefs on my SAM Flex 800 and the BoingBall screensaver works. Clicking use doesn't cause any problems. However, it was already an active module on my system. I tried moving it to inactive and selected use. When I reopened the screensaver prefs, test no longer works; it just goes to a black screen and returns. I moved the BoingBall module back to active and tried use and save but test no longer worked. I had to select save with BoingBall active and reboot to get it working again. I noticed that I still had the screen preferences for the BoingBall module set to 1024 16bit because i never updated it since getting a bigger monitor. I also notice that the BoingBall screensaver got ugly with Update3. The bouncing ball gets lines through it like the image movement isn't properly synchronized with the display. Something has apparently gone wrong with BoingBall when running Update3.
I tried to follow your example so I moved all blankers to be inactive, clicked use, reopened the window and the "Test" button wasn't clickable. I moved the boing blanker back, clicked use, reopened and CPU got stuck at 100% for a while, the little example was black (off course) but after some seconds it worked again. The blanker itself looks the same though. I got an A1 with a 9250.
BoingBall blanker works just fine here on my Update 3 machine, which is very similar to yours, a 733MHz Sam flex with 1GB and Radeon 9250.
I can only assume that there may be some errant files on your machine causing such problems. Whether these be libraries or configuration files, I have no idea, but perhaps trying a clean installation may fix your problems.
Ok i did a clean install from scratch --> Fresh Update 1 then Update 2 and finally the Update 3
Now as you say all works as expected ( ), no freeze at all using this screensaver, altrough many users experience hangs using it after installing the Update 3 on their "very-used" AmigaOS 4.1 Update 2 so i think some "small and hidden" problem still somewhere ...
I don't doubt there is a clash somewhere, but finding it is the hard part. Unfortunately, what constitutes a "well used" system, is usually one that has been hacked to death.
At least it works for you now, and I'll wager it has fixed your other problems too.
I can confirm there is a bug in the BlankerModule. Though I was unable which blanker it was. First I was downloading a file in OWB, Came back after five minutes system had frozen. I at first suspected OWB but grabbed a log which told otherwise. Had heard of it but now I had got a blanker crash!
I was also testing the new MUIOWB. Left it alone for a few minutes. Came back and another freeze had occured!
So have a log. BTW what's with the 68K stack and instructions? Something has corrupted!
Hidden Text - Click to Show :
Dump of context at 0x020991B0
Trap type: DSI exception
Machine State (raw): 0x0000F030
Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on]
Temporary stack trace:
#0: in module Kickstart/intuition.library.kmod+0x0008A5B8 (0x01A1EFF8)
#1: in module Kickstart/intuition.library.kmod+0x0001CDC4 (0x019B1804)
#2: in module Kickstart/intuition.library.kmod+0x00051D40 (0x019E6780)
#3: in module Kickstart/intuition.library.kmod+0x0001D4D0 (0x019B1F10)
#4: in module Kickstart/intuition.library.kmod+0x0001D634 (0x019B2074)
#5: in module Kickstart/intuition.library.kmod+0x00040EA4 (0x019D58E4)
#6: in module Kickstart/intuition.library.kmod+0x00040DF0 (0x019D5830)
#7: 0x7F2AC890
#8: 0x7F5675DC
#9: in module Kickstart/dos.library.kmod+0x00020A14 (0x01926A14)
#10: in module Kickstart/kernel+0x000416F0 (0x018416F0)
#11: in module Kickstart/kernel+0x00041770 (0x01841770)
#12: 0x00000000
Crashed process: BlankerModule (0x54EAB3B0)
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a load operation
0: 01A1EFF4 542CEC70 59032290 020A2AB4 6FF81DD8 00000000 00000000 021A3674
8: 3F5242EF 00000000 542CED38 54EAB3B0 48842084 41820014 00000000 577A4800
16: 02260000 00000000 02260000 00000000 5561EDC0 5A3050D8 00000000 7F567510
24: 5A305328 00000000 02270000 00000000 6FF814D0 6FF814D0 00000000 00000000
CR: 28842082 XER: 40004378 CTR: 0181C890 LR: 01A1EFF4
DSISR: 40000000 DAR: 00000084
FP0 : 0000000000000000 4082400000000000 4074A00000000000 0000000000000000
FP4 : 0000000000000000 4070FCCCC0000000 406DF999A0000000 41E0000000000000
FP8 : 4060000000000000 4032000000000000 3FF4000000000000 406FE00000000000
FP12: 3FF0000000000000 4081D00000000000 AC7BEFF7DAEAFCFA 1C8D57BCF7EEEEDA
FP16: BC0BBD75F7F77BF8 B0BFFFEEF11FFE7F FBFFFBCEFF7AEC7F 7D77BB9F9DB5FE39
FP20: BA1F8FAB5EE4EE63 FB1B5F2E35DDFC16 3F5F13FA5DFA7EDC EFB59FD0BE54FDB2
FP24: 783EDFEFFDC9EE9B BEDFBFAEFDE6EEFF A74FF7DFE5DFFDE6 B61F6FEECFFEFFF3
FP28: 7F7B6EADCFDFD679 FC5A3BAE277CCCBF BC5FEBBE5E61EEFB 9F1001C38FFFFEF9
FPSCR: 82004000
Dump of context at 0xEFAAD000
Trap type: DSI exception
Machine State (raw): 0x0000F030
Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on]
Temporary stack trace:
#0: in module Kickstart/intuition.library.kmod+0x0008A5B8 (0x01A1EFF8)
#1: in module Kickstart/intuition.library.kmod+0x0001CDC4 (0x019B1804)
#2: in module Kickstart/intuition.library.kmod+0x00051D40 (0x019E6780)
#3: in module Kickstart/intuition.library.kmod+0x0001D4D0 (0x019B1F10)
#4: in module Kickstart/intuition.library.kmod+0x0001D634 (0x019B2074)
#5: in module Kickstart/intuition.library.kmod+0x00040EA4 (0x019D58E4)
#6: in module Kickstart/intuition.library.kmod+0x00040DF0 (0x019D5830)
#7: 0x7F2AC890
#8: 0x7F5675DC
#9: in module Kickstart/dos.library.kmod+0x00020A14 (0x01926A14)
#10: in module Kickstart/kernel+0x000416F0 (0x018416F0)
#11: in module Kickstart/kernel+0x00041770 (0x01841770)
#12: 0x00000000
Crashed process: BlankerModule (0x54EAB3B0)
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a load operation
0: 01A1EFF4 542CEC70 59032290 020A2AB4 6FF81DD8 00000000 00000000 021A3674
8: 3F5242EF 00000000 542CED38 54EAB3B0 48842084 41820014 00000000 577A4800
16: 02260000 00000000 02260000 00000000 5561EDC0 5A3050D8 00000000 7F567510
24: 5A305328 00000000 02270000 00000000 6FF814D0 6FF814D0 00000000 00000000
CR: 28842082 XER: 40004378 CTR: 0181C890 LR: 01A1EFF4
DSISR: 40000000 DAR: 00000084
Well isn't directly related, but the fonts problem with MUI OWB happen again even with a clean OS install, previously this problem never happen so it must be MUI OWB for sure, time to open a new ticket for MUI OWB on bugs.os4depot
Heard of this. Did you run OWBB or the OWB launcher? I've only ran the atter. My install isn't fresh either. I wouldn't call it clean but it's not to dirty.