Help me out

[KHAN]

I am going to make an arcade machine.
so i have decided to use Dmame(pure DOS).

i have got some problems..

q:1)Does it require windows installation support ?
q:2)I don't understand how to do these settings ?
         
a)Autoexec.bat tweaking.
b)config.sys editing.
b)Perfomence (RAM) tweaking.
c)CWSDPMI for Dmame.

Please write in your own words that what should
i do in the beggining ? STEP BY STEP.
after doing this i will also use a frontend.

This is the very first time i am trying to run
Dmame,Your guidence will be a pleasure.

Thanks in advance..

[Grasshopper]

It would take a book to explain how to configure msdos!

But my first question would be have you got hold of a set of msdos installation disks yet. Later versions of dos had quite a good installer that set up usable defaults for config.sys and autoexec.bat.

If you've got Windows 98 (or 98se) then an easy way to set up a working dos 7 installation (and still have access to windows if you need it) is to do the following:

Install win98 in the usual way.

There will be a file called msdos.sys in the root directory of c which will be hidden by default.

Unhide it and load it into notepad.

Edit the BootGUI line to say BootGUI=0 then save the file.

The machine will now boot to a pure dos 7 prompt.

You can still use windows by typing win followed by return.

This doesn't answer all your questions but it's a good starting point.

[coldrain]

I have a machine set up in the above way with the GUI disabled and a line on my autoexec.bat file to boot into arcadeOS frontend. My problem is geting my soundcard to work. I have a creative labs PCI128 (model CT4740) and all works fine if I run from within windows 98se (using arcadeOS and dmame) but I get an error message that reads " AUDIO INITALIZATION FAILED, UNABLE TO INITIALIZE SYSTEM" when arcadeOS trys to run mame stright from a dos boot.? I think I need to add a few lines to my AUTOEXEC.BAT file to tell mt machine what soundcard and where but I am unsure what..? Does anyone know.?

[ries]

my guess is that you forget to tell the dos apps what you soundcard settings are using the set blaster= command. Have a look at this website for a far better explaination;

http://www.mameworld.net/dosmame/setup.php

hope this helps!

[coldrain]

Thankyou, thankyou, thankyou.

It helped a lot. Problem solved.  

[KHAN]

I have a machine set up in the above way with the GUI disabled and a line on my autoexec.bat file to boot into arcadeOS frontend. My problem is geting my soundcard to work. I have a creative labs PCI128 (model CT4740) and all works fine if I run from within windows 98se (using arcadeOS and dmame) but I get an error message that reads " AUDIO INITALIZATION FAILED, UNABLE TO INITIALIZE SYSTEM" when arcadeOS trys to run mame stright from a dos boot.? I think I need to add a few lines to my AUTOEXEC.BAT file to tell mt machine what soundcard and where but I am unsure what..? Does anyone know.?

Same problem i have got.
but i have done some things for correct it..
now the error is going to be changed ...

"WARNING: Cannot open swapfile c:
LOAD ERROR : NO DPMI MEMORY

I think some thing to do with DPMI but don't know yet..
what is swap file ? i don't get it...

[KHAN]

I have a machine set up in the above way with the GUI disabled and a line on my autoexec.bat file to boot into arcadeOS frontend. My problem is geting my soundcard to work. I have a creative labs PCI128 (model CT4740) and all works fine if I run from within windows 98se (using arcadeOS and dmame) but I get an error message that reads " AUDIO INITALIZATION FAILED, UNABLE TO INITIALIZE SYSTEM" when arcadeOS trys to run mame stright from a dos boot.? I think I need to add a few lines to my AUTOEXEC.BAT file to tell mt machine what soundcard and where but I am unsure what..? Does anyone know.?

Same problem i have got.
but i have done some things for correct it..
now the error is going to be changed ...

"WARNING: Cannot open swapfile c:
LOAD ERROR : NO DPMI MEMORY

I think some thing to do with DPMI but don't know yet..
which version of CWSDPMI require? swap file ?

[Chris]

Drop a copy of CWSDPMI.EXE in your MAME directory and you should be set. MAME will find it and load it.

[KHAN]

