Hi all,

I have been using my scanner on and off today to scan pics and such for a
family member. It was working perfectly until I suddenly got an error
message while loading a scan, that said...

Message box heading: Hposcv07

HPOSCV07: Caused an error in MSVCRT.DLL and will now close. And then when
you click OK, it shuts the scan process down and returns to the main menu.

In doing a search, I found a list located in various Program Files, one
being for the HP G55 all-in-one printer unit I have.

I rebooted and it would work for a time or two, then I'd get the message
again.

I have no idea what the MSVCRT.DLL is for, so I'm a bit puzzled as to what
has caused the error or where to troubleshoot the problem. I'd appreciate it
if someone could advise me as to what the .DLL file is in reference to, then
perhaps I can try to sort it out from there.

Best regards,
Jan :)

Re: Error in MSVCRT.DLL..? by Mart

Mart
Sat Dec 20 08:50:14 CST 2003

Jan, firstly confirm that any/all copies on your machine of msvcrt.dll are
the WinMe version - 6.1.8637.0 dated 8thJune 2000 1700Hrs. The file itself
is described in its properties as a 'MS Runtime Library' file and can be
regarded as 'part of the operating system' but is often 'modified' by OEM's
whose 'later' versions (which are *supposed* to be backward compatible) may
be (over)installed with other applications.

If you think that your copy(ies) of msvcrt.dll is/are the wrong version,
damaged or corrupted, then a 'fresh' compressed WinMe copy of msvcrt.dll can
be extracted and expanded (using msconfig.exe) from WIN_13.CAB to replace it
(them). N.B. You *may* have to do this in Safe Mode if the file is 'in use'.
In fact, only one copy of the file needs to be in the \windows\system
folder. All the others aren't necessary and can be renamed or deleted.

However, I would also suggest that you try 'removing' your HP G55 and
uninstalling its associated software. Reboot a couple of times and then try
re-installing it again.

BTW - If you trawl the KB for "msvcrt" under 'all MS products', you will see
just how many other things besides yours can be affected - many with similar
fixes <g>

HTH

Mart


"Jan Il" <abuse@localhost.com> wrote in message
news:j8REb.20400$J77.6214@fed1read07...
> Hi all,
>
> I have been using my scanner on and off today to scan pics and such for a
> family member. It was working perfectly until I suddenly got an error
> message while loading a scan, that said...
>
> Message box heading: Hposcv07
>
> HPOSCV07: Caused an error in MSVCRT.DLL and will now close. And then when
> you click OK, it shuts the scan process down and returns to the main menu.
>
> In doing a search, I found a list located in various Program Files, one
> being for the HP G55 all-in-one printer unit I have.
>
> I rebooted and it would work for a time or two, then I'd get the message
> again.
>
> I have no idea what the MSVCRT.DLL is for, so I'm a bit puzzled as to what
> has caused the error or where to troubleshoot the problem. I'd appreciate
it
> if someone could advise me as to what the .DLL file is in reference to,
then
> perhaps I can try to sort it out from there.
>
> Best regards,
> Jan :)
>
>
>



Re: Error in MSVCRT.DLL..? by Jan

Jan
Sat Dec 20 11:32:49 CST 2003

Hi Mart!

> Jan, firstly confirm that any/all copies on your machine of msvcrt.dll are
> the WinMe version - 6.1.8637.0 dated 8thJune 2000 1700Hrs. The file itself
> is described in its properties as a 'MS Runtime Library' file and can be
> regarded as 'part of the operating system' but is often 'modified' by
OEM's
> whose 'later' versions (which are *supposed* to be backward compatible)
may
> be (over)installed with other applications.
>
> If you think that your copy(ies) of msvcrt.dll is/are the wrong version,
> damaged or corrupted, then a 'fresh' compressed WinMe copy of msvcrt.dll
can
> be extracted and expanded (using msconfig.exe) from WIN_13.CAB to replace
it
> (them). N.B. You *may* have to do this in Safe Mode if the file is 'in
use'.
> In fact, only one copy of the file needs to be in the \windows\system
> folder. All the others aren't necessary and can be renamed or deleted.
>
> However, I would also suggest that you try 'removing' your HP G55 and
> uninstalling its associated software. Reboot a couple of times and then
try
> re-installing it again.

