For Windows XP, when a user selects LOGOFF and MS Notepad is running
with unsaved data, Notepad posts a messagebox that states "Unsaved
Data." About 10 seconds latter the system posts an END PROGRAM dlg
box stating that the system cannot be shutdown because an application
is waiting for user input.

Any info on what messages to process and what functions to call to
duplicate this behavior would be appreciated.

I have already looked at WM_ENDSESSION and WM_QUERYENDSESSION but do
not understand how these can be used to produce the behavior sought..

Thanks in advance for any information.

Is it possible to register somehow with Windows so that you can
monitor the creation and destruction of window handles?

I have a win32 application (win2k or winxp) where I am logging non-
permanently-persistent data that must be available to multiple
applications -- at most 1 producer to write, several consumers to read
-- & am trying to rethink my implementation of the lower-level
storage, & could use some help understanding some of the gory details
of what Windows does and does not offer.

Basically the producer produces an infinite stream of (raw bytes +
metadata) in a series of chunks, but because of practical storage
concerns, the chunks need to disappear when no one "cares" about them
any more -- e.g. I plan to reference count the chunks with "claims"
from either the producer or the consumers, & when the reference count
reaches 0, they deallocate. Producer typically puts a claim on only
the last 64K or so of data; consumers may hold random individual
chunks for longer.

I need to support both using shared memory and disk, and I need to be
robust against application crashing so that if any of the producer or
consumers die, the shared storage needs to be left in a consistent
state. All producer/consumers are on the same CPU.

I assigned a laptop to do overnight server duty. I don't want the monitor to be
on. When I close the lid the windows 2000 wants to go to standby allthough I have
disabled any standby or hibernate. It is running Windows 2000 pro. I am afraid
teh lcd will burn out. I disabled power management in BIOS but it still want to
go to standby when I close the lid. It displays a message "blah blah modem
device driver is preventing to go to standby". If I leave it that way and lid
closed the processor start feverishly processing standby messages and slows teh
systems 10%%.

When link builds binaries, the full path name of PDB files are coded
into EXE files.

For most applications, this is true. As for binaries released by
Microsoft, only the basename of the binary is revealed. Examples
below.

Would someone please help about which linker options or something to
set
to eliminate the full path info from the built binaries?

Examples:

Hi,

although the following window procedure causes a tooltip to appear
when the user puts his cursor over a label on Windows Vista, the
"Could not create label tooltip" error message box appears on Windows
XP.

Does anyone know why? I am using the OpenWatcom C/C++ compiler.

Many thanks.

phiroc

LRESULT CALLBACK WindowProcMainWindow( HWND hwnd, UINT message, \
WPARAM wParam, LPARAM lParam)
{

switch(message)
{
case WM_CREATE: