Windows 7 & 8 Help
It used to be that many WriteLog users reported that it is best to install WriteLog in a location other than C:\Program Files (x86) for both Windows 7 & 8 (including 8.1). However, the author of WriteLog, Wayne W5XD, suggests that WriteLog be installed in its default location. Here is what Wayne wrote:
What WriteLog is designed to do on Windows 7 (and 6 for that matter) is to leave UAC turned ON. It MUST be installed as an Admin (as all installs must be with UAC ON).
And it should install into C:\Program Files (x86)\WriteLog…or a similarly protected directory.
I do NOT recommend disabling UAC for WL either from the Windows 7 system, nor by installing it into an uncontrolled directory.
I recommend WL be run for normal contest operations using a NON-admin account. (Not specific to WriteLog: You really, really do NOT want to be running WL
or web browsers or anything else in admin mode these days. You only want to turn on admin when you KNOW you need to.)
But the country files, etc. are in admin-only directories. How to upgrade them? A)You can login as an admin and run the “Convert CTY to WL” and use its
Download button. B)When logged in as a non-admin, you can run “Convert CTY to WL” with a right mouse “run as administrator”. For reasons that escape me right now, my Win7 does NOT offer “run as admin” with a right mouse from the Start Menu, but DOES offer it when I use File Manager to Right mouse on the ReaCty32.exe file in Program Files. It is also a one-time operation to create your own shortcut while in the non-admin account to the ReaCty32.exe and then update that shortcut’s properties/Advanced to “run as admin”. (It also escapes me right now why I have not built the ReaCty32.exe to use UAC to insist on being run only as an admin. I know it does not do that now, and I know I have considered this, but I cannot remember why I did not. I think I will try this in a beta test.)
The main WL executable has a “File/Web Update…” button that immediately fails when run as non-admin. The solution is the same as for the country Files. Either login as admin and run WL from there, or right mouse, “run as administrator” when in the user account. On my Win7 system, my main WriteLog V11 icone DOES offer a “run as admin” (I have no idea why this one does and Convert CTY does not).
The WriteLog start menu has a Edit WriteLog.ini button that “knows” where the virtual store is for WriteLog.ini. (Note that different user login accounts have DIFFERENT writelog.in files under UAC.) This start menu button is, I believe, broken if you have turned system UAC off.
I followed Wayne’s advice when I bought my Windows 8.1 PC in April 2014. I created a standard user account that did not have admin rights and installed all my programs from this account using “install as administrator” and supplying the admin password. WriteLog and all my other ham programs installed correctly in their default location. Please note that MMTTY now installs in C:\ham\MMTTY directory by default.
W7 Professional and WriteLog by Tom, WX4TM
I received my new Dell W7 Professional 64 bit PC last Saturday morning (ordered on 04 Mar) and, of course, dropped what I was doing, and began the effort to set it up and install MMTTY and Writelog asap.
My W7 comes with two program directories: C:\Program Files and C:\Program Files (x86). There’s also a ProgramData directory which, I later determined, has no apparent files associated with MMTTY or WL.
A default install of MMTTY and Writelog put both programs in the ..(x86) directory. (Earlier, I mistakenly reported that MMTTY originally defaulted to the normal C:\Programs Files\).
During the install, an instance of the infamous Writelog.ini file was put in C:\Windows and C:\Users\yourname\AppData\Local\VirtualStore\Windows. I found that changing anything in the latter had no affect on Writelog and that the system would not let me change/save anything to the C: Windows\Writelog.ini File and that the MMTTY plug-in would not work at all.
I queried the Writelog email reflector with my problem and got half a dozen responses and a telephone call, all with simular suggestions: Install both MMTTY and Writelog directly in the C: drive. So I did that and the MMTTY Plug-in worked perfectly however I was still unable to make any change to the Windows\Writelog.ini file. Though I could still make changes to the C:\Users ..WL file, it continued to have no affect on Writelog that I could distinguish! This was contrary to what everyone was telling me. So I began looking very hard at the C:\Windows\Writelog.ini file.
In order to this, one has to have Administrator privileges. I had made sure of that during initial set-up of the PC. So I right clicked on the ‘Writelog.ini’ file;
clicked on’ properties’; then the ‘Security’ Tab. This displayed a list of Group or user names in the top screen and a list of permissions in the bottom screen.
Clicking on a group or user name displayed the associated permissions in the bottom screen. I noted that only the “system” user had ‘write’ permission in the bottom screen. So I set about setting both Administrator and Users (me, also listed as administrator) with all permissions. There is a ‘to change permissions, click Edit’ tap with which to do this. This took several tries and it wasn’t until I did a full system hard reboot that the changes took effect. Then, wa, la, I could edit and save changes to the c:\windows\writelog.ini file. I was now happy with my Writelog/MMTTY set up.
I’ve always liked to do ‘default’ installs of programs. That’s the way they’re ‘supposed to work’. Today, I got to thinking. “If I’d had ‘write’ privileges to the WL ini file from the beginning, would the MMTTY plug-in have worked with the default install?”. I found the answer to be YES!
After uninstalling MMTTY and Writelog, deleting all associated files and folders including both .ini files that were not deleted during the uninstall process, I began a re-install of each program. I first installed MMTTY. It automatically went to the ..x86 Program Files directory. I then set up MMTTY with all settings and ran it ‘standalone’.
Once I was satisfied that MMTTY was working properly, I began the install of WL. It too installed in the ..x86 Program Files Directory. I started WL; browsed for, and opened an existing RTTY log (BARTG). At this point, I had not opened a RTTYrite window. I saved the log, then saved configuration, and checked the status of the WL ini files. There was one in C:\Windows but there WAS NOT one in the C:\Users….. path! Back at the C:\Windows\Writelog.ini file, I opened it and deleted the only contest entry under the ‘[Recent File List]. Saved it and, wa la, it took it. The system remembered that I had ‘write’ privileges! To check, I opened WL and it was not showing any ‘recently used contest’ files.
For some reason I suspected it would be better to move a copy of the MMTTY Plug-in file to the Writelog\Programs\ directory (I had done this earlier too). Then I attempted the install. It seemed to go just fine. I opened Writelog; opened the ‘recently used’ program file (BARTG); then opened a RTTYrite Window, clicked on ‘TU Type’ and, there it was. MMTTY was listed. Clicked on it and the MMTTY Control panel came up and worked just fine. Saved the file. Saved the configuration with RTTY checked. Closed everything and brought it back up.
WRITELOG AND MMTTY are now working, on my W7 Professional PC, just fine with DEFAULT installs.
It was time, now, to install all the contest modules that’s not included with the basic WL install. Again, I suspected (no verifiable reason) that these files needed to be activated (installed) from within the Writelog program directory. So I moved a copy of WLCM_DL1EFD and SM6SRW install files to Writelog where I then ‘clicked on’ them to install. Each went just fine, as best I can tell. I did not compare, individually, to confirm if ALL of the contest modules were installed.
Next, it was time to address the reported problem with making a Cabrillo File. I went through the normal process and experienced absolutely no problem. It worked normally, just fine.
Summary: Lots of wierd things here. I know I had successfully set myself up as ‘administrator’ when I set up the new PC. Then, why, on default installs, did the system establish two INI files as many have experienced and not let the plug-in work correctly? And why, only after changing security settings on just ONE file in windows, did the next default install work correctly with only one INI file in the proper place and the Plug-in work correctly?. Obviously there’s lots of quirks with W7 and obviously there’s much to be learned. Further, there appears to be perhaps considerable differences between W7 Home and Professional OS systems.
Though I hope my experience might be helpful to others, one must consider that because of the newness of W7 and my lack of experience with it, you’ll need to just chalk this up to one person’s experience; and remember that ‘your mileage’ will vary – maybe alot?
Cabrillo File Creation Problems
If you are using Windows 7 (or Vista) and have trouble generating a Cabrillo log from WriteLog (top section of the Create Cabrillo File window is grayed-out , the following is from Joe, K0BX:
“I had a problem with the Cabrillo File every since I got a new computer with VISTA installed.
The Drop-Down list boxes in the Cabrillo File data entry window were empty. I had to edit the Cabrillo file in notepad adding the proper categories.
So what I did was to move a copy of the file file:///C:/Program%20Files/WriteLog/Programs/LogSubmission.ini
There was an older version in the Virtual Store, but after I replaced it, the Cabrillo File data entry window drop-down boxes are now populated.