'k...I've checked the version of the one I have in the Windows/System and it
is the same as the one you have listed here, so, it must be somewhere
between the G55 and the computer. I'll try the uninstall/reinstall as you
suggested, and see if that helps. I've had problems with the two units
having a spat before, but, this was a new one. Guess there's not much fun
to be had by throwing a hissy fit I'd already know how to fix. <g>

I'll rename all others for now, and if there's no flare-ups anywhere else,
I'll just delete them.
>
> BTW - If you trawl the KB for "msvcrt" under 'all MS products', you will
see
> just how many other things besides yours can be affected - many with
similar
> fixes <g>

Heh! Seems this 'lil guy can be a big pain when it wants to be, in more
ways than one. <g>

Thank you so much for your time and help, and the detailed information. I
truly appreciate it.

Jan :)

>
> "Jan Il" <abuse@localhost.com> wrote in message
> news:j8REb.20400$J77.6214@fed1read07...
> > Hi all,
> >
> > I have been using my scanner on and off today to scan pics and such for
a
> > family member. It was working perfectly until I suddenly got an error
> > message while loading a scan, that said...
> >
> > Message box heading: Hposcv07
> >
> > HPOSCV07: Caused an error in MSVCRT.DLL and will now close. And then
when
> > you click OK, it shuts the scan process down and returns to the main
menu.
> >
> > In doing a search, I found a list located in various Program Files, one
> > being for the HP G55 all-in-one printer unit I have.
> >
> > I rebooted and it would work for a time or two, then I'd get the message
> > again.
> >
> > I have no idea what the MSVCRT.DLL is for, so I'm a bit puzzled as to
what
> > has caused the error or where to troubleshoot the problem. I'd
appreciate
> it
> > if someone could advise me as to what the .DLL file is in reference to,
> then
> > perhaps I can try to sort it out from there.
> >
> > Best regards,
> > Jan :)
> >
> >
> >
>
>



Re: Error in MSVCRT.DLL..? by Mart

Mart
Sat Dec 20 13:29:31 CST 2003

I *may* have got a little carried away, when I 'implied' that THIS file "is
often 'modified' by OEM's". On reflection, some 'shared' Runtime Library
files are modified in this way and on looking at the KB articles, perhaps
this is not one of the most common, but they certainly suggest that a clean
replacement can effect a cure. Draw your own conclusions <g>

However, replacing msvcrt.dll with a 'fresh' copy and re-installing your G55
will do no harm at all.

BTW - "> I'll rename all others for now" How many other copies of
msvcrt.dll did you find besides the one in the windows\system folder?

Good luck and I hope you are able to resolve the issue.

Mart

