Win98 and 2k environment settings... 1

[fatboy2]

Durn microsoft! We did a massive PC upgrade to run some new VB/SQL stuff, and ended up with win2k on our new machines. Now my Clipper compiled dbase programs won't run because of a lack of file handles. I have tried this on win98 and can reproduce the crash.

I realize this is an environment problem, but I don;'t know exactly how to fix it. I have issued the set files and set buffers command from the dos prompt, and then tried to execute the program, with the same result. I even created a config.sys on my 98 machine with files and buffers in it, but that resulted nothing also.

I should have been a pig farmer.

 

[MiggyD]

We've had the db converted to Access format.

Only thing I can suggest is create a link (LNK) file. Then, right click the link (shortcut) and change the properties around in it like: program cannot detect windows, check off HMA and set all conventional memory to highest number listed instead of auto.

other than that, I don't know what to recommend.

--MiggyD

 

[fatboy2]

THx md.

I put it in VFP. Not crazy about doing that, but like everybody else, I have to pick my battles, if you know what I mean.

 

[MiggyD]

Yep, I knows what you mean partner.

Well at least now it's more portable than before.

 

[dbMark]

This is a problem experienced by all the DOS-based database programmers. Until recently I had always thought that all code such as "Files=" were stuffed into CONFIG.SYS, but WinNT and I guess also Win2000 and WinXP put it into CONFIG.NT, probably in the WinNT (or similarly named) main system directory.

What really stunned me was that WinMe did it differently. MS decided that a user would only need 30 file handles. Duh? Maybe they though WinMe was incapable of heavy duty work? By 1999 or 2000 there was a lot of memory sitting in all those systems, no need to be miserly! Fortunately they graciously allowed that if a user (such as all of us) wanted to add more file handles, the user should run MSCONFIG, go to SYSTEM.INI and in the 386Enh section add "PerVMFiles=50" (any number you want but no higher than 225) to get additional handles in the DOS "Virtual Machine" window.

 

[dbMark]

On reviewing your post, I think typing in FILES=nnn from the DOS prompt wouldn't do anything. Surely too late for those commands to take effect. Such values are most likely set at the computer boot or perhaps when the DOS window is opened.

Oh, on a side note probably not applicable here, Windows XP has the capability to run in "compatibility" mode. Right click on the desktop icon, select an earlier mode, such as Windows 95, etc. and see if that makes a difference. This doesn't sound like your problem, but can't hurt...

 

[dbMark]

"Too many files open error" does mean you need more file handles, I just found this Clipper thread:

thread290-179083

In win2K you have to put the following:
in config.nt (located in c:\winnt\system32)
files=100
buffers=40

in autoexec.nt (located in c:\winnt\system32)
Set clipper=F75 (or E:75 or whatever your app requires)

 

[Seagaze]

DbMark:
I have no knowledge of writing programs and little experience in computer problem solving.

The program I have is called RentRoll and I bought it about 10 years age. Very in-depth rental property management worked great for a very long time. I upgraded my computers to WinME and WinXP. Once that upgrade was completed and RentRoll was re-installed it would not allow the moving or changing of tenant information.

The error message was “Program module Netuse, code line number 1218, error info “open error Nmrrtsta.dbf Need more handles and clippers.” The program gave a solution, which was add lines to the config file which did not help.

I call the company tech department to help with this problem and was told that I own the rights to the program but no rights to tech help. Also, I found out that the company dose not sell the program anymore, they only lease the program outrages price.

I was then told that I could get help should I lease the new version for a minimum of 3 years. Needless to say I was very discouraged by this information. I then made several attempt at solving this to no avail.

Now to you, dbMark, your post to fatboy2, was absolutely on track. I followed your post tips to place the codes in the 386Enh and the proper config file. Well, dbMark it worked like a charm. Many thanks.

Seagaze (Tech User)