Invalid page fault

[HAWSSTKS]

Have been successfully using Word Perfect 7 for the past year. For unknown reason(s) upon loading a message appears: Wpwin 7 caused an invalid page fault in module shell32.DLL at 0167:7 cb1946. I uninstalled WP 7 and reinstalled. It worked faultlessly one time. At next start-up the same message appeared. I am running Windows 98SE. Any suggestions?

[MRT]

Hi HAWSSTKS,
Try this:

Problem

Trying to start WordPerfect 7 under Windows 98, the following error may be encountered: "Wpwin7 invalid page fault in module SHELL32.DLL @ 0177:7fce23b3."
Other addresses may include:
0157:7fce23b3
016f:7fce23b3
0257:7fce23b3


Answer:

The NT Enabled release of WordPerfect corrects this issue.

To find the version release of WordPerfect 7 check the CD for the VOLINFO.TXT file:
This will be on the root of the WordPerfect CD.
1. Insert the WordPerfect CD in the CD rom drive. Exit out of the install program.
2. Start | Programs | Windows Explorer
3. Scroll down to the CD Rom drive (Under All Folders).
4. See if the VOLINFO.TXT file is on the CD it will have a notepad icon.
5. Double click on the file and it will open in NotePad.
6. Check the version release ( NT Enabled is 7.0.2.19) Date is 11/05/96.

The NT Enabled release is no longer available for purchase from Corel Customer Service. To upgrade to the latest version of the Corel WordPerfect Suite, call Corel's order center at 800-77COREL (800-772-6735).


Details:

The errors only occur under Windows 98 ™.
The errors only occur with versions less than 7.0.2.19(NT Enabled).
The WordPerfect 7 Office Professional (7.0.1.9) has a file called COWIN7.TXT that will have a date 06/28/1996. The original version of WordPerfect 7 (7.0.0.2327) has a file called WPWIN7.TXT. This date will be 05/02/96. All of the files can be opened in NotePad.

[HAWSSTKS]

Thanks MRT. Well, it turns out that my old version of Word Perfect has the file WPWIN7.TXT, and when purchased specified that it was for Windows 95. Since it worked flawlessly on 98SE (as other earlier software has) I assumed some other problem, possibly remedied by a "patch" or other "fix." Alas, it is not to be -- at least I think that is what you are telling me. Looks like only the new high-price version is the solution. Thank you for sharing your knowledge.