PocketMatrix

First off, I would check the return code of fseek to make sure it isn't failing first. ferror returns the current error code, even if it wasn't set in the last function call (the only things that clear the error code is clearerr, fclose and the unsupported rewind function). The Windows system error number 32 is "The process cannot access the file because it is being used by another process." I don't know if that corresponds to the errors as returned by ferror or not. Whatever creates fpse.ini is not writing to it while you're trying to read, is it?

Also, remember that it is possible for the filesystem on your Pocket PC / Storage Card to become corrupted. It is just a standard FAT filesystem. If the file is corrupted errors could certainly be encountered when trying to read it. Try pulling it up in Pocket Word or copying it over to your PC.

Dan East

Ok, as I pound a book into my head, I think I fixed the problem (knock on wood). It appears as if another file included in the program defined fopen, fseek,... with it's own set of comands. Now, I have fixed that, and here is hoping that it will work

Yep, that was it. I wasted a day of programing because a simple fopen was declared incorrectly. Wow, am I pissed right now.

Good call