awkduck

How many hardware/vendor I.D.s are listed in you audio card inf file (wdma_int.inf)?

If you can install something else, without a disk space error, then you do not need a patch. Have you googled to see if this is a common error? You could install the game using a VM with Windows. You would save your registry to a file, before install. Save it again after install. Then use Windiff to compare the two. The results can be saved to a .reg file, with REGEDIT 4 at the top of it. Copy the game files over, to the same location as on the VM. Then double click the .reg file.

It looks like the maximum channels is 8. It might be useful to see you full boot, to see why no packet multiplexer is found. When you used Dillo, was it fullscreen (ALT+ENTER)?

Does it give you an output that says that? Or can you only load 2 instances of PKTDRV? I doubt free memory is the issue, but it might be. If that is the case, sometimes TSRs can be loaded high.

It has been suggested that Opera and Netscape are the best Win3x era browsers. But Links and Dillo are newer. There is also MicroWeb.

Other considerations, with live harddisk images of Win98. You can also use a Fat16 formated disk image. Then you can used DoubleSpace with extreme compression. Afterwards, you could create a smaller Fat16 image for the smaller footprint. The disadvantage is that, the live image runs over INT13, in "Dos Compatibility Mode". This means that Windows cannot relocate DoubleSpace to higher memory. In turn you would have less conventional memory. This might not be a problem, unless you run Dos games that need plenty of conventional memory. Alternatively, you can use UPX to compress Windows EXEs and DLLs. You will want to avoid the folder with dos EXEs (Scandisk etc.). Then will not work after compression. You can create a folder on the USB drive, to keep Windows cab files. This also means cab files from updates. That would also reduce the harddisk image footprint. -To add more a persistent state- Keep wallpapers in a folder on the USB drive. I name one Wallpaper.xxx and set is as the Windows background. Now when a different wallpaper is desired, in can just be names Wallpaper.xxx (BMP/JPG). Which ever image format used, would need to adhered to. Created a batch file, on the USB drive, for start up applications. Then placed a shortcut, to it, inside the Windows startup folder. For any portable applications create a folder, on the USB Drive, with Start Menu like shortcuts and folders inside it; something like Portable Apps. Then add a command, to the startup batch file, that copies the folder to the Windows Start menu folder.

If you are using PKTMUX, the you should be able to let go of WINPKT. Once when you ran Trumpet without WINPKT, it output that it could not find WINPKT or PKTDRV. WINPKT is not multiplexing for the Dos Prompt. It only multiplexes for winsock. With Trumpet 3, I believe, PKTDRV can be used instead of WINPKT. But if that is not the case, then you would need to run PKTMUX and PKTDRV before WINPKT. Also, PKTMUX has not been given your "packet driver" interrupt, or quantity of needed packet driver channels. Maybe this might work? The only thing I can't remember for sure, is if you set PKTMUX packet channels to 10, can you run PKTDRV 10 times right away; making them available when needed? Or, do you have to always run it directly before the next application? If I remember correctly, if you have a bunch of PKTDRVs running, PKTMUX will direct application use to the next open PKTDRV. When ever an application times out, after use of PKTDRV, it will resets to open; ready to be used again. If for some reason a PKTDRV does not reset, there is a PKTDRV switch "/r" that will force reset. I haven't looked through PKTMUX.DOC completely, lately. There might even be a switch to tell PKTDRV how many channels to run. That doesn't ring any bells, but maybe?

I thought of another option. You could use a USB add-on card or PCMCIA. Then you could have the bios booting USB host disabled in Windows. But the add-on USB would provide you with active USB support. It isn't pretty, but it would be easier.

If it does, you've certainly earned it.

Have you tried? The PKGMUX.DOC (which is really just a txt file) says, This files is included with PKGMUX. There is lots of good information in there. It is easier to use Trumpet. But even if you want to use WfW3.11 and the Wolverine TCP/IP stack, you can still get away with it. You just need to use a "packet driver" to "NDIS" shim.

You need to change PKTMUX to interrupt 90. It is at 80 in the screenshot. Make sure you run PKTDRV before you run DHCP. You need to run PKTDRV before you run any program that needs the packet driver.

Really, you don't need the install.bat. Delete "bin" and "doc". Just copy everything to a folder of you choice, without using install.bat.

Did you, ? I don't understand what you meant by "extensions". Please clarify. You did load your packet driver before PKTMUX, right? Just checking. If you did all of that, you could check if your "packed driver" supports choosing the interrupt. Then set it, and everything else, to interrupt 0x60.

What happens when you install the USB drivers for Windows? Booting Win98 from USB uses BIOS to provide the USB drive as drive C:. When you install USB drivers, it will cause problems. So, you could just never use USB. But if you have enough memory, - You could setup Win98se on the computer, drivers and all - Reduce it in size, unless you have a lot of memory - Create a harddrive img or vhd file large enough to hold your Windows install. - Use Virtualbox or something to make the harddrive image a system disk, using a Win98 floppy image. (Create one from your install, if you installed any update that modified MsDos 7 Boot files.) - Copy you Windows installation to the harddrive image. (Do not overwrite MsDos 7 boot files.) - Format your USB drive as FAT32. - Install Grub4Dos to the USB drive. - Then configure Grub4Dos to enable USB support and boot the Win98 harddrive image from memory. Every time you shutdown any changes will be lost. You can get around this by installing the HxD hex editor, and using it to copy the entire drive image to a new file. You do this "while" Windows is running. Then you swap the saved image with the new one you just created. You do this before shutdown or reboot. Some changes try to reboot Windows when they are finished. Like installing DirectX. Most of the time you are given a prompt, with an "OK" button. Run HxD and save the image before clicking the "OK" prompt. If you are given no prompt, you'll need to modify your harddrive boot image to start in Safe mode, on next boot. Then boot the harddrive image in VirtualBox or something. Finally, install whatever caused a reboot without prompting you first. As an additional tip, use or create portable applications. Also install those portable application to you USB drive, not the Windows harddrive image. That is, unless you have a huge amount of memory. You'll want to set a permanent drive letter for you USB drive, from the Drive's "Device Manager" properties. You'll probably want to move the default Windows and Dos temporary folders to a folder on the USB drive. Again, you'll want to assign a permanent drive letter to your USB drive You'll also have to decide if you want you Virtual memory enabled or not. It saves room on the harddrive image if you disable it. Drive C: will be running in "Dos Compatibility Mode". But it won't really matter. If you get a warning about your boot sector potentially being infected/corrupted, it is because you booted the image by it's partition and not as the drive. Nothing is wrong. Grub4Dos creates fake boot data to initiate the boot.

@Damnation It was suggested to me, that I search SweetLow's user name on google. If you search the forum, be sure to use the name with USB or USB 2.0; not USB2.

When Windows is running, check help/about. There you may find that Windows is already running in "Enhanced Mode". If it isn't start Windows with "WIN /3". Start PTKMUX.EXE like this "PKTMUX 5 90". "5" is for how many different programs will need to network access at the same time. "90" is for the interrupt your driver is using (0x90). Then run PKTDRV.EXE inside a Windows Dos prompt. In that same Dos prompt run the application you want to use. I am pretty sure you can also use PKTDRV.EXE as an alternative to WINPKT, for use with Trumpet. Just run PKTDRV before you start Trumpet.

I think(?) Trumpet came with WINPKT. But if Trumpet 3 did not provide it, you can get it from this zip file "WINPKT.COM". But I don't ever remember needing an extra program like that. You would add "WINPKT.COM 0X90" to "AUTOEXEC.BAT". This issue might be that Trumpet needs to know the interrupt of your "packet driver". I can't remember how Tumpet 3 managed that. Maybe a ini file? Something like TRUMPET.INI? Did it ask during installation? Bypassing the 30 day evaluation of Trumpet is something beyond the scope of this forum. With that in mind, you might end up wanting to uninstall Trumpet 3 and install Trumpet 2, which comes with "WINPKT.COM". Sorry, I had forgotten about the trial period. Note: Run Win3x in enhanced mode, for best support. Also, an alternative to "WINPKT" is "PKTMUX". "PKTMUX" is useful if you want to use multiple Dos only networking programs, in Desqview or Windows without winsock support. When you don't need winsock, you don't need to load Trumpet.

