rloew

Your BOOTLOG.TXT shows that ASPI2HLP.SYS failed. WININIT.INI shows that VMM32 hasn't been aggregated so you never reached protected mode. You should have gotten further without any patches or workarounds. Either your Installation CD is bad or you have a serious problem with your Computer. Do a Memory test if you haven't previously.

Post a Bootlog.

Did you use SETUP /p i when you installed Windows?

You made things more complicated by installing a lot of stuff and then trying to add the SATA Patch. Normally the SATA Patch is installed during installation of Windows 9x, long before any other Drivers. It is also not in the main section of my Website because it is not a fully polished package. I do not normally use Intel Motherboards, so I don't know the various combinations of Drivers used with each Motherboard. Only the Intel Disk Driver INF File needs to be removed or renamed so that it is not used to redetect the Drive. You can send me the ICH5IDE.INF File you mentioned. I cannot say if the disabled second GPU is an issue. I have not tested this configuration. I haven't tested the Intel 1000 MT either. The RAM Patch itself does not fix Hardware issues for games. In fact, a few DOS games break when you exceed 2GiB of RAM due to bugs in the games code or the DPMI module. The MBR issue is confined to the Standard Windows 9x MBR. If you have something else, then there may be no problem and if so, my MBR might be usable. My special MBR only replaces the Standard MBR, so it causes should be no problems. It only fixes the problem with Booting NTFS or ExFat Drives. It will not help with using NTFS Data Partitions. Grub4DOS uses it's own MBR.

I ran some experiments n the hope of supporting my Extended MBR approach to >2TiB Hard drives. As a minimum you need to modify or replace ATAPI.SYS. The Windows 2003 Version did not work. The UNIATA replacement does work. I was able to get past 2TiB with UNIATA using ASPI Commands but still did not see >2TiB through the \\.\PHYSICALDRIVE# Interface. I did not try your DISK.SYS with UNIATA.

Unlike newer system, Intel apparently didn't change Device IDs between Native and AHCI Modes. The Intel INF File is device specific so it gets priority during Device Detection. There is a small possibility that Intel made incompatible changes to the Registry. VIA did with theirs. The SATA Patch hides and protects ESDI_506.PDR to reduce the risk of it being overwritten. That is why you don't see it. Your BOOTLOG.TXT shows a MagicISO Driver loading just before ESDI_506.PDR. I'm not sure what impact that might have. Be sure that the Intel Disk Driver INF is renamed or deleted. Then try using PURGEHDC P A again. A wrapper for the MBR is not possible as the MBR runs first. If you are replacing a 9x MBR then nothing else should be affected. If it is not a 9x MBR then the replacement may not be needed. I can't guarantee that my RAM Limitation will fix everything. I have no idea what else is in your System. But it should fix the VFAT Problem.

The Hard Disk Controllers use their own DMA Engine so they do not use the built-in DMA Controller. RFDISK is a full Package so there is a Manual Included with the Free Demo. Download the Demo and read the Manual. I could write a MBR updater that would be cheaper if that is all you want. You can mix usage with other Partition tools as long as you do not use the Multi-Boot Profile MBR. At a minimum you can use RFDISK to refresh the MBR after you are finished with the others. The AMD970 crashed on VFAT which is usually a sign of memory exhaustion in the DMA area. Gigabit Ethernet and/or large Registries can cause this. The fix for this is the /M Option on my RAM Limitation Patch. Unfortunately this means another Patch, but you get to use a lot more RAM if you do. You already have the full nVidia Patch so you don't need the Shutdown fix that Dencorso recommended unless you aren't putting the Patch in that machine. I sent you the AHCIBIOS Package. I forgot to mention that you will have to Enable DMA on all of the redetected Disk Drives.

Close enough. KernelEx provides some User Mode support. My WDMEX provides some Kernel Mode support. But neither is complete. One particular problem is that there are Functions that have been changed, not just added. Supporting New Software can break Older Software. Some Programs that can work in either OS, run checks that may be triggered by the partial support, causing the Program to fail due to the lack of full support. Another problem are changes to System Structures and Internal Names.

Apparently not.

