Try this...
Try this:
del \\?\c:\path_to_file\lpt1
OR
- Open a Command Window (Start Accessories - Command Prompt)
- Leave it open but close down all other running programs.
- Now via the Ctrl Alt Del or from the Task Manager (Start - Run Type TASKMGR.EXE) under the processes tab, end the Explorer.exe process.
- Now leaving the task Manager open, return to the Command Prompt window and type "cd path" to take you to the folder where the file is. eg. "cd c:My Documents" (Without brackets. Also note there is a space between cd and c: )
- Now type "DEL " (eg "DEL badfile.exe" again without the brackets.
- Once done go back to the Task Manager and under File - New Task type EXPLORER.EXE. This will kick start the windows GUI (interface)
- Close task manager.
& LASTLY:
Make SURE you did not name the Directory/Folder pathnames beyond 255 characters length of the string, or use "off the wall" HIGHER ASCII characters in the names or deletes via Explorer.exe OR DOS/cmd.exe won't work either (fixed the last one I had today 06/06/2005)...
=========
REASONS:
=========
* Usually, when you see this type of thing? The file is LOCKED, exclusively, by a single user... us killing them above? Stalls that, cold. A 'knock out punch to the jaw', for the system's OWN good, temporarily.
So, as the above steps say? Just stop ALL of the background processes you can, services also (leave RPC alone, both of them) using services.msc included IF you have to as well ontop of the above because, you HAVE to find the locking file/offending process by elimination of them in memory.
So, AGAIN: Leave the RPC SERVICES alone (you need them period, or you will lag like hell, & especially for this) & taskmgr.exe & disable trayicon stuff too.
The list of those files? Appear dead-up locked, a temp file in your %Temp%/%Tmp% it looks like & by a process, local or not. Which is why the NEXT part may have to be done:
Yes, even sometimes on the network, (hence, WHY the command above MAY look like a network UNC path), but it SHOULD work!
It works, basically on a network level, first by dropping said connection & then doing a std. "change the first character of the filename" delete.
If needed, ontop of that? Drop your internet connection, disable it, temporarily, & try again.
SHOULD ALL/ANY OF THIS FAIL?
I have a program, a secure deleter I wrote, that SHOULD do it, but that I have to send you... I wrote it myself, it works.
APK
P.S.=> On the perflib stuff? I can see the performance counters generation being enabled & LOCKING that file too because it appears to be THEIR data!
Plus, some apps use it like COOLMON too, which I helped correct a bug in w/ the authors while @ 3dfiles.com regarding perfcounters NOT being on crashing it!
The performance counter generation it is creating its log & data temp files... all read from the FAKE registry hive in RAM call HKEY_DYN_DATA & used by the OS & apps like COOLMON...
So, to DISABLE ALL performance counters generation & data? Just first reboot, & try again AFTER using this FREE reskit tool from MS:
exctrlst.exe
Extensible Performance Counters enable/disable using it & do what I stated above, IF needed upon reboot, because no more HKEY_DYN_DATA is being formed, or perf counters generated (except maybe WMI stuff), & that dat file should be deletable now... apk