WriteLog
[Top] [All Lists]

[WriteLog] OLE Problem with WL10.37 on NEW Installations

To: <writelog@contesting.com>
Subject: [WriteLog] OLE Problem with WL10.37 on NEW Installations
From: wbarber@adelphia.net (Bill Barber)
Date: Sun Mar 16 09:22:40 2003
As a newbie I have been wrestling with this problem thru many emails since
December with the list, Ron and Wayne.  I finally have it resolved.  Through
no recommendations that have been sent my way.

Firstly, I installed the 10.37 in early December.  I used if after the SS
Phone and it was very useful fo capture that contest and send in the file.
Again I used it in ARRL 10 meters and CQWW160 Phone and it was great.  Just
one problem.  No Packet Window display.  I continuosly got the "Can't open
the Packet Automation OLE" error message.

I got the updated file below and ran it.  I did COMREG.exe, etc.  (perhaps
this is what also created the problem- I may have run it twice).

I have upgraded to 10.39 and recently to 10.40 and no improvement.  I
decided to try it on a "clean computer".
I loaded my 10.37 Full, then 10.40J, checked operation.  Got the OLE error.
Ran comreg.exe.  NO OLE error anymore.  The Packet Window opens.

I went back to the original computer...Deleted writelog.ini, Deleted ALL the
entire PROGRAM file.  Reinstalled 10.37 Full, Installed 10.40J.  Ran
comreg.exe ONCE.  It now works!

Bill NE1B
----- Original Message -----
From: "Eric Smitt" <k9es@bellsouth.net>
To: <writelog@contesting.com>
Sent: Thursday, December 19, 2002 8:40 PM
Subject: [WriteLog] OLE Problem with WL10.37 on NEW Installations


Just got the fix from Ron K5DF
He said that if Writelog  10.37 is installed for the first time (not an
update of an older version), the program corrupts a file necessary to run
the packet.  I use a packet TNC but I believe the problem will also exist if
you are going to use a telnet port.

Download below address and put in your C:\Programs
 File.
    http://www.writelog.com/Downloads/wlogpktDiag.zip

Unzip it into WriteLog's\programs directory. It will replace
wlogpkt32.exe. Then run the comreg.exe program in there.

It corrected my problem.  You will open the Packet Window, and from the
Files tool (in the packet window), select the port that the TNC is
connected.  It worked on my station.
73's   Eric K9ES


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog

<Prev in Thread] Current Thread [Next in Thread>
  • [WriteLog] OLE Problem with WL10.37 on NEW Installations, Bill Barber <=