We have a stand alone exe that we use to update Windows 95 machines
with the latest version of a home-grown application.  This program has
worked fine for 4 years now on a couple of hundred PCs...but last week
I found one PC that could not launch the program (it was working fine
for years...then all of a sudden stopped).

I have worked with Windows 95 for many years...but I haven't seen a
problem like this before.  When you click on the program and hour
glass comes up for about a second and disappears.  Checking the
background processes shows that it is not running.  I figured the file
was corrupted...so I replaced it with the current version...tried to
launch...same results.  Grabbed a file from another user that is
working...same results.  I decided to create a debugger version of the
program that logs all of the steps.  When I launched it on the PC it
worked perfectly...updated the software and ran.  The file that
wouldn't run was called "c2k_update.exe" my debugger was called
"c2k_update_debug.exe".  By shear luck I renamed the old file that
didn't work to "c2k_update_old.exe"...launched the file and it worked
perfectly.  I found that any executable named "c2k_update.exe" would
not launch on the PC.  Name it something else...it worked fine.

I thought it may be a McAfee problem but I could not find a block list
anywhere.  I disabled McAfee and tried "c2k_update.exe" and it still
would not launch.

Does anyone have any clue as to what could cause something like this?

One other note is that the very first thing my debugger program does
is splash a message box saying it have launched...when I run as
"c2k_update.exe" the message box doesn't even pop up.

Thanks for any help,
Ryan