replacing directory with "last good" on Windows XP non-boot data harddisk

[jim]

On Wed, 09 May 2012 10:35:53 -0400, in

You can use Imgburn, which is free. Note - turn down your speakers,
so any sound effects the program creates, don't scare the crap out of you
The author of this program, has a sense of humor, but also did a
good job writing the engine.

http://en.wikipedia.org/wiki/Imgburn

Thanks.

jim

 

[jim]

On Wed, 9 May 2012 11:07:53 -0400, in microsoft.public.windowsxp.general,

I use the free ISO Recorder for XP:
http://isorecorder.alexfeinman.com/isorecorder.htm

Thanks.

jim

 

[jim]

On Wed, 09 May 2012 10:35:53 -0400, in

But I'd also likely have
replaced it, purely by looking at the SMART stats, and
smelling a rat.

Apparently all SMART tests are not equal --
http://dl.dropbox.com/u/14875021/smartST.jpg

But then, i am an optimist....

jim

 

[glee]

How do you take a snapshot of the bluescreen?

With your digital camera... turn off the flash.

 

[glee]

On Wed, 09 May 2012 10:35:53 -0400, in



Apparently all SMART tests are not equal --
http://dl.dropbox.com/u/14875021/smartST.jpg

All the SMART Test results will show is if any parameters are outside
the drive-maker's specs.... if those incremented issues add up to the
number that causes it to report a SMART Failure. The other apps you
used to read SMART data showed the Uncorrectable Errors, but they
apparently had not incremented to a high enough number to trigger a
"SMART failure"... which is why those apps give an earlier warning of
possible trouble than a yes/no SMART test such as Seatools for DOS. The
advantage of Seatools for DOS is the long surface test which will better
find problems with the drive, whether SMART passes or not.

 

[Char Jackson]

How do you take a snapshot of the bluescreen?

The short answer is, as Glen suggested, to use a digital camera
without flash. The better answer, I think, is to use Nirsoft's
BlueScreenView program. In that case, you can view the BSOD (plural if
you have more than one) at any time and in any order and as often as
you want.

It's free, get it here:
<http://www.nirsoft.net/utils/blue_screen_view.html>

 

[jim]

On Wed, 9 May 2012 15:59:08 -0400, in microsoft.public.windowsxp.general,

All the SMART Test results will show is if any parameters are outside
the drive-maker's specs.... if those incremented issues add up to the
number that causes it to report a SMART Failure. The other apps you
used to read SMART data showed the Uncorrectable Errors, but they
apparently had not incremented to a high enough number to trigger a
"SMART failure"... which is why those apps give an earlier warning of
possible trouble than a yes/no SMART test such as Seatools for DOS. The
advantage of Seatools for DOS is the long surface test which will better
find problems with the drive, whether SMART passes or not.

I could see the aggregate vs specific item differences in the SMART tests,
but i am really saying that they give different 'views'.

I am hoping that SeaTools' repair option works wonders. <laughter at the
situation>

jim

 

[BillW50]

How do you take a snapshot of the bluescreen?

BlueScreenView works better than a camera. Just follow the directions
and press F8 for the blue screen view.

Blue screen of death (STOP error) information in dump files.
http://www.nirsoft.net/utils/blue_screen_view.html

 

[BillW50]

I use that utility also, but it's not too informative for newbies. It
helps to use it in combination with WhoCrashed.
http://www.resplendence.com/whocrashed

I don't know, it seems pretty easy to me. I just used the factory
recover disc on this machine. It is part of my ongoing experiments with
no security updates. And everything is running fine except launching the
latest version of Process Explorer causes an instant reboot. No BSOD or
anything. At least there was a minidump file created.

And BlueScreenView showed that Avast caused the kernel to crash. It all
makes sense to me. Don't run Process Explorer and Avast real time
scanner won't cause the kernel to crash. Looks like Microsoft has a
hotfix for this problem for SP2 and it is already included in SP3. But
I'm going to keep experimenting and leave it as is for now. ;-)

 

[Paul]

How do you take a snapshot of the bluescreen?

