Pandora with Dosbox

So you do not have a "dosbox.conf" inside your C:\Program Files\DOSBox-0.72 folder?
A sansGUI interface is one that does not have the small features called "Windows". The term comes from the French word sans, meaning "without".

SansGUI's are more typically used in Unix-like Operating Systems. The conventional wisdom is that a GUI (Grapical User Interface) help guide the casual computer user to perform routine tasks with Point and Click simplicity. SansGUI's have acquired considerable acceptance for users accustomed to the CLI (Command Line Interface).
When you're inside of Dosbox looking at all of the files, how do you have it set up to View???

While you have Dosbox open looking at the Files go up to the Top and click on the View button and select the "Details" option... Then under TYPE for the files names look for the CONF type of file, there is only ONE, it should be titled dosbox in lower case letters... And it should only be about 8 KB in size...
The Paved Straight Road, Won't Always Get You Farther Than The Winding Dirt Road...


Can You Run Your Game??? Click Here And Find Out...

*Note, Not All Games Have Been Tested & Therefore May Not Be Listed...
I redownloaded it from Nilo and this time found it! So again followed your instructions but again it was a no go - cannot use past feature.

So I went ahead and using the config file within dosbox that I downloaded from Nilo, I modifed it re your instructions.

Now I get a red message on the first screen that says it is not recommended that C:\ drive be mounted. Not sure what that means.

After modifing config file within dosbox from nilo tried again to start the game but again no go.
ipx=false

[autoexec]
# Lines in this section will be run at startup.
mount D D:\ -t cdrom -usecd 0 -ioctl
mount E E:\ -t cdrom -usecd 0 -ioctl

mount C C:\
C:

This is what is in the config file opened by notepad. Might there be a very special way to modify this in order to obtain the paste feature for DosBox?
Okay, you have a CONF file in Dosbox now and a Config file in Pandora... Right???


Pandora Config File wrote: [DIGI_CONFIG]
BoardNum=1
IoAddr=0x220
DMA=1
Int=7
Volume=100
ReverseStereo=No

[MIDI_CONFIG]
BoardNum=12
IoAddr=0x330
DigiDrums=Yes
Volume=30

[SYSTEM]
LastPlayer=MICHAEL
Pass=1
ChainInt8=Yes
ChainInt1C=Yes
WinMemReserve=0
Label=PANDORA

[PREF]
Hints=Off
Captioning=On
WalkingSpeed=Fast
MouseSens=Med
TiltCntrl=Norm
WindowSize=7
Rendering=High
Auto428x324=On
CyberMouse=Off
MPEG=Off
ForceScaling=Off

[VIDEO]
Univesa=Off
TransferRate=83967
DirectDrive=0
VGALetterBox=Off
Brightness=3
ScreenColor=2

[CD_MAP]
Disk1=E
Disk2=E
Disk3=E
Disk4=E
Disk5=E
Disk6=E

Copy and paste that into your Pandora Config File...

Dosbox CONF File wrote: # This is the configurationfile for DOSBox 0.72.
# Lines starting with a # are commentlines.
# They are used to (briefly) document the effect of each option.

[sdl]
# fullscreen -- Start dosbox directly in fullscreen.
# fulldouble -- Use double buffering in fullscreen.
# fullresolution -- What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# windowresolution -- Scale the window to this size IF the output device supports hardware scaling.
# output -- What to use for output: surface,overlay,opengl,openglnb,ddraw.
# autolock -- Mouse will automatically lock, if you click on the screen.
# sensitiviy -- Mouse sensitivity.
# waitonerror -- Wait before closing the console if dosbox has an error.
# priority -- Priority levels for dosbox: lowest,lower,normal,higher,highest,pause (when not focussed).
# Second entry behind the comma is for when dosbox is not focused/minimized.
# mapperfile -- File used to load/save the key/event mappings from.
# 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.txt
usescancodes=true

[dosbox]
# language -- Select another language file.
# memsize -- Amount of memory DOSBox has in megabytes.
# machine -- The type of machine tries to emulate:hercules,cga,tandy,pcjr,vga.
# captures -- Directory where things like wave,midi,screenshot get captured.

language=
machine=vga
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.
# Supported are none,normal2x,normal3x,advmame2x,advmame3x,hq2x,hq3x,
# 2xsai,super2xsai,supereagle,advinterp2x,advinterp3x,
# tv2x,tv3x,rgb2x,rgb3x,scan2x,scan3x.
# If forced is appended (like scaler=hq2x forced), the scaler will be used
# even if the result might not be desired.

