Off-Topic > Off-Topic - Tiny Core Lounge
wi-fi
cast-fish:
Hello
Well, if you see the OP here, there were computer malfunctioning symptoms manifest in software at
desktop level not working right.
A complete overhaul of the HDD and OS seemed to solve this issue.
After a couple of weeks usage, which is about as much as win32 can take, well here we are again, the hard drive will just suddenly lock into read loop. Light solid.
This is exactly what happened a while back, maybe a month and it first manifest in badly executing
desktop apps and software. It seemed to tolerate it's own demise....win32...for a few weeks
with bad software Initializing of apps and what have you. AGain, you would still sometimes after long usage see the hard drive lock into write mode.
eventually the comuter became hasstle and really not usable or reliable and that is when i did
the overhaul mentioned above which seemed to solve it.
1) I stripped the hard drive. (On the first attempt it indeed reported a hard drive error at Sector Block zero)
2) started completely again and from power up stripped the whole HDD again. THis time it was successful and these were both single ONE PASS attempts....just writting Ones.
SO THAT WAS A SUCCESS
3) the OS went back on with just ONE non read file, it correctly read that file on the second attempt
after pressing enter.
4) The win32 computer worked fine, like i say above, for maybe 3 plus weeks.
So now here we are, again , after prolonged 14 hour usage yesterday i actually "realtime" saw the fault take place and as i was watching NYC live on earthcam the hard drive went into a read loop.
http://earthcam.com/usa/newyork/timessquare/#?cam=tsrobo3
I believe that this hard drive has a fault, but i am more sceptical than that because it;s my nature
and i am wondering if this compaq motherboard was a recall ?....way back in the 2000's (all these machines) as they may have had some issue with certain brands of hard drives. It has a HITACHI
inside it.
The machine is currently working again now, exactly as before , as if perfect, until the next time a
crossover point is reached of either temperature?....caching hard drive reads?...or an intermittent
hard drive heads/sectors problem.
Point in note, the OS has hardly ANY software even installed on it....completely blank Fresh OS
and the perifpherals are all installed correctly with correct win32 drivers.
All these thread details about WI FI is a kind of stick in the mud, distraction from what was really causing the issue, a deep problem inside win32 or the hard-drive hardware is failing....well the former is NOT the case, because win32 is FRESH on this next overhaul i did. So it' all points to a hard-drive problem.
THe tool i used on the hard-drive is military grade. It DID say that the drive has an error.(Bad sector) It could be compounded further by intermittent long term usage Temperature issues on the laptop. 0___0
Guys at TCL.....it looks like the real safety net of Tinycore is going to come into play again for me
here as a solid usable OS on dinasour hardware.....and i thank you for the product indeed.
Vin.
Misalf:
If Windows has problems reading or writing to a drive for a specific amount of times, it switches from DMA to PIO and stays there (For this drive only; Check via Device Manager). Totally useless for CDs, happened a few times to me. I'm sure the same thing happens to HDDs, too.
Have you scandisk'ed the drive?
bmarkus:
It happenes to HDD's too, at least in XP/VISTA.
cast-fish:
Hello members,
thankyou for your replies.
It's exactly that (second to last reply)....windows decides it can't read OR write (how it likes ) to the hard drive and it goes into a stuck read loop (light on)
No guys, i can't compound this issue further, just not smart enough me,
but the error message blue screen of win32 says...."shadowing" and caching could be an issue
disable shadowing systems etc... (i use a shadow tool called "time freeze" free)
THe HDD also has the Check mark...to improve performance by caching up better....its an option
in win32 desktop options...
imagine the laptop has been on a very very long time. It reaches a point in the Shadow "snapshot" virtual session file it's creating. (via Time freeze) and all the blocks are used up...so to speak....it gets unhappy win32.....and a blue screen....complete shutdown. (windows detected an error)
who knows?....
but , you know, in my microcosm world....nothing eeks me more than (a what if) computer.... 0___0
i will have to make do.... Tinycore will certainly, (and has) worked fine on this laptop so its so so
thankyou for your replies. (you seem to be saying, win32 will just get unhappy with external peripherals HDD etc...it's intrinsicily the OS's demise)
forgot to say...the laptop is again, working perfectly right now, several hours (win32). Exactly as was........... a mirrored operation
Vin
cast-fish:
Yeah Thanks,
did do the usual things....scandisk etc and they show up faultless.
It's somekind of win32 to HDD issue......it's possible chip creep over many years
of sustained prolonged usage. 13 years
Vin
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version