[WriteLog] Need advice on Writelog installation conventions on Windows 7

[Dick Green WC1M]

Not true, Rick. My copy of writelog.ini is stored in c:\windows, and WL
updates the parameters in it just fine. I checked the security permissions
on c:\windows and c:\windows\writelog.ini and they're not special -- owner
is "trustedinstaller" and permissions appear to be restricted pretty
heavily. In other words, I don't think permissions have been altered from
the Windows 7 default.

I always run as an administrator, which may explain it.

Also, there are no files in
c:\users\<username>\AppData\Local\VirtualStore\Windows (where <username> is
the name of my account.

73, Dick WC1M

> -----Original Message-----
> From: Rick Tavan N6XI [mailto:rtavan at gmail.com]
> Sent: Thursday, July 04, 2013 2:21 PM
> To: AL9A
> Cc: Writelog user group
> Subject: Re: [WriteLog] Need advice on Writelog installation conventions
> on Windows 7
> 
> On Win 7 you absolutely can not store writelog.ini in c:\windows. All
> writes from non-admin users are forbidden and even reads get redirected
> to c:\users\<username>\AppData\Local\VirtualStore\Windows. I built a
> shortcut to that ridiculous path name and put it on my desktop. I can
> edit writelog.ini there easily and yes, changes persist. That's also
> where wl.exe stores writelog.ini when it exits, of course. I can live
> with this.
> It's having to switch back and forth between user and admin IDs and
> having to move around the results of Convert CTY that aggravates me.
> Some of this is Windows 7 silliness and I believe some is inconsistent
> or inadequate path name management in writelog functions and utilities.
> 
> /Rick
> 
> On Thu, Jul 4, 2013 at 11:13 AM, AL9A <al9a at mtaonline.net> wrote:
> 
> > I don't have Win7 on my PC, but since WL is installed in the root
> > directory the Virtual store path is not a problem. Check for your
> > writelog.ini file at C:Windows.  If the file is there check that it is
> > the correct one by making a small change in some parameter and see if
> > that change is in effect when you start WL. Or setup a new keyboard
> > shortcut in WL then save configuration and save the log file. Now
> > check the ini file and see If the new shortcut is shown in the
> > shortcuts section. If so, this is your active ini file.
> >
> > 73,
> > Gary AL9A
> 
> 
> --
> Rick Tavan N6XI
> Truckee, CA