MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.
Search the Community
Showing results for tags 'AHCI'.
Found 3 results
Hi! I have HP Pavilion dv6 notebook. It uses the AHCI mode of drives handling and my Win7 work OK with it. Now I found a way how to modify the BIOS to allow to change the AHCI mode into IDE mode. I have some reasons why to do it - sometimes I experiment with various hobbyists OSes and also FreeDOS which I sometimes boot feels better with IDE setting. So please dont't respond me to simply keep the AHCI setting. However after switching into IDE the win7 booting unsuccesfully ends in the first loading screen and the computer restarts. I expected this behaviour, though. My question is: The reinstalation certainly helps. But is necesarry the whole reinstalation with rewritting of all system? Or there is some possibility of limited instalation like "fix the booting problems"? Or the installation CD is not necessary at all and it can be solved in some other way? And last question: Can I expect big performance slowdown or the effect will be rather negligible?
I have been doing some further research on using Hard Disk Controllers in AHCI Mode with Windows 9x. First I have a warning. On at least two Computer, I observed that Disk I/O is corrupted when running on a Computer with AHCI enabled and an odd Start Address is requested while in Virtual Mode. I have not seen corruption but the risk is there. IOS.VXD does two Reads in Virtual Mode. One to check it's Safe List and one while loading DRVSPACX.VXD. These occur during Boot. EMM386 cannot be used with AHCI Enabled as COMMAND.COM will crash. I have written a small mitigation Program to correct this issue. There are a number of possible AHCI scenarios which I have listed as follows: 1. AHCI Only Controller with Direct Protected Memory Interface. The Marvell based HighPoint card, I previously posted about, falls into this category. As is, no Windows 9x recognizeable Drives can be present. Windows 9x will crash before it even has a chance to load Drivers. If the BIOS or Card can be modified to use Interrupt 15 or other supported Method then it may be more useable. See Scenario #2. The HighPoint Card had a Patchable Option ROM so I could modify it. Otherwise a compatable MBR or DOS DDO AHCI Driver is needed to allow Windows to Boot. I do not know if any exist. 2. AHCI Only Controller with Compatable Protected Memory Interface. An AHCI Controller of this type can boot Windows 9x, but see Warning above. I know of no AHCI Driver for Windows 9x so it will run in Compatability Mode at best Also, I have noticed that some of the earlier AHCI Drivers miscompute the size of the Hard Drive if it is larger than 2TiB and can lockout parts of the Drive well below the 2TiB limit. 3. Switchable AHCI Controller with Direct Protected Memory Interface. As in Scenario #1, Windows will not boot using this Mode as is. Otherwise read Scenario #4. 4. Switchable AHCI Controller with Compatable Protected Memory Interface. If the BIOS allows you to switch to Native Mode and you can do so without causing unresolvable issues with other OSes, do so, it will make things much easier and safer. Many newer Motherboards use AHCI when in RAID Mode so this may not help. If there is no BIOS Option or you will mess up another OS continue reading. This is the Scenario for my Warning above. If your Computer is not at risk, or you use my mitigation program, you may be able to run Windows 9x in Compatability Mode. I have developed a DOS DDO that switches the Controller to Native Mode and replaces the BIOS Driver. I am still running tests so I have not published it yet. In conjunction with my SATA Patch and a modified INF File, I have been able to run Windows 98SE in Protected Mode from a Motherboard started in AHCI Mode. 5. Switchable AHCI Controller with Native Mode Default. If it correctly reports the Native Mode Class Code then it can be treated like any other SATA Controller. If it reports the AHCI Class Code, as at least one JMicron PCI-E SATA Card does, a modified INF File will be needed. Either way, my SATA Patch will be needed for proper operation with Windows 9x unless a specific Driver is available. EDIT: I have reduced the severity of my Warning as the serious corruption issue I originally warned about was traced to a TeraByte Plus Patch I was using for my 6TB Test Drive. I have corrected the Patch and haven't seen corruption even without mitigation.
I try to install WinXP on a Notebook "Acer Aspire 3810T-354G32N". By trying this I get only trouble . Problem 1: The Acer doesn't have a floppy- or CD-ROM-drive, which makes booting difficulty. I can only boot from USB-stick. I can prepare USB-Sticks with Rufus or WinSetupfromUSB to be bootable. Problem 2: If I use Rufus, so the USB-Stick will not be bootable on the Acer. But I can "solve" problem2 by using WinSetupFromUSB (I tried several Versions, 1.0beta7 and 1.4). What I already did with WinSetupFromUSB: - Made a USB-Stick bootable with FAT32 file format - created a USB-Stick with WinXP-install-files; thereby the files were copied directly from a WinXP-install-CD, not from an ISO-file. Then it is principially possible to boot from this USB-Stick; I get first this screen http://www.winsetupfromusb.com/wp-content/uploads/2013/09/Ashampoo_Snap_2014.01.20_17h30m44s_001_QEMU.jpg and can select the WinXP Setup. The setup at the first starts fine, but after loading FAT file system I get - either a bluescreen with the 0x0000007B error (if I created the USB-Stick with WinSetupFromUSB1.0beta7) - or a blackscreen with blinking cursor in the top left of the screen. At http://www.winsetupfromusb.com/faq/ and http://forum.notebookreview.com/acer/586065-xp-aspire-3810t.html there are described some workarounds. I have tried some of them: 1.) I have already tried a modified ntdetect.com Ntdetect.7z, with no difference. 2.) I changed the BIOS setting "SATA MODE" from "AHCI Mode" tho "IDE Mode" and back, with no difference. 3.) I tried to select "Auto-detect and use F6 SATA/RAID/SCSI Driver" like described in http://www.winsetupfromusb.com/wp-content/uploads/2013/09, with no difference. 4.) I installed nLite on my (working) PC and tried to add following driver AHCI_Intel_220.127.116.119_XPx86XPx64_A.zip, which also can be downloaded from Acer's website: http://global-download.acer.com/GDFiles/Driver/AHCI/AHCI_Intel_18.104.22.1689_XPx86XPx64_A.zip?acerid=633773721411807534&Step1=Notebook&Step2=Aspire&Step3=Aspire%203810T&OS=X01&LC=en&BC=Acer&SC=PA_6. But even 4.) had no effect :angrym: ! I get still the blue- or black-screen described above. Maybe I did something wrong? I think I have added the driver not properly into nLite. Could it have something to do with the fact that I would need "text mode drivers" (or similarly)? PS: I had to unpack the nLite ISO- file before creating the bootable USB-Stick with WinSetupFromUSB. PPS: Here is the *.ini-file created from nLite LETZTE SESSION.INI.