They both are chromium based but only Edge has special driver for x64. Why?
Chrome
Edge
Maintained by different orgs. Chrome -> Google, Edge -> Microsoft
64-bit version driver availability depends on browser implementation, priorities of the orgs etc. Microsoft took initiative to support 64-bit version of Edge browser, while Google prioritizes supporting 32-bit version because it is still widely used.
Chrome driver developers may also be considering other factors such as compatibility with other operating systems, the need to support multiple versions of the browser, and the availability of engineering resources.
But, it's highly likely a 64-bit version of Chrome driver will be available in the future.
Related
In my manifest xml file I have this setting, does it mean that only 64bit Windows10 installations do accept my package? My app is native 32bit, which setting is recommended to this field to make it work with both 32 and 64 bit os?
ProcessorArchitecture="x64"
I think if you set ProcessorArchitecture="x64" in your manifest xml file, the package just only was installed on the x64 Windows 10. But you can set
ProcessorArchitecture="x86" in the manifest, because this x86 package can all work fine on x86 and x64 Windows 10.
This answer based on VS C++, but the context is basically the same for manifests. Surprised to see that W10 X86 only installations actually exist, but they do, (or did), because, as the free W10 upgrade did not provide an option to change architectures, only a clean install would.
However, from an old Tom's Hardware post:
All processors since the Opteron in 2003 and the intel Pentium 4 Prescott ( the latter editions ) has 64bit instruction set and will all run 64bit windows.
Thus as long a MSFT continues to support 32 bit architecture, X86 is the safer option, although X64 would probably still work.
processorArchitecture='*'
covers all bases as well.
Microsoft's documentation says to use processorArchitecture="ia64" for Windows 64-bit builds; however, they do not follow their own advice. Microsoft uses "amd64" for 64-bit builds of WordPad.exe and iexplore.exe (Internet Explorer 64-bit) according to the embedded app manifest of these EXEs on my Windows 10 computer.
As I understand, as Windows XP support was officially dropped, the newest versions of SSL certificates used in certain websites cannot be accessed by Chrome and IE on WinXP due to incompatibility. However, Firefox apparently still does support Windows XP and can access those websites freely.
I don't quite understand how the SSL certificates compatibility works, how is it possible that on Chrome and IE it requires you to switch to a new OS altogether but that's not needed when just using a different browser? Why can't a simple community developer just create a "patch" for Chrome and IE if Firefox can support them? What's the connection between the browser and the OS? Where do I draw the line?
OK, so looking at the example of mpql.net, we start with the SSL Labs analysis.
The problem appears to be that the server only supports elliptic curve cryptography (the various TLS_ECDHE_xxx suites) and, according to the MSDN articles Secure Sockets Layer Protocol and TLS Cipher Suites, Windows XP doesn't include any of the elliptic curve protocols. This is not related to the certificates per se, but to the way the web server is configured.
Firefox still works because it uses its own cryptographic library rather than using the SSL support built into Windows. Of course, if you were using a version of Firefox as old as Windows XP is, it probably wouldn't work either. :-)
Solution for this problem in XP is installing KB3055973-v3 that adds support for TLS 128-bit & 256-bit Advanced Encryption Standard (AES) cipher suites.
Google for this solution and beware it is natively for English OS version, otherwise you need to modify the installation files.
Note that I installed "Windows Embedded POSReady 2009" before.
certain websites cannot be accessed by Chrome and IE on WinXP due to incompatibility. However, Firefox apparently still does support Windows XP and can access those websites freely.
Chrome and IE use the CA store of windows while Firefox uses it's own independent store.
Why can't a simple community developer just create a "patch" for Chrome and IE if Firefox can support them?
It might be that some developer can do it, but why should somebody invest its time to support an OS which is dead and insecure just to support browsers which are no longer supported (Chrome will drop support end of 2015). If you feel this needs to be done anyway just do it. Otherwise, drop XP or at least use Firefox with it.
Although I cant say im 100% correct I believe ssl has everything to do with the browser and not much to do with the actual operating system. So I ran into an issue where the very opposite from what you are asking. A client was on a windows 7 machine and needed to access time warner business email through chrome but couldn't because of a SSL issue. The problem was that Chrome dropped support for the older version of SSL and so her options where use IE or Firefox or downgrade and hope chrome doesn't force its self to update. Microsoft is wanting users to upgrade so of course they are not going to keep IE up to date and google isn't going to support an outdated operating system. Firefox is open source so it makes sense that people would keep the browser compatible with as many devices as possible. Hope this helps.
You Need Various Browsers
So, you need to test
your web stuff
with various browsers.
Some of these browsers
may be unavailable
on the OS
in which you develop.
Microsoft browsers (Internet Explorer)
are only available for Windows.
Further,
each Windows installation
can have only a single
Microsoft browser.
Also, Safari is only available in OS X.
The Obvious Solution: Virtualization
The obvious solution is
hardware virtualization.
The idea is to host
virtual machines
in your development system,
in which you'll be free to install
the operating system
and browser combination
that you require for testing.
So, How?
How do I do that?
Safari: Only on OS X
The latest version of
Safari
is available only for
recent versions
of OS X.
running of OS X in virtualization
is supported only on
Apple hardware.
For further details, read:
VirtualBox's documentation on OS X guests
VMware's "Virtualizing Apple Mac OS X (1000131)".
Manually
You can
create VM's
and install
the OS/browser
combinations
that you require.
I recommend VirtualBox.
Advantages of Manual
You do not have to
discard
the changes in the VM
after each use session.
And, unlike with ievms,
you do not have to
reinstall from scratch
every time the license expires.
Apart from saving time,
this means that
you can configure/customize
the operating system and browser
and install additional software
according to your requirements and preferences.
The Disadvantage
Valid licenses for the
software involved
may be required by law.
Tips
The same version of browser
may behave differently
on different versions of Windows.
Provide enough memory to your VM's.
I recommend at least 1GB, per VM.
To be sure,
check how much memory is free
during a typical testing session.
If you wish to test on
multiple versions
of Internet Explorer,
see you install from
Windows installation media
that includes the version of Internet Explorer
that you require
and not a newer one.
Virtualization software
(like VirtualBox)
have powerful snapshot features.
Take snapshots after you make configuration
changes or install software or updates.
In case something goes bad,
you would be able to easily revert.
Clone the VM instead of
installing the same version of Windows
on multiple VM's.
After you install Windows on one VM,
clone it into a linked clone
(this is VirtualBox terminology)
and then simply upgrade Internet Explorer.
Choose to reinitialize the MAC addresses when you clone
(VirtualBox asks about this).
Make sure that the
browser will remain the same version
by turning off automatic updates
or choosing to ignore
the specific browser updates.
Disable System Restore.
Disable the screensaver.
Install the VirtualBox Guest Additions
and upgrade them each time you upgrade VirtualBox.
Configure your web browser
(home page, new tab page,
automatic form filling,
disable "accelerators", etc.).
ievms
An easy and popular way
for developers to
get some VM's with
Microsoft browsers
up and running
is ievms.
Time and Storage Saving Tip Regarding ievms
To save time and storage,
intall only those browsers that you intend to use.
When Google first released the 64-bit version of Chrome to the Canary and Dev channels they stated that:
Stability: Finally, we’ve observed a marked increase in stability for 64-bit Chrome over 32-bit Chrome. In particular, crash rates for the the renderer process (i.e. web content process) are almost half that of 32-bit Chrome.
http://blog.chromium.org/2014/06/try-out-new-64-bit-windows-canary-and.html
What exactly would make the 64-bit version more stable? Is there something about recompiling to 64-bit that makes it more stable, or was there some retooling under the hood that had this effect?
To develop NVIDIA CUDA programs, the tools needed are:
Developer drivers
CUDA Toolkit
GPU Computing SDK
What is this developer driver? Installing it silently overrides any NVIDIA graphics driver that is already installed. So, how is the developer driver different from the usual NVIDIA graphics driver? What extra components or functionality does it contain?
The developer driver is available in both 32-bit and 64-bit flavours. If I am developing 32-bit Visual C++/CUDA projects on 64-bit Windows 7, which flavour of the developer driver do I choose? Why?
From the developer download page:
Note: The developer driver packages below provide baseline support for the widest number of NVIDIA products in the smallest number of installers. More recent production driver packages for developers and end users may be available at www.nvidia.com/drivers.
The developer driver is released with the Toolkit and is intended to have wide support for all CUDA capable devices. On the other hand the drivers on the main driver page are released as appropriate; the main drivers have full support for CUDA, but each one may support a subset of devices.
Incidentally, when you install a NVIDIA driver it tells you what version is currently installed and what version you're installing (unless you choose a silent install!).