Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

A long time back I upgraded an ageing Sony VAIO SVE151A11W laptop with an SSD, which made it feel a bit faster. At that time I simply cloned the previous hard drive but not so long ago I decided to come back to this laptop and convert it to a retro gaming laptop, which meant re-installing Windows from scratch in my case.

I installed a new SSD and was actually able to find original driver downloads for the laptop (on Sony India website for some reason). Since I was installing all drivers and utilities from scratch I also decided to update the BIOS.

The update part completed successfully...

Capture.PNG Capture2.PNG


However after this step the setup utility got stuck trying to restart the laptop. Since this was a BIOS update, I didn't want to manually reboot the laptop in case the BIOS was actually corrupt, but after leaving it for around 30 minutes, I ran out of patience.

I terminated the process for the BIOS update tool and restarted the laptop. Going into the BIOS showed me that I did in fact have the latest R0240E6 version. Not bricked after all. From this point the laptop proceeded to boot OK too.
screen.jpg


I'm not sure why the setup utility got stuck, but since the update part was successful I think it's safe to say that a manual restart was definitely the right step forward (or I just got lucky that the laptop was bricked 😅).

Continue reading...  

, ,

Back in September I wrote about using a custom cache configuration file with Coherence. This was achieved by programatically loading the coherence-cache-config.xml file via a ConfigurableCacheFactory. I also mentioned that there was a much simpler way to do this, so lets see that way now.

With WebLogic 12.2, Oracle Coherence has updated names for all of it's system property overrides. The "tangosol" prefix is dropped, leaving for much simpler system property names.

The property we are interested in is...
coherence.cacheconfig


The value of this property needs to be set to the path of the custom Coherence cache configuration file. This should be done in the setUserOverrides script for WebLogic. For example...
 setUserOverrides
EXTRA_JAVA_PROPERTIES="-Dcoherence.cacheconfig=/my/config/coherence-cache-config.xml"


Once that is done, every time WebLogic is started, the Coherence cache configuration will be read from your custom file. This will impact all Coherence applications running in the WebLogic server. You can still use other cache configuration files on a per-application basis if needed though.

Continue reading...  

, , ,

A while back I wrote about how to fix the DNS records could not be found error in Google App Engine. Well it turns out, depending on your app.yaml settings and the rest of your certificate configuration, you could end up introducing an ERR_TOO_MANY_REDIRECTS loop for your website in a web browser. This is a simple thing to fix too, here's how.

This post is largely thanks to Egidio Caleiro Santoro and his comments on my earlier blog post.
ERR_TOO_MANY_REDIRECT2.png


If you have your CloudFlare security setting (SSL/TLS tab) set to Full or Full (Strict) and your app.yaml handler has secure set to always e.g. "secure: always", a redirect loop can arise. A temporarily workaround is to set secure to optional until you resolve these redirection issues.

In the above case a redirect loop should not typically occur since CF will contact your origin server using HTTPS, with secure set to always, GAE will respond over HTTPS too, no redirects are done. However if some of the old settings and DNS entries are still not in effect, redirections to HTTP could occur at some point in the communications.

CF has a good article explaining how to remove these redirect loops. Whenever dealing with DNS changes, it's always a good idea to wait 24-48 hours for all configurations to propagate (yes it should be quicker but sometimes waiting is the only option). At that point both CF and GAE security settings should be set to Full and always, respectively.

Continue reading...  

, , ,

My iPhone recently updated itself to iOS 13.1.3 and my Apple Pay stopped working. As most people (I imagine), I was using Apple Pay from the lock screen, well after that update every time I tried to pay for something, my phone would ask me for Touch ID unlock and instead of showing the Apple Pay screen, it would unlock and go to the home screen.

It was very annoying! It turns out that the Apple Pay from the lock screen is disabled by default in this update. To make it work as before, go to Settings, then scroll down to Touch ID & Passcode.
IMG_5867.png


From here scroll down to Wallet and make sure that the slider is turned to the On position...
IMG_5868.png


Once this change is made, Apple Pay will work as before.

Continue reading...  

, , ,