No Ext13H support!

[edelm]

Maxtor drive showing in bios, but when I run DiskPatch I get the message
No Ext13H support detected, disks can not be accessed

Please tell me I can get this to work!!

Thanks

[Joep]

Hello,

How old is the PC? And, do you have the DiskPatch logfile for us? And, what's wrong with the disk, why are you trying DiskPatch?

One of the easiest tests to see if the lack of int13h support is due to a disk error or the system BIOS, is to slave the disk to another system and run DiskPatch there.

[edelm]

Hi,

I'm not sure how old the disk is it was running on a pc that's about 6 years old but tbh it looks quite new (just started working with this company, 2 days ago!!!!)  It was running w2k and all was fine until it suddenly wouldn't boot on Monday. 

I had it in as a slave the first time I ran disk patch but disk 1 wasn't seen.  What can I do?

[Joep]

Hello,

You attached to a different meachine as a slave? How old was that PC? That's the issue: I am trying to establish if the PC is maybe to old to offer extended int13h support, or, if there is some serious problem with the disk.

Are you running DiskPatch from diskette, and if yes, can you post the logfile please?

Alternative test: If slaved to a Windows system, does iRecover see the disk?

[edelm]

Log below

This was with win xp master and maxtor drive as slave (not attached according to diskpatch)

The pc it is now attached to is 3yrs old. IRecover doesn't see disk either.  It is not showing in Device mgr either.

Thanks

Code:

.../000:03/LOG> ### LOG START ###
.../000:03/LOG> DISKPATCH 3.4.100
.../000:03/LOG> (C) 2000-2008 DIY DataRecovery
.../000:03/LOG> Contact info: HTTP://www.DIYDataRecovery.nl
.../000:03/LOG> MemFree: 77Kb
.../000:03/LOG> CommandLineParms: /sup
.../000:03/LOG> LogDate: 08-07-2008
.../000:03/CFG> FilePath="1/.\DPFILES\"
.../000:03/CFG> LogFilename="DP.LOG"
.../000:03/CFG> ReadRetries="32"
.../000:03/CFG> WriteRetries="32"
.../000:03/CFG> MaxReadErrors="32"
.../000:03/CFG> MaxWriteErrors="1"
.../000:03/CFG> ReadDelay="0"
.../000:03/CFG> VfyFixedBadSect="1"
.../000:03/CFG> CleanAfterDOD="1"
.../000:03/CFG> DiskReset="1"
.../000:03/CFG> SectorSkip="1024"
.../000:03/CFG> AutoSaveState="1"
.../000:03/CFG> DumpFoundSectors="0"
.../000:03/CFG> FixFats="1"
.../000:03/CFG> MaxFatScan="51200"
.../000:03/CFG> MaxDataColEntries="256"
.../000:03/CFG> IgnoreF8FF="0"
.../000:03/CFG> DownSizeExt="1"
.../000:03/CFG> ScanSignature="55AA"
.../000:03/CFG> Rebuild="00"
.../000:03/13H> Ext13H installed test requested
.../000:03/13H> Disk found at 128
.../000:03/13H> Ext13H version: 2.1 / EDD-1.1
.../000:03/13H> Ext13H Support: Extended disk access functions
.../000:03/13H> Ext13H Support: Enhanced disk drive functions
.../000:03/13H> Drive Interface Info :
.../000:03/13H> Disk 128 X13H data : 16383/16/63 234493056/512
.../000:03/13H> Ext13H tested ok
.../000:03/FDL> DiskList requested
.../000:03/FDL> Disk found at 128
### DISKLIST.ARRAY ###
__D_|________LBA_|___H_|__S_|__GB
128 | .234493056 | 255 | 63 | 111
..0 | .........0 | ..0 | .0 | ..0
..0 | .........0 | ..0 | .0 | ..0
..0 | .........0 | ..0 | .0 | ..0
.../000:03/IAS> AdmiSector found on disk 0 (128)
.../000:04/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:04/WAS> AdmiSectors in use : 0+
.../000:04/KEY> DEMO/1
.../000:04/PFC> UDMA driver not loaded
.../000:04/PFC> PQstuff signature not detected on disk 0 (128)
.../000:05/PFC> Partition State backup not found on disk 0 (128)
.../000:05/PFC> No Repair date found on disk 0 (128)
.../000:17/USD> No source / disk selected
.../000:17/USD> Select disk completed
.../000:17/LOG> RunTime: 000:17
.../000:17/LOG> ### CLOSE LOG ###

[Joep]

Let me add to that a little bit ...

int13h is the protocol used by DiskPatch to access a disk. Every PC built after 1998 should support that. If the disk is SCSI you may need to specifically enable int13h in the SCSI setup. If the disk is SATA you may need to enable the legacy or compatibility option in the system BIOS. Still, normally DiskPatch detects a disk without problems. If it does not, try the disk in another system.

If we still can't see the disk (or int13h errors pop up), int13h information we receive from the BIOS may not make sense. This can be the case when the disk lost it's own configuration data. If that's the case you will be needing a professional to recover the data that will use special hardware, software and experience to access the disk.

[Joep]

The pc it is now attached to is 3yrs old. IRecover doesn't see disk either.  It is not showing in Device mgr either.

Hmm, bad. And slaved to the other system, used different cables? Just to make sure it isn't the cabling? Once you have verified that I am afraid that our or any DIY software can't help you.

Maybe www.retrodata.co.uk can help. Their pricing is very reasonable.

[edelm]

Thanks anyway!