Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/24/2018 in all areas

  1. MKVToolnix announced that they were going to officially drop XP with version 9.x in 2015. Luckily, the next version v.10.0 was working on XP anyway. Today I decided to update it after a while and I found out that it wasn't working anymore. I took a look at the source code and luckily it didn't use anything weird and it was possible to compile every component targeting XP. As to the UI, this one was tricky. The mkvextractgui hasn't really been modified during the latest commits and relies on old calls, so it was easy to compile. As to to the mkvmergegui (mkvtoolnixgui), in the main branch it has been update to use functions available on Windows 7 only (not even Vista!). I was kinda curious to see what they did and they basically broke Vista and XP compatibility with the GUI to implement some "fancy" W7 loading bars and a few totally useless stuff. Anyway, I re-used the code from version 10.0 for the mkvmergegui ('cause it was XP compatible) and made it work with the new components and... guess what? It works. It's gonna complain about a "mismatch" between the GUI version and the components version as soon as you launch mkvtoolnixgui, but just ignore it and use the program 'cause it's working flawlessly. I just muxed a few .ts and .mp4 files into .mkv and it worked. I even extracted subtitles from a few .mkv files and it worked. Let me know if you find bugs and please note that this is an unofficial version, so DO NOT update via the GUI and DO NOT report bugs on the official MKVToolnix site, but only here. v25.0: REMOVED v26.0: REMOVED V27.0: REMOVED V28.0: REMOVED V29.0: https://mega.nz/#!GJcmUS6R!FvWCCGWxStx5_23MSSJ8l_PC0eJOPaGFaMRtN2XTZFM
    1 point
  2. Could also be KB4134651, which causes problems similar to KB4074852. IIRC both patches replace oleaut32.dll with a crippled version. KB4134651 first came out in May then was updated in July. If you have it try removing it and see if it fixes your problem. If so you can hide it so it doesn't reinstall, or @heinogandacan provide you a customized version of the patch by PM. IIRC it updates the same files as the MS version except oleaut32.dll.
    1 point
  3. Thank you, at least now I know where the problem lies :-) I will try to find the easy solution.
    1 point
  4. +1 (on my various 7 SP1 boot partitons).
    1 point
  5. I'm just staying with .NET v4.5 until I need a application that requires anything higher.
    1 point
  6. Hello all, as announced I have released a new CAupdater - and here is how it works. Download via CAupdater, password is wU8moSRS1S9vfYc Installation is easy, only extract the 7z file (and see under "/docs"). The benefit is the enhanced error handling. CAupdater will install only NEW MS CAstore (sst) files (always together with files not updated but still actual), regardless if incorrect OLDER files offered on MS servers. CAupdater use the update procedure as offered from MS regardless the version previous installed via WU / MU. Only WGET is used additionally to download the MS CAstore (sst) files, there are no other third party tools for the update of the CAstore. CAupdater himself only manage and launch the update. You can find the full AutoHotkey (AHK) code with comments of CAupdater.exe in the subdirectory "docs", see the file CaUpdater.ahk.txt. This are the steps CAupdater make. Every step, even every single MS CAstore (sst) file install, has a error routine and give a feedback about any error. 1. WGET looks for newer MS CAstore (sst) files on MS server and download them local only if they are newer as local stored. 2. Then compare the actual local stored MS CAstore (sst) file dates with the last installation (the file dates of the previous update are stored in the CAupdate INI file). 3. Then ask for confirmation to update the local client CAstore if one ore more local stored MS CAstore (sst) files are new. 4. If "YES" install ALL local stored MS CAstore (sst) files (ALL - this is the same as the MS CAstore update do). If "NO" CAupdater do nothing - and finish. The five commands to install the MS CAstore (sst) files are: updroots.exe authroots.sst updroots.exe -d delroots.sst updroots.exe -l roots.sst updroots.exe updroots.sst updroots.exe -l -u disallowedcert.sst 5. At last show the status (or errors if some), safe new installed MS CAstore (sst) file dates in CAupdater INI file and finish. If errors occure, only the date and status of the update try is stored in the INI file, so you can look for the problem and try again. With this steps only NEW MS CAstore (sst) files will be installed (always together with files not updated but still actual), regardless if incorrect OLDER files offered on MS servers. When you run CAupdater the first time there are no file dates in CAupdater INI file present. So ALL MS CAstore (sst) files marked as NEW in the confirmation dialog. This is also a way to install all MS CAstore (sst) files again - simply delete all the file date entries under section [CAupdaterLog] in CAupdater INI file and start CAupdater again. If you want to run CAupdater without any confirmation dialog you can set the entry "NoConfirmation=1" in CAupdater INI file. Then only Errors will be shown. With set to 2 only a small information dialog is shown on the end and close after five seconds. For special situations you can use two batch files stored in the subdirectory "UpdRoots". This will install the local stored MS CAstore (sst) files the same way as WU / MU do and set also all registry settings needed. The two batch run only this commands: #RootsUpdate.bat Rundll32.exe advpack.dll,LaunchINFSection rootsupd.inf,DefaultInstall #RevokedRootsUpdate.bat Rundll32.exe advpack.dll,LaunchINFSection rvkroots.inf,DefaultInstall The INF files are modified as shown by heinoganda in the first post of this thread
    1 point
  7. Wait. Let me find them out. I will post them in ryanvm
    1 point
  8. For the file itself, you could visit https://support.microsoft.com/en-us/help/975599/stop-error-when-you-put-a-computer-that-is-running-windows-7-or-window then look near the top of the page for the link text "Hotfix Download Available", click that; there will be a page where you can mark the checkbox for the version you want (x86), then give an email address. The site will then email you a download link to click. When you have the download you can use 7-zip or similar to extract the file. As for the custom installer, you would have to ask Dibya, you could try sending him a PM.
    1 point
  9. At the resale shop people donated a lot of those $300 PCs that had a 12 month warranty. They would say at 13 months the unit would not power up. We couldn't make them power up either. So spend another $300 to get another piece of crap that lasts a year. Cheap crap that comes with Windows 10, double crap. However, someone donated a Dell Latitude laptop of the $2,000 vintage. The software, Windows 10 just quit working, so they got rid of the PC. That was a great piece of hardware that I bought for $40. Put an SSD in it and now it is the Windows 7 Pro work station here. Not all Windows products are crap. But I suppose that you can buy a $2,000 PC for $40 in a resale shop there, too. But the iMac is still the work horse computer with both Microsoft and Apple software running on it. And with no design software used at all.
    1 point
  10. New build of basilisk/UXP for XP! Test binary: Win32 https://o.rthost.cf/basilisk/basilisk52-g4.1.win32-git-20180922-3c04affe2-xpmod.7z Win64 https://o.rthost.cf/basilisk/basilisk52-g4.1.win64-git-20180922-3c04affe2-xpmod.7z diff: https://o.rthost.cf/basilisk/UXP-xp-gitdiff-20180606.7z PM28XP build: Win32 https://o.rthost.cf/palemoon/palemoon-28.1.0a1.win32-git-20180922-3c04affe2-xpmod.7z Win64 https://o.rthost.cf/palemoon/palemoon-28.1.0a1.win64-git-20180922-3c04affe2-xpmod.7z Official repo changes since my last build: - Stop using PodZero in several places to initialize values of non-trivial type (847f12e88) - Initialize some asm.js structures using in-class initializers instead of PodZero (8bac8c27f) - Call memset on a void*, not a T*, in js_delete_poison to avoid memset-on-nontrivial warnings with gcc that don't matter for an object whose lifetime is about to end (d902382d8) - Don't memset-zero the BacktrackingAllocator::vregs array of non-trivial VirtualRegister instances (0712ac7f8) - Stop using the MainThreadTaskQueue from service workers. (ad30b9265) - Stop using the worker MainThreadTaskQueue from dom/fetch. (b2cbc7b65) - Send worker-runnables destined for the main thread actually to the main thread. (0384dc34b) - Merge pull request #767 from trav90/class-memaccess-errors (08dd8ff76) - [PALEMOON] Skip notifications for background tabs when restoring a session (465c0a564) - [BASILISK] Skip notifications for background tabs when restoring a session (c5ea5076e) - Merge pull request #770 from JustOff/PR_bgtab_notify (d118d486a) - New cycle version bump. (5bcd1cc22) - Use SessionStore.promiseInitialized() to avoid race condition in "about:home" (#774) (ab47a3a9a) - Rewrite the Code of Conduct document. (89f2f7627) - Merge branch 'worker-fix' (abb2a2a1d) - Add a null check in nsHttpTransaction::Close. (4b9081197) - Fix timer overflow on converting from sec to msec in idleService (7214d60a1) - Merge pull request #778 from MihailZenkov/master (4f89ce5af) - Give uint8_clamped a defaulted (and also trivial) default constructor, copy constructor, and copy-assignment operator. (33cd07bce) - Don't use PodCopy/PodMove to implement typed-array element-to-element copying (a0737572d) - Rename TypeSet::clone to TypeSet::cloneIntoUninitialized to indicate that it freshly initializes the TemporaryTypeSet* provided to it. (3b362e9de) - [PALEMOON] Restore strings mistakenly removed by [8be0c16be614d54183ee3d4877e2243cb9e468c8] (922c13081) - Merge pull request #781 from JustOff/PR_fileExecutableSecurityWarning (07a50b5c5) - Merge pull request #782 from trav90/class-memaccess-errors (3c04affe2)
    1 point
  11. I'm about to create a workaround, it takes a while. Will notify you about PM. A modded update is now available on request!
    1 point
  12. Attention! KB4134651-v2 has the same problem with the file "oleaut32.dll" as KB4134651!
    1 point
×
×
  • Create New...