Re: [Tuxpaint-devel] Tux Paint rebooting WinXP!?

[John P. <jo...@jo...>]

On Fri, Oct 07, 2005 at 04:51:20PM -0700, Bill Kendrick wrote:
> 
> Hello SDL and tuxpaint-devel folks...
> 
> 
> I just received this from an asst. principal of a school that's used
> Tux Paint at home, and is hoping to use it at his school, except...
> 
>   > I installed Tux Paint on the IBM S51's at school (XP Pro) -
>   > installation went fine - no errors etc. - and when I attempt to start
>   > it up (by desktop icon or through the Programs menu) the computer just
>   > reboots. No error messages to indicate problems - just reboots. The
>   > only thing I didn't do was install the optional rubber stamps. I have
>   > used both the Zip file and the Windows installer versions of the
>   > download with the same result.
> 
> He didn't say, but I can only assume he's using the latest (0.9.14) version.
> I've asked for any further details he can send about the WinXP version.
> 
> In the meantime... anyone here have ANY clues!?
> 
Hmm. Tuxpaint 0.9.14 works fine here on my fully updated, XP Pro SP2
machine.

I believe XP Pro defaults to rebooting the machine in the event of what
was formerly known as a "blue screen of death" by default. One of the
first things I do is change this:

 - Open the control panel and double-click on the System icon.
 - Select the "Advanced" tab.
 - Locate the "Startup and Recovery" section (at the bottom of the
   panel) and click on the "Settings" button.
 - Locate the "System Failure" section (bottom half of the panel).

I usually un-check the "Automatically Restart" and the "Send an
administrative alert" check-boxes, but leave the "Write an event to the
system log" checked. I also make sure that the "Write debugging
information" drop-list is set to "Small memory dump (64 KB)".

 - Click on the OK buttons, back to the control panel.

I *think* this will stop that behaviour and might give an opportunity to
see what is actually going on.

Of course, a user program shouldn't be able to crash the OS so
presumably it is some sort of audio/video driver problem.

Perhaps the machine is running some kind of "lock-down" software that
prevents the screen resolution from being changed?

Does it do this in Windowed mode?
Does the configuration program work?
Is it being installed by a "Poweruser", and then run by that same
"Poweruser"?

cheers,
John Popplewell.


> Thx!
> 
> 
> -bill!
> 
> 
> ------------------------------------------------------- This SF.Net
> email is sponsored by: Power Architecture Resource Center: Free
> content, downloads, discussions, and more.
> http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________ Tuxpaint-devel mailing
> list Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>