Parse errors in EcuFlash
#1
Parse errors in EcuFlash
I am having problems with parse errors in opening a ROM. 966940011 with lots of mods. I use notepad to do all the edits.
the msg I get is
XmlHandlerHelper
"parse error at line 394 column 9
tag mismatch"
I made backup copies before modding the def file 96940011.xml and also evo7base.xml. Those were working just fine
After editing and saving as 96940011.xml and evo7base.xml, I tried opening and got the parse error. double checked all files for errors and did not see any.
So I deleted the 2 modded files and opened the backups.....but same problem
parse error again
Just to check I tried opening a different ROM 88580014 and that works perfectly
Has anyone identified the problem why XmlHandlerHelper is not parsing things properly?
What is a tag mismatch?
Need help here !!!!!
Milburn
the msg I get is
XmlHandlerHelper
"parse error at line 394 column 9
tag mismatch"
I made backup copies before modding the def file 96940011.xml and also evo7base.xml. Those were working just fine
After editing and saving as 96940011.xml and evo7base.xml, I tried opening and got the parse error. double checked all files for errors and did not see any.
So I deleted the 2 modded files and opened the backups.....but same problem
parse error again
Just to check I tried opening a different ROM 88580014 and that works perfectly
Has anyone identified the problem why XmlHandlerHelper is not parsing things properly?
What is a tag mismatch?
Need help here !!!!!
Milburn
#2
Evolved Member
iTrader: (13)
it's not that Xml parser is not parsing properly. It's that you or the program you used to edit the xml file made mistake. Tag mismatch in xml definition is that the parser can locate a matching end tag in the xml logical tree document. For example,
<rom>
</rom>
the first line is <rom> mark beginning of an xml node and the </rom> is the end. If the parser traversal the tree and eventually can't find a logical node that match the you got the error.
Copy the backed up xml and carefully edit it again using windows NotePad. Try not to use other software as some of them put in some characters for their own format.
Also, leave no blank line in the beginning of the file.
<rom>
</rom>
the first line is <rom> mark beginning of an xml node and the </rom> is the end. If the parser traversal the tree and eventually can't find a logical node that match the you got the error.
Copy the backed up xml and carefully edit it again using windows NotePad. Try not to use other software as some of them put in some characters for their own format.
Also, leave no blank line in the beginning of the file.
#3
it's not that Xml parser is not parsing properly. It's that you or the program you used to edit the xml file made mistake. Tag mismatch in xml definition is that the parser can locate a matching end tag in the xml logical tree document. For example,
<rom>
</rom>
the first line is <rom> mark beginning of an xml node and the </rom> is the end. If the parser traversal the tree and eventually can't find a logical node that match the you got the error.
Copy the backed up xml and carefully edit it again using windows NotePad. Try not to use other software as some of them put in some characters for their own format.
Also, leave no blank line in the beginning of the file.
<rom>
</rom>
the first line is <rom> mark beginning of an xml node and the </rom> is the end. If the parser traversal the tree and eventually can't find a logical node that match the you got the error.
Copy the backed up xml and carefully edit it again using windows NotePad. Try not to use other software as some of them put in some characters for their own format.
Also, leave no blank line in the beginning of the file.
so fixed now just frustratin' waste of 3 hours
thanks though :-)
Milburn
#5
Evolved Member
iTrader: (5)
Join Date: Jun 2007
Location: Lombard IL
Posts: 552
Likes: 0
Received 0 Likes
on
0 Posts
Also in order to make it easier to find your mistake, in notepad, go to "view" and check status bar. It will show you which column and line you're at currently. This was a huge discovery to me. previously I was counting lines
#6
Any ways the thing that fixed it was taking the very last </table> out, apparently it is not needed for 1D tables at all. There are many instances in all the other rom defs that do not terminate 1D tables, just lists the next table name.
I ended up also putting the WGDCC tables much further in the file so they show up at the beginning of the turbo section now. Easier to see
I also tested the def file and rom on my other laptop running Vista Home Premium with EcuFlash 1.38 ( same as on my loogging laptop ) and it worked right off the bat there.
Thanks for all the suggestions and I hope other people that have this problem find this series of posts to fix the issue. Sticky maybe ?
Thread
Thread Starter
Forum
Replies
Last Post