My version of Virtualbox (4.x) is very old. So I don't have much to reference with. I would look over the Virtualbox networking settings. Maybe try switching between NAT and Bridge.

Are you running this in DosBox or a VM? Unless your network is under really heavy load, a 10 second timeout should be plenty of time. According to the output, locally things are working.

I have a couple of relatives that used to make a living programing PLC production lines. One of them leaned more towards the GUI. I guess he still does it.

MDGx has some example autoexec.bat/config.sys configurations you can examine. If you have Dos6X you can read here. For Dos7X here. Pay extra attention to "LOADHIGH", "DEVICEHIGH", "HIMEM.SYS", "UMBPCI.SYS", and maybe "EMM386.EXE". If "UMBPCI.SYS" work for you, then you probably don't need "EMM386.EXE". But if it doesn't work, the maybe use "EMM386.EXE" with the noems option. If you don't mind, what is the end goal?

The download should come with a SAMPLE.CFG file. Copy it and rename it somewhere like "C:\MTCP.CFG". Then add "set MTCPCFG=C:\MTCP.CFG" to "autoexec.bat", above/before anything related to your packet driver or the mTCP application you are running. The SAMPLE.CFG, or whatever you renamed it to, has basic settings for you network and mTCP applications. You edit SAMPLE.CFG and provide the interrupt of you "packet driver". Your packet driver is at interrupt "0x9" (as shown above). So in SAMPLE.CFG you would find "packetinit 0x60" and change it to "packetinit 0x9", or maybe "packetinit 0x90". The DHCP settings appear at the bottom of the SAMPLE.CFG file. If it is blank, then when you run DHCP it will automatically put the setting in there. If you want a static network setup, then you can put your own setting in there. With a static setup, you do not have to run DHCP; because programs will use the settings you saved. Remember, this is just to test that things are working. This way you know things do work.

How much conventional memory do you have available?

I'm not sure if it works that way. It has been a long time. I remember having problems getting connectivity through the Windows Command Prompt. I think instead, I used EnhancedDrDos/TaskManager and Desqview with a packet driver muxer. I have used Dos TSR in Windows. But it is hit and miss. Some are a roll of the dice, every time you access them. Try your packet driver with the MTCP programs. If that works, you have a start. For Windows, it might be better to use programs that rely on winsock. If you have Win3.11, then you can get Trumpet TCP/IP. But if you have WfW3.11 you can use MS's TCP/IP stack. But you may need to find a NDIS driver for you network device; or a "Packet Driver" to "NDIS" shim. Trumpet also works with WfW3.11. Perhaps with WfW3.11, Win32s, and MS's TCP/IP stack, you can use some 32bit Win9x command prompt networking tools. Although, if you can find them, there are plenty of Win16 command prompt networking tools. I guess it depends on what your end goal is. If you go the Desqview and Packet driver muxer route, you can run multiple Dos windows and even run "Standard Mode" Win3x inside a Desqview windows. Then maybe you can have Win3x use Trumpet. Even WfW3.11 can run in standard mode, if you know how to do it.

@Joaquim The "SET BLASTER=" command, in autoexec.bat, is only good for games that examine autoexec.bat for the settings. I personally, have never used one that needed it. But I have been told some do. Otherwise, both SBlaster Emulation and VDMSound set the values by themselves. Many games check the environmental variable %BLASTER% to find out what setting are needed. When running in pure Dos, having "SET BLASTER=" in "autoexec.bat" is the only way the variable gets set. So often, when running in Windows, the setting isn't really even needed.