This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Ongoing problem with linker Error 204 Posting linker file

Hi to you all
thank you for all the suggestions in relation to this problem.
I am posting the linker file for you to examine.I also have talked to the programmer that had previously been working for the company and he tried also to overcome the problem but with no luck.

 clock.obj, codes.obj, com_test.obj, comms.obj, config.obj, control.obj, crc.obj, &
eng_cod.obj, hols.obj, ind_init.obj, &
initmod.obj, inputs.obj, int10ms.obj, intercom.obj, keybd.obj, keyin.obj, &
lcd_mod.obj, man_cod.obj, mode_mod.obj, outputs.obj, overide.obj, &
print_c.obj, print_m.obj, print_r.obj, print_s.obj, printer.obj, &
records.obj, sensors.obj, settime.obj, setup.obj, site_cod.obj, start.obj, &
strings.obj, test.obj, utils.obj, zone.obj , startup.obj, disp_int.obj, &
ramdata.obj, e2_data.obj, s_zone.obj, s_sensor.obj, s_output.obj, &
s_input.obj, s_lux.obj, s_w_snsr.obj, s_codes.obj, r_sensor.obj, &
r_zone.obj, r_output.obj, r_input.obj, clockdat.obj, time.obj, display.obj, datatran.obj &
TO V10001e.abs &
RAMSIZE(256) CODE(0100H) XDATA(?xd?r_zone(00000H), ?xd?r_sensor(000e0H), &
?xd?r_output(00240H), ?xd?r_input(002e0H), ?xd?ramdata(00310H), ?xd?s_codes(0d007H), &
?xd?s_zone(0d037H), ?xd?s_sensor(0da1fH),?xd?s_input(0db67H), &
?xd?s_output(0dd87H), ?xd?s_w_snsr(0deffH), ?xd?s_lux(0df01H), &
?xd?clockdat(0E010H),00000H) &
SYMBOLS PUBLICS

Also all the files compiled and there where some assembly files within here.
However I edit the linker it will always come up with the same error.
Any suggestions would be welcome.
Thanks in advance
Nick

Parents
  • "I don't see any likelyhood of the company paying for seminars."

    Your 1st post on this subject was 24 Sep; you apparently got someting working on 7 Oct.

    For the benefit of the bean-counters, you might like to tot-up the cost of those 10 lost working days (I assume you didn't work weekends?) against a day's training/consultancy.

    Not forgetting, of course, to use your company's full overhead rate - probably at least 2x your hourly rate... :-0

Reply
  • "I don't see any likelyhood of the company paying for seminars."

    Your 1st post on this subject was 24 Sep; you apparently got someting working on 7 Oct.

    For the benefit of the bean-counters, you might like to tot-up the cost of those 10 lost working days (I assume you didn't work weekends?) against a day's training/consultancy.

    Not forgetting, of course, to use your company's full overhead rate - probably at least 2x your hourly rate... :-0

Children
No data