Problems With Windows 2000

[Arpan De]

I am working on Windows 2000 Professional (P-III, 192 MB RAM, 20GB Hard Disk). Everything was running fine till last 10-12 days
after which I find that my system clock doesn't show the correct time when I start Windows. For e.g. if I switch off my PC at
10:00 PM tonight & then switch it on the next day at any time, I find that the system clock still shows the time as 10:00 PM
(though the date changes correctly). This compels me to manually reset the time everyday when my PC starts. Please note that after
I set the correct time, the clock continues showing the correct time. The problem occurs if & only if I switch off my PC & then
start it after, say, 4-5 hours (or more). Why is this happening? Any solution to rectify this problem?? This problem happens only
with the time & not with the date.

Secondly, I find that suddenly my PC hangs for just a second or two, then starts working for the next 35 seconds or so, then again
hangs & then again starts working.....so on & so forth. This problem occurs at any time by itself & strangely enough this abnormal
behavior stops also by itself!! How do I get rid of this problem? It's a petty problem but is highly irritating!!!

Lastly, I find that my PC suddenly restarts by itself without any action from my end. How do I overcome this barrier as it wastes
a lot of my time? Today, while Windows was disc checking (since my PC restarted suddenly), I was shown the following error:

D:\Documents And Settings\Administrator\Local Settings\Content.IE5\01W9MTOP\SomePage.htm is cross-linked on allocation unit
917542.

What does this error mean? Please note that I created the HTML file SomePage.htm today & this problem of restarting all by itself
started today itself. Has this got any connection with the restarting problem? I doubt it!!! Also SomePage.htm is not the only
file I have created today; I created another 4-5 HTML & ASP files also along with SomePage.htm today.

Thanks,

Arpan

 

[Smile Extender]

If your computer is older like it seems to be, the battery used to keep bios
clock alive is propably exhausted and needs replacing. When your computer
looses correct time while power is off, but can keeps it when power on, the
battery is finito.

That cross-linked message means that there is disk problem. Two different
files are marked to contains same disk areas (sectors). That is not allowed
except with NTFS hardlinks. You might get cross-links if your computer
reboots or crashes just middle of disk operations. Normaly scandisk/chkdsk
can fix these problems.

When bios clock doens't keep correct time, that can cause other problems
too. You should of course check for viruses and spyware jsut to be sure you
don't have any parasites.

I am working on Windows 2000 Professional (P-III, 192 MB RAM, 20GB Hard

Disk). Everything was running fine till last 10-12 days

after which I find that my system clock doesn't show the correct time when

I start Windows. For e.g. if I switch off my PC at

10:00 PM tonight & then switch it on the next day at any time, I find that

the system clock still shows the time as 10:00 PM

(though the date changes correctly). This compels me to manually reset the

time everyday when my PC starts. Please note that after

I set the correct time, the clock continues showing the correct time. The

problem occurs if & only if I switch off my PC & then

start it after, say, 4-5 hours (or more). Why is this happening? Any

solution to rectify this problem?? This problem happens only

with the time & not with the date.

Secondly, I find that suddenly my PC hangs for just a second or two, then

starts working for the next 35 seconds or so, then again

hangs & then again starts working.....so on & so forth. This problem

occurs at any time by itself & strangely enough this abnormal

behavior stops also by itself!! How do I get rid of this problem? It's a

petty problem but is highly irritating!!!

Lastly, I find that my PC suddenly restarts by itself without any action

from my end. How do I overcome this barrier as it wastes

a lot of my time? Today, while Windows was disc checking (since my PC

restarted suddenly), I was shown the following error:

D:\Documents And Settings\Administrator\Local

Settings\Content.IE5\01W9MTOP\SomePage.htm is cross-linked on allocation
unit

917542.

What does this error mean? Please note that I created the HTML file

SomePage.htm today & this problem of restarting all by itself

started today itself. Has this got any connection with the restarting

problem? I doubt it!!! Also SomePage.htm is not the only

 

[Arpan De]

Hello Smile,

Thanks for your suggestions but I couldn't follow what do you mean by the word 'finito'? I am quite sure that viruses & worms
don't exist in my system as my anti-virus is upto date & I also get my system checked everyday. As you have pointed out when the
BIOS clock doesn't keep correct time, other problems can be caused. As far as the hanging & resuming back by itself is concerned,
could there be any other reasons behind this problem so that it can be got rid of irrespective of whether the BIOS clock functions
properly or not?

Thanks once again,

Regards,

Arpan1



