Jump to content

Dibya

Member
  • Posts

    2,134
  • Joined

  • Last visited

  • Days Won

    7
  • Donations

    0.00 USD 
  • Country

    India

Posts posted by Dibya

  1. Well Win32 my patch never caused any issues with ATI Radeon and Intel HD graphics even for your surprise hibernation works with my patch with so called buggy ATI Radeon .

    How it works then ?

    Let me explain . XP , 2k and 2k3 all handles pae differently .

    XP : keeps double DMA buffer enabled always when 64bit ramdisk is active

    2k : Enables dma buffer  when certain kernel calls are called by your driver (on those days high end components only used those API but that not lies today since nt is a major platform now unlike 9x in those days.

    2k3 sp2 : has special hal mechanism that detects defective driver and enable DMA buffer when the driver support in separate memory space .

     My new patch will port fullmechanism from win 2k3 unlike my old patch which ported some to prevent just few drivers which troubled me and my user . I am using my new patch for 4months . It is so far God like stable .. I will analyse new patch by Daniel since it enables pae without pae switch

  2. 6 minutes ago, daniel_k said:

    @HoppaLong

    Please read the following article, see section Method 3: Reconfigure the boot.ini:
    http://www.vernalex.com/guides/sysprep/hal.shtml

    Doing this way you don't need to replace any files (like the other tool posted by caliber), simply choose a boot entry.
    Unfortunately, don't have much time to thoroughly explain certain things. I'm usually messing with the complicated stuff.

    My patcher shouldn't have issues with USB2 and definitively works with KMDF drivers (from VIA and Fresco Logic).
    Be warned that some badly written drivers may cause issues with PAE enabled.

    PS: Just check that russian patcher, it is just an automated installer for Dibya's patch and has the same issues.

    That Russian fix128 thing breaks usb surf sticks and printer and few other .

    Mine doesn't because it backports DMA buffer logic from windows XP sp1.

    Original inventor of pae64 patch is one of my friend from a gaming forum. I still have source so I can build a automated patcher but since no one is interested before so I never ported it .

    I did experiment but it never released a complete version.

    Problem with fix128 urged me to make my own patch . I don't know if they fixed their old bug's

  3. @rloew hi , do you mind if i upload some of your father code which i own ? Like one from his api wrapper generator .

    Last time i talked with Rudy , We are talking about some of his cool tools like a patch generator . His  knowledge on reverse engineering was awesome . I personally use lot of his tool which are never discussed in public including his amazing disassembler . I guess their are many such never released tools which he never talked in public .

    Quote

    I have a tool that can extract the differences between the original file and the modified file and create a difference file that can be used to patch the original file again.

    I think LoneCrusader will love to short his code . I will love to have his CPP version of his MAKEWRAP tool whose assembly only version is with me ( Assembly only version was requested personally by me , and he made it just for me ) .

    Figuring out coding style of Rudy will be tough since as far as i know he used to use his own debugger so i may guess he might have used his own compiler in some cases . I will love to make and maintain a github repo for his work

    @LoneCrusader

  4. He was a amazing man , Of course a good friend .

    It is honor for me that i once worked with him in some project and learned many thing from him. 

    He was pioneer in patching OSes beyond their limit .  He was always straight forward which is rare in today's engineer .

    I cannot say anything , i am crying . Heck even i am so late , as i was offline for long .

    We will definitely miss him.

    RIP

  5. 14 hours ago, Paulo Eduardo said:

    Hi everyone.

    I am trying to install "Windows XP" 32 bits SP3, on Gigabyte GA-Z170-HD3 motherboard. In another forum, I read to install iaStor_skl.rar in order to make AHCI to recognize the HD.  I have incorporated it with nLite, but I got the message STOP: 0x0000007B (0xF7D2524, 0xC0000043, 0x00000000, 0x00000000). Can anyone suggest an Z170 chipset AHCI driver compatible with Windows XP? I am stuck in this issue...

    Thanks in advance,

    Paulo

    Try this driver in a clean XP source

    https://www.win-raid.com/t22f45-Guide-Integration-of-Intels-AHCI-RAID-drivers-into-a-Windows-XP-W-k-W-k-CD.html

     

  6. On 4/7/2019 at 6:30 AM, TuMaGoNx said:

    Cpython 3.5 and up use VS2015/2017 (which not run on XP,) to build C-ext thus porting just cpython is half of story. Different approach would be Pypy (pure python), last time I check (py 3.5) still use VS2008 (not that it matter much anyway) and run fine on XP.

    Then there is msys2's python3 (mingw64) if you want to go separate way from the official.

    MinGw has severe performance issues .

     

  7. 6 hours ago, roytam1 said:

    you have to recompile 3rd party libraries provided by Nevcairiel with v141_xp since he provides .lib libraries that is not compiled with v141_xp. And those libraries may need to hack around to make new windows API out of them, as well as ffmpeg.

    I already patched ffmpeg codes for removing condition variable , srw and bcrypt.

    I want to run the .sh script to compile ffmpeg because you can't compile lav without compiling ffmpeg and libbluray.

    If visual studio solution for libbluray exists so it's not a issue but ffmpeg is different.

     

  8. On 4/16/2019 at 5:45 AM, blackwingcat said:

    > Can I rely on DLLs dates (are changed DLLs newer than ones from previous release)? And what about detections by antivirus software?

    Yes you can. Perhaps no problem now.

    >   P.S. Why is your blog unavailable when connecting through Russian ISP?

    Really ? But I don't know that reason.

    It may be related that my blog provider  has been acquired by a Korean company.

    How about using proxy ?

     

    Wait livedoor is japanese company?

  9. 4 hours ago, siria said:

    (offtopic)

     


    I can't bear spying, but there seems no escape anymore, be it by Google/Facebook/Microsoft etc. or China - all the same, all stealing whatever they manage to grab. It's ironic, but I'm actually considering to buy a Xiaomi phone now: simply because their current Android One phones (Mi A1, A2...) seem the ONLY ones which even people like me have a chance to unlock without a giant struggle! Necessary for installing a custom ROM, which then hopefully has a lot less spying build in. All others make unlocking next to impossible (for me), or there are no custom ROMs, or phone features are missing, or crappy quality or wrong size or simply too expensive. This easy unlocking permission is extremely rare so am afraid only available for a short period.

    Mi A3 will come so I guess you shall wait .

    You may consider looking at Xperia xa2 plus or getting a OnePlus 3t for dirt cheap price in sealed condition.

    I used mi a1 , xiomi phones are good at paper but not at reality .  They are extremely unreliable , very high SAR value and stupid battery which blast like bomb (actually what happened with my A1)

    Lineage os is a excellent ROM . I use it daily with no google play services . As for apps I use fdroid app Store.

  10. On 3/26/2019 at 9:53 AM, luweitest said:

    Can't agree with that more. There are many great programs made by my countrymen, but you'd better avoid anything from or related to a Chinese company if you still have choice. "Do evil" is the default setting here.  This is not only a political warning.

    Xiomi is completely do whatever they like showing ads in UI , never fixing bugs and sending sensitive information to Chinese servers.

    People here still buy their phones.

  11. 7 hours ago, Dietmar said:

    @Dibya,

    I change 3 Byte.

    Look at acpi.sys with Hexeditor and replace

    75F87414FF -> 75F8EB14FF
    84C07508FF -> 84C0EB08FF
    59597C21A1 -> 59597C00A1

    thats all. It overcomes some stupid tests from acpi.sys in DSDT table in Bios (for example checksum).

    This was the breakthrough for full ACPI support in XP on all newer motherboards

    Dietmar

    Well , commander , the patches will be deployed against our biggest enemies on the border of XPLand , the blue kid !

    Hope Red boy will not invade us soon

  12. On 4/7/2019 at 3:49 AM, Dietmar said:

    Oha,
    I just noticed, that the timer in the original XP Bios from EVGA for the z390 dark motherboard not works.
    And also compi stays always in C0 state, brrr.
    And the most crazy thing: This happens also in Win10, power consumption on 9900k always about 27 Watt..

    Now I chance all against my modified

    acpi.sys
    hal.dll
    intelppm.sys

    and all is nice:
    Full ACPI support with Hyperthreading, Timer works, powerconsumption on 9900k about 2 Watt:)).

    This simple means,
    we, Mov AX, 0xDEAD and me Dietmar
    are better :))
    Dietmar

    Can I know more about your system file modification for ACPI?

×
×
  • Create New...