awkduck

I don't thing that would be the issue. But I can't test it for you. All my USB sata drives are full. None are NTFS.

If you never end up using all channels, you can reduce them to save memory. #AUTOEXEC.BAT PKTMUX 4 79 PKTDRV PKTDRV PKTDRV PKTDRV

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.

Is Trumpet running right now?

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"

Is this in a "Windows" MsDos Prompt, or Real Dos Prompt? You want to be using a Windows Prompt.

You can just type it, or add it to autoexec.bat and reboot. If you just type it, you need to use the same Prompt to run DHCP or PING. Once you close the prompt, the variable MTCPCFG with be lost. If it is in autoexec.bat, the variable will be available for all prompts.

Here, this might help. Close any open MsDos Prompts. Open a new MsDos Prompt. Run DHCP, to test the next I.P. your network assigns. It should be different then the one you have for Trumpet. This is probably the problem you are having. Your firewall might be blocking the new I.P.. Also, you could run "C:\MTCP\PING.EXE 8.8.8.8".

So what is happening when you are running Links?

Does Links still say it can't find wattcp.cfg?

For Links or Dillo?

Copy wattcp.cfg from the Dillo folders "NET\DILLO\ETC". Put it in the same folder as LINKS.EXE. Edit wattcp.cfg. Find pkt.vector and change it to your PKTDRV interrupt "pkt.vector = 0xXX. Then try to run Links again. XX = whatever interrupt PKTDRV installed to. For Dillo, place the Dillo folder in C: "C:\DILLO", edit "C:\DILLO\ETC\WATTCP.CFG" and change pkt.vector = 0x00 to the interrupt PKTDRV installed to. Then run "C:\DILLO\DILLO.BAT".

Try to run Links, press "g" type google.com > enter.

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"

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

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.

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.

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.

Every time you run PKTDRV it will say something like, 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.

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.

Good, we want all of those things to work. It is okay to set the mTCP config "SET MTCPCFG=C:\MTCP\CONFIG.CFG" in autoexec.bat. It is for all mTCP programs. It won't hurt anything. We just don't need DHCP in autoexec.bat. So with MTCPCFG set, reboot and manually run DHCP. We want to see what I.P. it assigns you. This is to make sure the I.P. we later put in Trumpet, is "unused" on the network. It may be different than before. DHCP should display the settings it receives. But it will also be saved at the bottom of" C:\MTCP\CONFIG.CFG". Next, Just to be extra careful, reboot and load into windows; without running DHCP. In Windows, put the new I.P. in Trumpet setup; unless it is the same. Test Opera. If Opera does not work, open a MsDos Prompt, run PKTDRV, and then run Links. Once Links is up, press the "G" key and type google.com. If Links works, but Opera does not, then we know it is either the settings in Trumpet or something is wrong with Opera. You could try to install Netscape as a test. If you can still Ping the D.N.S. with Trumpet Ping, then it almost sounds like a problem with Opera's settings. But I have to say, if you didn't change any of Opera's settings, the default settings should work.

What NTFS driver/application are you using?

Try Virtualbox NAT. You could also just run DHCP in a MsDos Prompt, after PKTDRV. The only reason for doing so, is to see what I.P. it assigns you. DO NOT add it to autoexec.bat. You really don't need it, for your system's normal use. It is more like a test/demo application. Other mTCP programs have DHCP built in. They all use the same mTCP config file.

Does it let you ping the google DNS? What is you current Virtualbox network config? If you run DHCP from Dos, Dos it still assign the same I.P.? Maybe I.P.s have changed on your network.

Congratulations, you have network connectivity! So the issue would seem to be your D.N.S. settings in Trumpet Setup. On your host PC, go to Who is my DNS and look for the result under "DNS Server". Put that in Trumpet's setup up for DNS. For USB, you might check out this page.