VOGONS


First post, by schaetzle73

User metadata
Rank Newbie
Rank
Newbie

Hi,

these games are a special case for Dosbox I think.
The games request to load special supervga drivers which were not available for all the graphic cards which were in the market at the time
of appearance of the games (1994-1995).
I understand that Dosbox emulates a S3 graphic card, which was not considered by these games for the supervga drivers.
Then, the only solution available was to use the universal "univbe" driver who works for all the graphic cards, however yo have to adjust your config.sys to allow te "univbe" to work,writing a line like this:

devicehigh=c:\windows\emm386.exe i=A000-AFFFF

Dos box gives this announcement when I try to run the games.
As far as I know we cannot write somethng in the config.sys of dosbox, we can tick "use xms" or use "ems" or "use umb" but we cannot write a specific line. Can you tell me how we can solve the problem?
Thank you.

Reply 1 of 10, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

Univbe has worked fine in DOSBox for quite some time. Just make sure it's version v5.3 or below.

How To Ask Questions The Smart Way
Make your games work offline

Reply 2 of 10, by schaetzle73

User metadata
Rank Newbie
Rank
Newbie

Dosfreak:

you tell me that univbe has worked fine with dos box.
Ok.
Can you tell me HOW can I make it work in dosbox?
Shall I write something like:

lh= c:\univbe.exe
in the autoexec.bat of dosbox?
Please tell me HOW.
Thank you.

Reply 3 of 10, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

You only needed to do that with EMM386 to get more memory.

Does the game actually give you an error when you try to run it?
Have you actually just tried using Univbe in DOSBox?

Last edited by DosFreak on 2008-04-03, 12:34. Edited 3 times in total.

How To Ask Questions The Smart Way
Make your games work offline

Reply 6 of 10, by schaetzle73

User metadata
Rank Newbie
Rank
Newbie

wd:

the message is the following:

Error: Can't map A000 with EMS- Check config.sys:
For EMM386.SYS replace RAM with i=A000-AFFF

Dosfreak: as you see EMS is enabled and the game do not work, I have already explained that in my previous post. Simply enabling EMS dos not do anything. It does not work.

Hal-9000: "You run univbe like any opther program." Very well, but I need to run "univbe" AND "patrol". How do I make run both programs at the same time in dosbox? I need univbe to run toghether with patrol, otherwise I will not "see" anything.

Thanks to all of you for your help. I think that wd is in the right track.
Sorry if I sound not nice:
Please do not tell me "There is no problem for this or for that in dosbox"
Please tell me HOW to solve the problem. You guys know perhaps too much and sometimnes forget that those who pose questions in this forum have limited knowledge and for them it is not so easy as for you to do this or to do that.
Thank you very much.

Reply 7 of 10, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Univbe is a TSR, this means you run it and it will stay in memory.

So you go to the directory with univbe and execute it. Then you go to the game's directory and run that. You can of course make a batch file which automatically does that.

1+1=10

Reply 8 of 10, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

You can download v5.3a of UNIVBE from SciTech's site for free, but don't expect support for it. This version seems to work pretty well in DOSBox, and I haven't had to mess around with EMS or whatever to get it to work. Just install it, register it with the provided codes, and run UNIVBE.EXE (the first time you run it, it will test the graphics and should detect an S3 Trio card in DOSBox.)

http://www.scitechsoft.com/ftp/sdd/

Reply 9 of 10, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Error: Can't map A000 with EMS- Check config.sys:
For EMM386.SYS replace RAM with i=A000-AFFF

There was another game that needed segment remapping (this is a rather
unusual thing to use an emm for), and it works fine for that game.
Nothing you can do about it at the moment if this is the source of the problem
besides booting xxdos inside dosbox and using emm386 there (this might
or might not work).