I don't see any email. make sure you spell retrotoniks like a dickhead that used an obvious name and had to spell it weird. You can send it to kelvin@retrotroniks.com too. I was wondering what was going on. I don't like unresolved issues. But yeah, just try resending it and I'll see what we can do. I'll go ahead an do some explanation here as well in case anyone has a similar problem. When you save, it first saves the info data to the eeprom and then it saves the code. If the code fails it is programmed to just put unknown because otherwise you'd have a corrupted slot. There are a few things you can do as long as everything is working. You can delete all of the new (Unknown) entries and try them again. You can delete all of the chips which is probably the best option, and then reinstall them maybe 15 at a time. It doesn't take long but it is annoying (sorry). If that doesn't work there is a factory reset to clear everything but as I stated to someone a few days ago, not sure if it was you, you really shouldn't have that kind of behavior and if you do, and it has happened to me before, then that's not acceptable and we'll just replace it. This is a new thing and of course it's going to have some issues but I can't have something out there that isn't working properly. 

I'm in the Software QA field, so here to help narrow this down, I get it things will happen and unknown issues always appear. 

Here is a quick breakdown/recap of what I was doing before the "Unknown" issue came up.  Just in case anyone gets the same issue in the future, maybe one of the items triggered it.

1.  About a week prior to the 'Unknown' bug I upgraded to the latest firmware.  It was an easy update, and all went fine.

2.  Updated to the latest VetusGUI.  No issues, and all went fine.

3.  This is where I think the problem came in:  I was attempting to create a script to test an Atari Sally Chip.  The tests, which I was creating are not the best and this is probably due to my crappy beginner coding skills on the Vetus Pars.  When I would sent the code to the Vetus Pars, I was getting a lot of connection issues with Windows 11 and the Vetus Pars, and as a remedy for it I had to power off the unit and power it back on because the reset button did not reestablish the connection.  When I did get a good connection, I was basically at the mercy of my testing script which seemed to just lock up the Vetus Pars.  Multiply my trial-and-error scripting attempts with the connection issues I was having between the Vetus and my Windows 11 machine; all requiring a need to power cycle the Vetus multiple times to get a connection and I think the I corrupted in internal memory (my guess).

4.  Troubleshooting:  I did delete all of the 'Unknown' entries that I created, then tried to upload a good test from the test section on this site.  The result of loading a good test was that it displayed as 'Unknown'.

5.  Troubleshooting:  I did delete all of the tests on the Vetus Pars and did attempt to load them back, but they just produced an 'Unknown'.

6.  Troubleshooting:  I backdated the firmware and retried steps 4 and 5 but got the same results.

7.  Troubleshooting:  Updated back to the latest firmware and retried steps 4 and 5 but got the same results.

I think this just leaves the Factory Reset (needs those steps), although if you have any other suggestions that I can try before sending it back, I'm up to try them.

Thanks,

C

I found a fix/workaround based on your earlier comment:  "then reinstall them maybe 15 at a time"

Initially I tried to reinstall them by adding a bunch of chip files then loading them one at a time with the 'Save on Vetus' button.  The result was a bunch of unknown files.

Then I took another approach:  (VetusGUI)

1.  Click 'Load', and select multiple .chip files.

2.  Click the 'Batch' button.

3.  Click the 'Refresh' button, and all tests are now present with the proper name.