I have a friend who is using windoooz CPS2.0 trying to program a ton of XTS3000 VHF radios and he has been experiencing numerous write failures, he can read a radio just fine but when he writes he runs into either 1 of 2 errors as follows "communication with radio failed" or the dreaded "cannot create stream" error messages. If after he reads a radio and modifies and then saves the code plug and then reboots his Laptop PC he can then write to more radios fine but only one or 2 more radios after which he has to reboot again and then repeat this sequence over and over and over, well I'm sure you get the picture.
He is using an IBM Thinkpad laptop/1 Ghz with 256 MB RAM so it's not a memory problem with the PC, oh yeah the PC O/S is windows 2000 profesional which the CPS says it runs on fine, and so far nothing from the Mot help on this issue.
Anyone out there using the XTS3000/astro saber CPS2.0 on a similar O/S who has any insight or ideas into what is going on, and no changing to the dos RSS is not a possibility as this friends govt. group has bought a ton of IBM laptops for just this purpose so he is stuck with using windooz software.
Mike
cps 2.0 and XTS3000 write problem with win2K
Moderator: Queue Moderator
Here are some excerpts from the notes during installation of Astro CPS version 2.00.00:
System Requirements:
--------------------
Operating Systems: Windows 98, Window NT 4.0 (SP 6 or higher),
Windows ME, Windows 2000 Professional,
Windows XP (Home and Office)
So, are you running regular Windows 2000, or professional? If these are brand new computers, have they been upgraded to at least service pack 2, from the Windows Update site? The latest is 3, but 2 should be fine. Here is some info regarding multiple retries in Windows 2000, from the same install notes:
CBI Programming may fail intermittently, especially on Dell PCs. On machines
where this is an issue, multiple retries might be required. Changing the port
settings as follows may help:
On Windows 2000:
1. Right click 'My computer' and select 'Manage' from context
menu.
2. Select 'Device Manager' on the tree in the left pane.
3. Expand the node 'Ports' on the tree in the right pane.
4. Double click the port that is being used
5. Go to 'Port Settings' Tab
6. Click 'Advanced'
7. Uncheck 'Use FIFO buffers' check box.
8. OK
If all else fails, do what I generally do with a new pre-assembled computer. Blow away the O/S (FDISK & Format) and re-load from scratch, preferably from a non-OEM version CD (use a plain-jane Win2k Pro CD instead). That way you know you're starting with a clean slate, without any third party crap possibly messing things up. While you're at it, do yourself a favour & set-up a dual boot with Win98SE & Win2k. That way you can pick & choose between the best that both have to offer.
Todd
System Requirements:
--------------------
Operating Systems: Windows 98, Window NT 4.0 (SP 6 or higher),
Windows ME, Windows 2000 Professional,
Windows XP (Home and Office)
So, are you running regular Windows 2000, or professional? If these are brand new computers, have they been upgraded to at least service pack 2, from the Windows Update site? The latest is 3, but 2 should be fine. Here is some info regarding multiple retries in Windows 2000, from the same install notes:
CBI Programming may fail intermittently, especially on Dell PCs. On machines
where this is an issue, multiple retries might be required. Changing the port
settings as follows may help:
On Windows 2000:
1. Right click 'My computer' and select 'Manage' from context
menu.
2. Select 'Device Manager' on the tree in the left pane.
3. Expand the node 'Ports' on the tree in the right pane.
4. Double click the port that is being used
5. Go to 'Port Settings' Tab
6. Click 'Advanced'
7. Uncheck 'Use FIFO buffers' check box.
8. OK
If all else fails, do what I generally do with a new pre-assembled computer. Blow away the O/S (FDISK & Format) and re-load from scratch, preferably from a non-OEM version CD (use a plain-jane Win2k Pro CD instead). That way you know you're starting with a clean slate, without any third party crap possibly messing things up. While you're at it, do yourself a favour & set-up a dual boot with Win98SE & Win2k. That way you can pick & choose between the best that both have to offer.
Todd
It is on Win 2K professional. I don't know if he has loaded any of the svc packs yet. We have been thru the com port settings especially those pertaining to CBI programming issues and he has set the ports as recommended for Win2k, with no changes at all. In fact he spend last week trying everything in the CD help files and still he has to reboot between radios. He already re-installed the O/S once and the CPS twice, the second time he reinstalled the CPS he was able to finally write to radios, prior to the 2nd CPS reinstall all he could do was read radios. I'll mention the win2K svc pack to him, that may be the only thing he forgot.
Mike
Mike
There is a non-professional workstation version, though I'm not sure what the difference is. Windows ME is just Win98SE with a few patches, some extra multimedia additions, and a system restore feature that causes more problems than it fixes. It is not based on the 32-bit kernel that NT/2000/XP share.alex wrote:There was never a "home" or "regular" edition of Windows 2000. Just Workstation, Server, Advanced Server, and Data Center.
The closest "home" version would have been Windows ME, which sucked as much as Windows 98 IMHO.
Todd's idea of putting 98 on as a seperate bootable OS however is not bad.
-Alex
Todd
When he re-installed the O/S, did he FDISK & Format first, or simply re-install over the existing data?mike m wrote:It is on Win 2K professional. I don't know if he has loaded any of the svc packs yet. We have been thru the com port settings especially those pertaining to CBI programming issues and he has set the ports as recommended for Win2k, with no changes at all. In fact he spend last week trying everything in the CD help files and still he has to reboot between radios. He already re-installed the O/S once and the CPS twice, the second time he reinstalled the CPS he was able to finally write to radios, prior to the 2nd CPS reinstall all he could do was read radios. I'll mention the win2K svc pack to him, that may be the only thing he forgot.
Mike
Todd
Right - ME was nothing more than a facelift with the same problems that 98 had, they now just have a prettier face.wavetar wrote:There is a non-professional workstation version, though I'm not sure what the difference is. Windows ME is just Win98SE with a few patches, some extra multimedia additions, and a system restore feature that causes more problems than it fixes. It is not based on the 32-bit kernel that NT/2000/XP share.alex wrote:There was never a "home" or "regular" edition of Windows 2000. Just Workstation, Server, Advanced Server, and Data Center.
The closest "home" version would have been Windows ME, which sucked as much as Windows 98 IMHO.
Todd's idea of putting 98 on as a seperate bootable OS however is not bad.
-Alex
Todd
I'm still quite confident that there isn't a non-worstation/server version. Next time I speak with my rep, I'll ask.
the words: Microsoft, Windows, System, and Restore do not belong in the same sentence.
THE only way to do a clean install is to follow the fdisk, format, and install. Sometimes "refreshing" the OS (installing right over itself again) can be a good thing, and sometimes it can cause more damage than good.
-Alex