From: corey@tsgc.dyndns.org.remove-n3f-this   
      
     To: Nathan   
     Re: Re: Vircom Major TCP issues   
     By: Nathan to alt.bbs.majorbbs on Mon Jul 19 2004 10:34 pm   
      
    > 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?   
    > >>>   
    > >   
    >   
    > --- Synchronet 3.11c-Win32 NewsLink 1.76   
      
   are you sure it's loading?   
   what about the network?   
   does the packet driver bind to the net layer?   
   do you have the gcomm ICO package? did you try that?   
      
   hmm.   
   worldgroup is a complicated system.   
      
   Corey   
      
   "this message posted on entirely post consumer recycled electrons.."   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)