Subj : Fastecho.log
To   : Bill Gordon
From : Dan Egli
Date : Fri Jan 30 2004 08:56 am

Thursday January 29 2004 19:56, you wrote to me:

 >> For the logs, try this:

 >> e:
 >> cd\ele\fe
 >> attrib -r -s -h *.*

 >> now see if there is a fastecho.log file there. If Not,
 >> next thing I'd say is to run ChkDsk (or scandisk if you
 >> use a 9x platform).

 >> For the DPMI problem, did you ever try the batch file
 >> idea I sent earlier?


 >> Dan

 BG> Tried it, seems to be NOWHERE on the computer AT ALL.

Strange. If you have a different drive (at least a different drive letter, i.e. 
different partition) try putting your FE.LOG there, and then run it. I take it 
you have all the options enabled in your log setup?

 BG> The batch file did not work for the DPMI problem, either.

Ok, then let's go over things again so we know where things stand. If any of 
this is wrong, let me know.

1) Your O/S is Win2k
2) You are using FE 1.46pl1 (the pl1 is very important because 1.46 had a bug 
in packing outbound netmail into binkley attachments. That bug is fixed in 
1.46pl1.)
3) You are calling FastEcho from a batchfile that resembles this:
@echo off
path C:\WINNT;C:\WINNT\System32;C:\COMPRESS;C:\BBS\ELE;C:\BBS\FE;C:\BBS\ALLFIX
SET FASTECHO=C:\FASTECHO
SET FE=C:\FASTECHO
CD \FASTECHO
FASTECHO TOSS -B
4) You are calling from BinkD. (I still do not understand why if you're using a 
Win32 O/S you don't just use Radius, but that's your decision, not mine).

Dan
Moderator BBS_SURVIVAL

---
 * Origin: Living in interesting times (1:3005/3)

.