Trouble Creating a Global Mutex - global

Testing on a Windows 10 Home edition. When I attempt to create a global mutex of the form "GLOBAL\mutext name", I get error code 3. I suspect that this may be because I am not running on a server-class machine. However, Microsoft documentation says this should work even on my old XP Pro system.

Related

Visual Studio Code on Windows server 2008

Can I install Visual Studio Code on Windows server 2008 ?
I am a developer but I sent the information to my administrators and they told me that the setup file crashes after launched
I get seput file from hee https://code.visualstudio.com/download
procesor: Intel(R) Xeon(R) Gold 6142 CPU # 2.60Ghz - 2.59 GHz
RAM: 8 GB
64-bit
virtual machine
1 CPU - 2 cores
Windows Server 2008
First time answering here so bare with my vintage reply formatting. (also pardon that i couldn't capture screen due to server is on a intranet that not accessible on this device causing a long reply)
Being a unfortunate fellow that need to work on legacy Systems and Application frequently, i happen to have a fresh 2008R2 server recently setup by my team's Server Admin with following specs:
processor: Intel(R) Xeon(R) Gold 5220 CPU # 2.20Ghz - 2.19 GHz ,
OS: Windows Server 2008R2 x64 ,
RAM: 8GB
The versions that is able to install was 1.70.3,which is the same version that is the last supporting versions for Windows 7 as well,if you happen to need to work on devices using that OS version.
although i'm uncertain whether it is a VM or not, i'd like to point out a few more things that your question did not cover but need to consider:
The installer version (System setup vs User Setup)
aside from the x64 |x86 | ARM installer differences, as you've not mentioned which versions of the build and which exact setup installer you sent to your admin, i've first replied which build version successfully installed on 2008R2, which as of writing the latest build was 1.73.0 and on run,it pop up a error message as follow regardless of System/User Setup:
This Program does not support the version of windows your computer is running.
in our current case that we want specific previous versions installer, VScode FAQ on previous versions have a URL lists that enables you to download a specific build version of your preferred setup. For my case (and also refer below to exactly why this one), i've go for System setup, and i know the aprox. supporting version was ~1.70.0, so i used the link as below and replace the {version} to start:
https://update.code.visualstudio.com/{version}/win32-x64/stable
Active Domain, Multiple user sessions etc.
Per VSCode requirements page stated,
VS Code does not support multiple simultaneous users using the software on the same machine, including shared virtual desktop
infrastructure machines or a pooled Windows/Linux Virtual Desktop host
pool.
as im not sure do you work solo or do have fellow colleagues to code on the server at the same time, you might need to reconsider to install using user or System setup.
if your intentions are to use exclusively on a specific AD account, then user setup should probably be good enough.
however, if the intentions was to setup say a shared Remote desktop connections on the VM that allows multiple RDC sessions simultaneously for coding,programming etc., so you intend to install a system setup to allow all users on said server to be able to use VScode, then you might run into the problem the VScode requirements stated it does not support.
in addition, as i was remote connected as administrator , when using a 1.70.2 user setup ,a different warning message as follow was thrown:
This user Installer is not meant to be run as Administrator. If you would like to install VS Code for all users in this system, download the system Installer instead.Are you sure you want to continue?
as the installer itself also checks with the operator on this matter, your admin may have skipped on the exact reasons why the install failed and just told you the installer crashed.
if you absolutely need VScode to run on the server but can't install for reasons, the last resort (aside from going for alternatives like notepad++) is to Setup a Portable Mode builds on your own workstation/devices first, then upload the package to the server and use it from there.
i wouldn't go into too much detail in that as this reply already span for a starwars trilogy length but keep in mind, version limitations still apply, and whatever add-ons you need, you need to download them first before bundle it into the package to upload and run on your server.
Anyone that is a System admin or infrastructure architects , do correct me on my novice understanding on Server settings etc. as although i'm primarily a programmer, i did end up touching a lot more things that i'm not specialized into over the few years of vendor career work so there bound to be incorrect/inaccurate concepts i spilled. cheers.

Run application as 32 bit in VS Code

I am trying to develop a small application which must interact with a very old version of access and pull the data out. We have a solution already in powershell but we want to move away from powershell and get it in C#
I think I have code that should work theoretically, but there's one setback, it must be run in 32-bit mode due to the age of the access version I'm working with. When I run my app, there are no exceptions, I simply get a message in my debug console that says:
The Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.
The powershell has a requirement that it must be run in 32-bit powershell and after researching the above message I believe my application must also be run in 32-bit mode. I have also settled on using OLEDB to access the file, just as the powershell does, further adding to my assumption
I primarily use VSCode to develop here, but I am not above installing regular Visual Studio if necessary
I installed the 32-bit VSCode and ran my application there but I got the same message
How can I fix this?

How to update from a original XP no service pack to XP3 with no internet

First off I used to be an XP guy and I still have the copy that I bought back in 2002. I had to downgrade my computer to an old iMac I had in storage and the only copy that I have of XP (I really do not want to buy a new one) is the old copy. I installed into a fully formatted drive and then realised that this XP disc came out before service pack 1. Which means that there really is no support for this. Next I noticed that the ethernet driver is unrecognized (big shock) therefore I have no internet, so I cannot install using windows update. Therefore I do not have any updates (again this disc is very old) and no access to the internet.
I have another computer that I can burn discs off of and it has the internet but I will not have it for much longer.
The device I installed the XP on is an 20-inch iMac (Early 2006), 2.0 GHz Intel(R) CPU T2500 with 1.98GB RAM
Is it possible to update my machine and be able to do use it the way it should be?
How I managed it was that I downloaded found an executable version of SP1a and then updated the system by moving the file over, then I downloaded the service pack SP3 ISO, updated the system.
However it didn't fix the ethernet driver and since I had no idea what the controller's actual name nor the company that made it, I moved over the Auslogics System Information, did a diagnostics took the problem devices "Value" and did research in order to find the needed information, and got the driver and moved it over. Yay monotony.

clGetPlatformIDs error -1001 when called in PostgreSQL UDF

I'm trying to write an OpenCL function that would be executed inside PostgreSQL. To do this i create DLL from my OpenCL code and link it to postgres using User-Defined Function mechanism. Everything goes well until clGetPlatformIDs is called. Function returns error -1001, which I read that indicates problem with finding OpenCL drivers.
I've tried to compile the same code(i had to remove some postgres magic) to exe and runed it with success - all platforms were found correctly, so I assume that i have correctly set up SDK and drivers.
I am runing PostgreSQL 9.1 on windows 7 x64. I am also using Nvidia CUDA SDK 4.2 with Visual Studio 2010 and running my code on GeForce GTS 450.
It's MSFT's problem with Windows, Services, GPUs, Security and device drivers.
You can't run PostgreSQL as a service on Windows AND see any GPUs. You are hitting Session O Isolation which does NOT allow any 'graphics' device access from a Windows Service. You can start PostgreSQL as a process (not a service) or put the server on Linux.
See http://www.scribd.com/doc/58343489/Windows-Session-0-Isolation-Impact-on-GPU-as-Service
Also there are other important reasons to run on Linux, as Windows will want to reboot your GPU if the screen is not accessed before the timeout period. See
http://msdn.microsoft.com/en-us/library/windows/hardware/ff570088%28v=vs.85%29.aspx
NVida have a non-graphics GPU device driver for specific Tesla cards on Windows. These cards don't have any video output. So they aren't considered to be graphics device drivers.
Maybe the libraries try to locate the SDK using some environment-variables and the environment is not inherited inside the PostegreSQL context.
So try to dump the environment from your two codes and check if any OpenCL/Cuda variables is available in your standalone program and missing in your PostegreSQL UDF.

Do virtualised machines require separate software licenses?

I have a windows 7 machine, but for various reasons I need to have access to windows xp also.
I know it's possible for me to have a windows xp virtual machine set up, so that effectively I can have use of both.
Irritatingly, I've got into a situation where I really must have visual studio 2008 installed on Windows 7 and XP (don't ask!). My question is, can I share my existing software licenses across the virtual machine also, or do I have to purchase separate ones?
Because you are running Win7 on a CPU that has hardware virtualisation enabled, you have the option of using the Windows XP Mode, which is a virtualised copy of XP that is already fully licenced, you don't need an extra licence for it.
If you want to setup a separate virtual machine running XP then yes, you will need a separate licence for XP itself.
If you sourced your copy of VS through a MSDN subscription then that is per user, so you can install it multiple times. If you bought a single copy of VS then the licence will be per machine (which includes virtual machines).
The simple answer is Yes - If you have a new Virtual Machine with an OS installed all software running inside this container (including the OS) is classed as a separate machine (such as a second PC next to it)
Double check your VS2008 Licence as you may be able to install on more than 1 PC.
Obviously this is my advise from previous experience - if your really concerned check with a Solicitor before proceeding
Many Microsoft licenses are per user, not per machine. If this is the case (check your license) then you can install it on both your Windows 7 installation and Windows XP installation.