Install Windows 1 01 Dosbox Tutorial
Having the original six discs, does make it easier.- those img will have to be extracted, to obtain their original files.here, copied all files, from all six disks, to one folder & run the setup.exe from there.- used to do that, when dualbooting with w98and wanted both O/Ss, on the one hdd.win3x didn't work too well in a modern Vbox though,- it had both dos 5x & win3x in it.- did get a copy win98 to run in a Vbox, though.has low graphics, as have no driver, to correct that.' AFAIK, dosbox is for playing dos games, not for running operating systems.' Coz it a crazy thing to do. You can most certainly run Windows 3.1. I run Windows 3.0 under Mint KDE.
See it my online Linux demo (link in my signature. It's at around 9 mins in.)The image files will have to be uncompressed first and then used as install disks. There are various utilities online. The trouble is that there is no standard for.img files!
So you will have to go hunting for the appropriate utility. It might be simpler to just get this extracted in Windows rather than Linux given this will be a one shot deal and this is a Windows img file.Here is a possible solution but no guarentees:Winimge has been the standard for img files in Windows so there is a high liklihood this will work. It's shareware so install on a Windows box, extract and uninstall.In regards to setting up and starting Windows - please be aware that DOSBox is 100% 16 bit. It does not allow for 32 bit operation at any level!
This means, while you can run Windows 3.x in DOSBox you can only do so in 'standard mode.' This means you can only start Windows 3.1 with the instruction:win -sI have a shell script that sets DOSBox to an SVGA 386 with 3MB of RAM. (Note: With Windows 3.1 in standard mode that maximum amount of RAM that can be used is 16MB.) I then use the delightful KDE keyboard shortcuts to start with 'Windows+3' on the keyboard! Instant access to Windows 3.0 and Word for Windows 1. I built up quite a stack of Windows 3.0 software.
I have excel 2 and 3, Access 1, Wordstar for Windows, loadsa utilities. I made Window 3.0 sing!However, I now just run up Windows 3.0 to shock students who have only seen XP onwards.
Linux KDE is so much fun. I haven't enjoyed using an OS so much since Windows 95. (Yeah, technically it stank but I enjoyed using it at the time.) - plus the video editing I get with Kdenlive.Here is my script (very simple!).
Code: # This is the configurationfile for DOSBox 0.73.# Lines starting with a # are commentlines.# They are used to (briefly) document the effect of each option.sdl# fullscreen: Start dosbox directly in fullscreen.# fulldouble: Use double buffering in fullscreen.# fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).# windowresolution: Scale the window to this size IF the output device supports hardware scaling.# output: What video system to use for output.# Possible values: surface, overlay, opengl, openglnb.# autolock: Mouse will automatically lock, if you click on the screen.# sensitivity: Mouse sensitivity.# waitonerror: Wait before closing the console if dosbox has an error.# priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized. Using 7Zip (installed by default in Debian Sid) has worked nicely for extracting the.img files. Thanks!However, I'm only extracting one at a time, because it appeared that there would have been multiple setup.exe files otherwise. Now I've gotten DosBox to use the first setup.exe, and I have the following message: 'Please insert the disk labeled Microsoft Windows 3.1 Disk #2 into Drive C: Press Enter when ready.'
What do I do now? I can't exactly type 'setup.exe' again.BTW: Why did you like 3.0 better than 3.1?Attachments. Pierre wrote:'What do I do now? I can't exactly type 'setup.exe' again. 'well - you are supposed to remove each floppy, replace it with the next one & press any key.- another way - is to extract & copy the contents of all six diskettes into one folder & run the setup.exe from there.it's also quicker, installation, that way.What he said. Windows does not ask you to keep inserting the floppy disk that way.In regards to Windows 3.0 over 3.1.
Technically Windows 3.0 only had two features over Windows 3.1:1) It was more reliable. That did not make it.reliable - only more reliable than its younger brother but you could run Windows 3.0 for more than 10 minutes before it bombed. Theoretically Windows 3,1 was more reliable but it wasn't.2) Windows 3.0 would run on an 8088/8086. I've done it! It runs without colour mind but if you use the Windows 2 drivers you get 8 colours! I have run up Word for Windows on an 8086 in colour!
Because I could!In all other respects 3.1 was superior to 3.0. Proper multi-media support (though I did a copy of Windows 3.0 multimedia extensions,) true type fonts (I got ATM 2.5 for 3.0,) better file manager, proper start up folder, etc, etc. There were over 1000 improvements in 3.1 over 3.0! You could even change all the screen colours without editing the win.ini file. No, seriously, you had to modify the win.ini file to change the colour of screen buttons and the like in 3.0.But I was using the 386 for fun, not professional work. Windows 3.1 felt more corporate.
In a way, 3.0 was always the prototype for 3.1. The icons were 2D and looked rough. The printing was unchanged from 2 thus slow, and the whole thing felt creaky and fun. Windows 3.1 was built up for business first and it felt like it.
All blue and corporate. Windows 3.0 just felt like a prototype.
Try it and see. There is a qualitative difference. 3.1 is more polished and yet, for me, more boring.Windows 3.0 was a test of the market and blew IBM out of the water. It exceeded almost everyone's expectations in terms of market impact. Thus, to follow that, Windows 3.1 was professionally designed, while 3.0 was originally a semi-secret project by the developers to get Gates to ACTUALLY produce a proper GUI with multitasking. He bought into it mind and it was formally developed but built on the programmers secret in-their-spare-time project, which began with crowbarring Windows 2 to run multiple DOS programs at a time.So - nothing more than fun. Windows 3.1 was just a bore.
I liked Windows 95, mind. The OS was less stable than 3.1! But the functionality was stunning at the time and I liked the GUI. That's why I stick with KDE. It feels like Windows 95 done right - properly developed.
Microsoft just kept overreacting every tie there was a technical innovation they had to monopolize again resulting in massive lurches in the GUI. Windows 8 was the ultimate in that. Redmond learnt the hard way that bullish ego does not equate to the world changing around you.I could handle Windows XP and it was more reliable than than the old 9x kernel but I was not a hge fan.
Vista gave me nightmares. Windows 7 I could use at work but hated the thought of it at home and, in 2012, I jumped to KDE and Linux and never looked back - especially when I found Kdenlive!I haven't found computing fun in a long time. Video editing, yes, but not technology. Mint and KDE give me a sense of fun again.
WIndows was fast becoming dictatorial in how it would be used.Now I love seeing people's faces when I start up apps with two button presses including starting up Windows 3.0. It's like the old Sinclair days when you pressed a button and something happened instantly. OK, maybe after 'Newline/enter.' I like pressing buttons. Fred Barclay wrote:One last thing. Has anyone tried doing the same thing with Windows 1 or 2?
I've got some more floppy files for these that I think would be fun to install in DosBox.Although I have not tried it, I would have thought Windows 2 would run. I did get it running under Windows 95 at one point! However, you will have to install from hard disk.Windows 1 is more painful because it absolutely insists on installing from Drive A: and I was never able to resolve that. Also, Windows 1 insists on being run on DOS 2-3 ONLY. So you may need to play around with DOSBox settings.But when you say 'fun' it isn't. Windows was described as 'user hostile' back in the 1980's.
All software for Windows 2 will run under Windows 3.x and will be much more usable. Windows 1 was written mainly to prevent software houses producing software for GEM and was not a serious enterprise. It has no overlapping Windows, runs like treacle, has no icons, is totally unintuitive and has no software written for it. I think there was one DTP package written for it but, generally, the industry looked at Windows 1 and went, “No.” Using 1 and 2 really hurts.Thanks to Bill Gates we had to wait until 1990 for a faintly usable GUI on the PC. Hence my frustration with those who insist Linux is hard to use and 'you can only compile software from source.'
I want to scream, “No, that was true in 1996! Do you not remember what Windows was originally like?” People have the memory of a goldfish for Windows and the memory of an elephant for Linux.I mean, I like legacy tech. I like taking teeny, tiny, feeble machines and making them do the impossible hence video editing on my tiny c50 netbook. But even I have run up Windows 1 and 2 and then tossed them aside.Still, if you want to talk legacy Windows and fun, PM me and I can give you hints and tips and more for Windows 3.x. You might want to try 3.0 some time.
You'll be amazed what you can squeeze out of it. Still, if you want to talk legacy Windows and fun, PM me and I can give you hints and tips and more for Windows 3.x. You might want to try 3.0 some time. You'll be amazed what you can squeeze out of it.Be checking your PM inbox soonYou are going to have to be patient with me though. Practically all of my (pathetic) computer knowledge is in Linux. Windows is going to take some getting used to.I've already got 3.0 but 7zip balks at extracting the files.I noticed the problem with Win 1 on insisting on drive A.
I haven't tried 2.xx yet. Fred Barclay wrote:I've gotten past that persistent bug in Windows 1 where it continues asking you to put a new floppy in drive A, but installation is still failing.Nicely done! If I may ask, how did you get past the 'Drive A:' limitation with Windows 1? I've also got several old.img files, and have played with installing old Windowz versions in different VMs, but never could get past the 'Drive A:' limit with Win 1.03.
Well, I did.once. by actually swapping the HDD out, installing DOS 3, and using a real floppy drive. But that's more of a pain than it's worth. (I did get 'Microsoft BOB' working in VM, which was an interesting experience.).
Contents.Basic ConceptsDOSBox is an emulator that recreates a MS-DOS compatible environment (complete with Sound, Input, Graphics and even basic networking). This environment is complete enough to run many classic MS-DOS games completely unmodified.
In order to utilize all of DOSBox's features you need to first understand some basic concepts about the MS-DOS environment. (Modems/Networking)InstallationThe first step is to install DOSBox. This guide will use the Windows 32-bit version which is available for. Download the for your operating system.
If you are a Windows user, get the Win32 installer.After downloading, install DOSBox to any directory. Also, make a folder to put all your old games in. I put DOSBox in C:DOSBox, and my old games directory is C:OLDGAMES. I put a game in my OLDGAMES directory, TESTDRIV, which is, an old racing game. Your directories should look like this. Error creating thumbnail: Unable to save thumbnail to destination Running a gameNow, the hardest part, getting games to run. First, run dosbox.exe in your DOSBox folder.
Remember that OLDGAMES directory you created in Step 1? You have to basically set that as new directory just for DOSBox. Essentially, it's going to become the drive of DOSBox. So, type:Z: MOUNT C C:OLDGAMESDrive C mounted as local directory C:OLDGAMESTo dissect the above:.: Tells the program to a directory. C: Tells the program what you want your new drive to be called (leaving it as C: is fine).
C:OLDGAMES: This is the directory I want to set as the new drive for DOSBox, because all my games are in it. If you created a different directory, write in the directory you created.(Note: If you want to a CD-ROM instead of a folder, type this: Z: MOUNT D D: -t cdromMSCDEX installed.Drive D is mounted as CDRom D:(Note: 'cdrom' is case sensitive and must be lowercase!)In this example, D: -T cdrom tells DOSBox that my D: drive is a CD-ROM drive, and the first D, tells DOSBox what my new drive name should be called. If you are running your game off a CD-ROM then make sure to use D: in place of C: in the following examples. You can find instructions on how to other devices, such as floppy drives, in the section).After you've done this, you will be prompted with a. Now, just write what you wanted to call your new DOSBox drive, which as I said above, we called C. To navigate to that newly mounted drive just type in:Z: C:C:Hopefully, you're all set! Now, it's time to run the game.
Previously I had mentioned a game called TESTDRIV in my OLDGAMES folder. I now want DOSBox to go to that folder.
Dosbox Install Windows 98
So type in:C: CD TESTDRIVC:TESTDRIVThat's it! Stands for 'Change Directory', so you've changed the directory to TESTDRIV. You can find instructions on how to use the command, in the section of the article.One more step, running the game! Most games have an EXE file in their directory that you can run. However, some might require a BAT file, or COM file (common in demos and really old games). Most of the time, the file is in the root folder. Please consult the documentation of your game for which file is needed to start the game.
In the case of, it's TDCGA.EXE. So now, I just type this:C:TESTDRIV TDCGA.EXEThat's it! Here's a picture of all of the commands I've written about in Step 2. Error creating thumbnail: Unable to save thumbnail to destination Alternate methods for running a gameThe steps described above are closely aligned with how DOS Based operating systems behave natively. However modern operating system allow for more user friendly (although less authentic) ways of playing your favorite games. If the steps above seem tedious or confusing you can try some of these other guides.
In most cases these guides will still require you to setup a working DOSBox environment.NOTE: If you have problems with launching the game, unrecognizable errors being spit out, saving settings, or having the game drop out while running it, one thing to try is to make sure all the files are not set to Read Only. In Windows, select the folder of the game, right click and hit properties, uncheck Read Only if it is checked, and apply to all sub folders.If you have other errors, please search the first before posting a question.PerformanceYay, you've gotten your game to run!
Install Windows 1 01 Dosbox Tutorial Pdf
But maybe you're experiencing slowdown? How do you fix this? With the following commands:CTRL+F7 = Decreases frameskipCTRL+F8 = Increases FrameskipCTRL+F11 = Slows down the gameCTRL+F12 = Speeds up the gamePress CTRL+ALT+DEL to open the Task Manager, and click the Performance tab. Start by pressing CTRL+F12 until your CPU Usage level begins to go above 95%. After that, if you still need a performance boost, hit CTRL+F8 to have DOSBox not render some frames. The console window will display all of the changes you've made, and the top of the game window will display the current settings.
Adjust these settings as needed until your game goes smoothly. Please keep in mind that not all games will run smoothly on DOSBox. Error creating thumbnail: Unable to save thumbnail to destination Other Useful features Quick Start for WindowsWindows users have an option of dragging the EXE of their DOS game onto the DOSBox program (or shorcut pointing to the DOSBox program). This will automatically start the game.
If this doesn't work, then I would recommend reading the rest of this article.Automatically Mounting Your DOS Games folderYou can save yourself some time by having DOSBox automatically your folders and change the drive to C. In original DOS based operating systems a file called contained any commands that the user wanted executed every time the computer booted up. This functionality is simulated by the section of the file.For DOSBox versions older than 0.73 browse into program installation folder and open the file in any text editor. For version 0.73 go to Start Menu and click on 'Configuration' and then 'Edit Configuration'. Then scroll down to the very end, and add these lines:MOUNT C C:OLDGAMESC:Now those commands will be executed automatically when starting! If you're having trouble with that, make sure it looks like this (look at the bottom).