This blog will provide technical data and insights into performance and reliability issues surrounding file system performance.
We hope to cover all topics related to system performance including defrag whether you are running SANs, NAS, workstations, servers,
SSD's or other systems. We will provide interesting anecdotes, white papers, and related story topics on defragmentation and other
performance issues. The blog is intended to be personal rather than a formal Diskeeper website. You will read personal viewpoints
on our products and where we see the industry and our company going. We are excited to have this opportunity to share our product
knowledge and insight, and hope this information helps you. We encourage your comments and look forward to you following this blog.
by Michael
27. April 2007 17:39
Preface: this article refers to making direct edits to the Windows Registry. If you are not experienced with this subject, ask your company's IT Administrator or a computer-expert friend/neighbor for help.
Our Tech Support group has seen a few reports of this error (Program not found - skipping AUTOCHECK) from customers when running Diskeeper's bootime defrag. The error starts early in the boot process while the Session Manager process (smss.exe) is busy getting the system up and running. Smss.exe is critical to loading the paging file, initializing the registry and loading kernel components. But, before it does any of that it looks to a registry key called BootExecute. At that location it launches any applications listed. Session Manager then looks to the Windows system32 folder for particular executables it has been instructed to launch. By default there is only one program listed here - autochk.exe, the boot-time version of chkdsk, which will run if there are any file system inconsistency flags detected (i.e. volume dirty bit is set).
Read on for the solution...
Currently rated 3.1 by 12 people
- Currently 3.083333/5 Stars.
- 1
- 2
- 3
- 4
- 5
Tags:
General