> The MD tool reports in the memory diagnostic screen during the test being run. After reboot the MD tool places an icon in the
> Systray with the results. If it did find an error it will also attempt to indentify the memory module causing the error.
[quoted text clipped - 14 lines]
> >
> > Jeff
> Hi,
>
[quoted text clipped - 6 lines]
> an Error! To be blunt what use is that unless its going to tell me what the
> error is, or even what it thinks the error might be :-(
Would you want to receive an error message logging onto your computer
like this one from:
http://support.microsoft.com/kb/276304
Error Message: Your Password Must Be at Least 18770 Characters and
Cannot Repeat Any of Your Previous 30689 Passwords
View products that this article applies to.
Article ID : 276304
Last Review : January 29, 2007
Revision : 3.3
This article was previously published under Q276304
SYMPTOMS
If you log on to an MIT realm, press CTRL+ALT+DELETE, click Change
Password, type your existing MIT password, and then type a new, simple
password that does not pass the dictionary check in Kadmind, you may
receive the following error message:
Your password must be at least 18770 characters and cannot repeat any of
your previous 30689 passwords. Please type a different password. Type a
password that meets these requirements in both text boxes.
Note that the number of required characters changes from 17,145 to
18,770 with the installation of SP1.
<grin>
Donchik - 21 May 2008 09:58 GMT
Sweet, but still not much use ;-)
Problem is that the Diagnostics find an error, but tell me nothing about
what it thinks is wrong.
I need a way to interrogate the BIN file it creates with the error.
Cheers,
Donchik
> > Hi,
> >
[quoted text clipped - 31 lines]
>
> <grin>
propman - 21 May 2008 20:14 GMT
just off the top of my head (and only on my 3rd coffee of the morning)....
In the old days, if I didn't have a specific program for reading binary
(eg *.bin, *.exe etc) log files or wanted to search for a particular
string within a binary file, I would use a hex(adecimal) editor/viewer.
In fact I just saw a notification about about one I used to use all the
time but at the present time it's name totally eludes me (did I mention
that I am only on my 3rd cup of coffee this morning?).....I'm sure if
you do a quick Google Advanced search, something will turn up pretty quick.
> Problem is that the Diagnostics find an error, but tell me nothing about
> what it thinks is wrong.
>
> I need a way to interrogate the BIN file it creates with the error.
Donchik - 21 May 2008 21:54 GMT
Hi Propman,
Not quite what I'm after. Without knowing what Microsoft intend the bytes to
represent a binary viewer is not any use.
Still looking for the way to read and understand these data.
Cheers,
Donchik
> just off the top of my head (and only on my 3rd coffee of the morning)....
>
[quoted text clipped - 11 lines]
> >
> > I need a way to interrogate the BIN file it creates with the error.
propman - 21 May 2008 23:26 GMT
How do you know until you tried one.....used to that all the time as a
last resort. Sometimes the contents of such a viewing will surprise a
person or give a another clue one can use. Anyways, just a suggestion.
PS.....used to load binary files into text viewers too for a quick and
dirty look at them....hex editor/viewer was definitely more versatile
though.
> Hi Propman,
>
[quoted text clipped - 21 lines]
>>>
>>> I need a way to interrogate the BIN file it creates with the error.