Search Results

Search results 1-6 of 6.

  • there should b a reason for this happening to him, and the worst-case scenario would b a hard disk failure.
  • here he goes again, meddles. don't listen to blaster, it can b a hd failure, ofc, just b sure to tell him to check what did cause it... and to hope it's not hardware related.
  • there r a few workarounds for this problem... the simplest one is switching ur harddisk controller to standard, or legacy mode, or whatever term they did use, in bios. after that u will b able to access ur disk from windows cd, and do the recovery. u should return bios to the previous state after recovery, and try to boot from disk drive. if u can, since we speak the same language, maybe u could contact me directly, and i'll help u... if u have any means for that. anyway, b sure to check ur dis…
  • drivers at floppy disk r not for hdd, but for the controller driving it... but anyway, that solution doesn't always work, especially in the case of intel's mobo chipsets, cause some driver versions r a bit buggy. if u choose floppy disk variant of the solution, u don't have to do anything in bios.
  • gonzo: ja sam vec pomogao argosu sa slicnim problemom, a inace radim vec vise od decenije kao tehnicka podrska, pa su mi ovakvi problemi poznati vrlo dobro. dovoljno je samo da odes u bios, i iskljucis napredni, native mod, ili kako vec da pise (zavisi od biosa), pristup disku. to ce ti omoguciti da bootujes sa win cda i vidis disk. onda uradis recovery iz win cda i vratis bios nazad. ubcd mozda takodje nece imati drivere za tvoj controller, pa ti je ovo sigurnija varijanta. iskreno, bilo bi na…
  • nlite is a waste of time and energy... but a solution too.