Jump to content

daniel_k

Member
  • Posts

    144
  • Joined

  • Days Won

    2
  • Donations

    0.00 USD 
  • Country

    Brazil

Everything posted by daniel_k

  1. I was scanning the whole hotfix database, but, sadly, when the work finished, the download server have been already shutdown. There was a single hotfix for XP Embedded which no one has noticed: KB2963522 - The system or application freezes in a Windows Embedded POSReady 2009-based device It updated the Netman.dll file and was available in 24 localized languages. It would be outstanding if someone who knows a Microsoft staff could him/her to save the whole Hotfix archive and make it available for us. It was public after all.
  2. In Control Panel -> Power options -> System standby/hibernate -> Never Device specific power management (processor, disk, monitor etc) has nothing to do with system "wide" standby or hibernation.
  3. Windows XP is not as "smart" as Vista and later OSes to tell when a device is not truly present. Just disable Port 60/64 emulation in BIOS -> USB devices. About your issue, I'm sorry but can't help you. While I understand you don't want a clean install. I don't have the time to learn how to properly change from APM/APIC mode to ACPI mode without a clean install of Windows. I'm compiling my own updated ISOs of Windows XP x86/x64 and Server 2003 x86/x64. I test them in VirtualBox and the final test is done on my computer, with the following specs: - i7-8700K - Gigabyte Z370 Aorus Gaming 3 - eVGA GTX 980 - ASUS Xonar DX - Creative X-Fi Titanium - VIA USB 3.0 card - ASIX (Moschip) MCS9990 USB 2.0 card - Samsung SSD 970 EVO 250GB -> Windows 7 x64 - Samsung SSD 840 250GB -> Windows XP x86 - Samsung SSD 840 250GB -> Windows XP x64 - Kingston SSDNow V300 240GB -> Windows 10 x64 - 2x Seagate Barracuda 3TB - Data drives - ASUS DRW-24D3ST DVD-RW The Samsung SSD 840 with XP x86 was running Server 2003 x86 in PAE mode just fine. I've formated it and clean installed XP with all updates including all the POSReady ones up to this month's just to make sure no updates were causing the issues you are experiencing. All the BIOS code (including the ACPI table) for a certain chipset series is about 99% the same for all motherboard models of a manufacturer (Gigabyte in this case). So something that works on my system will certainly work on yours.
  4. Unfortunately it doesn't work, hangs while restoring the Windows session. Otherwise everything else works, including processor power management, so consumes about the same as Windows 7 while idling.
  5. @ruthan http://www.mediafire.com/file/bxtwrw2qv82uttd Just flash the BIOS as usual (create a bootable DOS disk). There are 2 versions: - Firstly, try the one in the root folder, includes an additional modification to the previous version you flashed. - If there are any issues, try the BIOS in the "alternative" folder. Some notes: - The ACPI table modifications work with Windows XP x86/x64 and Windows Server 2003 x86/x64. - For Windows XP x86, I didn't try any PAE hacks. - Standby doesn't work at all. Further modifications are required (not worth the effort).
  6. @cc333 http://www.mediafire.com/file/5cuairv2xv8p0sb Just flash the BIOS as usual (create a bootable DOS disk). There are 2 versions: - Firstly, try the one in the root folder. - If there are any issues, try the BIOS in the "alternative" folder. Some notes: - The ACPI table modifications work with Windows XP x86/x64 and Windows Server 2003 x86/x64. - For Windows XP x86, I didn't try any PAE hacks. - Standby doesn't work at all. Further modifications are required (not worth the effort).
  7. Yep. If you are really willing to try it, let me know and I will patch the BIOS for you.
  8. Didn't see anything wrong with its ACPI table. Should support Windows XP right away, but I can't say anything about older OSes.
  9. Hi, here is the ACPI fixed BIOS. Only the ACPI table was modified. http://www.mediafire.com/file/g16d12a8wpw2yk9 Just flash in DOS using the modified Efiflash.exe included.
  10. Haswell and later architectures are just "too new" for anything but WinXP+. If you manage to find an AX88178 based USB 2.0 to Gigabit adapter, it does have Win9x drivers: https://www.asix.com.tw/products.php?op=pItemdetail&PItemID=84;71;100&PLine=71
  11. Try to: - force all option ROMs to Legacy in the BIOS tab of BIOS Setup. - force "Max Link Speed" to Gen1 or Gen2 in the M.I.T. tab -> Miscellaneous Settings of BIOS Setup. What about a LAN card with Realtek chipset? Not sure about an existing MacOS driver, but there are certainly XP drivers for almost if not all models, even Win9x drivers for some earlier Gigabit ones.
  12. Thanks, glad to be here! While this might work, device re-enumeration may cause many devices to be named #2, #3 and so on, which I personally dislike.
  13. I understand your situation. Problem is, I'm pretty sure you can't change the HAL from Standard PC to ACPI PC without reinstalling. Don't you have a spare hard disk just to try a fully working ACPI install of XP?
  14. The current PC architectures are optimized for and rely heavily on ACPI features. Having ACPI enabled is mandatory for all devices to work properly in Windows XP and Server 2003 as many devices share IRQs. I have managed to get ACPI fully working (except system wake-up) on my Gigabyte Z370 AORUS Gaming 3 by patching the ACPI table. I can patch your BIOS provided that you have a Gigabyte board, just let me know the exact model. Unfortunately there are absolutely no BIOS settings related to legacy ACPI compliance. Doesn't work, already tried this.
×
×
  • Create New...