Subject | Re: [firebird-support] msvcrt.dll issue |
---|---|
Author | Helen Borrie |
Post date | 2005-11-09T22:47:51Z |
At 12:35 PM 9/11/2005 -0700, you wrote:
directory, so the first thing to try would have been to 1) rename
msvcrt.dll in your c:\winnt\system32 directory and 2) copy the newer one
from $firebird\bin into system32.
You should do this on a reboot in safe mode since, once the dll has been
loaded by an application, it won't be available to rename or overwrite.
Windoze is *meant* to be able to find these system dlls in the application
path if they are there but it doesn't work. A number of approaches were
tried in the 1.5 betas, in accord with MS documentation and nothing worked
reliably.
If you find that the newer dll won't load, or causes problems, the best bet
will be to search the msdn site for the latest NT4 SP6 update pack that
contains this library and also msvcpp60.dll (which also needs to be in the
system32 directory. That said, I'm pretty certain that, during the early
betas, when I still had NT4SP6 on my Windows box, copying over the two dlls
worked fine.
./heLen
>What version and where do you put it of msvcrt.dll is needed forThe Firebird installation places v. 6.0.8797.0 in the $firebird\bin
>firebird 1.5 to run on nt4 sp 6?
>
>__lc_collate_cp is the entry point they cant find.
>
>they had 5.00.7303 version but we put a 6.something version in the bin
>folder of firebird with no affect.
directory, so the first thing to try would have been to 1) rename
msvcrt.dll in your c:\winnt\system32 directory and 2) copy the newer one
from $firebird\bin into system32.
You should do this on a reboot in safe mode since, once the dll has been
loaded by an application, it won't be available to rename or overwrite.
Windoze is *meant* to be able to find these system dlls in the application
path if they are there but it doesn't work. A number of approaches were
tried in the 1.5 betas, in accord with MS documentation and nothing worked
reliably.
If you find that the newer dll won't load, or causes problems, the best bet
will be to search the msdn site for the latest NT4 SP6 update pack that
contains this library and also msvcpp60.dll (which also needs to be in the
system32 directory. That said, I'm pretty certain that, during the early
betas, when I still had NT4SP6 on my Windows box, copying over the two dlls
worked fine.
./heLen