Why does FileMaker Pro 2.1 lock on startup when running under Windows 95?
This is due to a conflict with 3 network files – CLARISNW.DLL, NETBIONW.DLL and NOVELLNW.DLL. If you delete these three files which are located in the program directories, FileMaker will run. If you did not change the default install program directories when SuperSearch was being installed on your hard drive, delete these three files from the following directories that have been made on your hard drive: C:\SI-SFX, C:\SI-RFMUSIC, C:\SI-XV, and C:\SI-MUSICAUDITION. FileMaker Pro can also lock on startup when the font file becomes corrupted. If this happens to you, delete CLARIS.FNT from the C:\WINDOWS\CLARIS directory to fix the problem. This file will be recreated when you restart FileMaker Pro. .
Related Questions
- How do I install the PowerEdge Expandable RAID Controllers Power Console remote client utility on a console client running Windows 95?
- Is it true that there are problems running Windows 95 Disk Defragmentation with JFW for Windows 3.0?
- Why does FileMaker Pro 2.1 lock on startup when running under Windows 95?
