shelby Posted January 21, 2023 Share Posted January 21, 2023 2 minutes ago, awkduck said: 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" Ok i put it and save the file. Next? Link to comment Share on other sites More sharing options...
awkduck Posted January 21, 2023 Share Posted January 21, 2023 Try to run Links, press "g" type google.com > enter. Link to comment Share on other sites More sharing options...
shelby Posted January 21, 2023 Share Posted January 21, 2023 (edited) Edited January 21, 2023 by shelby Link to comment Share on other sites More sharing options...
awkduck Posted January 21, 2023 Share Posted January 21, 2023 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". Link to comment Share on other sites More sharing options...
shelby Posted January 21, 2023 Share Posted January 21, 2023 (edited) Edited January 21, 2023 by shelby Link to comment Share on other sites More sharing options...
shelby Posted January 21, 2023 Share Posted January 21, 2023 i change it and nothing happens Link to comment Share on other sites More sharing options...
awkduck Posted January 21, 2023 Share Posted January 21, 2023 For Links or Dillo? Link to comment Share on other sites More sharing options...
shelby Posted January 21, 2023 Share Posted January 21, 2023 both Link to comment Share on other sites More sharing options...
awkduck Posted January 21, 2023 Share Posted January 21, 2023 Does Links still say it can't find wattcp.cfg? Link to comment Share on other sites More sharing options...
shelby Posted January 21, 2023 Share Posted January 21, 2023 no Link to comment Share on other sites More sharing options...
awkduck Posted January 21, 2023 Share Posted January 21, 2023 (edited) So what is happening when you are running Links? Edited January 21, 2023 by awkduck Link to comment Share on other sites More sharing options...
shelby Posted January 21, 2023 Share Posted January 21, 2023 (edited) this. It happens even i put manually the ip dns gateaway etc Edited January 21, 2023 by shelby Link to comment Share on other sites More sharing options...
awkduck Posted January 21, 2023 Share Posted January 21, 2023 (edited) 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". Edited January 21, 2023 by awkduck Link to comment Share on other sites More sharing options...
shelby Posted January 21, 2023 Share Posted January 21, 2023 (edited) Edited January 21, 2023 by shelby Link to comment Share on other sites More sharing options...
awkduck Posted January 21, 2023 Share Posted January 21, 2023 5 hours ago, awkduck said: It is okay to set the mTCP config "SET MTCPCFG=C:\MTCP\CONFIG.CFG" in autoexec.bat. 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. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now