When a system BSODs, it also has the option of generating some
kind of "dump". A minidump, is a fairly compact collection of
data, that doesn't attempt to snapshot the entire machine state.
Or, you can do a dump which captures all of virtual memory.
There is a control panel (maybe the same one as the "Automatic
Restart" option?), where you control the dump type.

Another annoying detail, is Dr.Watson, WERFault or equivalent (a tool which
can run when a crash happens), can also intercept a dump, and instead
of leaving the dump file on the computer, sends the dump details
to Microsoft. You can change a registry setting to stop this, such that
more dump information stays on your own computer.

http://al.howardknight.net/msgid.cgi?STYPE=msgid&A=0&MSGI=<[email protected]>

You feed dump files, to the tools like BlueScreenViewer, to have
them analysed and put in summary form. There are also tools
such as Microsoft Windbg, which allows developers to do a lot
more with the information. The fun never ends.

Paul

 

[glee]

I don't know, it seems pretty easy to me. I just used the factory
recover disc on this machine. It is part of my ongoing experiments
with no security updates. And everything is running fine except
launching the latest version of Process Explorer causes an instant
reboot. No BSOD or anything. At least there was a minidump file
created.

And BlueScreenView showed that Avast caused the kernel to crash. It
all makes sense to me. Don't run Process Explorer and Avast real time
scanner won't cause the kernel to crash. Looks like Microsoft has a
hotfix for this problem for SP2 and it is already included in SP3. But
I'm going to keep experimenting and leave it as is for now. ;-)

Nirsoft's utility is useful... it's easy for you and for me... but it
might not be for Jim, or for most less experienced computer users, which
is why I suggest WhoCrashed in addition.... plus it uses Microsoft
Windbg for its analysis in the background.

 

[glee]

The short answer is, as Glen suggested, to use a digital camera
without flash. The better answer, I think, is to use Nirsoft's
BlueScreenView program. In that case, you can view the BSOD (plural if
you have more than one) at any time and in any order and as often as
you want.

It's free, get it here:
<http://www.nirsoft.net/utils/blue_screen_view.html>

I agree.... Nirsoft's utility, or WhoCrashed.... which I mentioned
earlier in this thread... are the best tools for most users to read the
dump files. JAS asked "how do you take a snapshot of the bluescreen"...
only one way to do that: with a camera.

 

[JAS]

With your digital camera... turn off the flash.

I did say snapshot didn't I,ha. But now to buy a digital camera to just
take snapshots of BSOD. Thanks for the reply.

JAS

 

[JAS]

The short answer is, as Glen suggested, to use a digital camera
without flash. The better answer, I think, is to use Nirsoft's
BlueScreenView program. In that case, you can view the BSOD (plural if
you have more than one) at any time and in any order and as often as
you want.

It's free, get it here:
<http://www.nirsoft.net/utils/blue_screen_view.html>

I will look into that, Thanks.

JAS

 

[JAS]

Nirsoft's utility is useful... it's easy for you and for me... but it
might not be for Jim, or for most less experienced computer users, which
is why I suggest WhoCrashed in addition.... plus it uses Microsoft
Windbg for its analysis in the background.

Yes I am not very experienced and was confused by the BlueScreen View.
Thanks for the other suggestions

JAS

 

[jim]

FWIW, all of the reported individual SMART drive parameters (except the
power-on hours) on the only disk that showed problems are now back within
the normal range:

http://dl.dropbox.com/u/14875021/SMARTST250Good.jpg

disk fitness is now 97% where it was previously 0% on the same test
platform.

Thanks to all,

jim



On Mon, 07 May 2012 09:27:52 -0400, in

 

[jim]

On Wed, 9 May 2012 21:13:33 -0400, in microsoft.public.windowsxp.general,

l... it's easy for you and for me... but it
might not be for Jim, or for most less experienced computer users

I would be interested in what you call "experienced" and in what computer
areas.

I have difficulty with being referred to as "less experienced" when on
another physical computer platform i was known as "the mullah" and the
"the doctor" when it came to VM and VSE Software on Big Blue hardware --
albeit in another life many years ago. So I derisively laugh at what most
people today call "experienced" or "computer literate" in regards to
software.

Back then, I always had 24/7 hardware support so that has always been a
big hole in my PC endeavors and when it comes to PC hardware i am very
weak.

I am also very amused by what people consider "new" innovations. In 1989
or so I had a hardware techie sketch out for me a quad core CPU unit that
was currently in operation on some forgotten IBM mainframe model.

And yes, that was a lifetime ago. I started in an era when to "Boot"
meant to load a bootstrap deck of punch cards that were read by the
machine and that told it who and what it was. And yes, that has little to
do with the current state of computing -- but IMO, it is "experience".

 

[glee]

On Wed, 9 May 2012 21:13:33 -0400, in
microsoft.public.windowsxp.general,


I would be interested in what you call "experienced" and in what
computer
areas.

I have difficulty with being referred to as "less experienced" when on
another physical computer platform i was known as "the mullah" and the
"the doctor" when it came to VM and VSE Software on Big Blue
hardware --
albeit in another life many years ago. So I derisively laugh at what
most
people today call "experienced" or "computer literate" in regards to
software.

Back then, I always had 24/7 hardware support so that has always been
a
big hole in my PC endeavors and when it comes to PC hardware i am very
weak.

I am also very amused by what people consider "new" innovations. In
1989
or so I had a hardware techie sketch out for me a quad core CPU unit
that
was currently in operation on some forgotten IBM mainframe model.

And yes, that was a lifetime ago. I started in an era when to "Boot"
meant to load a bootstrap deck of punch cards that were read by the
machine and that told it who and what it was. And yes, that has
little to
do with the current state of computing -- but IMO, it is "experience".

Sorry you misunderstood so, and took offense, where I wasn't referring
to you.

Re-read what I wrote: for Jim, OR for most less experienced computer
users
I didn't say anything about you being less experienced, I stated you,
"OR". On newsgroups and forums, until someone indicates otherwise, one
cannot assume any level of experience or of comfort doing certain tasks,
so I find it best to mention tools for both newbies and for "power
users".

As far as your previous experience, yes, it is extensive, but also on
another platform "a lifetime ago". That doesn't mean you are
comfortable with Windows behind the surface. I know a lot of people who
worked with computers extensively back in the 80's and even earlier....
some are just about lost in Windows. So, my use of the word involves
experience with Windows, not with punch cards or Cobol or Fortran.

 

[BillW50]

I agree.... Nirsoft's utility, or WhoCrashed.... which I mentioned
earlier in this thread... are the best tools for most users to read the
dump files. JAS asked "how do you take a snapshot of the bluescreen"...
only one way to do that: with a camera.

I disagree, BlueScreenView will show you nearly the exact same screen at
any time you want it too. Now you can see it as many times as you want
too. And use your favorite screen capture utility or whatever to take a
far better screen shot than a digital camera can do.

 

[jim]

On Thu, 10 May 2012 08:54:04 -0400, in

Sorry you misunderstood so, and took offense, where I wasn't referring
to you.

Re-read what I wrote: for Jim, OR for most less experienced computer
users
I didn't say anything about you being less experienced, I stated you,
"OR". On newsgroups and forums, until someone indicates otherwise, one
cannot assume any level of experience or of comfort doing certain tasks,
so I find it best to mention tools for both newbies and for "power
users".

As far as your previous experience, yes, it is extensive, but also on
another platform "a lifetime ago". That doesn't mean you are
comfortable with Windows behind the surface. I know a lot of people who
worked with computers extensively back in the 80's and even earlier....
some are just about lost in Windows. So, my use of the word involves
experience with Windows, not with punch cards or Cobol or Fortran..

Thanks for the nice and reasonable response.

The use of Fortran was before my day as a Systems Programmer though we did
have some Fortran called routines.

I never dealt with PC's at that time any more than I had to -- Accounting
expected me to know all about their PC's, but I decried knowledge of the
'fancy toasters'. I did not want to sully my other area and sure enough,
after I left and bought a 386, I found myself entering command level VM
and CMS commands into it. What i did find, was that a file was still a
file -- just in ASCII instead of EBCDIC and a program was still a program
-- and a HEX doubleword was still a HEX doubleword. What were MACLIBS to
me were now called DLLs -- and that is another thing that people thought
was a PC "innovation".

My apologies that i misunderstood you, I suppose that is not unlike the
other day when i started a sentence with "If it is a smooth progression"
and apparently that meaning was lost. (There are so many variables that i
long ago began starting sentences about observed computer states with "if"
or "apparently".)

Have a good day -- and i am sure you know more about XP than I.

jim