From: gangrif@mindless.com   
      
   No, its a single com file, all command line configured, no config files   
   of any sort.   
      
   Stewie Griffin wrote:   
   > Do you have something like a TCP.CFG or NET.CFG associated with that   
   > driver kit ?   
   >   
   > Rick   
   >   
   >   
   > Nathan wrote:   
   >   
   >> Well, here's why i have trouble believing that its a card/driver issue.   
   >>   
   >> I have another install of WG 2.0 on the same hdd.   
   >> if i run that one, it loads, but i have other, non tcp or packet   
   >> driver replated issues which im unable to resolve (missing files, all   
   >> sorts of nastyness), but it DOES fire right up, and i am able to   
   >> telnet to it.   
   >>   
   >> but if i just exit that one, and load the new fresh install, it gives   
   >> this error. So it makes me believe its a setting issue.  What im   
   >> basically looking for is others who may have run into this, and what   
   >> they did to fix it.  I guess i could get another NIC and slap it in   
   >> there (i have enough of them sitting around!) but then i have to dig   
   >> up a packet driver for that nic, which might not be easy anymore.   
   >>   
   >>   
   >>   
   >> Brian wrote:   
   >>   
   >>> I remember first setting the same thing you are years ago and having the   
   >>> same problem. I ended up having my Masters degreed genius guru ISP owner   
   >>> come over and he couldn't fix it either. Turned out that a different   
   >>> brand   
   >>> card slipped right in and fired up. To this day I don't know whether   
   >>> it was   
   >>> the card or the driver, flaw or compatibility issue.   
   >>>   
   >>>   
   >>>   
   >>> "Nathan"  wrote in message   
   >>> news:ececnal0_bO_62HdUSdV9g@ptd.net...   
   >>>   
   >>>> Autoexec.bat reads (literally)   
   >>>> C:\DOS\SMARTDRV.EXE /X   
   >>>> @ECHO OFF   
   >>>> PROMPT $p$g   
   >>>> PATH C:\DOS;c:\;c:\wgserv   
   >>>> SET TEMP=C:\DOS   
   >>>>   
   >>>> REM ======== USDrives IDE BUS CD-ROM Install Modification - Begin   
   >>>> ========   
   >>>> rem C:\CDROMDRV\MSCDEX /V /D:CD003 /M:10   
   >>>> REM ======== USDrives IDE BUS CD-ROM Install Modification - End   
   >>>> ========   
   >>>>   
   >>>> pcipkt 0x60   
   >>>> rem cd wgserv   
   >>>> rem bbs go   
   >>>>   
   >>>> the bbs commands are rem'd for troubleshooting, normally they   
   >>>> wouldnt be   
   >>>> rem'd and it would start the bbs on boot.   
   >>>>   
   >>>> this setup literally works on another install of the bbs, its got other   
   >>>> issues that i cant resolve though, so i decided to start from scratch.   
   >>>> I can only figure that its got to be some setting somewhere ive   
   >>>   
   >>>   
   >>>   
   >>> overlooked.   
   >>>   
   >>>> I set this up about 3 years ago and iirc had the same issue, and   
   >>>> somehow   
   >>>> worked through it.   
   >>>>   
   >>>>   
   >>>> Stewie Griffin wrote:   
   >>>>   
   >>>>> Do you have anything else that might've loaded before the BBS and   
   >>>>> after   
   >>>>> the Packet Driver that might be trying to access the packet   
   >>>>> driver?? and   
   >>>>> holding a lock on it?   
   >>>>>   
   >>>>>   
   >>>>>   
   >>>>> Nathan wrote:   
   >>>>>   
   >>>>>   
   >>>>>> Dos 6.22   
   >>>>>>   
   >>>>>> Same setup that i used when i ran it origionally, in fact, an old   
   >>>>>> semi   
   >>>>>> functional version of my BBS is still on the hdd, that works, as far   
   >>>>>> as the nic and tcp goes, its got other problems though.   
   >>>>>>   
   >>>>>> Stewie Griffin wrote:   
   >>>>>>   
   >>>>>>   
   >>>>>>> Nathan wrote:   
   >>>>>>>   
   >>>>>>>   
   >>>>>>>> This will be a telnet only bbs, so i also installed Vircom's   
   >>>>>>>> MajorTCP/IP.   
   >>>>>>>> After the install, and i configure everything, i get an error   
   >>>>>>>> when i   
   >>>>>>>> try to run the bbs, it says:   
   >>>>>>>> TCPLIB ERROR # 0xA  accessing packet driver   
   >>>>>>>>   
   >>>>>>>> now, the packet driver IS resident, on 0x60   
   >>>>>>>> and the hardware config options are set to the proper address for   
   >>>>>>>> the packet driver.   
   >>>>>>>   
   >>>>>>>   
   >>>>>>>   
   >>>>>>>   
   >>>>>>>   
   >>>>>>>   
   >>>>>>> What O/S are you trying to run this under?   
   >>>>>>>   
   >>>>>   
   >>>   
   >>>   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)