any windows 3.11 gurus kickin around?

[shelby]

OK i found what i did wrong. I put firewall on my ip.... Thanx for your help. I must fix the fonts now

Edited January 21, 2023 by shelby

[shelby]

dillo arachne and links do not work

[awkduck]

The mTCP config will actually need to be tuned for ever initiation of PKTDRV and whichever mTCP program.

In your "C:\MTCP\CONFIG.CFG" the setting "packetint 0x60" needs to be set to what ever interrupt each PKTDRV installs to.

Alternatively, I think each mTCP application allows you to set the interrupt with a command line switch at execution.

Did you just double click on Links, or did you run from the MsDos Prompt? You need to open a MsDos Prompt, run PKTDRV, and then change to the Links directory and run Links from the command prompt.

Tip: If you load PKTDRV with the "/n" switch "PKTDRV /n", it will only load a new PKTDRV channel if an open one is not available. 

Edited January 21, 2023 by awkduck

[shelby]

38 minutes ago, awkduck said:

In your "C:\MTCP\CONFIG.CFG" the setting "packetint 0x60" needs to be set to what ever interrupt each PKTDRV installs to.

So i have to change it to 0x7A. Or it should be 0x79?

[awkduck]

Every time you run PKTDRV it will say something like,

Quote

Installed at interrupt XX using multiplexor at XX

Ignore multiplexor. The multiplexer is PKTMUX. So "multiplexor at xx" = the interrupt PKTMUX uses to connect to your packet driver.

So when you run PKTDRV in autoexec.bat, that is for use with Trumpet.

The thing about MsDos, is that it is Single Tasking. So, "one" packet driver = "one" application.

PKTMUX manages multiple "Virtual" packet drivers.

PKTDRV is the "Virtual" packet driver. 

So, whenever you need another packer driver/PKTDRV you get a the new virtual packet driver at a new interrupt.

 

Edited January 22, 2023 by awkduck

[shelby]

[shelby]

12 minutes ago, awkduck said:

 

so 0x60 only works

[shelby]

dillo says even with 0x60

[awkduck]

 

So if you needed to run multiple mTCP programs, you could create multiple mTCP config files.

Like 60.cfg

packetint 0x60

63.cfg

packetint 0x63

7A.cfg etc.

packetint 0x7A

Then environment setting batch files.

60.bat

SET MTCPCFG=C:\MTCP\60.CFG

63.bat, 7A.bat, etc.

The you would open MsDos Prompt, run PKTDRV, look for the new interrupt, run matching environment setting batch, and finally the mTCP program.

But this is just for mTCP applications.

Other MsDos applications each have their own way of inputting the dos interrupt.

Another thing to keep in mind, Trumpet is a windows socket (winsock) with it's own I.P.. But when you run other Dos Applications, each will get their own I.P. address.

[awkduck]

14 minutes ago, shelby said:

so 0x60 only works

Please, look at the diagram "carefully". It is an example to help you understand how it works. The interrupts, in the diagram, are only examples.

[shelby]

So can you run multiple config.cfg in one bat file?

[awkduck]

In the "Diagram" 0x60 is already being used.

So you cannot use 0x60.

You only know what interrupt to use, after you run PKTDRV in a MsDos Prompt.

[awkduck]

Just now, shelby said:

So can you run multiple config.cfg in one bat file?

Lets figure out the other part first. We can come back to this later.

[shelby]

ok the pktdrv gives me ITN=0x7B. Where i put this

Edited January 21, 2023 by shelby

[awkduck]

For me, Links found it on it's own.

But for mTCP programs, it needs to be in "C:\mTCP\config.cfg" in front of "packetint" "packetint 0x7B"