Linda Walsh wrote:
Eric Blake wrote:
According to Charli Li on 12/24/2006 1:39 PM:
Fishy enough, the new dlls had a filename extension of .dll.new
Which means Windows is scheduled to rename it automatically at the next
reboot, since it was in use at the time you ran setup.exe. Didn't
Eric Blake wrote:
According to Charli Li on 12/24/2006 1:39 PM:
Fishy enough, the new dlls had a filename extension of .dll.new
Which means Windows is scheduled to rename it automatically at the next
reboot, since it was in use at the time you ran setup.exe. Didn't you
read the messag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Charli Li on 12/24/2006 1:39 PM:
> Fishy enough, the new dlls had a filename extension of .dll.new
Which means Windows is scheduled to rename it automatically at the next
reboot, since it was in use at the time you ran setup.exe. Didn't
When using setup.exe to update packages that includes dlls (such as
cygwin), it installs the dlls, but have a different file extension.
When I tried to start up bash after updating packages with new dlls,
bash briefly spits out an error saying that it couldn't find
cygreadine6.dll. zsh and company
4 matches
Mail list logo
