jstern@orion.oac.uci.edu (Jeff Stern) (04/09/91)
Thanks everyone for your suggestions, *BUT* I have as yet been unsuccessful getting telbin.exe to work with the WD8003E packet driver. In my packet driver command line I have tried 0x3 instead of 3; in CONFIG.TEL I have tried interrupt=60 instead of ioaddr=60; both interrupt=0 and address=0; and many combinations of above, all to no avail. I *am*, however, successful using *POPmail* and this WD8003E driver, when I load the driver with the command, WD8003E 0x60 0x5 0x280 0xD000 (I am now using interrupt 5, not 3). POPmail (the Beta version) works perfectly with this driver, as far as I can tell. Therefore, I am led to believe it is some configuration of my CONFIG.TEL file I have not yet tried which will do the trick. Therefore, if someone *is using* telbin.exe successfully with the *packet driver* (not the direct hardware) for the WD8003E, I would appreciate it if they sent me 1) the command line they load the WD8003E driver with, AND 2) their CONFIG.TEL file. Thanks. Jeff Stern.
jstern@orion.oac.uci.edu (Jeff Stern) (04/11/91)
Hi, all. Well, these are the results. Thanks to everyone for your suggestions, command-lines, and config.tel files. Since command files really varied greatly (the only common denominator among ALL of them was the 'hardware=packet' line!) and from peoples' command lines I knew I was doing the right thing, the only suggestion left was from a couple of people who said they had had problems with particular versions of Telbin. So I checked... Sure enough, I was using NCSA Telbin 1.2. So I downloaded CUTCP 2.2-D from clarkson and ran that, and *deleted* the ioaddr, interrupt, and addr lines (leaving only the 'hardware=packet' line) from my config.tel file, and as you read, I am writing to you using the packet driver! Ah, success!!! Once again, thanks all. Jeff Stern. ------------------------->jstern@orion.oac.uci.edu<-------------------------