The problem is still with me. I have re-installed everything twice,
and STILL no logfile.
The pathname is e:\ele\fe\fastecho.log, but it is nowhere on c:, d:,
e:, or f:.
I have the set statement in my autoexec.bat file set
fastecho=e:\ele\fe.
The problem is still with me. I have re-installed everything twice,
and STILL no logfile.
The pathname is e:\ele\fe\fastecho.log, but it is nowhere on c:, d:,
e:, or f:.
I have the set statement in my autoexec.bat file set
fastecho=e:\ele\fe.
This is really making me crazy.
Also, I have had no luck with the dpmi problem, either.
Sure could use some help. Tobias has not answered yet.
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
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
Tried it, seems to be NOWHERE on the computer AT ALL.
The batch file did not work for the DPMI problem, either.
As I said earlier, I am using Win XPTried 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?
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 importantNope, I'm using 1.46+ (am fixing to upgrade to pl1, though)
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 that10-4 on the batch file
resembles this:
@echo off
path C:\WINNT;C:\WINNT\Syste m32;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)
Tried it, seems to be NOWHERE on the computer AT ALL.
The batch file did not work for the DPMI problem, either.
I guess I'm gonna just have to limp along.
Ok.. And you're using the DOS or the DPMI version ofI have installed the DPMI version, changed everything over to the correct exec files, but all I get is a mysterious febusy.0 file appearing out of the blue, for no reason. And when I DO delete it, and crank up fastec16.exe, all it does
FastEcho?
Reason I ask is that after reviewing my setup I find thatThe reason I am using binkd is at the suggestion of my FidoNet RM, and it seems
I'm using the DOS sersion. I was thinking I was using the
DPMI executables, and they are there, but the batch file
calls fastecho.exe, not fastec16.exe which is the DPMI
version (Why he didn't name it fastec32 is beyond me.
fastec16 sounds like a 16 bit app, not a 32bit DPMI app).
Is there a specific reason you are using BinkD vs like
Radius or IRex?
OK. Couldn't remember, thats why I posted this.1) Your O/S is Win2kAs I said earlier, I am using Win XP
2) You are using FE 1.46pl1 (the pl1 is very importantNope, I'm using 1.46+ (am fixing to upgrade to pl1, though)
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 that10-4 on the batch file
resembles this:
@echo off
path C:\WINNT;C:\WINNT\Syste
m32;C:\COMPRESS;C:\BBS\ELE;C:\BBS\FE;C:\BBS\ALLFIX
SET FASTECHO=C:\FASTECHO
SET FE=C:\FASTECHO
CD \FASTECHO
FASTECHO TOSS -B
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.)
Ok.. And you're using the DOS or the DPMI version of FastEcho?
Reason I ask is that after reviewing my setup I find that I'm using the DOS sersion. I was thinking I was using the DPMI executables, and they are there, but the batch file calls fastecho.exe, not fastec16.exe which is the DPMI version (Why he didn't name it fastec32 is beyond me. fastec16 sounds like a 16 bit app, not a 32bit DPMI app).
Ok.. And you're using the DOS or the DPMI version ofI have installed the DPMI version, changed everything over to the
FastEcho?
correct exec files, but all I get is a mysterious febusy.0 file
appearing out of the blue, for no reason. And when I DO delete it,
and crank up fastec16.exe, all it does is cycle back to dos and leave
the febusy.0 file in the directory.
Reason I ask is that after reviewing my setup I find that
I'm using the DOS sersion. I was thinking I was using the
DPMI executables, and they are there, but the batch file
calls fastecho.exe, not fastec16.exe which is the DPMI
version (Why he didn't name it fastec32 is beyond me.
fastec16 sounds like a 16 bit app, not a 32bit DPMI app).
Is there a specific reason you are using BinkD vs likeThe reason I am using binkd is at the suggestion of my FidoNet RM, and
Radius or IRex?
it seems to be the EASIEST mailer one to use. (In fact, it has been
Hello there Dan!
30 Jan 04 at 08:56, Dan Egli writes to Bill Gordon:
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.)
Where do you get the pli version? I had never heard of it before, I
use the bink outbound and was not aware of any problems?
Hello there Dan!
30 Jan 04 at 11:19, Dan Egli writes to Bill Gordon:
Ok.. And you're using the DOS or the DPMI version of FastEcho?
Reason I ask is that after reviewing my setup I find that I'm
using the
DOS sersion. I was thinking I was using the DPMI executables, and
they are
there, but the batch file calls fastecho.exe, not fastec16.exe
which is
the DPMI version (Why he didn't name it fastec32 is beyond me.
fastec16
sounds like a 16 bit app, not a 32bit DPMI app).
You can easily just rename your executable?
fastecho.exe, not fastec16.exe which is the DPMI version (Why
he didn't name it fastec32 is beyond me. fastec16 sounds like
a 16 bit app, not a 32bit DPMI app).
I have re-installed the entire directory several times, all
without success.
I have the original copy of the registration key, and have
replaced the key in the directory each time with a fresh copy
of the original.
I know the log files are really not necessary, but I just hate
when I can't find what should be there.
Goes back to my investigator days......
Ok.. And you're using the DOS or the DPMI version of
FastEcho?
I have installed the DPMI version, changed everything over to
the correct exec files, but all I get is a mysterious febusy.0
file appearing out of the blue, for no reason. And when I DO
delete it, and crank up fastec16.exe, all it does is cycle
back to dos and leave the febusy.0 file in the directory.
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.)
Where do you get the pli version? I had never heard of it
before, I use the bink outbound and was not aware of any
problems?
fixed in 1.46pl1.)
Where do you get the pli version? I had never heard of it before, I
use the bink outbound and was not aware of any problems?
I got it from archives.thebbs.org. If you're IP capable or TXable I'll zip the patch set to you. Changes 1.46 to 1.46.1. The bug is only occuring randomly in attempts to pack crash or immediate mail to a node. Fastecho randomly refuses to do it in 1.46. 1.46.1 fixed that.
You can easily just rename your executable?
If it is not rtm.exe or dos4gw.exe then why not? But I have not renamed them. I was referring to the name that Tobias released them under.
before, I use the bink outbound and was not aware of any
problems?
i forget exactly what the problem was but it didn't show up in some circumstances...
fixed in 1.46pl1.)
Is that where I get a message that fastecho was unable to open a packet to add to it?
before, I use the bink outbound and was not aware of any
problems?
i forget exactly what the problem was but it didn't show
up in some circumstances...
I can't believe I never heard about it mark, weird!!
Hello there Dan!
31 Jan 04 at 15:12, Barry Blackford writes to Dan Egli:
fixed in 1.46pl1.)
Is that where I get a message that fastecho was unable to open a
packet to
add to it?
This is an example of what I was meaning...
─ Netmail (3:774/605) ──────────────────────────────────────────────── NETMAIL Msg : #25 [27] Rcv Uns Pvt Lo Fr
Fatch 3:774/605 31 Jan 04 17:22:35 To :
Barry Blackf 3:774605 31 Jan 04
18:45:16 Subj : PAC
erorreport ─0k──────────────────────────────────────────────────────── ──────────────────── Error opening D:\RADIUS\OUT.001\01130137.CLO: Permission denied Error opening D:\RADIUS\OUT.001\01130137.CLO:
Permission denied
If you run something with BinkP (or Telnet etc) my system can be
crashed at glonet.co.nz or mail it to me at the address in my
signature, I had never heard of this patch, so I appreciate that you brought it to my attention, many thanks!
FASTECHO FDN... BUPD124A.RAR is the released archive containing the
patching program needed to apply the distributed patch...
time, though... either FREQ via fido protocols over telnet or visit my
web or ftp site and grab them that way... the pipeline is not very
large so be warned ahead of time...
v1.46 was released on April 1, 1997... v1.46.pl1 patch file was released two days later on April 3, 1997... all were hatched in the FASTECHO FDN... BUPD124A.RAR is the released archive containing the patching program needed to apply the distributed patch...
all are available from me if needed... my POTS line is "down" at
this time, though... either FREQ via fido protocols over telnet
or visit my web or ftp site and grab them that way... the
pipeline is not very large so be warned ahead of time...
I tried crashing it to you, but for some reason our Radius's don't want to talk right. My logs keep saying "nothing for them". Try polling me at thedungeon.dnsalias.net. Failing that, I'll e-mail them to you. Standard mail or TransX?
*** Quoting Mark Lewis to Barry Blackford dated 01-31-04 ***
FASTECHO FDN... BUPD124A.RAR is the released archive containing the
patching program needed to apply the distributed patch...
Mark,
Just got it from you.
*** Quoting Mark Lewis to Barry Blackford dated 01-31-04 ***
time, though... either FREQ via fido protocols over telnet or visit my
web or ftp site and grab them that way... the pipeline is not very
large so be warned ahead of time...
Total time for the 16k file was 31 seconds. :}
This did include connecting and hand shacking.
v1.46 was released on April 1, 1997... v1.46.pl1
patch file was released two days later on April
3, 1997... all were hatched in the FASTECHO FDN...
BUPD124A.RAR is the released archive containing
the patching program needed to apply the
distributed patch...
Found it on my own system!!!! sheesh!
all are available from me if needed... my POTS line is "down" at
this time, though... either FREQ via fido protocols over telnet
or visit my web or ftp site and grab them that way... the
pipeline is not very large so be warned ahead of time...
No problems mark, when I ran it on the update I have here I
get:
fastecho.exe: No such file or directory (no problem)
BUPDATE: bad file length of source 'fastec16.exe' Hmm, this
was a fresh extracted file which I had to use the -i switch to
ignore time!!!
fastech2.exe: No such file or directory (no problem)
BUPDATE: sum check failed 'areafix.hlp' (no problem _ edited
the original)
My version of BUPD124A.RAR is dated 17/July/98
Argh!! nothing is ever simple!!
Hello there mark!
31 Jan 04 at 11:25, mark lewis writes to Barry Blackford:
v1.46 was released on April 1, 1997... v1.46.pl1 patch file was
released
two days later on April 3, 1997... all were hatched in the
FASTECHO FDN...
BUPD124A.RAR is the released archive containing the patching
program
needed to apply the distributed patch...
Found it on my own system!!!! sheesh!
all are available from me if needed... my POTS line is "down" at
this time, though... either FREQ via fido protocols over telnet
or visit my web or ftp site and grab them that way... the
pipeline is not very large so be warned ahead of time...
No problems mark, when I ran it on the update I have here I get: fastecho.exe: No such file or directory (no problem)
BUPDATE: bad file length of source 'fastec16.exe' Hmm, this was a
fresh extracted file which I had to use the -i switch to ignore
time!!!
fastech2.exe: No such file or directory (no problem)
BUPDATE: sum check failed 'areafix.hlp' (no problem _ edited the
original)
My version of BUPD124A.RAR is dated 17/July/98
Argh!! nothing is ever simple!!
it was delivered here 09-29-1997 and contains the following...
BUPDATE DOC 2391 06/22/94 12:45 5857 BEST
BUPDATE EXE 13835 12/19/93 02:42 24326 BEST
the first number is the compressed size and the second is the
actual
uncompressed size...
Argh!! nothing is ever simple!!
wierd... very wierd... i'll admit, its been a long time since i applied the patches... AIR, i had installed the originals and then just ran the patch program with the patch file a few days later...
so, did you get the patches all done or do you need someone to email the final .EXEs to you? i've all of them here...
Gotta love that. Tell ya what. Why don't I just compress my patched .exe files and e-mail those to you? :>
Hello there Dan!
01 Feb 04 at 12:24, Dan Egli writes to Barry Blackford:
Gotta love that. Tell ya what. Why don't I just compress my
patched .exe
files and e-mail those to you? :>
Ummm, sounds too easy..... that might have an effect, I have backed
the whole dir up just incase of problems :-)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,033 |
Nodes: | 15 (0 / 15) |
Uptime: | 216:00:46 |
Calls: | 529 |
Calls today: | 23 |
Files: | 95,154 |
D/L today: |
4,433 files (587M bytes) |
Messages: | 298,881 |
Posted today: | 12 |