Here are some snips from MSDN. Looks like some of the things to try when
recompiling may only apply to a C compiler, but maybe you'll find
something here.
-Tom
<From MSDN>
Linker Tools Error LNK1136
invalid or corrupt file
The input file either has a corrupt header or is zero size or abnormally
small.
See Corrupt Object File for more information.
Corrupt Object File
Sometimes the linker is unable to process your object files because they
are corrupt. Besides the usual causes of corrupt files such as network
problems or exposing a floppy disk to a magnetic field, sometimes the
compiler writes an incorrect object file, which you should report to
Microsoft Product Support Services. See the Technical Support command on
the Help menu for more information.
After you have ruled out a hardware, operating system, or network
problem as the cause of the corrupt object file, you should try the tips
below because sometimes by changing compiler options and recompiling,
the compiler will write a non-corrupt object file.
Here are some things to try when recompiling:
Turn off optimization with the /Od (Disable) option.
Disable incremental compilation with the /Gi- (Enable Incremental
Compilation) option.
Disable minimal rebuild with the /Gm- (Enable Minimal Rebuild) option.
Compile with the /Gy (Enable Function-Level Linking) option to package
functions.
Use a different code generation option. See the /G (Optimize for
Processor) options.
Change the order of functions and global variables.
<END FROM>
- Tom
Brett Burton <br
...@fmei.com> wrote in message
news:sneke5436tt56@corp.supernews.com...
> I have looked everywhere for any documentation on this error, and have
had
> no luck hopefully someone can shed some light.
> I get this error when I am attempting to build the EXE file. I have
tried
> doing so on a few different computers with lots of disk space, but
they all
> give me the same error, but sometimes in different OBJ files.
> Please let me know what the causes could be. And any solutions if
possible.
> Thanks,
> Brett Burton
> Programmer
> FME
> br...@fmei.com