fullscreen?

Yes, in fullscreen. I play all of my old games in fullscreen. I have been meaning to post this bug for a while now, but forgot to. It causes many games to have issues and some can even desynchronize if playing a network game and it comes on.

SDL says it disables the screensaver by default in fullscreen.

Want a Fraps?

http://www.libsdl.org/faq.php?action=listentr … s&category=9#90
http://www.libsdl.org/release/changes-1.2.html

Not sure what version of SDL DOSBox 0.72 is using...

I don't care what the notes say, it's broken. This happens on every computer and laptop I have run DOSBox 0.72 on. Want to test it? Simple! Set your screensaver to 1min, start DOSBox and sit back for a minute. Any questions?

Read what MiniMax wrote. And i don't want "a fraps".

Not broken for me.

Screensaver set to 1 minute.

Launched DOSBox.
Waited 1 min, 10 seconds.
Screensaver kicked in.
Pressed a key.
Exited DOSBox.

Launched DOSBox.
Pressed ALT-ENTER (fullscreen).
Waited 2 min or more.
No screensaver.
Exited DOSBox

Changed config to output=ddraw.

Launched DOSBox.
Pressed ALT-ENTER (fullscreen).
Waited 2 min or more.
No screensaver.
Pressed ALT-ENTER (windowed).
Waited 1 min or so.
Screensaver kicked in.
Pressed a key.
Exited DOSBox.

This with stock DOSBox 0.72, WinXP Pro/SP2.

12007-08-26  20:14         3 200 000 dosbox.exe
22007-08-17  19:44           331 776 SDL.dll

Any answers?

Well it hasn't worked that way on the dozen or so machines I have used it on, including this one. I suspect you may have a custom build and not realize it. I suppose I'll have to prove this FACT as well. I'll get the camcorder and record my INI settings being stock, stock DOSBox 0.72, and then show it with a screensaver. Note that if it kicks in while windowed, I could care less because I don't play windowed, but playing fullscreen and having the screensaver kick in is very annoying.

Uh READ what MiniMax wrote, and to what he linked.
Another hint: dosbox uses sdl 1.2.12 for the 0.72 release.
So this is no dosbox related thing, post your videos somewhere else.

It wasn't for fun that I posted the dates and sizes of my dosbox.exe and SDL.dll. If you had cared to check yours we would quickly discover if we are indeed using the same versions.

For your entertainment, I am now also posting the MD5 checksums. That should definitely show if we are using the same versions:

1cacb05c27202c3ab5b727867ef57fe32 *dosbox.exe
2097de590e613382fdd0d4ea289799867 *SDL.dll
314e5d3cf6b015066e6c9b04df8556e7c *DOSBox0.72-win32-installer.exe

Sephiroth: maybe you have some non-stock screensaver.

I did read what he wrote. He is stating that the screensaver is not kicking in during fullscreen operation, which is the exact opposite of every machine that I have ever used DOSBox on. This is mainly towers, but also several laptops. All are running XP SP2 with the exception of one or two, that use SP3. I can go into system specs if you want to blame that, but I think we both know that multiple systems with the same symptoms including several college machines proves that it isn't hardware-dependent.

Again, the problem that I am experiencing is that the screensaver DOES kick in during fullscreen operation. Windowed mode does not bother me at all because I don't use it except when debugging an old game or application. The screensaver kicks in during fullscreen operation in both OpenGL and DirectDraw modes. The reason that I am still posting is because I have been told that it does not behave this way when in fact it does.

*EDIT*

H-A-L, I am using the default screensaver that displays "Windows XP Professional", not a custom one, nor do i have custom screensavers installed. I keep my systems minimalistic to avoid problems while gaming, and as such have no extra services and have even disabled ones that I do not need, such as DNS and "Help And Support".

Max, I have the exact same filesizes as you. This definitely proves the existence of a bug if it chooses to show the screensaver on most systems but not others. That was the point in this thread to begin with, because I don't drop by and post problems for no reason. Oh and this problem occurs on nVidia, ATI, and Intel chipsets.

I did read what he wrote. He is stating that the screensaver is not kicking in during fullscreen

That's not the only thing he posted, see above.

Test some small SDL app and report it to them if it's reproducable.

I just used the stock DOSBox config to start DB0.72 and let it sit for 1min. Sure enough, my screensaver kicked in. I moved the mouse and then entered my password to unlock the system. I was presented with the desktop below. This should be enough proof, but if you desire, I will tape this, transfer it to AVI, and encode it to WMV or MPEG and put online so you can witness the bug in action. Oh, and my desktop normally runs in 1280x1024x32, not 640x400x8 or whatever that is.

