Damaged sectors

[Cyan]

Hi.
I've a request.

I've an HD with a simple LOGIC error that have determined a fake phisical
damaged sector (highest PCI BUS or not correct shutdown).
I'm SURE that isn't a phisical error.

Each time that I start up my windows it say me that there are damaged
sectors, and it wants to perform a VERY LONG phisical test.
How I can turn off this error?

I DON'T want to turn off my scandisk (AUTOSCAN=0).

I want only know where windows wrote the flag that remember itself to
perform phisical scandisk.

No problem to use Norton Diskedit, beacuse I'm sure that I must change a
byte everywere, in the bootsector or near it.

Thanks for answer.

 

[Folkert Rienstra]

Hi.
I've a request.

I've an HD with a simple LOGIC error that have determined a fake
phisical damaged sector (highest PCI BUS or not correct shutdown).
I'm SURE that isn't a phisical error.

Each time that I start up my windows it say me that there are damaged
sectors, and it wants to perform a VERY LONG phisical test.
How I can turn off this error?

Why do a workaround? Remove that damaged sector.

I DON'T want to turn off my scandisk (AUTOSCAN=0).

So remove that damaged sector.

I want only know where windows wrote the flag that remember itself to
perform phisical scandisk.

And how would that help? Windows is likely to set it again once you tog-
gled it. To change it is likely more time consuming than to cancel scandisk.

No problem to use Norton Diskedit, beacuse I'm sure that I must change
a byte everywere, in the bootsector or near it.

It is likely in the registry.

 

[Cyan]

So remove that damaged sector.

Maybe my english very bad, but I've sayd that THERE ISN'T any damaged
sector.

Windows BELIEVE that there are damaged sectors, but there'rent.

Windows has had troubles in write attempt due to PCI bus too high or
overheat.

It is likely in the registry.

It's impossible, because ANY hd with problems and scandisk required, mounted
in ANOTHER PC with ANOTHER windows (and another registry, of course) give
the same error.

Example: if I turn off my PC from power switch and I mount the HD in another
PC, Windows say me that scandisk is required.
The flag isn't in the registry.

Thank you anyway.

 

[Folkert Rienstra]

Maybe my english very bad, but I've sayd that THERE ISN'T any damaged
sector.

It's not bad english, just a lacking description of the error that you are
encountering and the lack of proper evidence that there aren't bad sectors.

Windows BELIEVE that there are damaged sectors, but there aren't.

Which you know how?

Windows has had troubles in write attempt due to PCI bus too high or
overheat.

A likely cause for a 'bad' sector.
That and "wants to perform a VERY LONG phisical test" supports
that there actually is a bad sector that hasn't been 'cured'.

It's impossible, because ANY hd with problems and scandisk required, mounted
in ANOTHER PC with ANOTHER windows (and another registry, of course) give
the same error.

Example: if I turn off my PC from power switch and I mount the HD in
another PC, Windows say me that scandisk is required.

The flag isn't in the registry.

Correct, I checked my news store, it wasn't the registry. It's in the FAT.

From a thread in juli 2002 Re: Win98 Scandisk flag

http://www.microsoft.com/technet/tr...Net/prodtechnol/win98/reskit/part2/wrkc10.asp

How Win.com Determines Improper Shutdown
Of the first 112 bytes of the FAT32, the first 8 bytes are reserved. The
eighth byte of the reserved area, by default, is 0F. The virtual file
allocation table (VFAT) and the Windows 98 shutdown process manipulate
the fourth bit of this byte to 1 or 0.

0 = VFAT has written to disk
1 = Windows has properly shutdown

When you write a file to the disk, VFAT handles the write. During the
write, VFAT clears the fourth bit to 0 (07h). When Windows 98 exits
properly, this bit is reset to 1. During reboot, Win.com reads that bit.
If it is set to 0, it runs ScanDisk to check the drive for errors.

Hard Sector Error. Windows 98 detects a hard sector error during
startup. This process toggles the third bit to zero (0Bh). When detected
during startup, Windows 98 automatically launches ScanDisk with a
surface scan test.

<EQ>

This still says there might be a bad sector in existence that windows keeps
bumping into and keeps track of.

 

[Salvo Ognibene]

and the lack of proper evidence that there aren't bad sectors.

It's happened many times.
1) when an HD failur driver occours.
2) when an HD overheat occours (termal protection, windows cannot write)
3) when there's a blackout and windows cannot update the VFAT
4) etc...

Just perform a complete phisical scandisk. Windows believe that there is not any error, and can't give me the scandisk error
anymore.

That and "wants to perform a VERY LONG phisical test" supports
that there actually is a bad sector that hasn't been 'cured'.

THERE IS NOT ANY SECTOR TO BE CURED.
WINDOWS CAN'T KNOW __NOW__ IF THERE ARE, but it supposed that there are.

__SUPPOSED__

Correct, I checked my news store, it wasn't the registry. It's in the FAT.
From a thread in juli 2002 Re: Win98 Scandisk flag

I've found this article tonight.
Thanks hovewer.

This still says there might be a bad sector in existence that windows keeps
bumping into and keeps track of.

Exact: MIGHT BE! BUT_NOT_ SURE!
But, since I'me sure that there is not, I wanna turn off this warning, without perform the scandisk.

Thanks.

 

[Cyan]

and the lack of proper evidence that there aren't bad sectors.

It's happened many times.
1) when an HD failur driver occours.
2) when an HD overheat occours (termal protection, windows cannot write)
3) when there's a blackout and windows cannot update the VFAT
4) etc...

