Update 3 ScreenBlanker --> BoingBall freeze

samo79 · Post by **samo79** » Tue Aug 30, 2011 12:06 am

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.

My computer is:

Sam Flex 800
Radeon 9250
AmigaOS 4.1 Update 3 (of course)

xenic · Post by **xenic** » Tue Aug 30, 2011 3:55 am

@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.

hotrod · Post by **hotrod** » Tue Aug 30, 2011 5:59 am

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.

Post by **Rigo** » Fri Sep 02, 2011 11:06 am

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.

Simon

samo79 · Post by **samo79** » Fri Sep 02, 2011 12:28 pm

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 ...

Post by **Rigo** » Fri Sep 02, 2011 8:05 pm

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.

Simon

samo79 · Post by **samo79** » Fri Sep 02, 2011 9:02 pm

Yep, i would love to give you the exact step to reproduce but at some point i decide to erase all and restart from beginning.

Even MUI issues seems to be solved now (need more testing of course), there were some problem with MUI OWB fonts (on the GUI interface)

Aniway ...

Post by **Hypex** » Sun Sep 04, 2011 4:24 pm

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 :

Last STCK bit repeates forever

Another:

Hidden Text - Click to Show :

samo79 · Post by **samo79** » Sun Sep 04, 2011 8:11 pm

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

Post by **Hypex** » Mon Sep 05, 2011 3:41 pm

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.

Hyperion Entertainment Message Boards

Update 3 ScreenBlanker --> BoingBall freeze

Update 3 ScreenBlanker --> BoingBall freeze

Re: Update 3 ScreenBlanker --> BoingBall freeze

Re: Update 3 ScreenBlanker --> BoingBall freeze

Re: Update 3 ScreenBlanker --> BoingBall freeze

Re: Update 3 ScreenBlanker --> BoingBall freeze

Re: Update 3 ScreenBlanker --> BoingBall freeze

Re: Update 3 ScreenBlanker --> BoingBall freeze

Re: Update 3 ScreenBlanker --> BoingBall freeze

Re: Update 3 ScreenBlanker --> BoingBall freeze

Re: Update 3 ScreenBlanker --> BoingBall freeze