VOGONS


First post, by Guest

User metadata

Hi all!

Got this error message while MoO2 tries to initialize ipx network: "CALL:Descriptor type 0 unsupported"
It appears shortly after MoO2 opens the socket 4668 or something and only if i am connected to an ipx server. If I am not, it starts correctly, but i cannot find any created games, as expected.
Somewhere else i read, that someone got MoO2 running with ipx. Don't know why this is not working.
BTW: I used the newest unofficial build. The official 0.63 release crashed with "interrupted on higher privilege" or something similar.

Thanks!
Guest

Reply 1 of 18, by HunterZ

User metadata
Rank l33t++
Rank
l33t++

Please don't use acronyms for game names without spelling them out at least once.

I'm guessing it's Master of Orion 2.

Reply 2 of 18, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Is that my build you tried?

Reply 3 of 18, by Guest

User metadata

I downloaded the build from
http://cvscompile.aep-emu.de/dosbox.htm
(2005-07-03)

And yes it's Master Of Orion 2. I know that I shouldn't post game specific errors here, didn't know where to post it.

BTW: Does DOS-Box really emulate every single instruction? Or are there at least patterns, that are interpreted to function in a specific way, so they can be executed a lot faster?

Reply 4 of 18, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

To get IPX in moo2 you will probably have to download my build - nobody else uses this patch AFAIK.

DirectSerial patch

Reply 5 of 18, by Guest

User metadata

dosbox emulates every instruction unless you use the dynamic core

Reply 6 of 18, by Guest

User metadata

Hi h-a-l-9000,

Where to get the things I need, and how do I get them running? Do I have to patch my DOS-Box?
Anyway, I hope that they will take your code for next official releases!

You don't know how long we've been trying to play the DOS-version of MoO2 multiplayer. This would be really great, if you could make that running!!

Thanks!
Guest

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

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Download the zipped binary on that message and put it to a directory of a dosbox installation (maybe rename the original dosbox.exe). You may also have to download mscvp71.dll and msvcr71.dll (ask Google). Run the new exe file.

Reply 8 of 18, by weigo

User metadata
Rank Newbie
Rank
Newbie

I've registered to the board, and now I see your attached files. Wow, this seems to work! Thanks a very lot!
Now the whole thing will be tested extensively!
Great support!

weigo

Reply 9 of 18, by QuietGuy

User metadata
Rank Newbie
Rank
Newbie

I get exactly the same error "Descriptor Type 0 unsupported" when I try the following:

I have Windows 3.11 running in DOSBox. It works perfectly, but if I install some games or applications I sometimes get the error and DOSBox quits. All those installations have one thing in common: they are made with Wise Installation Systems.

I am sure it's a bug in the installation and not a bug in DOSBox, since everything else works perfectly, but as it was not a problem on my 286 notebook, I think it shouldn't force a total DOSBox exit.

Is there a work around, patch, or something else?

I am using DOSBox v0.65, tried it on different PC's, only change to the default DOSBox config is ems set to false (otherwise Windows 3.11 won't run anyway).

Reply 10 of 18, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

This message just means that rubbish was executed, can be pretty
much everything.
Maybe some demo is available that shows the problem (uses the
wise installer and is compatible with win3.x), so you could post
a link to it.

Reply 11 of 18, by QuietGuy

User metadata
Rank Newbie
Rank
Newbie
wd wrote:
This message just means that rubbish was executed, can be pretty much everything. Maybe some demo is available that shows the pr […]
Show full quote

This message just means that rubbish was executed, can be pretty
much everything.
Maybe some demo is available that shows the problem (uses the
wise installer and is compatible with win3.x), so you could post
a link to it.

Since I don't want to break copyright laws, I created a dummy installation. It contains a text file. I noticed when it only contained the text file nothing went wrong, so I added the VB 4.0 runtime DLL's, and for that I got a price.

When he tried to register the DLL's it crashed DOSBox.

Reply 12 of 18, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

They use an invalid descriptor to swap in/out segments, works fine
if the call throws an exception in this case.

Reply 13 of 18, by QuietGuy

User metadata
Rank Newbie
Rank
Newbie
wd wrote:

They use an invalid descriptor to swap in/out segments, works fine
if the call throws an exception in this case.

So there is nothing really to do in this case I'm afraid? Too bad I can't really debug the setup files to fix a thing...

Reply 14 of 18, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Well it's pretty easy to fix 😀
You just need to insert a CPU_Exception where now is an E_Exit
(well almost), if you can compile the sources i'll post the line.
Otherwise just wait some time, might be added to the CVS sources.

Reply 15 of 18, by Kippesoep

User metadata
Rank Oldbie
Rank
Oldbie

Since QuietGuy is the not-so quiet guy sitting right next to me, just post the line and I'll compile a version for him. BTW, CVS updates seem to be pretty much impossible at the moment, as the anonymous CVS gives a premature EOF for any and all requests.

My site: Ramblings on mostly tech stuff.

Reply 16 of 18, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

I don't have it right here, but it's something like
CPU_Exception(EXCEPTION_GP, selector & 0xfffc)
where the E_Exit("Call: ...) is, will post it later on correctly.

Reply 17 of 18, by Kippesoep

User metadata
Rank Oldbie
Rank
Oldbie

It works. QuietGuy tells me I'm a hero, but credit goes to you, wd.

My site: Ramblings on mostly tech stuff.

Reply 18 of 18, by QuietGuy

User metadata
Rank Newbie
Rank
Newbie
Kippesoep wrote:

It works. QuietGuy tells me I'm a hero, but credit goes to you, wd.

I didn't said it like that.
I said "Steven, je bent geweldig." which is "Steven, you are great."

😁