As with the use of VX7 Commander, mods will be done at your own risk! Note, it is generally ILLEGAL to transmit on bands you are not licensed on except in an emergency. You should read and understand the following before activating software mods. On the mod screen, all fields shown are the current settings from the VX7 file loaded into VX7 Commander, except for the "Current Config" byte. THE SETTINGS: If you try a lot of different mods, you should leave "Enable Mods" checked. When this is unchecked, VX7 Commander ignores the mods and the default current config byte. There are 4 buttons at the top of the screen, for the different mods. Click one of these, the settings will change to the proper ones automatically. The "Current Config" byte is the current configuration of the VX7. The "Virtual Jumper" byte is the one to change for mods. Byte 8 and Byte 9 should not need to be changed, unless you need to use a file from a Japanese VX7 on a US model, or vice-versa. These must be set to the same as the VX7 being written to, or you will receive a "CLONE ERROR". Bytes 12, 13, and 14 can be changed freely, without receiving a clone error. I don't know what byte 12 is. I do know it is 00 in the Japanese VX7, and 01 in the US. Byte 13 - When set to 00 = Ham Only RX When set to 01 = Wide RX When set to 02 = Wide RX (Everything I have seen is set to 02) Byte 14 - When set to 00 = Ham Only TX When set to 01 = Wide TX Both bytes 13 and 14 are 00 after doing a MON/F + HM/RV + Internet Key reset toggle (Euro?). DETAILS: After writing to the VX7, the "Current Config" byte stored in the VX7 will be the same value as the "Virtual Jumper". So then if you read from the VX7, you will see that the "Current Config" and "Virtual Jumper" are identical. If you try to write to the VX7 and have the "Current Config" byte set differently than the one stored in the VX7 , you will get a "CLONE ERROR". However, it should not erase any of the VX7's memory. I tried to make this easy to manage: as long as you have "Enable Mods" checked, VX7 Commander will always default to the "Current Config" based on your last read or write to the VX7, and will use that when writing. This should make it easy to write different mods to the VX7 without any problems. So in you should never have to change the "Current Config", unless you hardware mod your VX7, use Commander to mod on another PC, managing more than one VX7, etc. If you do get a "CLONE ERROR", simply read from the VX7. This will automatically set your "Current Config" byte to the proper value. This byte can also be changed manually. Here's the Known Settings for the Virtual Jumper: Unmodified E0 = (11100000) MARS/CAP F0 = (11110000) Freeband E8 = (11101000) Japanese? F8 = (11111000) ***NOTE: After changing anything in the Mod screen and clicking OK, changes are applied to the file data loaded into VX7 Commander. Anytime you save after this, the modification changes you made will be written to your vx7 file. This means that when loading the file again, you will not have to change settings on the mod screen in order to perform the mod again, since the mod is written into your file. But take care not to save to a file you do not want saved in this way. Also, if you have "Enable Mods" checked, the "Curent Config" byte will always be changed in any vx7 file you open. So when you save then file, the "Current Config" byte will be written to your vx7 file. I do not know any more about the mods than I have written here. I have tried some different settings for the Virtual Jumper and the others. The VX7 accepts them, but I haven't noticed any major changes in the VX7's behavior. Feel free to try different settings, let me know what you find out. I would like to know what these are set at on different VX7 versions. It would also be nice to be able to correlate these with actual hardware jumper settings. Jim KC8UNJ