B.J.
You are exactly right regarding the use of an editor. I so much want to use one to avoid hassles such as this! But, there isn't an editor that I can trust just yet.
With the (beta) firmware that I am using, the editor that I think that you are referring to, doesn't work well. The other editors available have given me some rather troublesome and sporadic operation.
I agree that the editors don't work well for making changes, unfortunately, but I didn't really use it much for that purpose. I can't remember exactly the process I used, but basically, I took one of those .xml files you can create at some web page, then I put it into a regular Windows style text editor, one that has an option to use linux style 0D line termination, and used that to remove and/or add satellites. THEN, I used the Azbox editor to import that file, and convert it to Azbox format, and then send it to the Azbox. I did do some minor editing with the Azbox editor, such as perhaps deleting some entries, and perhaps something else {I can't remember}, but I definately did not try to change satellite parameters in the editor, because I had quickly learned that it didn't work very well, like you said.
Basically, I just used the editor to get a list of satellites into the Azbox in the proper order, then I did all setup of the sat parameters using the remote. It would be nice if they got an editor that allowed you to change all the parameters in the computer, but I agree that that can't be done yet. But at least with the version I have (and I thought that it would work with newer versions too, but maybe not), it would function with respect to the basic functions of upload, download, deleting sats, and I think changing the longitude perhaps.
You also hit on one item as a "procedural" matter that would probably be the best practice in any matter. That would be to ADD all the sats with the motor control set to OFF and then, after adding them to the list, change the motor control as required. It isn't too big of a deal for me since I only have the one satellite (30.0°W) that requires me to use DiSEqC 1.2, the rest all are set up with USALS and they don't interfere with one another.
B.J., to reply to your quote above, you will have to take my word for this, but I tried every way that I could possibly find to reorder the steps, try new steps, save the results and try them over and over again in various orders looking for a proper method. I think I spent about 16-18 hours, non-stop with only a short nap and a few distractions, trying different things over and over again looking for a solution and I still don't know if it is really perfect just yet. It is definitely a bug in the programming of the AZBox and not an "operator error". This is the strangest and most difficult glitch that I have seen with any receiver, other than one that just doesn't turn on.
In any respect, I did learn something about the AZBox and its programming.
RADAR
What you describe, relative to spending hours of trying to get the sats in there right reminds me of what I initially went through with the Azbox, because I found that the sat/transponder lists that came with the box, and were there even after upgrading firmware, were corrupted, and there was basically NO WAY to get the satellite list the way I wanted it. I had different problems than you did though, I think in my case, I was TRYING to delete all the sats, but it wouldn't LET me delete them all. There was one sat that I couldn't delete, and as long as that sat was in there, nothing worked right. I'd make changes, and the changes to one sat would cause other sats to be changed. It was a mess, and I spent days trying to fix it.
Finally, I gave up and tried that .xml thing, editing the file myself before feeding it into the editor. After I got a "clean" set of sat/transponder data in there, everything has worked well, and like I said, yesterday, I experimented, changing the setup of 3 or 4 of my sats, moving them from USALS to DiseqC-1.2, rebooted, and it retained the settings. I tried using the AUTO mode where the Azbox enters sat numbers starting with 1,2,3, etc, and also used the option to manually choose the sat number. The diseqC sat number then appears up with the sat name, to remind you which sat number you used, which is nice. I even tried setting diseqC-1.2 sat numbers in scrambled order of longitude, and that worked fine too. Everything seemed to work.
So again, it may just be that they broke the newer firmware versions (which I'll probably find out soon, as I'm thinking about upgrading soon, perhaps after the Olympics are over), but I really think that you might be suffering the symptoms of a corrupted sat/transponder data set, and that those symptom might go away if you'd start from scratch with one of those .xml files. My Azbox just seemed to have a mind of it's own, and was doing all sorts of weird things until I wiped that corrupted data out of there, which I was NOT able to do via deleting with the remote.
But I guess I'll see what happens when I finally switch to a newer firmware version. I've been waiting for improvements on either the streaming or PVR functions, and it looks like they are at least trying to do some things with the streaming, so I'll probably bite the bullet and try upgrading again.