Russell:
You are probably onto something here with your suggestion about a gap in the HEX file image.

There are some other issues to consider as well:

1) What are the target object address range requirements? If the code is being run on one of the older style development type boards with a loader/monitor located at code addresses from 0x0000 through 0x3FFF (for example) then a hard coded ORG in source code that forces records in the hex file to be in the same address range may be simply ignored by the loader.

2) Does the taget environment even have code memory in the place where Marty is trying to locate the ORG?

3) Maybe his target environment has some special settings in the IDE (integrated development environment) or in the MAKE files that proclude the placement of code and/or the string data at certain addresses. It is possible to anticipate that the linker could have arguments provided to it that specify the default ranges of memory that are permitted and yet these may not be set properly to match the target processor.

Hope that helps....Marty it looks to me like its time to really look into these types of tool settings...
Michael Karas