[WT-support] Problems with V4.13

Dave Zeph zephd at indy.rr.com
Sun Jul 6 23:36:07 CEST 2014


There is no need to RUN AS ADMINISTRATOR because the ADMISITRATOR ACCOUNT IS
ENABLED and there are NO OTHER ACCOUNTS.

 

The is NO ANTI-VIRUS PROGRAM installed

 

The WT.EXE in 5,392Kb.  This is the same size that I have on my PC which is
working properly.  I'm not sure how to compare my WT.EXE to yours since I DO
NOT HAVE your WT.EXE and don't know how to compare Binary Files.



I believe I already said that I removed the Registration Key and Win-test
opened Unregistered.  I already said that I Requested a New Registration
Code and that It Was The Same As The Original Code.  And I believe I ALREADY
SAID that  WIN-Test Once Again FAILED TO OPEN with the same Problem
Signature

 

I tickled to death that Win-test works properly on your system - good for
you, Bob.  It DOES NOT WORK on ANY OF K8AZ's Systems with the same
Validation Codes that worked with V4.12.

 

I'm not as stupid as you would like to think.  I am perfectly capable ot
double-clicking on V4.13Update.exe, and following the steps to install the
Update, start the software, and correctly observing that Win-Test FAILS TO
OPEN and with a CONSISTENT Problem Signature.  I did not expect you to solve
this problem.  It appears to me to be a problem with Win-Test Validation
Codes and I am hoping that Laurent will have time to look into it before
next weekend.  I sent him the WT.INI file on Friday.

 

 

W9PA

 

 

  _____  

From: rawilson at gmail.com [mailto:rawilson at gmail.com] On Behalf Of Bob
Wilson, N6TV
Sent: Sunday, 06 July, 2014 16:50
To: Dave Zeph, W9PA
Subject: Re: [WT-support] Problems with V4.13

 

Dave,

 

So far no one else has reported any problem like this.

 

I still don't know if you're running everything with "Run as Administrator".

 

I still don't know if you have tried temporarily disabling any anti-virus
programs.

 

I still don't know if you compared your WT.EXE to mine.

 

I would really like to look at your WT.INI file.  I will paste in MY
registration code and see what happens.

 

I removed the RegistrationKey from my WT.INI, and WT 4.13 came up in demo
mode.  I requested a new registration key.  It was the same as the old one.
I pasted into the Help | Register software window, exited and restarted WT
4.13.

 

No errors.  I simply cannot get Win-Test 4.13 to crash on my 32-bit Windows
7 system.

 

Perhaps it has something to do with sound card drivers or DLPortIO.DLL?  You
could try disabling things one by one in your WT.INI file.  But I think an
anti-virus program is the more likely cause, or failing to run as
administrator.

 

73,

Bob, N6TV

 

On Sun, Jul 6, 2014 at 1:35 PM, Dave Zeph <zephd at indy.rr.com> wrote:

Bob ... I have downloaded V4.13 Update several times - both Update and Full
Versions.   I have downloaded it to 2 systems other that K8AZ and tried
transferring it.

 

1)       V4.13 Update results in Win-test Failing to Start

2)       Installing V4.13 Full results in Win-Test Failing to Start

3)       Performing a Full Uninstall of V4.13 - including removals of all
residual Files and Folders - and then performing a new install of v4.13
results in Win-Test Failing to start

4)       If the Registration Information is removed, Win-Test will starr in
Unregistered Mode

5)       If I subsequently reapply for a NEW VALIIDATION CODE, and install
it, Win-Test FAILS TO START

6)       If I start Win-Test without a WT.INI and allow Win-Test to create a
new WT.INI, Win-Test will start.  However if I simply add the Registration
Information to the WT.INI - either by cutting & pasting, or via
Win-Test-->HE:LP-->REGISTER, Win-Test Fails to start

 

In all casess, when Win-Test fails to start, the PROBLEM SIGNATURE is the
same and I have already provided it.

 

My conclusion is that Win-Test has a problem with the Validation Code(s)
being provided by the Win-Test Robot.  This is NOT a Win-Test Configuration
problem.  This is NOT a Win-Test setup problem.  This IS a problem with the
Win-Test software which is why I posted this to the Win-Test Reflector.

 

I see no value in sending you my WT.EXE. WT4 File (I do know where these
files are located VTW), or WT.INI file since your hardware will have a
different hardware/software signature.  The information that causes these
PC's to fail is the Registration Code and these will not work on your
system.

 

 

W9PA

 

 

 

 

  _____  

From: rawilson at gmail.com [mailto:rawilson at gmail.com] On Behalf Of Bob
Wilson, N6TV
Sent: Sunday, 06 July, 2014 3:14
To: Dave Zeph, W9PA


Subject: Re: [WT-support] Problems with V4.13

 

Dave,

 

Attached is my WT.EXE (4.13), WT.INI, and a .WT4 file that WT 4.13 opens for
me with no issues.  See if you can get your copy of Win-Test to open it.
See if your WT.EXE is the same as mine (I named it wt.exebob otherwise Gmail
won't let me send the file).

 

Of course it will come up in demo mode.  So try your registration code.




73,

Bob, N6TV

 

On Sun, Jul 6, 2014 at 12:06 AM, Bob Wilson, N6TV <n6tv at arrl.net> wrote:

OK, sorry, I see that now, further down below.

 

Did you select "Run as Administrator," both when running the installer and
also when starting Win-Test 4.13?

 

If so, can you please try starting Win-Test 4.13 with the "-n" command line
argument to prevent any auto-log file loading?  Does that work?  It's
possible that Win-Test is trying to load a log file that it is having
trouble with.

 

Alternatively, you could edit wt.ini and change 1 line:

 

Change:

 

StartNow=1

 

to 

 

StartNow=0

 

If you still make no progress, please send me your WT.INI file and the .WT4
file you see listed under 

 

[Files]

Path=somefile.wt4

 

73,

Bob, N6TV

 

On Sat, Jul 5, 2014 at 11:50 PM, Dave Zeph <zephd at indy.rr.com> wrote:

I believe that I stated in my message that I tried installing with the full
V4.13 with THE SAME RESULT.

 

I used System Restore first to return the system to the same starting point.

 

It makes no difference whether V4.13 Update is used or the Full V4.13
Install - even installed from Scratch.

 

But then I think I said that in my posting.

 




More information about the Support mailing list