Page 1 of 1
ODB / Runtime error ASTRO RSS
Posted: Sat Jun 07, 2003 10:40 pm
by radiorepair
Just wondering why I keep getting an error (ODB file does not match runtime) after I edit the ODB file for expanded RF?
I'm trying to take a 450-512 AS3 to 440. Could anybody help?
Thanks, PHIL
Posted: Sun Jun 08, 2003 4:12 am
by RESCUE161
You have to make sure you do a 'check sum' before editing. That way you can go back in after you edit to change another non essential part of the file to make the 'check sum' go back to what it was before the mod was done. I'm pretty sure this is your problem, so I would go back to the original (man, I hope you saved the original ODB in another place) and do a check sum of it. Then go to your 'new' ODB file and do a check sum there. Then search for a text string that you would normally NEVER see, like:
"Warning! The operating system you are using has detected water in your RSS! Press 'F3' to initiate spin cycle.
Edit that file around until the check sum matches the original, then save it and try it again. Use the HEX calculator to make it easier to figure out how may hex figures it needs to move to change it...
The error message I typed was purely made up and doesn't exist. I just used it for demonstration purposes...hehehe
Checksum help
Posted: Sun Jun 08, 2003 6:55 am
by radiorepair
Thanks Rescue161, I'm trying that right now. I do have another question for you. After I edit all my figures and attempt to change an unused string to get my original checksum values do I add the figure from the hex calculator . Im using the hex calculator and get "16" . Should I delete characters to get the original CRC values or add 16 characters? Im a bit lost with how to proceed after the edit.
Thanks

Posted: Sun Jun 08, 2003 7:59 am
by RESCUE161
I am really no expert when it comes to hex editing. There are some on this board though.
The reason I used the hex calculator was to make it easy for me to match the original check sum. When you do the original checksum, you'll notice it will look like this:
Checksum 8 bit: 0x42
Checksum 16 bit: 0x6842
Checksum 32 bit: 0x01B96842
Checksum 64 bit: 0x0000000001B96842
The checksum that you do after the modification will be similar to this:
Checksum 8 bit: 0x47
Checksum 16 bit: 0x6847
Checksum 32 bit: 0x01B96847
Checksum 64 bit: 0x0000000001B96847
So you want to modify a non essential file in the program that will change those 47s back to 42s. If you subtract 42 from 47, you'll get 5. So you want to move that non essential file down '5'.
If the non essential file was like:
"Warning! The operating system you are using has detected water in your RSS! Press 'F3' to initiate spin cycle.
You could change the 'W', which is 57 in HEX, to 'R', which is 52 in HEX. This should move the checksum back to a 42. The example gave is pretty easy though, and most of the time it's a lot more in depth than that, but that's pretty much how I've done it. Once you get the checksum to match, just save it.
As I said, I'm no expert, so there may be an easier way. If I messed up anywhere, PLEASE somebody correct me! I don't want to pass bad info.
Good luck!
CRC Values
Posted: Sun Jun 08, 2003 8:16 am
by radiorepair
Scott thanks for helping me on this problem. I have done as you said and got all of the Checksum values to the original values however it seems that my CRC values are different than what I started with. Now when I attempt to run the software I get a general protection fault message.
I did save the original ODB file so I can always start over. I'll work on it some more but like wow this is a pain in the butt! Thanks, Phil
Posted: Sun Jun 08, 2003 8:33 am
by RESCUE161
Yes, I know. I've beat my head against the wall on some Orion software, but I finally got it to work. Maybe one of the 'HEXperts' will pipe in and help you...
Let me know when you get it to work, I can always use more information!
Posted: Sun Jun 08, 2003 8:46 am
by JAYMZ
Radio Repair...
Follow what Rescue161 said about fixing the checksum. Bring your original ODB file into hex editor and generate the checksum wihtout any mods done. Write the checksum down!! Your modded file has to match that.
And you may need to edit the bandsplit in the executable file as well in order to get the expanded band limits. If you look on the spectra page for a bandsplit modification there are a couple of small DOS-Window type programs that you can use to find the bandsplit tables in the DOS RSS. Most of the RSS uses the same type of format. It's just a matter of finding it. Those converion utilities will help you in finding what you are looking for. For example: If you are looking for the band edge of 450 in the RSS you would need to search for a hex string similar to 0000 0000 0020 7C40 . You'll be able to pick out the whole bandsplit table that way. It's a little tedious but the work is well worth it. I've used that utility to help me modify the GE Orion DOS RSS to take a low band Orion into the 6 meter range.
I beleive that utility was created by "xmo" around here so he may be able to explain it better than me. Or at least explain the logic behind it.
PS Rescue161 is it a bad thing when you get that error? The LCD on my laptop broke when I put it in the washer on the spin cycle.

j/k
Posted: Sun Jun 08, 2003 9:06 am
by RESCUE161
LOL, I usually send that to users on our network at work using 'net send'. They freak out and call our computer guys...
Most of the time I put something like:
The system server has detected that you have entered an illegal web site. Please press 'OK' to acknowledge accessing this site... hehehe