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. 


Leaderboard


Popular Content

Showing content with the highest reputation on 10/02/2018 in all areas

  1. 2 points
    I think what you discovered are backups of the files replaced during an IE8 upgrade, which are there to facilitate the downgrade back to IE6 (or 7), if one wishes. Nevertheless, I wonder if the old iexplore.exe can be modified to work more reliably with IE8's rendering engine? I'm also curious now if this would work in Windows Vista or 7 (with IE9 and 11, respectively)? Probably not, but it's worth a try nevertheless! c
  2. 1 point
    Thanks for your help,the software is running well now
  3. 1 point
    As a matter of fact, it's a matter of crap. Windows 10 scenario: 1) It's not working! 2)Turn it off or restart it? 3)When it comes up again, it's working!? I've heard this story so many times on the Insider Forum, I just figured it was programmed that way!? It's a laugh! That's why it's fun. Comedy Central or Saturday Night Live just to put this computer stuff in the proper perspective.
  4. 1 point
    What happens (or should happen) *sometimes* during the setup is that a command (not entirely unlike dd) is used to overwrite the first 440 bytes of the MBR (i.e. first absolute sector or sector LBA0) and possibly the magic bytes 55AA. To be copied these 440 bytes must exist *somewhere* (possibly also with an ending 55AA) most probably embedded in this (or that) file. The file in question (again very likely) is connected with partitioning, and as a first attempt I would look inside FDISK.EXE... ... hey, wait, it is there and it is actually documented by The Starman: https://thestarman.pcministry.com/asm/mbr/FDISK.htm https://thestarman.pcministry.com/asm/mbr/95BMEMBR.htm#CHS the issue is that it is "interspersed" with some unknown bytes and there is a "hole" for the error messages (that can still be found in FDISK, but at another address) and another "hole" for the partition data (just before the ending 55AA), and there are the mistery 00 bytes: https://thestarman.pcministry.com/asm/mbr/mystery.htm In a nutshell, and if you have - besides the time - the guts for it, you could test if: 1) your current MBR code is compatible (or can be made compatible) with the "segmentation" with which the original MBR is stored inside FDISK 2) if yes, if when you change ALL instances of the MBR code inside FDISK (and probably you will also need to modify the "error messages") FDISK (from a boot floppy or however from a pure DOS) does actually manage to write your modified MBR code (or throws a checksum error or whatever 3) if the above works, try if setup actually uses the data strored inside FDISK or gets the bytes from somewhere else, and if this latter is the case, look for the file that contains it (maybe a .dll?), rinse and repeat. jaclaz
  5. 1 point
    @sbkw1983...this has been the single biggest help in keeping AG running smoothly after cummulative updates. Thanks for your efforts, seriously...thank you!
  6. 1 point
    In case it helps, I updated my previous post to include Windows 10 (OS Build 17134.320). And I will do so again going forward, good day :-) ZiyaadMuhammad - You deserve credit for responding first, so thank you kindly :-)
  7. 1 point
    Cert_Updater updated to version 1.5 Corrected several bugs, optimized the program and improved some features. to the updated version
  8. 1 point
    http://www.mediafire.com/file/mlna772wez79xyl/symbols.rar/file
  9. 1 point
    One way: The following is not intended for Insider Preview builds of Windows 10. I'm assuming your AeroGlass install folder is the default location (C:\AeroGlass). Remember to ensure every file you download is unblocked (in File Properties) before attempting to use it. Ideally, re-run the attached .bat (Windows Batch) file (always as Administrator) which you've downloaded based on your CPU architecture (usually x64) after each Windows Update is downloaded, installed, and your PC is rebooted as required. ---------------------------------------------------------------------------------------- 1) Download (+ unblock) and install Windows 10 SDK from the following link: https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk 2) Open PC Settings and download + install the latest official updates for Windows 10. Reboot your computer afterwards if required. 3) Once completed Step 2 and logged in again, download the appropriate .bat (Windows Batch) file (based on your CPU architecture - usually it's x64) and run it as Administrator. 4) Press any key at the end to close the window. You should be done until the next update (you should have the latest symbols in question now), good day. ============================================= Edit: If I have time, I'll try to streamline it further (e.g: task .XML format), but this will have to do for now, sorry. AeroGlass_Symbols_Updater_x32.bat AeroGlass_Symbols_Updater_x64.bat
  10. 1 point
    Hello and welcome to MSFN forums! IMHO, you have a bigger problem in your hands by staying with Fx 28.0 ; it was released back in Mar 2014, still has a lot of unresolved functional bugs, not to mention that, security-wise, it has more holes than a piece of Swiss cheese... If you're clinging on it because it was the last pre-Australis major Fx release, then you can switch to latest, but EOL'd, FxESR 52.9.0 and install Classic Theme Restorer to regain 95% of the pre-Australis GUI+features; or install latest New Moon 28 build (a Pale Moon 28 fork modified so as to run on XP/Vista) that never implemented the Australis design... As for your original query: am afraid the answer is NO Fx 28.0 is simply too old; it does not support any form of EMEs (Encrypted Media Extentions = DRM components) and relevant CDMs (Content Decryption Modules), so installing Adobe Primetime CDM on Fx 28.0 is out of the question... On top of that, Fx 28.0 has no support for Media Source Extensions (MSE), needed for youtube MPEG-DASH streams; visiting https://www.youtube.com/html5 with Fx 28.0 on XP you should have got only HTMLVideoElement and WebM VP8 ticked in blue (i.e. supported); it would appear that youtube have retired the VP8 encodes, thus rendering Fx 28.0 on XP unusable... ; BTW, I'm not just speculating, I have got a portable installation of Fx 28.0 on an external HDD and by toggling media.windows-media-foundation.enabled (from true to false) I simulated an XP environment and conducted tests before posting this... On those of us on Vista and higher, Fx 28.0 by default has H.264 ticked in blue, because Fx 28.0 has support for Media Foundation, hence it has access to patented system decoders (h.264/aac) not present in the XP OS (by a M$ decision)... So I can still use Fx 28.0 on Vista on youtube, they serve me a progressive download (no MSE) of an MP4 encode... You want youtube in XP? 1. Use Google Chrome 49, or Advanced Chrome fork (or possibly other Chromium derivatives still supporting XP, e.g. Maxthon...) 2. Update to FxESR 52.9.0 ; native support for MSE+WebM VP9 (for other sites that require h.264/aac native browser support, follow the guides of this thread). 3. Update to New Moon 28 or Basilisk 52.9.0 by roytam1; both have native support for H.264/MSE+H.264/MSE+WebM VP9; (some) people on XP have encountered a small nuisance on Youtube, affectionately known as the "23min youtube bug"; it's not a deal breaker, TBH... And at least one person here has reported better aac (audio) decoding experience by disabling native support in Basilisk 52.9.0 and installing Adobe Primetime CDM there, as per this thread... Hope I made everything clear for you, I'm confident others can chime in for more detailed help, if you need it that is ...
×
×
  • Create New...