# rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality. # nosound: Enable silent mode, sound is still emulated though. # cycledown: Setting it lower than 100 will be a percentage. # cycleup: Amount of cycles to increase/decrease with keycombo. # 'max' will allocate as much cycles as your computer is able to handle This is what you usually need if 'auto' fails. # 'fixed #number' will set a fixed amount of cycles. # It usually works, but can fail for certain games. # 'auto' tries to guess what a game needs. Setting this value too high results in sound dropouts and lags. # cycles: Amount of instructions DOSBox tries to emulate each millisecond. # Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch. # Possible values: auto, dynamic, normal, simple. auto will switch to dynamic if available and appropriate. # Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x. If 'forced' is appended,the scaler will be used even if the result might not be desired. # scaler: Scaler used to enlarge/enhance low resolution modes. # aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!. # frameskip: How many frames DOSBox skips before drawing one. # There is generally no speed advantage when raising this value. # though few games might require a higher value. # This value is best left at its default to avoid problems with some games, # memsize: Amount of memory DOSBox has in megabytes. # captures: Directory where things like wave, midi, screenshot get captured. # Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe. # machine: The type of machine tries to emulate. # language: Select another language file. # usescancodes: Avoid usage of symkeys, might not work on all operating systems. # mapperfile: File used to load/save the key/event mappings from. # Possible values: lowest, lower, normal, higher, highest, pause. (pause is only valid for the second entry) Second entry behind the comma is for when dosbox is not focused/minimized. # waitonerror: Wait before closing the console if dosbox has an error. # autolock: Mouse will automatically lock, if you click on the screen. # Possible values: surface, overlay, opengl, openglnb. # output: What video system to use for output. # windowresolution: Scale the window to this size IF the output device supports hardware scaling. # fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. # fulldouble: Use double buffering in fullscreen. # fullscreen: Start dosbox directly in fullscreen. # They are used to (briefly) document the effect of each option. # Lines starting with a # are commentlines. (Yeah, technically it stank but I enjoyed using it at the time.) - plus the video editing I get with Kdenlive.Ĭode: Select all # This is the configurationfile for DOSBox 0.73. I haven't enjoyed using an OS so much since Windows 95. However, I now just run up Windows 3.0 to shock students who have only seen XP onwards. I have excel 2 and 3, Access 1, Wordstar for Windows, loadsa utilities. I built up quite a stack of Windows 3.0 software. (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 have a shell script that sets DOSBox to an SVGA 386 with 3MB of RAM. 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: In regards to setting up and starting Windows - please be aware that DOSBox is 100% 16 bit. It's shareware so install on a Windows box, extract and uninstall. Winimge has been the standard for img files in Windows so there is a high liklihood this will work. Here is a possible solution but no guarentees: 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. img files! So you will have to go hunting for the appropriate utility. The trouble is that there is no standard for. The image files will have to be uncompressed first and then used as install disks. See it my online Linux demo (link in my signature.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |