A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Allocation and lost clusters



 
 
Thread Tools Display Modes
  #1  
Old June 14th 04, 04:32 PM
Bryan
external usenet poster
 
Posts: n/a
Default Allocation and lost clusters

I have tried for almost 2 weeks to try to solve my
problems. They are as follow's: My first and most
disturbing is this,.... WINDOWS\ALLUSE~1\APPLIC~1
\AOL.\C_AMER~1.OA\IDB\main.idx this must be an AOHell
problem but I've tried everything they've suggested I also
get Lost Clusters when this happens. This ONLY happens
when playing the MMOG WWIIOnline. The allocation error
say's that too little or too much space is used for this.
I suspect that it would be too little space and was
wondering how to aalocate more for it, or am I off base
here? And what about the lost clusters. I also believe if
the allocation problems fixed those will go away as well??
I've ran Nortons scan disc many times Ive ran spybot I've
clear all cache and temp folders and defragged,...Ive
reloaded drivers,..checked my connections and cables. I
even took my entire system apart,..cleaned everything and
still have the same problems. All help and suggestions are
VERY GREATLY APPRECIATED. TIA.
BRYAN ASP26
  #2  
Old June 16th 04, 12:14 PM
H Leboeuf
external usenet poster
 
Posts: n/a
Default Allocation and lost clusters

Lost cluster is not good. It could mean some Hard Drive issues.
http://support.microsoft.com/?kbid=67321
--



Henri Leboeuf
Web page: http://www.colba.net/~hlebo49/index.htm
===
"Bryan" wrote in message
...
I have tried for almost 2 weeks to try to solve my
problems. They are as follow's: My first and most
disturbing is this,.... WINDOWS\ALLUSE~1\APPLIC~1
\AOL.\C_AMER~1.OA\IDB\main.idx this must be an AOHell
problem but I've tried everything they've suggested I also
get Lost Clusters when this happens. This ONLY happens
when playing the MMOG WWIIOnline. The allocation error
say's that too little or too much space is used for this.
I suspect that it would be too little space and was
wondering how to aalocate more for it, or am I off base
here? And what about the lost clusters. I also believe if
the allocation problems fixed those will go away as well??
I've ran Nortons scan disc many times Ive ran spybot I've
clear all cache and temp folders and defragged,...Ive
reloaded drivers,..checked my connections and cables. I
even took my entire system apart,..cleaned everything and
still have the same problems. All help and suggestions are
VERY GREATLY APPRECIATED. TIA.
BRYAN ASP26


  #3  
Old June 18th 04, 04:30 PM
cquirke (MVP Win9x)
external usenet poster
 
Posts: n/a
Default Allocation and lost clusters

On Wed, 16 Jun 2004 07:14:47 -0400, "H Leboeuf"

Lost cluster is not good. It could mean some Hard Drive issues.


Don't confuse "lost clusters" with "bad clusters" or "bad sectors".


A "lost cluster chain" results when a file system update is
interrupted. Sometimes the directory entry may have been deleted (or
has not yet been created) while data has already been written into a
cluster chain that is now chained out of the free space in FAT.

In that case, the cluster chain is noted to be chained out of free
space, but no other cluster chain links into it, and no directory
entry points to the (start of the) chain. It is, in essence, a lost
file or subdir, and the fix is to create a new directory entry that
points to it. No name, path or true length is known, so an arbitrary
name is created in the root to point to it, and the full length of the
chain is used for the file's true length in bytes.

There's another sequence that gives rise to lost cluster chains. A
file update is interrupted such that there is a mismatch between the
length of the file in bytes, as held in the dir entry that defines the
file, and the implicit length as per number of clusters chained into
the file's data area. Scandisk usually "fixes" this by truncating the
file's FAT chain as per the directory entry's length in bytes.

The rest of the chain is left as a chain, and will later be picked up
as a lost cluster chain. Depending on whether Scandisk is set to save
or delete these, it will either be pointed to as described earlier, or
those cluster addresses will be set to zero, i.e. "unused".


Bad clusters are a whole nother order of pain, and have nothing to do
with interrupted file operations or bad exits - they are a physical
defects in the disk at the hardware level. They can cause lockups and
bad exits, so associated file system logic errors are common.

A bad cluster is a cluster that contains one or more unreadable
sectors. A bad sector is exactly what it sounds like :-)



------------ ----- ---- --- -- - - - -

Our senses are our UI to reality
------------ ----- ---- --- -- - - - -

  #4  
Old June 19th 04, 12:33 PM
H Leboeuf
external usenet poster
 
Posts: n/a
Default Allocation and lost clusters

Thanks,


--

Henri Leboeuf
Web page: http://www.colba.net/~hlebo49/index.htm
===

"cquirke (MVP Win9x)" wrote in message
...
On Wed, 16 Jun 2004 07:14:47 -0400, "H Leboeuf"

Lost cluster is not good. It could mean some Hard Drive issues.


Don't confuse "lost clusters" with "bad clusters" or "bad sectors".


A "lost cluster chain" results when a file system update is
interrupted. Sometimes the directory entry may have been deleted (or
has not yet been created) while data has already been written into a
cluster chain that is now chained out of the free space in FAT.

In that case, the cluster chain is noted to be chained out of free
space, but no other cluster chain links into it, and no directory
entry points to the (start of the) chain. It is, in essence, a lost
file or subdir, and the fix is to create a new directory entry that
points to it. No name, path or true length is known, so an arbitrary
name is created in the root to point to it, and the full length of the
chain is used for the file's true length in bytes.

There's another sequence that gives rise to lost cluster chains. A
file update is interrupted such that there is a mismatch between the
length of the file in bytes, as held in the dir entry that defines the
file, and the implicit length as per number of clusters chained into
the file's data area. Scandisk usually "fixes" this by truncating the
file's FAT chain as per the directory entry's length in bytes.

The rest of the chain is left as a chain, and will later be picked up
as a lost cluster chain. Depending on whether Scandisk is set to save
or delete these, it will either be pointed to as described earlier, or
those cluster addresses will be set to zero, i.e. "unused".


Bad clusters are a whole nother order of pain, and have nothing to do
with interrupted file operations or bad exits - they are a physical
defects in the disk at the hardware level. They can cause lockups and
bad exits, so associated file system logic errors are common.

A bad cluster is a cluster that contains one or more unreadable
sectors. A bad sector is exactly what it sounds like :-)



------------ ----- ---- --- -- - - - -

Our senses are our UI to reality
------------ ----- ---- --- -- - - - -


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 11:39 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.