🚀 go-pugleaf

I place my reply in public, since it may be of public interest.
It also should be corrected in public if not correct.

In article <2vg0vc$biq@access3.digex.net> riker@access3.digex.net writes:

>Now, I went into WIN.INI, found all references to the common apps, and
>changed the path to a different drive.  Then, of course, I also copied
>all the program files for the common apps to the new drive and path.

>The long and short is, Word For Windows could not find the common
>applications. 

I once had a related problem, where W4W 6.0 seemed unable to read my 
modifications of WIN.INI. 

The reason?

W4W 6.0 (or it may be Windows 3.1 itself, I'm not sure) does not read 
WIN.INI. Instead it reads another file, named REG.DAT, which is not ASCII. 
And when you modify WIN.INI, REG.DAT is not updated! 
What human person could guess this? 

So what do you do to get REG.DAT updated? 

You just delete delete the file (REG.DAT). Then, the next time you start 
Windows, REG.DAT will be regenerated, using your modified WIN.INI.

After this treatment, the system should work. At least it did for me (but my 
problem, as I said, was related to this one, not identical)

Implementing automatic updating of REG.DAT after modifying WIN.INI should be 
very easy, checking, for example, the date of saving WIN.INI.


Best Wishes!

Jan Gunnar