- #Driver dell optiplex 170l windows 98 driver
- #Driver dell optiplex 170l windows 98 upgrade
- #Driver dell optiplex 170l windows 98 full
- #Driver dell optiplex 170l windows 98 pro
So I don't think that the problem is coming from the read/write/modify rights.
#Driver dell optiplex 170l windows 98 full
To prevent problems coming from the rights, now I'm doing my tests with a "Domain Admin" account, and I verified that this account has full control on the folder where the bdf files are. When you do get it fixed, let us know what did it.ĭbMark (in Ohio USA) RE: Error 111 FoxPro DOS 2.6 with Windows XP TimoP5 (Programmer)Īt the begining, I was testing a "limited" account user. Hard to really say what your fix will be, but these are some ideas to check out. Physical problems: Sometime a faulty NIC (network interface card) or netowrk cable is at fault but that's pretty rare. There's also a bug with XP clients that was fixed in XP Service Pack 1. "Opportunistic Locking" on the XP to server can affect this.
#Driver dell optiplex 170l windows 98 driver
Or maybe the language driver is different? Was the CDX (table's compound index) changed by another database language so that FoxPro wants to rebuild the index? It needs exclusive access to do that. Does your program write tables or other files to the C:\ root directory?Īnother idea is that something about the table has changed and the program tries to change the table but can't because it's been opened with SHARED or maybe NOUPDATE.
If the user doesn't have Administrator rights, XP will not let them write to the root directory of the computer.
If it's a work or temp file on the local computer, then it could be a rights issue of the person logged onto the XP computer. I wonder which files it's having problems with, are they the same ones all the time, or random ones? Are the files on the server or on the local computer? If it's on the server, verify the user or his group does have read/write/modify rights on that table/memo/indexes or folder(s). Make sure your user or his group is listed there with rights to read/write/modify.įolder and/or file security rights: Are these different users on the different computers? If so, have one of the users who you know it works on his computer go and log in to the problem XP. Shared folders: Remember, when a directory or folder is shared, you have to go into the Permission button to enable writing. RE: Error 111 FoxPro DOS 2.6 with Windows XP dbMark (Programmer) 21 Oct 05 19:35ĭoes the XP client have read/write/modify rights to those tables? Right now, we are lost, so any help or clue will be really appreciated. We tried to add FILES=150 to config.nt, we tried to use instead of cmd.exe, We tried to work with all the different compatibility modes, we tried to adjust memory size with no success. It seems that the problem is coming from Windows XP on the client side.
#Driver dell optiplex 170l windows 98 pro
Here are the results:ġ-FoxPro on a Windows 2000 server, Windows XP Pro Client: Everything working perfectly.Ģ-FoxPro on a Windows 2003 server, Windows 98 SE Client: Everything working perfectly.ģ-FoxPro on a Windows 2003 server, Windows XP Pro Client: Let's say 90% it's freezing saying error 111, and 10% it's working OK.
This problem is strange because it's always freezing at a different line in the code. FoxPro freezes saying "Error 111, Not able to write in a read only file" (This is the English translation of the French error message). Since we are running Windows 2003, it's not possible to go trough all the process. So basically, it's a loop doing "open the file, read the file, print data, deleted printed data, close the file". This program is reading a few dbf files (maybe 200 files) to print a sales report. Now everything is working correctly excepting 1 program.
#Driver dell optiplex 170l windows 98 upgrade
Everything was running fine until we decided to upgrade the server to a Windows Server 2003. We are using FoxPro DOS 2.6 for several years. First of all, I want you to excuse my English.
0 kommentar(er)
