Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


About pappyN4

Profile Information

  • OS
    XP Pro x64

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

pappyN4's Achievements



  1. Had another one while testing, fresh install XP64, 2019 updates, only storahci,stornvme,and usb3 drivers installed. Totally new install, nothing running except for a VMware workstation install.
  2. @Dietmar @Mov AX, 0xDEAD Is kdnet kernel debugging possible for x64? I did a bunch of acpi tests and would like to be able to capture proper BSOD data. Test was 100 restarts in a row. Found BSOD 7E (C0000005,...,...,...) BAD_POOL_HEADER BSOD 19 (20,...,..,...) On B450/Zen2 XP32 v4 50 restarts no problem 2003x86 v4 150 restarts no problem XP64 v4 50 restarts, found 1x 7E and 1x 19 during restart XP32 v7 100 restarts, no problem XP64 v7 100 restarts, 3x(7E) 1x(19) during restart XP64 v7 on a old Athlon64 Venice CPU, 100 restarts no problem.
  3. Simple, for both samsung and "new", if PAE patcher is set with 4GB flag, then it does not work. I use win7 stornvme on ISO as generic boot since it works in all situations. Once booted, XP32 with PAE 4GB visible and working with stornvme. Change driver to samsung or "new", and nvme driver fail code 10. Change ntoskrnl to a bigger PAE patch (I use 64GB as max possible) then it works. So somewhere >4GB it starts working. On XP64 the samsung driver also code 10 when nvidia 368.81 installed, but not when 355.98. The 'new' driver does not have this problem so its better for me. I do not remember XP32 having this problem with 368.81 or 355.98. GT710 for test.
  4. I thought I had posted this earlier but I must have missed it. Patch location for timer fix and frequency divider fix from assembley code on first page. File was modified with WinXPPAE 3.5 patcher first. x86 halmacpi.dll (PAE) 5.1.2600.5687 HAL_acpitimer_fix @1933d 79 -> EB HAL TSC frequency divider fix @c7F 75 2D -> 90 90 @c87 74 12 -> 74 19 @c96 89 01 89 51 04 0F 31 64 03 05 AC 00 00 00 64 13 15 B0 00 00 00 C2 04 00 8B 4C 24 04 0B C9 74 0F C7 01 DE 34 12 -> 0F AC D0 0A C1 EA 0A 89 01 89 51 04 0F 31 64 03 05 AC 00 00 00 64 13 15 B0 00 00 00 0F AC D0 0A C1 EA 0A C2 04 First pic adds changes to an empty .TEXT area in the file after guidance from MovAX on where to put it. It's easier to read, so if someone wants to try to learn a little bit by doing. You can see the original code @C96 and @CA4. It is replaced with an E8 command and a hex number, read from right to left, for location where patched code is. 90 is NOP filler if there is extra space. In the patched location, you can see the original code that was replaced and the new shrd/shr that was added, and a C3 to return back. Second pic is less readable. Instead of jumping to patched locations it just overwrites code at the original location that looks like is orphaned because we changed a JNZ to a NOP The timer fix is for skylake and newer. But the frequency divider fix benefits AMD as well. It brings the freq down to the same value as on XP64.
  5. @AndaluI like your idea since it only needs one extra modified file, but with this patch I still had the deadlock. The one I have on github is based on the same changes that server2003 and win8 storports need for uasp deadlock fix based on example from MovAX
  6. @AndaluI think I asked you before, maybe on old winraid.. Yours is Intel CPU? Is the motherboard Gigabyte or does it use an ITE LCPIO? Every so often I get annoyed using a PS2-USB adapter for my keyboard and do bit of testing. With ASRock and with MSI no PS2 reboot issue. Just with Gigabyte. And only with XP/server2003x86/XP64. On win7 its fine. The ASRock and MSI both use a Nuvoton LCPIO. The Gigabyte an ITE one. I think it was in this thread back in august where loading dsdt table into registry was discussed. So I tried to trick the gigabyte table to use same OSVR as for win7 but no change. I even loaded the entire asrock table into registry just to see. To my surprise the gigabyte board has no issues running with it. Unfortunately, the PS2 reboot issue was still there. Seems weird since I'm assuming it's something with the gigabyte DSDT not working with the ACPI from XP causing the soft-reboot to not finish. https://ufile.io/lm3nsvmp
  7. NewMoon 28 is indeed my primary. Palefill looks like it works thanks
  8. Yes, but the x86 InitializeAcpi1Cstates function looks very similar to one from x64. So if needs to be changed in x64 then I would have assumed that x86 would need same change. I dont have Intel CPU to test :) Just trying to have complete ISO so I could use for Intel if I get one :) I have IDA Free 7.0.191002 x64. It does have that ability. If you use CFF explorer to change to 5.2, then it works on XP64 Too many features that I do not know how to use. I use IDA to see changes with graphics/flowcharts. Then simple hex editor/pechecksum to make final versions.
  9. @Dietmar Question. Copy of intelppm for x86 that I have only makes C2/C3 change in InitializeAcpi2IoSpaceCstates. The x64 version here makes change in both InitializeAcpi2IoSpaceCstates AND InitializeAcpi1Cstates. Should I update my x86 to also change C2/C3 in InitializeAcpi1Cstates? or is it only needed for x64? thanks -pappy
  10. Tested the "new" nvme driver. XP64 win7 - good samsung - needs to use nvidia 355.98 to work. Does not work when 368.81 is insatlled. "new" - good. Tested with 355.98 and 368.81. XP32 win7 - good samsung - needs to use PAE with >4GB. When using nonPAE or PAE4GB does not work. "new" - Need PAE>4GB to work. Did not work with PAE4GB. Did not test nonPAE. server2003x86 "new" - good Both samsung and "new" able to show SMART on MZVLW256HEHP using modded CrystalDiskInfo
  11. @roytam1 Is it possible / any plans on adding JavaScript Optional Chaining (?.) and Nullish Coalescing (??) example of site where it's used is github -pappy
  12. SYSTEM_SERVICE_EXCEPTION 0x0000003b Had this BSOD while trying something. Only software running was a windows PPTP connection, MyPal29 and a filehare app. BSOD happened twice while is was testing, and once right into BSOD before booting finished after rebooting from previous BSOD. I could not get it to crash again. Tried maxing out CPU, iperf3 UDP to max out network, while looping video and running app for a day, still no crash. Bluescreenview Mini011123-01.dmp 1/11/2023 8:54:22 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`80000003 fffff800`01026e20 fffffad9`820c4000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+2eb10 x64 ntoskrnl.exe+2eb10 F:\bluescreenview\Mini011123-01.dmp 16 15 3790 131,072 1/11/2023 8:55:40 PM Mini011123-02.dmp 1/11/2023 9:07:08 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`80000003 fffff800`01026e20 fffffad9`83c72d50 00000000`00000000 wdmaud.sys wdmaud.sys+cccd50 x64 ntoskrnl.exe+2eb10 F:\bluescreenview\Mini011123-02.dmp 16 15 3790 131,072 1/11/2023 9:07:44 PM Mini011123-03.dmp 1/11/2023 9:07:44 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`80000003 fffff800`01026e20 fffffad9`835a4ca0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+2eb10 x64 ntoskrnl.exe+2eb10 F:\bluescreenview\Mini011123-03.dmp 16 15 3790 131,072 1/11/2023 9:08:14 PM Running analyze with WinDbg points to afd!AfdIssueDeviceControl+0x1a8, afd!AfdBind+0x630 as the issue. Googling showed that issue could be network driver itself not afd.sys. Tried runing Driver Verifier Manager to stress test driver and see if i can replicate problem. On XP64 with NVME boot drive, Verifier could not get it to boot into windows. It stays on the windows GUI screen with bar scrolling forever when using win7nvme driver or "blue" nvme driver. With the samsung it gets 7B BSOD (or Code10 when boot is SSD and NVME is second drive). On XP32 with SSD boot drive. Using win7nvme driver tested tcpip.sys, afd.sys, rtenic.sys (Realtek NIC) individually. When Verifier is on, get PAGE_FAULT_NONPAGED_AREA, STOP 0x00000050 (0x80566000, 0x0, 0xB1E18F0D, 0x0), dump_ntoskrn8.sys address 0xB1E18F0D at base b1b17000. Tried older 2014 network driver for fun, same error except 0xB1E1FF0D b1e1e000. Further testing with win7nvme, if NVME is disabled, boots fine with Verifier. If network is disabled, and nvme is enable boots fine with Verifier. This matches result from samsung and blue nvme driver, it boots with Verifier because nvme gets automatically disabled Code10. On server2003x86. Just works?? All three nvme driver had no issue booting with Verifier turned on. I dont know what think. Original problem is 3B BSOD that I could not recreate and no clear idea where it came from. Common thread appears to be having a nvme drive active in computer. I remember when i first tested samsung it had little quirks like having to use a slightly older GPU driver in XP64 or needing the PAE>4GB patch in XP for it to work. I guess maybe I'll switch to blue driver and see if it happens by itself over the months. windbg_3B.txt Mini011123-01.dmp Mini011123-02.dmp Mini011123-03.dmp
  13. Nothing installed, just a couple of image files on DATA for easy restore for testing, otherwise completely empty.
  14. Anyone have occasional issues during TXT mode install of WinXP onto NVME? Until now all my XP tests have been with SSD so did not notice. Problem happens when going from the screen where you pick which partition to install and the Format/Quick/FAT/NTFS screen. If you are lucky and can get to the format screen then windows install fine. But if you are unlucky, after you select a partition it hangs before you get to the format screen. If it worked the first time, you can get it to hang by ESC back to the partition screen and going to the format screen again. If you do that a couple of time you can recreate the situation and get it to hang. Stuck on "Updating XXX MB Disk0 at ID0 on bus0 on stornvme(MBR). Using the TXT installer to create partition can also hang. Same thing happens on Ramsey's ISO also so not a problem with my ISO. Server2003x86 (or XP64) does not have this problem. Based on research: https://en.wikipedia.org/wiki/Windows_NT_booting_process https://www.betaarchive.com/forum/viewtopic.php?p=409982#p409982 https://stackoverflow.com/questions/5770134/windows-xp-text-mode-installer-is-it-really-a-dos-application I tried copying files from 2003 that sounded like it had anything to do with disk checking or formating, also opened setupdd.sys and copied files that were mentioned inside. Did not break TXT installer, but still get hang: NTFS.sys, mountmgr.sys, ntdll.dll, crcdisk.sys, autochk.exe, autofmt.exe, SMSS.exe, NTDETECT.COM, diskpart.exe, format.com, CHKDSK.exe, CHKNTFS.exe, FREEDISK.EXE (does not exist in XP), USETUP.EXE Replacing setupldr.bin setupldr.exe got "error code 14 setupdd.sys cound not be loaded", also replacing setupdd.sys got "error code 7 setupdd.sys cound not be loaded" Playing around I noticed that setupdd.sys call RtlInitAnsiStringEx, RtlInitUnicodeStringEx, which is in 2003 but not in XP, added it to ntoskrn8 and changed setupdd to use. Gets BSOD 71 (00,00,00,00) SESSION5_INITIALIZATION_FAILED. Removed all other files and kept just new setupdd, same. Out of ideas. Maybe something else needs to be copied? https://ufile.io/sy7pyv9m
  15. Possible RAM limit for XP I had some extra RAM from a friends new computer so I had a chance to test. XP32 did not like having 128GB of RAM. As soon as I boot with existing WinXP it restarts into SafeMode/LastKnownGood screen. Tried a fresh install, same issue. This was using the 128GB/ALL PAE patched ntkrnl. On both a MSI and Gigabte B450 mobo. When I changed it to a PAE 64GB limit patch, it works no problem. Why would you need 128GB for XP32 . Tested XP64, ran fine with 128GB, no problems to boot.

  • Create New...