For some strange reason, RPM is not detecting a single Com port at all and it is giving me a strange error message (QueryDosDevice Error 122 The Data area passed to a system call too small.) Anyone have any idea on how to fix this issue? Its PRM 14 btw.
-
To anyone looking to acquire commercial radio programming software:
Please do not make requests for copies of radio programming software which is sold (or was sold) by the manufacturer for any monetary value. All requests will be deleted and a forum infraction issued. Making a request such as this is attempting to engage in software piracy and this forum cannot be involved or associated with this activity. The same goes for any private transaction via Private Message. Even if you attempt to engage in this activity in PM's we will still enforce the forum rules. Your PM's are not private and the administration has the right to read them if there's a hint to criminal activity.
If you are having trouble legally obtaining software please state so. We do not want any hurt feelings when your vague post is mistaken for a free request. It is YOUR responsibility to properly word your request.
To obtain Motorola software see the Sticky in the Motorola forum.
The various other vendors often permit their dealers to sell the software online (i.e., Kenwood). Please use Google or some other search engine to find a dealer that sells the software. Typically each series or individual radio requires its own software package. Often the Kenwood software is less than $100 so don't be a cheapskate; just purchase it.
For M/A Com/Harris/GE, etc: there are two software packages that program all current and past radios. One package is for conventional programming and the other for trunked programming. The trunked package is in upwards of $2,500. The conventional package is more reasonable though is still several hundred dollars. The benefit is you do not need multiple versions for each radio (unlike Motorola).
This is a large and very visible forum. We cannot jeopardize the ability to provide the RadioReference services by allowing this activity to occur. Please respect this.
RPM Issues
- Thread starter squall8ball
- Start date
- Status
Windows 10 latest updates on it and it's a rs 232 to USB cable. And literally same exact error message
the wierd part is if you act like your trying to connect via bluetooth to anything through the radio- usb settings its show all active com ports
- Joined
- Jan 11, 2008
- Messages
- 1,081
- Reaction score
- 43
The .Net version change from Windows 10 1903 and later breaks a bunch of things, namely the ability for RPM to parse the COM ports.
If you are a tinkerer, you can change the COM port number in the config file (C:\ProgramData\Harris\RPM\RadPersMgr.xml) and then open RPM. Just don't touch the COM port selection button and the software will communicate just fine with the port defined.
Only real fix is to only use Windows 10 LTSB or 1809 and lower. Going beyond 1909 also breaks even the latest version of RPM2, I guess Harris doesn't use the latest Windows versions in-house!
If you are a tinkerer, you can change the COM port number in the config file (C:\ProgramData\Harris\RPM\RadPersMgr.xml) and then open RPM. Just don't touch the COM port selection button and the software will communicate just fine with the port defined.
Only real fix is to only use Windows 10 LTSB or 1809 and lower. Going beyond 1909 also breaks even the latest version of RPM2, I guess Harris doesn't use the latest Windows versions in-house!
i am attempting to "roll back" to 1809 but so far no luck, and as far a messing with that config file, i honestly dont know the proper wording it requires.. honestly im drawing a blank!
That is very nearly the same thing I use. In RPM, if the USB/RS232 adapter is not plugged in or if the drivers are wrong, the port won't show.
My adapter is genuine FTDI with FTDI drivers and works perfect. Use it with programmer 18 co- installed.
RPM comes with the proper .net and should be no issue on Win 10.
Changing .net, you will break something. Worst case is uninstall RPM and re-install.
Blogs are claiming problems with other than genuine FTDI for your RS232.
Clarifying, I have programmer 20 on my XP bench machine with a hardware RS232. My problem with that is maintenance won't start so I have ver 18 on my new Dell machine(only USB and works. No more 'newer version' errors.
I might experiment with rolling back RPM to 10B07 for better comparability.
Might be wrong but only XG and XL radios can program via bluetooth.
My adapter is genuine FTDI with FTDI drivers and works perfect. Use it with programmer 18 co- installed.
RPM comes with the proper .net and should be no issue on Win 10.
Changing .net, you will break something. Worst case is uninstall RPM and re-install.
Blogs are claiming problems with other than genuine FTDI for your RS232.
Clarifying, I have programmer 20 on my XP bench machine with a hardware RS232. My problem with that is maintenance won't start so I have ver 18 on my new Dell machine(only USB and works. No more 'newer version' errors.
I might experiment with rolling back RPM to 10B07 for better comparability.
Might be wrong but only XG and XL radios can program via bluetooth.
- Joined
- Jan 11, 2008
- Messages
- 1,081
- Reaction score
- 43
You said a lot there, and either none of it applied to this issue or was incorrect.
RPM does come with .Net 4.0 but is not supported on Windows 10. .NET 4.7 is built into Windows 10 and has been since 1607. .Net 2.0/3.5 was an optional install that ProGrammer needed and would need to be installed. Re-installing RPM will not fix this issue. The problem stems from a change Microsoft made to the version of .Net included in Windows. RPM parses thru available COM ports using a very old school technique that's been around since the XP days, and they never bothered to update because RPM2 was their focus and "if it works..." Sometime after 1809, Windows came bundled with .NET 4.8 and it seems to be what is breaking things. I am still doing research into the exact why, but I do know that when taking a bare-bone install of Windows 10 1607 and doing iterative upgrades, RPM COM port parsing will break after 1809 and RPM2 will become buggy after 1909. Both problems persist thru 20H2 with all patches applied.
To answer squall8ball's question, open the XML file in notepad and look for "PortNumber="1"" in the file, change the 1 to the COM port number you need. 2 for COM2, 3 for COM3 etc. You can find available COM ports in Device Manager.
On a personal note to merlin,
I see a lot of your posts on the forums the past few months and almost every single one is misleading at best or flat out wrong. I realize we are here to learn and share knowledge, but if you aren't confident in the answer, please don't post it on a public forum to confuse others when someone comes across it searching for help.
For the record, there are a lot of XG radios, most are serial. The XG100p is USB and bluetooth programmable, the XL series are USB or WiFi only.
RPM does come with .Net 4.0 but is not supported on Windows 10. .NET 4.7 is built into Windows 10 and has been since 1607. .Net 2.0/3.5 was an optional install that ProGrammer needed and would need to be installed. Re-installing RPM will not fix this issue. The problem stems from a change Microsoft made to the version of .Net included in Windows. RPM parses thru available COM ports using a very old school technique that's been around since the XP days, and they never bothered to update because RPM2 was their focus and "if it works..." Sometime after 1809, Windows came bundled with .NET 4.8 and it seems to be what is breaking things. I am still doing research into the exact why, but I do know that when taking a bare-bone install of Windows 10 1607 and doing iterative upgrades, RPM COM port parsing will break after 1809 and RPM2 will become buggy after 1909. Both problems persist thru 20H2 with all patches applied.
To answer squall8ball's question, open the XML file in notepad and look for "PortNumber="1"" in the file, change the 1 to the COM port number you need. 2 for COM2, 3 for COM3 etc. You can find available COM ports in Device Manager.
On a personal note to merlin,
I see a lot of your posts on the forums the past few months and almost every single one is misleading at best or flat out wrong. I realize we are here to learn and share knowledge, but if you aren't confident in the answer, please don't post it on a public forum to confuse others when someone comes across it searching for help.
For the record, there are a lot of XG radios, most are serial. The XG100p is USB and bluetooth programmable, the XL series are USB or WiFi only.
I appericate the imput sir, but i still have a problem, the document you want me to find is in .exe form and also does not contain that wording in that file at all for some reason. attached below this next sentence is All that is in said .exe notepad document.
<?xml version="1.0"?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v2.0"/>
<supportedRuntime version="v4.0"/>
</startup>
</configuration>
I think that .exe file is the activation script.Win 10, you most certainly can install Ver.4 .net as an option during install, It looks like you have done that, so your issue is something other.
Now running that .exe file would 'activate' ver. 2 and 4 if installed. (I didn't need that)
If you are using the USB for programming, check blutooth settings in both RPM and windows and disconnect BT.
Visa vera if you are using BT and make sure the radio is connected.
Dont use both at the same time.
Times like this I wish I had an XG to refer to, newest I have is P7300 and it also programs with BT or USB.
- Joined
- Jan 11, 2008
- Messages
- 1,081
- Reaction score
- 43
It appears you are in the wrong place. What you linked is the RadPersMgr.exe.config which is in "C:\Program Files (x86)\Harris Radio Personality Manager"
What you need to edit is RadPersMgr.xml which is in "C:\ProgramData\Harris\RPM". Do note that the ProgramData folder is hidden in Windows by default, but if you copy/paste that path into the address bar in explorer it will take you there.
Merlin... you literally have NO idea what you're talking about. the exe.config file is a definition file to pass config options to executables. Configuring Apps by using Configuration Files
I would love to see that P7300 that is Bluetooth programmable, I'm sure TAC would too!
What you need to edit is RadPersMgr.xml which is in "C:\ProgramData\Harris\RPM". Do note that the ProgramData folder is hidden in Windows by default, but if you copy/paste that path into the address bar in explorer it will take you there.
Merlin... you literally have NO idea what you're talking about. the exe.config file is a definition file to pass config options to executables. Configuring Apps by using Configuration Files
I would love to see that P7300 that is Bluetooth programmable, I'm sure TAC would too!
I could kiss you on the lips right now... you honestly have no idea!! thank you soooo damn much!
OK so you have your terms for the very same thing. SC4/5,,same thing. That ""SCRIPT"" does exactly as both you and I mentioned. BTW "C:\ProgramData\Harris\RPM" never was hidden on my system.
ok so now im seeming to have yet another issue, and im starting to get frustrated. For some reason now it wont let me load the key onto the radio with key loader. It keeps giving me the error of "The Distribution Set could not be loaded. The following error was reported: Key Loading failed. Unable to query device capabilities (Unable to read a valid response). Ensure that the device is powered on, connected properly, and in "Key Load" mode (where applicable). Resolve the error and click the Load button to try again." I checked to make sure that i dont have a f6 or f7 dsp code, witch i dont and now im stuck...
I use an RS-232 adaptor w/RPM14 and RPM2, on 2 different machines that are running up to date versions of Win10 with no issues at all. Very strange!
What model radio are you trying to keyload?
What model radio are you trying to keyload?
P7100ip systems
Are you trying to use KeyAdmin? I've never had any luck keyloading a 7100 (7200 and above, no problem). Not sure if it's a cable issue or what, but never seems to work.
N4VGW
Member
Do you have the right cable? the P7100 series used a key loading cable that has an internal 2210 ohm resister-(Across Pins E8 & E10) that puts the radio into the key loading mode-The regular cable that's used on the radio to program won't work. The P7200 radios will key load with the normal cable.
Last edited:
Crap, then no I do not have the right cable.. any idea as to where I can find one or anyone near by have one?
N4VGW
Member
New London Technology Has them. The part number is: RPM 113 2472/36
- Status
Similar threads
