­Hola Mike!

El Mi‚rcoles 12 Enero 2005 a las 13:57, Mike Ehlert escribi¢ a All:

 >> 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 c:\bbs\node1
 ME> directory for node1, and so on...

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

 Thanks Mike ;)

Saludos,

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

--- FMail/Win32 1.60