Normally your DEL command should work, but during a logging process it is possible to get a deadlock situation, when one command tries to delete a file and another process tries to create one.
The windows95 deltree can handle open files for other environments like Windows NT, but for his own environment you get a deadlock.
The goal to clean up the temp directory is possible, when you specifies som different submask.
At our site we limit it to the following actions:

code:

---

    del "c:\ffastun*.*"
    del "c:\file*.chk"
    del "c:\temp\~*.*"
    del "c:\temp\*.tmp"
    del "c:\windows\~*.*"
    del "c:\windows\*.tmp"
    del "c:\windows\temp\~*.*"
    del "c:\windows\temp\*.tmp"

---

Another solutions are:

• to start cleaning after the completion of the login process.
  
• to add a batch call to your autoexec.bat file, which cleanup the system from a lot of temporary files before windows 95 starts running.
  The autoexec.bat will always be running after power-on your system. It will never be influenced by another process, because it runs in single-task-mode.
  

Greetings.