Date   

Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

John GM0OPS
 

On Thu, Oct 1, 2020 at 08:31 AM, Rick Ellison wrote:

s there a log file in the directory where the installer is located??

Also when the installer is running there are about 6 files that it asks if you want to over write what is currently on the system. Are you over writing the file or letting the newer ones rema

Hi Rick

Cant see any log file thats an issue if anyone knows its names but I did check by time and date to see if any other files had been generated.

The installer is basically failing before it gets to copying the 6 files. I take it thats the files listed in the setup.lst file

Regards
John


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

John GM0OPS
 

On Thu, Oct 1, 2020 at 08:27 AM, Michael Harris wrote:
C:\Radio\Logger32

Even when I overwrote Win7/64 Pro with Win10/64 Pro everything just showed up in the right place and ran.

If I remember correctly the installer does ask where you want to install too. I've not had to do a fresh install for ag
Hi Mike

It failed before it asked that part. Thats the issue as I would tell it to goto a clean DIR on C: drive called Logger32

Regards
John


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

Rick Ellison
 

John..

Is there a log file in the directory where the installer is located??

Also when the installer is running there are about 6 files that it asks if you want to over write what is currently on the system. Are you over writing the file or letting the newer ones remain??

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of John GM0OPS via groups.io
Sent: Thursday, October 1, 2020 8:03 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

 

Hi Tom

It is a clean folder and its the C Drive.  The LST file shows what should happen when setup is ran but the files are going into the C: windows dir, I have no control over that at all

I think I will just have to give up on Logger32 and move to another program that installs on Windows10. There does not seem to be a fix for this and to be clear to everyone

1. Its a clean download of V3.50
2. I have Logger32 dir in the C: drive
3. CCLeaner has been run for any reg stuff that needed cleaned
4. I run it as administrator
5. Anti-Virus software is off (windows defender)

I even tried version 3.49 from the site and it had the same issue. There is not much information on the actual issue on the web also I cannot find the logs to show what the issue is.

The joys of software

Regards
John
GM0OPS


Virus-free. www.avast.com


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

Michael Harris
 

Hi John,

I install all my radio applications in an appropriate folder in C:\Radio
in the case of L32 it is:

C:\Radio\Logger32

Even when I overwrote Win7/64 Pro with Win10/64 Pro everything just showed up in the right place and ran.

If I remember correctly the installer does ask where you want to install too. I've not had to do a fresh install for ages.

Regards,

Mike VP8NO

On 01/10/2020 09:03, John GM0OPS via groups.io wrote:
Hi Tom
It is a clean folder and its the C Drive.  The LST file shows what should happen when setup is ran but the files are going into the C: windows dir, I have no control over that at all
I think I will just have to give up on Logger32 and move to another program that installs on Windows10. There does not seem to be a fix for this and to be clear to everyone
1. Its a clean download of V3.50
2. I have Logger32 dir in the C: drive
3. CCLeaner has been run for any reg stuff that needed cleaned
4. I run it as administrator
5. Anti-Virus software is off (windows defender)
I even tried version 3.49 from the site and it had the same issue. There is not much information on the actual issue on the web also I cannot find the logs to show what the issue is.
The joys of software
Regards
John
GM0OPS


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

John GM0OPS
 

Hi Tom

It is a clean folder and its the C Drive.  The LST file shows what should happen when setup is ran but the files are going into the C: windows dir, I have no control over that at all

I think I will just have to give up on Logger32 and move to another program that installs on Windows10. There does not seem to be a fix for this and to be clear to everyone

1. Its a clean download of V3.50
2. I have Logger32 dir in the C: drive
3. CCLeaner has been run for any reg stuff that needed cleaned
4. I run it as administrator
5. Anti-Virus software is off (windows defender)

I even tried version 3.49 from the site and it had the same issue. There is not much information on the actual issue on the web also I cannot find the logs to show what the issue is.

The joys of software

Regards
John
GM0OPS


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

Tom Wylie
 

John. Are you installing it in a clean folder. Like. C:\Hamlogger.      Don't let it install in programme files.


Tom 
GM4FDM 

On Thu, 1 Oct 2020, 08:26 John GM0OPS via groups.io, <j.m.dundas=btinternet.com@groups.io> wrote:
Hi Rick

Thanks for the info. I followed each line and still the same issue. The cab files are being copied to the windows main dir but going by the lst file I would have thought they would have went to a temp file.

Also not sure if this is a VB6 issue with windows 10. I have been looking at event logs and things for any issues etc.

I installed another logging program to see if that would have any issues and it did not (its now been removed). I know it might be different db etc but worth checking.

The sad thing is that Logger32 was running on this machine until I had an issue that meant I required to do a reset.

So back to the drawing board on this one.

Regards
John
GM0OPS


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

John GM0OPS
 

Hi Rick

Thanks for the info. I followed each line and still the same issue. The cab files are being copied to the windows main dir but going by the lst file I would have thought they would have went to a temp file.

Also not sure if this is a VB6 issue with windows 10. I have been looking at event logs and things for any issues etc.

I installed another logging program to see if that would have any issues and it did not (its now been removed). I know it might be different db etc but worth checking.

The sad thing is that Logger32 was running on this machine until I had an issue that meant I required to do a reset.

So back to the drawing board on this one.

Regards
John
GM0OPS


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

Rick Ellison
 

John..

1.       Run CCleaner and clean your registry..

2.       Make sure you are installing it to a folder that is actively backed up by Onedrive or other drive backup

3.       Turn off your Anti-Virus

4.       Unzip the Logger32 install files to a new directory

5.       Make sure the directory you are installing it to is empty.

6.       Run the setup program for Logger32 using the Run as Administrator setting.

 

This has worked for me each time I have had To install/reinstall Logger32

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of John GM0OPS via groups.io
Sent: Wednesday, September 30, 2020 7:04 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

 

Hello Folks

Anyone else have any ideas on this issue at all? Starting to get a bit desperate as I need the logger32 working for the JTDX side of things and also of course for the two calls I run with.  I have tried numerous times to do the installation and all with they same issue as reported by the original poster.

Anything from anybody please 

Thanks
John
GM0OPS


Virus-free. www.avast.com


Re: Version 4

Bob
 

Mike, ver 4.0 is not scheduled for release until Christmas. While the basic look/feel is still the original Logger32, there are many subtle changes (hopefully enhancements), and a few completely feature/functions. It is quite stable, and very few problems are being reported. What it does lack is documentation. I would like to see a cooperative effort to have 21st Century on-line documentation.

You are more than welcome to participate in the ver 4.0 testing (without documentation) if you so desire. As a cautionary note, the invitation is for testing/evaluation the new release, not an invitation to enumerate you long list of "Gee, I wish Logger32 did this". We would also like you assistance/cooperation in the (soon to start) documentation efforts.

One other warning ... once you're on ver 4.0 there is NO rollback to 3.50.xxx Be sure to backup all your logs in ADI format and hide them under the mattress (just in case).

Still interested, then send a message to W5IFP, and Jim will send you an update file to upgrade to ver 4.0.132 When you're there, auto-update to the current release, and you'll be soaring with the eagles (while everyone else will still be scratching in the dirt with the chickens).

SeventyThree(s).

On 09/30/2020 1:53 PM Michael Harris via groups.io <mike.harris=horizon.co.fk@groups.io> wrote:


G'day,

How's progress on the beta testing of v4. Maybe it's time to grasp the
nettle and have a look.

Regards,

Mike VP8NO



Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

John GM0OPS
 

Hello Folks

Anyone else have any ideas on this issue at all? Starting to get a bit desperate as I need the logger32 working for the JTDX side of things and also of course for the two calls I run with.  I have tried numerous times to do the installation and all with they same issue as reported by the original poster.

Anything from anybody please 

Thanks
John
GM0OPS


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

mike tenore
 

I had the same problem yesterday! The error message said try running as
administrator.
Itried that three times yesterday. No luck!
I tried it again four hours ago and it finally worked?

It was on my lap top I was setting up to use for future portable /Sota/Pota
operations as I am in a HOA situation.

regards
Mike WB2LCW



Sent from my Galaxy Tab A


-------- Original message --------
From: "John GM0OPS via groups.io" <j.m.dundas@...>
Date: 9/30/20 12:39 PM (GMT-05:00)
To: hamlogger@groups.io
Subject: Re: [hamlogger] Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

Hi Robert,

I just logged on to the group to do a search and see if there was anything about the exact same issue your having. I have the same error messeages. I also had Logger cabs in the windows dir but not 11 copies of the ST6.

I am also keen on finding a resolution to this issue. I have never had issues with moving logger before between computers.

Lets hope we can figure it out or some nice person tells us what to do.

Regards
John
GM0OPS/MM9I


Logger32 Version 4 (BETA)

Bob Schofield
 

Group

I have seen a few comments about Logger32 Version 4.

I am not sure how far along this is and when it may be released.

One thing that I would like to have checked if possible is the use of "MORTTY" with Logger32.

I am currently using "MORTTY" with both N1MM and Logger32. The CW generated with MORTTY and N1MM is very clean and easy to copy CW.  To me sounds very normal.

However, when using Logger32 and the CW Machine with "MORTTY" the CW is not quite as clean and smooth as with N1MM and just wondering if this can be checked an hopefully fixed so the CW generated is sent smooth.

When I start using the MORTTY with Logger32 there was a problem, and unless you had a string of characters ready to go, there was a 5 second delay between characters if you wanted to Keyboard your response, and you had to wait at least 5 seconds either between characters, if keyboarding, and 5 seconds between using the FKeys.  This problem has been resolved, but the CW is just not nice and smooth.

When using MORTTY and N1MM the generated CW is very clean.  I just wonder if this might be a minor problem with how Logger32 sends its CW to MORTTY to be sent?

Bob/VE1RSM


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

Tom Wylie
 

Someone once told me that an error 5 indicates the programme need to be run in administrator mode, but really have no clue. I have never had this problem



Tom
FDM

On 30/09/2020 19:33, John GM0OPS via groups.io wrote:
Hi Tom
Thats what I am trying to do. I did a backup (as everyone should) to my cloud server and now trying to load a new copy of Logger32 then do an import from the data. I just cant get the new Logger32 to load and have the same issues as Robert.
I will spend some more time on it latter once the UKEICC 80cw is over.
Thanks
John


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

John GM0OPS
 

Hi Tom

Thats what I am trying to do. I did a backup (as everyone should) to my cloud server and now trying to load a new copy of Logger32 then do an import from the data. I just cant get the new Logger32 to load and have the same issues as Robert. 

I will spend some more time on it latter once the UKEICC 80cw is over. 

Thanks
John


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

Tom Wylie
 

John
Why not just upload a fresh copy of the entire Logger 32 latest programme then import your old log as an ADIF file. Seems to me to be much simpler than trying to move software from one machine to another....

Tom
FDM

On 30/09/2020 17:39, John GM0OPS via groups.io wrote:
Hi Robert,
I just logged on to the group to do a search and see if there was anything about the exact same issue your having. I have the same error messeages. I also had Logger cabs in the windows dir but not 11 copies of the ST6.
I am also keen on finding a resolution to this issue. I have never had issues with moving logger before between computers.
Lets hope we can figure it out or some nice person tells us what to do.
Regards
John
GM0OPS/MM9I


Version 4

Michael Harris
 

G'day,

How's progress on the beta testing of v4. Maybe it's time to grasp the nettle and have a look.

Regards,

Mike VP8NO


Re: Cannot install Logger32 on a new machine - Runtime error 5 - Invalid Procedure call or argument

John GM0OPS
 

Hi Robert,

I just logged on to the group to do a search and see if there was anything about the exact same issue your having. I have the same error messeages. I also had Logger cabs in the windows dir but not 11 copies of the ST6.

I am also keen on finding a resolution to this issue. I have never had issues with moving logger before between computers.

Lets hope we can figure it out or some nice person tells us what to do.

Regards
John
GM0OPS/MM9I


Re: Need to import old "bad" contacts

Jeffrey Wolf
 

Thanks, Bob. That was the solution I was hoping to see. Much appreciated.
--
Jeff, K6JW


Re: Need to import old "bad" contacts

Bob
 

It depends on what you're trying to achieve:

Option 1 -- You want to import the errant 280 QSO with correct Counties? The only way to do that is fix all 280 ADIF records. 

Option 2 -- To hell with the silly Counties, just import the damn QSOs anyway. Try this:

a) Edit the BAD.ADI file and do a global change to change to make CNTY: XCNTY: Now rename the BAD.ADI file to DamnImClever.ADI and import them.

Option3: -- Something else you're trying to achieve?

SeventyThree(s).

On 09/28/2020 7:21 PM Jeffrey Wolf <k6jw@...> wrote:


   I just installed Logger32 and imported my log as an ADI file. Unfortunately, it failed to upload about 280 "bad" contacts, almost all of them related to county errors with a smattering of others. Nearly all of them are contacts that go back many years -- some as far back as 1959. There is no way to correct these old contacts since the operators are silent keys, no longer licensed, or in a few cases perhaps still living and licensed but with new callsigns and new QTHs. The effort to fix these contacts would be substantial and, in many cases, it would not be possible. Still, the contacts were real at the time and I want them in the log. So, my question: Is there any way to get these contacts into the log even if they're "bad"?
   My thanks to anyone who can help.


Re: Need to import old "bad" contacts

Jeffrey Wolf
 

Thanks for the response. Doing it for over 200 contacts seems as if it should be unnecessary. I'd rather be able to import the contacts and correct them if/as necessary. None of them affects my DXCC totals, so they're not critical. I'd just like to have them in the log. This has not been a problem in the program I've been using up to now.
--Jeff, K6JW


On 9/28/2020 4:29 PM, Darl DEEDS wrote:

Why don’t you take a look at the bad file and see what is bad about them. Most of the time its simple and easily corrected. I have never had to contact the ham in question for a correction of the log. Sometimes it’s a different county spelling. Check and see first.

 

73

 

Darl  NA8W

 

From: Jeffrey Wolf
Sent: Monday, September 28, 2020 19:22
To: hamlogger@groups.io
Subject: [hamlogger] Need to import old "bad" contacts

 

   I just installed Logger32 and imported my log as an ADI file. Unfortunately, it failed to upload about 280 "bad" contacts, almost all of them related to county errors with a smattering of others. Nearly all of them are contacts that go back many years -- some as far back as 1959. There is no way to correct these old contacts since the operators are silent keys, no longer licensed, or in a few cases perhaps still living and licensed but with new callsigns and new QTHs. The effort to fix these contacts would be substantial and, in many cases, it would not be possible. Still, the contacts were real at the time and I want them in the log. So, my question: Is there any way to get these contacts into the log even if they're "bad"?
   My thanks to anyone who can help.

 



--
Jeff, K6JW

921 - 940 of 82114