Solved Chkdsk results

[ICIT2LOL]

Agree

Yeah Neutron it certainly is a mystery why the change to wininit came about, as I found refs to chkdsk way back then.

THe chkdsk I ran last night I ran from Computer > Properties > Tools > and so on perhaps if I just do it from Start > type chkdsk and take it from there tonight and see what happens.

What has got me stumped is why is my mates machine doing it also??

However trawling right back to 2009 I couldn't find one chkdsk in his machine apart form the one last night!

 

[ICIT2LOL]

Neutron

I did what I said I would do last night as you told me that the 1001 event was a normal start up thing.

I was told that to do a chkdsk that one had to go to Computer > right click > Properties > Tools > check disk > schedule > close out and then reboot, which I have been doing giving us this wininit thing.
So I thought about it on the way to work and got home last night and ran chkdsk from Start > chkdsk > Run as admin - a little black screen popped up and the check was over in a very short time indeed.

So I have obviously been wrongly advised as to how to perform a chkdsk!! Just out of curiousity I ran the chkdsk the same way a short time after and you can see the result in the pics. Plus you can note the time it took for the second wininit one to start up as I did the set up about two minutes after the first chkdsk ended that I accessed from Start.

There is a little info in the reports that may be of interest but it all looks reasonably ok.

(This happened on all four machines)


Look thanks for staying with me on this one I know I am a ruddy nuisance, and I could really give the person a serve for telling me how to do it - but won't because it's not worth the grief.

You're a real friend - a lot would have dumped me ages ago!!

 

[Neutron16]

No problem, mate!

It is good, that you have figured that out.

Btw, when you run chkdsk from Windows (chkdsk-results-x picture), it runs in READ-only mode. So it can't fix anything, just reports. If you want it to fix and move stuff it has to be started before Windows (chkdsk-results-xx.png picture).

 

[ICIT2LOL]

Thanks a million

Thanks so much Neutron if it were not for your input I would be still scratching around for an answer.

It was your ref to the 1001 and 26212 codes that got me thinking.

Now just one last thing when you say if you want to fix anything it has to be started before Windows does this mean hit some F key as you start the machine up?

Anyway I'll take a trip through the tutorials too a bit more often as I have relied on someone who has either given me a gooseberry or just doesn't know themselves.

Still thanks so much again for your time and patience!!

 

[Neutron16]

You are welcome.

/f is a parameter of chkdsk. Some programs will perform something different if they will be run without parameter, with a one parameter or with another parameter. For example if you use parameter -private on IE9 it will start in Private mode.

"%programfiles%\Internet Explorer\iexplore.exe" -private

Generally, to find out if a Windows file has any parameters, you need to start CMD and type there the name of the program and /? behind it.
Here is what you could get if you type chkdsk /? in CMD (Command Prompt).

CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B]


  volume          Specifies the drive letter (followed by a colon),
                  mount point, or volume name.
  filename        FAT/FAT32 only: Specifies the files to check for fragmentation
.
  /F              Fixes errors on the disk.
  /V              On FAT/FAT32: Displays the full path and name of every file
                  on the disk.
                  On NTFS: Displays cleanup messages if any.
  /R              Locates bad sectors and recovers readable information
                  (implies /F).
  /L:size         NTFS only:  Changes the log file size to the specified number
                  of kilobytes.  If size is not specified, displays current
                  size.
  /X              Forces the volume to dismount first if necessary.
                  All opened handles to the volume would then be invalid
                  (implies /F).
  /I              NTFS only: Performs a less vigorous check of index entries.
  /C              NTFS only: Skips checking of cycles within the folder
                  structure.
  /B              NTFS only: Re-evaluates bad clusters on the volume
                  (implies /R)

The /I or /C switch reduces the amount of time required to run Chkdsk by
skipping certain checks of the volume.

chkdsk /F forces chkdsk to fix errors.
If you run chkdsk without /F, you will get read-only mode.

But if you use chkdsk /f in Windows it might tell you (depending on is it system disc or not) that volume needs to me dismounted first.
If you dismount that volume, you will lose access to it (access will be locked to chkdsk only for a period of checking).
You might not want to do that on a system disc if this option is available.

Here is more info from Microsoft.

 

[ICIT2LOL]

Thanks

Neutron you are a legend thanks so much for that mate I so much appreciate as I really am not that savvy and you have taken the time and trouble to fill me in.

What else can I say??