It's not always called native mode. Sometimes you have to turn off AHCI mode, or look for IDE or Compatibility mode.
Main Topics
Browse All TopicsHi all,
I'm hoping you can help me.
Heres the problem, I have an HP laptop and the option for disabling SATA native mode is missing in the BIOS.
The reason this is a problem is XP was installed on it with SATA Native mode disabled, (I know I done the installation of XP on it), and now it's blue screening.
I'm buggered if I know what the heck is going on. I KNOW the option to disable it WAS in the BIOS, now it's not.
I've downgraded the BIOS with no effect. The people who use the laptop swear nothing new was installed (And although they fell into the Antivirus 2009 malware they learned from it and have been very good ever since.)
Where the heck has the SATA Native mode settings in BIOS gone is my question in essence.
It WAS there and it's disappeared.
Also if that bios option has disappeared completely never to return, could I slipstream the base level drivers into an XP install CD and then use that to do a repair install/install over the top? (I.E if we don't find a way to fix the BIOS problem how do I recover the machine keeping everything in tact)
Thanks for any advise you can provide.
Terry
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
HP Pavilions never had option to swith to SATA native.
You need to get SATA driver loaded before XP install.
Here is how, note you will need external floppy drive:
http://www.intel.com/suppo
Or you can slipstream SATA drivers to XP installation disk, you will need SATA drivers:
http://downloadmirror.inte
And slipstream it with nLite, here is how:
http://www.nliteos.com/gui
qz8dsw - Hope you know you can inject the SATA drivers into the Bart-PE.
Download the latest SATA drivers from the Vendor Site.
Extract
Copy the drivers into the Bart-PE 's storage drivers location. (You can refer the Bart-PE manual for Where and How also... )
You then will also have to inject the drivers into your XP-Image as Aliokas said. If its GHOST then injecting is much simple.
Hope this helps.
@rindi I've been looking for them too, ALL of them.
The system configuration part of BIOS not has a very limited subset of what I remember used to be available.
@Aliokas - YES they most definately did. Might be a regional thing (NZ as opposed to the US), but they did. I done the XP install myself and distinctly remember having to switch it off, then when I upgraded the BIOS XP failed to boot and having to go into bios and switch it off again. I'm TOTALLY at a loss as to where it went.
It seems by both Aliokas'h comment and bvvjagan's comment my best bet is slip streaming unless rindi can add more. On to the second part of my original question, Would a repair install from a slip streamed XP CD put the drivers on the hard drive so the HD install of XP can boot?
Notes before you say it
1) I don't have an external enclosure for a 2.5 mm hard drive to plug it in via usb to another machine.
2) I don't have a USB floppy drive for it.
(I'm doing this as a favour for a mate, which was what the original install a new hard drive and install XP was)
Thanks for your help so far,
Terry
You could try copying the drivers to the C:\Windows\Drivers folder. You'd have to get a 2.5" to 3.5" adapter so you can connect the disk internally to a desktop PC (connecting internally is always better than using an external enclosure, as enclosures add a point of failure). If it is a SATA drive you don't need any adapter as long as your Desktop PC uses SATA, which all modern PC's do.
You might also be able to access the HD within the PC using Puppy, knoppix or another LiveCD, builtin driver support is generally a lot better than that of windows...
http://www.puppylinux.org/
http://knoppix.org
Ok, I've got access to the drive slip streaming the SATA drivers, but now for the bad news.
Because XP was installed with SATA Native mode off, although the drive is now recognisable/visable the XP cd, the contents are not.
Format is unrecognisable (If you go through the XP install until it gets to the drive parameters).
I'm still totally as a loss (And bloody annoyed) as to where the option went in bios, I've been through it 10-15 times now.
There is nothing that even hints at SATA/AHCI/IDE/Compatabilit
So to save the data as such, I'm thinking I would need to hook it up to a sata controller with Native mode off before I could read it from what I'm seeing, would that be correct in your experience?
Thanks for your help so far,
Terry
In this case your issue has nothing to do with using SATA mode or not. You rather have an issue with the drive itself. Whether you can access the data on the drive or not has nothing to whether it was formatted using native or standard modes, the format itself stays the same.
You can try recovering any important data from the drive first by connecting it to another PC and scanning it with getdataback. If the tool lists the files you need, you can register the tool so you can copy the data off. You can also try imaging the drive using bootit-ng (the trial version is fully functional), or partimage which is included on the Parted Magic CD:
http://runtime.org
http://terabyteunlimited.c
http://partedmagic.com/
Then run the HD manufacturer's diagnostic utility on the HD. There are usually short and long test. First run the short test and then the long one. These tools you'll find on the UBCD:
http://ultimatebootcd.com
If the diagnostic tool tells you the drive needs to be replaced, get it replaced. If on the other hand it asks whether it should try to fix any errors, allow that.
Sometimes after this step it is possible that the drive is usable again (maybe chkdsk /x has to be run at bootup to fix filesystem errors).
If the drive isn't yet bootable, use the Parted Magic CD again and run testdisk. After running testdisk and the drive still isn't usable, and you got the data off earlier, you can again try using the manufacturer's utility to lowlevel format or Zero fill the drive. After that it should be possible to install a fresh OS to it.
Hi rindi,
Don't get me wrong, the drive itself is fully functional, IMOHO it is because the SATA mode option has disappeared from BIOS. Let me explain some more.
I've tried the tools available under the ultimate boot CD, and although the harddrive checks out fine in itself the file system on it does not.
The drive is not too old at all and also passes HP's own bios checks and the HD manufacturers diags both short and long.
I'm interested when you say "has nothing to whether it was formatted using native or standard modes" as I've always found the modes to be mutally exclusive (I.E a drive formatted under sata native mode can't be properly read by a controller under non native mode and the converse also applied).
That comes from personally on my own machine as well as a couple of others.
If the mode the controller is in does not matter why does XP blue screen if it does not have the correct "F6" drivers from the XP install in my case?
If your system is set to use a SATA controller in SATA mode, the OS needs the drivers to see the controller and the devices connected to it. The OS also needs a driver for IDE controllers, but these are already included in XP so you don't require 3rd party drivers for these, unless it is an unusual controller. If it doesn't have the drivers windows bluescreens. That has nothing at all to do with how the drive is high-level formatted and the file-system. The only possible issue could be if the controller uses a different mapping for the Cylinders and sectors etc in ATA mode compared with IDE mode, but I've never seen a controller use different mapping when using another mode.
If you move a disk that was using SATA mode on one PC to another PC that doesn't have SATA mode, you will still be able to read the file-system on it. You may just not be able to boot into the OS that is on that disk, because you are using different hardware.
Also, the disk itself may work OK if you have tested it using the manufacturer's tools, but those tests normally test the disk's surface and it's SMART status, and sometimes it can fix surface errors (it doesn't actually fix them, it rather remaps them so those bad areas aren't used anymore). Once these tests are OK the disks themselves are OK, but that doesn't mean the file-system or partition table is.
A corrupt file-system can very often not be accessed by windows, and that seems to be your error. Again, this has nothing to do with SATA or IDE modes. To repair a corrupt files-system you need to run chkdsk /x. The problem is that chkdsk, when run on a bad disk, can cause you to loose data, for that reason it is important to first run the manufacturer's low-level test to make sure it is OK. That's the reason I told you above to start with that first. Normally after chkdsk has repaired your file-system you will again be able to access it normally on it's original PC. If chkdsk can't be run because the drive letter can't be accessed, the file-system is either too corrupt, or the partition table is bad. In such a situation it is best to repartition and format the disk. So if you can't run chkdsk even with the disk connected to another PC, that is what you should do. This will also require you to reinstall your OS from your recovery media.
The first option I mentioned above, getdataback, is the best data recovery utility available. With this you can get data from a bad drive whether the file-system or partition table is bad, and sometimes also when the disk itself is bad, so if you have data worth getting from the disk, that is always what should be done first.
Hi Rindi,
I have resolved the problem machine itself by just refomatting with the SATA drivers slip streamed in the XP CD. (Fortunately these people took backups onto an external drive on a regular basis.)
Drive fully checks out with 3-4 different HDD testing tools.
I have no idea what happened to make the drive partition an unknown format. The only known change was the SATA mode being forced on. (Well that won't worry it again).
Thanks all for your help and thanks Rindi for the extra explainations around the SATA modes.
Business Accounts
Answer for Membership
by: qz8dswPosted on 2009-08-09 at 23:59:09ID: 25057624
Oh, and the reason why I'm leaning towards the SATA native mode being the issue is my BART-PE boot CD and a Windows XP install CD can't see the drive is there, but the HP BIOS can run diagnostics on it.