"Jan Il" <abuse@localhost.com> wrote in message
news:LC%Eb.20771$J77.1626@fed1read07...
> Hi Mart!
>
> > Jan, firstly confirm that any/all copies on your machine of msvcrt.dll
are
> > the WinMe version - 6.1.8637.0 dated 8thJune 2000 1700Hrs. The file
itself
> > is described in its properties as a 'MS Runtime Library' file and can be
> > regarded as 'part of the operating system' but is often 'modified' by
> OEM's
> > whose 'later' versions (which are *supposed* to be backward compatible)
> may
> > be (over)installed with other applications.
> >
> > If you think that your copy(ies) of msvcrt.dll is/are the wrong version,
> > damaged or corrupted, then a 'fresh' compressed WinMe copy of msvcrt.dll
> can
> > be extracted and expanded (using msconfig.exe) from WIN_13.CAB to
replace
> it
> > (them). N.B. You *may* have to do this in Safe Mode if the file is 'in
> use'.
> > In fact, only one copy of the file needs to be in the \windows\system
> > folder. All the others aren't necessary and can be renamed or deleted.
> >
> > However, I would also suggest that you try 'removing' your HP G55 and
> > uninstalling its associated software. Reboot a couple of times and then
> try
> > re-installing it again.
>
> 'k...I've checked the version of the one I have in the Windows/System and
it
> is the same as the one you have listed here, so, it must be somewhere
> between the G55 and the computer. I'll try the uninstall/reinstall as you
> suggested, and see if that helps. I've had problems with the two units
> having a spat before, but, this was a new one. Guess there's not much fun
> to be had by throwing a hissy fit I'd already know how to fix. <g>
>
> I'll rename all others for now, and if there's no flare-ups anywhere else,
> I'll just delete them.
> >
> > BTW - If you trawl the KB for "msvcrt" under 'all MS products', you will
> see
> > just how many other things besides yours can be affected - many with
> similar
> > fixes <g>
>
> Heh! Seems this 'lil guy can be a big pain when it wants to be, in more
> ways than one. <g>
>
> Thank you so much for your time and help, and the detailed information. I
> truly appreciate it.
>
> Jan :)
>
> >
> > "Jan Il" <abuse@localhost.com> wrote in message
> > news:j8REb.20400$J77.6214@fed1read07...
> > > Hi all,
> > >
> > > I have been using my scanner on and off today to scan pics and such
for
> a
> > > family member. It was working perfectly until I suddenly got an error
> > > message while loading a scan, that said...
> > >
> > > Message box heading: Hposcv07
> > >
> > > HPOSCV07: Caused an error in MSVCRT.DLL and will now close. And then
> when
> > > you click OK, it shuts the scan process down and returns to the main
> menu.
> > >
> > > In doing a search, I found a list located in various Program Files,
one
> > > being for the HP G55 all-in-one printer unit I have.
> > >
> > > I rebooted and it would work for a time or two, then I'd get the
message
> > > again.
> > >
> > > I have no idea what the MSVCRT.DLL is for, so I'm a bit puzzled as to
> what
> > > has caused the error or where to troubleshoot the problem. I'd
> appreciate
> > it
> > > if someone could advise me as to what the .DLL file is in reference
to,
> > then
> > > perhaps I can try to sort it out from there.
> > >
> > > Best regards,
> > > Jan :)
> > >
> > >
> > >
> >
> >
>
>



Re: Error in MSVCRT.DLL..? by Jan

Jan
Sat Dec 20 15:25:12 CST 2003

> I *may* have got a little carried away, when I 'implied' that THIS file
"is
> often 'modified' by OEM's". On reflection, some 'shared' Runtime Library
> files are modified in this way and on looking at the KB articles, perhaps
> this is not one of the most common, but they certainly suggest that a
clean
> replacement can effect a cure. Draw your own conclusions <g>

Oh...well...NOW you tell me! <bg>
>
> However, replacing msvcrt.dll with a 'fresh' copy and re-installing your
G55
> will do no harm at all.

No.. it won't hurt, and I sometimes wonder if the software for the G55 is
perhaps a bit.....woppled. I've had to do a reinstall a few times in the
past to resolve other types of printing issues. If this does not fully
resolve the problem then I'll replace the file from the Cabs as you
suggested and see how that goes.
>
> BTW - "> I'll rename all others for now" How many other copies of
> msvcrt.dll did you find besides the one in the windows\system folder?

10 others...that is why I didn't really know for sure which might be the
'one' causing the problem. <g>

> Good luck and I hope you are able to resolve the issue.

Thank you for the follow-up on the information, Mart. I really do appreciate
it.

Jan :)