Just perform a complete phisical scandisk. Windows believe that there is not
any error, and can't give me the scandisk
error
anymore.

That and "wants to perform a VERY LONG phisical test" supports
that there actually is a bad sector that hasn't been 'cured'.

THERE IS NOT ANY SECTOR TO BE CURED.
WINDOWS CAN'T KNOW __NOW__ IF THERE ARE, but it supposed that there are.

__SUPPOSED__

Correct, I checked my news store, it wasn't the registry. It's in the FAT.
From a thread in juli 2002 Re: Win98 Scandisk flag

I've found this article tonight.
Thanks hovewer.

This still says there might be a bad sector in existence that windows keeps
bumping into and keeps track of.

Exact: MIGHT BE! BUT_NOT_ SURE!
But, since I'me sure that there is not, I wanna turn off this warning,
without perform the scandisk.

Thanks.

 

[Barry OGrady]

Maybe my english very bad, but I've sayd that THERE ISN'T any damaged
sector.

Your english is fine.

Windows BELIEVE that there are damaged sectors, but there'rent.

Windows has had troubles in write attempt due to PCI bus too high or
overheat.

I had the same problem due to a poor power connection.

It's impossible, because ANY hd with problems and scandisk required, mounted
in ANOTHER PC with ANOTHER windows (and another registry, of course) give
the same error.

I too found that.

Example: if I turn off my PC from power switch and I mount the HD in another
PC, Windows say me that scandisk is required.
The flag isn't in the registry.
True.

Thank you anyway.

I would like to know the same information.


-Barry
========
Web page: http://members.optusnet.com.au/~barry.og
Atheist, radio scanner, LIPD information.
Voicemail/fax number +14136227640

 

[Barry OGrady]

It's happened many times.
1) when an HD failur driver occours.
2) when an HD overheat occours (termal protection, windows cannot write)
3) when there's a blackout and windows cannot update the VFAT
4) etc...

5) When a poor power connection causes intermittent power to the drive.

Just perform a complete phisical scandisk. Windows believe that there is not
any error, and can't give me the scandisk
error
anymore.




THERE IS NOT ANY SECTOR TO BE CURED.
WINDOWS CAN'T KNOW __NOW__ IF THERE ARE, but it supposed that there are.

__SUPPOSED__



I've found this article tonight.
Thanks hovewer.



Exact: MIGHT BE! BUT_NOT_ SURE!
But, since I'me sure that there is not, I wanna turn off this warning,
without perform the scandisk.

I want the same, to avoid an overnight surface check but still allow scandisk to run if there
is a real problem.

Thanks.

-Barry
========
Web page: http://members.optusnet.com.au/~barry.og
Atheist, radio scanner, LIPD information.
Voicemail/fax number +14136227640

 

[Casomail]

I would like to know the same information.

I've found this, but doesn't tell anything about damaged sectors:
----

How WIN.COM determines Improper Shutdown
The VFAT file system has the ability to record an improper Windows shutdown.
Of the first 112 bytes of the FAT32, the first 8 bytes are reserved.
The eighth byte of the reserved area, by default, is 0F. The virtual
file allocation table (VFAT) and the Windows 98 shutdown process
manipulate the fourth bit of this byte to 1 or 0.
0 = VFAT has written to disk
1 = Windows has properly shutdown
When you write a file to the disk, VFAT handles the write. During the
write, VFAT clears the fourth bit to 0 (07h). When Windows 98 exits
properly, this bit is reset to 1. During reboot, Win.com reads that bit.
If it is set to 0, it runs ScanDisk to check the drive for errors.

Disabling ScanDisk at Boot.

There is a way to disable the improper shutdown check. It is in the
Msdos.sys file under [OPTIONS]. The parameters for AutoScan are as follows:

Value
Definition

AUTOSCAN = 0 Ignore the bits in the reserved FAT entry
AUTOSCAN = 1 Default behavior, run ScanDisk

 

[Casomail]

"Casomail" <[email protected]> ha scritto nel messaggio

It's alway me: Cyan.

 

[Folkert Rienstra]

5) When a poor power connection causes intermittent power to the drive.

That's a potential 'bad' sector cause.
It won't be a physical one but it is still a bad sector to the system.

I want the same, to avoid an overnight surface check but still allow scandisk to run
if there is a real problem.

I would expect that a successfully completed scandisk would set the bits in
the FAT back to normal. Are you two saying it doesn't?

 

[Folkert Rienstra]

I've found this, but doesn't tell anything about damaged sectors:

Obviously, since you snipped the part that handled that.
Do you even bother to read the answers you get?

----

How WIN.COM determines Improper Shutdown
The VFAT file system has the ability to record an improper Windows shutdown.
Of the first 112 bytes of the FAT32, the first 8 bytes are reserved.
The eighth byte of the reserved area, by default, is 0F. The virtual
file allocation table (VFAT) and the Windows 98 shutdown process
manipulate the fourth bit of this byte to 1 or 0.
0 = VFAT has written to disk
1 = Windows has properly shutdown
When you write a file to the disk, VFAT handles the write. During the
write, VFAT clears the fourth bit to 0 (07h). When Windows 98 exits
properly, this bit is reset to 1. During reboot, Win.com reads that bit.
If it is set to 0, it runs ScanDisk to check the drive for errors.

Disabling ScanDisk at Boot.

There is a way to disable the improper shutdown check. It is in the
Msdos.sys file under [OPTIONS]. The parameters for AutoScan are as follows:

Value
Definition

AUTOSCAN = 0 Ignore the bits in the reserved FAT entry
AUTOSCAN = 1 Default behavior, run ScanDisk