awkduck

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..

Maybe, when you are setting up your laptop, install USB and NTFS; before everything else. If you are still having problems, then you know it is likely the USB drivers. If there are no problems, then install everything else. But check to see if NTFS still works, after each thing you install.

Hey jaclaz, This has been my suspicion. On other setups, HxD can copy the whole physical drive and edit the MBR. Under "Extras > Open Disk" you are given partition options, under a "Logical disks" lable. They are listed as C:, D:, etc.. Below that you are given a label "Physical disks". They are listed "Hard Disk 1", "Hard Disk 2", etc.. I am opening under the "Physical disk" label. This is exactly what I believe is happening. But I haven't had enough experience with USB and Win9x. I know it lets me format it, as a kind of superfloppy, if there isn't already a partition on the drive. I just don't know if that is normal, or not. There will be no MBR. It will mount multiple partitions, if they are present on the device.

After a fresh reboot, run Trumpet and leave it open. Then run mTCP DHCP. What I.P. does DHCP receive?

It seems that, with USB drives, I cannot access the MBR under Win98. I've also notice the same thing under DOS, when using USB drivers for DOS. "SYS X:", X equals USB Drive under Dos/Windows, and Windows format do transfer system files. But both fail to touch the MBR. If I used HxD to view the drive, the MBR is not to be found. And Partition magic cannot see the drive. The test USB drive is a 16GB pendrive. This post is just to verify that this is a limitation of Win98. If not, a work around would be welcomed. Or is this the outcome of using updated USB drivers? The PartitionMagic manual says USB drives are fine.

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.