frameskip=0
aspect=false
scaler=normal2x

[cpu]
# core -- CPU Core used in emulation: normal,simple,dynamic,auto.
# auto switches from normal to dynamic if appropriate.
# cycles -- Amount of instructions DOSBox tries to emulate each millisecond.
# Setting this value too high results in sound dropouts and lags.
# You can also let DOSBox guess the correct value by setting it to max.
# The default setting (auto) switches to max if appropriate.
# cycleup -- Amount of cycles to increase/decrease with keycombo.
# cycledown Setting it lower than 100 will be a percentage.

core=auto
cycles=auto
cycleup=500
cycledown=20

[mixer]
# nosound -- Enable silent mode, sound is still emulated though.
# rate -- Mixer sample rate, setting any devices higher than this will
# probably lower their sound quality.
# blocksize -- Mixer block size, larger blocks might help sound stuttering
# but sound will also be more lagged.
# prebuffer -- How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=22050
blocksize=2048
prebuffer=10

[midi]
# mpu401 -- Type of MPU-401 to emulate: none, uart or intelligent.
# device -- Device that will receive the MIDI data from MPU-401.
# This can be default,alsa,oss,win32,coreaudio,none.
# config -- Special configuration options for the device. In Windows put
# the id of the device you want to use. See README for details.

mpu401=intelligent
device=default
config=

[sblaster]
# sbtype -- Type of sblaster to emulate:none,sb1,sb2,sbpro1,sbpro2,sb16.
# sbbase,irq,dma,hdma -- The IO/IRQ/DMA/High DMA address of the soundblaster.
# mixer -- Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode -- Type of OPL emulation: auto,cms,opl2,dualopl2,opl3.
# On auto the mode is determined by sblaster type.
# All OPL modes are 'Adlib', except for CMS.
# oplrate -- Sample rate of OPL music emulation.

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
mixer=true
oplmode=auto
oplrate=22050

[gus]
# gus -- Enable the Gravis Ultrasound emulation.
# gusbase,irq1,irq2,dma1,dma2 -- The IO/IRQ/DMA addresses of the
# Gravis Ultrasound. (Same IRQ's and DMA's are OK.)
# gusrate -- Sample rate of Ultrasound emulation.
# 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=22050
gusbase=240
irq1=5
irq2=5
dma1=3
dma2=3
ultradir=C:\ULTRASND

[speaker]
# pcspeaker -- Enable PC-Speaker emulation.
# pcrate -- Sample rate of the PC-Speaker sound generation.
# tandy -- Enable Tandy Sound System emulation (off,on,auto).
# For auto Tandysound emulation is present only if machine is set to tandy.
# tandyrate -- Sample rate of the Tandy 3-Voice generation.
# disney -- Enable Disney Sound Source emulation. Covox Voice Master and Speech Thing compatible.

pcspeaker=true
pcrate=22050
tandy=auto
tandyrate=22050
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).
# timed -- enable timed intervals for axis. (false is old style behaviour).
# 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=true

[serial]
# serial1-4 -- 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.
# for directserial: realport (required), rxdelay (optional).
# for modem: listenport (optional).
# for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
# transparent, port, inhsocket (all optional).
# Example: serial1=modem listenport:5000

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=none

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

ipx=false

[autoexec]
# Lines in this section will be run at startup.
mount D D:\ -t cdrom -usecd 0 -ioctl
mount E E:\ -t cdrom -usecd 0 -ioctl

mount C C:\
C:
Copy and Paste this to your Dosbox CONF file...


These are copied right out of mine and I've been running fairly smoothly for 2 months... See if that does anything for you...
The Paved Straight Road, Won't Always Get You Farther Than The Winding Dirt Road...


Can You Run Your Game??? Click Here And Find Out...

*Note, Not All Games Have Been Tested & Therefore May Not Be Listed...
So I went ahead and using the config file within dosbox that I downloaded from Nilo, I modifed it re your instructions.

Now I get a red message on the first screen that says it is not recommended that C:\ drive be mounted. Not sure what that means.
I emailed Nilo about that warning message awhile back. The message CAN be ignored. It is there merely as a guideline that you shouldn't use the root of your hard drive to install or play games as the DOSBox environment will simulate any folder you declare in the config file as root.

