1  |   Order by index

Aug 21, 2005, 4:12pm

It appears that an "improvement" in the latest AW software includes a "crash
my browser on screensaver start". What is with that? I read on the release
notes that this is an improvement? I myself don't see the benefit in having
to ensure my screensaver is OFF (I have children who are not allowed to surf
the net regularily so my screensaver must remain for security), or ensure my
AW browser is minimized every time I leave my desk to grab a coffee. I don't
know how many times I forget to do this, and upon my return, AW is crashed
and needs to restart!! This.... imo.... is NOT an improvement, but a major
inconvenience, not too mention looks terrible in the program stability dept.
Is there anything that can be done with that?

Aug 21, 2005, 5:16pm

Just an FYI, but, screensavers are more harmful than good. The problem they
save the screen from is no longer an issue. You'll save more $ on your
power bill by just using the monitor shut off feature instead of a
screensaver.

- Com

[View Quote]

Aug 21, 2005, 8:45pm

Looking into it now on Beta.

Imagine once they find a solution it will be migrated to 3.6

--
- Mark Randall
http://zetech.swehli.com

[View Quote]

Aug 21, 2005, 8:59pm

Dunno if this still applies, but i'm sure Strike will feel free to
correct me if i'm off on this. If AW is running in OpenGL or DirectX
rendering mode and your screen saver is using the same ( DirectX or
OpenGL rendering ) that is why it crash's. I've seen many cases of 3d
games crashing during play due to a screen saver that decided to go
active and pull control of the graphics card away from it. dunno if
that's the case here but I'd only ask what screen saver specifically
were you running at the time =)

-Cj


[View Quote]

Aug 24, 2005, 4:19pm

Seems me and John Dough ended up posting towards each other in email so
for everyone's benifit i'm posting the threads in here. ( and maybe to
save Strike looking for a fix that wouldn't exist due to the problem
being on the client side )
-Cj


[View Quote] Re: Sceensaver Crashes Inbox

John Dough
to me

Thanx for the attempted answers.
I don't use any "fancy" downloaded screensavers which might require
OpenGL or DirectX etc that I'm aware of. The screensavers I use are only
basic WinXP screensavers that come default with the OS. (3D Pipes for
instance).

The AW error I get is something along the lines of ["ensure you close
AW before changing monitor resolution"] (sorry, I don't recall the exact
error wording). I have at no time changed my monitor resolution either.
I know some programs, like some games, automatically adjust your screen
resolution, so I can understand those crashing if it happened, but does
AW automatically adjust my monitor's resolution? I didn't think so. AW
runs on your current monitor settings and should therefore not crash due
to a resolution settings change (unless I changed my resolution).

For now, I guess I will continue to minimize AW when I leave, and only hope
they come up with a fix soon. ;)



CyBerJak to John:

3d pipes, 3d flower box, and a few others are all based on DirectX 6
or higher and the flowerbox in specific even has open gl extenstion
in it, i work for a pc manufacture, and we use those specific screen
savers to test the grahpics processor core for function only if a 3d
card were to crash using those we usually replace the graphics card at
that point in most cases.

also as one of the companies software advisors we advise customers who
have applications close because of a cscreen saver active during a
directX application cause Direct input for some cases hides usage of
the mouse or keyboard allowing the screen saver to go active, at which
point it crash's the game. this would apply to Active worlds as well i
bet if you set aw to software render mode it wouldn't do that even
with screen saver which suggests either you need to re-install directX
9c cause of a corruption or your screen saver is for some reason being
able to take the GPU ( graphics chip ) awa from aw and aw freaks out.
i know the error your talking about it usually happens more commonly
when a person switch's from 16bit to 32bit color or re-sizes their
desktop with aw running but i'm betting the screen saver is the
culprit as it does have minor control over desktop resolution and size

best reguards

-Cj


from: John Dough

More options 5:24 pm (1½ hours ago)
Thanx for the follow up CyBer! I have tried running AW in software
rendering mode as you suggested, and you're right, no crashing. I have
since updated my DirectX drivers, and tried OpenGL and Direct3D, and
to my surprise, no crashing... so far *grins*. Thankyou again for
your help :)) Also, I didn't realize I had posted a private email to
you on the NG's. I had meant to post a normal reply, but must have
zigged when I should have zagged ;) Thanx again!

Aug 24, 2005, 4:23pm

I've had AW crash the other day just from the "Blank" screensaver...

[View Quote] > Dunno if this still applies, but i'm sure Strike will feel free to correct me if i'm off on this. If AW is running in OpenGL or DirectX rendering mode and your screen saver is using the same ( DirectX or OpenGL rendering ) that is why it crash's. I've seen many cases of 3d games crashing during play due to a screen saver that decided to go active and pull control of the graphics card away from it. dunno if that's the case here but I'd only ask what screen saver specifically were you running at the time =)

Aug 24, 2005, 4:25pm

The only "modern" reason to use one is because on NT OSes (2000, XP, etc.) the dekstop can also be "locked" and require the user to enter his password to get back in.

[View Quote] > Just an FYI, but, screensavers are more harmful than good. The problem they save the screen from is no longer an issue. You'll save more $ on your power bill by just using the monitor shut off feature instead of a screensaver.

1  |   Order by index