Jump to content

mjd79

Member
  • Posts

    99
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Poland

Posts posted by mjd79

  1. 9 hours ago, Dixel said:

    Did you just run your Opera "out of the box" without modding?

    No, it's Blaukovitch crack, you can easily find it, here the link I will not give. The reason I share this is that he created wrappers for many system libraries and rewrote a few (api-ms), and I am very positively surprised that it works on Vista with the extended kernel.

    8680794400_1707913269.png

  2. While using Chrome 109 on the March 6 extended kernel, I noticed a status_access_violation error on some pages. The solution is to use --no-sandbox mode, or far safer, redirect the original DWrite.dll locally. BTW, with the March 6 version have kernel32 and kernel33.dll. For Chrome 109, it is better to redirect the latter locally, because then the system will be detected as Vista and no unsuccessful upgrade attempts will be made.

  3. On 10/21/2023 at 12:25 PM, Dixel said:

    That's what I thought! Another onboard user. Do we have someone with a dedicated sound card, except me? A normal Pci-e or PCI card.

    I can try with Soundblaster SB0220 :)

    BTW after installing the March 6 version, you can redirect userenv.dll from the March 9 version for Chromium-based applications where the sound does not work, and it will be fixed.

  4. 1 hour ago, Dixel said:

    Good point, but it then will involve adding missing stub DLLs. no? I didn't try myself on Win 8, but I kind of gussed it will not be finished with just replacing virtualalloc.

    In Windows 8.1, the missing imports in DWrite.dll can be replaced with kernel32.dll

    4128594100_1696964253.png

     

  5. Dixel's prediction has not yet come true. Just by replacing one missing function, Chromium 118 will still work on LTSB 2015 LOL

    I won't reveal the details for now, because someone from the Chromium team might read this and make for a spite in the next versions :(

    5732672400_1693498123.png

  6. 1 hour ago, mshultz said:

    Add the rest of your memory after installation is complete.

    I installed W7 x64 on a Kaby Lake and H110 motherboard with 8GB of RAM (in one module) There was no problem at all. So, either you have a defective RAM bone, or there is a problem with its contact in the slot. Alternatively, you have something misaligned in the BIOS or a corrupted ISO.

  7. 23 hours ago, D.Draker said:

    One bad sector - the only straight road for that HDD is your garbage bin. 

     

    Such a drive can be exploited if you are at least a little in the subject, control its condition, copy the data to another medium regularly. On top of that, it can't be a complete s*** like Seagate DM. If the model is highly failing, the number of reallocated sectors is more than single digits in RAW, even knowledgeable people should not take risks. To complete laymen and average users, I actually recommend replacing the drive when the drive begins to physically degrade.

    My record in this regard is using a defective Samsung 160GB for at least 6 years. Of the 145GB of data on it, I managed to recover some 110GB. I completely ignored its condition at the time, and that's how it ended up (hundreds or maybe thousands of bad sectors...).

×
×
  • Create New...