![]() This way, my DOSBox-X (or other applications) and their settings persist between reboots of the Sandbox.Īlternatively, you can use Chocolatey to get DOSBox-X inside the Sandbox (you could put these lines into your startup script): Set-ExecutionPolicy Bypass -Scope Process -Force ::SecurityProtocol = ::SecurityProtocol -bor 3072 iex ((New-Object ).DownloadString('')) I install to C:\Users\WDAGUtilityAccount\Desktop\MySandbox\MyPrograms which is a folder on the host beside my Sandbox setup scripts. I install my DOSBox-X into that read-write area, i.e. wsb that I keep a shared folder as read-write (written as false). You have a couple options for installing DOSBox-X. wsb file to customise the Sandbox (adjust the D:\0\MySandbox address that I use to suit your needs) and a startup script, put anything you want in there. The Sandbox is completely secure, and opens in seconds. Enable Windows Sandbox from an Admin PowerShell console:Įnable-WindowsOptionalFeature –FeatureName "Containers-DisposableClientVM" -All -Online -NoRestart.Opening Task Manager, go to Performance tab, then at lower right, look for "Virtualization: Enabled". Confirm Virtualization UEFI/BIOS for the motherboard.I run DOSBox-X from inside Windows Sandbox and it works very well. Indeed, it has been for some years now, and is called Windows Sandbox. "I wonder why this feature isn't part of Windows itself.". I have a lot of personal and valuable data which I truly don't want leaked or stolen. While true, it doesn't help me feel any safer. I'm afraid that the answer is going to be: "you have to trust people in life or you will be unable to function whatsoever". It should be possible to "isolate" individual programs while still running them on the actual OS and not have to fiddle about with these slow and cumbersome VMs. I wonder why this feature isn't part of Windows itself. How does one reasonably handle things like this? I know of "Sandboxie", but it was never able to instill any confidence with me. Yet all the programs I do run on it are ones which logically have to run there they cannot run in a VM for logical reasons. Every single program I run on my host OS is a total security nightmare waiting to happen. Actually, while I'm specifically asking about DOSBox-X in this case, this question could also be made much more generic. You probably don't realize how big of a deal this is to me. This, while honest, does not make me more likely to trust it on my main OS. ![]() There is no guarantee of complete containment by DOSBox-X of the guest operating system or application. There may be vulnerabilities, bugs, and flaws in the emulation that could permit malicious DOS executables within to cause problems or exploit bugs in the emulator to cause harm. It contains a lot of code designed for performance, not security. ![]() Just trusting DOSBox-X to begin with is a major deal for me, but then you explicitly read this on their own website:ĭOSBox-X cannot claim to be a "secure" application. Then it would (probably) allow me to "Alt-tab" between it running something in fullscreen and my host OS's programs. It would of course be quite technically possible to install DOSBox-X on the host OS instead. Fullscreen and "Alt-tabbing" between it and programs on my hos OS is either highly impractical, or impossible. Then switch to it, run DOSBox-X inside of it, and then finally start using it. If I could afford it and had the physical space, I would set up a real classic PC and not bother with any emulators.Įvery time I want to play around in my "nostalgia box", I have to first fire up the Windows 10 VM. I currently have it installed inside a Windows 10 VM inside of my Windows 10 bare metal PC. ![]() It's basically a somewhat less awful version of the basically-abandoned DOSBox. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |