- #GET ACTIVEX VLC PLUGIN REGISTERED INSTALL#
- #GET ACTIVEX VLC PLUGIN REGISTERED SOFTWARE#
- #GET ACTIVEX VLC PLUGIN REGISTERED WINDOWS 7#
There's literally a dozen different ways to make the system work however you want.How to register an ActiveX control (.ocx) manually Summary
#GET ACTIVEX VLC PLUGIN REGISTERED INSTALL#
And it's dead simple to install 32-bit Debian then install a 64-bit kernel giving you full, non-PAE access to memory while having a 32-bit userland if you need it for compatibility with some odd non-free app. The only things that seemed to have issues porting had heavy roots in Win32 like FF, OO.org, etc native unix/Linux apps worked with minimal effort because they were already compiled and tested on Alpha, sparc64, etc years ago.
The package managers took a little bit to become biarch, I'm not even sure if dpkg/apt are yet but RPM has been for a while now (probably because RH wanted to support non-free crap like Oracle), but that development has lagged because it's not really necessary because pretty much all Linux packages have 64-bit builds that work just fine and the disk/memory savings from running a 32-bit app are minimal. Besides if you don't want to worry about what bitness program you install, just always opt for 32-bit. exes is not worth the costs when you could just offering a seperate version, and also people might want to control what bitness of the program they install for whatever reason. Possibly because doubling the size of some. As far as OS X, are you referring to fat binaries? I believe MS has reasons for not doing fat binaries, but I'm not sure what they are. Well I've never noticed anything not work in 圆4 Windows in the 4 years or so I've been using it. Is this a UNIX thing or something Apple? I don't worry about OS X installs being the wrong version, but I have to with Linux distros/Windows installs. You can change the kernel type with a preference modification. I want to know what Apple is doing to offer 32-bit and 64-bit in one package.
#GET ACTIVEX VLC PLUGIN REGISTERED SOFTWARE#
Most 32-bit software works on Windows 圆4, but there are some exceptions and enough to be noticeable. you get no increased entropy on 圆4, so it's a moot point. Wasn't it difficult to mix 32-bit and 64-bit user land apps in linux distros such as debian until recently? Windows never had that problem, seeing as 32-bit worked equally well on 32-bit and 64-bit systems, and the app itself doesn't need 4GBs+, why bother recompiling and testing the app? Of course, that ignores benefits from 64-bit ASLR, but MS does not use 64-bit ASLR in 圆4 Windows yet, i.e. In short, there's no point in worrying about it but it is odd. Look at FF, I've been using 64-bit builds on Debian for over 5 years now and it works just fine and yet there's still no official 64-bit Windows build. I don't know what the technical hurdles are on Windows, but they sure seem to exist since so much software doesn't have 64-bit builds when they do for other platforms, but the reality is that it doesn't really matter.
And a 64-bit VLC ActiveX/Mozilla plugin would be nice for the browsers and media, leaving (once again) only Flash as the only real culprit holding 64-bit browsing back.
#GET ACTIVEX VLC PLUGIN REGISTERED WINDOWS 7#
Now, the 32-bit VLC runs just fine on Windows 7 圆4, but it kinda seems they're leaving Windows out from the 64-bit party. Their compiler wasn't 64-bit or something like that? Surely something has improved in the last three years? Why not Windows? The last posts I can find on the issue are from 2008. I would assume the Linux version has a 64-bit version.