The files in question in this thread are standalone CPU upgraders.
Yeah, I know!
If the radio is working as it should, you use Whistler's EZ-Scan for any future updates. The old GRE EZ-Scan will no longer connect to a server for any kind of updates.
Ahh, OK, and?
The reason for two different files was pointed out earlier in this thread. It is because the original PSR800 and the others have different bootloader code embedded into their eeproms.
The old original PSR800 that has been upgraded by Whistler to a WS1080 would use the one with Legacy in the name as the site implies.
A WS1080 model that has a case that says WS1080 on it for the model would be a Whistler factory product and would use the updater without Legacy in the name.
OK, how exactly do you know this? Are you getting this from a post, supposition, guess, or satisfied with any answer that seems OK?
The main thing is, you do not normally need these files but they are good to have around just in case. There have been users that somehow managed to wipe the CPU firmware from the radios eeprom chip. That's when you would use these files, to unbrick you radio. It's really not bricked at this point but for all practical purposes, it's about the same thing as the radio is near brain dead until you write the CPU firmware back to the radio using the appropriate file as listed in this thread.
If what you say is true, then someone who gets a legacy upgrade scanner and needs an updater then they cannot use any other CPU updater file or else?
I do agree that it's kind of confusing! I'm also not sure if using the wrong file would truly brick the radio or if it would still allow you to use the correct file. I'm not going to try in order to find out!
Yeah, exactly, reason I posted...
The radios are very near identical but there are differences between the original GRE PSR800 and the Whistler WS1080. The RadioShack models are also different and would use the file with Legacy in the name in the unfortunate event that you wiped your firmware code somehow.
Almost all the differences are in the firmware and boot loader code. The boot loader code is hard written in the eeprom and cannot be altered. At least not easily if it can be at all. It's this boot loader code that the files in this thread are working with. The boot loader is different between the models.
OK, you know this exactly how? You know what eeprom IC's are right (
electrically erasable programmable read-only memory )? Isn't that WHY we send in our radios?