> "Jan Il" <abuse@localhost.com> wrote in message
> news:LC%Eb.20771$J77.1626@fed1read07...
> > Hi Mart!
> >
> > > Jan, firstly confirm that any/all copies on your machine of msvcrt.dll
> are
> > > the WinMe version - 6.1.8637.0 dated 8thJune 2000 1700Hrs. The file
> itself
> > > is described in its properties as a 'MS Runtime Library' file and can
be
> > > regarded as 'part of the operating system' but is often 'modified' by
> > OEM's
> > > whose 'later' versions (which are *supposed* to be backward
compatible)
> > may
> > > be (over)installed with other applications.
> > >
> > > If you think that your copy(ies) of msvcrt.dll is/are the wrong
version,
> > > damaged or corrupted, then a 'fresh' compressed WinMe copy of
msvcrt.dll
> > can
> > > be extracted and expanded (using msconfig.exe) from WIN_13.CAB to
> replace
> > it
> > > (them). N.B. You *may* have to do this in Safe Mode if the file is 'in
> > use'.
> > > In fact, only one copy of the file needs to be in the \windows\system
> > > folder. All the others aren't necessary and can be renamed or deleted.
> > >
> > > However, I would also suggest that you try 'removing' your HP G55 and
> > > uninstalling its associated software. Reboot a couple of times and
then
> > try
> > > re-installing it again.
> >
> > 'k...I've checked the version of the one I have in the Windows/System
and
> it
> > is the same as the one you have listed here, so, it must be somewhere
> > between the G55 and the computer. I'll try the uninstall/reinstall as
you
> > suggested, and see if that helps. I've had problems with the two units
> > having a spat before, but, this was a new one. Guess there's not much
fun
> > to be had by throwing a hissy fit I'd already know how to fix. <g>
> >
> > I'll rename all others for now, and if there's no flare-ups anywhere
else,
> > I'll just delete them.
> > >
> > > BTW - If you trawl the KB for "msvcrt" under 'all MS products', you
will
> > see
> > > just how many other things besides yours can be affected - many with
> > similar
> > > fixes <g>
> >
> > Heh! Seems this 'lil guy can be a big pain when it wants to be, in more
> > ways than one. <g>
> >
> > Thank you so much for your time and help, and the detailed information.
I
> > truly appreciate it.
> >
> > Jan :)
> >
> > >
> > > "Jan Il" <abuse@localhost.com> wrote in message
> > > news:j8REb.20400$J77.6214@fed1read07...
> > > > Hi all,
> > > >
> > > > I have been using my scanner on and off today to scan pics and such
> for
> > a
> > > > family member. It was working perfectly until I suddenly got an
error
> > > > message while loading a scan, that said...
> > > >
> > > > Message box heading: Hposcv07
> > > >
> > > > HPOSCV07: Caused an error in MSVCRT.DLL and will now close. And
then
> > when
> > > > you click OK, it shuts the scan process down and returns to the main
> > menu.
> > > >
> > > > In doing a search, I found a list located in various Program Files,
> one
> > > > being for the HP G55 all-in-one printer unit I have.
> > > >
> > > > I rebooted and it would work for a time or two, then I'd get the
> message
> > > > again.
> > > >
> > > > I have no idea what the MSVCRT.DLL is for, so I'm a bit puzzled as
to
> > what
> > > > has caused the error or where to troubleshoot the problem. I'd
> > appreciate
> > > it
> > > > if someone could advise me as to what the .DLL file is in reference
> to,
> > > then
> > > > perhaps I can try to sort it out from there.
> > > >
> > > > Best regards,
> > > > Jan :)
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>


Re: Error in MSVCRT.DLL..? by Mart

Mart
Sat Dec 20 18:03:28 CST 2003

10 others!!! Geez.

Just try a quick check on each for its Properties to see if there is at
least one different version. I also begin to wonder if Windows gets
confused when it finds multiple copies of the 'same' .dll file? Not
absolutely sure how it searches for .dll's and therefore not certain if it
looks in the windows\system folder or the associated application folder
first.

Mart

<snipped>



Re: Error in MSVCRT.DLL..? by Jan

Jan
Sat Dec 20 18:56:43 CST 2003

Hi Mart -

> 10 others!!! Geez.

