Jump to content

pappyN4

Member
  • Posts

    30
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

Everything posted by pappyN4

  1. @LoneCrusaderI dont know what you need it for... But looks like all the patch does is skip the checks in pSetupVerifyFile found in setupapi.dll. Fortunately XP64 has the same logic as XP for that part so same patch should also work. x86 setupapi.dll 5.1.2600.5603 @53789 8B FF 55 8B EC -> 33 C0 C2 30 00 x64 setupapi.dll 5.2.3790.4511 @94240 48 81 EC 98 00 -> 33 C0 C2 30 00
  2. 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.
  3. @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.
  4. 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.
  5. 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.
  6. @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
  7. @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
  8. NewMoon 28 is indeed my primary. Palefill looks like it works thanks
  9. 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.
  10. @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
  11. 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
  12. @roytam1 Is it possible / any plans on adding JavaScript Optional Chaining (?.) and Nullish Coalescing (??) example of site where it's used is github -pappy
  13. 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
  14. Nothing installed, just a couple of image files on DATA for easy restore for testing, otherwise completely empty.
  15. 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
  16. 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.
  17. @DietmarAssuming a 16 thread CPU or more. As soon as you run it, WinXP should become laggy. Example, browsing through MyExplorer, or even just dragging a windows across the screen. Assuming you have a "feel" for how responsive your computer is. Normally I let it run for a few hours before I get the "stall" symptom, but no need for you. If you have the lag, then eventually its will stall. Same test but with disabled cores (real or SMT does not matter), max 8 or even limit to 4, there should be no lag. Not a RAM/CPU/heat/power supply issue because with Win7 it runs no problem, max cores. @DamnationI thought of that. According to the WinTimer test I did it is not needed for AMD. Tried here anyways just to see. -fTPM off -different ACPIs -with nvidia GPU driver or with default windows driver -AVX patched or unpatched krnl -RTC timer patch - CoolNQuiet / minimal power managment off / on -Precision Boost Overdrie OFF /on -on msi and gigabyte mobo, different power supplies -memtest was run when I first built it, RAM is fine -tried a XPpatched python 3.7 -runs fine with Win7 so not system issue with RAM or CPU or heat Best part. I tried it on a XP32 host with a XP32 virtual machine. As soon as the VM run the software the XP in the VM had the same laggy symptoms. Only difference is that it ran longer before the other issues happens. Funny thing, is that the XP host had absolutely no lag and ran fine under full load. Problem was contained to the virtual machine. Seems to me that for whatever reason, either python or the 4nec EXE does not like a high core count under NT5.1 or 5.2. No issues with NT6.
  18. @DamnationI have CoreTemp running. Same temp with win7 as with xp/xp64. Maxes at 69* under full load, which is higher than what i get with prime95 stress test. I limit my PPT to 50W cause I like it quiet :) Idle works fine under all three for me with the XP amd processor drivers. Original mobo is Gigabyte B450 Aorus M. I bought a MSI B450M ProVHD-max on sale over the weekend just to test. Same problem. A lot less features compared to the gigabyte so dont want to use it permanently, but the one thing i did notice is that the ps2/noreboot issue I have with the gigabyte works fine with the msi. So that's something on my todo list, did not see anything different PS2 DSDT wise when comparing both. If i have time today i think I'll run it under a win7 VM with XP host and see what happens. Dont really have any more ideas. Other than maybe trying a Ryzen 5700x which has 1x8 CCX, compared to my 3700X which is 2x4. Maybe XP/64 doesnt like having a split core? Only thing that made a difference was playing with core count... Maybe @Dietmar is willing to do a quick test with an Intel system if he has time? On XP the lag should be instantly noticeable. 1. Install python to C:\Program Files\Python 3.4, check the add to path when installing. https://www.python.org/downloads/release/python-343/ 2. extract folder nec to Python34\Lib\site-packages https://ufile.io/za58phav 3. copy test NEC file to a folder somewhere and open/run with opt.bat found in nec folder. I always set the python.exe to lowest priority to run in the background.
  19. CPU/thread scheduling with XP Writing this here to avoid cluttering the ACPI thread since this is not (as far as I can see) an issue with acpi.sys Been using XPpos2019 for some light usage, old XP era games, no issues. But I recently tried to run a modeling application that seems cause an issue with CPU/thread scheduling with XP. Program runs fine on old computer with XP,XP64. Runs fine on ryzen with Win7x64, but it causes instant issue with XP and eventual with XP64 on ryzen. XP should be able to handle 32 threads from what I read, but the only thing that seems to have an affect is limiting it, even with that there are still issues. This is the "small" amount of steps to show issue. There was a lot of other thing I tried while troubleshooting that I will skip: old computer, A-7600, 4core,4 thread -XP64original, used it many times. Application runs for days, no problem. -XPpos2019,v4,AVX,PAE,NTOSKRN8,etc... Installed "modern" XP on old computer, ran for 12 hours overnight, no issues found. new computer, Ryzen 3700X, 8core,16thread -Win7x64, application runs fine, 3 days runtime test. Proves application can use extra cores/resources and is stable. -XPpos2019 "modern". As soon as application is started, windows instantly has "hard lag". Everything from browsing files in explorer, to dragging a windows is very slow. Application runs for a few hours then "stalls", thread no longer launches its child process and it is impossible to kill the parent thread from the processors tab. You can press the restart button in windows, but it does not actually restart. Windows does register the click, because for example if you kill explorer.exe and try to start it again, you get "failed to initialize because window station is shutting down" -XP64pos2019 "modern". No lag when you start. But after a day of running you get "medium lag". You can stop the application as normal, but even if you do, the lag still remains. Restart works, but is slower, takes a minute or two. If you start software, like VLC or MyPal, then it shows up in the processes tab, but does not load on desktop. I assume it would eventually but windows is lagging. -Server2003x86 base ISO but "modernized", quick test with this, no lag when you start it, same as XP64, but didnt run for long. Difference seems to be NT5.1 bad, NT5.2 not as bad but still not ok, NT 6.1 ok. Only BIOS change that had effect. "SMT Disabled" -XPpos2019modern, no lag when application started, but after a few hours get "stalls" problem -XP64pos2019modern, ran for 36 hours did not see problem, but ps2/usb adapter got disconnected in device manager, had to unplug/replug to get working. Related? Dont know... I would want to run for 3 days at least before saying it works correct. -XPpos2019modern, second test, this time got BSOD 50 (FFFFFFFB, 00, , 00) after a couple of hours. Searching online, found some tools related to cpu scheduling, ryzen, and windows 10... ProcessLasso and ProjectMercury. On XPpos2019modern, with ProjectMercury, -NoCCX setting, (4 real cores/4 SMT cores available to be used by OS), no lag at start, but same BSOD 50 after a few hours. -no SMT setting (8 real cores available to be used by OS), should be same as Disabled SMT in BIOS: no lag at start, got a weird phantom "you plugged device into audio jack" popup, after 7 hours got "stall" problem -NoCCX, noSMT (4 real cores only available), set this up just now to run overnight and got "stall" after 15 mins... Time for sleep
  20. @Mov AX, 0xDEADIs there a safe space to add assembly code in existing dll file? I tried patching two new subroutines to an empty 0000000 block at the end of the file, but it does not like it. Windows restarts a few seconds after loading with this patch.
  21. I do not remember having those on mine. Only 7E c0000005 and 05 0000011 with unmodified acpi. XP 7777v4 looks good, updated to newest firmware, tested on Gigabyte, B450, with AGESA 1.2.0.6 B
  22. @DietmarIt's fine. Official CAT specification is usually for 100m length, and is expected to be used in server rooms, so interference "noise" from other network cables, etc... Unofficial, I have 15m of cat3 in wall, running 1Gigabit no problem. You can use iperf3 to test network connection speed between computer to computer.
  23. @George King has the individually patched tests, maybe he can narrow down which one specifically worked? This one has the original patch from Dietmar and the four experiment tests that we tried and seemed to work. @Damnationhttps://ufile.io/xyabacfm
  24. There is no patched version of the default XP64 NT5.2x64 acpi that I can test with. At least I haven't seen one. I've only seen longhorn 5048 until now. That's why I mentioned my XP results from the patched NT5.1x86 and longhorn acpis. I also have a server 2003 NT5.2x86 install I can test with. I used the older xp 7777v2 to get it to boot for the first time a little while ago to compare a nvme driver that didnt work in 5.1x86 but works in 5.2x86. I'm assuming a 5.2x86 acpi compile would have the same issue, but I can give it a try to see. I haven't played with setting up the compiler... Is a 5.1x64 compile possible?
  25. @Damnation Looks like I spoke too soon. More testing, this acpi adds a restart bug. After windows turns off in the restart cycle, it never comes back. Have to physically push the restart button. I had this problem before when a PS2 keyboard was attached and no acpi would fix it. But in this case the PS2 is not being used. USB only. All other acpis that boot do not have restart issue when PS2 is not used: x64 5048, x86 5048, 6666, and 7777 v3.
×
×
  • Create New...