DOS Games Message Board
DOS Games Discussion
A message board to talk about DOS games, get help, and find old games.
Do NOT post warez or abandonware requests please
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
NEW! DOSGames.com has been massively upgraded to v2.0 with TONS of new features!
Check out the new design and dozens of new features including online play!


Merlin [Win7 64]

 
Post new topic   Reply to topic    DOS Games Discussion Forum Index -> Get Games to Work
Author Message
Guest







PostPosted: Wed Nov 28, 2012 2:47 am     Post subject: Merlin [Win7 64] Reply with quote

cheak out the post in looking for old games "merlin 1992 version" Happy id post a link but it wont let me.

i need help id LOVE to play this game again but i have NO idea on how to get it to work. i have downloaded it and "extracted" file from winrar.

my computers a 64bit windows 7.

and please in non computer language Happy i know basic things.

thanks in advance.

Benevolent
Back to top
dosraider
Admin
Admin


Offline
Joined: 15 Mar 2005
Posts: 9245
Location: ROTFLMAO in Belgium.

PostPosted: Wed Nov 28, 2012 3:17 am     Post subject: Reply with quote

Edited your topic's tittle to something understandable ......
It's about this one:
http://www.dosgames.com/forum/viewtopic.php?t=12629


As you're on Win7 64 your options are rather limited, the game itself will not run directly on it.
Your options as far as I see it:

dosraider wrote:
Is a Win3.x game.

Your possibilities if it can't run directly on your OS:
-> Dosbox 0.74 + Win3.x
-> VPC2007 + Dos/Win3.x
-> VPC2007 + W98(SE)


You also could try XPmode, depends what license you have, but XP mode isn't really suited to run those ol'games.

If you don't understand any of those:
-> Dosbox 0.74 + Win3.x
-> VPC2007 + Dos/Win3.x
-> VPC2007 + W98(SE)
Then you're in a hell of a ride to get things working.

For dosbox it starts there:
Win7+dosbox 0.74
Plus you'll need Win3.x, you can get it from AB
Windows 3.11 for DOSBox, ready-to-run

For VPC it's there:
Win7 64 /VPC2007

Tale your pick, both are working for Merlin.

As I said, if you're an absolute beginner (as implicated by your questions....), you have picked a pretty complicated game to get to run on your modern OS, but on the other hand, once you know what to do, you'll be able to run all old dosgames (dosbox) or Win3/W9x games(VPC).
Maybe it wouldn't be a bad idea to ask for some help on the spot from someone that knows a bit more of those matters.

If you want to do it yourself I would advise dosbox/Win3, and I'll be glad to help you, maybe register on the forum, will make things easier.

Also:
Anonymous wrote:
.....and please in non computer language Happy i know basic things.

Eeeuuurrrhhhh ..... I can try to keep things simple, but there will be 'computer language", as you'll need to set up correctly an emulator(dosbox) or a Virtual VM(VPC). Those things will ask some effort from you.
Those softs aren't meant to be 'user friendly' but are meant for peeps with at least some basic compy skills. But it's doable even for absolute beginners. (Also known as n00bs ... . Laughing )
Back to top
Guest







PostPosted: Thu Nov 29, 2012 5:21 am     Post subject: Reply with quote

ok well i have downloaded the dosbox and changed the settings for it to mount the files it needs .... but im kind of confused about the next part.
Back to top
dosraider
Admin
Admin


Offline
Joined: 15 Mar 2005
Posts: 9245
Location: ROTFLMAO in Belgium.

PostPosted: Thu Nov 29, 2012 6:43 am     Post subject: Reply with quote

Next you will need this:
dosraider wrote:

Plus you'll need Win3.x, you can get it from AB
Windows 3.11 for DOSBox, ready-to-run

Unpack everything in your \oldgames\
Be sure to keep the folder structure intact.

Next unpack the merlin folder on your \oldgames\

Run dosbox and input windows
If (and only then!) you have doen it all as it should be Win3 will run.
Don't mind the wallpaper, you're in Win3.

And here you're in the ol'windows, go to
main -> file manager -> merlin and double click merlin.exe

Back to top
energizer
Guest






PostPosted: Thu Jul 31, 2014 4:33 pm     Post subject: Reply with quote

Old thread, I know. But I've been on a bit of a nostalgia trip lately and I have fond memories of playing this.

I'm completely new to DOSBox, however. (For everything else, I've been using a Win98 VM, but VMWare Fusion doesn't seem to have the ability to emulate the lovely internal "beeper" speaker tones that this game uses, so I tried the DOSBox with 3.11)

The game opens just fine and plays its "loading" tune, but the second the game finishes loading, DOSBox just crashes.

Does DOSBox have any sort of crash log? Or something that would actually make the problem identifiable?
Back to top
MrFlibble
Demoniac Demo maniac
Demoniac Demo maniac


Offline
Joined: 05 Dec 2010
Posts: 2443

PostPosted: Fri Aug 01, 2014 12:58 pm     Post subject: Reply with quote

energizer wrote:
Does DOSBox have any sort of crash log? Or something that would actually make the problem identifiable?

If this error is reproducible, you should post your system specs and the contents of your DOSBox configuration file.
Back to top
energizer
Guest






PostPosted: Fri Aug 01, 2014 6:52 pm     Post subject: Reply with quote

I'm working on a MacBook Pro 9,1
Code:
Processor Name:   Intel Core i7
  Processor Speed:   2.6 GHz
  Number of Processors:   1
  Total Number of Cores:   4
  L2 Cache (per Core):   256 KB
  L3 Cache:   6 MB
  Memory:   8 GB
  Boot ROM Version:   MBP91.00D3.B08
  SMC Version (system):   2.1f175

  Graphics:
    Built-in: Intel HD Graphics 4000
    Discrete: NVidia GeForce GT 650M
                      VRAM (Total):   1024 MB


Like I said, this is a new installation of DOSBox, so the config file should be stock (I haven't even bothered to add autoexec lines to launch Win3.11 yet).
But I'll still post the contents:
Code:
# 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.
#         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=original
windowresolution=original
output=surface
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper-0.74.map
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=16

[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=false
scaler=normal2x

[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=auto
cycleup=10
cycledown=20

[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=false
gusrate=44100
gusbase=240
gusirq=5
gusdma=3
ultradir=C:\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=true
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.


Back to top
energizer
Guest






PostPosted: Fri Aug 01, 2014 7:13 pm     Post subject: Reply with quote

Oh, yes, haha. OSX version 10.9.4
Back to top
energizer
Guest






PostPosted: Fri Sep 05, 2014 8:44 am     Post subject: Reply with quote

bump
Back to top
Display posts from previous:   
Post new topic   Reply to topic    DOS Games Discussion Forum Index -> Get Games to Work All times are GMT - 5 Hours
Page 1 of 1

 


Powered by phpBB © 2001, 2005 phpBB Group and Ask an Expert
Also powered by Darren and the other admin and mods' hard work! ;)