Oh, and here's the DOSBox configuration used.

1# This is the configurationfile for DOSBox 0.72.
2# Lines starting with a # are commentlines.
3# They are used to (briefly) document the effect of each option.
4
5[sdl]
6# fullscreen -- Start dosbox directly in fullscreen.
7# fulldouble -- Use double buffering in fullscreen.
8# fullresolution -- What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
9# windowresolution -- Scale the window to this size IF the output device supports hardware scaling.
10# output -- What to use for output: surface,overlay,opengl,openglnb,ddraw.
11# autolock -- Mouse will automatically lock, if you click on the screen.
12# sensitiviy -- Mouse sensitivity.
13# waitonerror -- Wait before closing the console if dosbox has an error.
14# priority -- Priority levels for dosbox: lowest,lower,normal,higher,highest,pause (when not focussed).
15#             Second entry behind the comma is for when dosbox is not focused/minimized.
16# mapperfile -- File used to load/save the key/event mappings from.
17# usescancodes -- Avoid usage of symkeys, might not work on all operating systems.
18
19fullscreen=false
20fulldouble=false
21fullresolution=original
22windowresolution=original
23output=surface
24autolock=true
25sensitivity=100
26waitonerror=true
27priority=higher,normal
28mapperfile=mapper.txt
29usescancodes=true
30
31[dosbox]
32# language -- Select another language file.
33# memsize -- Amount of memory DOSBox has in megabytes.
34# machine -- The type of machine tries to emulate:hercules,cga,tandy,pcjr,vga.
35# captures -- Directory where things like wave,midi,screenshot get captured.
36
37language=
38machine=vga
39captures=capture
40memsize=16
41
42[render]
43# frameskip -- How many frames DOSBox skips before drawing one.
44# aspect -- Do aspect correction, if your output method doesn't support scaling this can slow things down!.
45# scaler -- Scaler used to enlarge/enhance low resolution modes.
46#           Supported are none,normal2x,normal3x,advmame2x,advmame3x,hq2x,hq3x,
47#                         2xsai,super2xsai,supereagle,advinterp2x,advinterp3x,
48#                         tv2x,tv3x,rgb2x,rgb3x,scan2x,scan3x.
49#           If forced is appended (like scaler=hq2x forced), the scaler will be used
50#           even if the result might not be desired.
51
52frameskip=0
53aspect=false
54scaler=normal2x
55
56[cpu]
57# core -- CPU Core used in emulation: normal,simple,dynamic,auto.
58#         auto switches from normal to dynamic if appropriate.
59# cycles -- Amount of instructions DOSBox tries to emulate each millisecond.
60#           Setting this value too high results in sound dropouts and lags.

61#           You can also let DOSBox guess the correct value by setting it to max.
62#           The default setting (auto) switches to max if appropriate.
63# cycleup   -- Amount of cycles to increase/decrease with keycombo.
64# cycledown    Setting it lower than 100 will be a percentage.
65
66core=auto
67cycles=auto
68cycleup=500
69cycledown=20
70
71[mixer]
72# nosound -- Enable silent mode, sound is still emulated though.
73# rate -- Mixer sample rate, setting any devices higher than this will
74#         probably lower their sound quality.
75# blocksize -- Mixer block size, larger blocks might help sound stuttering
76#              but sound will also be more lagged.
77# prebuffer -- How many milliseconds of data to keep on top of the blocksize.
78
79nosound=false
80rate=22050
81blocksize=2048
82prebuffer=10
83
84[midi]
85# mpu401      -- Type of MPU-401 to emulate: none, uart or intelligent.
86# device      -- Device that will receive the MIDI data from MPU-401.
87#                This can be default,alsa,oss,win32,coreaudio,none.
88# config      -- Special configuration options for the device. In Windows put
89#                the id of the device you want to use. See README for details.
90
91mpu401=intelligent
92device=default
93config=
94
95[sblaster]
96# sbtype -- Type of sblaster to emulate:none,sb1,sb2,sbpro1,sbpro2,sb16.
97# sbbase,irq,dma,hdma -- The IO/IRQ/DMA/High DMA address of the soundblaster.
98# mixer -- Allow the soundblaster mixer to modify the DOSBox mixer.
99# oplmode -- Type of OPL emulation: auto,cms,opl2,dualopl2,opl3.
100#            On auto the mode is determined by sblaster type.
101#            All OPL modes are 'Adlib', except for CMS.
102# oplrate -- Sample rate of OPL music emulation.
103
104sbtype=sb16
105sbbase=220
106irq=7
107dma=1
108hdma=5
109mixer=true
110oplmode=auto
111oplrate=22050
112
113[gus]
114# gus -- Enable the Gravis Ultrasound emulation.
115# gusbase,irq1,irq2,dma1,dma2 -- The IO/IRQ/DMA addresses of the 
116#            Gravis Ultrasound. (Same IRQ's and DMA's are OK.)
117# gusrate -- Sample rate of Ultrasound emulation.
118# ultradir -- Path to Ultrasound directory.  In this directory
119#             there should be a MIDI directory that contains
120#             the patch files for GUS playback.  Patch sets used
121#             with Timidity should work fine.
122
123gus=true
124gusrate=22050
125gusbase=240
126irq1=5
127irq2=5
128dma1=3
129dma2=3
130ultradir=C:\ULTRASND
131
132[speaker]
133# pcspeaker -- Enable PC-Speaker emulation.
134# pcrate -- Sample rate of the PC-Speaker sound generation.
135# tandy -- Enable Tandy Sound System emulation (off,on,auto).
136#          For auto Tandysound emulation is present only if machine is set to tandy.
137# tandyrate -- Sample rate of the Tandy 3-Voice generation.
138# disney -- Enable Disney Sound Source emulation. Covox Voice Master and Speech Thing compatible.
139
140pcspeaker=true
141pcrate=22050
142tandy=auto
143tandyrate=22050
144disney=true
145
146[joystick]
147# joysticktype -- Type of joystick to emulate: auto (default), none,
148#                 2axis (supports two joysticks,
149#                 4axis (supports one joystick, first joystick used),
150#                 4axis_2 (supports one joystick, second joystick used),
151#                 fcs (Thrustmaster), ch (CH Flightstick).
152#                 none disables joystick emulation.
153#                 auto chooses emulation depending on real joystick(s).
154# timed -- enable timed intervals for axis. (false is old style behaviour).
155# autofire -- continuously fires as long as you keep the button pressed.
156# swap34 -- swap the 3rd and the 4th axis. can be useful for certain joysticks.
157# buttonwrap -- enable button wrapping at the number of emulated buttons.
158
159joysticktype=auto
160timed=true
161autofire=false
162swap34=false
163buttonwrap=true
164
165[serial]
166# serial1-4 -- set type of device connected to com port.
167#              Can be disabled, dummy, modem, nullmodem, directserial.
168#              Additional parameters must be in the same line in the form of
169#              parameter:value. Parameter for all types is irq.
170#              for directserial: realport (required), rxdelay (optional).
171#              for modem: listenport (optional).
172#              for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
173#                             transparent, port, inhsocket (all optional).
174#              Example: serial1=modem listenport:5000
175
176serial1=dummy
177serial2=dummy
178serial3=disabled
179serial4=disabled
180
181[dos]
182# xms -- Enable XMS support.
183# ems -- Enable EMS support.
184# umb -- Enable UMB support.
185# keyboardlayout -- Language code of the keyboard layout (or none).
186
187xms=true
188ems=true
189umb=true
190keyboardlayout=none
191
192[ipx]
193# ipx -- Enable ipx over UDP/IP emulation.
194
195ipx=false
196
197[autoexec]
198# Lines in this section will be run at startup.
199
200

I got this default configuration by using "writeconfig -write dosbox.conf" from within DOSBox.

> and then entered my password to unlock the system.

This might make a differece.

No, it shouldn't. Bear in mind that if the screensaver was DISABLED as it should be, the system never would have locked. A Windows XP system will only lock if the current user has a password on the account and the screensaver kicks in OR if the user presses the Windows logo key and L at the same time. Besides, this happens on systems that log a default user right in without a password as well, so I have my doubts that a password in Windows has any relation to disabling the screensaver.

Test some small SDL app and report it to them if it's reproducable.

I don't have time to run around looking for an SDL application. If you know of one that doesn't mess with the registry or anything else, doesn't require an installer, and is basically a small file I can execute without altering anything on the system, please link me and I'll get right on it, but I refuse to install some game or something and add entries to my registry or plop files in my system32 directory just to prove that I am having an issue across multiple machines with DOSBox.