Need help with Unitrunker

[rkorchensky]

I have been using Unitrunker and its prior versions for a very long time. For some reason it has recently decided to "stick" in an unusual mode.

It won't start.

After some thought I got the bright idea that perhaps the data file was corrupt, and I think this is the case.

The problem is that I cannot delete the current file, and I cannot get the program to let me revert to an older version. It is "stuck" on the current version.

I renamed the current file to xxxunitrunker hoping it might load the next file, but still no luck.

Any suggestions as to how I might get the program to "release" the current data file and go to an older one?

Thanks in advance.

Ralph, VE3EUK

 

[wvscanner]

If you are using the dos version's, you will need to uninstall it under start, control panel, add and remove programs. When it is unistall the data that you collected will still be there. Then you can install the dos 1.0.57 retro or the windows version.

 

[K8TEK]

If you mean it says you shut it down improperly, you need to revert back to 0.1.0.54. This is a known issue

 

[dougr1252]

Try putting the executables in separate folders so they can't see the other data files. But maybe this is the version that timed out on January 1 ?

http://www.radioreference.com/forum...-decoders/129730-unitrunker-quit-running.html

 

[SCPD]

Any suggestions as to how I might get the program to "release" the current data file and go to an older one?

Go to the archive tab, select an older revision, and press the "Take me back" button.

If the program is failing to start, obviously you won't be able to go to the Archive tab. Open the folder where your data files are stored. Copy one of the older Unitrunker.xml.xxx files over the latest file (Unitrunker.xml with no revision number). Try starting the program.

 

[rkorchensky]

Thank you all for your concern and helpful answers.

I must apologize as I was called away unexpectedly and could not respond.

All your answers make sense and are helpful and appreciated, however after reviewing them and looking further into the problem I think the problem "might" be a bad input on my sound internal sound card. Further investigations are necessary.

I'll let you know if I find the problem.

Ralph, VE3EUK