The SATA Patch does not fix nVidia problems. These are unrelated issues. I posted a fix for the nVidiia Shutdown problem. U98SESP3 sets the Registry to Enable DMA. PURGEHDC P A will erase them. There is a disclaimer in U98SESP3 saying it is not for SATA Drives. I got your order, but there is no AHCI "Patch" so I asked you to confirm you want AHCIBIOS. When I said a DVD might not work with my Patch, I was referring to a configuration prohibited my Microsoft, that is more likely when using SATA. It is not a problem with the Patch. Microsoft explicitly prohibits an Optical Drive as a Primary Master on the Legacy Mode Controller. With PATA Drives, the Primary Master slot is normally used by the Boot Hard Drive, so the problem doesn't occur. With SATA Drives and my Patch, the Boot Hard Drive is connected to the Native Mode Controller, so the Primary Master slot on the Legacy Mode Controller is free. This allows the prohibited configuration to be used. I removed this restriction in my Terabyte Plus Driver. The $21 is for my RFDISK advanced partitioning tool, not just for the MBR. The MBR is just one feature. You can get rid of some of those nVidia errors by disabling it's Services.

I have a tool called SCANPCI that lists all Hardware IDs on the PCI Bus. It does not identify what they are. You would need to go to the PCI IDs Website to find out what they are. Writing a Program to read the Registry would provide more information, but only for recognized Devices.

If you have material new information or questions, put them in a new Post rather than updating an existing Post. Otherwise there is no notification and I may never see them. Not all BIOS Disables are total. Some BIOSes remove the disabled Drives from the INT 13 list but do not remove the Controllers from the PCI List. DOS won't see them but Windows can.

Go to the "Disk Drives" Section in Device Manager. Turn on DMA on each Drive. This should improve performance. PURGEHDC erased all of the previous settings. If you enable AHCI, the Controller ID and Type will change so it will appear as a New Unknown Device. You do not need to disable the existing Driver as it will not be loaded for that Controller. In this case having ATA0106.INF installed would be a liability. Be aware that some AHCI BIOSes incorrectly handle Odd Address Transfers in Compatibility Mode and can cause corruption. I would recommend using AHCIBIOS and ATA0106.INF for long term usage.

You can use my SATA Patch with the U98SESP3 ESDI_506 File, but you must apply the Patch after it is installed. U98SESP3 replaces the ESDI File. It doesn't Patch it.

I see the problem. You overwrote the Patch with another ESDI_506.PDR. It looks like the Version that comes with U98SESP3. Delete the 2 BAK Files. Rerun the SATA Patch Program. When installing something like U98SESP3, you have to Uninstall the SATA Patch, Install the Third-Party Software, then Reinstall the Patch, all without rebooting.

I just E-Mailed you a Program that can completely clean out all Disk Drivers and Settings from the Registry. What is the size and date of the WINDOWS\SYSTEM\IOSUBSYS\ESDI_506.PDR File? Boot into Normal Mode using the Logging Option. Post the last 10 lines from the resulting BOOTLOG.TXT File.

I am assuming that the SATA Patch has been applied and the SATA.INF File is in the WINDOWS\INF Folder. Switch all 6 SATA Ports to IDE in the BIOS. Boot into Safe Mode. Remove all of the Controllers except Primary and Secondary ones. Remove the NOIDE Registry Value. Reboot into normal mode. AHCIBIOS is $11.00 US. We can worry about this after you resolve the SATA issue.

Since the SATA Patch is normally installed from DOS, a GUI is not practical. The Error 10 will remain until you reboot after removing the NOIDE Entry. Do not remove the IOS Key, just the NOIDE entry. I was referring to the Sil3512 Config Menu before the Hard Disk is Booted. AHCIBIOS will work with the M5A97. You can contact me by E-Mail to order it. RFDISK does not cause data loss if properly used. It will replace the MBR with one I designed, if you use the "M" Command.

I did some further experiments with a RTL8136 Revision 7 NIC. For reasons that are unclear, RTGND.DOS reported an internal error with the RTL8136. So you need the RTEND.DOS Driver File for the RTL8136. The NetrtgRM.inf file can be edited by replacing 8168 with 8136 everywhere and replacing RTGND with RTEND everywhere.

