Everything worked,

As a nice summery some screens.

And a question :

What were the IRQ for the folowing situations :
DOSBox 0.60 (I know its old but hey, D.O.G. supports it)
The Modem
DOSBox 0.61
The Modem
DOSBox 0.62
The DirectSerial
The Modem
DOSBox 0.63
The DirectSerial
The Modem
DOSBox 0.65
Anything differant of DOSBox 0.70?

Erik.

looks nice.
There are more irqs offcourse. (the clock(pit) the clock (RTC), keyboard)

And at what IRQ are these devices set?

I also have built in a check for the DMA channels.

Thanks for the input,

I'll take you up on that after you fix the problems and after I had a play again - too used to WC2 at the moment

Oh and ... "LET THE GAMES BEGIN"

I'm going to start checking every game and make sorts of PDF pictureguides for them downloadable from my site.

Erik.

0 system timer
1 keyboard
2 cascade ( =IRQ8-15)
8 RTC
11 IPX
12 mouse

Looks like in tandy mode IRQ5 is used for RAM refresh.

> DOSBox 0.65
> Anything differant of DOSBox 0.70?

They have a few different parameters.

> DOSBox 0.60
Those are from before my time here but they probably stick to the real hardware defaults (COM1 IRQ4 COM2 IRQ3 ...)

Thanks,

2 cascade ( =IRQ8-15)

IRQ 2 is used for the "cascade" device, but what do you mean with ( =IRQ8-15)?

They have a few different parameters.

I know, so nothing IRQ wise?

Are some IRQ's shareable? I mean can the Gravis UltraSound device have the same IRQ as the Tandy refresh device? As they both default to IRQ 5.

Erik.

> IRQ 2 is used for the "cascade" device, but what do you mean with ( =IRQ8-15)?

The interrupt controller they desgined back in the day could only handle 8 interrupts directly, but had cascading capabilities. The cascaded interrupt controller uses an interrupt of the primary one to work. You could say IRQ 8-15 (the second IRQ controller) "hang on" IRQ 2 😉

> Are some IRQ's shareable?
It's only a problem if the devices that are on the IRQ are used simultaneously.
It was probably not common practice to put a GUS in a tandy (if that is possible at all).
Also depends on the software: If it knows it's got shared interrupts it could be made to work that way.

So it is best to always warn people when they have two devices with the same IRQ and disregard shareability as it may prove errorprone?

One more question though, when behind a router and using IPX or a modem, do I then set in the clients DOSBox's the IP-address of the router of the Server DOSBox?

So for PC1 Server
IPX STARTSERVER

for PC2 Client
IPX CONNECT 186.15.50.7 (or something like it from my ISP)

Same for the modem but then for the calling DOSBox's.

Thanks for the help.

Erik.

You shouldn't warn about tandy refresh though when DOSBox is set to VGA.

There is another limitation. The ISA bus only provides those IRQs:
3,4,5,6,7,9,10,11,12,14,15. The others are hardwired.

About the router:
files/ipxudp_portfw.png

It works similar with modem. You have to forward the port on the server side.

You shouldn't warn about tandy refresh though when DOSBox is set to VGA.

I know, already implemented it that way.

files/ipxudp_portfw.png

As expected.

Thanks, now if red_avatar or anybody else wants to take me on in a multiplayer session we can test how well it plays over the net. Just leave a PM.

But remeber I'm in Belgium and I work from 6 till 19 o'clock (Well with 4 hours of traffic anyways).

Erik.

h-a-l-9000 wrote:

There is another limitation. The ISA bus only provides those IRQs:
3,4,5,6,7,9,10,11,12,14,15. The others are hardwired.

So these values are free to be choosen (except 11=IPX,12=mouse) by the enduser?
It is no 13 in there? A piece of superstition by the ISA bus creators? 😉

ErikGG wrote:

...the Gravis UltraSound device have the same IRQ as the Tandy refresh device? As they both default to IRQ 5.

That's not the problem of DOSBOX frontends creators, isn't it? 😦
Even not a problem of the DOSBOX creators... 🤣

...planning the next version of the Universal Binary MacOS X frontend...

11 also if IPX is not active.
13 has something to do with the coprocessor. I don't know if/how DOSBox uses it but it is definitly not on the ISA bus.

ErikGG wrote: ...the Gravis UltraSound device have the same IRQ as the Tandy refresh device? As they both default to IRQ 5. […]
Show full quote

ErikGG wrote:
...the Gravis UltraSound device have the same IRQ as the Tandy refresh device? As they both default to IRQ 5.

That's not the problem of DOSBOX frontends creators, isn't it? Oops
Even not a problem of the DOSBOX creators... Laughing Out Loud

Well it sort of is, remember the click sound "glitch"? That was because I had set the serial device to the same IRQ as the SoundBlaster. Wich results in either a crash or well glitches. In the end these "bugs" tend to pop up once in a while and who do you think gets the blame for this even though it is the users fault? 😁

Well IMO, either the frontend devs or the DOSBox devs. Therefore I just added a small routine in D.O.G. to check if IRQ's are set to more devices. And now they can't complain about not knowing it was incorrectly set, or they must be blind as you don't miss a popupballoon taking in 1/4th of the entire screen.

It is kind of a preventive routine. A routine to avoid problems, dummy proofing it or some sorts.

11 also if IPX is not active.

Woops, made it only check IRQ 11 if active. Will make it a "hardwired" IRQ.

Erik.

It is assumed that you have at least *some* idea about the values.
If you like having all irqs on the same line, why not, your problem.

Oops I meant IRQ11 can also be used if IPX is not active.

Oops I meant IRQ11 can also be used if IPX is not active.

Ok, less work.

If you like having all irqs on the same line, why not, your problem.

Well it is only a warning that pops up when setting devices IRQ's or activating them. So if a user wants too, he still can, but he is warned. I won't though.

Erik.

h-a-l-9000 wrote:

11 also if IPX is not active.
13 has something to do with the coprocessor. I don't know if/how DOSBox uses it but it is definitly not on the ISA bus.

h-a-l-9000 wrote:

Oops I meant IRQ11 can also be used if IPX is not active.

I read your first sentence in your second way, though. 😉

Thank you for your informations!

I think, I'll remove the 11 from my pulldown menus, because:
When my user select the 11 anywhere and later enables IPX, I've to warn him.
It's better to disable the 11 before.

My experience with DOS is the Mac application 'SoftPC' many years ago in pre-MacOS X times, so don't expect, em, specialized knowledge, of me. 😀

Found some IRQ related informations:
A list of IRQ's and what they're for:

http://www.heise.de/ct/Redaktion/ciw/irq.html
(german site, should easily be translatable)

The screenshot is taken from the DOS-Utilities collection by Shamrock Software. The application INTPROF.EXE from their download checks what IRQs has been used for 10 seconds:
http://www.shamrock.de/dostools.htm
(DOS application and site also german)

Good information, usefull. Never knew an application that could detect IRQ useage, but now I do.

Thanks

Erik.

Don't rely too much on this, it can of course only count irqs that
actually happened (e.g. if you don't hit a key irq1 won't show up).

True, also for IRQ 12 and the mouse.

Erik.