From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Windows10 Creators Update
Date: Mon, 17 Jul 2017 17:41:00 -0000 [thread overview]
Message-ID: <87o9sj6jw5.fsf@Rainer.invalid> (raw)
In-Reply-To: <20170717083045.GB14583@calimero.vinschen.de> (Corinna Vinschen's message of "Mon, 17 Jul 2017 10:30:45 +0200")
Corinna Vinschen writes:
>> But, then again, what's the lowest address for the wow64 DLLs you
>> observed? And what about native 32 bit (no wow64 DLLs)?
I can't test native 32bit easily (have to request a test hardware at
work), all my systems at home are 64bit/WoW64 combos.
On WoW64, the lowest I've seen was this:
58E60000-58E61000 r--p 00000000 0000:0000 0 /cygdrive/c/Windows/System32/wow64.dll
This was after update and before reboot.
The lowest I've seen after clean reboots was somwhere around 0x6A000000,
IIRC.
>> We can't stabilize the address for the Windows DLLs, but we
>> can obviously adapt to it by changing rebase.
But that restricts and already strained resource. I _think_
(i.e. haven't checked) it'd be almost impossible to still get one of the
desktop environments running if we did that.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
prev parent reply other threads:[~2017-07-17 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 8:36 Achim Gratz
2017-07-16 9:10 ` Achim Gratz
2017-07-17 8:09 ` Corinna Vinschen
2017-07-17 8:31 ` Corinna Vinschen
2017-07-17 17:41 ` Achim Gratz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o9sj6jw5.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).