Yeah....now you see why I didn't know which one was the one causing the
problem? And..the error message did not say which one or where.
>
> Just try a quick check on each for its Properties to see if there is at
> least one different version. I also begin to wonder if Windows gets
> confused when it finds multiple copies of the 'same' .dll file? Not
> absolutely sure how it searches for .dll's and therefore not certain if it
> looks in the windows\system folder or the associated application folder
> first.

There are 4 of the 10 with different versions, 6.1.8924, 6.0.8337, 6.0.8397,
and 6.0.839.

One of the 10 a folder called msvcrt.dll.

The other 5 are all 6.1.8924, too.

It would seem as if each program is installing a version of it's own. Could
it be that the various program versions can't use but that particular file
version so it installs it along with? It seems kinda redundant to have so
many of the same file, but, so many different versions.

But, I don't understand these things you see. No...I don't understand these
things at all, so it's very confusing to me.

Jan :)




Re: Error in MSVCRT.DLL..? by Mart

Mart
Sat Dec 20 19:10:25 CST 2003

OK Jan, - It's back to plan A(i).

Make a note of and rename each in turn - starting with the 'older'
versions - e.g. msvcrt1.old etc., and try your printer after *each* change.

That should help you locate exactly which version AND its location when the
problem clears itself (Total confidence <bg>)

Mart

BTW - we hit the (bed)Time Zone barrier in the UK - will continue tomorrow


"Jan Il" <abuse@localhost.com> wrote in message
news:U66Fb.21074$J77.2208@fed1read07...
> Hi Mart -
>
> > 10 others!!! Geez.
>
> Yeah....now you see why I didn't know which one was the one causing the
> problem? And..the error message did not say which one or where.
> >
> > Just try a quick check on each for its Properties to see if there is at
> > least one different version. I also begin to wonder if Windows gets
> > confused when it finds multiple copies of the 'same' .dll file? Not
> > absolutely sure how it searches for .dll's and therefore not certain if
it
> > looks in the windows\system folder or the associated application folder
> > first.
>
> There are 4 of the 10 with different versions, 6.1.8924, 6.0.8337,
6.0.8397,
> and 6.0.839.
>
> One of the 10 a folder called msvcrt.dll.
>
> The other 5 are all 6.1.8924, too.
>
> It would seem as if each program is installing a version of it's own.
Could
> it be that the various program versions can't use but that particular file
> version so it installs it along with? It seems kinda redundant to have so
> many of the same file, but, so many different versions.
>
> But, I don't understand these things you see. No...I don't understand
these
> things at all, so it's very confusing to me.
>
> Jan :)
>
>
>



Re: Error in MSVCRT.DLL..? by Jan

Jan
Sat Dec 20 19:51:51 CST 2003

> OK Jan, - It's back to plan A(i).

'k...?..?
>
> Make a note of and rename each in turn - starting with the 'older'
> versions - e.g. msvcrt1.old etc., and try your printer after *each*
change.
>
> That should help you locate exactly which version AND its location when
the
> problem clears itself (Total confidence <bg>)

Ah..yes...total confidence is a good thing. And..I do feel better already.
<G>

So, by the process of elimination I should be able to root out the file the
error referenced, without, of course, actually doing so.

Very well...I'm off to chase the White Rabbit... ;-)

> Mart
>
> BTW - we hit the (bed)Time Zone barrier in the UK - will continue tomorrow

Got'cha.....have a good night.

