VOGONS


Quicktime in Windows 3.1

Topic actions

Reply 40 of 54, by Riverwolf

User metadata
Rank Newbie
Rank
Newbie
Dominus wrote:

Did you do anything else to the dosbox.conf?

In this particular experiment, no.

I'll go ahead and post my .conf settings(as they are after the experiment):

# This is the configurationfile for DOSBox 0.74. (Please use the latest version of DOSBox) # Lines starting with a # are comment […]
Show full quote

# 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=true
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=simple
cputype=386_slow
cycles=14000
cycleup=500
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=true
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.

Reply 41 of 54, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

those [cpu] settings are not the default.

Water flows down the stream
How to ask questions the smart way!

Reply 42 of 54, by Riverwolf

User metadata
Rank Newbie
Rank
Newbie
Qbix wrote:

those [cpu] settings are not the default.

The cores and cputypes were originally set to auto; I changed them at an earlier recommendation.

Do you think changing the cycles around might help?

Reply 43 of 54, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

if it works for others and not for you, then I can only think that the version of the files you are trying to install are different.

Water flows down the stream
How to ask questions the smart way!

Reply 44 of 54, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

I cannot reproduce this at all. I just made sure to run a (pretty) pristine US Windows 3.1 install (not WfW 3.11). Tried with your conf (just reset the [cpu] section and disabled fullscreen) and Quicktime installer for 2.1.2. Installed fine without a problem and reported that it successfully installed and the sample played. I even tried to mess with it by not setting Windows in the PATH.

I can only recommend yet another installation of windows 3.1 following the guide Windows 3.1x DOSBox Guide to the letter. And don't do ANY tweaking unless mentioned in the guide. No dosbox.conf tweak, no Windows 3.1 tweak...

I'm attaching the installer that does work for me.

Reply 45 of 54, by Riverwolf

User metadata
Rank Newbie
Rank
Newbie
Dominus wrote:

I cannot reproduce this at all. I just made sure to run a (pretty) pristine US Windows 3.1 install (not WfW 3.11). Tried with your conf (just reset the [cpu] section and disabled fullscreen) and Quicktime installer for 2.1.2. Installed fine without a problem and reported that it successfully installed and the sample played. I even tried to mess with it by not setting Windows in the PATH.

I can only recommend yet another installation of windows 3.1 following the guide Windows 3.1x DOSBox Guide to the letter. And don't do ANY tweaking unless mentioned in the guide. No dosbox.conf tweak, no Windows 3.1 tweak...

I'm attaching the installer that does work for me.

Okay, I tried to follow the steps as best they were. However, before I tried to install Quicktime, I get this message after installing the sound blaster driver whenever I start Windows up:

"One of the library files needed to run this application is damaged. Please reinstall this application."

The thing is, the trumpet fanfare still plays okay. But that may be the culprit. The message had been popping up before, but I thought it was referring to Quicktime, not sound blaster.

Reply 47 of 54, by Riverwolf

User metadata
Rank Newbie
Rank
Newbie
Dominus wrote:

Have you installed the SB drivers the guide provides or different ones?

The one the guide provides.

Reply 48 of 54, by Riverwolf

User metadata
Rank Newbie
Rank
Newbie

I should point out an odd hiccup when I installed the S3 video driver. As before, I have to run the "Setup" from Windows itself (if I try to run it from DOSBox, I get the install program instead.) When I tried to install the S3 card, it seems to go okay, but then it says to insert a disk or type in the path the files are in. The "c:\drivers\s3" is automatically typed in, as I typed it in before that just before installing, which worked fine, but now when I press the "ok", literally nothing happens. I have to exit setup. However, the drivers are now available, so I can select any one of them at my leisure. I'm not sure what that's about.

Reply 49 of 54, by Davros

User metadata
Rank l33t
Rank
l33t

are you supposed to run setup from dosbox ?
when you say you get the install program instead, what install program ?

Guardian of the Sacred Five Terabyte's of Gaming Goodness

Reply 50 of 54, by Riverwolf

User metadata
Rank Newbie
Rank
Newbie
Davros wrote:

are you supposed to run setup from dosbox ?
when you say you get the install program instead, what install program ?

The one that installs Windows 3.1. According to the guide, it shouldn't be that program; it should just be a "similar".

Reply 51 of 54, by Davros

User metadata
Rank l33t
Rank
l33t

if you follow the guide the windows 3.1 setup installs the s3 drivers you shouldnt be trying to installing them again

Guardian of the Sacred Five Terabyte's of Gaming Goodness

Reply 52 of 54, by Riverwolf

User metadata
Rank Newbie
Rank
Newbie
Davros wrote:

if you follow the guide the windows 3.1 setup installs the s3 drivers you shouldnt be trying to installing them again

Huh?

The guide details how to install 3.1, but how to install s3 is later, and seems to indicate that Windows needs to be installed already. The default driver is VGA, and the screenshots in the guide indicate this, as well.

Are you saying I should install the S3 drivers at the same time as installing Windows?

Reply 53 of 54, by Davros

User metadata
Rank l33t
Rank
l33t
Riverwolf wrote:

The "c:\drivers\s3" is automatically typed in, as I typed it in before that just before installing,

what do you mean you typed it in before ?
according to the guide you only type it in once

Guardian of the Sacred Five Terabyte's of Gaming Goodness

Reply 54 of 54, by Riverwolf

User metadata
Rank Newbie
Rank
Newbie
Davros wrote:
Riverwolf wrote:

The "c:\drivers\s3" is automatically typed in, as I typed it in before that just before installing,

what do you mean you typed it in before ?
according to the guide you only type it in once

When I first run Setup and choose to select to install the driver from a folder, I type in the address and hit "okay". Everything seems to be going okay so far. Then, when I try to pick an actual setting, it once again asks for the disk or directory, and for some reason, the "c:\drivers\s3" directory doesn't work anymore; I hit "okay" and the screen doesn't go away. I close the installer, restart windows, and I can still select any of the S3 video modes.