Windows 7 RTM

-
Yes it's true. Windows has finally been finished and released to MSDN. Go and get it! It's good, really it is! Forget Vista and move on.

Comments

Post a Comment

Popular posts from this blog

Enabling SNMP on an ASUS RT-N66U

-
Recently I wanted to monitor an ASUS RT-N66U, a brilliant router with many feature, one of which did NOT appear to be SNMP. After some rooting around on the Internet (pun intended?), I discovered that it is actually quite easy to set up. For this you will need a small USB stick, I used an old tiny 4GB thumb drive. Ensure it's partitioned and formatted to ext2. If you're using Windows then EaseUS Partition Master can help, there's a free version for home use.  Otherwise the Gnome Partition Editor , otherwise known as GParted, will work. Just pop the USB drive into the back of the router and go to the "USB application" page in the UI, it's one of the options under "General" on the left hand index. At the bottom of that page is the "Download Master" which you can then choose to install onto your USB. What this does is into install a package manager, along with various packages for the Download Master, but this gives you the abilit
Read more

Making Microsoft Dataverse OData queries using Postman

-
Once you have registered your application and have your ClientId and ClientSecret you can use these to authenticate using oauth2 client credentials workflow. Environment Create an appropriate Postman environment with the following variables: url - https://<yourcompanyname>.crm4.dynamics.com clientid - <your clientid> clientsecret - <your clientsecret> version - 9.1 webapiurl - {{url}}/api/data/v{{version}} tenantid - <guid> authurl - https://login.microsoftonline.com/{{tenantid}}/oauth2/v2.0/token Collection Authorization Setup Authorization for your Postman Collection so all the calls within will inherit it and use the token. Set the Type to "OAuth 2.0" Add auth data to "Request Headers" Configure New Token Token Name - "MyToken" Grant Type - "Client Credentials" Access Token URL -  "{{authurl}}" Client ID - "{{clientid}}" Client Secret - "{{clientsecret}}" Scope - "{{url}}/.default"
Read more

Making node / npm / gulp / elixir work for Laravel using Homestead on Vagrant with Virtualbox on Windows

-
Wow what a title. More of a note to myself this one. Problem: npm install or variants thereof cause errors, mainly related to long filenames when run inside a homestead virtualbox virtual machine on Windows. A simple fix is to create a symbolic link inside the vm for the node_modules path so that it doesn't reside inside the folder being shared with the Windows file-system. Modify the Vagrantfile or the scripts/homestead.rb file if using homestead to include the following as part of the config: config.vm.provider "virtualbox" do |v|     v.customize ["setextradata", :id, "VBoxInternal2/SharedFoldersEnableSymlinksCreate/v-root", "1"] end Then you'll need to run the Git Bash shell as admin, otherwise it won't let you create the symbolic links. The important part here is actually that winnfsd.exe starts as admin so you could change the compatibility in the properties to start as admin. Start vagrant with a "vagrant up&q
Read more