VOGONS

Common searches


First post, by Fester77

User metadata
Rank Newbie
Rank
Newbie

I got an laptop with win 7 widescreen 1366x768.

Im trying to get DB (0.74) to run fullscreen using all of the screen.
Problem now is that i get two vertical bars left and right.

I remember some other version of DB (something 0.6x) i could open DB in a window and literally stretch it like a mediaplayer. This was on another laptop that got XP , don´t know if that matters.
Having seen that I figure it most be possible to stretch the widescreen thus not having those vertical black bars.
I tried swtiching the output (ddraw,opengl etc), and tested setting aspect true and false.

I tried searching the forums but mostly find stuff regarding the opposite, that is people who like the orignal aspect.

Any ideas?

Reply 2 of 10, by Fester77

User metadata
Rank Newbie
Rank
Newbie

--------------------------------------------------------------------------------------

# This is the configurationfile for DOSBox 0.74. (Please use the latest version of DOSBox)
# Lines starting with a # are commentlines and are ignored by DOSBox.
# They are used to (briefly) document the effect of each option.

[sdl]
# fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back)
# fulldouble: Use double buffering in fullscreen. It can reduce screen flickering, but it can also result in a slow DOSBox.
# fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# Using your monitor's native resolution with aspect=true might give the best results.
# If you end up with small window on a large screen, try an output different from surface.
# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
# (output=surface does not!)
# output: What video system to use for output.
# Possible values: surface, overlay, opengl, openglnb, ddraw.
# autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)
# 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.
# pause is only valid for the second entry.
# Possible values: lowest, lower, normal, higher, highest, pause.
# mapperfile: File used to load/save the key/event mappings from. Resetmapper only works with the defaul value.
# usescancodes: Avoid usage of symkeys, might not work on all operating systems.

fullscreen=false
fulldouble=false
fullresolution=0x0
windowresolution=0x0
output=ddraw
autolock=true
sensitivity=250
waitonerror=true
priority=higher,lower
mapperfile=mapper.txt
usescancodes=true

[dosbox]
# language: Select another language file.
# machine: The type of machine tries to emulate.
# Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
# captures: Directory where things like wave, midi, screenshot get captured.
# memsize: Amount of memory DOSBox has in megabytes.
# This value is best left at its default to avoid problems with some games,
# though few games might require a higher value.
# There is generally no speed advantage when raising this value.

language=
machine=svga_s3
captures=capture
memsize=32

[render]
# frameskip: How many frames DOSBox skips before drawing one.
# aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!.
# scaler: Scaler used to enlarge/enhance low resolution modes.
# If 'forced' is appended, then the scaler will be used even if the result might not be desired.
# Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x,

rgb3x, scan2x, scan3x.

frameskip=0
aspect=true
scaler=normal3x

[cpu]
# core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
# Possible values: auto, dynamic, normal, simple.
# cputype: CPU Type used in emulation. auto is the fastest choice.
# Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
# cycles: Amount of instructions DOSBox tries to emulate each millisecond.
# Setting this value too high results in sound dropouts and lags.
# Cycles can be set in 3 ways:
# 'auto' tries to guess what a game needs.
# It usually works, but can fail for certain games.
# 'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
# (Example: fixed 4000).
# 'max' will allocate as much cycles as your computer is able to handle.
#
# Possible values: auto, fixed, max.
# cycleup: Amount of cycles to decrease/increase with keycombo.(CTRL-F11/CTRL-F12)
# cycledown: Setting it lower than 100 will be a percentage.

core=auto
cputype=auto
cycles=22000
cycleup=500
cycledown=500

[mixer]
# nosound: Enable silent mode, sound is still emulated though.
# rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
# Possible values: 1024, 2048, 4096, 8192, 512, 256.
# prebuffer: How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=44100
blocksize=1024
prebuffer=20

[midi]
# mpu401: Type of MPU-401 to emulate.
# Possible values: intelligent, uart, none.
# mididevice: Device that will receive the MIDI data from MPU-401.
# Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use.
# See the README/Manual for more details.

mpu401=intelligent
mididevice=default
midiconfig=

[sblaster]
# sbtype: Type of Soundblaster to emulate. gb is Gameblaster.
# Possible values: sb1, sb2, sbpro1, sbpro2, sb16, gb, none.
# sbbase: The IO address of the soundblaster.
# Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300.
# irq: The IRQ number of the soundblaster.
# Possible values: 7, 5, 3, 9, 10, 11, 12.
# dma: The DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# hdma: The High DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7.
# sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
# Possible values: auto, cms, opl2, dualopl2, opl3, none.
# oplemu: Provider for the OPL emulation. compat might provide better quality (see oplrate as well).
# Possible values: default, compat, fast.
# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
# Possible values: 44100, 49716, 48000, 32000, 22050, 16000, 11025, 8000.

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
sbmixer=true
oplmode=auto
oplemu=default
oplrate=44100

[gus]
# gus: Enable the Gravis Ultrasound emulation.
# gusrate: Sample rate of Ultrasound emulation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# gusbase: The IO base address of the Gravis Ultrasound.
# Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
# gusirq: The IRQ number of the Gravis Ultrasound.
# Possible values: 5, 3, 7, 9, 10, 11, 12.
# gusdma: The DMA channel of the Gravis Ultrasound.
# Possible values: 3, 0, 1, 5, 6, 7.
# ultradir: Path to Ultrasound directory. In this directory
# there should be a MIDI directory that contains
# the patch files for GUS playback. Patch sets used
# with Timidity should work fine.

gus=true
gusrate=44100
gusbase=240
gusirq=5
gusdma=3
ultradir=C:\OS\ULTRASND

