home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!news.univie.ac.at!scsing.switch.ch!univ-lyon1.fr!ghost.dsi.unimi.it!rpi!usc!cs.utexas.edu!bcm!lib!sphm42.sph.uth.tmc.edu!sph0301
- From: sph0301@utsph.sph.uth.tmc.edu
- Newsgroups: comp.os.ms-windows.apps
- Subject: WPWin5.2 problem
- Message-ID: <sph0301.165.728146594@utsph.sph.uth.tmc.edu>
- Date: 27 Jan 1993 14:56:34 GMT
- Sender: usenet@lib.tmc.edu
- Organization: Univ. of Texas School of Public Health
- Lines: 32
- Nntp-Posting-Host: sphm42.sph.uth.tmc.edu
-
- Having exhausted the resources of the WP support group, let me try the
- wisdom of the net...
-
- I've been trying for a week to get WP for Windows 5.2 working on my home
- PC. Version 5.1 worked fine. The new version installs without a hitch
- but when I try to start the program all I get is a window saying "Error,
- can't load shared code DLLs". I've reinstalled it four times already,
- trying various things and the same error comes up. What's been tried
- already:
- 1. First install was an update from 5.1; next three installs
- were from scratch after deleting all WP files.
- 2. Tried both basic install and custom install
- 3. Disk space, memory and resources are suficient (29Mb free,
- 4700K free, 83% free respectively)
- 4. wp{wp}.env file points to the correct directory for shared
- files
- 5. Both the main wp directory and the shared directory are in
- the path
- 6. Tried loading the shared code manually by running wpcdll.exe;
- that worked okay but the program still wouldn't start.
- 7. Varified the correct sizes/dates of the shared code dll files
- with the WP support rep
- 8. Tried installing the program on my work PC just in case one
- of the diskettes was bad - no problem there.
-
- I'm out of ideas and so is WP Support. Has anyone else encountered anything
- like this? The PC is a 386 with 4Mb RAM. Another curious thing: the first
- time through the install program it asked whether I wanted to modify the
- autoexec file - since then I've never seen that question again even though
- I restored autoexec to it's original state between each install.
-
- kate
-