Tungar
December 11th 03, 09:37 PM
Hi,
I checked the sigs with the default scan. The only files
returned without digital signatures are the Nv* files for
Nvidia cards. the driver for my USB 2.0 ports on my board
and the ultra 133 driver for my onboard promise
controller. Nothing revealing there.
I also did an advanced scan and singled out *.sys files -
again, nothing to report there. I finally did a scan on
*.dll files, but the results were so overwhelming (when
check sudirectories was ticked) as to be impractical to
diagnose what file might be at fault.
As for chkntfs, I have already tried to get chkntfs to
recognise that the volume is dirty, but it doesnt deem it
to be a serious enough problem to warrant a chkdsk at
boot time. I disagree with chkntfs though, as when the
amount of unused indexes for that file rises above 500
(there or abouts), then hdd access on that volume becomes
noticably slower. As it goes on the performance is
proportional to the number of unused entries.
In fact, I do believe there may be a problem with
chkntfs, even since the hotfix and SP1 which supposedly
fixed the issue where chkdsk could run at boot time...as
well, I have had some volumes that have been
horrendously 'dirty' - e.g. crosslinked files, bad free
space assignment etc - and chkntfs just hasnt instigated
a chkdsk. Perhaps this may be linked to my problem, even
though the dirty volumes have been attached to the
regular onboard via/100 controllers.
Perhaps the trouble all relates to having the boot volume
on this ide 'scsi' channel - I know that XP can handle
booting off scsi no probs, but maybe the driver is
poor...and I have tried several different versions of the
driver & have run fine with the current driver in the
past.
ho hum
Anyhoo, thanks for the tip, though unfortunately I'm no
further ahead...got any more ideas?
Chairs
Tungar
>-----Original Message-----
>Try going to run type:SigVerif After the initial run,
> use the "check other areas" button,you can set to .dll
> etc.,for driver signatures.In cmd prompt type:Chkntfs
>>-----Original Message-----
-snip-
I checked the sigs with the default scan. The only files
returned without digital signatures are the Nv* files for
Nvidia cards. the driver for my USB 2.0 ports on my board
and the ultra 133 driver for my onboard promise
controller. Nothing revealing there.
I also did an advanced scan and singled out *.sys files -
again, nothing to report there. I finally did a scan on
*.dll files, but the results were so overwhelming (when
check sudirectories was ticked) as to be impractical to
diagnose what file might be at fault.
As for chkntfs, I have already tried to get chkntfs to
recognise that the volume is dirty, but it doesnt deem it
to be a serious enough problem to warrant a chkdsk at
boot time. I disagree with chkntfs though, as when the
amount of unused indexes for that file rises above 500
(there or abouts), then hdd access on that volume becomes
noticably slower. As it goes on the performance is
proportional to the number of unused entries.
In fact, I do believe there may be a problem with
chkntfs, even since the hotfix and SP1 which supposedly
fixed the issue where chkdsk could run at boot time...as
well, I have had some volumes that have been
horrendously 'dirty' - e.g. crosslinked files, bad free
space assignment etc - and chkntfs just hasnt instigated
a chkdsk. Perhaps this may be linked to my problem, even
though the dirty volumes have been attached to the
regular onboard via/100 controllers.
Perhaps the trouble all relates to having the boot volume
on this ide 'scsi' channel - I know that XP can handle
booting off scsi no probs, but maybe the driver is
poor...and I have tried several different versions of the
driver & have run fine with the current driver in the
past.
ho hum
Anyhoo, thanks for the tip, though unfortunately I'm no
further ahead...got any more ideas?
Chairs
Tungar
>-----Original Message-----
>Try going to run type:SigVerif After the initial run,
> use the "check other areas" button,you can set to .dll
> etc.,for driver signatures.In cmd prompt type:Chkntfs
>>-----Original Message-----
-snip-