I tried my hardest to get the SDS 100 to mess up but it worked like a champ. On the other hand, I tried on my other SDS 200 and good Lord it messed up really bad. Somehow even without reading the scanner's corrupt card it corrupted my Sentinel files. They looked ok but in the scanner the dreaded NOTHING to SCAN.
Thank the Lord I have more than one computer. I was able to restore my programming from another computer.
The SDS 100 seems to be immune to this problem. Has to be some difference in firmware.
You sure have one heck of an odd problem here!
It does sound like it may be a possible firmware issue being as you can create the problem outside of Sentinel. But an issue that seems to only affect the SDS200.
Just as a test, have you tried cloning a good working SD card from your 100 to a new SD card or one you can lose and then stick that in the 200 and see what happens. I'm not sure you will be able to figure anything out from such a test other than your own satisfaction but it may be neat to see how that card behaves when loaded in your SDS200.
I've had issues with my SDS100 recently. I had one department in a favorite list that would not produce any talk.
I checked service types as well as made sure that departments QK was indeed enabled. All was good. The same programming worked just fine in a 436 and two 536s so why not in the SDS100. I was stumped.
I went into Sentinel and looked at that systems department QKs and it reported all were on as did when checked in the radio.
I tried unselecting the department and then saving it in Sentinel and then using the Erase Favorites from Scanner option in Sentinel, I wrote the files back to the radio. I'll be darn if a fresh read from the SDS100 into Sentinel did not show that this department was back enabled again even though I had disabled it before writing to the 100.
I also removed that favorite list from Sentinel and let the file in the radio recreate it. No matter what, this one department would not scan even though everything showed that it was enabled.
I finally decided to look at that favorites list file on the SD card with a text editor. The FL files on the SD card are stored in Human Readable ASCII format so they are very easy to read by eye.
This particular department was showing as NOT enabled when looking at the file with the text editor! I again used both the radio and Sentinel and toggled that department off and on but it had zero effect on the actual file on the SD card. And yes, I made sure and checked the box to erase my favorites when writing with Sentinel plus Sentinel warned me that my favorites would be erased.
Once I made the edit in my text editor and set the No value to Yes for the bad department, the department started working just fine plus I can now toggle the department on or off and my choice is honored plus reflected correctly in the actual favorite list file on the SD card. Sentinel also reports correctly if the department QK is on or off as well.
I have no idea why this worked but it did.
The only think I forgot to do what look at the FL ASCII file with hidden ASCII codes viewable. I had non printing or odd ascii codes hidden as a FL file should not have any anyway. It's possible that FL file did have some corrupt data and contained some hidden ascii codes.
Somewhere, I still have a copy of the file that would not work so I can still look for hidden ascii data when I have time.
One other thing I did while trying to get this department working was to copy a good working favorite list from a 536 and replace the bad file on the SDS100s SD card. That also failed and the list would show the department as enabled or on in the radio and in Sentinel when the 100 was read. Sentinel would also tell me that FL had been changed so it could see something was indeed different. I'd always tell Sentinel to read the file from the radio and overwrite it in Sentinel so Sentinel had the working file from the 536 I'd copied over to the SDS100s SD card. When I did many of these file copies from the 536 to the SDS100 card, I'd usually do manual copies without Sentinel and sometimes used a card reader.
I don't get it but I've seen it happen and I could reproduce the problem.
Is it something in the SDS100 or something in Sentinel. Like your case with your SDS200, my problem happened without even using Sentinel so my thinking is something is amiss with the FW in the SDS100 in my case.
Since I made the manual edit with the text editor, that problem department and its favorite list have been working just fine. If I unselect the department on the radio, Sentinel will now report that the department is indeed not selected as it should when I read the radio into Sentinel! Before all this, Sentinel would always report this one department as On or Enabled regardless of its Off status in the file when checked with a text editor.
I have over 90 favorite lists and am worried there may be problems in some of the others but not really knowing what to look for with a text editor, I'm kind of guessing when I try and find a similar problem in other FLs.
The best thing I can probably do is set all departments and site QKs to On in all FLs and then make sure Sentinel reports the same. Then set them all to Off and again look at each in Sentinel and make sure it again reports their true status.
Talk about a time consuming PITA!
Anyway, I do think you may be on to something here after thinking about my problem with my SDS100. Not exactly the same problem as yours but definitely something odd only on the SDS100 in my case.
Sorry for the length post but I did not know how to accurately explain what I say and what I tried as well as what I did to correct the problem.
I also now only use a copy of Sentinel on another computer with the SDS100. The 4 and 536 models use a copy of Sentinel setup just for them. No more changing the Target Type for me. I do wonder if something gets messed up when the Target Type is changed from an x36HP to one of the SDS models. That's how I did things before I found and fixed my problem, I used one copy of Sentinel for all radio types. I always have been accurate about making sure I had the Target Type set correctly before doing a read or write so that should be covered as not the cause.
Good Luck on this one!
...is when you deleted the system, the quick key was a duplicate of other systems and it deleted all systems under that Favorite List? 
