Content Type
Profiles
Forums
Events
Everything posted by Mov AX, 0xDEAD
-
Hi George King Sorry for looong response 1) memcmp for x32 already done by MS in one of .lib, i think in storport.lib, to enable add new section: 2) MmMapIoSpaceEx - OK 3) RtlInitAnsiStringEx - OK if it is w2003/xp copypaste 4) RtlInitUnicodeStringEx - OK if it is w2003/xp copypaste 5) RtlDowncaseUnicodeChar - Wrong, use w2003/xp copypaste, require copy of macros and probably static tables Nls844UnicodeUpcaseTable/Nls844UnicodeLowercaseTable p.s. may be towlower() is alternative, there is argument type mismath 6) PoFx* - as i wrote before, stubs is OK, but not enough, driver still waits for callbacks from kernel
-
@Dietmar One more test please ? in boot.ini create dublicate line with existing config, but add /ONECPU After loading Windows will have only one core in Task Manager, but all cores in Device Manager 1) Repeat deleting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\GenuineIntel_* 2) Reboot 3) Look for changes in Device Manger after first reboot
-
pre-v6 diff patch is what you already have, no any changes. There is no more to test, your KDNET log is fine, patcher do anything right, all device definition patched succesfully, all 64 definitions named correctly "intel bla-bla" at ACPI side. Issue happens later outside of processor definition, i have no idea.
-
This is OK, after reboot or rescan devices, windows request ACPI for device list and get processors: setupapi.log: ACPI\GenuineIntel_-_x86 has priority over acpi\processor, so IntelPPM_Inst section selected Maybe Windows has bug with installing same driver for multi cpu ? You can check yourself: 1) backup current setupapi.log 2) delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\GenuineIntel_-_x86_Family_6_Model_151 3) reboot 4) backup again setupapi.log, 5) compare first and second setupapi.log, look only for new lines, it will be 10 or 12 detections depending on luck
-
@Dietmar 1) Orig definition is PR00, PR01, ... , PR63 Modded is C001, C002, ... , C03F and not in same position as orig Later DSDT has definition of _SB->PEPD->DEVY with link to _SB.PR00, _SB.PR01, ... On modded bios, these links linked to nothing 2) Do you always get right names of all cores with modded bios and prev acpi.sys ? 3) Check PM for free version
-
@reboot12 1) Did you sure about Intel SSD Toolbox, Solid State Doctor, etc ? On pre-Vista OSes these utils must traverse NTFS filesystem, find free clusters and send TRIM to disk for each found cluster number. Check with "trimcheck" for real results. 2) Try TxBENCH, it supposed do right way to calculate TRIM clusters on XP, may be it will works with SCSI too