We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
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
This doesn't match your previous error of:
Linking *** FATAL ERROR 204: INVALID KEYWORD
As Stefan says, you seem to be very confused by all this; and it doesn't sound like you have anyone else to hand who really knows the tools to assist you? If you're in Southern England, maybe we could help you out with a day's on-site Consultancy - look at this problem and give you a general walk-though on the Tools? If you're interested, mail
Sales at Antronics dot co dot uk
I finally solved the problem as I reverted back to the original version of software but using a dongle of another version as the original dongle along with the original software cannot be found at the moment. So all the problems disappeared once I got the version back using the original installed directory copied over the C51 and Keil directories so I have a working enviroment of sorts. As you said I have little experience with the Keil tools and as you guessed I am working completely on my own with no one to assist me but at the moment I don't see any likelyhood of the company paying for seminars. So anyway I will persevere for the moment. Still in the case Im in up to my eyeballs with problems I will have to seek external consultancy.
"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