Jump to content

awkduck

Member
  • Posts

    388
  • Joined

  • Last visited

  • Days Won

    1
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by awkduck

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. You are having fun with this 192.168.1.68 (show above as 168.192.1.68) was your I.P. right? 127.0.0.1 > <192.168.1.68 = localhost We want to ping an I.P. that is outside your Virtualbox machine. The gateway, you posted earlier, is 192.168.1.254. You should ping that. If your network allows pings between clients, you could also ping another computer on your network. This is how you would use mTCP ping "C:\MTCP\ping 192.168.1.254".
  10. There are some USB drivers for Dos. If you are looking to transfer files, to and from your Virtualbox VM, mTCP FTP works good. Bret Johnson's USB, DOSUSB, and another. Also, the creator of the original Hiren's Boot CD has some Dos utilities.
  11. Yes, you put an I.P., that is on your network, in place of "localhost". Click Start, wait a few seconds, and then click Stop.
  12. As a test, before loading into Windows, you could use mTCP Ping. If that works, you could load into Windows, not start Trumpet, and then run mTCP Ping; in a MsDos Prompt. If that works, load Trumpet and use it's Ping. If they all work, check the D.N.S..
  13. Yeah, I forgot. The range is 0x60 to 0x7F. Your last setup looks good. I tested it last night. I would use the Trumpet Ping program, to ping your gateway. I guess I've had a packet driver that could only go to 0x74. So not all things are equal.
  14. @Joaquim Vitrual Memory = Pagefile/Swapfile
  15. @UCyborg Thanks for the keen recognition skills
  16. This is in the readme.txt file, The resolution of you image was too low, I couldn't make out the error message. It seems like many of the "Acer Aspire 1690" series laptops only came with 80GB harddrives. I did see some review labelled 1690/1692 that mentioned a 160GB harddrive. Is your drive only 80GB?
  17. @shelby Okay, I've tested it on a real machine. This is what I've had to do. Part of my autoexec.bat I didn't check to see if everything loaded high, but it caused no problem. You can probably REM out DHCP. The settings are saved to your mTCP config file. That way you don't use a PKTDRV for it. Just load the one for Windows/Trumpet. Now, if you've already setup a vector (interrupt) for Trumpet, you can enter the Trumpet folder and edit "TRUMWSK.INI". Find "vector=XX" and delete whatever is in there, unless it is the interrupt PKTDRV used. I mention this because with the wrong vector/interrupt Trumpet did not load for me. I had to delete that setting first. Leave the "vector=" part. Start Trumpet and then select File > Setup. You need to add a static I.P., your D.N.S. (or any usable D.N.S.), select the Packet driver dot/bullet, make sure the vector is correct, add your netmask and finally your gateway. Then click okay and restart Trumpet. Run Opera to check for connection at Google. Then open MsDos Prompt and run PKTDRV. change to the directory of Links and run it. It will fail the first connection type attempt, but when it changes to DHCP it should connect. Your screen will look blank with a block mouse cursor. Press the "G" key and type google.com > enter key. There is probably a way to skip the first Links connection type. But I didn't read the manual :) Also, I think Links has a Graphical mode, instead of text only. That would be in the manual too.
  18. To run Cutemouse, run ctmouse.exe. shelby, I've noticed that your packet driver isn't in autoexec.bat. There is nothing for PKTMUX to use, without a packet driver. If I get a chance, I will post the description of a working setup.
  19. You could try CuteMouse. I myself, out of curiosity, would like to see your whole autoexec.bat and what happens when you run Trumpet. But only if you feel like obliging me this. I will not be offended, if you wish only to stay on your current task.
  20. User rloew created several patched for Win9x. He was/is a 9x saint. You can get his 137GB patch at the Memorial site or Retro System Revival. You don't need the patch, if your harddisk is under that size.
  21. Actually, Tripredacus has a good point. I missed that you only posted your free harddrive space. The is a patch for drives over 137GB.
  22. Like jaclaz has said, it can be done that way. Again, like in that video, do not install your USB drivers.
  23. Do you have another computer you can install this game on?
×
×
  • Create New...