rloew

I am talking about both at the same time. I have a schematic for my Y cable and it uses separate pins. My MA785 is a Gigabyte Motherboard, but it supports only one at a time. It does some test during the BIOS phase and sets the PS/2 Port one way or the other. I have had problems where it gets confused and thinks my Mouse is a Keyboard. I have to plug in a different Mouse, boot the Computer, restore the original Mouse and reboot again.

I have the proper cable but the Motherboard doesn't support it. I found it easier to use a Mouse on the PS/2 Port and an USB Keyboard. There is no COM Port. Navigation through Installation is easier during the USB Driver Installation where the Keyboard fails. Windows 95 will not boot, without a warning, if no detected Mouse, unless you set an Option. USB Keyboards do need Drivers. The Files are already present, but you have to go through the detection sequence.

Not necessarily. As I posted earlier, my MA785 has a single combo PS/2 Port. It can handle either a Mouse or Keyboard but not both. I have the PS/2 Y Cable but it does not work. I think only some laptops support that Y Cable.

If you use my Patch, HIMEM.SYS works just fine above 512MB. If not, then HIMEM issues are not my problem. I suggested the experiment because LoneCrusader has a Motherboard that takes nearly a half hour to boot due to a HIMEM related issue. Apparently the future arrived. Now we can work on a solution. The new Scan shows that the 0:31:5 Disk Controller is incorrectly reporting that it is in Legacy Mode. It clearly shows that it is using Native Mode I/O Ports. This is an Intel bug. Switch the M.2 to "Force SATA" and send a "SCANPCI ALL" report. Switch the M.2 to "Force M.2" and send another "SCANPCI ALL" report. If neither work, it will be necessary to add an Exception entry to the SATA.INF File.

The FX 5200 also should work.

The two Controllers in Legacy Mode will conflict with each other causing unpredicatable behavior. Write Errors are entirely possible. If you cannot switch the Intel Controller to Native Mode or disable it, you will have to remove the Asmedia Card. Rename the ASPI2HLP.SYS File. I cannot support HIMEM.EXE. Use HIMEM.SYS with the /M:1 Option. You did not provide the "SCANPCI ALL" output I asked for.

"Task Manager Replacement"? What did I tell you about complicating issues with undescribed modifications. VDD errors are associated with Graphics. Remove the failing SATA Controller and see if it is redetected upon reboot. If it is, post the Output of: SCANPCI All Also display the Resources for the failing SATA Controller

It was a long shot, but the Marvell Controller would have gotten further.

Rescan with SCANPCI All Two Legacy Controllers will not work unless one uses an alternate I/O Configuration. Is there a jumper or configuration program for that Asmedia Controller Card?

Why is your background blue not black? I said it has to be run from true DOS not from a DOS Box even Full-Screen.

It may have been during our experiments, but I put it in before I released the Package. The 82.69 was an exact fit. I could not include Drugwash's flag Byte so I put it in myself rather than forcing people to Hex Edit it in.

Try: AHCISW Noint If same result, no need to show screenshot.

I already told you that the Shutdown Patch was already incorporated in my larger NVSIZE Patch. You are trying to apply my Shutdown Patch a second time. Drugwash's Patcher added a one Byte flag to my Patch Code. With the other Patches my Patch was an exact fit. There was no room to add the flag to tell his Patcher that it was already Patched.

There is one experiment either of you can try. This will test if the AHCI can be forced off. This applies to the H110 and Z170 Motherboards. Connect a partitioned and formatted Hard Drive, with at least one working program on it, such as MEM,EXE, to a Motherboard SATA Port, preferably SATA #0 (#1 if no #0). Boot true DOS. Run the attached AHCISW Program. Does it crash, reset, display an error message, or display a completion message? Does it hang or do you get a new prompt? Run the program on that Hard Drive. Internal Commands do not count. Does the program run, or does it hang during loading? Copy a file to the Hard Drive or within the Hard Drive. Does it hang or do you get a new prompt? Can you access the new File? AHCISW.COM

The FX 5500 should work. You can even try older Drivers such as 77.72. No Patches needed.

Now there are three Hard Disk Controllers. One Intel Controller in Legacy IDE Mode. One Intel Controller in Native IDE Mode (needs SATA Patch if anything connected). The Asmedia Controller in Legacy IDE Mode. I see an incompatible Video Card. You are still trying to load ASPI2HLP.SYS in your CONFIG.SYS File. Try removing it or commenting it out. Add the /M:1 option to HIMEM.SYS in CONFIG.SYS. You could try waiting half an hour to see if it boots in normal mode.

Test 3 and 4 will return exactly the same result. Test 4 is redundant.

A bad customer blames my Software when he/she hasn't eliminated other possibilities. If there are unexpected problems, I wan't to know about them so I can try to fix them. This requires careful and sometimes extensive debugging, especially since I am not there to control the process. It becomes a lot harder when there are all sorts of Programs, Hardware or Settings that I don't know about. E-Mail or a product specific Forum is the standard way to provide Customer Support. Since other people have not had a problem installing my Patches, I don't think they are learning anything from your trials and tribulations. The Manuals are intended for normal usages and situations. They have proven sufficient so far. Extreme cases will always involve Customer support. I have two AMD970s working, so getting yours to work should not be so hard.

You switch between AHCI Boot Mode and IDE Boot Mode using the BIOS. You can Install in either Mode. Install SATA Patch, ATA0106.INF and AHCIBIOS if in AHCI Mode. Install SATA Patch, and SATA.INF if in IDE Mode. You cannot change the Mode after Installation without messing thing up, if you don't follow the proper procedure. If you want to be able to change Mode, then Install everything for BOTH Modes when Installing Windows. Boot in one Mode to activate one set of Drivers, then Boot in the other Mode to activate the other set of Drivers.

The SCANPCI dump shows the Intel Controller in AHCI Mode and the Asmedia Controller in Legacy IDE Mode. Unless you set an Override in the BIOS, I would expect the Boot Device to be the Intel Controller.

Unfortunately, based on test results that MrMateczko sent me, this Motherboard adds two more nails to the Windows 9x coffin, and I do not have enough Patches to cover them. There are not enough slots or BIOS Options on this particular Motherboard to put together a decent 9x System. If I can get an AHCI Driver working, it might become a minimally decent System for 9x. Unfortunately, the work LoneCrusader and I have been doing on USB3 has not gotten very far, so a fix seems far off.

New systems introduce new issues that no one can foresee. My Patches, just like any other Software, cannot be guaranteed to work in such cases. I don't appreciate the accusations you keep making against my Software. You have yet to prove that there is any bug in any of them. MSFN is a general interest forum, not a Customer Support Department and certainly not MY Customer Support Department. I said that my Patches would support an AMD970 because I had two AMD970 based Computers using them. You encountered a lot of problems because you either didn't read the instructions, or had created problems before you even applied my Patches. Also, since you only bought one license per Patch, you are only authorized to use my Patches on one Machine each.

The RTF was fine under Windows XP. I tried a AMD 770 Motherboard. It was much better at overclocking than the 970. I was able to get it to work, but it didn't seem very stable and there was something I didn't like about it so I returned it. The amount of RAM, once you exceed 4GiB, will not make any difference whatsoever. Having one, two or four sticks might make a difference in performance due to interleaving.

My Interrupt Fix only solves problems where the Mouse freezes, jerking once every 15 seconds, along with shutdown of other devices sharing the Video. not Mouse, interrupt, such as disk drives. The 7600GS might need the PCI Patch in my NVSIZE Package. Nothing new in the McKracken package. Try reading the entire thread.

The use of shared interrupts is one of the issues my SATA Patch has to resolve. The standard Windows setup does not distinguish between Legacy (separate interrupts) and Native (shared interrupts) mode Controllers.