A genuine stab-in-the-dark, David...

Have you tried moving the printer itself?... either away from the data serving machine if its already there or to it if its elsewhere.

good luck


>Dear all
>
>A customer is using the HP BUSINESS INKJET 2200 and he keep getting invalid seek offset. This is the information I have assumed up to now, they are printing a report that uses two memos, one of these memos is changed quite a lot, which may be the problem. They use the printer from 8.00am to 10.00pm and two or three times a week they get invalid seek offset. There seems to be no pattern to why this is happening
>
>I have done the following: -
>
>1. Contacted HP - no help!
>2. What we call a memo repair (add a memo field to the table, then deleting it and then packing (We have found that if you do this to a corrupted memo file, you may be able to restore it, or have a bit of corruption))
>3. Destroy indexes and recreate them
>4. Have the network checked
>
>The network is a peer to peer of 4 Windows 98 machines which the printer is connected to one, shared so the others can use it.
>
>I am also aware that HP writes bad drivers which do not follow the windows standard for memory arrangement
>
>Any help would be appreciated
>
>Thank you
>
>David
>Anagram Systems