When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
bump- anyone?? i' opened a trouble ticket a couple days ago with evoscan, still no reply. at this point the software is completely useless to me if i can't edit/add data items. is there a way to enable debug mode so i can see exactly what's triggering this error?
Something must be wrong with the data item your attempting to edit "Timing Alpha". Make sure you have your entries set correctly for any changes you made, otherwise delete all entries for Timing Alpha so it's blank so you can go back to the main screen.
Something must be wrong with the data item your attempting to edit "Timing Alpha". Make sure you have your entries set correctly for any changes you made, otherwise delete all entries for Timing Alpha so it's blank so you can go back to the main screen.
Thanks for the suggestion- unfortunately that's not the problem. I've tried reinstalling multiple times with different versions and have also tried to delete all items and/or all but one item that I know is configured correctly and I still get that error...
Looks to be some kind of bug. I would suggest reinstalling/finding a clean xml data file for the parameters and manually editing the data as suggested in post #1 Solution until Hamish can resolve the issue.
Looks to be some kind of bug. I would suggest reinstalling/finding a clean xml data file for the parameters and manually editing the data as suggested in post #1 Solution until Hamish can resolve the issue.
Manually editing looks like my only choice as of right now- I know for a fact the xml files are not corrupt- I have a feeling this 'bug' has something to do with the fact that I'm on windows via parallels (virtual machine running on mac osx). I think parallels mounts the filesystem as a netshare or something along those lines- I haven't had issues with any other software (EcuFlash for example) however- and am able to datalog in EvoScan etc. If I could simply step through the code in a debugger and or have access to verbose output I'm sure it's something simple to fix....