Jump to content

reboot12

Member
  • Posts

    826
  • Joined

  • Last visited

  • Days Won

    2
  • Donations

    0.00 USD 
  • Country

    Poland

Everything posted by reboot12

  1. I tested two acpi 64-bit acpiSkull2A511.sys and 06 - acpi 5048 - 2022.04.12 - PappyN4 with my WinXP 64-bit SP2 in pure UEFI on Intel Gen 8 CPU. It is the same on both - freeze on boot screen and not work restart. To workaround boot screen freeze I need use bootdebug in BCD (BCC) Can you upload patched version acpi.sys 5048 which there are no these problems?
  2. It was still working at the end of August. Today I checked and there is actually a 403 error.
  3. What's new at acpi.sys? I use acpiSkull2.sys from you but these are some different - it will differ in 3 bytes: 128: 19 A3 129: 4C 4B 48246: EB 75
  4. @LoneCrusader I use acpi 7777 x64 in my project - link in my signature (sysprep_pub.7z\sysprep_pub.iso\WINDOWS\system32\drivers\acpi.sys)
  5. I use nightly build version 2024.08.07 and no any errors.
  6. Does dmdiag.exe -v or diskmap.exe -ddisk_number displays the similar errors?
  7. I do not know how in the v45 version but in DP_Ported_DriversCollection_v44.7z many x64 drivers do not install because .inf files are incorrect - I tested only NVMe: Generic_NVMe_1.3.1014.00, Generic_NVMe_1.5.1200.00, Generic_NVMe_10.4.49.0 - have universal HW ID: PCI\CC_010802 but errors in .inf files Samsung_NVMe_3.3.0.2003, IaNVMe_4.4.0.1003 - no compatible HW ID: PCI\CC_010802 The only one that can be installed and works on real hardware (but not in VMware) is Generic_NVMe_6.1.7601.23403 because it has a universal HW ID in the .inf file: %PCI\CC_010802.DeviceDesc%=Stornvme_Inst, PCI\CC_010802
  8. I test both Release XP & Release XP SSE work OK on SSE only CPU with vcredist x86 14:
  9. @nicolaasjan But binary from dropbox not work.
  10. @Dietmar What devices do you have on Other devices - give hardware id's then I make dummy drivers :-)
  11. @Dixel What DEV ID ? My is 0412 and driver works in WinXP 64-bit:
  12. Yes, of course, my second link in the signature.
  13. @saphta You were looking for something poorly because it was here on the forum: https://msfn.org/board/topic/176355-intel-haswell-hd-4600-xp-drivers-here/?do=findComment&comment=1227311
  14. @Dietmar Can you try to patch x64 the driver for the Intel I219-LM 8086 15BB ?
  15. @Dietmar Excellent Try also my WinXP 64-bit
  16. @Dietmar BIOS AMI ?
  17. @Jakob99 There are drivers ported for the I2C touchpad: Ported drivers for XP x86/x64 They are old in the link. Ask @George King about new ones - I have DP_Ported_DriversCollection_v44.7z from him but not tested I2C:
  18. Try this: https://forums.mydigitallife.net/threads/winxp-64-bit-on-a-modern-pc-iso-boot-wim-install-wim.88435
  19. Yea, I know - also for Intel Gen 8: https://www.betaarchive.com/forum/viewtopic.php?p=477539#p477539 Intel Gen 9:
  20. Yea, what does this have to do with this topic and modified acpi.sys ???
  21. But I test same USB 3 16GB on ThinkPad X61 (original acpi.sys WinXP SP2 64-bit) and clone and copy block speed is same ~11 min Only on Intel Gen 8 Copy Block is faster than Clone
  22. Does this mean that Copy Block speed from USB depends on the modified acpi.sys ???
  23. I do not use such large pendrive as yours - the latest I have is Kingston DataTraveler USB 3.0 16GB I connected it to the USB 3 port and did the test: Clone Disk ~10 min clone_16GB.img Copy Block ~3 min - incredible (no display copy speed) copy_16GB.img Both files exactly same checksum: How is this possible? Clone USB > NVMe but Copy Block from RAM to NVMe ???
  24. OK, I'm back. The time of creating an image on the NVMe disk by cloning or copying the block is identical and the same as on the ThinkPad for SATA HDD disk - 1.5 min ??? This means that the acpi.sys or USB drivers and even the destination disk type (HDD, NVMe) does not matter and it depends only from the controller chip in-build in USB stick. I use WinHex 15.8 @Dietmar Try test with older smaller USB stick like me 1GB
×
×
  • Create New...