• Fastecho.log

    From Bill Gordon@1:123/22 to All on Wed Jan 28 10:32:00 2004
    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.

    ---
    * Origin: Keyboard Solutions telnet://kbd-solutions.dyns.net (1:123/22)
  • From Walter Medak@1:140/51 to Bill Gordon on Wed Jan 28 08:57:19 2004
    Hello Bill.

    28 Jan 04 10:32, you wrote to all:

    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.

    Would it help any if you put a trailing backslash in your set statement?

    e.g. - set fastecho=e:\ele\fe\

    I've found that something as simple as that does wonders on occasion.

    Walter

    --- GoldED+/LNX 1.1.5-31012
    * Origin: Rainbow's End (1:140/51)
  • From Dan Egli@1:3005/3 to Bill Gordon on Wed Jan 28 16:53:04 2004
    Wednesday January 28 2004 10:32, you wrote to All:

    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
    Moderator BBS_SURVIVAL

    ---
    * Origin: Living in interesting times (1:3005/3)
  • From Bill Gordon@1:123/22 to Dan Egli on Thu Jan 29 19:56:52 2004
    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.

    I guess I'm gonna just have to limp along.

    Thanks....

    ---
    * Origin: Keyboard Solutions telnet://kbd-solutions.dyns.net (1:123/22)
  • From Dan Egli@1:3005/3 to Bill Gordon on Fri Jan 30 08:56:40 2004
    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

    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?

    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)
  • From Bill Gordon@1:123/22 to Dan Egli on Fri Jan 30 12:29:06 2004
    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?

    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
    As I said earlier, I am using Win XP

    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.)
    Nope, I'm using 1.46+ (am fixing to upgrade to pl1, though)

    3) You are calling FastEcho from a batchfile that
    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
    10-4 on the batch file

    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)

    ---
    * Origin: Keyboard Solutions telnet://kbd-solutions.dyns.net (1:123/22)
  • From mark lewis@1:3634/12 to Bill Gordon on Fri Jan 30 12:31:06 2004
    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.

    limp?? and there are many who detest the logs since they can actually slow down
    the process as each entry has to be created, written and stored...

    have you tried recreating your configs from scratch? have you tried erasing your reg key file and putting a new copy in place? have you tried this with the
    executables?

    )\/(ark


    * Origin: (1:3634/12)
  • From Bill Gordon@1:123/22 to mark lewis on Fri Jan 30 13:42:10 2004
    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......

    ---
    * Origin: Keyboard Solutions telnet://kbd-solutions.dyns.net (1:123/22)
  • From Bill Gordon@1:123/22 to Dan Egli on Fri Jan 30 13:49:22 2004
    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.

    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 like
    Radius or IRex?
    The reason I am using binkd is at the suggestion of my FidoNet RM, and it seems
    to be the EASIEST mailer one to use. (In fact, it has been super simple to make to work.)

    ---
    * Origin: Keyboard Solutions telnet://kbd-solutions.dyns.net (1:123/22)
  • From Dan Egli@1:3005/3 to Bill Gordon on Fri Jan 30 11:19:26 2004
    Friday January 30 2004 12:29, you wrote to me:

    1) Your O/S is Win2k
    As I said earlier, I am using Win XP
    OK. Couldn't remember, thats why I posted this.

    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.)
    Nope, I'm using 1.46+ (am fixing to upgrade to pl1, though)

    You better if you're gona use either BinkP or Radius. Liks I said, there's a bink packing bug in 1.46 that was fixed in pl1.

    3) You are calling FastEcho from a batchfile that
    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
    10-4 on the batch file

    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).

    Is there a specific reason you are using BinkD vs like Radius or IRex?

    Dan
    Moderator BBS_SURVIVAL

    ---
    * Origin: Living in interesting times (1:3005/3)
  • From Barry Blackford@3:774/605 to Dan Egli on Sat Jan 31 10:00:15 2004
    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?

    Best Rgds, Bazz
    barry@glonet.co.nz
    ---
    * Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)
  • From Barry Blackford@3:774/605 to Dan Egli on Sat Jan 31 10:25:52 2004
    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?

    Best Rgds, Bazz
    barry@glonet.co.nz
    ---
    * Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)
  • From Dan Egli@1:3005/3 to Bill Gordon on Fri Jan 30 15:36:42 2004
    Friday January 30 2004 13:49, you wrote to me:

    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.

    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 like
    Radius or IRex?
    The reason I am using binkd is at the suggestion of my FidoNet RM, and
    it seems to be the EASIEST mailer one to use. (In fact, it has been

    Could be an XP issue. I never tried using the DPMI executables under XP (or if I did I don't remember it). Tell you what. Are you listed in the Nodelist as BinkPable? If so I'll zip up my entire directory (minus node files and my .key)
    and crash binkp it to you. Then you can just modify it to taste and try it. I do think you should look into Radius. It's an awsome program. It has never given me any grief beyond the fact that it does not support BinkP on any port other than 24554. But since I only need to worry about that for one node and I run through a linux gateway that was not too hard to get around. At least until
    Dennis gets a new version out that supports variable BinkP ports. It may not be
    quite as simple as BinkD (I don't know, I never tried BinkD) but it is not hard
    and I'd be happy to help you out with it.

    Dan
    Moderator BBS_SURVIVAL

    ---
    * Origin: Now accepting prisoners at telnet://thedungeon.dnsalias.n (1:3005/3)
  • From Dan Egli@1:3005/3 to Barry Blackford on Fri Jan 30 15:42:18 2004
    Saturday January 31 2004 10:00, you wrote to me:

    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?

    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.

    Dan
    Moderator BBS_SURVIVAL

    ---
    * Origin: Now accepting prisoners at telnet://thedungeon.dnsalias.n (1:3005/3)
  • From Dan Egli@1:3005/3 to Barry Blackford on Fri Jan 30 15:43:56 2004
    Saturday January 31 2004 10:25, you wrote to me:

    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?

    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.

    Dan
    Moderator BBS_SURVIVAL

    ---
    * Origin: Now accepting prisoners at telnet://thedungeon.dnsalias.n (1:3005/3)
  • From mark lewis@1:3634/12 to Dan Egli on Fri Jan 30 19:25:06 2004
    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 believe that FE32 was reserved for native 32bit versions... IINM, the DPMI stuff is still 16bit... it just uses DPMI library calls to access more memory much like EMS and XMS software can/did...

    )\/(ark


    * Origin: (1:3634/12)
  • From mark lewis@1:3634/12 to Bill Gordon on Fri Jan 30 19:29:46 2004
    I have re-installed the entire directory several times, all
    without success.

    geez... i can understand your frustration, then...

    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 guess you've been doing this by completely wiping out the old directory contents (or at least all the files) and then putting in the new ones rather than overwritting, correct? even to a knew directory?

    and this is winXP? its been working under this "OS" with the log files and everything?

    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......

    i hear ya...

    have you tried acquiring a new copy of the archives and going from there?

    hey wait... XP? HOME or?? you are running with admin privs, right? and the bat files and such? it seems wierd but could it be a privs problem where fe can't write the logs to the assigned directory?

    have you tried copying the setup from the XP box to another non-XP box and seeing if it works properly from the copy?

    )\/(ark


    * Origin: (1:3634/12)
  • From mark lewis@1:3634/12 to Bill Gordon on Fri Jan 30 19:30:50 2004
    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.

    its crashing and leaving the busy semaphore behind... we gotta find out why its
    crashing...

    )\/(ark


    * Origin: (1:3634/12)
  • From mark lewis@1:3634/12 to Barry Blackford on Fri Jan 30 19:33:50 2004
    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

    that pl1 (Patch Level One)

    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...

    )\/(ark


    * Origin: (1:3634/12)
  • From Barry Blackford@3:774/605 to Dan Egli on Sat Jan 31 15:12:38 2004
    Hello there Dan!

    30 Jan 04 at 15:42, Dan Egli writes to Barry Blackford:

    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.

    Is that where I get a message that fastecho was unable to open a packet to add to it?

    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!

    Best Rgds, Bazz
    barry@glonet.co.nz
    ---
    * Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)
  • From Barry Blackford@3:774/605 to Dan Egli on Sat Jan 31 15:16:34 2004
    Hello there Dan!

    30 Jan 04 at 15:43, Dan Egli writes to Barry Blackford:

    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.

    Argh! okay!

    Best Rgds, Bazz
    barry@glonet.co.nz
    ---
    * Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)
  • From Barry Blackford@3:774/605 to mark lewis on Sat Jan 31 15:20:32 2004
    Hello there mark!

    30 Jan 04 at 19:33, mark lewis writes to Barry Blackford:

    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!!

    Best Rgds, Bazz
    barry@glonet.co.nz
    ---
    * Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)
  • From Barry Blackford@3:774/605 to Dan Egli on Sat Jan 31 18:46:14 2004
    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

    Best Rgds, Bazz
    barry@glonet.co.nz
    ---
    * Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)
  • From mark lewis@1:3634/12 to Barry Blackford on Sat Jan 31 11:25:56 2004
    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!!

    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...

    )\/(ark


    * Origin: (1:3634/12)
  • From Dan Egli@1:3005/3 to Barry Blackford on Sat Jan 31 11:07:20 2004
    Saturday January 31 2004 18:46, you wrote to me:

    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


    That is something different. The issue is that sometimes FE will not "see" the mail to be packed. It only happens on Crash/Immediate mail and only randomly. I
    put on the patch when I was setting up because I didn't want to take any chances.

    Dan
    Moderator BBS_SURVIVAL

    ---
    * Origin: Now accepting prisoners at telnet://thedungeon.dnsalias.n (1:3005/3)
  • From Dan Egli@1:3005/3 to Barry Blackford on Sat Jan 31 11:50:00 2004
    Saturday January 31 2004 15:12, you wrote to me:

    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!

    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?

    Dan
    Moderator BBS_SURVIVAL

    ---
    * Origin: Now accepting prisoners at telnet://thedungeon.dnsalias.n (1:3005/3)
  • From Rich Wonneberger@1:2624/50 to Mark Lewis on Sat Jan 31 20:17:42 2004
    *** 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.

    Rich
    I-Net turtil@frontiernet.net


    ... Ross Perot Had A 2 Hour Summit With Space Aliens
    ---
    * Origin: Turtil's Pond BBS. Monroe NY 845-783-2106 (1:2624/50)
  • From Barry Blackford@3:774/605 to mark lewis on Sun Feb 1 17:58:08 2004
    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!!

    Best Rgds, Bazz
    barry@glonet.co.nz
    ---
    * Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)
  • From Barry Blackford@3:774/605 to Dan Egli on Sun Feb 1 23:51:55 2004
    Hello there Dan!

    31 Jan 04 at 11:50, Dan Egli writes to Barry Blackford:

    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?

    I just updated to the Jan 30th version of Radius, tried polling you on both and
    it just did a normal looking exit....

    If you wouldn't mind email attaching them to me at the addres below I would appreciate it as the ones I used appear to hve a problem..

    Best Rgds, Bazz
    barry@glonet.co.nz
    ---
    * Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)
  • From mark lewis@1:3634/12 to Rich Wonneberger on Sun Feb 1 11:12:46 2004
    *** 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.

    yup, saw the FREQ Processor report this morning ;-)

    *** 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.

    dunno... i've never really timed it to see <<GG>>

    )\/(ark


    * Origin: (1:3634/12)
  • From mark lewis@1:3634/12 to Barry Blackford on Sun Feb 1 11:22:24 2004
    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!

    BTDT-GTTS %*)

    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!!!

    hunh? -i switch?

    [time passes]

    ahhh... that's a switch for the patcher... ok...

    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

    sounds like the archive got restamped from FTP or something... possibly even by
    someone updating the archive comment or similar... here's the specs on the one i have...

    BUPD124A.RAR, 16736 bytes 06-22-1994

    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...

    )\/(ark


    * Origin: (1:3634/12)
  • From Dan Egli@1:3005/3 to Barry Blackford on Sun Feb 1 12:24:38 2004
    Sunday February 01 2004 17:58, you wrote to mark lewis:

    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!!

    Gotta love that. Tell ya what. Why don't I just compress my patched .exe files and e-mail those to you? :>

    Dan
    Moderator BBS_SURVIVAL

    ---
    * Origin: Now accepting prisoners at telnet://thedungeon.dnsalias.n (1:3005/3)
  • From Barry Blackford@3:774/605 to mark lewis on Tue Feb 3 01:38:59 2004
    Hello there mark!

    01 Feb 04 at 11:22, mark lewis writes to Barry Blackford:
    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

    I'll make a comparison later (thanks)

    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...

    Dan emailed them through to me today, thanks Mark, I'll have another go next weekend.

    Best Rgds, Bazz
    barry@glonet.co.nz
    ---
    * Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)
  • From Barry Blackford@3:774/605 to Dan Egli on Tue Feb 3 01:40:33 2004
    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 :-)

    Best Rgds, Bazz
    barry@glonet.co.nz
    ---
    * Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)
  • From Dan Egli@1:3005/3 to Barry Blackford on Mon Feb 2 07:45:42 2004
    Tuesday February 03 2004 01:40, you wrote to me:

    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 :-)

    Well I upgraded Radius to the Feb-1 beta and it finally sent the files to you. so you should have multiple copies now :> One in your Fido inbound one in your email :>

    Dan
    Moderator BBS_SURVIVAL

    ---
    * Origin: Now accepting prisoners at telnet://thedungeon.dnsalias.n (1:3005/3)