Hi Gert,   
      
   >>>>>> 1st, check the path in your filedirg.000 file. 2nd, check for the   
   >>>>>> same path in your external.bbb file [tick] section.   
      
   >>>>>>> I have the path for the files and directory made for the files.   
   >>>>>>> Can someone help me up with this or tell me what could be wrong.   
      
   >>>>>> If it's not #1 or #2 above, then check the permissions on your hard   
   >>>>>> drive file areas for user bbbs.  I am not sure about Windows, since I   
   >>>>>> run the Linux version but I thought you also control permissions in   
   >>>>>> the same sort of way with Windows.   
      
   >>>>>> Also check in filedirg.000 for permissions in the area, permissions   
   >>>>>> for R&W should look something like this:   
      
   >>>>> Got and I find a little typus miss where I had write /home/bbbs/ and   
   >>>>> forgot it is /dsds2/home, after the corrected here it got import and   
   >>>>> process some files but then end up with coming with pwd error for node   
   >>>>> and not find out if it is 2:230/152.16 or .18   
   >>>>> It uplink is 2:230/152.16 for fidonet and the bbbs aka as bbs is   
   >>>>> 152.18   
      
   >>>> Kim one day worked with me to make sure the spaces were correct between   
   >>>> the passwords for a node in the external.bbb [nodes] section.  Maybe   
   >>>> the spaces between the passwords is the problem?   
      
   >>>> ; node      spass   apass   ppass   tpass gr  st pa route   
   >>>> ; --------- ------- ------- ------- ----- --- -- -- -------------------   
      
   >>>> 1:261/2      passwrd  passwrd  passwrd  passwrd  XFG H   2 1:261/5   
      
   >>>> If the downlink doesn't want a packet password, you still have to put   
   >>>> in a dash (-) there.   
      
   >>>> 1:261/2      passwrd  passwrd  -      passwrd  XFG H   2 1:261/5   
      
   >>> It is just strange for nodes section when I mean that first nodenumber   
   >>> should be the aka for the system and not the uplink.   
      
   >> NO :)  The first number in the [nodes] section is the DOWNLINK's or   
   >> UPLINK's node number and his password(s).   
      
   >> At the _end_ of the line, where I have 1:261/5 (last field), that is a   
   >> routing statement saying any netmail for another node (1:261/5) should   
   >> get routed to 1:261/2.   
      
      
   >>> In the bbbs sysop.txt doc says it 'This node' for node so it is the aka   
   >>> for bbbs and not the uplinks aka.   
      
   >> You mean this line?   
      
   >> "node        The FidoNet address of this node."   
      
   >> That is refering to "this node you are connecting with", it could be   
   >> your uplink or downlink, not your own node number.   
      
   > Yes and it the right so bbbs aka 2:230/152.18 have in the file node aka to be   
   > uplink 2:230/152.16 and etc,. for zone 115 and 145.   
      
   If you are a registered user, you can get the most recent beta from Kim Heino.   
   Early versions of BBBS only used "@fidonet" for all zones, but in the new beta   
   Kim added "othernet support";So now, in external.bbb you can put   
      
   ===cut here===   
   [ftndomains]   
      
   ^[1-6]: fidonet   
   ^111: stnnet   
   ^115: pascal-net   
   =====cut here===   
   I am not sure, but I don't think that section will work with trial   
   (unregistered) version.   
      
   > I tested out by hatch a new linux game in lnx4games and each time it got to   
   >bbbs for import it got filtered and deleted why bbs not could find or requnize   
   > a unzip.exe from where I have the path for it. so I just to go to sourceforge   
   > and get a dl of unzip here and then copy 3 files for unzip to both \usr\bin\   
   > and \home\bbbs dirs and write 2 new extra lines in external.bbbs file so bbbs   
   >first look in usr\bin and then again the same place if not found then look for   
   > it in its own directory.   
      
   Ok.   
      
   >Now a new zip file was ask to be resend from 2:230/150 to /152.16 and to bbbs,   
   > and it now looks got fine process and put to pub dir lnx4game with fine info   
   > header with both your hdr and mine there.   
      
   Sounds good.   
      
   >>> When I change the bbbs real aka from 2:230/152.18 ( aka for the system   
   >>> to uplinks aka as 2:230/152.16 ) is it working for import mails and   
   >>> files. The system has 2 own akas as 2:230/152.18 115:4500/5 145:2/31 and   
   >>> it uplinks akas is 2:230/152.16 115:4501/17 and 145:2/20   
   >>> Then wil there maybe could be extra intern aka for it as 999:999/15 with   
   >>> uplin as 999:999/2 (for own network dsdsnet).   
      
   >>>>>> ===example filedirg.000===   
   >>>>>> /                /home/ftp/pub                 Root directory   
   >>>>>> /incoming       /home/bbbs/pub/incoming       @rw:fsysop New uploads   
   >>>>>> /comm  /home/ftp/pub/comm/        @rw:fsysop @r:all [COMM] Comm/term   
   >>>>>> Files]   
   >>>>>> /mail   /home/ftp/pub/mail/      @rw:fsysop @r:all [MAIL] Mail   
   >>>>>> Utilities   
   >>>>>> /pdn   /home/ftp/pub/pdn/      @rw:fsysop @r:all [PDN] Programmers   
   >>>>>> Distribution   
   >>>>>> /pdn/pdnai   /home/ftp/pub/pdn/pdnai/      @rw:fsysop @r:all AI   
   >>>>>> (artificial int   
   >>>>>> /pdn/pdnasm   /home/ftp/pub/pdn/pdnasm/    @rw:fsysop @r:all ASM   
   >>>>>> Programming   
   >>>>>> [...]   
   >>>>>> =======example filedirg.000====   
      
   >>>>> Then was there 3 files to lnx4games there got erroring the most time   
   >>>>> but I fin out that in external.bbb and filedirg it was writte as   
   >>>>> lnx4games when harddisk directory was made as lnx4game, so I set bbbs   
   >>>>> to use dir lnx4game.   
      
   >>>> Ok, so that sounds like some progress..   
      
   >>> Nearly but not complete.   
   >>> I have to make some test with PascalNT and Gmsnet akas and see if new   
   >>> echos an areas can be working for those and too some fido areas.   
      
   >> Use that method I mentioned in my last message to you to autocreate the   
   >> msg. areas (bcfg4->Global->Multiadd)   
      
   >>>>>>> I could too like bbbs to just autocreate echomail and file areas   
   >>>>>>> when it is a save way that nothing is getting directly to bbbs from   
   >>>>>>> outside.   
      
   >>>>>> Check out the [badareas] section in external.bbb.. There, you tell   
   >>>>>> bbbs who to expect new echomail areas from and what specific flags to   
   >>>>>> apply to each imported area your Uplink sends to you.  Then you can   
   >>>>>> run   
      
   >>>>>> ./bcfg4 bad  [Autocreate echoareas]   
   >>>>>> and   
   >>>>>> ./bbbs bogus b [Forward bad mail and write them to BBBS]   
      
   >>>>>> IIRC, There isn't a way to automatically add file echos.   
      
   >>>>>> Maybe Torbjorn will mention something I'm not thinking of here since   
   >>>>>> he runs the Windows version.   
      
   >>>>> It should be the same for windows as for linux should I mean, but as   
   >>>>> this is telling about in the sysop files is it missing as section in   
   >>>>> the external.bbb file.   
   >>>>> The bbbs I have it the old bbbs_nt version.   
      
   >>>> If you want me to take a look at your external.bbb file, you can attach   
   >>>> it to an email and send it to me at janis@filegate.net.   
      
   >>> I make some extra test to see if I make things to work right by do some   
   >>> route sending from main system 2:230/150 -> 2:230/152.16 -> 2:230/152.18   
   >>> and for 2 other networks akas to see if the route now is working bbbs see   
   >>> it rights of akas present by names and akas. Then this is done email I   
   >>> you with attach file as like dsds-bbbs.zip of the external.bbbs file.   
      
   >> Ok, sounds good.   
      
   >So it is now if I can get the 2 other akas to work and it will be most for 145   
   > gmsnet as there is getting lot of games in this network now. (It is my own   
   > games hatching to it.)   
      
   Hope it all works for you..   
      
   Take care,   
   Janis   
      
   --- BBBS/Li6 v4.10 Dada-1   
    * Origin: Prism bbs (1:261/38)