In order to fix it, I had to run System Restore. The other laptop (#2 for this conversation) has exactly the same problem, except that the bug started occurring after updating some Lenovo Drivers (and MBAM?). Since I had made a bunch of changes since my last macrium Reflect backup (a few days before) I entered Safe mode and system restored to when Dosbox worked (1:28PM). It is the exact same problem as mentioned here Updating to the newest D-Fend Reloaded did no good. Later, (at 9PM)-without knowingly changing anything other than travelling to a different "home" wifi network, updating MBAM to the latest definitions and Steam auto-updating on Windows boot and maybe hitting the "Insert" key which has been remapped to now be "Pause/Break"-when I tell Dosbox to go fullscreen, it starts the process to go fullscreen, crashes to minimized, and eventually exits Dosbox. On #1, at 1:28 PM (local time) Dosbox went fullscreen successfully. I also have McAfee (Preinstalled 30 day trial), Malwarebytes Anti-Malware Free (currently in the 14 day free trial of Premium with on-access scanning, start when Windows boots, etc-unchecking the "protect MBAM from malware" option made no difference-error had already broken it?), and Malwarebytes Anti-Exploit (also in the 14 day free trial of Premium). On mine (#1 for this conversation), one of the things we installed was D-Fend Reloaded (normally for Vista and up-to user profile). They both are Win7Pro 64bit downgraded from Win10 Pro.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |