Jump to content

R1600

Member
  • Posts

    41
  • Joined

  • Donations

    0.00 USD 
  • Country

    Korea, Republic Of

Posts posted by R1600

  1. 7 hours ago, TheFighterJetDude said:

    @blackwingcat When you start working on the extended kernel v3.2 these are some things that could possibly be added to it (some people on reddit came up with this list):

    GPT disk + UEFI support (ported from XP/32 bit 2003?)

     

    Also, for the Extended Core v1.7:

    Add USB 3.0+USB 3.1+USB 3.2, and NVMe support for Intel/AMD and other manufacturer motherboards

    UEFI support isn't even complete on XP/2003 32bit. Some drivers(USB3.x, eMMC, etc...) from Win7/8 are successfully backported to XP(thanks to NTOSKRNL_EMU project), but it requires a lot of modification to run in Win2K. It won't be easy.

  2. 22 hours ago, MilkChan said:

    You could check out my Source file here for creating UpdatePacks, it might be helpful for you

    It may help you a little.
    I collect every language.
    Some improvements I don't have it in every language.

    https://archive.org/details/windowsnt-UpdatePacks

    Thanks for letting me know. For now, I don't think I'll need it for this project thanks to WU URL DUMP, but it will probably be useful later.

    I think there are some updated versions of the files included in ExKernel. Maybe I can report them to blackwingcat.

     

  3. For a complete and correct localization, you will need to replace the image base address and resources of about 100 files with those of your language version. - https://win2k.org/blog/2019/10/07/1989811/

    That means localization requires collecting files from various updates such as KB891861, XP SP3, SV2003 SP2, non-public updates, etc. I'm tracking down what I actually need.

    My final plan is making auto localization python script which download, extract, modify, and re-compress everything automatically.

     

    A little spoiler -

    image.png.8ff23ec2f6d2d2d64dd14e730bd67bd1.png

  4. On 10/23/2023 at 3:03 AM, K4sum1 said:

    I was able to fix this by disabling the Nvidia GPU, running only on the integrated Intel iGPU. After Windows was installed, it seemed to work with the dGPU enabled, although no drivers made it mostly useless.

    However I have a friend with a Broadwell laptop, E5450, and they get this with the ACPI. No dGPU to disable, going to have them look through the BIOS to see if they can find anything.

    IMG_20231022_185957.jpg?ex=6547d83c&is=6

    You can get full debug log via LAN with this one https://github.com/MovAX0xDEAD/KDNET

    There were several attempts in this thread, try searching for keywords like debug.

  5. 37 minutes ago, tyukok said:

    Here's how I did it a few months ago:

    1. I unpacked the contents of the English version of KEX into a separate folder.

    2. Went through every single .dll and .exe of the package with Resource Hacker, replacing the contents of "Menu", "Dialog", "String Table" and "Message Table" with the contents from already localized system-native versions of these .dlls.

    3. In update.inf I changed the "LangTypeValue=" so that the installer worked.

    And that's it. Didn't even repackage it back or anything, just ran setup.exe and installed it. Editing all the files took me awhile, but it worked in the end.

    Basically I want to do the same thing. However, BWC said that without ImageBase address and other changes, he could not guarantee normal operation and full localization.
    You can find that some files (for example, dnsapi.dll) don't have resource (except for version info), but the Japanese and English versions have different ImageBases.

  6. Hi. I'm trying to localize Extended Kernel in a language other than English and Japanese.
    http://blog.livedoor.jp/blackwingcat/archives/1989811.html - Although @blackwingcat wrote localization guide but honestly, it's definitely better than nothing, but not written in detail. Unless you're familiar with the PE format and the components of Windows, it's probably hard to understand.

    So I'm tracking the sources of language-dependent files to get correct ImageBase address and Resources) and trying to follow the guide properly. (The first version of guide was written in 2014, but no one seems to have followed it properly so far :huh:) My goal is to make a complete easy-to-follow localization guide within this year.

    image.png.7653ed6245e6c72c0287414a7ef5b184.png  (a little spoiler)

    More information coming soon!

  7. 4 minutes ago, roytam1 said:

    lately I got an ITX board with AMD FX-9830P APU, and I tried to attach one of my installation to it for testing. I tried some of ACPI.sys drivers in "WinXP-IE Optional Patch Integrator v2.3.4 Stable.zip" and I can get it work with "acpi 5048 - 2019.11.1 - diderius6" and none of "acpi 6666" driver is working with this board.

    Patch Integrator v2.3.4 is very old version from September 2020. Try the latest one (v3.4.6)

×
×
  • Create New...