Tux Paint rebooting WinXP!?

SDL Development
1

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!?

Thx!

-bill!

2

In the meantime… anyone here have ANY clues!?

Buggy DirectX drivers? Can you build him a version of SDL that forces
windib and waveout instead of directx for video and audio?

–ryan.

3

That is a common behavior of XP. My first thought upgrade to Win2K. Second
thought upgrade to Linux. :slight_smile:

Otherwise there’s a solution to apps causing a reboot in XP. You have to go
into Startup and Recovery where there are options for setting the shutdown
and reboot options when (not if) XP crashes.On Friday 07 October 2005 16:51, 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.

–
Kai Ponte
www.perfectreign.com

linux - genuine windows replacement part

4

In the meantime… anyone here have ANY clues!?

Buggy DirectX drivers? Can you build him a version of SDL that forces
windib and waveout instead of directx for video and audio?

I cannot, as I don’t have XP at home. :^/ No time to figure out how
to cross-compile the libs again, either.

Here are some details he sent about his system, though:
(minus stuff like floppy drive specs. ;^) )

— begin —

I’ve had a look at the machines in question. For graphics they use the Intel
826X /G/ GV/GL chipset family. To answer the questions

Does it do this in Windowed mode?
Yes

Does the configuration program work?
Yes

Is it being installed by a “Poweruser”,
Yes

and then run by that same “Poweruser”?
Yes

Info regarding the model computer is detailed below:

System
IBM ThinkCentre S51
8172-XXX (TBA)

Processor
Intel Pentium 4 2.80GHz with Hyper Threading Technology

Motherboard
PXE Enabled, Wake on LAN Support, 800MHz Front Side Bus

Memory (RAM)
512MB DDR SDRAM

Chipset
Intel 915G

Video-Graphics Card
Integrated Intel Graphics Media Accelerator 900

Sound Card
SoundMAX Cadenza

Operating System provided and installed by Vendor
Microsoft Windows XP Home license, Microsoft Windows XP Professional

Link to Vendor website
www.ibm.com/solutions/au/publicsector/edu_sol/t4l

— end —

Any ideas? Anyone have any WinDIB-compatible SDL DLLs that would work
with Tux Paint that I can have him try?!

Thanks!

-bill!On Sat, Oct 08, 2005 at 01:10:39PM -0400, Ryan C. Gordon wrote:

5

Any ideas? Anyone have any WinDIB-compatible SDL DLLs that would work
with Tux Paint that I can have him try?!

If someone can build SDL on Windows, you should go into
SDL12/src/video/SDL_video.c, and comment the ENABLE_DIRECTX section.
Then do the same in SDL12/src/audio/SDL_audio.c.

Rebuild and see if it works.

–ryan.

6

John Popplewell built the SDL test apps into a suite of Win32 EXEs
and threw a README.txt inside explaining how to use them. (testver, etc.)

He seemed to suggest that an env. var. could be used to force SDL to
use wavout and windib (if I recall the names correctly).

Anyway, I’ve passed it along to the “Tux Paint crashes WinXP” person
and the “Gem Drop X doesn’t draw right on WinXP” person, to see what
results they get.

Wish us all luck!On Mon, Oct 17, 2005 at 03:55:31AM -0400, Ryan C. Gordon wrote:

Any ideas? Anyone have any WinDIB-compatible SDL DLLs that would work
with Tux Paint that I can have him try?!

If someone can build SDL on Windows, you should go into
SDL12/src/video/SDL_video.c, and comment the ENABLE_DIRECTX section.
Then do the same in SDL12/src/audio/SDL_audio.c.

–
-bill!
bill at newbreedsoftware.com
http://www.newbreedsoftware.com/

7

He seemed to suggest that an env. var. could be used to force SDL to
use wavout and windib (if I recall the names correctly).

You can, but several people have told me they don’t work on Windows (SDL
grab env vars from the wrong place or something), so I didn’t want to
risk you forcing it to windib and having it pick directx anyhow.

Keep us posted.

–ryan.

8

He seemed to suggest that an env. var. could be used to force SDL to
use wavout and windib (if I recall the names correctly).

That should be ‘waveout’ :slight_smile: If the driver name is wrong, you get a
"Couldn’t open audio: No available audio device" error from ‘loopwave’.

You can, but several people have told me they don’t work on Windows (SDL
grab env vars from the wrong place or something), so I didn’t want to
risk you forcing it to windib and having it pick directx anyhow.

Keep us posted.

–ryan.

I’ve heard the same, but not seem it. To be sure, I tested it first.

The test programs ‘testvidinfo’ and ‘loopwave’ show which driver they
are using. In a command-prompt on XP Pro and Win2K the environment
variables seem to work fine.

Looking forward to the results myself :slight_smile:

cheers,
John Popplewell.On Mon, Oct 17, 2005 at 06:27:57PM -0400, Ryan C. Gordon wrote:

SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

9

To be specific, this seems to be related to which window you use to
run the program. If you open a command prompt, set the env variable
there, and then use that same command prompt to run the program, it
should work fine.

I’ve seen someone open a command prompt, set the env variable, and
then use the GUI to launch the program (doubleclick). That, of course,
didn’t work - environment variables set in a command prompt window
ONLY affect that window.

If you need users to be able to doubleclick to launch and still use a
specific driver, you need to set it globally. On XP, right click the
My Computer icon, select Properties. Go to the Advanced tab on this
window and click on Environment Variables. There are two groups of
settings here, the top one is for the specific user who is currently
logged in, and the bottom one is for all users at this computer. Have
them set the env variable in the global one and it should take even if
they doubleclick to launch your app.

Hope this helps!

-JustinOn 10/17/05, John Popplewell wrote:

On Mon, Oct 17, 2005 at 06:27:57PM -0400, Ryan C. Gordon wrote:

You can, but several people have told me they don’t work on Windows (SDL
grab env vars from the wrong place or something), so I didn’t want to
risk you forcing it to windib and having it pick directx anyhow.

The test programs ‘testvidinfo’ and ‘loopwave’ show which driver they
are using. In a command-prompt on XP Pro and Win2K the environment
variables seem to work fine.

10

Forgot to add that you will probably need to reboot the system for the
new environment variables to be loaded, sorry.

-Justin

11

Forgot to add that you will probably need to reboot the system for the
new environment variables to be loaded, sorry.

Thanks for mentioning this technique for making it permanent.

On XP and 2K you don’t need to reboot, but you do need to close and
reopen any running command-prompts for the change to take effect.

Not sure about non-console apps. Still, I don’t think reboots are going
to be a problem here :slight_smile:

The SDL test programs I bundled are shell-oriented (all will open a
shell if not started from within one) so setting the environment
variables in a shell and playing with them is the most useful scenario
until the cause of the reboot is identified,

cheers,
John Popplewell.On Tue, Oct 18, 2005 at 01:03:44PM -0400, Justin Coleman wrote:

-Justin

SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl