I am having problems with locating a second function to follow on from the first.
The following linker command works....
?PR?_LOADER?LOADER(0FA00h),?PR?_HEX2CHARNICK?LOADER(0FC30h)
but i do not want to specify the location of the second function just the first, looking at the documentation it says that i should be able to do the following....
CODE(?PR?_LOADER?LOADER(0FA00h),?PR?_HEX2CHARNICK?LOADER)
This causes a linker error..
What do I need to put in the linker command line so that the second function follows immediately on from the first.
If line length is a problem why does the following command work... be happy it does, I just recall that I have had instances of line length problems.
Since that made me 'mend my ways" forever, it could, of course, have been solved in a later release.
Erik
Most line length problems are not application problems but Win32 problems. M$ are not a company run by developers, so they can't see the need for long command lines. Since their own tools are creating build scripts or piping commands on-the-fly, their developers don't complain to product management.
A lot of third-party tool vendors have teached their tools to support a @fname command line parameter, representing the name of a file with the actual command line.