home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   ENGLISH_TUTOR      English Tutoring for Students of the Eng      4,347 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 2,545 of 4,347   
   CRAIG STRUTT to All   
   WcStart vs Windows 10   
   31 Jan 19 19:17:19   
   
   Date: Wed, 10 Feb 2016 16:45:23 -0400   
   From: CRAIG STRUTT   
   To: HECTOR SANTOS   
   Subject: WcStart vs Windows 10   
   Newsgroups: winserver.public.gamma.testing   
   Message-ID: <1455140723.40.0@winserver.com>   
   X-Mailer: Wildcat! Interactive Net Server v7.0.454.5   
   Lines: 35   
      
   I've been working with this for about four months.   Upgraded my Winserver    
   machine to Windows 10 64 bit.   
      
   Everything is working fine... except...   
      
   WcStart does what it is supposed to do, with very little memory and CPU    
   usage, then when it's done and tries to exit, it locks one (of 4 CPUs on    
   this machine) at 100%  (25% overall) and hangs.   
      
   For a long time I thought it was perhaps hanging up waiting for a process    
   to report back, then I discovered that I can start WcStart (from the home    
   directory) as if I were going to make changes to the startup routine.  If I    
   do something, or nothing (it doesn't matter) and then attempt to close the    
   program (either by the red X, or by ALT-X, or by clicking on schedule and    
   exit) it does the same thing as mentioned above.      
      
   With WcStart hogging the first CPU, everything else slows to a crawl, and    
   automated shutdown will not work until WcStart is manually ended using Task    
   Manager.   
      
   This forces me to manually backup, and manually restart the system if    
   needed for updates.   
      
   On a different note, WcMail occasionally (about 1 out of 10 times) when it    
   starts will grab ALL processors at 100%.   Simply changing the affinity and     
   deselecting one processor (it doesn't matter which one) and saying okay,    
   drops the processor load to 0%.   Then I can go back in, change the    
   affinity to all processors, and it continues to operate just fine.   
      
   I am at wcSTART v7.0.454.4.   
      
   Windows 10 Home 64bit   
   Version 11511   
   Build 10586.104   
   4GB RAM    
   --- Platinum Xpress/Win/WINServer v3.1   
    * Origin: Prison Board BBS Mesquite Tx  //telnet.RDFIG.NET www. (1:124/5013)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca