Posted 17 April 2008 - 10:26 AM
I recently purchased Search and Recover 3d from a third party. I tried several times to install the programme from CD and am running XP Home. The programme appeared to install, but most of the time it could not be opened either from the desktop icon or Programmes. On the odd attempt to open the programme, a window opened with following "NT_read error; error no. 1167; drv 129, LBA 0, blocks 1; Abort, Retry or Ignore".
If I clicked on Ignore, the programme would open and appeared to be useable, but the fact this error window opened made me believe the programme had not loaded correctly. If it has loaded correctly, I wouldn't want all this difficulty opening it each time I wanted to use it.
I tried loading it in Safe Mode; the window opens and after clicking on Ignore, the programme will open. If the PC is then turned off and back on again however, the window no longer opens and the programme cannot be opened.
I phoned the vendor and explained the problem and was sent a second CD. Unfortunately there is no difference.
This is the first time I have experienced such a problem when loading a programme, and I have more than five years experience with my current PC system.
Firstly I scanned my hard drive with a reputable third party utility, which found no problems.
I then scanned it (a Seagate product) with Seagate's own Windows hard drive diagnostic software and again no problems were found. This diagnostic involved five different types of scan, including every sector on the drive.
Finally, I scanned it with Seagate’s DOS version of their hard drive diagnostic software, which would report on any faulty sector, and no faults were reported.
As an experiment, I have also downloaded the trial version of Search and Recover 4.0 from your web site, which loaded and opened without problems. Why should version 4.0 load and open properly and not version 3.0?
I would appreciate any help with overcoming this NT-error 1167 issue. I believe it means a device is not connected. I thought it may be that I hadn't switched on my external HD, but this made no difference either, so I have no idea which device it is referring to.