After modifing config file within dosbox from nilo tried again to start the game but again no go.
Are your hard drives still C: and D:?
Do you still have two CD drives (E: and F:)?
Is E: still the possibly bad drive?
A sansGUI interface is one that does not have the small features called "Windows". The term comes from the French word sans, meaning "without".

SansGUI's are more typically used in Unix-like Operating Systems. The conventional wisdom is that a GUI (Grapical User Interface) help guide the casual computer user to perform routine tasks with Point and Click simplicity. SansGUI's have acquired considerable acceptance for users accustomed to the CLI (Command Line Interface).
Oh yeah, I forgot about the Possibly BAD CD/DVD Drive... If your E: drive is going bad or is already bad, then my Config and CONF files won't work for you, you'll have to change the Mounting of the CDROM to F:...
The Paved Straight Road, Won't Always Get You Farther Than The Winding Dirt Road...


Can You Run Your Game??? Click Here And Find Out...

*Note, Not All Games Have Been Tested & Therefore May Not Be Listed...
No Bafitis your suggestion did not work - sorry. So now where are we at? Are you both saying my E drive may be bad - needs replacing? Have had no other problems with it re game playing so far or even with burning.

Yes I have a C and D hard drives
And have E and F CDRom drives
E is CD and F is DVD
Gee if you guys/gals are back East it must be terribly late for you. I am beginning to get buggy eyed out here on the west coast. Shall we layoff until tomorrow and tackle it all again? Sorry to be such a problem here. Must be frustrating for you both.
Edit the dosbos [autoexec] section like this

Code: Select all

[autoexec]
# Lines in this section will be run at startup.
mount E E:\ -t cdrom -usecd 0 -ioctl
mount F F:\ -t cdrom -usecd 0 -ioctl
mount C C:\
mount D D:\
C:
Save and exit.

Try the game again.
A sansGUI interface is one that does not have the small features called "Windows". The term comes from the French word sans, meaning "without".

SansGUI's are more typically used in Unix-like Operating Systems. The conventional wisdom is that a GUI (Grapical User Interface) help guide the casual computer user to perform routine tasks with Point and Click simplicity. SansGUI's have acquired considerable acceptance for users accustomed to the CLI (Command Line Interface).
OK off and running:)
nondaj wrote:Gee if you guys/gals are back East it must be terribly late for you. I am beginning to get buggy eyed out here on the west coast. Shall we layoff until tomorrow and tackle it all again? Sorry to be such a problem here. Must be frustrating for you both.

I'm in Arizona :)
A sansGUI interface is one that does not have the small features called "Windows". The term comes from the French word sans, meaning "without".

SansGUI's are more typically used in Unix-like Operating Systems. The conventional wisdom is that a GUI (Grapical User Interface) help guide the casual computer user to perform routine tasks with Point and Click simplicity. SansGUI's have acquired considerable acceptance for users accustomed to the CLI (Command Line Interface).
nondaj wrote:OK off and running:)
Off and running to change the dosbox file or the game is working?
A sansGUI interface is one that does not have the small features called "Windows". The term comes from the French word sans, meaning "without".

SansGUI's are more typically used in Unix-like Operating Systems. The conventional wisdom is that a GUI (Grapical User Interface) help guide the casual computer user to perform routine tasks with Point and Click simplicity. SansGUI's have acquired considerable acceptance for users accustomed to the CLI (Command Line Interface).
lol it's after 2am here right now... I am getting off here, I have a few things to do on my Laptop before heading to bed...

I thought you said something about a month back or so that you were having problems with your E: drive??? That someone came in to do something and it hadn't worked right since, or something like that...

Sorry the Files didn't work, we must have a different setup...



Why not start from the Top... Lay down your Hardware and Software for us, everything you got that is major... The Operating System, How much Memory, Harddrive Size, CPU Size and Speed, Video Card, Sound Card, types of CDROMs/DVDROMs... Any type of Enhancing Software you might have had put on... Anything you think might be relevant...


Sorry we didn't get anywhere tonight... Wish I was coming to Cali some time in the near future for business, I'd stop by and take a look at it for you...

Have A Good Night...
The Paved Straight Road, Won't Always Get You Farther Than The Winding Dirt Road...


Can You Run Your Game??? Click Here And Find Out...

*Note, Not All Games Have Been Tested & Therefore May Not Be Listed...
Your are not going to believe this - disc swap screen says put disc in Drive D!

Again I carefully copied/modifed DosBox Config file as instructed.