>Ran into an odd situation with a customer running an older FPW 2.6 app on XP SP2 (32-bit). Application seems to be "invisible" -- i.e. main window does not seem to appear. No error is displayed about "divide-by-zero" nor problems with the 16-bit subsystem. Task manager shows the usual "wowexec.exe" and "foxw2600.esl" as if the program is running. Checked for CONFIG.FPW and CONFIG.FP files and haven't the usual culprits (e.g. SCREEN=OFF). When running the application on another computer (same copy of program from a share), the application shows up as expected. Anybody run across this situation before?
A few ideas:
1. Hmm, just noticed it's FPW, not FPD. I was going to suggest starting the program in a window, then pressing Alt-Enter to toggle for full screen, but that just fixes some display problems with FPD, not FPW.
2. Maybe you could try disabling themes, see if that makes a difference
3. If the app's starting from a shortcut, check that there aren't any funky non-default settings (FNDSs) in that shortcut. Or, bypass the shortcut, just try double-clicking on the app's .EXE from Windows Explorer
4. Check that the video driver is exactly correct for the hardware, and that there aren't any FNDSs in either the standard Windows configuration options, or any extended configuration pages for the specific driver (e.g. nVidia or ATI). Check for any special handling of 16-bit apps, any virtual desktop settings etc.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up