Jan :)
>
>
> "Jan Il" <abuse@localhost.com> wrote in message
> news:U66Fb.21074$J77.2208@fed1read07...
> > Hi Mart -
> >
> > > 10 others!!! Geez.
> >
> > Yeah....now you see why I didn't know which one was the one causing the
> > problem? And..the error message did not say which one or where.
> > >
> > > Just try a quick check on each for its Properties to see if there is
at
> > > least one different version. I also begin to wonder if Windows gets
> > > confused when it finds multiple copies of the 'same' .dll file? Not
> > > absolutely sure how it searches for .dll's and therefore not certain
if
> it
> > > looks in the windows\system folder or the associated application
folder
> > > first.
> >
> > There are 4 of the 10 with different versions, 6.1.8924, 6.0.8337,
> 6.0.8397,
> > and 6.0.839.
> >
> > One of the 10 a folder called msvcrt.dll.
> >
> > The other 5 are all 6.1.8924, too.
> >
> > It would seem as if each program is installing a version of it's own.
> Could
> > it be that the various program versions can't use but that particular
file
> > version so it installs it along with? It seems kinda redundant to have
so
> > many of the same file, but, so many different versions.
> >
> > But, I don't understand these things you see. No...I don't understand
> these
> > things at all, so it's very confusing to me.
> >
> > Jan :)
> >
> >
> >
>
>


Re: Error in MSVCRT.DLL..? by Jan

Jan
Sun Dec 21 01:44:22 CST 2003

> OK Jan, - It's back to plan A(i).
>
> Make a note of and rename each in turn - starting with the 'older'
> versions - e.g. msvcrt1.old etc., and try your printer after *each*
change.

Hah!! Found him!

It is the one in the Windows\System, version 6.1.8637. It was the last one I
tried, as I did have to do that one in Safe Mode. I have a cordless mouse
which will not work in Safe Mode, so, I have to hook up my old cord mouse to
work in Safe Mode (kind of a complicated task from under the desk).

See...what happens is that the scanner will scan the photo, but, when it
tries to load the image in the scanner view window, that is when I get the
error message and then it shuts down the whole thing. Not while trying to
scan.

'k...so I'll wait now until I hear back from you.

Jan :)

<snip>




Re: Error in MSVCRT.DLL..? by Mart

Mart
Sun Dec 21 04:25:32 CST 2003

Good morning Jan,

> Hah!! Found him! - Found It! please <g>

Well at least it does seem to confirm that a Windows application looks for
an associated .dll file in the windows\system folder first before looking
elsewhere.

However, if I understand correctly, this copy (version 6.1.8637), is now the
ONLY actively available version on your system - all others being renamed.
And you are still getting the error report?

If so, that leaves two scenarios:-

(i) this copy is damaged/corrupted - replace with a fresh copy as outlined
in para 2 of my first reply.

(ii)Your HP G55 needs re-installing - see para 3 of my first reply.
(It would also be interesting to see if your HP software tries to install a
'new' copy of msvcrt.dll - and which version!!)

If that doesn't fix it, I have another plan (Plan B) <g> - concerning
mfc42.dll. But let's not go there just yet - long story!

Mart

"Jan Il" <abuse@localhost.com> wrote in message
news:65cFb.21311$J77.15615@fed1read07...
> > OK Jan, - It's back to plan A(i).
> >
> > Make a note of and rename each in turn - starting with the 'older'
> > versions - e.g. msvcrt1.old etc., and try your printer after *each*
> change.
>
> Hah!! Found him!
>
> It is the one in the Windows\System, version 6.1.8637. It was the last one
I
> tried, as I did have to do that one in Safe Mode. I have a cordless mouse
> which will not work in Safe Mode, so, I have to hook up my old cord mouse
to
> work in Safe Mode (kind of a complicated task from under the desk).
>
> See...what happens is that the scanner will scan the photo, but, when it
> tries to load the image in the scanner view window, that is when I get the
> error message and then it shuts down the whole thing. Not while trying to
> scan.
>
> 'k...so I'll wait now until I hear back from you.
>
> Jan :)
>
> <snip>
>
>
>



Re: Error in MSVCRT.DLL..? by Jan

Jan
Sun Dec 21 18:28:41 CST 2003

And very sunny San Diego afternoon to ya Mart,

> Good morning Jan,
>
> > Hah!! Found him! - Found It! please <g>

Ah, yes..you're right. I sometimes forget my P's & C's at times of delirium.
<bg>
>
> Well at least it does seem to confirm that a Windows application looks for
> an associated .dll file in the windows\system folder first before looking
> elsewhere.
>
> However, if I understand correctly, this copy (version 6.1.8637), is now
the
> ONLY actively available version on your system - all others being renamed.
> And you are still getting the error report?

