I am using Win96 to program scanners (pro96 and PRO2096) but when I download the RR data via win96 I don't get all the data that is posted on the site. Why is that?
WIN96 not getting all the RR data
- Thread starter N0FON
- Start date
seamusg
Member
It is usually a bad character in the DB. It would help if you posted which system you're trying to download.KB0TQF said:
jfdurham2000
Member
Unfortunatly the Colorado state system is too big to put in one bank. You may have to program this system in manually.
Dolceg
Member
I had a similar problem. Do it bank by bank and you may have to do it a couple times before the info shows up in Win 96.
loumaag
Silent Key - Aug 2014
I have moved this to the software support forum (since that is where it belongs) and if the offending character is ever found and discussed here, I will try and fix it as soon as possible.
DonS
Member
BTW...
The easiest way to determine where Win96 is barfing is to look at the file XMLDUMP.TXT that Win96 creates (in the directory where WIN96.EXE resides).
The file contains two sections. The first is the raw XML as received from RR. The second is a "parsed" version of the XML, indicating how Win96 has processed the data. By looking at the very end of the file, you can see the last "valid" XML item. You can then look at the first part of the file, find that last valid item, and then look at the next item.
In this case, the last valid item is TGID 2429:
Looking at the first part of the file, searching for "2429" (including quotes), shows the next item as TGID 2431, which has:
(the apostrophe is the offending character).
If it's assumed that the XML will always contain 7-bit "ASCII" characters (which is an OK assumption until non-7-bit characters are correctly encoded in UTF-8), we can also do the following (from a bash prompt, if you've got it) to find all "bad" elements:
The easiest way to determine where Win96 is barfing is to look at the file XMLDUMP.TXT that Win96 creates (in the directory where WIN96.EXE resides).
The file contains two sections. The first is the raw XML as received from RR. The second is a "parsed" version of the XML, indicating how Win96 has processed the data. By looking at the very end of the file, you can see the last "valid" XML item. You can then look at the first part of the file, find that last valid item, and then look at the next item.
In this case, the last valid item is TGID 2429:
Code:
Element: name=tg, value=
Element: name=dec, value=2429
Element: name=subfleet, value=
Element: name=desc, value=Prisoner Transport "DCR"
Element: name=disp, value=
Element: name=group, value=Colorado Dept. of Corrections
Element: name=mode, value=D
Element: name=tgid, value=104060
Code:
desc="Denver Woman’s Correctional Facility"If it's assumed that the XML will always contain 7-bit "ASCII" characters (which is an OK assumption until non-7-bit characters are correctly encoded in UTF-8), we can also do the following (from a bash prompt, if you've got it) to find all "bad" elements:
Code:
$ pwd
/c/Program Files/WinXX/
$ grep --v
grep (GNU grep) 2.5
$ grep [^[:print:]] xmldump.txt
<tg dec="2431" subfleet="" desc="Denver Woman's Correctional Facility" disp="" group="Colorado Dept. of Corrections" mode="D" tgid=116823" />
<tg dec="2433" subfleet="" desc="Denver Woman's Correctional Facility" disp="" group="Colorado Dept. of Corrections" mode="D" tgid=116824" />
$DonS
Member
Nope. The dump file is just a record of what Win96 received and processed.KB0TQF said:
You need to get the DB changed to fix the bad characters. Lou said he'd try to do it, as soon as it was identified here.
- Status
Similar threads
- Question
