Empi said:Wow...
Sorry.
I don't think my question is so unclear to deserve such a response.
Someone was not in the mood.
Here is a quote from 13 messages ago:
***************************************************
Hi.
I've just got a word from one of my companies site,
indicating that my software, running on an Hp iPaq,
has reported a "checksum error".
My software report this error when it compares (on startup) the exe's md5
signature
against a pre stored value (stored in an xml file).
This is done in order to detect changes made to the software and eliminate
imprpoer use of it.
I got 2 copies of the exe.
One was copied immidatly after the error occured,
and another one that was copied about 15 minutes later.
I was amazed to see that there is a memory page of 80 bytes that is not
the
same.
On the "damaged" copy, it has the values e4 42 e4 42.... all over the 80
bytes.
The software doesn't access the exe on runtime.
The questions are:
1) Does it imply memroy defect on the specific device?
1.1) If so - how often I should expect getting it? is it related to the
device's age and usage?
2) Any suggestion on testing the flash memory?
I intend to get 10 different copies of the app's directory in order to
check for diff's.
Thanks !
Empi
********************************************************
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:[email protected]...Could *WHAT* be because of a flash memory problem? We aren't somehow
following who you are or what question you might have asked before. If
you didn't get a useful answer to your question, reply to it yourself in
that thread; don't start a new thread, particularly one with NO USEFUL
INFORMATION in it.
Paul T.
Chris Tacke said:So we're supposed to go searching through all old messages to see what
you're talking about?
Empi said:Wow...
Sorry.
I don't think my question is so unclear to deserve such a response.
Someone was not in the mood.
Here is a quote from 13 messages ago:
***************************************************
Hi.
I've just got a word from one of my companies site,
indicating that my software, running on an Hp iPaq,
has reported a "checksum error".
My software report this error when it compares (on startup) the exe's md5
signature
against a pre stored value (stored in an xml file).
This is done in order to detect changes made to the software and
eliminate
imprpoer use of it.
I got 2 copies of the exe.
One was copied immidatly after the error occured,
and another one that was copied about 15 minutes later.
I was amazed to see that there is a memory page of 80 bytes that is not
the
same.
On the "damaged" copy, it has the values e4 42 e4 42.... all over the 80
bytes.
The software doesn't access the exe on runtime.
The questions are:
1) Does it imply memroy defect on the specific device?
1.1) If so - how often I should expect getting it? is it related to the
device's age and usage?
2) Any suggestion on testing the flash memory?
I intend to get 10 different copies of the app's directory in order to
check for diff's.
Thanks !
Empi
********************************************************
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
DOT com> wrote in message news:[email protected]...Could *WHAT* be because of a flash memory problem? We aren't somehow
following who you are or what question you might have asked before. If
you didn't get a useful answer to your question, reply to it yourself in
that thread; don't start a new thread, particularly one with NO USEFUL
INFORMATION in it.
Paul T.
Hi.
I did not get an answer regarding the flash memory.
I'll try to rephrase.
Could it be that because of flash memory problem, an iPaq will load a
damaged exe to the memory with no system fatal error?
Thanks.
Empi
Empi said:No you are not.
I think, and may be I'm wrong, that
*****************************************************
Could it be that because of flash memory problem, an iPaq will load a
damaged exe to the memory with no system fatal error?
*****************************************************
is a simple yes no question.
Chris Tacke said:So we're supposed to go searching through all old messages to see what
you're talking about?
Empi said:Wow...
Sorry.
I don't think my question is so unclear to deserve such a response.
Someone was not in the mood.
Here is a quote from 13 messages ago:
***************************************************
Hi.
I've just got a word from one of my companies site,
indicating that my software, running on an Hp iPaq,
has reported a "checksum error".
My software report this error when it compares (on startup) the exe's
md5
signature
against a pre stored value (stored in an xml file).
This is done in order to detect changes made to the software and
eliminate
imprpoer use of it.
I got 2 copies of the exe.
One was copied immidatly after the error occured,
and another one that was copied about 15 minutes later.
I was amazed to see that there is a memory page of 80 bytes that is not
the
same.
On the "damaged" copy, it has the values e4 42 e4 42.... all over the 80
bytes.
The software doesn't access the exe on runtime.
The questions are:
1) Does it imply memroy defect on the specific device?
1.1) If so - how often I should expect getting it? is it related to the
device's age and usage?
2) Any suggestion on testing the flash memory?
I intend to get 10 different copies of the app's directory in order
to
check for diff's.
Thanks !
Empi
********************************************************
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
DOT com> wrote in message Could *WHAT* be because of a flash memory problem? We aren't somehow
following who you are or what question you might have asked before. If
you didn't get a useful answer to your question, reply to it yourself
in that thread; don't start a new thread, particularly one with NO
USEFUL INFORMATION in it.
Paul T.
Hi.
I did not get an answer regarding the flash memory.
I'll try to rephrase.
Could it be that because of flash memory problem, an iPaq will load a
damaged exe to the memory with no system fatal error?
Thanks.
Empi
That's not a useful question. Here's my answer, "sure". Helpful? It's a
waste of both of our time, I would say, but there you are.
Paul T.
Empi said:No you are not.
I think, and may be I'm wrong, that
*****************************************************
Could it be that because of flash memory problem, an iPaq will load a
damaged exe to the memory with no system fatal error?
*****************************************************
is a simple yes no question.
Chris Tacke said:So we're supposed to go searching through all old messages to see what
you're talking about?
Wow...
Sorry.
I don't think my question is so unclear to deserve such a response.
Someone was not in the mood.
Here is a quote from 13 messages ago:
***************************************************
Hi.
I've just got a word from one of my companies site,
indicating that my software, running on an Hp iPaq,
has reported a "checksum error".
My software report this error when it compares (on startup) the exe's
md5
signature
against a pre stored value (stored in an xml file).
This is done in order to detect changes made to the software and
eliminate
imprpoer use of it.
I got 2 copies of the exe.
One was copied immidatly after the error occured,
and another one that was copied about 15 minutes later.
I was amazed to see that there is a memory page of 80 bytes that is not
the
same.
On the "damaged" copy, it has the values e4 42 e4 42.... all over the
80
bytes.
The software doesn't access the exe on runtime.
The questions are:
1) Does it imply memroy defect on the specific device?
1.1) If so - how often I should expect getting it? is it related to the
device's age and usage?
2) Any suggestion on testing the flash memory?
I intend to get 10 different copies of the app's directory in order
to
check for diff's.
Thanks !
Empi
********************************************************
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
DOT com> wrote in message Could *WHAT* be because of a flash memory problem? We aren't somehow
following who you are or what question you might have asked before.
If you didn't get a useful answer to your question, reply to it
yourself in that thread; don't start a new thread, particularly one
with NO USEFUL INFORMATION in it.
Paul T.
Hi.
I did not get an answer regarding the flash memory.
I'll try to rephrase.
Could it be that because of flash memory problem, an iPaq will load a
damaged exe to the memory with no system fatal error?
Thanks.
Empi
Empi said:Yes it does help.
I know that when wroking with hard disks, one gets a crc error when trying
to load damaged data.
I don't know if it is the case with flash memory.
Since I did put lots of info on my first version and got no answer, I
tried to rephrase it and
ask a shorter questions (ok. I admit. too short).
I don't think it is a reason to SHOUT on me.
But ... I know we all bring out mood with us anywhere, and reading the
questions here (including my questions)
know how much patient you guys need.
Thanks anyway.
Empi.
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:[email protected]...That's not a useful question. Here's my answer, "sure". Helpful? It's
a waste of both of our time, I would say, but there you are.
Paul T.
Empi said:No you are not.
I think, and may be I'm wrong, that
*****************************************************
Could it be that because of flash memory problem, an iPaq will load a
damaged exe to the memory with no system fatal error?
*****************************************************
is a simple yes no question.
"Chris Tacke, MVP" <ctacke.at.opennetcf.dot.com> wrote in message
So we're supposed to go searching through all old messages to see what
you're talking about?
Wow...
Sorry.
I don't think my question is so unclear to deserve such a response.
Someone was not in the mood.
Here is a quote from 13 messages ago:
***************************************************
Hi.
I've just got a word from one of my companies site,
indicating that my software, running on an Hp iPaq,
has reported a "checksum error".
My software report this error when it compares (on startup) the exe's
md5
signature
against a pre stored value (stored in an xml file).
This is done in order to detect changes made to the software and
eliminate
imprpoer use of it.
I got 2 copies of the exe.
One was copied immidatly after the error occured,
and another one that was copied about 15 minutes later.
I was amazed to see that there is a memory page of 80 bytes that is
not the
same.
On the "damaged" copy, it has the values e4 42 e4 42.... all over the
80
bytes.
The software doesn't access the exe on runtime.
The questions are:
1) Does it imply memroy defect on the specific device?
1.1) If so - how often I should expect getting it? is it related to
the
device's age and usage?
2) Any suggestion on testing the flash memory?
I intend to get 10 different copies of the app's directory in order
to
check for diff's.
Thanks !
Empi
********************************************************
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
DOT com> wrote in message
Could *WHAT* be because of a flash memory problem? We aren't somehow
following who you are or what question you might have asked before.
If you didn't get a useful answer to your question, reply to it
yourself in that thread; don't start a new thread, particularly one
with NO USEFUL INFORMATION in it.
Paul T.
Hi.
I did not get an answer regarding the flash memory.
I'll try to rephrase.
Could it be that because of flash memory problem, an iPaq will load
a damaged exe to the memory with no system fatal error?
Thanks.
Empi
Loading an EXE is not the same as loading the part of the file that
happens to be damaged. Let's say that you have a big bitmap and that part
of the disk happens to be damaged. If the EXE containing that bitmap in
its resource path never loads that resource, so what if it's damaged?
Even if some of the code in the EXE is in damaged sectors, that doesn't
mean that things will crash. The error might not be detected by the disk
driver and the specific code that happens to be bad might not be executed,
so, again, the system doesn't 'care' that it's bad.
Your form for trying to strobe us to answer the actual question is wrong.
You should reply to yourself in the existing thread, so that we have the
question details to begin with.
Paul T.
Empi said:Yes it does help.
I know that when wroking with hard disks, one gets a crc error when
trying to load damaged data.
I don't know if it is the case with flash memory.
Since I did put lots of info on my first version and got no answer, I
tried to rephrase it and
ask a shorter questions (ok. I admit. too short).
I don't think it is a reason to SHOUT on me.
But ... I know we all bring out mood with us anywhere, and reading the
questions here (including my questions)
know how much patient you guys need.
Thanks anyway.
Empi.
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
DOT com> wrote in message news:[email protected]...That's not a useful question. Here's my answer, "sure". Helpful? It's
a waste of both of our time, I would say, but there you are.
Paul T.
No you are not.
I think, and may be I'm wrong, that
*****************************************************
Could it be that because of flash memory problem, an iPaq will load a
damaged exe to the memory with no system fatal error?
*****************************************************
is a simple yes no question.
"Chris Tacke, MVP" <ctacke.at.opennetcf.dot.com> wrote in message
So we're supposed to go searching through all old messages to see what
you're talking about?
Wow...
Sorry.
I don't think my question is so unclear to deserve such a response.
Someone was not in the mood.
Here is a quote from 13 messages ago:
***************************************************
Hi.
I've just got a word from one of my companies site,
indicating that my software, running on an Hp iPaq,
has reported a "checksum error".
My software report this error when it compares (on startup) the exe's
md5
signature
against a pre stored value (stored in an xml file).
This is done in order to detect changes made to the software and
eliminate
imprpoer use of it.
I got 2 copies of the exe.
One was copied immidatly after the error occured,
and another one that was copied about 15 minutes later.
I was amazed to see that there is a memory page of 80 bytes that is
not the
same.
On the "damaged" copy, it has the values e4 42 e4 42.... all over the
80
bytes.
The software doesn't access the exe on runtime.
The questions are:
1) Does it imply memroy defect on the specific device?
1.1) If so - how often I should expect getting it? is it related to
the
device's age and usage?
2) Any suggestion on testing the flash memory?
I intend to get 10 different copies of the app's directory in
order to
check for diff's.
Thanks !
Empi
********************************************************
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no
spam DOT com> wrote in message
Could *WHAT* be because of a flash memory problem? We aren't
somehow following who you are or what question you might have asked
before. If you didn't get a useful answer to your question, reply to
it yourself in that thread; don't start a new thread, particularly
one with NO USEFUL INFORMATION in it.
Paul T.
Hi.
I did not get an answer regarding the flash memory.
I'll try to rephrase.
Could it be that because of flash memory problem, an iPaq will load
a damaged exe to the memory with no system fatal error?
Thanks.
Empi