R
Rob Graham
I received an Access file from what should be a totally reliable source,
unzipped it, checked it functioned OK and sent it off to the floppy for a
back-up. Before it even got there the screen went blue with a message at
the top about a 'kernel_data_inpage_error' - no pop-up as in the blue SOD.
The drive then disappeared altogether when I rebooted and the machine booted
on the slave which has W2k on it too. I tried swapping the drives round,
changing the master/slave status and did get the original drive to reappear
again at one point but running extremely slowly with the red light almost
continuously on; it finally booted up (15minutes) in safe mode and allowed
me access but the blue screen reappeared with the same error report and
'Dumping physical memory to disk : <counting serially upwards>'. At some
number greater than 100 it rebooted itself, reported it couldn't find an HD
again and obviously just hung.
I tried setting this drive to slave and booting off the original slave set
as master so that I could run an A-V but the seemingly faulty drive just
hung everything with the HD light always on.
I'm now back on the 'good' slave with the 'duff' HD removed.
Anybody got some ideas please.
Rob
unzipped it, checked it functioned OK and sent it off to the floppy for a
back-up. Before it even got there the screen went blue with a message at
the top about a 'kernel_data_inpage_error' - no pop-up as in the blue SOD.
The drive then disappeared altogether when I rebooted and the machine booted
on the slave which has W2k on it too. I tried swapping the drives round,
changing the master/slave status and did get the original drive to reappear
again at one point but running extremely slowly with the red light almost
continuously on; it finally booted up (15minutes) in safe mode and allowed
me access but the blue screen reappeared with the same error report and
'Dumping physical memory to disk : <counting serially upwards>'. At some
number greater than 100 it rebooted itself, reported it couldn't find an HD
again and obviously just hung.
I tried setting this drive to slave and booting off the original slave set
as master so that I could run an A-V but the seemingly faulty drive just
hung everything with the HD light always on.
I'm now back on the 'good' slave with the 'duff' HD removed.
Anybody got some ideas please.
Rob