Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


PPeti66x

Member
  • Content Count

    11
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About PPeti66x

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

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

  1. @genieautravail Hi! Your problem is that you have notebook and not desktop PC. And in case of USB this is a big difference: notebooks have not enough USB ports to connect physically all USB ports that is supported by the chipset. And due to compatibility with older systems, all USB ports are in 2.0 mode on Dell notebooks, except the compatible OS is detected. This behavior can be forced via BIOS settings, but you can not force USB 3 mode on Dell computers - this is automatic. And device driver for this switcher does not exists for Windows XP/2003. So if you returns from Windows 7 or later, 1st time you will have USB 3.0 on XP (without modded AMD driver no working USB ports at this time), but 2nd and later times you will have only USB 2. So if you need USB 3 on XP, start the Win7/later, then restart to the Windows XP. But be careful, the switching mechanism is not 100% reliable. At this time no solution found for this problem. It seems that Intel Host Controller Switch (iusb3hcs.sys) device driver must be modded for the Windows XP, but a simple INF file modding is not enough, it is binary incompatible with the Windows XP. PS: With ACPI.SYS build 5048 from Longhorn you may have other problems (at least on my M4800 these problems exists): 1. display brightness Fn keys no longer works; 2. monitor switching Fn key no longer works. If your notebook have a discrete graphics card, you will have problems with display switching if you returns from sleep mode or if display was turned off by system/software - with original ACPI.SYS you can reenable the display with the Fn key, which not works with the build 5048 version.
  2. acpi_inf_for_Longhorn5048_x86.zip The long awaited driver. But still not perfect. For desktop users probably solves the USB3-related problems, but notebooks (e.g. DELL M4800) may use a switching mechanism. If compatible OS detected, some or all ports are switched to USB3, else USB2 (and USB3 mode can not be forced in BIOS) - this is not too reliable, sometimes requires more restarts. So in case of my M4800 if I switch back from Win7, 1st time the ports are in USB3 mode (and works correctly), but 2nd time, these ports are switched back to USB2 mode. By this driver the problem with disfunctional ports after 1st restart to WinXP was solved. The other (minor) problem, that ACPI.SYS from Longhorn build 5048 is required to install the USB3 driver. But this ACPI version have some missing features for notebook users accessible via function keys: changing the monitor brightness, switching between built-in and external monitors. And Microsoft ACPI-Compliant Embedded Controller driver (ACPI\PNP0C09) remains incorrectly installed - but it is not more needed/supported by the new ACPI.SYS. I made a modded INF for this ACPI.SYS, but installing on a live system may be problematic - without removing all references to ACPIEC from registry manually prior reinstalling the "Microsoft ACPI-Compliant Embedded Controller" the reinstallation was incorrect.
  3. medowe: This means that non-english versions of ntdll.dll may generate wrong error messages on error because some messages are shifted by 1 in the resource part. Language packs are not affected.
  4. Interesting. This tool not works as intended on my computer, but solved my problem (at least partially). It can not turn off the screen properly - it will switch back after 2-3 seconds. The /enable function have no effect at all (it can not enable the disabled screen). But the /disable or the /switch commands are able to re-enable the disabled screen. So now I can use 2 programs, one for disabling, and this for enabling. Thanks for the tip. The Dell have proper tools for supporting these functions, but it requires Windows 7 and .NET framework 4 (officially) - on XP x64 Edition the screen switching fails similiar as in the Multi-Monitor Tool. And all these tools are slow (reaction times are sometimes near 0, sometimes about 2 sec). I hate the .NET framework.
  5. I tried the acpi.sys from the Longhorn build 5048 and it solved the standby problem on my Dell M4800 notebook (Haswell, QM87). And the sound is also OK (the xp version killed the sound after unsuccessful sleep, so the audio driver required to be resterted manually). It also detects the Intel USB 3 device, but the driver is still non-working (it can be installed now by the modified inf files). Newer acpi.sys builds from Longhorn (5112 and above) are incompatible (0x0000007B error). Now I need to solve the screen problem - after the standby the monitor remains turned off, and I can not turn on again. So I must send to standby and it is mostly recovered 2nd time correctly. It is probably because notebook is switched back to the Intel integrated graphics instead of nVidia, but in XP using multiple garaphics adapters is not supported. Is there a way to reinit the nVidia graphics (without restarting/logging out)?
  6. I can confirm the ntdll.dll bug in hungarian and czech versions. Microsoft added a new message (ID: 0x8020000B) in Feb 2016, but forgot to update the localized resources. All following messages are shifted by 1 except the last one (which is also a new message). So most of the messages are messed up.
  7. My question is: how to filter out updates with SSE/SSE2 requirement. For Windows Installer (executing one MSI file, e.g. office 2002 installer) and gdiplus.dll (executing Foxit Reader) was easy. The problem is, that untested files with SSE/SSE2 requirement may produce problems later, when some application trying to use it on old systems.
  8. Because some people had problems with the new XP updates on non-SSE-2 CPUs, I made a big test and installed WinXP SP3 and all updates (up to October 10, 2018 from catalog update) on my old 200 MHz Pentium-1 computer (P5 architecture with MMX support). .NET Framework 2.0 SP2 was installed, but not updated nor tested. Windows Media Player was not updated to v10 or v11 and Windows Search 4.0 was not installed. The results are: - Everything installed fine - System booted up correctly - Some updates failed to work due to SSE-2 requirement: kb4340937 (august, 2018) - msi.dll (and may be msihnd.dll and msiexec.exe) kb4343674 (august, 2018) - gdiplus.dll only kb4458000 (september, 2018) - gdiplus.dll only kb4462987 (october, 2018) - gdiplus.dll only So the new gdiplus.dll and Windows Installer updates should be skipped on non-SSE-2 CPUs. But not all installed files are executed by the system by default, so SSE(2) requirement of some of the other files is unknown. e.g. msvidc.dll, t2embed.dll, mf3216.dll, msxml3.dll, msxml6.dll, mrx*, MS JET files should be tested. MS JET seems to be compiled with MSVC12 (which is very uncommon for Windows XP files) - and most of (may be all) MSVC12 compiled applications I used required SSE-2. ================= A different thing: I installed the Windows XP SP3 on the Dell M4800 notebook (Haswell, Q87 chipset). Everything works fine (except VGA in CPU - if dedicated VGA is installed, it is always used by XP, but this is by design), but I can not use sleep/stanydby - it is prohibited by "Microsoft ACPI-Compilant System" driver (HWID: ACPI_HAL\PNP0C08). Device state mappings: S0-D0, S1-Unspec., S2-Unspec, S3-D2, S4-D3, S5-D3 (so the supported sleep states: S0, S4, S5). Is possible to solve this problem (e.g. by remapping S3 to D3)?
  9. AMD R9 280x (3GB VRAM) works fine on XP SP3 (but some - mostly unused - features are not supported)
  10. Hi! OS is Windows XP SP2 (english) hdaudres.dll = KB888111 patched at offset 110h; original: 00,00; new: 64,86 npdsplay.dll = KB911564 patched at offset 160h; original: 00,00,00; new: 61,8F,06 Date difference is because at patching nLite sets the current date. I made the date set back, but +1 minute compared to original. Tripredacus: I'm sorry.
  11. nLite always patches some files: syssetup.dll (to disable checking of signed INF files) sfcfiles.dll (to disable checking of (potentially) patched files, eg. syssetup.dll, tcpip.sys, uxtheme.dll,...) hdaudres.dll - why? npdsplay.dll - why? Can anyone tell my, why these files are patched? (I included these 2 files in original and in patched form in one zip file.)
×
×
  • Create New...