Yes, all the other copies are still renamed. The 6.1.8637 is now the only
active one.
I have tested a few scans and thus far the error message has not come up
again.
>
> If so, that leaves two scenarios:-
>
> (i) this copy is damaged/corrupted - replace with a fresh copy as outlined
> in para 2 of my first reply.
>
> (ii)Your HP G55 needs re-installing - see para 3 of my first reply.
> (It would also be interesting to see if your HP software tries to install
a
> 'new' copy of msvcrt.dll - and which version!!)
>
> If that doesn't fix it, I have another plan (Plan B) <g> - concerning
> mfc42.dll. But let's not go there just yet - long story!

'k....since the problem occurs sporadically, after a varied number of
scans, I decided to do both (i) and (ii). As you stated before, there is
no harm in doing both.

The G55 software did not install a different file version to the
Windows\System folder. However, just for the sake of curiosity, I ran
another Search, and now there is one in the Program Files\Hewlett-Packard\HP
Officejet G Series\Oig\Is folder, which has a version date of 6.0.8397 too.
I know this file did not show up in this HP folder in the previous Searches,
as I printed out a screen shot of the Search results for reference.

I can't help wondering why it is creating this file there, when it seems to
be using the one in the Windows/System. I feel pretty sure of this, because
I renamed the one in the HP folder and tried the scan process again, and it
worked ok. Could there some sort of file donor running amuck somewhere...??
I mean..these files sure seem to be multiplying out of nowhere with
different birthdates!

While I've run several scans and the problem is not popping up at the
moment, I'm not sure why. And, since the error message does not define
which msvcrt.dll file is the culprit when if does, I'm still confused. I
guess I'll just have to do some more extensive testing and see if the error
comes up again. Then I guess your plan B might need to be considered.
BTW...what is file mfc42.dll? (Ahmm...I'm beginning to feel like Agent 99
with all this files lingo floating around...) <g>

Jan :)


Re: Error in MSVCRT.DLL..? by Mart

Mart
Sun Dec 21 19:33:38 CST 2003

Hi Jan,

A VERY dark and chilly 'longest' night here the NW of England <g>

I've snipped your reply in an attempt to keep this download short(ish).

My apologies for appending the following extract from the Win98 Resource
Kit - for all intents and purposes, it also applies to WinMe - but I hope it
gives some insight to the problem.

"Running Applications That Replace System Dynamic-Link Libraries

