EZ Scan wiped out my Alpha Tags, PRS-800

[chas0039]

I had the usual Alpha Tags that are locked in by the factory for the Scan Lists above 151 and all was well with the 1.04 version of EZ Scan. I updated to the 1.05 version so I could fix the battery problem and the save to the SD card wiped out all the tags, so now all the 151-181 scan lists just show the number. I went back, cleared out the lists, reloaded the lists, and re-saved to the SD card; no better.

Unfortunately, the software will not allow me to edit these tags so I am stuck. Any ideas?

Thanks

 

[Geological]

I had the usual Alpha Tags that are locked in by the factory for the Scan Lists above 151 and all was well with the 1.04 version of EZ Scan. I updated to the 1.05 version so I could fix the battery problem and the save to the SD card wiped out all the tags, so now all the 151-181 scan lists just show the number. I went back, cleared out the lists, reloaded the lists, and re-saved to the SD card; no better.

Unfortunately, the software will not allow me to edit these tags so I am stuck. Any ideas?

Thanks

Same thing happened here.
I just editted the factory ones in the software to scanlist 151,152....etc
I honestly don't think I would ever get to that level of lists on a consistent basis without starting fresh at some point.
New to this but I only have 12 lists so far and would likely be pushing it to get to 50 in total.
I am new to this though.

 

[chas0039]

Thanks for your idea. I have been working on this for a while and I started from scratch with a new SD card and that solved the problem. It also fixed the database which for some reason did not copy the first time when it said it did.

 

[stetsonbob]

Try turning off the location in the advanced features tab(bottom left), that will put the names back in spots 150-179.Hope that helps.

 

[chas0039]

Try turning off the location in the advanced features tab(bottom left), that will put the names back in spots 150-179.Hope that helps.

Oddly, GRE tech support said the opposite, and that didn't work. Fortunately, reformatting and re-loading worked, even though it happened again.