Also, As the number of programs loaded on my NT4ws has grown, the registry size is such that there is a quite noticable impact on the speed of the boot process. When it was a virgin install, the machine would boot just like a Win9x clean machine, now it takes aWhhhiiiilllleeee. But, the point of leaving the registry Alone unless absolutely called for is good practice and with an abundance of INI access routines in the public domain (I think I have an ActiveX component at my site) to manipulate them, the registry would best be left undisturbed.
----- Original Message ----- From: "Lawrence Lustig" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 19, 2001 10:09 AM Subject: Re: Placement of RBASE.CFG and RBASe.INI files > > R:Base would do well to store dynamic data like > recent files in the > > registry, rather than in the INI file. That is > where most programs store > > this kind of information. The less you write to > important files like > this, > > the less chance there is of them being corrupted. > > I vote a big NO on this idea. Using the registry for > storage means that in > the event of corruption, the entire OS is open for > damage, not just the > setup for an individual program. Also, the registry > is much harder to edit > for people who need to do manual configuration or who > need to recover from > some kind of problem. > > I used the registry for storing settings in the > original version of R:Code, > and have moved away from it in later programs. > Sometimes the new ways are > not better ways. > -- > Larry > > > __________________________________________________ > Do You Yahoo!? > Find the one for you at Yahoo! Personals > http://personals.yahoo.com >