Some setup applications do not check the version of the system files they
are installing and overwrite the newer Windows 98 versions of those dynamic-
link libraries (DLL's).
Windows 98 restores its original DLLs after every setup application runs and
for the first three startups thereafter. If an application stops running or
behaves erratically after you install it, you may need to obtain an updated
version of the application that does not overwrite Windows 98 system files.

Versions of Windows earlier than Windows 95 allowed applications to
redistribute parts of the system with no ill effects. For example, an
application might overwrite a system file with no adverse consequences. In
Windows 98, multiple system files have been consolidated to expedite the
startup process. If an application tries to overwrite a system file that is
no longer used, Windows allows the application to copy the file, but does
not use it.

If your application must run with a replacement file, you can add that file
to the \Windows\System\Vmm32 directory (which is initially empty after you
set up Windows 98).

After you install an application, Windows 98 checks for files that are
commonly overwritten by setup applications. If any are found, a dialog box
appears, enabling you to restore the files from the hidden \Windows\Sysbckup
directory.

Windows 98 includes a new utility, System File Checker, that checks for
replaced system files."

Well, that's the theory - but doesn't always seem to stop the problem!!

It *might* even have been caused by 'randomly' picking-up one of the other
(older) versions located elsewhere - perhaps previously loaded by another
application requiring that 'same' .dll file, before being called for by the
scanner. (Remember, it may be shared)

Regarding mfc42.dll - this is another very common 'shared' file that is
regularly overwritten and one (along with msvcrt.dll) which I have had
problems with, (and fixed by using exactly the same course of action as
msvcrt.dll) especially with scanners!! in the past.

However, if your scanner is now pretty stable, it might be as well to leave
things alone (if it ain't broke, .... ) and see how it settles down. Only
continue with the 'fixes' on a 'need to' basis.

Sorry for the waffle, but hope it helps to explain things.

Mart



Re: Error in MSVCRT.DLL..? by Jan

Jan
Sun Dec 21 21:42:34 CST 2003

Hi Mart,

> A VERY dark and chilly 'longest' night here the NW of England <g>

I sympathize..it often gets down to 23 F or less here in Santee during the
winter...brrrr!!! ;-)
>
> I've snipped your reply in an attempt to keep this download short(ish).

What.....so now I'm long winded?
<g>

> My apologies for appending the following extract from the Win98 Resource
> Kit - for all intents and purposes, it also applies to WinMe - but I hope
it
> gives some insight to the problem.

No prob...I was on dialup for a long time before we got cable out here in
the
boonies, so I understand.
>
> "Running Applications That Replace System Dynamic-Link Libraries
>
> Some setup applications do not check the version of the system files they
> are installing and overwrite the newer Windows 98 versions of those
dynamic-
> link libraries (DLL's).
> Windows 98 restores its original DLLs after every setup application runs
and
> for the first three startups thereafter. If an application stops running
or
> behaves erratically after you install it, you may need to obtain an
updated
> version of the application that does not overwrite Windows 98 system
files.
>
> Versions of Windows earlier than Windows 95 allowed applications to
> redistribute parts of the system with no ill effects. For example, an
> application might overwrite a system file with no adverse consequences. In
> Windows 98, multiple system files have been consolidated to expedite the
> startup process. If an application tries to overwrite a system file that
is
> no longer used, Windows allows the application to copy the file, but does
> not use it.
>
> If your application must run with a replacement file, you can add that
file
> to the \Windows\System\Vmm32 directory (which is initially empty after you
> set up Windows 98).
>
> After you install an application, Windows 98 checks for files that are
> commonly overwritten by setup applications. If any are found, a dialog box
> appears, enabling you to restore the files from the hidden
\Windows\Sysbckup
> directory.
>
> Windows 98 includes a new utility, System File Checker, that checks for
> replaced system files."

> Well, that's the theory - but doesn't always seem to stop the problem!!
>
> It *might* even have been caused by 'randomly' picking-up one of the other
> (older) versions located elsewhere - perhaps previously loaded by another
> application requiring that 'same' .dll file, before being called for by
the
> scanner. (Remember, it may be shared)

Yes, now I see....and that does help explain where some of the additional
copies and various versions may be coming from. Whew!!
>
> Regarding mfc42.dll - this is another very common 'shared' file that is
> regularly overwritten and one (along with msvcrt.dll) which I have had
> problems with, (and fixed by using exactly the same course of action as
> msvcrt.dll) especially with scanners!! in the past.

Hmm...I'll make a note of that to keep in my reference library along
with the msvcrt.dll info.
>
> However, if your scanner is now pretty stable, it might be as well to
leave
> things alone (if it ain't broke, .... ) and see how it settles down. Only
> continue with the 'fixes' on a 'need to' basis.

Agreed. Since it is not throwing the error at this point, I'll wait and see
if what has been done thus far has actually resolved the problem. I have
some more scans to do as I can in the next few days for Christmas, so if
the problem is going to crop up again it should happen in the next few
days. Then I can yell back and see what else might need to be done.
>
> Sorry for the waffle, but hope it helps to explain things.

Thank you very much for all your time and detailed help. It has
cast some interesting light on how the parts of the various programs tend to
relate in some ways, at least for me as a novice. The more I learn, the more
it all makes sense. Ya know....that's kinda scary...8-o

Happy Holidays!
Jan :)