Jump to content

any windows 3.11 gurus kickin around?


Recommended Posts


Posted (edited)

Is this in a "Windows" MsDos Prompt, or Real Dos Prompt?

You want to be using a Windows Prompt.

Edited by awkduck
Posted

If you have rebooted, then you need to run PKTDRV and make sure that the installed interrupt is the same as in "C:\MTCP\CONFIG.CFG"

Posted (edited)
9 minutes ago, awkduck said:

If you have rebooted, then you need to run PKTDRV and make sure that the installed interrupt is the same as in "C:\MTCP\CONFIG.CFG"

it is the same. i made a net.bat that runs in windows promtp
Screenshot-1.jpg

Screenshot-1.jpg

Edited by shelby
Posted

My Windows is letting me get away with a lot more then yours.

But here is a I.P. safe way to do everything.

Keep in mind, you will have a different I.P. for things. So your firewall will need to be taken into consideration.

----

Edit autoexec.bat and add a PKTDRV for every channel you need.

PKTMUX 8 79
PKTDRV
PKTDRV
PKTDRV
PKTDRV
PKTDRV
PKTDRV
PKTDRV
PKTDRV

Reboot but do "not" start Windows.

Examine "all" the PKTDRV installed interrupts.

Once you have them written down, or something, start windows.

The first interrupt is already set for Tumpet.

Give the second interrupt to mTCP. C:\mTCP\config.cfg > packetint 0xXX

Give the third to Links C:\LINKS\WATTCP.CFG > pkt.vector = 0xXX

And the fourth to Dillo. C:\DILLO\ETC\WATTCP.CFG or C:\DILLO\WATTCP.CFG > pkt.vector = 0xXX

I copies all the C:\DILLO\BIN\*.* files to C:\DILLO, C:\DILLO\ETC\WATTCP.CFG to C:\DILLO, and deleted DILLO.BAT.

Then I just ran DILLO.EXE.

If Dillo and Links still result in  "cannot resolve host" or "host not found", add your D.N.S. to both WATTCP.CFG files,

nameserver = 8.8.8.8
# or whatever your D.N.S. is

Now when you open a Windows MsDos Prompt you don't have to run PKTDRV.

To test if it is working, make sure Tumpet is running and run DHCP.EXE.

You should now see DHCP report a different I.P. then Trumpet.

Posted

If you never end up using all channels, you can reduce them to save memory.

#AUTOEXEC.BAT
PKTMUX 4 79
PKTDRV
PKTDRV
PKTDRV
PKTDRV

 

Posted

That is now working like it should.

Will your firewall prevent the new I.P. addresses from working, like before?

Notice, that DHCP now gives itself a different I.P. then Trumpet. Which is the way it is supposed to work.

Each channel "should" request it's own I.P..

 

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...