New
#21
Were these a sort of 'general' log files that said something like:
(which only indicates that chkdsk was run and had an error)Chkdsk shows errors..
Error return from Chkdsk ox80000001a Code 01
Or, was is a 'Chkdsk.log', produced by Chkdsk, something like:
A kind of 'gibberish', so to speak...Check sum error, sector 0x3a8b
CRC error, repaired byte old:ae new:af
Can't read cyl 0x2cf hd 0xe sec 0xaf
The file system data structures appear good...I can see files just by going to a C:\> through the repair function of the install disk or with F8 booting to the 'select OS' page.
Don't know much about NTFS though. 'Technet' should help there.
OTOH, the 'chkdsk /r' was "Repairing" your NTFS HDD, when something bought the farm...
F8 booting to 'select OS' - do you actually see that (bootmgr) screen?
There should be a 'Cmd prompt' for that, from a normal working install), but sounds like you're still stuck with the .wim winimage, packed version, who doesn't know anything about the one that's supposed to run...There is an update to the ATI driver. Can't install from C:\> on the box.
Where's he gonna 'install' it to ?
Is the ATI a zip file, .exe, or something else?
If its zip, see what files are inside.
Should be a .sys, .inf, .dll and maybe .exe plus more...
If its .exe, then winrar or 7zip or others should give more info about it.
Don't execute (launch) the .exe, just let those other tools 'look' at it.
Post the list of 'unzipped' filenames, and look in \win\sys32\drivers\ for the same .sys name.
Also \win\inf\ for the same .inf name.
Then \win\sys32\ for the .dll name, maybe .exe and others also.
By same name, I mean not nec exactly the same (tho they might be), but off by a number or letter or two.
------------------------------------------
Do you have 'tinyhex' as a plugin, in your BartPE ? Or on the Hirens?
Tinyhex was not distrib as part of default PEBuilder, but was listed somewhere on a referenced "favorites', or 'suggested', or 'popular' type of list,
relative to Bart's home page, somehow.
Later,
Chuck