­Hola Mike!

El Jueves 13 Enero 2005 a las 11:25, Albano De Manuel escribi˘ a Mike Ehlert:

 >>> And that's the log:
 >>> 12-Jan 18:47:09 EL01 OS shell : c:\ele\nfoss\nf.bat
 >>> c:\ele\doors\vs\vs3.bat *N
 >>> ! 12-Jan 18:47:11 EL01 Modem initialisation failure

 ME>> It looks like the vs3.bat does something that causes NetFoss
 ME>> to fail. Are you using "Virtual Sysop ]I{ version 3.00df"?
 ME>> This version works fine here with NetFoss 0.9.1...

 ME>> My vs3.bat looks like this:

 ME>> cd\bbs\vs3
 ME>> VSYSOP.EXE -D C:\BBS\NODE%1

 ME>> This tells virtual sysop to look for the drop file in the
 ME>> c:\bbs\node1 directory for node1, and so on...

 AM>  My VS3 version is 3.00df, my vs3.bat is the same (as you told some
 AM> months ago, thanks), but my NetFoss version is just 0.9 and not 0.9.1,
 AM> I suppose they not the same, so I'll download 0.9.1 and see if I have
 AM> the same problem.

 >>> What's does "modem initialisation failure" means?
 >>> My BBS is telnet only :-? That line can be the problem?

 ME>> I think Maarten might not have changed this message when he
 ME>> added telnet support, and it just means that EleBBS could not
 ME>> recover the telnet connection (because NetFoss could not be
 ME>> uninstalled).

 ME>> I think what happens is for some reason your version of vs3
 ME>> is crashing and not releasing itself from memory, so NetFoss
 ME>> is unable to uninstall, and in turn EleBBS is unable to take
 ME>> over the telnet port again.

 AM>  Thanks Mike ;)


 Hi Mike, do you remember my problem? I'm close to get mad with it. I have
tested right now Zoc and it seems that when I run a door using Zoc the BBS
hangs, but it doen't happen when I use Netrunner for example. I'm going to
test other telnet clients to see what happens.

Saludos,

          Albano de Manuel
          FidoNet 2:341/201
          telnet://pucelabbs.dyndns.org

--- FMail/Win32 1.60