Upgraded to Windows 10. All is working well (with a lot of effort in between) One issue left that I can't seem to squash.
WcStart runs just fine, and starts up all the correct programs in the correct order. If the system is rebooted and it runs (automatically) WcMail takes up all of the processor time. If I decrease the CPU
affinity to just 2 of 4, it immediately stops the excess CPU usage and
I can then bump it back up to all processors and all operates normally.
If I do a shutdown after reboot, and restart, WcMail works as expected.
That is minor and I reboot infrequently so not a terrific issue other
than Windows 10 auto updates.
The big issue is that WcStart does not finish correctly, and after all other programs are running correctly, hangs with 25% CPU usage.
I've run DGView but I'm not understanding the log file, so I'll attach
that for you here. If you need any additional information please let
me know.
Window 10 64bit
Latest AUP update.
WcStart is listed as 6.4.454.2 and is running in compatibility mode XP Service Pack 3 as are most other Winserver programs.
On 9/3/2015 5:38 PM, CRAIG STRUTT wrote to HECTOR SANTOS:
Upgraded to Windows 10. All is working well (with a lot of effort in between) One issue left that I can't seem to squash.
WcStart runs just fine, and starts up all the correct programs in the correct order. If the system is rebooted and it runs (automatically) WcMail takes up all of the processor time. If I decrease the CPU affinity to just 2 of 4, it immediately stops the excess CPU usage and
I can then bump it back up to all processors and all operates normally.
If I do a shutdown after reboot, and restart, WcMail works as expected.
That is minor and I reboot infrequently so not a terrific issue other than Windows 10 auto updates.
The big issue is that WcStart does not finish correctly, and after all other programs are running correctly, hangs with 25% CPU usage.
I've run DGView but I'm not understanding the log file, so I'll attach that for you here. If you need any additional information please let
me know.
Window 10 64bit
Latest AUP update.
WcStart is listed as 6.4.454.2 and is running in compatibility mode XP Service Pack 3 as are most other Winserver programs.
As far as WC6.4 XP SP3 compatibility mode and Windows 10 from my testing
all it does is screw up things, some of my programs wouldn't even function properly with it set and I tried all the different OS modes even the compatibility troubleshooter which I abruptly aborted when I saw where it was going. Have you tried wcMail and wcStart and all the other WC apps for that matter without any compatibility mode on them? That's the way I'm running WC6.4 without any problems on a 2CPU Pentium 4 under W10 Pro 32Bit.
What is your last entry in wcStart? Does it have "wait for program to finish" box checked?
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,034 |
Nodes: | 15 (0 / 15) |
Uptime: | 137:47:46 |
Calls: | 669 |
Calls today: | 3 |
Files: | 95,163 |
D/L today: |
603 files (105M bytes) |
Messages: | 297,608 |