MCS2000 Programming

[HunterGatherer]

Hi brains trust,
I have the software for the MCS2000. the software is from 2004 and I am attempting to install on windows 10. Issue is that the program won't install due to 'NT4.0 or later is required'. Of course I've never had issues in the past installing, loading and using this software on older laptops. does anyone have any idea how to get around this OR know where the best place to purchase the latest software for the MCS2000?

 

[beaker7]

The newest i was able to get the mcs2000 cps to work on is Windows 7 32bit. Dont think it would work on anything newer. You could set up dualboot. I wouldnt try using a VM as they are unstable.

 

[Skypilot007]

I agree, don't think you will have any success running that CPS on a win 10 operating system. If win 7 32 bit won't work go back to XP 32 bit. A real serial port helps things as well. You can't purchase this software anymore, it's long been EOL'd by /\/\. Google is your friend in finding the latest version. Even the last version of this CPS is not going to run on win 10 as its probably 10 or more years old.

 

[a417]

I can and do run it in a VM for ease of making changes to the codeplug on an accessible computer, yet I keep an old Win XP laptop (dell d830) running just for writing to the MCS2k & other vintage moto hardware (which is done by a pentium 75 laptop). I can read the radio from the VM running XP, yet I choose not to take the chance of writing to it due to spotty serial port access via virtualized machines.

If you want to continue to use this relic (as I do), you basically have to commit to finding and maintaining a legacy machine to do so.

 

[MTS2000des]

What he said. These legacy radios such as MTS/MCS, Astro Saber/Spectra/XTS3000 were the first CPS platforms Motorola ever developed, and that was back when the O/S was Windows 2000/XP up until Vista, at which time these products were retired. The last MCS/MTS CPS was updated was back in 2008 for rebanding. Trying to read/write with anything OTHER than Win 7 32 bit is a waste of time. Good news is plenty of dual core CPU laptop/desktops flood Goodwills, thrift shops and Ebay for nothing. Buy a few NOW and keep them in good health BEFORE they all dry up and they become as expensive and scarce as 286/386/XT machines are for programming older relics like Saber/Maxtracs/Spectra analogs, etc.

 

[HunterGatherer]

T

The newest i was able to get the mcs2000 cps to work on is Windows 7 32bit. Dont think it would work on anything newer. You could set up dualboot. I wouldnt try using a VM as they are unstable.

;
thanks mate

I agree, don't think you will have any success running that CPS on a win 10 operating system. If win 7 32 bit won't work go back to XP 32 bit. A real serial port helps things as well. You can't purchase this software anymore, it's long been EOL'd by /\/\. Google is your friend in finding the latest version. Even the last version of this CPS is not going to run on win 10 as its probably 10 or more years old.

Thanks mate

What he said. These legacy radios such as MTS/MCS, Astro Saber/Spectra/XTS3000 were the first CPS platforms Motorola ever developed, and that was back when the O/S was Windows 2000/XP up until Vista, at which time these products were retired. The last MCS/MTS CPS was updated was back in 2008 for rebanding. Trying to read/write with anything OTHER than Win 7 32 bit is a waste of time. Good news is plenty of dual core CPU laptop/desktops flood Goodwills, thrift shops and Ebay for nothing. Buy a few NOW and keep them in good health BEFORE they all dry up and they become as expensive and scarce as 286/386/XT machines are for programming older relics like Saber/Maxtracs/Spectra analogs, etc.

cheers mate thanks

T

I can and do run it in a VM for ease of making changes to the codeplug on an accessible computer, yet I keep an old Win XP laptop (dell d830) running just for writing to the MCS2k & other vintage moto hardware (which is done by a pentium 75 laptop). I can read the radio from the VM running XP, yet I choose not to take the chance of writing to it due to spotty serial port access via virtualized machines.

If you want to continue to use this relic (as I do), you basically have to commit to finding and maintaining a legacy machine to do so.

Thank you mate appreciate the info.