Unitrunker Unitrunker resetting itself

[HM1529]

I have been having an intermittent problem over the last six months with Unitrunker essentially resetting itself. I have the software installed on an old Acer Netbook. It worked with no problem for a few years. Now, in the last six months, I have had the program essentially start from scratch on several ocassions. By this I mean that when I open up the program, nothing is there...none of the half dozens sites I monitor, no receivers, nothing. I have to rebuild everything. However, if I look through the files, the old data are all saved.

Has anyone had this issue? Is it possible to merge to multiple XML files so that I can end up with comprehensive talkgroup and unit ID lists? It is getting to be a pain starting over every few months. I have been using Pro96Com, too, but there are some things that I like better about Unitrunker.

 

[maus92]

I've have had occasional xml failures that *might* have been related to improper shutdowns, but yours sounds like a data integrity issue possibly related to hardware. The most recent unitrunker.xml archive file should already be comprehensive. At the very least, I'd do a thorough HDD check, and stress test the computer / RAM. I just recently had the system board fail on a 2 year old MacBook, so it does happen.

 

[HM1529]

It seems like ever since I switched the computer over to Windows 10, it really bogs down if Unitrunker is running more than a day or two at a time. I used to run this netbook for days at a time with Unitrunker running on Win 7 to monitor the local TRS. I have had to force restarts a few times when the computer was totally unresponsive since moving to 10. I could see those forced reboots contributing to the issue. This past weekend, however, I didn't have any obvious problem. I had Unitrunker running in one location in the AM, closed it properly, put the computer to sleep, and then reopened Unitrunker later when I was going to monitor a different TRS in another area. I opened it up and nothing...completely blank. However, the data archives are still there, I just can't seem to get Unitrunker to load the old data.

 

[moonbounce]

Funny you should mention this, I just had the same problem, let me ask you do you use Malwarebytes?

 

[maus92]

What are the specs of the computer running Unitrunker? Is Win10 fully updated? It does seem that this is either a hardware or Win10 install issue.

To "force" Unitrunker to use an archived / backup copy of Unitrunker.xml, you have to rename it. My latest archive file is currently "Unitrunker.xml.2706" (w/o the quotes.) In order to replace the corrupted xml file, you have to delete your current unitrunker.xml, then rename the latest backup to unitrunker.xml - in my case, I would simply delete the last 4 numbers and the dot preceding them: (.2706)

I run Unitrunker 2 on a Win10 Pro 64bit, Dell i5 4310U 8GB RAM laptop, but the principal is the same. The data files are located in the Users folder, under AppData/Roaming/Unitrunker

 

[HM1529]

Funny you should mention this, I just had the same problem, let me ask you do you use Malwarebytes?

I do have Malwarebytes installed. I don't have the rest of the specs since I am at work now.

 

[moonbounce]

I do have Malwarebytes installed. I don't have the rest of the specs since I am at work now.

Well Malwarebytes erased all of my Unitrunker settings once about a year ago after which i took it off and no more problems. Move ahead to about a week ago and I reinstalled Malwarebytes and it deleted all of my Unitrunker settings again, so once again I have uninstalled MB and all things are happy again.

 

[maus92]

If Malwarebytes is indeed the issue, you can exclude the Unitrunker folders from the scan that looks for suspect files.