Here's a gotcha that ruined my day.

The sequence of events was:

1. develop a  MapX demo app using MapX 3.5
2. on the morning of the demo, check that it still works
3. without rebooting, uninstall MapX 3.5
4. without rebooting, install MapX 3.5.2 (internally it calls itself MapX 3
. 52 . 43)
5. check that the demo still works
6. shut down
7. at the demo site, reboot on the PC and launch the app
8.  watch sadly as the demo dies with the message "cannot find file
mxintl30.dll"

I think that the lost file problem arose like this:

   Step 2 above runs MapX which uses mxintl30.dll.  This file gets a
non-zero usage count
   which seems to remain set long after the app terminates.

  In Step 3 UnInstallShield tells Windows to delete mxintl30.dll, but
Windows puts the request "on hold" until  the next reboot, because it thinks
the file is busy

  In Step 4 InstallShield sees mxintl30.dll as being already installed, so
does not bother to install the new version, although the current file is
actually on "death row"

  Step 5 works ok, despite the fact that mxintl30.dll is now marked for
termination with extreme prejudice

  Step 6 finally removes mxintl30.dll.

My mistake was to ignore the recommendation in the InstallShield message
issued at the end of step 3: "MapInfo Mapx 3.5 has been removed from your
system.  It is recommended that you restart your machine to remove files
that were in use during uninstall."

Lesson learned:

In Windows 95 (or 98) systems, when carrying out an uninstall/install
sequence to upgrade a software product, ALWAYS REBOOT after the uninstall
step.


David M Haycraft                          Phone/Fax:  61 + 2 + 6231 8104
Information Analysis Assocs  P/L   Mobile:     0412 001 134
ACN 085 516 105                          Email:
[EMAIL PROTECTED]
1 Cumming Place, Wanniassa
A.C.T. 2903, Australia                     A MapInfo Partner


----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]

Reply via email to