Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!umich!samsung!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!rutgers!njin!gould From: gould@pilot.njin.net (Brian Jay Gould) Newsgroups: comp.windows.ms Subject: Need to drive "virtual COM1". HELP. Message-ID: Date: 9 Aug 90 02:13:03 GMT Organization: NJ InterCampus Network, New Brunswick, N.J. Lines: 16 I want to modify my windows com driver so that my virtual COM1 is actually a named pipe going to a LAN Manager server with a modem pool. Using debug, it appears that comm.drv is used to do the actual "in" and "out" stuff. So if I create a new comm.drv, I can solve my problem. Right? The problem is that I have no idea how comm.drv is supposed to work. Does anyone know anything about it? As a temporary solution, I tie com1 to com2 with a short cable. A separate program moves com2 out to the named pipe and a program on the OS/2 server. I'd really rather have a cleaner solution. -- ************************************************* * Brian Jay Gould - Professional Brain-stormer * *************************************************