The window Sizes should be a multiple of the MTU (or MSS,I cannot remember) and Not Just the Maximum.

I use multiples of MTU, still not sure if that's right as some people say MSS, others say MTU, and the odd person says its irrelevant..I do know if you simply use maximum values your connection can become jerky with unexpected timeouts and dropped connections.

I use manual MTU values, one day I might experiment with the window sizes to see what happens with different values and auto MTU/MSS values but it's not a high priority thing for me as what I currently have works, though an MTU of 1500 should work fine for me I've discovered the best for me is around 1000 (which ever number is closer in multiples of eight ). <== changed No. 8 to written eight

If the card volume is low or non existant, standard trick is to check your x:\mmos2\mmpm2.ini file and in any line under the "mixer sections", what the"PARMSTRING=BALANCE=50,VOL=80,INPUT=LINE,GAIN=70,OUTPUT=SPEAKER" line values for GAIN and VOL are.

Not all mixers can change, or change the correct VOL and GAIN parameters and I've had no problems with the mixers for SBAWE32 and 64 when I used them. If you do need to manually change these parameters, boot to maintence mode or boot from a CD/DVD otherwise your edits will be lost. You can sometimes change the values and simply hit the reset button as long as nothing else is running but it is not the recommended way of doing it, you could end up with a corrupt mmpm2.ini file.

As already pointed out, check the cards irq and ports are not conflicting with something else as the AWE drivers are not high IRQ aware, they can only use the old base interrupts. If you can check under a different operating system where the AWE card works to double check the card's settings and adjust those on the drivers line in your config.sys file. I now remember when I let the AWE32/64 driver figure it out automatically that it did not work. driver switches should be in one of the packages.

When putting the MMRE driver before the FXWRAP (injoy firewall) driver, the speed increases a lot.For those using IJFW, I suggest them having the FXWRAP device after the network device

The FXWRAP driver is ment to come after the NIC driver to the outside/external/unprotected enviroment but before the NIC driver to the inside/internal/protected network, otherwise the firewall cannot do its job 100%.

MMALC.OS2 is for the NIC connected to my external modem/routerFXWRAP.SYS is the InJoy firewall driver that will intercept the datastream from MMALC.OS2 and establish itself before the driver the the internal network is loaded.E1000.OS2 is for the NIC connected to my internal network.

Added: Putting another driver with software between interfaces will also slow down a system depending on how much grunt your system has and the number of firewall rules. Just something we live with for the added protection.

If you are using static IP's, put it in your x:\mptn\bin\setup.cmd file on the ipconfig line for your interface, ie

ifconfig lan0 192.168.1.4 netmask 255.255.255.0 -trailers

trailers have been off for linux/unix for a long time, though there it is specified as 'notrailers', it applies to static as well as dynamic IP's.If you are only using dhcp, you can add it as "ifconfig lan0 -trailers" to your setup.cmd file or as you say, to your dhcpcd.cfg file.

I looked at it decade(s) ago and could not see any difference. YMMV

For OS/2, '-trailers' means turn it off, 'trailers' means turn it on. From memory that's how it worked.

Peter is still around though busy with many things. I remember Peter said he was off somewhere and I think he said he would be back next week (or there abouts). Internet in Australia is rather patchy these days, so his connection may have dropped out.

Though.. my connection is up and my traffic is about 1/5 of what it normally is over the past week, and I note that to reach Europe my connection now goes from Perth, across to Melbourne, Sydney, USA West coast, USA East coast, then over to Europe.. Perth to Singapore Undersea cable(s) down more than up lately.

Voice hosts the Weasel list (weasel-list), the last email I've received was Wednesday this week.

send an email to MajorMajor@os2voice.org with the word HELP in the email body

I don't have any triple digit models, happy with what I have, they all still work but went and disassembled a few thinkpads to refresh my memory, all the ones here, the buttons below the touchpad are controlled by the chip on the PCB under the touchpad. The buttons (2 or 3 depending on model) above the touch pad are part of the keyboard which would be logical, keep them as part of the stick so use a different controller though really, everything is programmable.

However..The two buttons below the touchpad on my TP R61 are not integrated, they have separate lines via a lead to the touchpad controller which are simply directed to the plug that goes to the MB.The two buttons below the touchpad on my TP R61i (model without fingerprint thingy) go through the touchpad controller, they do not have separate lines so it seems to be very much a try it and see thing even depending on similar models. Not that this helps Andi but it does answer a sidetracked curiosity.

Maybe Andy's pointing to his setup will help Andi, if not looks likes it's time for some foil. I would not cut any Mylar cables unless you have spares!

In 0-0-touchpad-1.jpg, what happens if you flip the cable grip up and remove the Mylar flat cable?Hard to tell with the picture but do the button's control go back out to the MB or do they go to the touch PCB?Flip the grip up and remove the flat cable and try it. Be gentle with the grip socket though, as they can sometimes break easily.

If the button activation is part of the touch controller board then what I would normally do, would not work either, that is to remove the fuse near the plug on the touchpad PCB (normally a black 0 resistor).

Firefox 45.9.0-3 works fine here, I downloaded the RPM file, unRPM'ed it, copied the @unixroot\usr\lib stuff to my d:\apps\firefox directory after renaming the old one to firefox_old, started fine. I haven't bothered to update anything per the required RPM list as I suspect I'm up to date anyway.

The previous version ran utube videos fine here. I haven't noticed any performance difference or any issues but then its only day 2.I don't use yum/rpm stuff beyond unrpm'ing any rpm files required.

I have checked a few youtube videos and every one I have looked at, University of Western Australia material, Hawkwind, Anatomy, etc, have all played well including audio. No stuttering.FYI: I use an Intel Core2Duo 3GHz (CPU=1 in config.sys) with 4G Ram and a 500G Seagate SATA HD with 64M JFS cache. The only plugins I use are Download Helper and NoScript.