gordo999

Hi...remember you from winraid. A little bird told me. How's it going? I have been using x64 on all devices. I am not running any x86 installations except for XP. I discovered recently that Asus uses an unconventional pinout on its mobo serial ports. The standard serial to USB connector uses a different pinout. I made my own cable and I need to check it against the Asus pinout. Normally that should not be an issue when using a back-panel connector that connects a 9-pin serial D-type connector to the mobo, which has a 10 pin connector. I just don't remember how I made the connection but I have to alter it extensively from the standard 10-pin layout. If you look at the mobo pinout, the pins start at the bottom left hand corner as pin 1. You can tell the orientation because there is no pin where pin 10 should be. So, if you look at the pins with the top right-most pin, having no pin, oriented to top right, then pin 1 is on the bottom left hand side. The standard serial connector then proceeds left to right from 1 to 5. The Asus connector uses another standard where pin 2 in right across from pin 1. So left to right it is 1,3,5,7 and opposite 2,4,6,8 with no pin where pin 10 should be. On a standard RS232 9 pin DIN plug, the Rx and Tx are right beside each other whereas on the ASUS 10 pin layout they are across for each other diagonally to the left. If you look at an equivalent serial 9-pin DIN connector, it is very different. It is shaped like a 'D' with flat diagonal edges an has no pin 10. If you lay the D flat so the narrow end is on top, the pin count begins at the far right side and proceeds 1 to 5 along the bottom, right to left. then pin 6 is on the top row at the far right. Then it proceeds 6,7,8,9 right to left. That means pin 6 is across from and between 1 and 2 and pin 9 is across from and between 4 and 5. Asus tells you nothing about that in earlier literature.You have to dig for it. In serial comm, the Rx (receive) pin is always pin 2 and the Tx (transmit) pin is always pin 3. It is crucial that the other pins be correct as well, otherwise machines cannot communicate. I have more urgent problems right now but checking the serial connections will be a priority when I get back to this issue.

1)Hi, Mov AX. Thanks for info. I was using the USB to Serial adapter attached to the host USB port, so the target end was a serial port. However, the host was a W7 HP Elite Pro laptop. 2)I'll need to research that and check Windbg dependencies for XP. The LAN chip is a Realtek PCIe 2.5 GbE Family Controller. Just looked it up and got to realtek site. They supply installers going back to XP. Impressive. They indicate the model as RTL8125. In Device Manager it's hardware ID is PCI\VEN_10EC&DEV_8125 with generic CC_020000. Note...just checked the Microsoft site for windbg compatibility and the Realtek 8125 is listed as OK. Look under manufacturer 10EC. Re code 10...I can't even load a driver. Note that I am working with only a PS/2 keyboard. I did manage to load drivers from W10 to W7 as an offline image (f:\) using command... Dism /Image:f:\ /Add-Driver /Driver:f:\drivers\ /recurse /forceunsigned I loaded my INF files in f:\drivers and W10 happily installed them. Note that DISM does not work if the f:\ windows directory is used. If the drive is specified alone, it works. I did get an XHCI driver loaded but no hub drivers. Also, on my Windows 10 installation they have an -AsMedia Generic SuperSpeed USB Hub, -5 x Generic USB hubs, -an Intel USB 3.20 eXtensible Host Controller (VEN_8086&DEV_7A60) -a USB 3.0 Hub.

Hi Mov AX, talked to you a couple of times at winraid forum. I want to setup a system to do kernel debugging but I was using serial setup with a USB - serial connector and never got it working. I am interested in your debugging article about networking and I have a better setup now, using a W10 laptop as host. Before, my host was a W7 laptop. I understand that kernel debugging via a network requires W10, so how can we debug a W7 or XP system as a target? Is it based on using a W10 kdnet module on the W7 or XP drive? I now have an Asus B760M, with CSM, and I can get W7 to the desktop with no USB. I cannot load a USB driver for some reason and before I try it with XP, I thought it might be easier to try it with W7 first. I can do just about anything I normally do with W7 using a PS/2 keyboard except having USB functionality. Any hints on where to begin debugging the system if I get a kernel debug session going. I am thinking about setting breakpoints in the device manager process, while activating the driver update process to see why it is not loading USB drivers.

The troubling things for me is that Asus provided two PS/2 ports on on the B360M and only one on the B760M. Since they have marked the single port as both green and purple, one might think it is intended for two devices but the manual suggests it's either/or. Hopefully the manual is wrong. Testing this means either pulling the mobo and tracing the circuit, which I am reluctant to do, or taking a chance plugging in a splitter cable. First. I'd need to test the splitter for continuity to ensure no short-circuit is present between the +5V connector on pin 4 and ground on pin 3 or any other pin. If the splitter is using pins 2 and 6, it should pose no problem as far as damaging the mobo. I am curious as to how the dual port PS/2 is implemented on the B360M mobo. I would not think it relies on logic chips only since there could be a condition where a mouse key and keyboard key are struck simultaneously as in a Shift-Right click. In such a case, the computer logic needs to know what device is operating in order to install drivers for each device and that would be masked by the logic. As you point out, it makes absolutely no sense to supply one port unless you have USB operational, but then, why would you need to use PS/2? Both my mouse and keyboard are USB and I only need PS/2 when USB is not working.

