We just purchased new HP Z200 machines that came with Windows 7 Enterprise 64-bit on them and we have upgraded them to Service Pack 1.
When we go into Component Services and expand computers and right-click on My Computer and choose properties, the Options tab has a disabled "Enable partitions" option that we have not been able to figure out how to enable.
We do not have this issue on Windows 2008.
Any ideas?
According to: http://social.technet.microsoft.com/Forums/windows/en-US/a601d45a-10c0-4da9-a424-d35afef22161/how-to-enable-windows-7-windows-8-com-partitions-function
I'll quote in it's entirity:
According to the Product team on this behavior, starting from Windows
Vista, they have the “Enable Partitions” checkbox grayed out on client
desktops. This was an intentional change as they want the ability to
have COM+ partitions to be available only on servers and not client
desktops.
...which makes me wonder why the blazes the checkbox is there in the first place if there's never going to be a way to enabled it.
Related
Hi I have a new protocol URL:myTest, how can I add it in windows 10 so I can see it listed in default programs? Shall I add it in registry? How/Where exactly could I do that?
I want to associate a program with this protocol.
The registration for "Default Programs" is in the registry under SOFTWARE\RegisteredApplications. If your application fits one of the client types then you should point your RegisteredApplications value to Software\Clients\%ClientType%\%YourCanonicalName%\Capabilities, otherwise you can use any key like Software\%YourCompany%\%YourApp%\Capabilities or Software\Classes\Applications\%Filename%\Capabilities.
The most important subkey in your case is UrlAssociations.
You must also register your protocol in the normal way.
Some of this changed in Windows 10 and I would recommend that you test on Windows 7 or 8 as well. "Default Programs" has been deprecated in Windows 10.
You should also register yourself in the Applications key for integration with the "Open with" dialog.
This is the way it works for pure desktop apps, I'm not sure what happens if you convert a desktop app to UWP. Modern apps declare their protocol in the manifest.
I have this code in my WinJS default.html:
<x-ms-webview src="http://localhost/"></x-ms-webview>
<x-ms-webview src="http://display/"></x-ms-webview>
<x-ms-webview src="http://192.168.1.2/"></x-ms-webview>
display is defined in the hosts file:
127.0.0.1 display
and 192.168.1.2 -- the one that is successful -- is another computer on the network.
This is in my appx.manifest:
display and localhost successfully load in IE on the desktop and metro.
My OS is Windows 8.1 Enterprise. I have also completely disabled the Windows Firewall and this has had no effect.
What else can I do?
Microsoft blocks connections to the local machine except while running from the Visual Studio debugger.[1]
There is, however, a workaround tool. Quoting from this post on an MSDN blog:
Immersive applications (and IE11 on the Desktop) run inside isolated processes known as “AppContainers.” By default, AppContainers are forbidden from sending network traffic to the local computer (loopback).
[...]
I have built a GUI tool that allows you to very easily reconfigure an AppContainer to enable loopback traffic. This tool requires Windows 8 and runs on the .NET Framework v4. When launched, the utility scans your computer’s AppContainers and displays them in a list view. Each entry has a checkbox to the left of it, indicating whether the AppContainer may send loopback traffic. You can toggle these checkboxes individually, or use the buttons at the top to set all of the checkboxes at once. Click Save Changes to commit the configuration changes you’ve made, or click Refresh to reload the current configuration settings.
The aforementioned standalone tool is available from here.
I am making an installer for my application using visual studio installer.I was wondering if there is any way to "pin" my application to the "Windows Start Menu" using the installer
You really should not be doing this - pinning and unpinning is meant to be a user action / preference. No matter how amazing your application might be, it is up to the user if they want to pin it or not.
A small set of applications are pinned by default for new
installations. Other than these, only the user can pin further
applications; programmatic pinning by an application is not permitted.
There are ways around this limitation, i.e: this and this. But even there it notes that you are not supposed to be doing this.
I've noticed that in the Phone 7 Beta emulator there is a settings application. It contains an "applications" panel. This seems to imply that we should be writing settings plugins so that settings for all apps are managed centrally, similarly to how the iPhone settings work.
Does anyone know how we write/register these plugins? Or if I'm on completely the wrong track?
Thanks!
All settings and configuration for any application you create should be managed from within that application.
This is different from the iPhone where settings and configuration are considered separate and should be managed in separate places.
The Settings "application" on the device/emulator contains system settings and what it calls "application" settings. What are termed applicatoin settings actually relate to hub settings (plus IE & Search).
From the UI Design and Interaction Guide for Windows Phone 7 version 2.0 (page 66 - System and system application settings)
"Application settings must be
implemented within the application
itself."
MSDN: How to: Create a Settings Page for Windows Phone
Edit:I just tried the SettingsSample and that doesn't appear in the OS settings page but I think that is the plan in the final SDK this functionality should be available.
I am running McAfee VirusScan Enterprise 8.7i on my Windows 7 machine.
I am writing this utility to configure McAfee. Now how do I turn off McAfee programmatically (using C++ or C#)?
The only ways I can do it right now are:
Manually opening the McAfee Virusshield icon from the system tray and then selecting Exit.
Run a command prompt under SYSTEM account (using System internals tool psexec) and then issue the command "sc stop McShield"
I guess the point of virus scanners is that they CANNOT be switched off by other software (at least not easily)
Right click on the VShield icon in the system tray and choose Manage features and the VirusScan Enterprise
Double click on Access Protection to get to the properties
Un-check the option for "Prevent McAfee services from being stopped"
You should now be able to stop the McAfee services