I alredy put the cwsdpmi4.exe in the mame folder.
the error given below remains ...

does i need cwsdpmi5.exe

[Chris]

I alredy put the cwsdpmi4.exe in the mame folder.
the error given below remains ...

does i need cwsdpmi5.exe

If it's called cwsdpmi4.exe, MAME won't find it.  Rename it to cwsdpmi.exe.

--Chris

[KHAN]

it name as "cwsdpmi.exe"
I was just telling about the version..


because i know that the version 3 is use for 32mb or greater ram
and version 4 is use for 64 + ram. now version 5 should be 128 +.
so i have 128 mb DDR ram...

problem is problem....
waiting for Coldrain because he has solved his ...

[KHAN]

I have a machine set up in the above way with the GUI disabled and a line on my autoexec.bat file to boot into arcadeOS frontend. My problem is geting my soundcard to work. I have a creative labs PCI128 (model CT4740) and all works fine if I run from within windows 98se (using arcadeOS and dmame) but I get an error message that reads " AUDIO INITALIZATION FAILED, UNABLE TO INITIALIZE SYSTEM" when arcadeOS trys to run mame stright from a dos boot.? I think I need to add a few lines to my AUTOEXEC.BAT file to tell mt machine what soundcard and where but I am unsure what..? Does anyone know.?

I am unable to get rid of this errot...

AUDIO INITALIZATION FAILED
UNABLE TO INITIALIZE SYSTEM

I have same problem that sound in windows looks perfers but when it comes
to DOS...no sound...

another problem is the time of loading a game is slower than command line mame...and games also run slow ...as compared with dMAME in windows.

[Thenasty]

as far as your cwsdpmi4.exe, maybe that file is ZIP Self-Extracting. Renaming to cwsdpmi.exe won't do it.

just use the latest version of cwsdpmi which is I think 5b. Make your it is UNZIP or if you get a self-extracting EXE, run it.

For DOS SOUND to work, you need to install your card DOS SOUND DRIVERS.

make sure you have in your autoexec.bat

SET BLASTER=A220 I5 D1 H7 P330 T6
SET SBPCI= WHERE-EVER IT IS INSTALLED (If your card is
                     a Soundblaster )

SBINIT         (If it is a soundblaster card, this should                    
                     automatically be there)

[KHAN]

you are absolutely correct .
cwsdpmi problem was due to the wrong version,but now it is solved.
thanks for it....

the sound problem is still remains...
i also download the (sbpci and sblive) audio drivers for dos.
but they are not effective here.....

I have  P4 (INTEL D84FGLAD)mother board with a builtin
(SIGMATEL C-Mejor Audio) SoundBlaster.
As you are saying that i have to need a dos driver of my sound card.
Does i require specific (Dos) sound drivers for it ?
I am not getting a correct path for an autoexec.bat file whether
it is already install in windows.

[Thenasty]

I have  P4 (INTEL D84FGLAD)mother board with a builtin
(SIGMATEL C-Mejor Audio) SoundBlaster.
As you are saying that i have to need a dos driver of my sound card.
Does i require specific (Dos) sound drivers for it ?

Save yourself the HEADACHE looking for drivers for it and get yourself a Sb16 PCI card, its only around $15.00.
Most onboard sound will not support DOS driver. If you got a 16 Bit/ISA slot, then get a Soundbalster 16 ISA, it works wonderfully w/MAME. To stinking bad that MOBO companies decided to drop ISA in new MOBO's. Why can't they get rid of the Hi-Riser MODE and replace it w/ISA ? No one uses it anyway.

[KHAN]

Save yourself the HEADACHE looking for drivers for it and get yourself a Sb16 PCI card, its only around $15.00.
Most onboard sound will not support DOS driver. If you got a 16 Bit/ISA slot, then get a Soundbalster 16 ISA, it works wonderfully w/MAME. To stinking bad that MOBO companies decided to drop ISA in new MOBO's. Why can't they get rid of the Hi-Riser MODE and replace it w/ISA ? No one uses it anyway.

To buy a another is not any more problem.
my PENTIUM 4 Board has not contain ISA slot.

It means that as far as the world is going towards
forward the Hardware  Compatiblity going backward.