system shutdown

[cccc]

I would like milkdrop to elegantly respond to a WM_Close, WM_EndSession messages, ect. (or whatever???)

Currently when milkdrop is running and the ATX power supply tries to shut the system down it locks up. However when ALT-F4 or START:SHUTDOWN:OK is pressed it shuts down fine.

I want to use Winamp/milkdrop without a keboard or mouse.

[Krash]

May I suggest closing milkdrop before turning off your computer? It seems like a fairly elegant solution to me. ;) :p

- Krash

[cccc]

youve completely missed the point.

i want a machine with no keyboard or mouse.

i suppose i could write a master app that remotes winamp and intersepts the messages and handle it for milkdrop, but it would be much easier milkdrop just to handle the message properly.

it responds to "alt-f4" witout incident, so it is either igmoring the QueryEndsession or somthing like that.

when you hit the atx Powerbutton windows handles all the shutdown sequence. Winamp works like it should, so milkdrop must be the problem.

I suppose it could be a "BUG" and could submitted as a "bug report."

[Krash]

So, you're trying to set up the machine so that it boots, starts winamp with a playlist, and then starts milkdrop all on its own...

And then, when you push the power button, you want windows to shut everything down on its own, and then turn the machine off. Right?

But your problem is that Milkdrop crashes, and the machine just sits there, and doesn't shut down...

Simple solution, my friend - hold the power button down for a couple extra seconds - the whole machine turns off instantly - just like magic. None of that foolish waiting for things to shut down.

- Krash

[cccc]

Your description is 100% correct, and that is the current solution.

When you hold button down the ATX power supply turns itself off hard. just like a powerswitch.

However, besides being totally annoying to have to hold the button for 5 seconds, there is a reason to shutdown the computer. Windows likes to take that time to properly close the registry files and save a proper backup for rescue purposes, as well as set the bootup to skip the scan disk from an improper shutdown. And if it all works you dont wait for anything, it just turns off.

Even though the likelihood of corruption of the hard drive is very minimal. The poweroff solution is still very much, wrong. It would be far better for milkdrop to correctly handle itself.

I'm not by any means suggesting to take time from the other features, just address this issue by putting the proper message handle during the next build. It shouldn't take but 5 or ten minutes. but it will only be done if someone perceives it as a problem, which it is.

[Krash]

=]
good point.

now, where's Ryan?

RYAN!!!!

- Krash