shevett@mccc.edu (dave shevett) (03/07/91)
My company has written a fairly large (60,000+ lines) FoxPro application for a certain bottling company. The system runs great on standard PC's under various incarnations of DOS (except DOS 4.0 - memory hassles), and on our NetWare 2.12 ELS II system here in the office. One of our unforunate customers has Netware 2.0a. You know, the one without FCONSOLE and the shell is loaded via 'ANET3'? Wellllll, he can run our system (called LMP2) from the console. If he sits down and logs in (as the same user) from one of the workstations, the system gets to point x, and craps out with a 'TOO MANY FILES OPEN'. We have checked the following: Workstation CONFIG.SYS: normal (FILES=50, BUFFERS=30, this is fine) FoxPro configuration file (CONFIG.FP) - FILES=50 (again, normal) The first thing we tried was creating a SHELL.CFG file on the workstation, and throwing 'file handles=50' in it. This seemed to make a difference, in that the system got FARTHER, and then crapped out. Questions before the panel: Is there a physical limitation to the number of files this version of the shell can handle? If I up the file handles in the shell.cfg, I don't get any better results. It seems stuck at a certain level. Can I gen a new shell via NetWare 2.15 somewhere, and run that on the workstation? Will it connect with the ancient NetWare on the server? Has anyone else had problems like this - can run a program on the server, but can't run it from the workstation logging in under the same user? (note, the workstation has only 1 floppy. ALL software for the Net is stored on the server, including the FoxPro runtime). Answers, helpful hints, interesting propaganda welcome... shevett@mccc.edu - Dave Shevett