0 Comments

If your iMac starts with a screen similar to this:

image

don’t worry! There is a solution. Apple admit that they had bad hardware in a certain line of 2011 models. Apple offered to replace the videocard for free. But that offer has expired. I was not even aware it existed.

Never mind, the Apple store says that replacing the videocard will be between 600 and 700 euro.

That’s an expensive solution, so here is a cheaper one:

Bake your video card in the oven

I found this YouTube video about opening the iMac and put the card in the oven.

https://youtu.be/9vPM41ZmLoshttps://images-na.ssl-images-amazon.com/images/I/41wB-fA7TbL._SY355_.jpg

Here are the ingredients for the recipe:

  • Torx T10 (almost all screws are t10)
  • Torx T9 (2 screws holding the video card to the cooling system)
  • Cooling paste
  • regular Phillips screwdriver
  • 2 suction cups
  • a bit of aluminum foil (to make 4 aluminum balls to stabilize the card in the oven on the plate)
  • conventional oven (with bottom and top radiation and a plate)

I also used some alcohol, tissues and q-tips/ cotton bud to remove the old cooling paste

Start by removing the ram modules from the bottom of the iMac.

Follow the steps in the video to remove the glass with the suction cups and remove 4 screws on each side of the panel to tilt the panel and disconnect all 4 connectors. Remove the panel and disassemble the main board/ logic board. The required screws cannot be found in the video. But you can find then in this video:

https://youtu.be/6B4iCYSWlWM?t=4m55s

The link starts the video at 4 minutes and 55 seconds. Which explains the screws you need to remove for the main board. afterwards you need to remove all connectors on the front. Tilt the board and remove the connectors on the back.

Follow that video to the end and then continue with the previous one to remove the cooling from the videocard.

clean the videocard and put it on 4 aluminum balls on a plate and put it in a pre-heated oven for 8 minutes on 200 degrees Celsius.

image

put new thermal/cooling paste on the chips and re-assemble everything. Do not forget the ram modules.

Here are some pictures from my baking experience:

IMG-20171108-WA0001IMG-20171108-WA0002WP_20171108_09_32_11_ProWP_20171108_09_32_19_ProWP_20171108_09_42_30_ProWP_20171108_09_51_20_ProWP_20171108_09_51_25_ProWP_20171108_10_23_18_ProWP_20171108_10_33_18_RichWP_20171108_10_37_19_RichWP_20171108_10_48_19_RichWP_20171108_11_39_23_RichWP_20171108_11_41_24_Rich

Good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn

I was trying to create new packages for a Store application and got this error. I was updating my Nest Thermostat application and adding the new Navigation View component. Which is a great new XAML component.

The docs for the navigationview xaml control are great. But during the creation of the new store package I got this dummymodulereference error… Here is my attempt to fix it:

image

  1. cleared all nuget caches
  2. removed the .vs hidden folder in my solution folder
  3. removed in each project folder the bin and obj folder
  4. removed the project.lock
  5. Had to open my solution file in notepad++ to see that I had a project in my solution in an other (parent) dir. So had to remove bin and obj and project.lock there too.
  6. right click on solution in the solution explorer and restore nuget packages
  7. build –> rebuild solution

But unfortunately..  I Googled with Bing and found people having similar issues: https://developercommunity.visualstudio.com/content/problem/133644/internal-compiler-error-5.html

and https://developercommunity.visualstudio.com/content/problem/137629/error-on-build-for-store.html


I even removed the symbol cache (tools –> options –> debugging –> symbols –> empty symbol cache)

Also skipped the nuget restore, because creating store packages will auto restore nuget packages.


I found out that the issue was in a global nuget package:

image

So I added a reference in my store app project to the same nuget but a newer version. Not 1.7.1 but 2.0.0

That did not help, so I added the microsoft.net.native.compiler package to all my referenced projects.

Also no fix. Last resort: tweet to @VisualStudio because it is already listed in the vs feedback.




Please let me know if you have a solution.

Pin on pinterest Plus on Googleplus Post on LinkedIn

The 15.4 update of Visual Studio has a lot of new things. Also the Fall creator update enables you to use .net Standard 2.0 in UWP apps. Adding UWP apps in the store is easy and native. But you can also pack other types and submit them as store apps.

WAP

Windows Application Packaging Project. it’s a new project template in vs15.4 You can load up the solution containing your application and add a new project of this type.

Select the target and minimum version of the Windows SDK (this is recognizable from uwp apps)