You have the latest standard SATA Patch, which is for IDE. I also had sent you ATA0104.INF which is for IDE RAID Mode as in some old VIA Controllers. A few days ago, I sent you ATA0180.INF which is for Mass Storage Drivers such as the Sil 3512, and PATCHPCI which fixes the problem with VIA Controllers that made using RAID Mode necessary. The Sil 3512 has a configuration menu. If I allows selecting IDE vs. AHCI, select IDE. Use the ATA0180.INF File to install it. I wrote the ATA0106.INF because some early PCI-E Cards used the AHCI Code. Like my Laptop, the Cards did not Enable AHCI by Default so they worked with the INF. The AMD 97 Motherboards will Enable AHCI when using RAID or AHCI Mode so the INF is not enough. I developed a separate program (AHCIBIOS) after you bought the SATA Patch that can turn off AHCI and provide a replacement BIOS to run DOS until Windows can boot. You would need this Program if you want to multi-boot with other OSes using AHCI. TRIM is not an AHCI related Function. I sell a separate TRIM Program. The NOIDE Value is in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\IOS. It is a Binary String that would be set to 01. The "terabyte" Patch you refer to is my High Capacity Disk Patch, which overcomes the 137GB limit. It lets you use 2TiB Hard Drives but is not described as a "terabyte" Patch as I have other Patches with that name. The RFDISK MBR is installed when you use RFDISK. I haven't offered it separately. See the description of RFDISK on my Website.

@densorso I used a TSR I wrote rather than a DOS Device Driver. I have two TSR Programs that I wrote to mount Disks. One adds an unrecognized Disk to the INT 13 Chain and provides the low level access Code. This comes in handy when hot-swapping Drives. The second can mount a Partition so it can be accesses by a Drive Letter. This can be used with the first TSR or to mount hidden Partitions. By extending existing tables, I did not need to write an actual DOS Driver. @jaclaz I didn't expect it to boot in CSM Mode but it should have detected the Drive. You can't Partition or Format a Drive you cannot see. That makes it a serious flaw.

I don't remember the make and model as I went through a number of Laptops. I tested a few in the store but for later ones I had to buy them and return them. The internal drive had the default GPT format. The Drive was physically present but was not detected, so no INT 13 Call would work. I had to load a raw driver to mount the internal drive.

Luck or sacrifice? I found a Laptop that would not recognize the internal Hard Drive in CSM Mode. A USB Key or CD would have been needed just to Boot DOS and Windows 9x.

There is only one SATA Patch. The SATA.INF File that comes with it handles Native and Legacy IDE Mode. The other INFs are for special purposes and are experimental so I provide them after consultation. The ATA0106.INF for AHCI, only makes it recognize an AHCI Controller. It does not add support for AHCI. There are three possible AHCI Mode scenarios: AHCI only. This requires an AHCI Driver which I have not written so far. AHCI on. This requires a separate Program such as AHCIBIOS to turn off the AHCI Mode before starting Windows. AHCI off. This is the only scenario where ATA0106.INF would work with my SATA Patch without other programs or Drivers. So far, only one cheap Laptop actually worked this way. Unless you have scenario #3, there is no point sending you the file. The SATA Patch was intended to be installed before connecting SATA Drives. The default Microsoft Driver will claim them and cause problems. If certain errors occur, the system will permanently lock out the Drivers. This is why I said to remove the "NOIDE" Entry from the Registry. At a minimum you need to remove all Drivers that can be removed using Safe Mode and have everything redetected. I have two TeraByte Patches. The 1TB Partition Patch and the TeraByte Plus Package. You did not purchase either one. What "TeraByte" Patch do you have and where did you get it? Paragon is complaining about the MBR on the Hard Drive. It wants to know if you want LBA or CHS Support for the Partition. There is also a problem in the standard DOS/9x MBR. It Boots a Type 7 (NTFS/ExFAT/Etc...) Partition as CHS. I fixed this in my RFDISK MBR.

I used NetrtgRM.inf to install my 8111E. The Driver will scan for all 4 IDs and will do so automatically as it is not bound by the INF. Windows however is bound by the INF. Only one ID is listed in NetrtgRM.inf. The others have to be added. I do not know if the other three require any different settings.