awkduck

With Trumpet, you can check the main log Window. With WATTCP, there is an option in the config, to save the DHCP settings to a file. Obviously, if you specify a static address, that should be the I.P. you are using. I believe, if mTCP programs are not pre-assigned DHCP in the config, they will display the information during execution. If you need your host I.P., for Windows you can follow these directions. Those are for Win10&11. But its very similar for other Windows. If you need to find out what other I.P.s are on you network, it might be good to have a administer access to your gateway/router. That should, at the very least, have a log. But more then likely, It will have detailed network client information and status. ---Some Notes--- Since you say you are kinda just learning things, there are some things I'd like to put out there. There is a ton of information that could be included in this thread. You and I are just stumbling on them as subjects occur. But with that said, even on the subjects we have touched on, there is plenty of undisclosed information. For example, with the setup you are now using, it should be possible to use all static addresses having the same I.P.. But there is potential for occasional conflicts. I have never had one, when run that way. But, I am sure it is possible. My explanation for suggesting the setup you have now, is that it is the more "By the Book" clean approach. Since you are having some configuration issues, it seems best to apply the most diagnostic friendly setup. Earlier we had you running PKTDRV in MsDos Prompts. For me, that has worked pretty well, for some projects. But, by the nature of these components, I have occasionally ran into memory conflicts. The constraints involved there are a deeper subject. With appropriate care and consideration, those conflicts can be avoided. The simple rule of thumb, is to unload every PKTDRV before closing the MsDos Prompt, that loaded it. You would run the desired application, in between loading and unloading, from that same prompt. And if loading multiple MsDos Prompt PKTDRV sessions, manually specifying each new interrupt would be advisable. Separate Dos VMs (Windows MsDos Prompts) don't acknowledge, or at least don't always acknowledge, each others interrupt use. They will tend to only acknowledge real Dos interrupt use. PKTMUX is running in real dos. But even without that real/VM Dos crossover, there is probably potential for conflict.

It certainly can be done. Just gotta pick your poison. I suppose the issue for some people, is portability. Depending on the OS configuration, some machines may not care to boot it. Using Hiren's minimal Windows 98 as an example, it goes to show that a high rate of compatibility can be achieved.

I'm just mentioning the 2 versus 1 partition, as a way to expand on some of the speculations jaclaz has put forth. The primary issue, is accessing the MBR. As an example, the boot loader Syslinux comes with an MBR that must be written to the drive, in order to function as a sole boot loader. When I am installing it, to the main O.S. drive, I can use something like WDE for dos. However, in attempting to do this for a USB drive, WDE cannot even view the MBR. The same is true for the HxD hex/drive editor. But to answer your question, if the drive is zero filled, FDISK cannot even see the drive. "Change current fixed disk drive" displays only the physical C: drive.

One that is within the range your gateway/router is configured to accept. When you ran mTCP DHCP, it only added 1 the the I.P. of Trumpet. So, you are probably safe following that example. For every static I.P. you need, you can probably just add one. Certainly, 254 is the max. However, some routers are configured for a shorter range. Since you gateway is 192.168.1.254, 254 is off limits. Any other I.P. already in use, on the network, is also off limits.

In Windows FDISK can see the drives partition, when there is only one. If I put two partitions on the drive, FDISK crashes after asking if you want to enable large disk support. The reason I looked into this, is because sometimes I end up behind a Windows machine, more then a Linux machine. I also don't really ever use any NT variant. Sometimes I run into a situation where I'd like to make a bootable USB drive, and would like to do it without rebooting. It is something I can easily live without. But, sometimes you've just got to see if it can be done.

Consider this, the free version of Paragon NTFS for Win9x works on Win95. So that eliminates the likelihood of needing several updates. The manual states that the System requirements are: Windows 95/98/ME, 16 MB of Ram, an NTFS partition or the space to create one. I don't know about other NTFS drivers/software, because I haven't tried them.

Will do.

Their DHCP is built in (onboard). mTCP programs will read the config file. If the config file is configure for DHCP, mTCP programs will use their internal DHCP; unless the config file has the settings already saved at the bottom. WATTCP programs will also follow their config file, and use their internal DHCP. But those setting are only saved, for latter use, if the config file is set with the option to save them. At the bottom of this page, it says that some WATTPC programs don't always work with DHCP. (bug?) If that is the case, you might need to set the file your self. That same page provides a example snippet.

I have the files to give "Switch to Win3" a shot, but haven't gotten around to it. I haven't examined the Win3x drivers from the leaked build. But, I think they certainly would aid it beyond the stock files. They are probably the most important files. I've guessed that there is a little more to it then just being in a V.M.. If the host keyboard input is disabled during use, then you can't simply Alt+Enter to see it turn to a Window. The up side, is that the guest would get your Alt+Tab, instead of the host. So, if a V.M., it is an altered one. It would be nice if someone running it sported the about Window. Or testified if you could open a Dos Prompt. I'm sure it can't. There are enough legacy files, in Win9x, to build an okay standard mode Win3x. But you'll get no Dos Prompt. You'd need to build a better "SYSTEM.INI".

In the Arachne DOC folder, there is a file "LAN.HTM". It says,

In WATTCP.CFG there is a variable "my_ip". It can be set to dhcp (the default) or static I.P. "my_ip = dhcp" or "my_ip = xxx.xxx.xxx.xxx"

Yup Or at least it seems like you got it.

No. Dillo and Links look to WATTCP.CFG at execution and use the information inside to determine how to connect. They have their own DHCP. DHCP is just used to put information at the bottom of MTCPCFG.CFG. But I asked you to use it, to verify that your Dos applications were getting a different I.P.. And to show you what I.P. you might have to allow firewall passage, if you wanted connection for them.

TCP/IP Stack It is important to understand, that in Windows there is a single TCP/IP stack that Windows programs utilize for networking. There is a TCP I.P. issued and all Windows TCP/IP programs route through it. Dos does not use the Windows TCP/IP stack. Dos also does not have a "main" TCP/IP stack. Most of the time, a TCP/IP stack is built into each program. Since Dos is single tasking, this isn't a problem. One task = one I.P.. So, if we multitask TCP/IP stacks, we get multiple I.P. addresses. Wattcp is a TCP/IP stack, and programs with it built into them use WATTCP.CFG as a configuration file. mTCP is a TCP/IP stack, and programs with it built into them use MTCPCFG.CFG as a configuration file. They can't use the same file, because they are not the same TCP/IP stack.

No. MTCPCFG is only for mTCP programs. Dillo and Links both use WATTCP.CFG. If you are only using one (Dillo/Links) at a time, you can use the same config by adding "SET WATT.CFG=" in autoexec.bat. But if you are going to be using both, at the same time, then each needs their own config in the folder with them.

@SweetLow They don't seem to work on my Win98FE. But, I'm glad to have a copy of them.

No. Not unless you want to use two or more mTCP programs at the same time. If you use FTPSRV and HTTPSERV at the same time, then yes. In an earlier post, I was giving instruction on how you could do it. But unless you needed it, I wouldn't worry about it. Making sure your Dillo and Links worked, seemed more important. By now, you have your head wrapped around this pretty good. I'll probably have to start asking you for advice. I do apologize. This last setup, I should have had you try right away. It is the most appropriate configuration. For whatever reason, my Windows behaves differently; allowing me to cheat a little.

You must be talking about this guy. Err.... Actually this guy > www.geoffchappell.com/notes/windows/retro/extrawin.htm Interesting, huh Win3x is my favorite Windows. With that said, out of the operating systems I use, it gets used the least. NOTICE: I had no idea there was history with that guy. I just clicked my own link, to meet a surprise.

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