Sounds good.
If you're starting from 0x3500 you might be able to
go from the end of cygwin1.dll upward. You could also
try ldd on BitDefender and see if ti tell you anything
about the dlls it loads and where they typically want to
go
Best -- EM
--
Problem reports: http://cygwin.c
Eliot Moss wrote:
Ok, I was wrong about ash (not) using cygwin1.dll.
Running ldd on rebase and peflags reveals that they use it
too, which pretty much says that they are cygwin apps.
Thanks. I was beginning to think I'd lost my mind...
However, it also shows that the preferred load address,
Is BitDefender on the BLODA list?
It may be wedging itself in, between cygwin and Windows,
redoing various Windows system calls -- but in a way that
defeats cygwin ...
Cheers -- EM
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentat
Ok, I was wrong about ash (not) using cygwin1.dll.
Running ldd on rebase and peflags reveals that they use it
too, which pretty much says that they are cygwin apps.
However, it also shows that the preferred load address, on
my system anyway, for cygwin1.dll is 0x6100. That
explains the start
On 12/5/2009 3:41 PM, Ed Gaines wrote:
As before, I searched for open cygwin dlls before and after running
rebase. I couldn't find any at all. I tried searching for these dlls
DURING the rebase, but unfortunately the rebase command completes
before the dll search completes. So even though the dl
Ed Gaines wrote:
Any reason I can't run the rebase and peflags commands from with
cmd.exe? Are
they "pure" windows executables, in other words?
I can't stand it.
In order to answer my own question cited above, I went back and ran a cmd.exe
window as administrator, and then tried to run reb
Eliot Moss wrote:
Any progress?
Well, I still don't have it working. But I did learn some rather startling
things about ash.exe and cygwin1.dll.
As always, this will seem overlong. But I've worked in the IT industry for
28 years, and I've learned that it's always the one datum you don't men
Eliot Moss wrote:
I should have asked you in my last email: should I have reloaded cygwin
prior to attempting to use the steps you prescribed in your response?
What does "reloaded" mean?
Reinstalled, in other words. Poor choice of words on my part...
Best procedure is:
- reboot system
-
Alas, I ran the commands as you recommend below, and there is yet no joy
here in Mudville.
I apologize in advance for the length of this -- I'm ignorant, so I don't
know which details I can omit -- but as you'll see when you arrive at the
end, the questions I'm asking are in fact quite few and qu
Thanks so much for your response! A few mop-up questions below. Hope you
don't mind.
Eliot Moss wrote:
Dear Ed --
I posted this a couple of days ago under another
thread.
My apologies. I thought I'd researched this carefully before posting.
Should have cast my net a bit wider, I guess.
H
Dear Ed -- I posted this a couple of days ago under another
thread. Here is the rebase procedure that works for me:
/bin/rebase -d -b 0x6100 -o 0x2 -v -T
> rebase.out
and
/bin/peflags -d0 -v -T > peflags-d.out
/bin/peflags -t0 -v -T > peflags-t.out
Note particularly the base
Okay, I'm hoping someone can help me understand what I SHOULD have done to
properly rebase cygwin 1.7 under Win 7 so it would make nice with BitDefender.
As has been pointed out here before, the combination of cygwin 1.7 and
BitDefender 2010 make for one unhappy little user. As a reminder, BitD
12 matches
Mail list logo
