gw@sickkids.UUCP (Graham Wilson) (10/24/90)
I have been experiencing "Invalid Object Module" errors during the linking
phase - and I am stumped as to what is the cause. Can anybody offer any
suggestions? Here are the facts:
I am using Microsoft C 4.0 under MS DOS 3.3 on a 386 system with a Connors
80 meg IDE hard drive.
I started getting the errors a few months ago. The link would abort because
some object module (either just compiled, or one from a library - it seemed
random) was invalid. Run the link again, and either a different object file
was found invalid, or all worked fine. I moved the library files to a RAM disk,
and never again got an error from an object module in a library - but the
errors from object files on the hard disk continued. Sounded very much like
a flaky hard disk to me, and the people who sold me the system agreed. The
harddisk was changed. Still getting errors. Change the controller. Still
getting errors.
Also note that I could not force the problem to occur under controlled
circumstances (i.e. comparing files on hard disk to those on RAM disk
thousands of times always worked %100).
I have used the same copies of this software previously on two different
systems, with no problems!
So what is causing these errors? If it is a bug in the MS linker - why does
it not occur with RAM disks, and if it is a hardware problem - how come I
cannot force it to occur?
Any help and/or suggestions are greatly appreciated!
-----------------------------------------------------------------------------
Graham Wilson, CyberFluor Inc, 179 John St #400, Toronto, Ont, (416) 977-5450
UUCP: {watmath!utai!utgpu, uunet!mnetor!lsuc}!sickkids!gw
BITNET: gw@sickkids.utoronto
INTERNET: gw@sickkids.toronto.edu or gw@sickkids.utoronto.ca