• What's new?

    From Ruben Figueroa@1:124/5013 to All on Tue Oct 23 13:21:38 2018
    Anything happening lately?
    --- Platinum Xpress/Win/WINServer v3.0pr5
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From Robert Wolfe@1:261/20 to Ruben Figueroa on Tue Oct 23 17:38:06 2018
    Anything happening lately?

    Sadly, not much. The only thing I have done with my own BBS is write a CAPTCH mod into the MAIN.WCX module to prevent script kiddies from trying to log in.

    --- BBBS/2 v4.10 Toy-3
    * Origin: Omicron Theta (BBBS/2) * Southaven MS USA (1:261/20)
  • From Ruben Figueroa@1:124/5014 to Robert Wolfe on Wed Oct 24 08:25:15 2018
    Anything happening lately?

    Sadly, not much. The only thing I have done with my own BBS is write a CAPTCH mod into the MAIN.WCX module to prevent script kiddies from
    trying to log in.


    I sent this message to Winserver and I thought I would send you a copy of
    what I typed. Don't know if you can help, but here goes:

    If I logon directly to the wildcat on the windows 10 (not via the networked wildcat), I can do netmail. Hopefully this makes sense of
    what I am trying to convey.

    On the networked version the path to the wildcat is w:\wc5 and pxw is
    from that point of view on w:\pxw, and on the networked versionin environmnet variables both folders are set in the path.

    So I assume something in the fidomsg.wcx is an issue but I don't have
    the skill or tools to modify that wcx. Assuming that is the issue.

    Thanks in advance for anyone's assistance.

    Ruben Figueroa aka Zazz
    Mystic Prison Board Sysop
    telnet://pb.darktech.org:24
    Web: www.rdfig.net

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Mystic Prison Board*Mesquite Tx*pb.darktech.org:24 (1:124/5014)
  • From Ruben Figueroa@1:124/5014 to Robert Wolfe on Wed Oct 24 08:27:42 2018
    The message I send you on wildcat netmail issue dealt with the ability to
    use netmail from the networked version of wildcat (VM running on XP) While
    main install is on windows 10 pro 32 bit.

    Error is problem loading pxsrv.dll that is called by the fidomsg.wcx

    Ruben Figueroa aka Zazz
    Mystic Prison Board Sysop
    telnet://pb.darktech.org:24
    Web: www.rdfig.net

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Mystic Prison Board*Mesquite Tx*pb.darktech.org:24 (1:124/5014)
  • From LEE GREEN@1:102/401 to RUBEN FIGUEROA on Wed Oct 24 08:10:48 2018
    The message I send you on wildcat netmail issue dealt with the ability to use netmail from the networked version of wildcat (VM running on XP) While main install is on windows 10 pro 32 bit.

    Do you have these 3 files (fidomsg.wcx, pxsrv.dll, pxnl.dll) in your
    WC5 root folder on BOTH PC's (W10 & XP-VM)? also do you have px.ini in WC5/PXDATA directory on both systems?

    It would be nice if you replied to my previous messages about PXW and
    BRE so I know if any of my suggestions worked otherwise I won't waste my
    time replying to you anymore..

    Error is problem loading pxsrv.dll that is called by the fidomsg.wcx


    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Mystic Prison Board*Mesquite Tx*pb.darktech.org:24 (1:124/5014)
    --- Platinum Xpress/Win/WINServer v3.0pr5
    * Origin: TECHWARE BBS - Since 1995 - www.techware.dynip.com/ (1:102/401)
  • From Robert Wolfe@1:261/20 to Ruben Figueroa on Thu Oct 25 03:45:28 2018
    If I logon directly to the wildcat on the windows 10 (not via the
    networked wildcat), I can do netmail. Hopefully this makes sense of
    what I am trying to convey.

    On the networked version the path to the wildcat is w:\wc5 and pxw is
    from that point of view on w:\pxw, and on the networked versionin
    environmnet variables both folders are set in the path.

    So I assume something in the fidomsg.wcx is an issue but I don't have
    the skill or tools to modify that wcx. Assuming that is the issue.

    So you can send netmail when logged on to WC on the same machine WC is running on but not when trying to run from a remote machine. It would help that the WC
    and PXW drives were mapped to the same letter on both the local machine and across the network. That would seem to be the first thing I would check to see
    that everything is working correctly.

    --- BBBS/2 v4.10 Toy-3
    * Origin: Omicron Theta (BBBS/2) * Southaven MS USA (1:261/20)
  • From Robert Wolfe@1:261/20 to LEE GREEN on Thu Oct 25 03:46:52 2018
    <mod hat on>

    It would be nice if you replied to my previous messages about PXW and
    BRE so I know if any of my suggestions worked otherwise I won't waste my
    time replying to you anymore..

    Please take this discussion to netmail. Thanks.

    </mod hat off>

    --- BBBS/2 v4.10 Toy-3
    * Origin: Omicron Theta (BBBS/2) * Southaven MS USA (1:261/20)
  • From LEE GREEN@1:102/401 to ROBERT WOLFE on Thu Oct 25 07:07:18 2018
    SGID: 1:261/20.0 1f451c54
    EPLY: 1:102/401 1f0609a2
    ZUTC: -0500
    HARSET: PC-8
    <mod hat on>

    It would be nice if you replied to my previous messages about PXW and
    BRE so I know if any of my suggestions worked otherwise I won't waste my ->> time replying to you anymore..


    Why netmail what is this conference for if not WC? no thanks.

    His netmail isn't working so I should send him netmail? yeah that makes sense!

    Please take this discussion to netmail. Thanks.

    </mod hat off>

    --- BBBS/2 v4.10 Toy-3
    * Origin: Omicron Theta (BBBS/2) * Southaven MS USA (1:261/20)



    ...What has four legs and an arm? A happy pitbull.
    ---BapStats Module (bsDBASE v6.1 Build 1)

    * Origin: TECHWARE BBS - Since 1995 - www.techware.dynip.com/ (1:102/401)
  • From Ruben Figueroa@1:124/5013 to Robert Wolfe on Thu Oct 25 07:21:28 2018
    So you can send netmail when logged on to WC on the same machine WC is
    running
    on but not when trying to run from a remote machine. It would help that the
    WC
    and PXW drives were mapped to the same letter on both the local machine and across the network. That would seem to be the first thing I would check to
    see
    that everything is working correctly.

    That would have solved my issue. the px.ini in \wc5\pxdata points to
    drive D: whee WC resides. I edited that file and on the remote machine
    I could get fidomsg.wcx to come up properly.

    I still have one issue left, when I type in fido address of where I
    where to send the message, it eventually times out and returns to the
    fido address prompt. So it looks like it can't fido the address or it
    is not finding the nodelist info.

    --- Platinum Xpress/Win/WINServer v3.0pr5
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From Robert Wolfe@1:116/17 to Ruben Figueroa on Sat Nov 3 22:40:16 2018
    The message I send you on wildcat netmail issue dealt with the ability to use netmail from the networked version of wildcat (VM running on XP) While main install is on windows 10 pro 32 bit.

    Error is problem loading pxsrv.dll that is called by the fidomsg.wcx

    Okay, you might want totry putting your PXW directory in your PATH
    statement as your WINServer home directory should be.
    --- Platinum Xpress/Win/WINServer v3.0pr5
    * Origin: Omicron Theta (1:116/17)