CompuServe Thread

Kevin, I'm still here. Sorry not to have dropped you a line lately. We got a pretty good snow fall this morning. I say we close down Florida and let the gators have it. I've been trying to figure out how to solve my UMB/network adapter/multisound conflicts. It seems with all my adapters loading their drivers low I ran out of room for my dos communications. Fortunately, Windows Magazine to the rescue. There's an article in the current issue with my solution. Seems I have have to use eem386.exe with the 'no frame' switch which means I don't have EMS available. I excluded the 32k buffer needed by the multisound and the space needed by the scsi adapter. I have no idea if the network used UMBs before, but I've been able to load the device drivers high because there is no 64k page frame taking up space in upper memory. It seems win386.exe or the network was mashing the multisound 32k buffer somehow. Well whatever, I have 500k of conventional memory with mscdex and the pioneer driver loaded low and nothing left in upper memory with the three network drivers, multisound 32k buffer, scsi adapter rom area, and win386 as well as the video and bios areas. I guess I've maxed out the machine. Anything less than 500k and no communications. The final report, the multisound doesn't lock up my machine any more. I looked up the switches for eem386.exe and could find no switch called 'no frame'. So I guess my subscription to the magazine saved me from more teeth grinding. Undocumented features!!!! Paul