IPS Driver Error

[Bâshrat the Sneaky]

mySQL query error: UPDATE ibf_topics SET title='PROB | RIS: nVidia NIC driver not detected during RIS-boot',description='' WHERE tid=54344

SQL error: Incorrect key file for table: 'ibf_topics'. Try to repair it
SQL error code: 
Date: Sunday 09th of October 2005 12:01:09 PM

This is the error I got after trying to edit the topic title of this topic. I tried it 5 times, each time with the same result.

I tried to edit the topic title of another topic in that same forum: no problems.

I hope you can fix this without too much problems, xper?

[xper]

Link doesn't work. Takes me to forums index.

[Bâshrat the Sneaky]

Never mind, it's now in EVERY topic I try, at least in the DriverPack LAN forum.

EDIT 1: In the DriverPacks General Discussion forum there aren't any problems.

EDIT 2: Nor in the DriverPack MassStorage forum.

EDIT 3: No more errors....

EDIT 4: Hmm... it seems it just doesn't work for *SOME* topics...

And you see it coming here, xper... it's those topics that were created during the time that you disabled topic descriptions... It *must* be that. Or am I out of line here?

Edited October 9, 2005 by Bâshrat the Sneaky

[Bâshrat the Sneaky]

My theory seems to be incorrect, since I cannot edit this topic's title either and this one has been started June 21 of this year, months before that (temporary?!) policy of you, xper.

So it must be ... a damaged database? I don't know... I hope you can figure it out.

EDIT:

an example of another error:

mySQL query error: UPDATE ibf_topics SET title='REQ | Xircom CardBus driver?',description='SOLVED' WHERE tid=51555

SQL error: Incorrect key file for table: 'ibf_topics'. Try to repair it
SQL error code: 
Date: Sunday 09th of October 2005 01:07:04 PM

As you can see, the exact same error... it must be the "incorrect key file for the 'ibf_topics' table" that is causing this.

Could you fix that?

Edited October 9, 2005 by Bâshrat the Sneaky

[xper]

I edited this topic http://www.msfn.org/board/index.php?f=108&t=54344&p=379268& w/o problem. I did repair database too.

Try now.