: If your computer is older like it seems to be, the battery used to keep bios
: clock alive is propably exhausted and needs replacing. When your computer
: looses correct time while power is off, but can keeps it when power on, the
: battery is finito.
:
: That cross-linked message means that there is disk problem. Two different
: files are marked to contains same disk areas (sectors). That is not allowed
: except with NTFS hardlinks. You might get cross-links if your computer
: reboots or crashes just middle of disk operations. Normaly scandisk/chkdsk
: can fix these problems.
:
: When bios clock doens't keep correct time, that can cause other problems
: too. You should of course check for viruses and spyware jsut to be sure you
: don't have any parasites.
:
:
:
: : > I am working on Windows 2000 Professional (P-III, 192 MB RAM, 20GB Hard
: Disk). Everything was running fine till last 10-12 days
: > after which I find that my system clock doesn't show the correct time when
: I start Windows. For e.g. if I switch off my PC at
: > 10:00 PM tonight & then switch it on the next day at any time, I find that
: the system clock still shows the time as 10:00 PM
: > (though the date changes correctly). This compels me to manually reset the
: time everyday when my PC starts. Please note that after
: > I set the correct time, the clock continues showing the correct time. The
: problem occurs if & only if I switch off my PC & then
: > start it after, say, 4-5 hours (or more). Why is this happening? Any
: solution to rectify this problem?? This problem happens only
: > with the time & not with the date.
: >
: > Secondly, I find that suddenly my PC hangs for just a second or two, then
: starts working for the next 35 seconds or so, then again
: > hangs & then again starts working.....so on & so forth. This problem
: occurs at any time by itself & strangely enough this abnormal
: > behavior stops also by itself!! How do I get rid of this problem? It's a
: petty problem but is highly irritating!!!
: >
: > Lastly, I find that my PC suddenly restarts by itself without any action
: from my end. How do I overcome this barrier as it wastes
: > a lot of my time? Today, while Windows was disc checking (since my PC
: restarted suddenly), I was shown the following error:
: >
: > D:\Documents And Settings\Administrator\Local
: Settings\Content.IE5\01W9MTOP\SomePage.htm is cross-linked on allocation
: unit
: > 917542.
: >
: > What does this error mean? Please note that I created the HTML file
: SomePage.htm today & this problem of restarting all by itself
: > started today itself. Has this got any connection with the restarting
: problem? I doubt it!!! Also SomePage.htm is not the only
: > file I have created today; I created another 4-5 HTML & ASP files also
: along with SomePage.htm today.
: >
: > Thanks,
: >
: > Arpan
: >
: >
: > ---
: > Outgoing mail is certified Virus Free.
: > Checked by AVG anti-virus system (http://www.grisoft.com).
: > Version: 6.0.502 / Virus Database: 300 - Release Date: 18/07/2003
: >
: >
:
:

 

[Dan Seur]

'finito' means 'dead or dying.' One explanation for clock misbehavior is
that the little watch-type battery on the mainboard is so close to dead
that it doesn't have the juice to keep the little clock circuit running
when external power is off. That battery is not used when external power
is on; it at least gets some rest, and may even pick up a small charge.

Your system hiccuping problem - pause & resume, essentially - can be
caused by automatic built-in "retry" circuitry in the controller/hard
drive subsystem. If a read or write access to a hard drive fails, that
circuitry keeps reissuing the command up to some preset number of times
or until the access is successful. If a drive is gradually failing, you
can expect these freezes to get longer and longer - sometimes many
minutes - until one day the system declares the drive dead - or simply
fails to boot. (More rarely, this might be a failing controller or
motherboard.)

To test any drive, get a downloadable diagnostic from that drive's
manufacturer; they all have them and they're free. It will be a diskette
image that includes a primitive DOS-type system, and is bootable from
A:. Make sure you have a diskette available. This sort of diagnostic
usually cannot (and should not) be run from within an OS like NT or W2k;
it requires special "hands-on-the-hardware-itself" capability to issue
various diagnostic commands not normally available to the OS. NT-class
systems go to great lengths to prevent anything but the OS kernel itself
ever having such hands-on to the hardware. It's a matter of security and
integrity, and it's why they so seldom* crash. Applications can easily
shoot themselves, but seldom* the system or other apps.

* relatively speaking. It's an imperfect world...

The hiccup, or freeze, occurs because the OS is unaware of the furious
activity occurring around the hard drive hardware. All the OS knows is
that the access request has not completed - and it must wait until it
receives an OK to that I/O request. (Normally, the wait is measured in
milliseconds.) If the access request involves something the OS needs in
order to perform some very high-priority system function, like get a
pagefile or some system module from disk, and the retry circuitry kicks
in, that can get to be a very long wait.

Incidentally, from time to time those diagnostics can repair the
problem. Things like very small head-alignment corrections can be done,
to better align the read/write heads with the tracks on the disk surface
when over time the heads (mechanically jerking back and forth) "drift".