|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Novell Archives Archived content from Novell openSUSE support forums |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Hi,
I have a very specific question that probably can be answered by anyone with more knowledge than I. I am running 10.2, accessing my Novell Netware 4.1 network using IPX over ncpfs. I also installed ipxutils and mars-nwe (although neither installation is required to access my server and they don't seem to do anything anyway!). I am accessing some very old DOS programs, i.e., Foxpro 2.0 LAN and Wordstar 7.0 LAN (actually, the access is through Dosemu). Both work well EXCEPT I seem to be having file locking or user access issues. Foxpro requires the use of a file called foxuser.dbf, which doles out user access to the database and controls file locking. I think I am having a problem with this file. If I open Foxpro on my server using Linux everything works just fine. HOWEVER, all other users cannot get in. If I close Foxpro, access for others works just fine. Run FP again -- other users get locked out. There is a pattern here. My DOS mounting point is on my drive, and have used the Yast SUDO to give the ncpfs utilities root access. I tried giving foxprol.exe root through SUDO but no avail. Anyone have any ideas? Thanks Alan |
|
|||
|
The foxuser.dbf and foxuser.fpt are stored in the Foxprolan home
directory (ie: /foxprol ) Under DOS environtment the Fox dBase family programs works with the c fox and the c applicat two-different folders. First containfoxpro.exe libraries and other foxpro runtime files. In c applicat forexample only leave your application files like tables, forms, menus and reports, indexes, etc. To run the application you should include the fox path into autoexec.bat sentence. With this the foxuser.* files still working into fox folder. Now, if these don't exist, when application start, the foxuser.* files are created into application folder. Then, check the path of these foxuser.* files and see the date. If are recent, backup and delete both foxuser.* files. Start the application and fox will create new ones. Alan O escribió: > Hi, > > I have a very specific question that probably can be answered by anyone > with more knowledge than I. I am running 10.2, accessing my Novell > Netware 4.1 network using IPX over ncpfs. I also installed ipxutils and > mars-nwe (although neither installation is required to access my server > and they don't seem to do anything anyway!). > > I am accessing some very old DOS programs, i.e., Foxpro 2.0 LAN and > Wordstar 7.0 LAN (actually, the access is through Dosemu). Both work > well EXCEPT I seem to be having file locking or user access issues. > Foxpro requires the use of a file called foxuser.dbf, which doles out > user access to the database and controls file locking. I think I am > having a problem with this file. If I open Foxpro on my server using > Linux everything works just fine. HOWEVER, all other users cannot get > in. If I close Foxpro, access for others works just fine. Run FP again > -- other users get locked out. There is a pattern here. > > My DOS mounting point is on my drive, and have used the Yast SUDO to > give the ncpfs utilities root access. I tried giving foxprol.exe root > through SUDO but no avail. > > Anyone have any ideas? > > Thanks > Alan > > |
|
|||
|
Foxpro is set up properly, in separate directories, etc. I have been
using this set up for many years, and when I log into Linux on my machine, it works wonderfully. The problem is that once I start running what is usually a shared program, for some reason Linux is locking the program or directory so that it cannot be shared. My Netware server is set up so that most of the files in the /apps/foxpro2 directory, i.e., the program and setup files, can be SRO, but the data files in /data/dbase are SRW (they can be written to). However, as soon as I start the programs in Linux, all files become RO and cannot be properly executed. I cannot explain this. Thanks Alan |
|
|||
|
Your across-platform schema is not helping in this case.
You mean fox and app are stored and hosted in a IPX NW4 server, right? You can do a lab: install a old 486 or PII machine the free DR-DOS -called Caldera DR-DOS- and try load the fox application. The DR-DOS comes with native IPX client. If the problem persist the the problem still in the NW4 box. If the problem is suppered then the problem can be in emulator utility. |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|