supplykillo.blogg.se

1. #Running windows in dosbox how to#
2. #Running windows in dosbox software#
3. #Running windows in dosbox windows 7#

I hope you and your readers find this helpful - it took me a few hours to figure it all out, so if passing it along helps someone, then awesome. Step 4 - If things go very wrong, go back to DOSBox's AppData folder, delete mapper.txt, and rename the copy you made to mapper.txt, and you're back where you started. All WP51 commands should now work as they're supposed to, and CTRL-F12 will get you back into Mapper in case you want to further customize it. Step 3 - Click Save (saves all changes to \mapper.txt. Now you have assigned Mapper to the keyboard command CTRL-F12. Just press F12 on your real keyboard and then click "Mod1" in the vertical triad (Mod1 Mod2 Mod3) at the bottom of the screen. *Just* F12 if you try to press CTRL-F12, it'll expect you're trying to assign a new function to Left-CTRL. The red text tells you that it's waiting on a keyboard combination. Here's how: Click Mapper so that it's green, then click "Add" down below.

#Running windows in dosbox how to#

But the DOSBoxWiki page doesn't explain well how to assign things to CTRL- though.

CTRL-F12 is good, because WP51 doesn't use that. Step 2 - Make a new assignment for Mapper so you can get back in. For instance, click on ShutDown so that it turns green and click Del in the box below. One by one, delete whatever keyboard shortcuts are assigned to them.

On the right, below the representation of the keyboard, are 12 named functions: ShutDown, Cap Mouse, etc. Step 1 - In DOSBox, fire up the Keyboard Mapper by pressing CTRL-F1 (which ought to be Go To Dos in WP51, darn it!). There, make a copy of mapper.txt (in the appropriate AppData folder for DOSBox) and save it under a different name. Step 0 - Open up Windows Explorer (or whatever 7 is calling it) and go to C:\Users\\AppData\Local\DOSBox. Thankfully, there's also a keyboard mapper that allows the WP51 user to reclaim CTRL-F5 and all the rest of the commands we use. As it turns out, this is because DOSBox interprets CTRL-F5 as a command to take a screenshot.ĭOSBoxWiki tells us that there are special keys bound by default to certain DOSBox functions. CTRL-F5 failed to bring up the Save As menu.

#Running windows in dosbox windows 7#

I also was very glad to find DOSBox, because WP51 is my preferred writing environment, and I just got a new laptop with Windows 7 on board.īut I got a terrible surprise the first time I tried to save my document as a text file. But I am sure there will be Windows 7 emulators running somewhere in the cloud or on your watch-sized mobile phone. If this is true, Windows 7 will soon be a very primitive OS. Considering that the development in IT is growing exponentially, it is likely that the next five years or so, will bring comparable innovations to those of the last 20 years. The DOS era ended only about 20 years ago, but this environment seems unbelievably primitive compared to today's information technology. When I installed WordPerfect, I began to remember how system administration was in those days. I must say I was quite fascinated when I played with DOSBox. There are a couple of frontends that simplify the configuration. To configure settings, such as the screen size or the amount of high memory available to programs (how I miss these good old DOS times), you have to edit the nf file. The only justification given for this is ‘DOSBox is modern software’, in spite of DOSBox specifically, and compatibility with emulators more generally, being explicitly mentioned in examples of on-topic questions elsewhere.To run external programs in DOSBox, you have to mount a folder on the host with the command "mount c c:\".

#Running windows in dosbox software#

Which again, suggests that questions about compatibility of emulators with retro software is within scope.ĭespite this, How can I get Windows 95 to run in DOSBox? was closed as off-topic. Which Commodore 64 emulator offers better compatibility for ⟨game⟩? The wiki for the emulation tag lists as an example question: It’s not hard to stretch this to cover Windows 95. The top-voted answer (with 33 upvotes and zero downvotes as of my writing this, meaning everyone who read it apparently agrees) implies that troubleshooting retro software under an emulator is on-topic, mentioning this as an example:įor example, "I can't get SimCity to play sound in DosBox" is on-topic because it has a corresponding non-emulated question: "I can't get SimCity to play sound on my IBM-compatible". The meta question Is emulation on topic? has multiple highly upvoted answers, all of which agree that emulation of retro systems is generally on-topic, to one extent or another.