Path: utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!geac!contact!zooid!dve From: dve@zooid.UUCP (David Mason) Newsgroups: comp.windows.ms Subject: Re: Editor... Message-ID: Date: 10 Oct 90 00:48:31 GMT References: <90280.143318CC65MGTW@MIAMIU.BITNET> Organization: here Lines: 30 CC65MGTW@MIAMIU.BITNET writes: > It would be virtually impossible. > Every Windows app you install has its own unique parameters it puts into > WIN.INI. These parameters are found by a simple search of the file, and > the parameters are read in. > Since there are hundreds of applications, and each application can have any > number of parameters, there is virtually no way to have ae editor any more > efficient than the undocumented SYSEDIT.EXE. > Even then, there are very few WIN.INI parameters you would ever have to adjus > and then only once. I think the Windows manual does an adequate job. > -Chris I don't agree. Perhaps Microsoft could design an editor for WIN.INI that could have parameters by a new program. Admittedly it would be complex, but it would be better than the current solution. You can take a Mac out of the box, plug it in, install a couple programs, and it works fine. To fine tune a Mac you just use a few control-panel type programs. Of course Windows is inherently more complex because it runs over DOS, but I am in touch with users of Windows who've barely touched a computer before and the last thing they want to do is wade through a text file, trying to figure out all the lines to change, add, or delete, after reading all the .TXT files it is necessary to read to fine-tune Windows. Microsoft could at least provide a control-panel type interface for the basic WIN.INI commands, such as the COM parameters. As it is I consider Windows only to be really useable in an organization that has a support person available, and that's from experience because during the first couple weeks of our new Windows department I spent a fair amount of time in WIN.INI fine-tuning. And that was just on 286s, on 386s it becomes more complex.