>>>Bringing this vfp Invalid Seek Offset problem over to this forum, now that the problem is isolated better. Is there an equivalent under NT to the Files = # issued in the config.sys of DOS for Win9x? I think I may be losing file handles under NTWS, is there a way to request more?
>>
>>(1) CONFIG.NT takes a FILES= statement just like CONFIG.SYS under Win9x
>>(2) You can custom configure the operating environment for each app through its PIF
>
>Thanks Ed - We don't use PIFs here any longer, in general. But here's what is currently in the config.nt, after a lot of REMs about TSRs and whatnot:
>
>
>dos = high,umb
>device=%SystemRoot%\system32\himem.sys
>files = 20
>
>I don't know squat about NT, but this doesn't look right. We don't even use himem.sys with Win9x here anymore, and the # files looks way too small.
>
>Any suggestions? This is a Dell 300/64 I'm testing on, the best I can get for a test machine at the moment.

The CONFIG.NT on this box is simpler:

FILES=150

I make detailed adjustments to apps on an app by app basis with PIFs, since that lets me control how the app is isolated, how much I'll let it consume, and in the case of DOS apps, what kinds of memory resources it will find. The detailed adjustment to _DEFAULT.PIF are inherited by things spawned in a new VDM where you've not established parameters for use.

My base server here has hundreds of files open at times, but I won't think about NT with less that 128MB for pragmatic reasons, and 256MB is more realistic in a server envronment.