in my experience, Win10, P9, the correct place to change is registry

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Borland\Database 
Engine\Settings\SYSTEM\INIT

Hth

Am 28.06.24 um 19:16 schrieb Peter:
> Leslie, what is the name of the "cfg" file?
> 
> Peter
> 
> 
> On 06/28/2024 04:32 a.m., Leslie wrote:
>> Hi Ivan,
>>
>> In the world of UAC, it really is not a good idea to leave the BDE 
>> installed under the Program Files folder, nor is it a good idea to 
>> have the BDE use the Registry because you will run into many issues 
>> around UAC and access rights/permissions.
>>
>> Years ago now, I wrote a replacement BDE installer that incorporates 
>> the BDE 2/4GB diskspace fix, it sets the BDE to store/maintain its 
>> settings inside the cfg file thus ignoring the Registry after initial 
>> installation, plus it moves the BDE outside of the Program Files 
>> folder and into the C:\BDE32 folder.
>>
>> The installer allows you to override its default behaviour if you must 
>> but really it is a set and forget. The beauty is that you can run it 
>> even after the BDE has been installed and it just works.
>>
>> So for one last time, you can find the BDE installer on this page: 
>> https://www.all2ezy.com/pages/developer_downloads.php
>>
>> The reason I say one last time, is that this is likely one of my last 
>> msgs to this group as I wont be going over to google groups.
>>
>> Oh and for the record, MAXFILEHANDLES is really a legacy setting going 
>> back to Windows of yesteryear, I leave it set to 128 and have never 
>> had an issue in 20+ years.
>>
>> FWIW
>> Leslie.
>>
>>
>> On 28/06/2024 6:51 PM, Ivan wrote:
>>> Hi Kevin,
>>>
>>> I don't say, that it has something to do with MAXFILEHANDLES in the 
>>> BDE. I
>>> say, that it solves that error message (simply it can be a subsequent 
>>> error
>>> of something - e.g. smb, which copes with network mapping ...).
>>>
>>> I've tried the solution (I think it was from Liz - 03/01/2023). Changes
>>> MAXFILEHANDLES to whatever (e.g. 128, 255) - nothing changes. The same
>>> error, that there are No More Files (and it follows something with IDAPI
>>> (this is BDE).
>>> Then I've tried to reinstall Pdox9 - nothing changes.
>>> Interesting was, that Pdox9 Runtime had no problems - only Pdox9.
>>> The user I know uses only Runtime - and had minor problems.
>>>
>>> OK I've try to solve it. Each step after pc-restart.
>>> Changes every settings within BDE (nothing changes), change the 
>>> IDAPI32.cfg
>>> file - nothing changes, tried to use something old from archive - 
>>> nothing
>>> changes.
>>> Then it was impossible to work with Pdox9. Even to open a table (No more
>>> files message with the first table I've tried to open).
>>>
>>> And so on.
>>>
>>> Then I've look at the OpLocks (just to try something) - nothing changes.
>>> Then I've set some values in the registry - nothing changes.
>>> Rewrite my scripts - nothing chages. They said - everything is OK 
>>> (even the
>>> values, but fails to open a table on a local HD - not network).
>>>
>>> Then I start to delete parts of the BDE registry settings and install 
>>> the
>>> BDE. At the beginning - nothing changes.
>>> As I've deleted the whole BDE directory and the Rgistry BDE entry 
>>> CONFIG01,
>>> then reinstall the BDE - the day was saved - everything works normal.
>>> Of course I've to change some settigs (e.g. the LANGDRIVER, ...).
>>>
>>> Now I've a "german Pdox9" e.g. the Menus are in german language - 
>>> before I
>>> had the english version (how this happen - don't ask me - but this is no
>>> problem for me).
>>>
>>>
>>> I hope, this is the solution, but maybe the future will think different.
>>>
>>>
>>> I know about google, but ther's very little to read.
>>>
>>> Perhaps I start something about "how to save Pdox" - something with
>>> smb1, 2,
>>> 3. Or if it's possible to make pdox a open source and then ask the 
>>> MariaDB
>>> (open source MySQL), if it were possible to include Pdox to MariaDB
>>> (something like now Pdox can handle DB and DBF, then MariaDB would have
>>> their database (the same as MySQL) and for local network purposes there
>>> could be a Pdox table version).
>>> Just ideas, which could be presented later. Now I've much to do - at 
>>> least
>>> until the end of the first july-week.
>>>
>>> Hope MAXFILEHANDLE will be silent.
>>>
>>> Greetings
>>>
>>> Ivan
>>>
>>> "Kevin Zawicki" <numberjack@wi.rr.com> schrieb im Newsbeitrag
>>> news:667e4210$1@pnews.thedbcommunity.com...
>>>>
>>>>
>>>>
>>>>>
>>>> one have to reinstall completely the BDE
>>>> <
>>>> What did you base that on?
>>>>
>>>> What was the MAXFILEHANDLES setting in the BDE? (under system-int)?
>>>>
>>>> What is it after re-install?
>>>>
>>>>
>>>> Note the usage of these groups is moving to:
>>>> https://groups.google.com/g/thedbcommunity
>>>>
>>>>
>>>> "Ivan" <ivan.moro@web.de> wrote:
>>>>> One of my users got an earlier here mentioned "MAXFILEHANDLE Limit"
>>>>> error
>>>>
>>>>> message and send me an screenshot.
>>>>>
>>>>> I've worked half a day to find out, what's wrong.
>>>>>
>>>>> The solution is, one have to reinstall completely the BDE. But it's 
>>>>> not
>>>>
>>>>> enougt to delete the whole BDE directory (e.g.):
>>>>>
>>>>>    Programs (x86)\Borland\Common Files\Bde
>>>>>
>>>>> You have to delete the following whole rgistry entry too (at least
>>>>> within
>>>>
>>>>> value "Database Engine" the data entry "CONFIG01" has to be deleted -
>>>>> otherwise it won't work):
>>>>>
>>>>> for 64 bit:
>>>>>    HKLM\SOFTWARE\WOW6432Node\Borland
>>>>>
>>>>> for 32 bit:
>>>>>    HKLM\SOFTWARE\Borland
>>>>>
>>>>> After you've deleted that registry entry, no Pdox work (temporarily).
>>>>> You have to reinstall completely the BDE (e.g. from the install CD).
>>>>> After
>>>> =
>>>>>
>>>>> this is made, the error message disappears and everything works. Be
>>>>> shure,
>>>> =
>>>>>
>>>>> you use the idapi32.cfg and then you have to proove the paramter
>>>>> settings
>>>>
>>>>> for BDE (e.g. DATE Format, INIT section, ...) and save them to the
>>>>> idapi32.cfg file.
>>>>>
>>>>> Wish everyone a nice day.
>>>>>
>>>>> Ivan
>>>>>
>>>>>
>>>>> ---
>>>>> Diese E-Mail wurde von AVG auf Viren gepr=C3=BCft.
>>>>> http://www.avg.com
>>>>>
>>>>
>>>
>>>
>>> ---
>>> Diese E-Mail wurde von AVG auf Viren geprüft.
>>> http://www.avg.com
>>>
>>