rfnagel wrote:

jwt27 wrote:

Great! I've searched for that game on there earlier but was unable find it, and I didn't bother to add it. I never played this very often anyway, but this is certainly a good reason to start doing so 😀 I just added two scores on the Duke Nukem table, on Novice and Regular.

And you more than DOUBLED my score for the Duke Nukem pinball table <AARRGGHH> 🤣! 😀 Man, I remember when I got the score a while back that I posted for that table... I "played my ass off", I don't think I could get any higher 🤣!

That... was a bit of an accident 🤣
Right after I posted my existing high scores (there weren't that many, I played this maybe only once or twice before on this system) I just started playing and got this score on the first run.

Besides, I was just wondering... I have my monitor set to 160Hz, but does this game actually draw at 160fps? Movement does seem super smooth. How would I check that? Not that it really matters anyway.. but it's just nice to know 😀

And.. some more Epic Pinball speed glitches for your enjoyment 😀
http://imageshack.us/a/img850/7162/img4033x.jpg
http://imageshack.us/a/img580/5599/img4031xe.jpg

rfnagel wrote:

You know, I SWEAR... I SUCK at SOOOOOOO may games. […]
Show full quote

WolverineDK wrote:

It seems to me, I am not the only who collected cheats and what not many years ago, and I suffered from being shitty at games. Cause I was constantly "hunting" for cheats and codes and so forth back in 1990s. And I though I was "helping" people with knowing and finding cheat codes and so forth for the games. Oh well I learned my lesson, but I still had fun 😀

You know, I SWEAR... I SUCK at SOOOOOOO may games.

Why?

Because when I get a new game I spend MORE freakin' time trying to figure out every little "tidbit" and "niblet" of the game, than ACTUALLY PLAYING IT 🤣!

(EDIT) gawd knows I spend MORE TIME using the utility in the attached screenshot than I usually do playing the games 🤣!

I used to cheat in about every game as well, when I was younger. I suppose once you get a bit older (not that I'm old or anything 🤣) you'll realize that games are much more fun if you're actually good at it. Maybe no-brainer games offering zero challenge becoming the norm has something to do with it.

rfnagel and jwt27, I believe also why I cheated so much in games. Was because I am a tinkerer of stuff. And me cheating in those games were basically because I was exploring the possibilities 😀 So cheating is perhaps the start to exploring/tinkering ? 😀

jwt27 wrote:

That... was a bit of an accident 🤣. Right after I posted my existing high scores (there weren't that many, I played this maybe only once or twice before on this system) I just started playing and got this score on the first run.

Man... that's pretty impressive! 😀

jwt27 wrote:

Besides, I was just wondering... I have my monitor set to 160Hz, but does this game actually draw at 160fps? Movement does seem super smooth. How would I check that? Not that it really matters anyway.. but it's just nice to know 😀

Unfortunately, I don't think that there are any framerate counters built into any of these games (via cheat code, etc...).

jwt27 wrote:

I used to cheat in about every game as well, when I was younger. I suppose once you get a bit older (not that I'm old or anything 🤣) you'll realize that games are much more fun if you're actually good at it. Maybe no-brainer games offering zero challenge becoming the norm has something to do with it.

To tell the truth, I don't cheat in the games when I'm playing "normally". I usually try out all of the cheat codes that I can find (or discover on my own), simply to see what they do. But, if I'm "really playing", I never cheat.

Hehe, I even backup ALL of my various games' validly-played high score files... so's I don't screw them up when I'm experimenting with cheats and such 😀

WolverineDK wrote:

rfnagel and jwt27, I believe also why I cheated so much in games. Was because I am a tinkerer of stuff. And me cheating in those games were basically because I was exploring the possibilities 😀 So cheating is perhaps the start to exploring/tinkering ? 😀

THAT is exactly why I do the same... twiddling around to see what I can discover about the games, and learning their inner-workings and mechanics 😀

Sort of on-topic... Hehe, here's a little tidbit for y'all:

For Epic Pinball, go to a DOSBox prompt.

Then, type "ORDER.EXE PIN01.TFP <ENTER>", "ORDER.EXE PIN02.TFP" <ENTER>, "ORDER.EXE PIN03.TFP" <ENTER>, etc.. <grin> 😀

rfnagel wrote:

Sort of on-topic... Hehe, here's a little tidbit for y'all:

For Epic Pinball, go to a DOSBox prompt.

Then, type "ORDER.EXE PIN01.TFP <ENTER>", "ORDER.EXE PIN02.TFP" <ENTER>, "ORDER.EXE PIN03.TFP" <ENTER>, etc.. <grin> 😀

🤣 I think I do know the rules 😉

Hehe, the reason that I remembered that one (i.e. "Adventures with a hex editor" <grin>):

Back in the day, I was quite impressed with those "TFP" documents... they supported bookmarked hyperlinking, pretty pictures, and various animated text effects.

I thought to myself that I could make some neat "presentations" using whatever it was that was used to create those "TFP" files, so I called Epic MegaGames and asked what they used. They said that they really didn't remember, as a third-party had created those documents.

Loading "ORDER.EXE" in a hex editor/viewer reveals this at the bottom of the file:

1PROGRAM BY STEVE FOSTER (209)533-4814!!!

...so I called that phone number 🤣!

Low and behold, Steve answered the phone, and we had a little discussion about those "TFP" documents.

Seems that *HE* was the one who had created and developed this format, and had even created an editor to create new ones from scratch.

He had licensed his editor to Epic MegaGames back when they used it to create their very *FIRST* "ORDER.TFP" catalog file... you know, how Epic MegaGames always used to use those older ANSI graphics for their "CATALOG.EXE" files? They wanted something nicer and fancier looking.

Well, as it turns out, his license to Epic MegaGames was ONLY for use with their FIRST "TFP" catalog file, and NOT for creating all of the in-game help and catalog files that Epic MegaGames was using for most all of their games of the time (including "One Must Fall: 2097").

He had NO idea that Epic MegaGames was using his proprietary editor and document format for all of their games! Heh, and the software *COMPANIES* are concerned about "pirating" 🤣?

rfnagel wrote:

Heh, and the software *COMPANIES* are concerned about "pirating" 🤣?

Off-topic, but along those same lines...

On a Windows XP installation, this directory:

WINDOWS\Help\Tours\WindowsMediaPlayer\Audio\Wav

...these files:

wmpaud1.wav
wmpaud2.wav
wmpaud3.wav
wmpaud4.wav
wmpaud5.wav
wmpaud6.wav
wmpaud7.wav
wmpaud8.wav
wmpaud9.wav

A looksie in a hex editor reveals these WAV comment chunks at the end of the files:

1INFOICRD 2000-04-06
2IENG Deepz0ne
3ISFT Sound Forge 4.5

YES, Mickey$oft was using the PIRATED "Deepz0ne" release of Sound Forge v4.5 to create those music WAVs with (Google it) 🤣!

rfnagel: The music on your site is beautiful, and in some ways. I think it would be splendid if you had a cooperation with Star Salzman ( http://www.starblast.org/ ), you both could benefit from it. But thank goodness I am not interested in politics. Cause then I could give you a run for your money in debating for or against the current problems in both my country and yours.

WolverineDK wrote:

rfnagel: The music on your site is beautiful

MANY THANKS, I'm glad you enjoyed the music! 😀

As you can probably tell, I like a lot of genres of music, but for my composing I usually favor "blockbuster movie" type of soundtracks, as well as pretty melodies 😀

Some of the stuff is simply just me "playing around" though (such as the "Astrosmash" tunes <grin>).

That being said, that isn't even 10% of my music... there is a LOT of stuff that I either haven't recorded to MP3s, or haven't got off of my butt and uploaded.

WolverineDK wrote:

and in some ways. I think it would be splendid if you had a cooperation with Star Salzman ( http://www.starblast.org/ ), you both could benefit from it.

Thanks for the link, I'll check out his site ASAP 😀

WolverineDK wrote:

But thank goodness I am not interested in politics. Cause then I could give you a run for your money in debating for or against the current problems in both my country and yours.

Hehe, anyone who know me knows that I SPEAK MY MIND 🤣! Hehe, and you probably wouldn't want to "friend" me on FaceBook as well 🤣! 😀

rfnagel wrote:

jwt27 wrote:

That... was a bit of an accident 🤣. Right after I posted my existing high scores (there weren't that many, I played this maybe only once or twice before on this system) I just started playing and got this score on the first run.

Man... that's pretty impressive! 😀

Aaand... I already beat it. Just by a little bit, though.

rfnagel wrote:

jwt27 wrote:

Besides, I was just wondering... I have my monitor set to 160Hz, but does this game actually draw at 160fps? Movement does seem super smooth. How would I check that? Not that it really matters anyway.. but it's just nice to know 😀

Unfortunately, I don't think that there are any framerate counters built into any of these games (via cheat code, etc...).

I already found out.. I took some pictures of the screen at varying shutter speeds (multiples of 1/160s). At 1/80 I see two frames, 1/40 shows 4 frames, 1/25 shows 6, etc.. So yes, it IS drawing at 160fps 😀

rfnagel wrote:

jwt27 wrote:

I used to cheat in about every game as well, when I was younger. I suppose once you get a bit older (not that I'm old or anything 🤣) you'll realize that games are much more fun if you're actually good at it. Maybe no-brainer games offering zero challenge becoming the norm has something to do with it.

To tell the truth, I don't cheat in the games when I'm playing "normally". I usually try out all of the cheat codes that I can find (or discover on my own), simply to see what they do. But, if I'm "really playing", I never cheat.

Hehe, I even backup ALL of my various games' validly-played high score files... so's I don't screw them up when I'm experimenting with cheats and such 😀

I just have Epic Pinball installed twice, one to try out the cheats and one with the real scores.

rfnagel wrote:

Off-topic, but along those same lines... […]
Show full quote

rfnagel wrote:

Heh, and the software *COMPANIES* are concerned about "pirating" 🤣?

Off-topic, but along those same lines...

On a Windows XP installation, this directory:

WINDOWS\Help\Tours\WindowsMediaPlayer\Audio\Wav

...these files:

wmpaud1.wav
wmpaud2.wav
wmpaud3.wav
wmpaud4.wav
wmpaud5.wav
wmpaud6.wav
wmpaud7.wav
wmpaud8.wav
wmpaud9.wav

A looksie in a hex editor reveals these WAV comment chunks at the end of the files:

Copy code to clipboard

1INFOICRD 2000-04-06
2IENG Deepz0ne
3ISFT Sound Forge 4.5

YES, Mickey$oft was using the PIRATED "Deepz0ne" release of Sound Forge v4.5 to create those music WAVs with (Google it) 🤣!

Wow! Who would have thought... 🤣

Oh and something else...
I hope IBM fired the guy who decided the shift keys on the Model M did not need stabilizing bars. 😒

jwt27 wrote:

Aaand... I already beat it. Just by a little bit, though.

Man, I swear, I don't know how you get those crazy high scores 🤣! I'm thinking that it must be something that I'm doing wrong... NOT fully understanding the table rules and such (which can make a HUGE difference in one's final scores).

jwt27 wrote:

I already found out.. I took some pictures of the screen at varying shutter speeds (multiples of 1/160s). At 1/80 I see two frames, 1/40 shows 4 frames, 1/25 shows 6, etc.. So yes, it IS drawing at 160fps 😀

Hey, that's a GREAT idea! 😀 I never thought of that before, but one thing I did remember... a buddy of mine used to FRAPS some of our Counter-Strike games, and he said that FRAPS would display what the actual framerate of the game was (although, the Half-Life GoldSource engine DOES already have a console command to display one's framerate).

jwt27 wrote:

I just have Epic Pinball installed twice, one to try out the cheats and one with the real scores.

Hey, this might be simpler for you... simply back up your "CONFIG.PIN" and "HISCORE.PIN" files 😀

jwt27 wrote:

Wow! Who would have thought... 🤣

Hehe, yeah really, who would have thought... this from a company who sics their trademark lawyers like rapid dogs on most ANYONE who farts the wrong way!

jwt27 wrote:

Oh and something else... I hope IBM fired the guy who decided the shift keys on the Model M did not need stabilizing bars. 😒

Man... If I had a keyboard that didn't have those bars on the shift keys (or the spacebar and enter keys as well), mine would have fell off a LONG time ago 🤣!

rfnagel wrote:

jwt27 wrote:

Aaand... I already beat it. Just by a little bit, though.

Man, I swear, I don't know how you get those crazy high scores 🤣! I'm thinking that it must be something that I'm doing wrong... NOT fully understanding the table rules and such (which can make a HUGE difference in one's final scores).

I don't really pay attention to the rules, just try keep the ball in game as long as possible and the score will go up eventually 😀
Once you start playing more often, you'll automatically start aiming as well. At least that's what I do. You just remember "if the ball comes down from there, hit the flipper at that point and it will go up there".
That said, in Balls of Steel that is a lot harder to do than in Epic Pinball. Mostly because BOS is like ten times faster. But it's easier to keep the ball in game, since the flippers are wider and the ball does not nearly as often drop down the center as it does in EP. Like in Android, when the ball comes down from the bumper area it often just falls inbetween the flippers and there's nothing you can do about it. Also in EP the slingshots often shoot it down the outer lanes in the blink of an eye. The Jill of the Jungle table is a good example of that.

rfnagel wrote:

jwt27 wrote:

I already found out.. I took some pictures of the screen at varying shutter speeds (multiples of 1/160s). At 1/80 I see two frames, 1/40 shows 4 frames, 1/25 shows 6, etc.. So yes, it IS drawing at 160fps 😀

Hey, that's a GREAT idea! 😀 I never thought of that before, but one thing I did remember... a buddy of mine used to FRAPS some of our Counter-Strike games, and he said that FRAPS would display what the actual framerate of the game was (although, the Half-Life GoldSource engine DOES already have a console command to display one's framerate).

FRAPS only works in 3D games, right? And I think BOS just uses DirectDraw or something, so that's probably not gonna work. But I could always try it, of course.

rfnagel wrote:

jwt27 wrote:

Wow! Who would have thought... 🤣

Hehe, yeah really, who would have thought... this from a company who sics their trademark lawyers like rapid dogs on most ANYONE who farts the wrong way!

I just thought.. could this be used as get-out-of-jail-free card if you ever get caught using a pirated copy of Windows? 🤣

rfnagel wrote:

jwt27 wrote:

Oh and something else... I hope IBM fired the guy who decided the shift keys on the Model M did not need stabilizing bars. 😒

Man... If I had a keyboard that didn't have those bars on the shift keys (or the spacebar and enter keys as well), mine would have fell off a LONG time ago 🤣!

I don't think they'd fall off anytime soon, but you have to hit the key exactly in the middle, it's much stiffer near the sides. I think I'd better remap the keybindings to use the letter keys, like S/L for the flippers and Q/P for side nudges. That places your thumbs closer to the spacebar as well. Too bad that's not possible in EP.

jwt27 wrote:

I don't really pay attention to the rules, just try keep the ball in game as long as possible and the score will go up eventually 😀 Once you start playing more often, you'll automatically start aiming as well. At least that's what I do. You just remember "if the ball comes down from there, hit the flipper at that point and it will go up there". That said, in Balls of Steel that is a lot harder to do than in Epic Pinball. Mostly because BOS is like ten times faster. But it's easier to keep the ball in game, since the flippers are wider and the ball does not nearly as often drop down the center as it does in EP. Like in Android, when the ball comes down from the bumper area it often just falls inbetween the flippers and there's nothing you can do about it. Also in EP the slingshots often shoot it down the outer lanes in the blink of an eye. The Jill of the Jungle table is a good example of that.

Thanks for the tips, I'll keep those in mind when I play again 😀 Although, I DO try to aim... it just never seems to go the way that I think that it will 🤣! And yeah, those "slingshots" really drive me nutz... not much you can do when the ball does that 🙁

jwt27 wrote:

FRAPS only works in 3D games, right? And I think BOS just uses DirectDraw or something, so that's probably not gonna work. But I could always try it, of course.

Yeah, I'm not sure if it will work or not. Doesn't hurt to try, though 😀

jwt27 wrote:

I just thought.. could this be used as get-out-of-jail-free card if you ever get caught using a pirated copy of Windows? 🤣

Hehe, maybe if you paid your lawyer(s) enough 🤣!

jwt27 wrote:

I don't think they'd fall off anytime soon, but you have to hit the key exactly in the middle, it's much stiffer near the sides. I think I'd better remap the keybindings to use the letter keys, like S/L for the flippers and Q/P for side nudges. That places your thumbs closer to the spacebar as well. Too bad that's not possible in EP.

You can't use DOSBox's key mapper to remap the keys for EP?

rfnagel wrote:

Thanks for the tips, I'll keep those in mind when I play again 😀 Although, I DO try to aim... it just never seems to go the way that I think that it will 🤣! And yeah, those "slingshots" really drive me nutz... not much you can do when the ball does that 🙁

Not pretending to be a pinball wizard here though 🤣 But that's just how I play it.

rfnagel wrote:

You can't use DOSBox's key mapper to remap the keys for EP?

I play the game on straight DOS, so no. Last time I tried it on DOSBox I just got a nice slideshow with no vsync. Might have to try it again though, as someone here pointed out I need to use a fixed cycle count. But I think my PC is just not up to it.

jwt27 wrote:

I play the game on straight DOS, so no. Last time I tried it on DOSBox I just got a nice slideshow with no vsync. Might have to try it again though, as someone here pointed out I need to use a fixed cycle count. But I think my PC is just not up to it.

Wow, I thought MINE was an antique 🤣!

That being said, I run all of the mentioned pinball games fluidly smooth on my current rig:

An Intel P4 2.666GHz CPU, 2GB RAM, ATI Radeon 9600 Pro with 256MB VRAM, Windows XP Professional with Service Pack 3 (and NO additional WinDoZe updates), DirectX v9.0c (IIRC), WinDoZe desktop resolution 800x600x32-bit, and a Gateway VX900 19" CRT monitor.

I have the following Windows XP environment variables set (sample registry file follows):

1Windows Registry Editor Version 5.00
2
3[HKEY_USERS\S-1-5-21-1214440339-507921405-682003330-1003\Environment]
4"SDL_AUDIODRIVER"="dsound"
5"SDL_VIDEODRIVER"="directx"

...and here is my custom DOSBox "DOSBox.conf" configuration file contents:

1# This is the configurationfile for DOSBox 0.74. (Please use the latest version of DOSBox)
2# Lines starting with a # are commentlines and are ignored by DOSBox.
3# They are used to (briefly) document the effect of each option.
4
5[sdl]
6#       fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back)
7#       fulldouble: Use double buffering in fullscreen. It can reduce screen flickering, but it can also result in a slow DOSBox.
8#   fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
9#                     Using your monitor's native resolution with aspect=true might give the best results.
10#                     If you end up with small window on a large screen, try an output different from surface.
11# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
12#                     (output=surface does not!)
13#           output: What video system to use for output.
14#                   Possible values: surface, overlay, opengl, openglnb, ddraw.
15#         autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)
16#      sensitivity: Mouse sensitivity.
17#      waitonerror: Wait before closing the console if dosbox has an error.
18#         priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized.
19#                     pause is only valid for the second entry.
20#                   Possible values: lowest, lower, normal, higher, highest, pause.
21#       mapperfile: File used to load/save the key/event mappings from. Resetmapper only works with the defaul value.
22#     usescancodes: Avoid usage of symkeys, might not work on all operating systems.
23
24fullscreen=true
25fulldouble=false
26fullresolution=original
27windowresolution=640x480
28output=overlay
29autolock=true
30sensitivity=250
31waitonerror=true
32priority=higher,normal
33mapperfile=Mapper.txt
34usescancodes=true
35
36[dosbox]
37# language: Select another language file.
38#  machine: The type of machine tries to emulate.
39#           Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
40# captures: Directory where things like wave, midi, screenshot get captured.
41#  memsize: Amount of memory DOSBox has in megabytes.
42#             This value is best left at its default to avoid problems with some games,
43#             though few games might require a higher value.
44#             There is generally no speed advantage when raising this value.
45
46language=DOSBox.lang
47machine=svga_s3
48captures=Capture
49memsize=16
50
51[render]
52# frameskip: How many frames DOSBox skips before drawing one.
53#    aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!.
54#    scaler: Scaler used to enlarge/enhance low resolution modes.
55#              If 'forced' is appended, then the scaler will be used even if the result might not be desired.
56#            Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.
57
58frameskip=0
59aspect=false
60scaler=normal2x

61
62[cpu]
63#      core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
64#            Possible values: auto, dynamic, normal, simple.
65#   cputype: CPU Type used in emulation. auto is the fastest choice.
66#            Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
67#    cycles: Amount of instructions DOSBox tries to emulate each millisecond.
68#            Setting this value too high results in sound dropouts and lags.
69#            Cycles can be set in 3 ways:
70#              'auto'          tries to guess what a game needs.
71#                              It usually works, but can fail for certain games.
72#              'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
73#                              (Example: fixed 4000).
74#              'max'           will allocate as much cycles as your computer is able to handle.
75#            
76#            Possible values: auto, fixed, max.
77#   cycleup: Amount of cycles to decrease/increase with keycombo.(CTRL-F11/CTRL-F12)
78# cycledown: Setting it lower than 100 will be a percentage.
79
80core=auto
81cputype=auto
82cycles=max
83cycleup=10
84cycledown=20
85
86[mixer]
87#   nosound: Enable silent mode, sound is still emulated though.
88#      rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
89#            Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
90# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
91#            Possible values: 1024, 2048, 4096, 8192, 512, 256.
92# prebuffer: How many milliseconds of data to keep on top of the blocksize.
93
94nosound=false
95rate=44100
96blocksize=1024
97prebuffer=20
98
99[midi]
100#     mpu401: Type of MPU-401 to emulate.
101#             Possible values: intelligent, uart, none.
102# mididevice: Device that will receive the MIDI data from MPU-401.
103#             Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
104# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use.
105#               See the README/Manual for more details.
106
107mpu401=none
108mididevice=none
109midiconfig=
110
111[sblaster]
112#  sbtype: Type of Soundblaster to emulate. gb is Gameblaster.
113#          Possible values: sb1, sb2, sbpro1, sbpro2, sb16, gb, none.
114#  sbbase: The IO address of the soundblaster.
115#          Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300.
116#     irq: The IRQ number of the soundblaster.
117#          Possible values: 7, 5, 3, 9, 10, 11, 12.
118#     dma: The DMA number of the soundblaster.
119#          Possible values: 1, 5, 0, 3, 6, 7.
120#    hdma: The High DMA number of the soundblaster.
121#          Possible values: 1, 5, 0, 3, 6, 7.
122# sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer.
123# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
124#          Possible values: auto, cms, opl2, dualopl2, opl3, none.
125#  oplemu: Provider for the OPL emulation. compat might provide better quality (see oplrate as well).
126#          Possible values: default, compat, fast.
127# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
128#          Possible values: 44100, 49716, 48000, 32000, 22050, 16000, 11025, 8000.
129
130sbtype=sb16
131sbbase=220
132irq=5
133dma=1
134hdma=5
135sbmixer=true
136oplmode=none
137oplemu=default
138oplrate=44100
139
140[gus]
141#      gus: Enable the Gravis Ultrasound emulation.
142#  gusrate: Sample rate of Ultrasound emulation.
143#           Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
144#  gusbase: The IO base address of the Gravis Ultrasound.
145#           Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
146#   gusirq: The IRQ number of the Gravis Ultrasound.
147#           Possible values: 5, 3, 7, 9, 10, 11, 12.
148#   gusdma: The DMA channel of the Gravis Ultrasound.
149#           Possible values: 3, 0, 1, 5, 6, 7.
150# ultradir: Path to Ultrasound directory. In this directory
151#           there should be a MIDI directory that contains
152#           the patch files for GUS playback. Patch sets used
153#           with Timidity should work fine.
154
155gus=true
156gusrate=44100
157gusbase=240
158gusirq=7
159gusdma=3
160ultradir=C:\ULTRASND
161
162[speaker]
163# pcspeaker: Enable PC-Speaker emulation.
164#    pcrate: Sample rate of the PC-Speaker sound generation.
165#            Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
166#     tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
167#            Possible values: auto, on, off.
168# tandyrate: Sample rate of the Tandy 3-Voice generation.
169#            Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
170#    disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).
171
172pcspeaker=true
173pcrate=44100
174tandy=off
175tandyrate=44100
176disney=false
177
178[joystick]
179# joysticktype: Type of joystick to emulate: auto (default), none,
180#               2axis (supports two joysticks),
181#               4axis (supports one joystick, first joystick used),
182#               4axis_2 (supports one joystick, second joystick used),
183#               fcs (Thrustmaster), ch (CH Flightstick).
184#               none disables joystick emulation.
185#               auto chooses emulation depending on real joystick(s).
186#               (Remember to reset dosbox's mapperfile if you saved it earlier)
187#               Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
188#        timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away).
189#     autofire: continuously fires as long as you keep the button pressed.
190#       swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks.
191#   buttonwrap: enable button wrapping at the number of emulated buttons.
192
193joysticktype=ch
194timed=true
195autofire=false
196swap34=true
197buttonwrap=false
198
199[serial]
200# serial1: set type of device connected to com port.
201#          Can be disabled, dummy, modem, nullmodem, directserial.
202#          Additional parameters must be in the same line in the form of
203#          parameter:value. Parameter for all types is irq (optional).
204#          for directserial: realport (required), rxdelay (optional).
205#                           (realport:COM1 realport:ttyS0).
206#          for modem: listenport (optional).
207#          for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
208#                         transparent, port, inhsocket (all optional).
209#          Example: serial1=modem listenport:5000
210#          Possible values: dummy, disabled, modem, nullmodem, directserial.
211# serial2: see serial1
212#          Possible values: dummy, disabled, modem, nullmodem, directserial.
213# serial3: see serial1
214#          Possible values: dummy, disabled, modem, nullmodem, directserial.
215# serial4: see serial1
216#          Possible values: dummy, disabled, modem, nullmodem, directserial.
217
218serial1=disabled
219serial2=disabled
220serial3=disabled
221serial4=disabled
222
223[dos]
224#            xms: Enable XMS support.
225#            ems: Enable EMS support.
226#            umb: Enable UMB support.
227# keyboardlayout: Language code of the keyboard layout (or none).
228
229xms=false
230ems=false
231umb=false
232keyboardlayout=auto
233
234[ipx]
235# ipx: Enable ipx over UDP/IP emulation.
236
237ipx=false
238
239[autoexec]
240# Lines in this section will be run at startup.
241# You can put your MOUNT lines here.
242@ECHO OFF
243MOUNT C C:\GAMES -FREESIZE 1000
244VER SET 7 10
245SET PATH=C:\;C:\DOS;C:\FED;GM_RESET;C:\NC;C:\NE;C:\NU;C:\PATH;C:\PKZIP;C:\TEMP;Z:\
246SET TEMP=C:\TEMP
247SET TMP=C:\TEMP
248C:

why do you use normal2x together with
windowresolution=640x480
output=overlay

And why do you use windowresolution=640x480 at all? for shrinking?

robertmo wrote:

why do you use normal2x together with windowresolution=640x480 output=overlay […]
Show full quote

why do you use normal2x together with
windowresolution=640x480
output=overlay

And why do you use windowresolution=640x480 at all? for shrinking?

I guess because the game is in 320x240, scaled x2 = 640x480 ?

rfnagel wrote:

Wow, I thought MINE was an antique 🤣!

That being said, I run all of the mentioned pinball games fluidly smooth on my current rig:

An Intel P4 2.666GHz CPU, 2GB RAM, ATI Radeon 9600 Pro with 256MB VRAM, Windows XP Professional with Service Pack 3 (and NO additional WinDoZe updates), DirectX v9.0c (IIRC), WinDoZe desktop resolution 800x600x32-bit, and a Gateway VX900 19" CRT monitor.

My system is more or less the same 🤣 I should be able to run it then.

And... can you really live with 800x600 as desktop resolution? 😳

robertmo wrote:

why do you use normal2x together with windowresolution=640x480 output=overlay And why do you use windowresolution=640x480 at […]
Show full quote

why do you use normal2x together with
windowresolution=640x480
output=overlay
And why do you use windowresolution=640x480 at all? for shrinking?

Basically, what Jwt27 replied. Anyhow, I don't normally play these games in a window, but my previously posted config gives me the closest look and "feel" to the original game(s).

If (on the slim chance) I decide to play the game in a window, the same holds true... it looks and "feels" the same, without any graphics smoothing and such.

Oh, and I use "overlay" MOSTLY because I seem to get a little better framerate in most ALL of my DOS games.

jwt27 wrote:

My system is more or less the same 🤣 I should be able to run it then.

Most definitely 😀 BTW, other than a few games (such as the Epic MegaGames pinball games), I have a similar *SINGLE* DOSBox config that I run ALMOST ANYTHING with fairly well.

Just for the curious, my *NORMAL* "DOSBox.conf" that I runs just about ANYTHING that I throw at it quite well...

Windows XP environment variables set (sample registry file follows):

1Windows Registry Editor Version 5.00
2
3[HKEY_USERS\S-1-5-21-1214440339-507921405-682003330-1003\Environment]
4"SDL_AUDIODRIVER"="dsound"
5"SDL_VIDEODRIVER"="directx"

...and here is my *NORMAL* DOSBox "DOSBox.conf" configuration file contents (runs damned near anything GREAT):

1# This is the configurationfile for DOSBox 0.74. (Please use the latest version of DOSBox)
2# Lines starting with a # are commentlines and are ignored by DOSBox.
3# They are used to (briefly) document the effect of each option.
4
5[sdl]
6#       fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back)
7#       fulldouble: Use double buffering in fullscreen. It can reduce screen flickering, but it can also result in a slow DOSBox.
8#   fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
9#                     Using your monitor's native resolution with aspect=true might give the best results.
10#                     If you end up with small window on a large screen, try an output different from surface.
11# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
12#                     (output=surface does not!)
13#           output: What video system to use for output.
14#                   Possible values: surface, overlay, opengl, openglnb, ddraw.
15#         autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)
16#      sensitivity: Mouse sensitivity.
17#      waitonerror: Wait before closing the console if dosbox has an error.
18#         priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized.
19#                     pause is only valid for the second entry.
20#                   Possible values: lowest, lower, normal, higher, highest, pause.
21#       mapperfile: File used to load/save the key/event mappings from. Resetmapper only works with the defaul value.
22#     usescancodes: Avoid usage of symkeys, might not work on all operating systems.
23
24fullscreen=true
25fulldouble=false
26# fullresolution=original
27fullresolution=desktop
28# windowresolution=original
29windowresolution=640x480
30# output=surface
31output=overlay
32autolock=true
33sensitivity=250
34waitonerror=true
35# priority=highest,highest
36priority=higher,normal
37mapperfile=Mapper.txt
38usescancodes=true
39
40[dosbox]
41# language: Select another language file.
42#  machine: The type of machine tries to emulate.
43#           Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
44# captures: Directory where things like wave, midi, screenshot get captured.
45#  memsize: Amount of memory DOSBox has in megabytes.
46#             This value is best left at its default to avoid problems with some games,
47#             though few games might require a higher value.
48#             There is generally no speed advantage when raising this value.
49
50language=DOSBox.lang
51machine=svga_s3
52captures=Capture
53# memsize=16
54memsize=31
55
56[render]
57# frameskip: How many frames DOSBox skips before drawing one.
58#    aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!.
59#    scaler: Scaler used to enlarge/enhance low resolution modes.
60#              If 'forced' is appended, then the scaler will be used even if the result might not be desired.

61#            Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.
62
63frameskip=0
64# aspect=false
65aspect=true
66# scaler=normal2x
67scaler=normal3x
68
69[cpu]
70#      core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
71#            Possible values: auto, dynamic, normal, simple.
72#   cputype: CPU Type used in emulation. auto is the fastest choice.
73#            Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
74#    cycles: Amount of instructions DOSBox tries to emulate each millisecond.
75#            Setting this value too high results in sound dropouts and lags.
76#            Cycles can be set in 3 ways:
77#              'auto'          tries to guess what a game needs.
78#                              It usually works, but can fail for certain games.
79#              'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
80#                              (Example: fixed 4000).
81#              'max'           will allocate as much cycles as your computer is able to handle.
82#            
83#            Possible values: auto, fixed, max.
84#   cycleup: Amount of cycles to decrease/increase with keycombo.(CTRL-F11/CTRL-F12)
85# cycledown: Setting it lower than 100 will be a percentage.
86
87core=auto
88cputype=auto
89# cycles=auto
90cycles=max
91cycleup=10
92cycledown=20
93
94[mixer]
95#   nosound: Enable silent mode, sound is still emulated though.
96#      rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
97#            Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
98# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
99#            Possible values: 1024, 2048, 4096, 8192, 512, 256.
100# prebuffer: How many milliseconds of data to keep on top of the blocksize.
101
102nosound=false
103rate=44100
104blocksize=1024
105prebuffer=20
106
107[midi]
108#     mpu401: Type of MPU-401 to emulate.
109#             Possible values: intelligent, uart, none.
110# mididevice: Device that will receive the MIDI data from MPU-401.
111#             Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
112# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use.
113#               See the README/Manual for more details.
114
115mpu401=intelligent
116mididevice=default
117midiconfig=
118
119[sblaster]
120#  sbtype: Type of Soundblaster to emulate. gb is Gameblaster.
121#          Possible values: sb1, sb2, sbpro1, sbpro2, sb16, gb, none.
122#  sbbase: The IO address of the soundblaster.
123#          Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300.
124#     irq: The IRQ number of the soundblaster.
125#          Possible values: 7, 5, 3, 9, 10, 11, 12.
126#     dma: The DMA number of the soundblaster.
127#          Possible values: 1, 5, 0, 3, 6, 7.
128#    hdma: The High DMA number of the soundblaster.
129#          Possible values: 1, 5, 0, 3, 6, 7.
130# sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer.
131# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
132#          Possible values: auto, cms, opl2, dualopl2, opl3, none.
133#  oplemu: Provider for the OPL emulation. compat might provide better quality (see oplrate as well).
134#          Possible values: default, compat, fast.
135# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
136#          Possible values: 44100, 49716, 48000, 32000, 22050, 16000, 11025, 8000.
137
138sbtype=sb16
139sbbase=220
140# irq=7
141irq=5
142dma=1
143hdma=5
144sbmixer=true
145oplmode=auto
146oplemu=default
147oplrate=44100
148
149[gus]
150#      gus: Enable the Gravis Ultrasound emulation.
151#  gusrate: Sample rate of Ultrasound emulation.
152#           Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
153#  gusbase: The IO base address of the Gravis Ultrasound.
154#           Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
155#   gusirq: The IRQ number of the Gravis Ultrasound.
156#           Possible values: 5, 3, 7, 9, 10, 11, 12.
157#   gusdma: The DMA channel of the Gravis Ultrasound.
158#           Possible values: 3, 0, 1, 5, 6, 7.
159# ultradir: Path to Ultrasound directory. In this directory
160#           there should be a MIDI directory that contains
161#           the patch files for GUS playback. Patch sets used
162#           with Timidity should work fine.
163
164gus=true
165gusrate=44100
166gusbase=240
167# gusirq=5
168gusirq=7
169gusdma=3
170ultradir=C:\ULTRASND
171
172[speaker]
173# pcspeaker: Enable PC-Speaker emulation.
174#    pcrate: Sample rate of the PC-Speaker sound generation.
175#            Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
176#     tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
177#            Possible values: auto, on, off.
178# tandyrate: Sample rate of the Tandy 3-Voice generation.
179#            Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
180#    disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).
181
182pcspeaker=true
183pcrate=44100
184tandy=auto
185tandyrate=44100
186disney=true
187
188[joystick]
189# joysticktype: Type of joystick to emulate: auto (default), none,
190#               2axis (supports two joysticks),
191#               4axis (supports one joystick, first joystick used),
192#               4axis_2 (supports one joystick, second joystick used),
193#               fcs (Thrustmaster), ch (CH Flightstick).
194#               none disables joystick emulation.
195#               auto chooses emulation depending on real joystick(s).
196#               (Remember to reset dosbox's mapperfile if you saved it earlier)
197#               Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
198#        timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away).
199#     autofire: continuously fires as long as you keep the button pressed.
200#       swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks.
201#   buttonwrap: enable button wrapping at the number of emulated buttons.
202
203joysticktype=ch
204timed=true
205autofire=false
206swap34=true
207# buttonwrap=true
208buttonwrap=false
209
210[serial]
211# serial1: set type of device connected to com port.
212#          Can be disabled, dummy, modem, nullmodem, directserial.
213#          Additional parameters must be in the same line in the form of
214#          parameter:value. Parameter for all types is irq (optional).
215#          for directserial: realport (required), rxdelay (optional).
216#                           (realport:COM1 realport:ttyS0).
217#          for modem: listenport (optional).
218#          for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
219#                         transparent, port, inhsocket (all optional).
220#          Example: serial1=modem listenport:5000
221#          Possible values: dummy, disabled, modem, nullmodem, directserial.
222# serial2: see serial1
223#          Possible values: dummy, disabled, modem, nullmodem, directserial.
224# serial3: see serial1
225#          Possible values: dummy, disabled, modem, nullmodem, directserial.
226# serial4: see serial1
227#          Possible values: dummy, disabled, modem, nullmodem, directserial.
228
229serial1=directserial realport:com1
230serial2=dummy
231serial3=disabled
232serial4=disabled
233
234[dos]
235#            xms: Enable XMS support.
236#            ems: Enable EMS support.
237#            umb: Enable UMB support.
238# keyboardlayout: Language code of the keyboard layout (or none).
239
240xms=true
241ems=true
242umb=true
243keyboardlayout=auto
244
245[ipx]
246# ipx: Enable ipx over UDP/IP emulation.
247
248ipx=true
249
250[autoexec]
251# Lines in this section will be run at startup.
252# You can put your MOUNT lines here.
253@ECHO OFF
254# MIXER MASTER 75:75
255MOUNT C C:\GAMES -FREESIZE 1000
256# VER SET 5 0
257VER SET 7 10
258SET PATH=C:\;C:\DOS;C:\FED;C:\GM_RESET;C:\NC;C:\NE;C:\NU;C:\PATH;C:\PKZIP;C:\TEMP;Z:\
259SET TEMP=C:\TEMP
260SET TMP=C:\TEMP
261C:
262CLS

jwt27 wrote:

And... can you really live with 800x600 as desktop resolution? 😳

Hehe, these old aging 51+ year old eyes have a helluva time seeing the WinDoZe desktop at anything higher on this old 19" CRT monitor 🤣!

P.S. Been using 800x600x32-bit (or 24-bit, depending on video card) since 1995 with Windows 3.11 WFWG (re: http://jasonwilliams400com.startlogic.com/sno … _486DX4-100.htm ) 😀

"You can't teach an old dog new tricks!"

🤣!

BTW, just a heads-up:

A few more games that have been recently added to CyberScore, requested by your's truly:

Bejeweled Twist -> http://www.cyberscore.me.uk/game/1275

The *ORIGINAL* Epic Pinball shareware table, "Android" (*NOT* to be confused with newer "Super Android") -> http://www.cyberscore.me.uk/chart/160819

Recently requested, but not added yet:

Bejeweled Deluxe - The original version for PC.
Bejeweled Blitz - The PC Windows version of the popular Facebook game.
Bejeweled 2 Deluxe - Additional scoreboards for the unlockable game modes.

(Edit) P.S. Detailed information about the differences of the "Android" and "Super Android" pinball tables here -> http://www.cyberscore.me.uk/forum/index.php?topic=3626.0 , and more discussion here -> http://www.cyberscore.me.uk/forum/index.php?topic=3638.0 .

And... download the *ORIGINAL* version of the "Android" pinball table ("0pinball.zip") here -> ftp://ftp.princeton.edu/pub/clk/pc/dos/games/0pinball.zip , or here -> http://cd.textfiles.com/ems/emspro20/disk4/GA … ES/0PINBALL.ZIP 😀