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. 


Popular Content

Showing content with the highest reputation on 09/30/2019 in all areas

  1. 3 points
    The x64 beta seems to completely support XP x64, so there may be a slight possibility of a x86 build coming.
  2. 2 points
    Definitely not sure, but the new 1.7.20570 Beta is only 64 bit: http://t1.daumcdn.net/potplayer/beta/PotPlayerSetup64.exe It is possible that the stable version will be 32 bit, but without any tests.
  3. 2 points
    ... What makes you say that, actually? Is there an official announcement to support the claim x86 release builds are to be discontinued? FTR, 1.7.20538 is the latest STABLE release, has been out since Sept 19th, 2019; if you head to vendor's (official) download page, https://potplayer.daum.net/ both links (32-bit DOWNLOAD + 64-bit DOWNLOAD) yield version 1.7.20538 installers... This change has been documented in the latest Release Notes: As you, I don't see the reasoning behind this change ; only fairly recent CPU+GPU combinations support hardware decoding of h265/HEVC (and only on Vista SP2 +) . This, in essence, means downgrading PotPlayer ; another way to tackle this is to install (if not already) the Open Codec bundle and then, via the player's GUI, change h265/HEVC decoder to the one from ffmpeg.dll: Regards
  4. 1 point
    I'm on 1909 Build 18363.387 now and latest AeroGlass works after reload the symbols!
  5. 1 point
    They have indeed revised their main page recently; but Sandboxie 5.22 (signed Oct. 30, 2017) was the last version to support XP and is also the version I am using on Vista. It is also the only older version that is available for download at sandboxie.com. Your post inspired me to attempt to register 5.22, but https://www.sandboxie.com/index.php?RegisterSandboxie now redirects to the main page, where clicking Buy merely invites one to download the latest version that does not support XP.
  6. 1 point
    I took a look with debugger on it. It does not look that wimgapi does anything wrong. It extracts WimBootCompress.ini and reads the PrePopulateList entries. After applying it opens all matching files and calls NtFsControlFile with FSCTL_DELETE_EXTERNAL_BACKING code. (That exactly the same I did in Beta 7) Now the problem is that the function succeeds but the files remain WIM backed. Some fail with error code 0xc000046d - that are your 3 "empty" files. However 0xc000046d means STATUS_OBJECT_NOT_EXTERNALLY_BACKED what makes no sense as the files is a pointer file. Seems this bug is only related to identical files inside WIM, that is not bound by hard links in the image.
  7. 1 point
    I'm surprised that no XP enthusiasts in this thread are sandboxing their browser for added security. I have passed the 30-day point where nagging begins, but will continue to use the free version.
  8. 1 point
    Tools\WimBootCompress.ini is actually supposed to help Windows version that does not natively support wimboot/compactOS. So it should only apply to Windows 7/8.x. But it wasn't for some (wimgapi only) cases until beta 8. You can still use it with command line option "/wbc:{WimBootCompress.ini}". It will not replace the internal, but append it.
  9. 1 point
    Oops! The new SSU only has an sha256 digital signature, and April's SSU is a prerequisite for such updates, hence KB4493730 apparently must be installed before KB4517134 in any case!?
  10. 1 point
    That was the correct driver pack! We reinstalled Windows NT (after several false starts and much web research), were able to install the tape drive and restore the system. However, something still don't work. Hopefully, once I install the networking card and setup networking, everything will work. Thanks for your help.
  11. 1 point
    I released Extended Kernel v3.0d * Installer is improved. * TLS1.1/1.2 support *Download Folder Support. ・GDIPLUS・MSXML6・JSCRIPT9 update ・add functions in KERNEL.DLL GetLocaleScripts GetStringScripts VerifyScripts ・add functions in ADVAPI32.DLL EventProviderEnabled EventSetInformation EventWriteEndScenario EventWriteStartScenario EventActivityIdControl EventWriteString EventWriteTransfer EnableTraceEx ・wevtapi.dll bug fix ・WindowsCodecs.dll/wmphoto.dll (WIC) upgrade to Windows 7 compatible
  12. 1 point
    I have found another way to solve the problem. First install Debugging Tools for Windows 10, and then save the code below as symbols.cmd 32 bit: MKDIR %userprofile%\appdata\local\temp\dlls CD C:\Windows\System32 XCOPY "dwmcore.dll" %userprofile%\appdata\local\temp\dlls CD C:\Program Files\Windows Kits\10\Debuggers\x86 SYMCHK /r %userprofile%\appdata\local\temp\dlls /s SRV*C:\AeroGlass\symbols\*http://msdl.microsoft.com/download/symbols RD /S /Q "%userprofile%\appdata\local\temp\dlls" 64 bit: MKDIR %userprofile%\appdata\local\temp\dlls CD C:\Windows\System32 XCOPY "dwmcore.dll" %userprofile%\appdata\local\temp\dlls CD C:\Program Files (x86)\Windows Kits\10\Debuggers\x64 SYMCHK /r %userprofile%\appdata\local\temp\dlls /s SRV*C:\AeroGlass\symbols\*http://msdl.microsoft.com/download/symbols RD /S /Q "%userprofile%\appdata\local\temp\dlls" Run symbols.cmd as administrator and the dwmcore.pdb folder will appear in C:\AeroGlass\symbols. Click retry button and it should work.
  • Create New...