Conference jamin::pathworks32

113.0. "SPAWN32 Hogging CPU (NT)" by VMSNET::S_VORE (Smile - Mickey's Watching!) Wed Feb 05 1997 14:44

    One-system anomoly or QAR material?  
    Anyone else had problems with SPAWN from the latest bits?
    
    NT4.0
    Installed PW32 from pw32daily 5-Feb 10:30am Eastern
    
    Selected
    	DECnet
    	LAT
    	VT320
    	Licensing
    
    Rebooted after setup completed, logged on. The system appeared to hang
    partway through the logon process.  Clicking on the [Start] menu
    resulted in a depressed [Start] button and an hourglass pointer, no
    start menu.  Task manager showed SPAWN32.EXE hogging the cpu, % ranging
    between 75 & 95, the task manager itself was the only other application
    able to get any cycles.  [End task] was unable to stop SAPWN32,
    producing an Access Denied alert box, though my account has full privs
    (copy of Administrator).
    
    Ended up booting from a different NT installation directory and
    renaming SPAWN32.EXE in order to get the system usable again. Since
    doing this, all attempted functions work, though of course I've not
    tried to spawn any tasks via DECnet.
    
    -Steven
    

    I see it on my machine with the Feb 4th spawn32.exe.  Qar it.
    
    Thanks for reporting this.
    

    7-Feb bits solved the problem.