• Windows 10

    From JERRY SEHL@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Fri, 31 Jul 2015 15:50:27 -0400
    From: JERRY SEHL
    To: all
    Subject: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1438372227.32.0@winserver.com>
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 16

    I installed after a long download, it took a while a a bunch of restarts
    until it was ready, however in starting it up with my winserver all seemed well when I received messages and sent some, but in checking my own
    websites found they didn't exist.

    I made an appointment for a call from MS and waited till 5 pm the next day
    and viola a phone call but was quickly handed over to another then another where I was on hold for 1 1/2 hours. The service tech advisor quickly told
    me he didn't understand as it wasn't a Microsoft product etc etc.

    A feature to roll back to Windows 7 is built in good for 30 days after the upgrade, I used it and all is back well again.

    But did find that 32 bit support exists!


    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From CRAIG STRUTT@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Wed, 12 Aug 2015 15:12:50 -0400
    From: CRAIG STRUTT
    To: JERRY SEHL
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439406770.32.1438372227@winserver.com>
    References: <1438372227.32.0@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 35

    I'm up and running on Windows 10 64bit (upgrading from XP so a BIG jump). The only problem I am having relates to my MySQL and PHP setup. Admittedly it's my fault since I was running PHP 4.3 and MySql 3.4. I can't seem to get the older PHP to work with a newer (had to reinstall) MySql. I
    remember the configuration was a bear in the beginning. For that reason, since it worked, I didn't touch it. Now I'm going to have to spend hours reading and reconfiguring to get it all back and running as it should be.

    Not Winserver's problem. Not Windows 10 problem. If there is a "best"
    place to start, feel free to point me in that direction (anyone...)

    On 7/31/2015 3:50 PM, JERRY SEHL wrote to all:

    I installed after a long download, it took a while a a bunch of restarts until it was ready, however in starting it up with my winserver all
    seemed
    well when I received messages and sent some, but in checking my own websites found they didn't exist.

    I made an appointment for a call from MS and waited till 5 pm the next
    day
    and viola a phone call but was quickly handed over to another then
    another
    where I was on hold for 1 1/2 hours. The service tech advisor quickly
    told
    me he didn't understand as it wasn't a Microsoft product etc etc.

    A feature to roll back to Windows 7 is built in good for 30 days after
    the
    upgrade, I used it and all is back well again.

    But did find that 32 bit support exists!



    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Thu, 13 Aug 2015 06:11:18 -0400
    From: MICHAEL PURDY
    To: CRAIG STRUTT
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439460678.32.1439406770@winserver.com>
    References: <1439406770.32.1438372227@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 83

    If you check the unsupported branches list

    http://php.net/eol.php

    You will note the 3.x and 4.x has been End of Life for many years.

    The expectation when running MySQL 5.x is that you will have migrated to
    PHP 5.x.

    There are differences in the Extensions:

    extension=php_mysql.dll
    extension=php_mysqli.dll

    used in PHP 3.x, 4.x and 5.x. They are not compatible.

    I suggest in your PHP.INI you temporarily set

    error_reporting = E_ALL
    display_errors = on
    display_startup_errors = on

    Which when a script is called will show any Startup errors such as DLLs
    failing to load.

    You could of course set the logging to file should you prefer.

    error_log = \php\phperror.log

    A simple test script such as

    <?php
    phpinfo();


    Run at the CLI against PHP.EXE e.g.

    php test.php > debug.txt

    Would send all of the information necessary for debugging to a text file
    called DEBUG.TXT



    On 8/12/2015 3:12 PM, CRAIG STRUTT wrote to JERRY SEHL:

    I'm up and running on Windows 10 64bit (upgrading from XP so a BIG jump). The only problem I am having relates to my MySQL and PHP setup.
    Admittedly
    it's my fault since I was running PHP 4.3 and MySql 3.4. I can't seem to get the older PHP to work with a newer (had to reinstall) MySql. I remember the configuration was a bear in the beginning. For that reason, since it worked, I didn't touch it. Now I'm going to have to spend hours reading and reconfiguring to get it all back and running as it should be.

    Not Winserver's problem. Not Windows 10 problem. If there is a "best" place to start, feel free to point me in that direction (anyone...)

    On 7/31/2015 3:50 PM, JERRY SEHL wrote to all:

    I installed after a long download, it took a while a a bunch of restarts until it was ready, however in starting it up with my winserver all
    seemed
    well when I received messages and sent some, but in checking my own websites found they didn't exist.

    I made an appointment for a call from MS and waited till 5 pm the next
    day
    and viola a phone call but was quickly handed over to another then
    another
    where I was on hold for 1 1/2 hours. The service tech advisor quickly
    told
    me he didn't understand as it wasn't a Microsoft product etc etc.

    A feature to roll back to Windows 7 is built in good for 30 days after
    the
    upgrade, I used it and all is back well again.

    But did find that 32 bit support exists!




    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From JERRY SEHL@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Thu, 13 Aug 2015 09:23:12 -0400
    From: JERRY SEHL
    To: CRAIG STRUTT
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439472192.32.1439406770@winserver.com>
    References: <1439406770.32.1438372227@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 52

    Whast did you have to do with the networking to recognize a workgroup or
    did you setup a home group as it seems to ask?


    On 8/12/2015 3:12 PM, CRAIG STRUTT wrote to JERRY SEHL:

    I'm up and running on Windows 10 64bit (upgrading from XP so a BIG
    jump).
    The only problem I am having relates to my MySQL and PHP setup.
    Admittedly
    it's my fault since I was running PHP 4.3 and MySql 3.4. I can't
    seem to
    get the older PHP to work with a newer (had to reinstall) MySql. I remember the configuration was a bear in the beginning. For that
    reason,
    since it worked, I didn't touch it. Now I'm going to have to spend
    hours
    reading and reconfiguring to get it all back and running as it should
    be.

    Not Winserver's problem. Not Windows 10 problem. If there is a "best" place to start, feel free to point me in that direction (anyone...)

    On 7/31/2015 3:50 PM, JERRY SEHL wrote to all:

    I installed after a long download, it took a while a a bunch of
    restarts
    until it was ready, however in starting it up with my winserver all
    seemed
    well when I received messages and sent some, but in checking my own websites found they didn't exist.

    I made an appointment for a call from MS and waited till 5 pm the
    next
    day
    and viola a phone call but was quickly handed over to another then
    another
    where I was on hold for 1 1/2 hours. The service tech advisor
    quickly
    told
    me he didn't understand as it wasn't a Microsoft product etc etc.

    A feature to roll back to Windows 7 is built in good for 30 days
    after
    the
    upgrade, I used it and all is back well again.

    But did find that 32 bit support exists!




    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From CRAIG STRUTT@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Thu, 13 Aug 2015 17:42:26 -0400
    From: CRAIG STRUTT
    To: JERRY SEHL
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439502146.32.1439472192@winserver.com>
    References: <1439472192.32.1439406770@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 107

    I assigned it to my workgroup (I don't use a domain) and used the
    following settings on network security:

    Under Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings

    Private
    Turn on Network Discovery
    Automatic Detection of attached devices

    Turn on File and Print Sharing
    Use User accounts and passwords to connect to other computers


    Guest or Public (really doesn't matter since we'll always be private)

    Turn OFF Network Discovery
    Turn On file and Print Sharing

    All Networks (again - private secure Network, so I'm not so worried and
    I WANT access from within my network to control the machine)

    Turn ON Sharing
    Use 128bit encryptions
    Turn OFF Password protected sharing.

    I have a mixture of Android / WinXP / Win7 / Win8.1 / Win 10 machines.

    I have access from all of them locally, and with the proper ports
    forwarded, and the firewall open on the server, outside access works
    just fine.





    On 8/13/2015 9:23 AM, JERRY SEHL wrote to CRAIG STRUTT:

    Whast did you have to do with the networking to recognize a
    workgroup or
    did you setup a home group as it seems to ask?


    On 8/12/2015 3:12 PM, CRAIG STRUTT wrote to JERRY SEHL:

    I'm up and running on Windows 10 64bit (upgrading from XP so a
    BIG
    jump).
    The only problem I am having relates to my MySQL and PHP setup.
    Admittedly
    it's my fault since I was running PHP 4.3 and MySql 3.4. I
    can't
    seem to
    get the older PHP to work with a newer (had to reinstall) MySql.
    I
    remember the configuration was a bear in the beginning. For
    that
    reason,
    since it worked, I didn't touch it. Now I'm going to have to
    spend
    hours
    reading and reconfiguring to get it all back and running as it
    should
    be.

    Not Winserver's problem. Not Windows 10 problem. If there is a
    "best"
    place to start, feel free to point me in that direction
    (anyone...)

    On 7/31/2015 3:50 PM, JERRY SEHL wrote to all:

    I installed after a long download, it took a while a a bunch
    of
    restarts
    until it was ready, however in starting it up with my
    winserver all
    seemed
    well when I received messages and sent some, but in checking
    my own
    websites found they didn't exist.

    I made an appointment for a call from MS and waited till 5 pm
    the
    next
    day
    and viola a phone call but was quickly handed over to another
    then
    another
    where I was on hold for 1 1/2 hours. The service tech advisor
    quickly
    told
    me he didn't understand as it wasn't a Microsoft product etc
    etc.

    A feature to roll back to Windows 7 is built in good for 30
    days
    after
    the
    upgrade, I used it and all is back well again.

    But did find that 32 bit support exists!





    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From CRAIG STRUTT@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Thu, 13 Aug 2015 18:07:20 -0400
    From: CRAIG STRUTT
    To: MICHAEL PURDY
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439503640.32.1439460678@winserver.com>
    References: <1439460678.32.1439406770@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 115

    Thanks Mike. I'm *trying* to do just that. Thus far, the shutting
    down, and starting up again of the server just to change a setting in
    PHP.INI is an issue.

    I still don't have the auto shutdown routines working correctly, and
    the auto startup works on reboot, but not when the machine is already
    running (can't figure that one out!) WcStart.exe -run works fine in
    the scheduler with an ON logon high privilage, but not after the
    machine is running. <sigh> I WILL get this.

    On 8/13/2015 6:11 AM, MICHAEL PURDY wrote to CRAIG STRUTT:

    If you check the unsupported branches list

    http://php.net/eol.php

    You will note the 3.x and 4.x has been End of Life for many years.

    The expectation when running MySQL 5.x is that you will have
    migrated to
    PHP 5.x.

    There are differences in the Extensions:

    extension=php_mysql.dll
    extension=php_mysqli.dll

    used in PHP 3.x, 4.x and 5.x. They are not compatible.

    I suggest in your PHP.INI you temporarily set

    error_reporting = E_ALL
    display_errors = on
    display_startup_errors = on

    Which when a script is called will show any Startup errors such as
    DLLs
    failing to load.

    You could of course set the logging to file should you prefer.

    error_log = \php\phperror.log

    A simple test script such as

    <?php
    phpinfo();


    Run at the CLI against PHP.EXE e.g.

    php test.php > debug.txt

    Would send all of the information necessary for debugging to a text
    file
    called DEBUG.TXT



    On 8/12/2015 3:12 PM, CRAIG STRUTT wrote to JERRY SEHL:

    I'm up and running on Windows 10 64bit (upgrading from XP so a
    BIG jump).
    The only problem I am having relates to my MySQL and PHP setup.
    Admittedly
    it's my fault since I was running PHP 4.3 and MySql 3.4. I
    can't seem to
    get the older PHP to work with a newer (had to reinstall) MySql.
    I
    remember the configuration was a bear in the beginning. For
    that reason,
    since it worked, I didn't touch it. Now I'm going to have to
    spend hours
    reading and reconfiguring to get it all back and running as it
    should be.

    Not Winserver's problem. Not Windows 10 problem. If there is a
    "best"
    place to start, feel free to point me in that direction
    (anyone...)

    On 7/31/2015 3:50 PM, JERRY SEHL wrote to all:

    I installed after a long download, it took a while a a bunch
    of restarts
    until it was ready, however in starting it up with my
    winserver all
    seemed
    well when I received messages and sent some, but in checking
    my own
    websites found they didn't exist.

    I made an appointment for a call from MS and waited till 5 pm
    the next
    day
    and viola a phone call but was quickly handed over to another
    then
    another
    where I was on hold for 1 1/2 hours. The service tech advisor
    quickly
    told
    me he didn't understand as it wasn't a Microsoft product etc
    etc.

    A feature to roll back to Windows 7 is built in good for 30
    days after
    the
    upgrade, I used it and all is back well again.

    But did find that 32 bit support exists!





    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From CRAIG STRUTT@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Thu, 13 Aug 2015 18:27:58 -0400
    From: CRAIG STRUTT
    To: ALL
    Subject: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439504878.32.0@winserver.com>
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 10

    Other interesting things.

    WcStart was hanging up seemingly after everything started. I found out
    that I had forgotten to set the compatibility mode for WcMail (the last program started). I set them all as WinXP SP3 administrative priv.

    I'm hoping that squashes that issue.

    Now on to learning what's going on with PHP... issues with force-cgi-
    redirect apparently.
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Thu, 13 Aug 2015 18:29:09 -0400
    From: MICHAEL PURDY
    To: CRAIG STRUTT
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439504949.32.1439503640@winserver.com>
    References: <1439503640.32.1439460678@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 129

    Changes to the PHP.INI file are dynamic and do not require any
    shutdown/restart with Wildcat!.

    If you are using another web server then a restart maybe required.

    Assuming you can connect successfully to MySQL using the CLI mysql command
    tool or a GUI tool like SQLyog https://github.com/webyog/sqlyog-community
    then you need to go through the PHP specific troubleshooting process.



    On 8/13/2015 6:07 PM, CRAIG STRUTT wrote to MICHAEL PURDY:

    Thanks Mike. I'm *trying* to do just that. Thus far, the shutting
    down, and starting up again of the server just to change a setting in PHP.INI is an issue.

    I still don't have the auto shutdown routines working correctly, and
    the auto startup works on reboot, but not when the machine is already running (can't figure that one out!) WcStart.exe -run works fine in
    the scheduler with an ON logon high privilage, but not after the
    machine is running. <sigh> I WILL get this.

    On 8/13/2015 6:11 AM, MICHAEL PURDY wrote to CRAIG STRUTT:

    If you check the unsupported branches list

    http://php.net/eol.php

    You will note the 3.x and 4.x has been End of Life for many years.

    The expectation when running MySQL 5.x is that you will have
    migrated to
    PHP 5.x.

    There are differences in the Extensions:

    extension=php_mysql.dll
    extension=php_mysqli.dll

    used in PHP 3.x, 4.x and 5.x. They are not compatible.

    I suggest in your PHP.INI you temporarily set

    error_reporting = E_ALL
    display_errors = on
    display_startup_errors = on

    Which when a script is called will show any Startup errors such as
    DLLs
    failing to load.

    You could of course set the logging to file should you prefer.

    error_log = \php\phperror.log

    A simple test script such as

    <?php
    phpinfo();


    Run at the CLI against PHP.EXE e.g.

    php test.php > debug.txt

    Would send all of the information necessary for debugging to a text
    file
    called DEBUG.TXT



    On 8/12/2015 3:12 PM, CRAIG STRUTT wrote to JERRY SEHL:

    I'm up and running on Windows 10 64bit (upgrading from XP so a
    BIG jump).
    The only problem I am having relates to my MySQL and PHP setup.
    Admittedly
    it's my fault since I was running PHP 4.3 and MySql 3.4. I
    can't seem to
    get the older PHP to work with a newer (had to reinstall) MySql.
    I
    remember the configuration was a bear in the beginning. For
    that reason,
    since it worked, I didn't touch it. Now I'm going to have to
    spend hours
    reading and reconfiguring to get it all back and running as it
    should be.

    Not Winserver's problem. Not Windows 10 problem. If there is a
    "best"
    place to start, feel free to point me in that direction
    (anyone...)

    On 7/31/2015 3:50 PM, JERRY SEHL wrote to all:

    I installed after a long download, it took a while a a bunch
    of restarts
    until it was ready, however in starting it up with my
    winserver all
    seemed
    well when I received messages and sent some, but in checking
    my own
    websites found they didn't exist.

    I made an appointment for a call from MS and waited till 5 pm
    the next
    day
    and viola a phone call but was quickly handed over to another
    then
    another
    where I was on hold for 1 1/2 hours. The service tech advisor
    quickly
    told
    me he didn't understand as it wasn't a Microsoft product etc
    etc.

    A feature to roll back to Windows 7 is built in good for 30
    days after
    the
    upgrade, I used it and all is back well again.

    But did find that 32 bit support exists!






    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Thu, 13 Aug 2015 20:37:08 -0400
    From: MICHAEL PURDY
    To: CRAIG STRUTT
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439512628.32.1439504878@winserver.com>
    References: <1439504878.32.0@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 20

    cgi.force_redirect is an Apache concept and not wildcat related. In all versions of PHP it should be set as:

    cgi.force_redirect = 0



    On 8/13/2015 6:27 PM, CRAIG STRUTT wrote to ALL:

    Other interesting things.

    WcStart was hanging up seemingly after everything started. I found out that I had forgotten to set the compatibility mode for WcMail (the last program started). I set them all as WinXP SP3 administrative priv.

    I'm hoping that squashes that issue.

    Now on to learning what's going on with PHP... issues with force-cgi- redirect apparently.

    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From CRAIG STRUTT@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Fri, 14 Aug 2015 10:28:56 -0400
    From: CRAIG STRUTT
    To: MICHAEL PURDY
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439562536.32.1439504949@winserver.com>
    References: <1439504949.32.1439503640@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 147

    Thanks for you help. Yes, my issues are directly related to depreciated commands (mysql_connect). I'm working through those.

    I still have two strange issues which I'll have to touch base with Hector
    on. When the system powers up, WCMail takes up nearly 100% of the
    processor power and WcStart continues to run in the background. Although restarting WcMail takes care of it, I've also found (strangely enough) that setting it's affinity to 2 CPUs (running a quad core) immediately stops the high CPU usage (drops to 0) and then I can put it back on all cores and it runs fine. I've left WcStart running this time (normally I force it to
    stop) and I'm watching it slowly reduce it's memory footprint. I want to
    see if it stops on it's own eventually (a settings issue) or if it keeps running. Right now, it's taking 25% of the CPU cycles.

    On 8/13/2015 6:29 PM, MICHAEL PURDY wrote to CRAIG STRUTT:

    Changes to the PHP.INI file are dynamic and do not require any shutdown/restart with Wildcat!.

    If you are using another web server then a restart maybe required.

    Assuming you can connect successfully to MySQL using the CLI mysql
    command
    tool or a GUI tool like SQLyog https://github.com/webyog/sqlyog-community then you need to go through the PHP specific troubleshooting process.



    On 8/13/2015 6:07 PM, CRAIG STRUTT wrote to MICHAEL PURDY:

    Thanks Mike. I'm *trying* to do just that. Thus far, the shutting down, and starting up again of the server just to change a setting in PHP.INI is an issue.

    I still don't have the auto shutdown routines working correctly, and
    the auto startup works on reboot, but not when the machine is already running (can't figure that one out!) WcStart.exe -run works fine in
    the scheduler with an ON logon high privilage, but not after the
    machine is running. <sigh> I WILL get this.

    On 8/13/2015 6:11 AM, MICHAEL PURDY wrote to CRAIG STRUTT:

    If you check the unsupported branches list

    http://php.net/eol.php

    You will note the 3.x and 4.x has been End of Life for many years.

    The expectation when running MySQL 5.x is that you will have
    migrated to
    PHP 5.x.

    There are differences in the Extensions:

    extension=php_mysql.dll
    extension=php_mysqli.dll

    used in PHP 3.x, 4.x and 5.x. They are not compatible.

    I suggest in your PHP.INI you temporarily set

    error_reporting = E_ALL
    display_errors = on
    display_startup_errors = on

    Which when a script is called will show any Startup errors such as
    DLLs
    failing to load.

    You could of course set the logging to file should you prefer.

    error_log = \php\phperror.log

    A simple test script such as

    <?php
    phpinfo();


    Run at the CLI against PHP.EXE e.g.

    php test.php > debug.txt

    Would send all of the information necessary for debugging to a text
    file
    called DEBUG.TXT



    On 8/12/2015 3:12 PM, CRAIG STRUTT wrote to JERRY SEHL:

    I'm up and running on Windows 10 64bit (upgrading from XP so a
    BIG jump).
    The only problem I am having relates to my MySQL and PHP setup.
    Admittedly
    it's my fault since I was running PHP 4.3 and MySql 3.4. I
    can't seem to
    get the older PHP to work with a newer (had to reinstall) MySql.
    I
    remember the configuration was a bear in the beginning. For
    that reason,
    since it worked, I didn't touch it. Now I'm going to have to
    spend hours
    reading and reconfiguring to get it all back and running as it
    should be.

    Not Winserver's problem. Not Windows 10 problem. If there is a
    "best"
    place to start, feel free to point me in that direction
    (anyone...)

    On 7/31/2015 3:50 PM, JERRY SEHL wrote to all:

    I installed after a long download, it took a while a a bunch
    of restarts
    until it was ready, however in starting it up with my
    winserver all
    seemed
    well when I received messages and sent some, but in checking
    my own
    websites found they didn't exist.

    I made an appointment for a call from MS and waited till 5 pm
    the next
    day
    and viola a phone call but was quickly handed over to another
    then
    another
    where I was on hold for 1 1/2 hours. The service tech advisor
    quickly
    told
    me he didn't understand as it wasn't a Microsoft product etc
    etc.

    A feature to roll back to Windows 7 is built in good for 30
    days after
    the
    upgrade, I used it and all is back well again.

    But did find that 32 bit support exists!







    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Fri, 14 Aug 2015 18:43:54 -0400
    From: MICHAEL PURDY
    To: CRAIG STRUTT
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439592234.32.1439562536@winserver.com>
    References: <1439562536.32.1439504949@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 196

    If it is third party PHP application then I would presume the author would
    have a v5 offering unless its abandon-ware. If its your own application
    then it maybe worth considering porting it to WCX/wcODBC.

    Before reporting it to HS I would start each of the Wildcat programs
    manually (in dependency order) and verify that if you do NOT use wcStart
    things run correctly.

    Normally wcStart only misbehaves if there is a problem with the "Wait for
    Up Signal" property associated with one of the applications. For example
    the wcMail signal Wildcat.MailUpEvent

    I would verify the signal syntax for each of the main applications e.g.

    Wildcat.MailUpEvent
    Wildcat.OnlineUpEvent
    Wildcat.ListServeUpEvent
    Wildcat.SmtpUpEvent.Router
    Wildcat.SmtpUpEvent.Sender
    Wildcat.SmtpUpEvent.Receiver
    Wildcat.NntpUpEvent

    If there is a signal issue wcstart with continue to run waiting for the
    signal and that will then cause issues with the startup of other lower
    level applications.

    I would recommend you install SysInternals

    https://technet.microsoft.com/en-us/sysinternals/bb842062

    Run

    DBGVIEW.EXE

    Debug Viewer and then run wcStart.exe and you will see what is happening in
    the background at startup.



    On 8/14/2015 10:28 AM, CRAIG STRUTT wrote to MICHAEL PURDY:

    Thanks for you help. Yes, my issues are directly related to depreciated commands (mysql_connect). I'm working through those.

    I still have two strange issues which I'll have to touch base with Hector on. When the system powers up, WCMail takes up nearly 100% of the processor power and WcStart continues to run in the background. Although restarting WcMail takes care of it, I've also found (strangely enough) that setting it's affinity to 2 CPUs (running a quad core) immediately stops the high CPU usage (drops to 0) and then I can put it back on all cores and it runs fine. I've left WcStart running this time (normally I force it to stop) and I'm watching it slowly reduce it's memory footprint. I want to see if it stops on it's own eventually (a settings issue) or if it keeps running. Right now, it's taking 25% of the CPU cycles.

    On 8/13/2015 6:29 PM, MICHAEL PURDY wrote to CRAIG STRUTT:

    Changes to the PHP.INI file are dynamic and do not require any shutdown/restart with Wildcat!.

    If you are using another web server then a restart maybe required.

    Assuming you can connect successfully to MySQL using the CLI mysql
    command
    tool or a GUI tool like SQLyog
    https://github.com/webyog/sqlyog-community
    then you need to go through the PHP specific troubleshooting process.



    On 8/13/2015 6:07 PM, CRAIG STRUTT wrote to MICHAEL PURDY:

    Thanks Mike. I'm *trying* to do just that. Thus far, the shutting down, and starting up again of the server just to change a setting in PHP.INI is an issue.

    I still don't have the auto shutdown routines working correctly, and the auto startup works on reboot, but not when the machine is already running (can't figure that one out!) WcStart.exe -run works fine in the scheduler with an ON logon high privilage, but not after the machine is running. <sigh> I WILL get this.

    On 8/13/2015 6:11 AM, MICHAEL PURDY wrote to CRAIG STRUTT:

    If you check the unsupported branches list

    http://php.net/eol.php

    You will note the 3.x and 4.x has been End of Life for many years.

    The expectation when running MySQL 5.x is that you will have
    migrated to
    PHP 5.x.

    There are differences in the Extensions:

    extension=php_mysql.dll
    extension=php_mysqli.dll

    used in PHP 3.x, 4.x and 5.x. They are not compatible.

    I suggest in your PHP.INI you temporarily set

    error_reporting = E_ALL
    display_errors = on
    display_startup_errors = on

    Which when a script is called will show any Startup errors such as
    DLLs
    failing to load.

    You could of course set the logging to file should you prefer.

    error_log = \php\phperror.log

    A simple test script such as

    <?php
    phpinfo();


    Run at the CLI against PHP.EXE e.g.

    php test.php > debug.txt

    Would send all of the information necessary for debugging to a
    text
    file
    called DEBUG.TXT



    On 8/12/2015 3:12 PM, CRAIG STRUTT wrote to JERRY SEHL:

    I'm up and running on Windows 10 64bit (upgrading from XP so a
    BIG jump).
    The only problem I am having relates to my MySQL and PHP
    setup.
    Admittedly
    it's my fault since I was running PHP 4.3 and MySql 3.4. I
    can't seem to
    get the older PHP to work with a newer (had to reinstall)
    MySql.
    I
    remember the configuration was a bear in the beginning. For
    that reason,
    since it worked, I didn't touch it. Now I'm going to have to
    spend hours
    reading and reconfiguring to get it all back and running as it
    should be.

    Not Winserver's problem. Not Windows 10 problem. If there
    is a
    "best"
    place to start, feel free to point me in that direction
    (anyone...)

    On 7/31/2015 3:50 PM, JERRY SEHL wrote to all:

    I installed after a long download, it took a while a a bunch
    of restarts
    until it was ready, however in starting it up with my
    winserver all
    seemed
    well when I received messages and sent some, but in checking
    my own
    websites found they didn't exist.

    I made an appointment for a call from MS and waited till
    5 pm
    the next
    day
    and viola a phone call but was quickly handed over to
    another
    then
    another
    where I was on hold for 1 1/2 hours. The service tech
    advisor
    quickly
    told
    me he didn't understand as it wasn't a Microsoft product etc
    etc.

    A feature to roll back to Windows 7 is built in good for 30
    days after
    the
    upgrade, I used it and all is back well again.

    But did find that 32 bit support exists!








    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From CRAIG STRUTT@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Fri, 14 Aug 2015 19:32:02 -0400
    From: CRAIG STRUTT
    To: MICHAEL PURDY
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439595122.32.1439592234@winserver.com>
    References: <1439592234.32.1439562536@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 262

    It's my own mess of code. I never learned PHP or MySql truly. I
    looked at other's code and the manual, and hacked things together.

    I do a lot of Basic Programming, and work with HTML, a little CSS, and
    even some Java.

    I'm starting to feel old when I'm not sure I want to learn one more
    thing, which is what happens frequently when you do a major upgrade.

    Thanks for your suggestions. I'll take a look and see if I can figure
    it out.

    On 8/14/2015 6:43 PM, MICHAEL PURDY wrote to CRAIG STRUTT:

    If it is third party PHP application then I would presume the author
    would
    have a v5 offering unless its abandon-ware. If its your own
    application
    then it maybe worth considering porting it to WCX/wcODBC.

    Before reporting it to HS I would start each of the Wildcat programs manually (in dependency order) and verify that if you do NOT use
    wcStart
    things run correctly.

    Normally wcStart only misbehaves if there is a problem with the
    "Wait for
    Up Signal" property associated with one of the applications. For
    example
    the wcMail signal Wildcat.MailUpEvent

    I would verify the signal syntax for each of the main applications
    e.g.

    Wildcat.MailUpEvent
    Wildcat.OnlineUpEvent
    Wildcat.ListServeUpEvent
    Wildcat.SmtpUpEvent.Router
    Wildcat.SmtpUpEvent.Sender
    Wildcat.SmtpUpEvent.Receiver
    Wildcat.NntpUpEvent

    If there is a signal issue wcstart with continue to run waiting for
    the
    signal and that will then cause issues with the startup of other
    lower
    level applications.

    I would recommend you install SysInternals

    https://technet.microsoft.com/en-us/sysinternals/bb842062

    Run

    DBGVIEW.EXE

    Debug Viewer and then run wcStart.exe and you will see what is
    happening in
    the background at startup.



    On 8/14/2015 10:28 AM, CRAIG STRUTT wrote to MICHAEL PURDY:

    Thanks for you help. Yes, my issues are directly related to
    depreciated
    commands (mysql_connect). I'm working through those.

    I still have two strange issues which I'll have to touch base
    with Hector
    on. When the system powers up, WCMail takes up nearly 100% of
    the
    processor power and WcStart continues to run in the background.
    Although
    restarting WcMail takes care of it, I've also found (strangely
    enough) that
    setting it's affinity to 2 CPUs (running a quad core) immediately
    stops the
    high CPU usage (drops to 0) and then I can put it back on all
    cores and it
    runs fine. I've left WcStart running this time (normally I
    force it to
    stop) and I'm watching it slowly reduce it's memory footprint.
    I want to
    see if it stops on it's own eventually (a settings issue) or if
    it keeps
    running. Right now, it's taking 25% of the CPU cycles.

    On 8/13/2015 6:29 PM, MICHAEL PURDY wrote to CRAIG STRUTT:

    Changes to the PHP.INI file are dynamic and do not require any shutdown/restart with Wildcat!.

    If you are using another web server then a restart maybe
    required.

    Assuming you can connect successfully to MySQL using the CLI
    mysql
    command
    tool or a GUI tool like SQLyog
    https://github.com/webyog/sqlyog-community
    then you need to go through the PHP specific troubleshooting
    process.



    On 8/13/2015 6:07 PM, CRAIG STRUTT wrote to MICHAEL PURDY:

    Thanks Mike. I'm *trying* to do just that. Thus far, the
    shutting
    down, and starting up again of the server just to change a
    setting in
    PHP.INI is an issue.

    I still don't have the auto shutdown routines working
    correctly, and
    the auto startup works on reboot, but not when the machine
    is already
    running (can't figure that one out!) WcStart.exe -run
    works fine in
    the scheduler with an ON logon high privilage, but not
    after the
    machine is running. <sigh> I WILL get this.

    On 8/13/2015 6:11 AM, MICHAEL PURDY wrote to CRAIG STRUTT:

    If you check the unsupported branches list

    http://php.net/eol.php

    You will note the 3.x and 4.x has been End of Life for
    many years.

    The expectation when running MySQL 5.x is that you will
    have
    migrated to
    PHP 5.x.

    There are differences in the Extensions:

    extension=php_mysql.dll
    extension=php_mysqli.dll

    used in PHP 3.x, 4.x and 5.x. They are not compatible.

    I suggest in your PHP.INI you temporarily set

    error_reporting = E_ALL
    display_errors = on
    display_startup_errors = on

    Which when a script is called will show any Startup
    errors such as
    DLLs
    failing to load.

    You could of course set the logging to file should you
    prefer.

    error_log = \php\phperror.log

    A simple test script such as

    <?php
    phpinfo();


    Run at the CLI against PHP.EXE e.g.

    php test.php > debug.txt

    Would send all of the information necessary for
    debugging to a
    text
    file
    called DEBUG.TXT



    On 8/12/2015 3:12 PM, CRAIG STRUTT wrote to JERRY SEHL:

    I'm up and running on Windows 10 64bit (upgrading
    from XP so a
    BIG jump).
    The only problem I am having relates to my MySQL and
    PHP
    setup.
    Admittedly
    it's my fault since I was running PHP 4.3 and MySql
    3.4. I
    can't seem to
    get the older PHP to work with a newer (had to
    reinstall)
    MySql.
    I
    remember the configuration was a bear in the
    beginning. For
    that reason,
    since it worked, I didn't touch it. Now I'm going to
    have to
    spend hours
    reading and reconfiguring to get it all back and
    running as it
    should be.

    Not Winserver's problem. Not Windows 10 problem. If
    there
    is a
    "best"
    place to start, feel free to point me in that
    direction
    (anyone...)

    On 7/31/2015 3:50 PM, JERRY SEHL wrote to all:

    I installed after a long download, it took a while
    a a bunch
    of restarts
    until it was ready, however in starting it up with
    my
    winserver all
    seemed
    well when I received messages and sent some, but
    in checking
    my own
    websites found they didn't exist.

    I made an appointment for a call from MS and
    waited till
    5 pm
    the next
    day
    and viola a phone call but was quickly handed over
    to
    another
    then
    another
    where I was on hold for 1 1/2 hours. The service
    tech
    advisor
    quickly
    told
    me he didn't understand as it wasn't a Microsoft
    product etc
    etc.

    A feature to roll back to Windows 7 is built in
    good for 30
    days after
    the
    upgrade, I used it and all is back well again.

    But did find that 32 bit support exists!









    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Fri, 14 Aug 2015 19:51:44 -0400
    From: MICHAEL PURDY
    To: CRAIG STRUTT
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1439596304.32.1439595122@winserver.com>
    References: <1439595122.32.1439592234@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 278

    I will leave you to review it all.

    I would suggest you use DBGVIEW.EXE from Sysinternals to see what is
    happening before logging a issue/question with SSI about wcStart

    Using WCX/wcODBC maybe more worth your effort than persisting with PHP, but that is your call.

    If you wish to discuss the SQL options further at some point then let me
    know if you have an IM/Skype address as that is more appropriate than
    playing email tag.


    On 8/14/2015 7:32 PM, CRAIG STRUTT wrote to MICHAEL PURDY:

    It's my own mess of code. I never learned PHP or MySql truly. I
    looked at other's code and the manual, and hacked things together.

    I do a lot of Basic Programming, and work with HTML, a little CSS, and
    even some Java.

    I'm starting to feel old when I'm not sure I want to learn one more
    thing, which is what happens frequently when you do a major upgrade.

    Thanks for your suggestions. I'll take a look and see if I can figure
    it out.

    On 8/14/2015 6:43 PM, MICHAEL PURDY wrote to CRAIG STRUTT:

    If it is third party PHP application then I would presume the author
    would
    have a v5 offering unless its abandon-ware. If its your own
    application
    then it maybe worth considering porting it to WCX/wcODBC.

    Before reporting it to HS I would start each of the Wildcat programs manually (in dependency order) and verify that if you do NOT use
    wcStart
    things run correctly.

    Normally wcStart only misbehaves if there is a problem with the
    "Wait for
    Up Signal" property associated with one of the applications. For
    example
    the wcMail signal Wildcat.MailUpEvent

    I would verify the signal syntax for each of the main applications
    e.g.

    Wildcat.MailUpEvent
    Wildcat.OnlineUpEvent
    Wildcat.ListServeUpEvent
    Wildcat.SmtpUpEvent.Router
    Wildcat.SmtpUpEvent.Sender
    Wildcat.SmtpUpEvent.Receiver
    Wildcat.NntpUpEvent

    If there is a signal issue wcstart with continue to run waiting for
    the
    signal and that will then cause issues with the startup of other
    lower
    level applications.

    I would recommend you install SysInternals

    https://technet.microsoft.com/en-us/sysinternals/bb842062

    Run

    DBGVIEW.EXE

    Debug Viewer and then run wcStart.exe and you will see what is
    happening in
    the background at startup.



    On 8/14/2015 10:28 AM, CRAIG STRUTT wrote to MICHAEL PURDY:

    Thanks for you help. Yes, my issues are directly related to
    depreciated
    commands (mysql_connect). I'm working through those.

    I still have two strange issues which I'll have to touch base
    with Hector
    on. When the system powers up, WCMail takes up nearly 100% of
    the
    processor power and WcStart continues to run in the background.
    Although
    restarting WcMail takes care of it, I've also found (strangely
    enough) that
    setting it's affinity to 2 CPUs (running a quad core) immediately
    stops the
    high CPU usage (drops to 0) and then I can put it back on all
    cores and it
    runs fine. I've left WcStart running this time (normally I
    force it to
    stop) and I'm watching it slowly reduce it's memory footprint.
    I want to
    see if it stops on it's own eventually (a settings issue) or if
    it keeps
    running. Right now, it's taking 25% of the CPU cycles.

    On 8/13/2015 6:29 PM, MICHAEL PURDY wrote to CRAIG STRUTT:

    Changes to the PHP.INI file are dynamic and do not require any shutdown/restart with Wildcat!.

    If you are using another web server then a restart maybe
    required.

    Assuming you can connect successfully to MySQL using the CLI
    mysql
    command
    tool or a GUI tool like SQLyog
    https://github.com/webyog/sqlyog-community
    then you need to go through the PHP specific troubleshooting
    process.



    On 8/13/2015 6:07 PM, CRAIG STRUTT wrote to MICHAEL PURDY:

    Thanks Mike. I'm *trying* to do just that. Thus far, the
    shutting
    down, and starting up again of the server just to change a
    setting in
    PHP.INI is an issue.

    I still don't have the auto shutdown routines working
    correctly, and
    the auto startup works on reboot, but not when the machine
    is already
    running (can't figure that one out!) WcStart.exe -run
    works fine in
    the scheduler with an ON logon high privilage, but not
    after the
    machine is running. <sigh> I WILL get this.

    On 8/13/2015 6:11 AM, MICHAEL PURDY wrote to CRAIG STRUTT:

    If you check the unsupported branches list

    http://php.net/eol.php

    You will note the 3.x and 4.x has been End of Life for
    many years.

    The expectation when running MySQL 5.x is that you will
    have
    migrated to
    PHP 5.x.

    There are differences in the Extensions:

    extension=php_mysql.dll
    extension=php_mysqli.dll

    used in PHP 3.x, 4.x and 5.x. They are not compatible.

    I suggest in your PHP.INI you temporarily set

    error_reporting = E_ALL
    display_errors = on
    display_startup_errors = on

    Which when a script is called will show any Startup
    errors such as
    DLLs
    failing to load.

    You could of course set the logging to file should you
    prefer.

    error_log = \php\phperror.log

    A simple test script such as

    <?php
    phpinfo();


    Run at the CLI against PHP.EXE e.g.

    php test.php > debug.txt

    Would send all of the information necessary for
    debugging to a
    text
    file
    called DEBUG.TXT



    On 8/12/2015 3:12 PM, CRAIG STRUTT wrote to JERRY SEHL:

    I'm up and running on Windows 10 64bit (upgrading
    from XP so a
    BIG jump).
    The only problem I am having relates to my MySQL and
    PHP
    setup.
    Admittedly
    it's my fault since I was running PHP 4.3 and MySql
    3.4. I
    can't seem to
    get the older PHP to work with a newer (had to
    reinstall)
    MySql.
    I
    remember the configuration was a bear in the
    beginning. For
    that reason,
    since it worked, I didn't touch it. Now I'm going to
    have to
    spend hours
    reading and reconfiguring to get it all back and
    running as it
    should be.

    Not Winserver's problem. Not Windows 10 problem. If
    there
    is a
    "best"
    place to start, feel free to point me in that
    direction
    (anyone...)

    On 7/31/2015 3:50 PM, JERRY SEHL wrote to all:

    I installed after a long download, it took a while
    a a bunch
    of restarts
    until it was ready, however in starting it up with
    my
    winserver all
    seemed
    well when I received messages and sent some, but
    in checking
    my own
    websites found they didn't exist.

    I made an appointment for a call from MS and
    waited till
    5 pm
    the next
    day
    and viola a phone call but was quickly handed over
    to
    another
    then
    another
    where I was on hold for 1 1/2 hours. The service
    tech
    advisor
    quickly
    told
    me he didn't understand as it wasn't a Microsoft
    product etc
    etc.

    A feature to roll back to Windows 7 is built in
    good for 30
    days after
    the
    upgrade, I used it and all is back well again.

    But did find that 32 bit support exists!










    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From CRAIG STRUTT@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Wed, 26 Aug 2015 11:50:18 -0400
    From: CRAIG STRUTT
    To: MICHAEL PURDY
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1440604218.32.1439596304@winserver.com>
    References: <1439596304.32.1439595122@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 353

    I've fixed enough of the MySQL / PHP problems to know where I'm going
    with that, and thus have come back to the less critical issue of
    WcStart not finishing properly, and WcMail taking 100% processor time.

    Both can be "fixed" manually, so I've been bungling along day by day.

    I did download DBGView.exe and run it as you suggested. I'm not quite
    sure what I'm looking for but no huge errors seem to pop out. I
    thought I'd attach a run from Shutdown, to successful startup to see if
    you might want to take a look before I bother Hector. I still have
    one other issue, and that is the fact that Autoupdate won't connect,
    but I'll approach that later.

    Attached is my DBGView log that I mentioned

    On 8/14/2015 7:51 PM, MICHAEL PURDY wrote to CRAIG STRUTT:

    I will leave you to review it all.

    I would suggest you use DBGVIEW.EXE from Sysinternals to see what is happening before logging a issue/question with SSI about wcStart

    Using WCX/wcODBC maybe more worth your effort than persisting with
    PHP, but
    that is your call.

    If you wish to discuss the SQL options further at some point then
    let me
    know if you have an IM/Skype address as that is more appropriate
    than
    playing email tag.


    On 8/14/2015 7:32 PM, CRAIG STRUTT wrote to MICHAEL PURDY:

    It's my own mess of code. I never learned PHP or MySql truly.
    I
    looked at other's code and the manual, and hacked things
    together.

    I do a lot of Basic Programming, and work with HTML, a little
    CSS, and
    even some Java.

    I'm starting to feel old when I'm not sure I want to learn one
    more
    thing, which is what happens frequently when you do a major
    upgrade.

    Thanks for your suggestions. I'll take a look and see if I can
    figure
    it out.

    On 8/14/2015 6:43 PM, MICHAEL PURDY wrote to CRAIG STRUTT:

    If it is third party PHP application then I would presume the
    author
    would
    have a v5 offering unless its abandon-ware. If its your own
    application
    then it maybe worth considering porting it to WCX/wcODBC.

    Before reporting it to HS I would start each of the Wildcat
    programs
    manually (in dependency order) and verify that if you do NOT
    use
    wcStart
    things run correctly.

    Normally wcStart only misbehaves if there is a problem with
    the
    "Wait for
    Up Signal" property associated with one of the applications.
    For
    example
    the wcMail signal Wildcat.MailUpEvent

    I would verify the signal syntax for each of the main
    applications
    e.g.

    Wildcat.MailUpEvent
    Wildcat.OnlineUpEvent
    Wildcat.ListServeUpEvent
    Wildcat.SmtpUpEvent.Router
    Wildcat.SmtpUpEvent.Sender
    Wildcat.SmtpUpEvent.Receiver
    Wildcat.NntpUpEvent

    If there is a signal issue wcstart with continue to run
    waiting for
    the
    signal and that will then cause issues with the startup of
    other
    lower
    level applications.

    I would recommend you install SysInternals

    https://technet.microsoft.com/en-us/sysinternals/bb842062

    Run

    DBGVIEW.EXE

    Debug Viewer and then run wcStart.exe and you will see what is
    happening in
    the background at startup.



    On 8/14/2015 10:28 AM, CRAIG STRUTT wrote to MICHAEL PURDY:

    Thanks for you help. Yes, my issues are directly related
    to
    depreciated
    commands (mysql_connect). I'm working through those.

    I still have two strange issues which I'll have to touch
    base
    with Hector
    on. When the system powers up, WCMail takes up nearly
    100% of
    the
    processor power and WcStart continues to run in the
    background.
    Although
    restarting WcMail takes care of it, I've also found
    (strangely
    enough) that
    setting it's affinity to 2 CPUs (running a quad core)
    immediately
    stops the
    high CPU usage (drops to 0) and then I can put it back on
    all
    cores and it
    runs fine. I've left WcStart running this time (normally
    I
    force it to
    stop) and I'm watching it slowly reduce it's memory
    footprint.
    I want to
    see if it stops on it's own eventually (a settings issue)
    or if
    it keeps
    running. Right now, it's taking 25% of the CPU cycles.

    On 8/13/2015 6:29 PM, MICHAEL PURDY wrote to CRAIG STRUTT:

    Changes to the PHP.INI file are dynamic and do not
    require any
    shutdown/restart with Wildcat!.

    If you are using another web server then a restart maybe
    required.

    Assuming you can connect successfully to MySQL using the
    CLI
    mysql
    command
    tool or a GUI tool like SQLyog
    https://github.com/webyog/sqlyog-community
    then you need to go through the PHP specific
    troubleshooting
    process.



    On 8/13/2015 6:07 PM, CRAIG STRUTT wrote to MICHAEL
    PURDY:

    Thanks Mike. I'm *trying* to do just that. Thus
    far, the
    shutting
    down, and starting up again of the server just to
    change a
    setting in
    PHP.INI is an issue.

    I still don't have the auto shutdown routines working
    correctly, and
    the auto startup works on reboot, but not when the
    machine
    is already
    running (can't figure that one out!) WcStart.exe -
    run
    works fine in
    the scheduler with an ON logon high privilage, but
    not
    after the
    machine is running. <sigh> I WILL get this.

    On 8/13/2015 6:11 AM, MICHAEL PURDY wrote to CRAIG
    STRUTT:

    If you check the unsupported branches list

    http://php.net/eol.php

    You will note the 3.x and 4.x has been End of Life
    for
    many years.

    The expectation when running MySQL 5.x is that you
    will
    have
    migrated to
    PHP 5.x.

    There are differences in the Extensions:

    extension=php_mysql.dll
    extension=php_mysqli.dll

    used in PHP 3.x, 4.x and 5.x. They are not
    compatible.

    I suggest in your PHP.INI you temporarily set

    error_reporting = E_ALL
    display_errors = on
    display_startup_errors = on

    Which when a script is called will show any
    Startup
    errors such as
    DLLs
    failing to load.

    You could of course set the logging to file should
    you
    prefer.

    error_log = \php\phperror.log

    A simple test script such as

    <?php
    phpinfo();


    Run at the CLI against PHP.EXE e.g.

    php test.php > debug.txt

    Would send all of the information necessary for
    debugging to a
    text
    file
    called DEBUG.TXT



    On 8/12/2015 3:12 PM, CRAIG STRUTT wrote to JERRY
    SEHL:

    I'm up and running on Windows 10 64bit
    (upgrading
    from XP so a
    BIG jump).
    The only problem I am having relates to my
    MySQL and
    PHP
    setup.
    Admittedly
    it's my fault since I was running PHP 4.3 and
    MySql
    3.4. I
    can't seem to
    get the older PHP to work with a newer (had to
    reinstall)
    MySql.
    I
    remember the configuration was a bear in the
    beginning. For
    that reason,
    since it worked, I didn't touch it. Now I'm
    going to
    have to
    spend hours
    reading and reconfiguring to get it all back
    and
    running as it
    should be.

    Not Winserver's problem. Not Windows 10
    problem. If
    there
    is a
    "best"
    place to start, feel free to point me in that
    direction
    (anyone...)

    On 7/31/2015 3:50 PM, JERRY SEHL wrote to all:

    I installed after a long download, it took a
    while
    a a bunch
    of restarts
    until it was ready, however in starting it
    up with
    my
    winserver all
    seemed
    well when I received messages and sent some,
    but
    in checking
    my own
    websites found they didn't exist.

    I made an appointment for a call from MS and
    waited till
    5 pm
    the next
    day
    and viola a phone call but was quickly
    handed over
    to
    another
    then
    another
    where I was on hold for 1 1/2 hours. The
    service
    tech
    advisor
    quickly
    told
    me he didn't understand as it wasn't a
    Microsoft
    product etc
    etc.

    A feature to roll back to Windows 7 is built
    in
    good for 30
    days after
    the
    upgrade, I used it and all is back well
    again.

    But did find that 32 bit support exists!












    <<<< Note: message contains attachment: WcStart_LG.log >>>

    *** File "WcStart_LG.log" has been uudecoded and
    attached to this message.

    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Wed, 26 Aug 2015 21:05:17 -0400
    From: MICHAEL PURDY
    To: CRAIG STRUTT
    Subject: RE: Windows 10
    Newsgroups: win.server.program
    Message-ID: <1440637517.32.1440604218@winserver.com>
    References: <1440604218.32.1439596304@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 72

    Craig

    Short Answer

    Wildcat is an SSI product and Hector has previously said that he prefers
    people to contact him directly so ˙he˙ knows about potential problems. I
    think this is important given that SSI will need to deal with an increasing number of W10 users over the next 12 months. So my recommendation would be
    to contact him directly. The other option would be to post in the BETA Winserver List that he does read.

    Long Answer

    DBGVIEW receives some output from the Windows OS but most comes from output sent to the Debug Stream by third party developers. You can read about the Output Stream here:

    https://msdn.microsoft.com/en-us/library/windows/desktop/aa363362(v=vs.85).aspx

    The main thing to keep in mind is that if the developer does not send any
    debug output to the stream then you will not see anything and consequently DBGVIEW is of little value. A couple of reasons for using the debug stream
    are to reduce the overhead of sending debug information to STDOUT such as
    File or the Console and to avoid frightening end users etc.

    Fault tolerant heap shim

    This normally means a program has crashed e.g.:

    1. It completely died and bailed
    2. Its has become unresponsive
    3. It exited abnormally on program stop.

    The most common cause is problems with memory management in the application
    or incompatibility problems. There are several other causes that need to
    be investigated by the developer on a case-by-case basis. I encountered a
    lot when I first moved to Win7.

    The shim will allow a crash prone application to run, but the associated registry shim entries are often lost especially after reboot. Basically
    you don˙t want shim errors.

    Troubleshooting

    Q. Have you set wcStart.exe and wcMail.exe to Run As Administrator

    Q. Have you navigated to the Wildcat root folder and Right Clicked on
    wcStart / wcMail and Run the Troubleshoot Compatibility Option and saved
    the suggested compatibility settings? This will tell you if W10 considers
    the Applications are Incompatible!

    Addition Troubleshooting Information

    I have a utility called wcdiag.exe that when run at the CLI

    wcdiag /t

    will produce a log called wcdiag-trouble.log this along with the DBGVIEW
    log may / may not be of help to HS/SSI You can download it here:

    http://wcstatus.mapurdy.com.au/downloads/downloads.wct

    If you wish to touch base with me again then send me an IM to either:

    Gtalk: mapurdy.com.au or
    Skype: mike_purdy.

    I don˙t login here now as much as I once did.

    Mike


    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)