I don't think the problem is with your files. I have W10 running on one disk and W7 on another. I think the problem arose when I was running w10 and Defender was checking the w7 disk. I think I may have other issues. I got W7 running on the Asus B760M by changing the SATA drivers to a w10 variant. The variant is old, dating back to the Intel version 8 chipset level. I need to take a closer look at my chipset drivers, especially the PCI driver. My current setup does not seem to be installing USB drivers at all, marking them as 'UNKNOWN'. That would likely happen if the PCI driver stack was not right. Might be better if I did a fresh install using some of the packages available, like those of George King. If that works, I could compare the running version with my current version.

That's what I am trying to do now. My W7 was installed on an Asus B360M and I think I was running Cannon Lake as a chipset. I had XP running on it fine as well and the only mod I needed was for USB on W7 although extensive mods were required for XP.

Thanks, I'll try to find a splitter. Most splitters I have seen are from PS/2 mouse and keyboard to USB, not from PS/2 to PS/2. These devices are understandably not stocked a lot these days and I may have to make my own. Problem is, as I described earlier, getting the proper pinout. I guess Asus should be able to advise although tech reps from major companies are not always helpful. They tend to farm the work out to other countries where someone reads from a script. The fact that the B760 has a dual-coloured PS-2 port suggests that two devices can be connected via a splitter, but when you read the Asus manual for that mobo it says 'either' a mouse or a keyboard, which makes absolutely no sense to me. Why would anyone want to run a PS/2 keyboard without a mouse? The B360M has two ports.

Thanks for reply. The problem with a splitter is when the PS/2 port is not wired to allow one. The chipset has to identify what device is using the port at any one time. If you have a keyboard plugged in, the system can identify it by interrogating the keyboard internals and supply a proper driver. Same if you have just a mouse plugged in. If you have both plugged in, the system will ID the keyboard when a key is depressed or the mouse when a button is clicked, but what happens when you need to press the shift key and the left mouse button at the same time? The system cannot tell which is which unless there is a delay between each action. I'll have to try it and see if it freezes. The PS/2 connector has 6 pins and two of them are not used normally. That leaves one for ground and one for +5 volts. One other pin carries data while the remaining pin carries a clock signal. Apparently, when PS/2 is wired for both mouse and keyboard, one of the non-used pins is used for that purpose. That should mean a special driver to decipher the difference. I don't know yet.

I found another issue on W10 that explains why the drivers may not have loaded correctly. Apparently, Windows Defender arbitrarily erases dll files it does not like. You have to disable that dumb feature. When I look at the folder in which I stored your files, several of them had a size of 0 bytes, especially the XHCI sys driver. I have tried installing since with the proper drivers and it still fails. However, a file with 0 bytes might explain the BSOD related to the NTFS error. Also the .Net framework 1,1 referenced in the original post for the drivers seems to be dated. That is likely why my system would not load them.

Dietmar, I cannot argue with your point that XP SP3 is better. I had a running W7 OS to work with and it had the USB 3 drivers from @canonkong. Those drivers no longer work on the B760. I managed to load some SATA drivers from an old Russian mod of W10 drivers and got W7 running well enough to reach the desktop. I had forgotten to add the hardware Ids for the SATA controller in the INF files. It actually runs fairly smoothly, although I need to use a PS/2 keyboard with no mouse. I am learning how to use the keyboard with 'mouse keys', a Windows feature that allows you to use the numeric keypads to position the mouse cursor. For whatever reason, the B760 only has one PS/2 port and I am trying to find a way to combine the USB mouse and keyboard into one PS/2 port. Apparently it can be done but it depends on how Asus wired the PS/2 connector. PS/2 and the USB 2 standard are similar. One thing to look for with W8 drivers on W7 or XP is their use of special files that begin with ext-ms-win- or api-ms-win-. They are small files used by the system for some reason. I found them referenced in depends and they are found in W8 in the setup.wim file. Microsoft may have not included them in the W10 setup.wim because they presumed W10 was an update to W8 and W8 already had them. Therefore, if you are using W10 drivers on W7 or XP,, and Depends marks them as missing, you should check out W8 for these files and maybe copy them to the c:\windows\system32 directory.

Great news. I am sure it will run W7 just as well. I had XP running well on the B360M but it only ran in SVGA mode with the Nvidia GT 1030.

Thanks for reply. I am looking at the W10 Device Manager for the same USB that is working on W10, The only drivers listed are usbxhci.sys and UsbXhciCompanion.dll. The hardware Id. is PCI\VEN8086&DEV_7A60&SUBSYS_88821043&REV_11. In the alternate hardware ids, there is reference to CC_0C0330, which I think is the generic Id. In the INF file for W10, all they list is a Generic driver as PCI\CC_0C0330. It seems, then, for W7, that USB XHCI should run with a generic driver. The questions is, which one? I need to spend time checking that out. There may be other issues. The INF references PCI.sys and I have yet to set that stuff up. I realize this is a lot more than simply swapping drivers between W10 and W7. There is work to do.

BTW...I got a BSOD with a Stop 0x24 error, which is related to an NTFS file system error. I found no file-related errors and that error showed up immediately following installation of the USB drivers.

Ed...thank for driver but it did not work. May be related to KB2864202, which I don't have on Win7, but when I d/l the x64 version for W7, I get an error message that the update does not apply to my version. Makes no sense since it is marked as being for W7 - x64. Maybe there are other updates I need or maybe one has superseded it.

Hi...don't know if I should start a new thread. I am on the next chipset generation up from Alder Lake, it's called Raptor Lake. Have a new B760M-A Asus mobo and I have managed to get W7 to the desktop although I can only get in using the Admin logon selection. It seems stable. No USB, I am using a PS/2 keyboard. Any suggestions? BTW...this is not a fresh install, it am modding the INF files as I go along and installing offline via DISM. Please don't suggest a fresh install, I have far too many old apps on the disk to consider that at this time.

Dietmar...good to hear from you again. I appreciate all the work you have done with XP. I have the mobo box in front of me and it says Prime B760M-A D4. Part #90MB1D00-M0AAY0. The 'C' on your part number may be a reference to another definition of CSM offered by Asus. George checked this out and it is confusing. There is no reference to CSM as on the B360M box but in BIOS there is the same CSM option as in the B360M. In BIOS it is referred to as a Compatibility Support Module and you access CSM in the Boot menu, I recall that George checked with Asus and they confirmed it has CSM. In BIOS, It has the following options: Launch CSM...Options: Enabled/Disabled Boot Device Control...Options UEFA and Legacy Oprom, Legacy Oprom Only, UEFI only Boot from Network Device...Options: Ignore, UEFI only, Legacy only. Boot from Storage Devices...Options: Ignore, UEFI only, Legacy only. Boot from PCI-E/PCI Expansion devices....Options: UEFI only, Legacy only. One improvement in BIOS is the ability to use a mouse. Also, to access BIOS you need to hold the F2 or DEL key down through the entire boot period. Once into BIOS there is a large screen with convenient information. To access the actual BIOS you need to click on Advanced Mode or use F7, which toggles you into and out of the Advanced Mode. On the introductory screen there is a handy feature. It appears you can set boot order simply by dragging the desired boot device into various positions. The board has one serial port and you have to be carefully when connecting to it. Asus has their own pin layout and I can supply that for you since it is hard to find. The connector pinout on the mobo is not the same pinout used on a serial cable with the same number of pins. More confusion. I made my own serial cable a while ago and I am going to verify the connections. However, when connected via windbg, I can see a Break if I send one. I need a better serial monitor however and I am looking into that. Also have a newer laptop running W10 so I'll try my USB to serial connector on it. A plus on the board is a PS/2 connector but it incorporates both the mouse and keyboard in one connector. So, you need a splitter to plug a USB mouse and keyboard into it.

@Dietmar @George King ...took a long time to catch up with you guys. I finally got Dietmar's link at MDL long after it was posted and I have been in touch with George at MDL. I told George I have a new mobo, an Asus B760M - A D4 and it has CSM in BIOS. I realize this is an XP forum and I have no intention of disrespecting that by asking W7 questions. However, the methodology is the same and I am planning to get XP running on the new mobo as well. However, I am trying to get W7 running first since it seems an easier prospect than getting XP running at this time. Got W10 running satisfactorily, next is W7, then XP. I noticed in another post that Dietmar is using windbg in a kernel mode setup. I've had a lot of grief using windbg for this even though I'd prefer that method. I have been using a USB to serial adapter and that is part of the problem. I could not get it running well enough from a W7 host to an XP target. MOV@xDEAD was using a LAN setup and covered a USB 3 setup but W7 is finicky with such setups and I am sure XP is even worse. I was trying to get a k-mode connection between W7 and XP. Right now I need to get one between W7 and W7 or W10 and W7, to oserve the boot sequence. Do you guys have any suggestions on that? What setup are you using to get the host talking to the target? I am currently experiencing the same 0x7B BSOD error we experienced with XP and that should mean a SATA driver issue. I suppose if I get past that I will get the old ACPI 0xA5 error.

ps. be aware that anything that is offered free is not done for your benefit. All these apps, and Windows 10, are busy spying on you. I caught Microsoft Edge spying on me while I was doing online banking.

I have used the free Comodo version for years on both XP and 7. I don't believe anything out of the US government related to Kaspersky. Comodo can lock a system down if required. The point is, no antivirus is any good if you are going to go online and surf the Dark Web, or even sites offering freebies. Also, one has to be wary of opening links in emails. I do my surfing on a laptop that is never used to do banking or any other transactions. Keep a good backup image from an app like Macrium (free).