Help! - "Error performing inpage operation"

[Dan Sundin]

I recently started getting the above message "Error performing inpage
operation."

I get this when attempting to COPY or XCOPY files via RAS from my
office to home PC. I don't remember ever seeing this in the past, but
can't pinpoint whether it started since upgrading to NT Server 3.51.

I've tried restarting - no luck. Sometimes the message comes up
immediately, other times it seems to copy for awhile.

Thanks for any info!

Dan

[Marc Palmer]

I'm afraid this isn't helpful, but I've been getting the same message on 3.51 when
I use Borland C++ 4.5 to compile my programs. It only happens sometimes, when BC++
is executing the DOS program IMPLIB.EXE. I'm mystified too.

--
Marc Palmer

[David Boreham]

In article <878088...@landscap.demon.co.uk>
Marc Palmer <Ma...@landscap.demon.co.uk> wrote:

This error is caused as follows:

The virtual memory manager issues a filesystem operation to bring a virtual
page in from a pagefile to physical memory. Becuase of the way NT files work,
this may happen for both "tradiational" paging operations to the system pagefile, and
also for file I/O to a regular file. Interested parties should read Helen Custer's recent
MSJ article on the subject.

Anyway, if said fileystem operation fails, the VMM is put in an awkward position.
It doesn't really expect these operations to fail, in general they only do if
a) there's a hardware fault; b) there's a media flaw which causes an
unrecoverable read error; c) the operation was to a network redirector and the
network connection has timed out or otherwise been hosed.

Under these conditions, the system just gives up trying to recover gracefully and
issues the error message dialog you're seen.
These errors should not be happening !
There is something wrong with your machine (Marc) or your network connection
(Dan). I've seen these problems caused by bad disk hardware, bad disk controller
hardware, bad motherboard PCB tracks and unterminated SCSI cables (and by poor
quality SCSI cables). Have a look at these issues.
The RAS case is almost certainly due to a flakey modem connection.

Hope this helps.

This particular aspect of NT's error recovery and reporting could do with
some improvement. You can get one of these "inpage error" dialogs just because
you're reading from a floppy disk with defective sectors on it. I'd really prefer
"your floppy is crap" or something similar :)