Right click applications in the solution explorer and add a reference to your main application project

Add Project Reference

Then you can use the create app packages like you would do for an UWP app

You can read more about it on the microsoft docs site

https://docs.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-packaging-dot-net

Pro tip: visit the Microsoft Docs website more often. They are really improving lately. Like a lot!

There is just one thing I would like to point out: your developer account needs extra permissions to submit such type of application.

You will need to submit your info on this page:

https://developer.microsoft.com/en-us/windows/projects/campaigns/desktop-bridge

and they will get back to you in 6 business days.

I have submitted two apps, one for the general store and one as a business app which is only available for my colleagues in a private store. Both are still waiting for approval. Hope to hear soon from the team.

So the pro-tip of today is: make sure your dev ms account has privileges to submit a desktop bridge app to the store!


Good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn
0 Comments

I am using https://github.com/Lone-Coder/letsencrypt-win-simple for a while now and moved to 1.9.5.1 today. It has a great new feature. Updating my webapplications was done by changing the path in IIS

For instance: C:/www/website1/20170918 had a newer version in C:/www/website1/20170919 So I just changed the path in IIS and could revert back to the older version in seconds. The Let’s Encrypt application got confused by this, because it stored the path in the registry. The latest version checks the IIS meta database for the current path, which is really nice for me.

But back on topic: The Asp.Net forms auth can be an issue. When the Let’s Encrypt tries to reach the .well-know dir, it get’s a redirect to the configured login page.

I tried to fix this by excluding the well-known dir in my web.config but that broke my web applciation (error 500)

I have also tried to escape the . (dot)

<location path=".well-known">
     <system.web>
       <authorization>
         <allow users="*" />
       </authorization>
     </system.web>
   </location>

Like this:

<location path="\.well-known">
     <system.web>
       <authorization>
         <allow users="*" />
       </authorization>
     </system.web>
   </location>

But that also gave me the 500 error. So The only workaround I could think of was to temporarily comment out some lines:

<authentication mode="Forms">
       <forms name=".ASPXAUTH" loginUrl="Login.aspx" protection="All" path="/" timeout="120" defaultUrl="Index.aspx" slidingExpiration="true" />
     </authentication>
     <authorization>
       <deny users="?" />
       <allow users="*" />
     </authorization>

And ran the letsencrypt.exe follow the wizard, and uncomment the part again and save the web.config. Please contact me if you have a better or more permanent solution by mail or tweet.

Good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn
0 Comments

My Surface Pro 3 died last October which had my bitcoin wallet on it. I forgot that I had any. I had bought them a (long) time ago for about 10 euro if I remember it correctly. But since the hardware crash of my sp3, the rate went up. Way up….

snip_20170809160659

I decided to look into my backup and try to restore my wallet to see how much I had and how much it’s worth today. I had multibit classic in the beginning and upgraded to multibit HD 0.5.x back then. During the move from classic to HD I forgot my wallet words and only had my password and the backup AES wallet files.

I started my first recovery attempt on may 30th, but failed because I had no wallet words.

My second try was last week as I found this GitHub repo with a python script which can extract words from a backup file if you have the password. Sort of brute force “attack”. https://github.com/gurnec/decrypt_bitcoinj_seed

So I installed python 2.7.x alongside with 3.6 which I already had. and ran the PowerShell script.

I had a Windows 7 style backup by the way of my Win10 device and had to navigate to “C:\Users\myUsername\AppData\Roaming\MultiBitHD” and restored the full content of that folder to a new folder on my desktop. Please do not forget to check the box to have the original folders restored. Otherwise it will replace files with the same name and path references will be broken.

But somewhere in the mutlibithd is the rolling backup which you can restore once you have your password and wallet words…. so I thought.

But the amount stayed unconfirmed. So it’s useless. I have seen a lot of people with this exact same issue. Some moved away from multibitHD just because of this. The solution was not that obvious. It also did not work for everyone.

I had to downgrade to MultiBit HD 0.1.1 https://multibit.org/releases/multibit-hd/multibit-hd-0.1.1/

and renamed “C:\Users\myUsername\AppData\Roaming\MultiBitHD” to “C:\Users\myUsername\AppData\Roaming\MultiBitHD-old” and re-restored the wallet with the password, wallet words and backup file.

snip_20170809162115

It is weird to have the old 0.1 version, but I am glad that it is confirmed again and in my wallet. Now I can step away to alternative wallets.


Good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn