[Linker Error] TEXTFILE.LIB' contains invalid OMF record, type 0x00 1

[xljohn]

Greetings,

After I got instructions from Ronald about the MapObject, now I passed the compiling process. Now linking, error:

[Linker Error] 'C:\KARL\PC_IIE_JAN_18\LIB\TEXTFILE.LIB' contains invalid OMF record, type 0x00

Oh, my! Can any guru give me some hints? Thanks and thanks.

John

 

[2ffat]

You didn't say which BCB you are using. Sounds like TEXTFILE.LIB was compiled with a different version of Borland C++ than you are currently using. If you have the source code, recompile it, otherwise, you will have to do some tricks with wrapping the .LIB in a .DLL and use implib to get it to work.



James P. Cottingham

When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity.
[tab][tab]Albert Einstein explaining his Theory of Relativity to a group of journalists.

 

[xljohn]

James,

Thanks you very much for your quick reply.

After posting the thread, I open the textFile project and recompiled it. The original code was created using BCB 4 or 5. I fixed some bugs in it, then it works fine. But now there are errors, I'm not happy. Run time error:

The instruction at "0x005429cd" referenced memory at "0x00000000". The memory could not be "read".

I think the problem comes from a null pointer being referenced. But where to locate the pointer? Can you give me some hints?

Thanks again.
John

 

[2ffat]

Ouch! This is a hard bug to track down since it may not even be your program doing this. If you look in the NT, 2000, and XP Pro workstation forums you'll find all sorts of references to this, even with MS products. Some solutions are, look for a null point in your program as you noticed, bad RAM, a poorly written DLL, invalid printer reference (surprisingly a common problem), older HP printer driver, a trashed pagesys file, etc., etc. These seems to be no common fix.

I would first look to make sure any objects you create are properly destroyed. Sometimes this can cause a null pointer. Next, I would check all pointers by displaying their contents on screen (start with the obvious one first). Nasty work but it has to be done. After that, check your RAM, check your printer drivers, service patch, etc.


James P. Cottingham

When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity.
[tab][tab]Albert Einstein explaining his Theory of Relativity to a group of journalists.

 

[xljohn]

Thanks. You're really a guru and I'm really a beginner, what you said make me lost.

I think the pointer checking will be painful since the project has hundreds of pages(not lines), and it was not created by myself. It's written in BCB 4 or 5 in 1999, and it used MapObject LT. Now I'm using BCB6 and MapObject 2.1. So...

I don't know how to check the RAM and printer drivers and service patches. Why they are working on my project? Sigh...

Can you give me some more specific instructions? Thank you very very much.

BTW, I'm using HP laser jet printers hooked up by intranet. System: win 2000. AMD Athlon, RAM:256MB.

Thanks.
John

 

[2ffat]

Unfortunately the thread that explained this is now gone and I can't remember all the details. One thing I do remember is the HP printers were a problem if they were NOT local. Specify a local printer as a default.

Another option is to compile the program as a stand-along (see FAQs in this forum on how to do that) and try running it on another computer. If it works there then the problem is not the program but the computer.


James P. Cottingham

When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity.
[tab][tab]Albert Einstein explaining his Theory of Relativity to a group of journalists.

 

[xljohn]

James,

Thanks. I will read the FAQs to learn how to compile the program as a stand-along.

John