PRISM Forum - Message Replies


Topic: PRISM Questions and Answers
Topic Posted by: SRC (src_forum@alionscience.com )
Organization: SRC
Date Posted: Wed Jan 12 8:33:33 US/Eastern 2000
Topic Description: Welcome to the PRISM forum! Please feel free to post your questions and comments about the PRISM assessment software here.

Back to message list Show all replies About this forum

Original Message:

Posted by: Dave Ellis (ellis@ezlink.com )
Organization:Ellis Quality Engineering Services
Date posted: Sat Oct 7 21:28:05 US/Eastern 2000
Subject: Installation of InterBase
Message:
I downloaded the PRISM demo last week from your web site and then uninstalled it and InterBase. I received the PRISM software yesterday and tried to install it on the same computer - Gateway 650MHz laptop with 64M RAM. During the install, InterBase keeps saying I have it installed even though I did the uninstall to remove it. Once PRISM installs, I get "Unable to connect to common elements database. Terminating..." I have uninstalled and reinstalled PRISM and InterBase 2 times and still get the same response. I have had to install on my home PC - Gateway 333, 64M RAM and have had no problems. Any insight on what I should do on the laptop? I don't understand why after using the InterBase uninstall, InterBase thinks it is still installed. Thanks.


Reply:

Subject: InterBase Un-Install
Reply Posted by: Tammy T Sehn (rac_software@alionscience.com )
Organization: IIT Research Institute
Date Posted: Mon Oct 9 8:41:29 US/Eastern 2000
Message:
When uninstalling InterBase 5.5 using the 1.0 installation (currently being sold) one must manually remove "gds32.dll" from the windows system directory. The windows system directory depends on the operating system you are using. For NT machines it is labeled WINNT/SYSTEM32, and for most other computers it is labeled WINDOWS/SYSTEM After this file is removed you should not have any more problems uninstalling InterBase. If you do please contact the RAC and we will work directly with you to resolve any problems you are still encountering.


Reply to this message