[speaker]
# pcspeaker: Enable PC-Speaker emulation.
# pcrate: Sample rate of the PC-Speaker sound generation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
# Possible values: auto, on, off.
# tandyrate: Sample rate of the Tandy 3-Voice generation.
# Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).

pcspeaker=true
pcrate=44100
tandy=auto
tandyrate=44100
disney=true

[joystick]
# joysticktype: Type of joystick to emulate: auto (default), none,
# 2axis (supports two joysticks),
# 4axis (supports one joystick, first joystick used),
# 4axis_2 (supports one joystick, second joystick used),
# fcs (Thrustmaster), ch (CH Flightstick).
# none disables joystick emulation.
# auto chooses emulation depending on real joystick(s).
# (Remember to reset dosbox's mapperfile if you saved it earlier)
# Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
# timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away).
# autofire: continuously fires as long as you keep the button pressed.
# swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks.
# buttonwrap: enable button wrapping at the number of emulated buttons.

joysticktype=auto
timed=true
autofire=false
swap34=false
buttonwrap=false

[serial]
# serial1: set type of device connected to com port.
# Can be disabled, dummy, modem, nullmodem, directserial.
# Additional parameters must be in the same line in the form of
# parameter:value. Parameter for all types is irq (optional).
# for directserial: realport (required), rxdelay (optional).
# (realport:COM1 realport:ttyS0).
# for modem: listenport (optional).
# for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
# transparent, port, inhsocket (all optional).
# Example: serial1=modem listenport:5000
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial2: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial3: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.
# serial4: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial.

serial1=dummy
serial2=dummy
serial3=disabled
serial4=disabled

[dos]
# xms: Enable XMS support.
# ems: Enable EMS support.
# umb: Enable UMB support.
# keyboardlayout: Language code of the keyboard layout (or none).

xms=true
ems=false
umb=true
keyboardlayout=auto

[ipx]
# ipx: Enable ipx over UDP/IP emulation.

ipx=false

[autoexec]
# Lines in this section will be run at startup.
# You can put your MOUNT lines here.
mount c c -freesize 1000

-------------------------------------------------------------------------------------

AMD Mobility Radeon HD 5470 graphics
(http://www.trustedreviews.com/Acer-Aspire-555 … G_Laptop_review)

-------------------------------------------------------------------------------------

fullresolution=0x0 <- have tried setting to screenres
windowresolution=<- also tried setting to screenres
output=ddraw

Reply 3 of 10, by Mau1wurf1977

User metadata
Rank l33t++
Rank
l33t++

Change these lines and give it a go!

fullscreen=true
fullresolution=1024x768
aspect=true

IF your display adapter (driver setting) is set to stretch, you should get a stretched full screen image when playing a 320 x 200 DOS game.

Reply 4 of 10, by Fester77

User metadata
Rank Newbie
Rank
Newbie

Tried it but it did not do the trick.
I asume you meant if my hard/software outside DB whould scale that to fullscreen.
Maybe this box has that stuff I dunno. What I DO know is that when I change screenres in win say to 800x600 those vertical blackbars also apear.
Seems my screen is only showing real lines so I can asume their is no hardware-scaling or there is some gizmo I forgot to turn on.

Reply 5 of 10, by Mau1wurf1977

User metadata
Rank l33t++
Rank
l33t++

Ok, try this.

Set the windows desktop to 1024 x 768 and tell me if it's stretched or letterboxed (black bars left and right).

If it's letterboxed, you need to go into the AMD/ATI driver and change the scaling setting, so that it does stretch.

Reply 6 of 10, by Fester77

User metadata
Rank Newbie
Rank
Newbie

I´ve tried that ... get vertical blackbars left and right.
I´ve found that I must enable GPUscaler in my catalyst control center. I found it to be grayed out (11.3). ATM I´m getting the latest (11.5). Perhaps the GPUscaler will not be grayed out after I´ve installed it.

Sure this is a solution. But its on a hardware/driver basis.
I still wonder what happend to DB and being able to use its softscaler like I mentioned above.

Anyway I´ll let you know on the GPUscaler when its done.

Reply 7 of 10, by Fester77

User metadata
Rank Newbie
Rank
Newbie

nah still cant get the GPUscaler to work and that is outside DB to fix. So its back to getting the DB softscaler to work again.

It seems window resolution is not what getting sized to what you set to more to what is closest to some preset sizes. 800x600 get to that, 1024x768 but all above turn to 1024x768, 1200x768 for example dont seem to make any difference.
But is seem pointless as this sets the initial DB window and as soon as a game is launched the game resets to whatever res is used by the game , unscaled.

independed GPUscaling sure whould be great now...

Reply 8 of 10, by Fester77

User metadata
Rank Newbie
Rank
Newbie

I found this
http://forums.amd.com/game/messageview.cfm?ca … keyword1=scaler

I got there in regedit, mine was set 4. with the risk of having the laptop exploding in my face I changed it to 3. After when i changed res in windows to 800x600 and you name it res, they ALL where scaled to the whole screen.

So i switched back the DB.conf to what you suggested first (fullscreen 1024x768) and now all is shown right as GPUscaler takes over.
Norton commander is slightly litterboxed but games come in in fullscreen (whole) .

Reply 10 of 10, by Mau1wurf1977

User metadata
Rank l33t++
Rank
l33t++
Fester77 wrote:

So i switched back the DB.conf to what you suggested first (fullscreen 1024x768) and now all is shown right as GPUscaler takes over.
Norton commander is slightly litterboxed but games come in in fullscreen (whole) .

Awesome!

Norton Commander uses textmode I think and that might be the reason.

Enjoy your games!