Jump to content

Andalu

Members
  • Posts

    29
  • Joined

  • Last visited

Posts posted by Andalu

  1. @pappyN4

    Hi pappy,
    although with delay, I have to thank you for the updated files.

    Do you have solved the JMS583 restart issue with your "W7deadlockTest1" driver?

    Even if I'm sure you have already solved, I wanted to confirm that the driver works without issues here. The stor_uas.sys (modified to exclude the last reference to storport.sys) should have SHA-1 1F712DE6864E14F201EF3D59BB5A161E7A735019 now.

    Another way to find a solution for the restart issue could be to try the "coexistence" of different versions of storport.sys as
    @Mov AX, 0xDEAD had reported on the deleted XP thread:

    "To coexist different versions of storport need:
    1) rename storport.sys to stor_xxx.sys or xxx_stor.sys
    2) in stor_xxx.sys change unicode "\Device\RaidPort%d" to unique string, like "\Device\UaspPort%d" or "\Device\NVMePort%d"
    ."

     

    Edit: I just seen you've updated the Emu_Extender readme with the instructions for the Windows 8's UASP driver. Thanks ;)

  2. @pappyN4

    Hi,

    sorry for the delay in my reply.

    I don't have the restart issue you reported for the JMS583 USB to NVMe enclosure in 3 systems tested, but all of them have an USB intel xHCI controller. Unfortunately, I don't have any AMD board to test.

    Here the test systems configuration with stor_uas driver from Win8:

    JMS583.png

    storport.sys v6.1.7601.23403 (SHA1: 52B722E6D53E6E539996F9C0FAD3F43B069C616E)
    usbd8.sys  v6.2.9200.20761 (SHA1: 5B0951A9817203A1B3DD1770062F1A5F1DE8694D)
    storpor8.sys v5.1.2600.8 (SHA1: 0F522653335981E4074127737200D35908634E11)
    stor_uas.sys v6.2.9200.16384 (SHA1: 34EBEDF9AD9F4CDC89B59E580CC3CD4223F6DE78)
    uaspstor.sys v6.2.9200.16384 (SHA1: 7F9C97BE9820DB7B586D3B00F73940A12715C4BA)
    usbd_w8.sys v6.2.9200.16384  (SHA1: 6B26C1252D7CC00E9B6E4C46EE773DB03DEF4B90)
    WppRecorder.sys v6.2.9200.16384 (SHA1: AB0369D23C2A03A7C7D1769713770B3415761637)


    Do you have already tried with the USB3 Etron driver? It also works for the UAS devices and as for the stor_uas driver from Win8 it has better performances than the Via UAS driver.

     

    Edit: I see you're using an updated storport.sys (I think it's already patched) that I was not able to find. Could you please upload it somewhere?

     

     

  3. @George King

    I tried your last acpi.sys from the "i386_free" folder on the following boards:

    - Gigabyte H470 HD3 -> A5 BSOD (0x011, 0x08, 0xB998B000, 0x20160527);

    - Asus Prime Q370M -> A5 BSOD (0x03, 0xA755B9BC, 0xC014008, 0x494E495F);

    - Asrock H310M-HDV -> A5 BSOD (0x03, 0x97EE06D0, 0xC0140008, 0x494E495F);

    - Asrock B250M Pro4 -> A5 BSOD (0x03, 0x8A8A64C4, 0xC0140008, 0x494E495F);

    - Asus Prime B250M -> it works as well as the previous version.

  4. The forum seems to be working again :)

     

    @pappyN4

    I did a test installing the NVMe samsung v3.3.0 driver and nvidia v368.81 drivers on a GT730 and detected no problems on my intel B250 system. Perhaps the problem you encountered could just be due to an incompatibility with amd systems?

     

    P.S.: can anyone suggest how to get the blue background when typing @(member)?

     

  5. @pappyN4

    Thank you for the modified DiskInfo.exe and for explaining how to make it work.

    As for the Samsung NVMe driver, I've installed XP on NVMe drives like WD SN750, Crucial P5, and Sabrent Rocket with no problems. Now I can get smart data for all of them with CrystalDiskInfo.

    I add that if @Dietmar said that this driver doesn't work all the time, I have no reason to have doubts.

  6. 14 hours ago, Dietmar said:

    @Andalu

    It is this storport.sys

    https://ufile.io/4euzojgb

     

    with SHA-1

    3DDD09C2E6909926E8CE0F672CA7F8C020420050
     
    Have a nice day
    Dietmar

    I encountered some problems with that storport.sys getting the same error code 39 for all NVMe drivers I have installed (Samsung, Microsoft and OFA v1.5 and v1.3). I only uploaded the image for the OFA v1.5 driver:

    Error-on-OFA-NVMe-driver-1-5.png

     

    No problem using Kai-Schtrom's sata/ahci driver and another version of storport.sys (in the screenshot is the one by @George King), where you can also get the smart data from the latest version of CrystalDiskInfo for the NVMe drive but only with the Samsung NVMe driver and when DiskInfo32.exe can no longer load the wbemprox.dll otherwise it crashes (that library can also be renamed for testing purposes only):

    OK-on-OFA-NVMe-driver-1-5.png

  7. 1 hour ago, Dietmar said:

    I just build an XP SP3 with the Sata driver from Kai and the storport.sys with SMART support, with all updates for XP and my last acpi.sys from last August.

    For USB I use the from Win8.1 ported driver.

    It boots XP SP3 on all(!) my Intel boards from x58 to z690, always all USB works,

    niccccee😍

    Dietmar

    Hi Dietmar,

    could you kindly point out the SHA-1 of the storport.sys with SMART support you are using? Does it report data smart for the NVMe drives as well?

    Thanks as always for your helpful info and support ;)

  8. @Dietmar

    thanks for your tests on the boards with chipset Z690.

    I have two requests:
    - is there a possibility to install XP on a motherboard that has no PS/2 port? How to get past text mode setup?

    - could you please upload somewhere the PEMaker 0.82 tool, because from the link http://blog.livedoor.jp/blackwingcat/archives/1313117.html I always get the Bad GateWay error?

    Thanks ;)

     

    P.S.: the Update Mini Tool is the one from MDL?

  9.  

    @Dietmar

    I'm sure that with your skill you'll be able to overcome the forcing that Gigabyte has started to introduce in its bios.

    I didn't have a good experience with the Gigabyte B560M-D3H bios. So much so that, exhausted by the headaches it gave me, I decided to return it when suddendly, after a normal restart, it didn't boot up anymore and get stuck on the gigabyte home screen. The boot no longer worked also with Win10. The CMOS clear didn't help.

    I downgraded the bios from version F6 to F5 and booting worked on Win10 but it was not possible to keep the CSM on enabled which was automatically put on disabled at each reboot, so XP still did not work. Updating the bios to the latest version F7 would have meant no longer being able to downgrade, with unpredictable consequences for the XP installation.

    I'm still wondering how it was possible that a working motherboard, regularly turned off in the evening, the next morning gives no sign of life when the power button is pressed. This time the CMOS clear helped (I have never performed so many CMOS clears as with this board).

    I'm going to start staying away from Gigabyte motherboards (and I'm writing from a GA-H470 that works like a charm).

  10. @Dietmar

    I tried the USB3 driver v6.2.9200.22099 (backported from Win8) with usbhub3.sys dated 23 June 2020. UAS devices are installed via the same driver and their proper USB speed is now correctly listed in USB Device Tree Viewer software.

    The performance detected by CrystalDiskMark for USB3.2 Gen.2 and Gen.2x2 mass storage devices is also as expected (and better than what is achieved with the USB3.X xHCI driver v2.2).

    No issues detected so far.

  11. @Dietmar

    Thanks.

    The files are almost the same. Only USBXHCI.inf is different while in your package there are the files "USBXHCI.inOrif" and "USBXHCIUSBboot.iNixxnf" which I don't know what they are :)

    The boot works now by disabling the XHCI Hand-off option in bios. Tomorrow I will try all my USB3 devices.

    Good night ;)

  12. 2 hours ago, Dietmar said:

    EDIT2: ALL USB2, 3, 3.1, 3.2 work with the original win8 USB driver, transported from @Mov AX, 0xDEAD 

    from 5 May 2020, niccce:))).

    This USB driver is without any Extender.

     

    Hi Dietmar,
    which acpi.sys are you using? Here also the USB driver from 5 May 2020 installs correctly but on reboot my B560 system hangs on the XP logo screen with the sliding bar stuck.
    Can you also please confirm that USB driver from 5 May 2020 contains the following files?

    UCX01000.SYS        340064116B210ADF78239F1C171A69A07325C601
    usbd_w8.sys            6B26C1252D7CC00E9B6E4C46EE773DB03DEF4B90
    USBHUB3.SYS         7EA99282C304A13889B092EEB9F295CE1B681094
    USBXHCI.inf             8AA3652EA655E14EDFCC047B4A780CD9A428760C
    USBXHCI.SYS          C6D35C456E5B011603FAE67472BF1A4AACF61B42
    WDF01_W8.SYS     18D4788BBF520E0C2F3EF95CBDD26F03FE519670
    WdfLdr8.sys             921913D31D9199D574D6FB77D077133002A1AFF9
    WppRecorder.sys    AB0369D23C2A03A7C7D1769713770B3415761637

  13. 3 hours ago, infuscomus said:

    @Andalu

    Yeah, ACPI errors are tough to fix, we usually just jump over the error in the driver, have you tried any of the 5048 versions to see if they work any better?

    I'm curious, why that ADSL modem card?

    Old sound/graphics cards I get since they're useful for retro games, but a modem?

    I have tried all available versions of the acpi.sys driver on my board and only the two v6666 mentioned above work. All the others, including the 5048 versions, give the classic A5 BSOD.

    Anyway, considering the many difficulties to install on this mobo an operating system different from the one imposed by the factory (and under very specific conditions), I think it is already a great achievement to be able to have a working XP even if not at 100% of the possibilities we were used to until now. Always a big thank to the wonderful work of genius guys.

    If then also on this crazy board I could have a fully working USB3 function, it would be the best :)

    About the modem, I simply need to set a single location with internet access on demand and not always on.

  14. 11 hours ago, infuscomus said:

    @Andalu

    We can do it via editing the registry of boot.wim image using NTLite

    Inside the boot.wim registry It's in Computer\HKEY_LOCAL_MACHINE\NLTmp~614f60f8~SYSTEM\ControlSet001\Control\CrashControl

    set AutoReboot to 0, save changes to the boot.wim image and then boot from it.

    Thank you, your method works but the error message displayed is the same as before: "Your pc ran into a problem and needs to restart. We're just collecting some error info, and then you can restart (0% complete).

    But now I can see the additional message:

    "If you'd like to know more, you can search online later for this error: ACPI_BIOS_ERROR".

    11 hours ago, infuscomus said:

    @Andalu

    You mentioned you needed this board for the PCI slot, what PCI card are you trying to use?

    It's an old ADSL PCI modem card. I don't want use anything else :)

     

  15. The method to disable automatic restart surely works on the installed operating system. In my case, though, Windows 8.0 won't install.....

    Some updates about my GA-B560M-D3H board:
    after reading a similar case on forum.gigabyte.us I finally managed to get the video outputs to work with the integrated graphics. Unfortunately I have to confirm that it only works with Windows 10 (and I think Win11 as well) if installed in UEFI mode and only on GPT disk. On MBR disk with CSM enabled no video output from the integrated graphics even with Win10.

  16. @infuscomus

    No BSOD with code. The Win 8.0 installation doesn't even begin. The system reboots immediately without even getting to the "purple" installation screen. The above error message appears only for a moment before the automatic reboot. It is the classic error message preceded by the 'nice' symbol :( that is also displayed in Win10 in case of error detection.

    Thanks for the advice but unfortunately no other recent motherboard in mATX format not Gigabyte has the old PCI slot and two PCIEx as the GA-B560M-D3H. For reasons of limited space I can't use a PCIEx x1 to PCI adapter.

  17. @infuscomus

    No way to install Win 8.0 on the GA-B560M-D3H. The system restarts automatically after displaying for a few moments the error message: "Your pc ran into a problem and needs to restart. We're just collecting.....bla bla" (I had to record a video to read it). With the same pendrive Win8 installs without problems on a B250 board.

     

  18. @infuscomus

    Already tried to change the XHCI Hand-off option in BIOS without changes. Another option is Port 60/64 emulation but i don't think it's that.

    I too have never seen such behavior, but I can assure that I have clicked the power button for more than 10 seconds without getting a shutdown. This is already the third time this has happened.

  19. 15 minutes ago, infuscomus said:

    @Andalu

    I also have a problematic USB controller, although for my case it simply does not start and does not bring the whole system to a crash.

    Can you do a test to see if the same behavior occurs in Windows 8.0? (NOT 8.1)

    At least you can use a PCIEx to USB3 card. Here all my USB3 cards have become unusable.

    I will try windows 8.0 as soon as I can.

    In the meantime, also the AMDXHCI XP 276 driver starts to give problems: using the kvm switch the system hangs at reboot on the "windows is shutting down" screen and to perform a reset it is necessary to disconnect the power supply because both the reboot and power buttons on the front panel become ineffective.

    I'm slowly getting more and more convinced to return it.

     

  20. Unfortunately I got an Intel motherboard where the USB3.X xHCI v2.2 driver doesn't work. It is a Gigabyte B560M-D3H.
    When I try to manually install the driver on a working XP system (after installing the Kernel Mode Driver Framework v1.11), it immediately crashes during the driver update and I have to do a manual reboot. The system also freezes on the "Setup is starting windows" screen when installing "XP - Integral Edition" from scratch with the ISO containing that driver.

    Installing XP works without any problems using the AMDxHCI XP 276 driver. But this driver does not have the same features as the USB3.X xHCI v2.2 driver: PCIEx to USB3.x cards (Asmedia and Via chipsets) are no longer recognized and also the UAS protocol is no longer available.

    The Hardware ID for the onboard USB controller is VEN_8086&DEV_43ED&CC_0C0330. The ACPI drivers so far surely working with this board are acpi_6666 of 22Oct2020 (SHA-1 4DFDDBF9D786433CE8868F0CDAC8312B581836DF) and of Dec2020 (SHA-1 1C240A25E8D5C10CAE67C7C03F10715802C5950D).

    Assuming this is a problem with the acpi.sys driver, are there any newer ones I can try to get the USB3.X xHCI v2.2 driver fully working again? If not, this will be the definitive reason for me to return this motherboard because already none of its four video outputs work.

     

×
×
  • Create New...