Archive

Posts Tagged ‘Fix’

Fix: Cisco Webex Meetings install fail (AddDllDirectory @ KERNEL32.dll)

Looking into the following error message occuring with Cisco WebEx Meetings installer on Windows 7, found this useful discussion:

https://social.technet.microsoft.com/Forums/en-US/a0970bfe-2bca-4ae3-a463-a5a04df83770/could-not-locate-dynamic-link-library-kernel32dll?forum=w7itproinstall

image

where the following are suggested:

– install Update for Windows 7 (KB2533623) from Microsoft:

https://www.microsoft.com/en-us/download/details.aspx?id=26767

– video tutorial:

https://www.youtube.com/watch?v=TpRRiMGJ_xA


And an extra tip, in case you after the installation, when you try to connect via a meeting URL, you see this dialog:

image 

then try enabling TLS 1.1 & 1.2 at your browser (e.g. was told Chrome on Win7 had then both off). See how to do this for various browsers at: https://knowledge.digicert.com/generalinformation/INFO3299.html

Fix: make ownCloud installer display in English language

OwnCloud is an interesting solution for setting up a file sharing cloud for a group of people.

However,one issue I’ve found with its Windows desktop client’s current version (which looks clean of any viruses since I always check first) is that if your Windows 10 is configured with a preferred language that the desktop client’s installer doesn’t have localization support for, then it doesn’t show up in English as you’d expect, but in Czech or someother language that most of us don’t know how to read.

Screenshot (493)

So I tried running it’s MSI installer (ownCloud-2.6.1.13407.13049.msi) with –? parameter from the command-line and the /g languageCode parameter mentioned there looked promising, but trying /g en for English didn’t work. I guessed it needed some specific language code number (and not double-letter language code like en for English), since the help text was mentioning to see Windows Installer SDK for more help.

After a quick search I found an article that suggested passing the parameter Productlanguage=1033 to an msi installer on the command-line for it to ALWAYS show in English. And indeed it worked.

Screenshot (494)

To open a command window one can click the Search icon on the windows taskbar and type CMD then press ENTER.

Then they can drag-drop the .MSI file of ownCloud installer onto the black command-line window that opens up and type an extra space char and then Productlanguage=1033 before pressing ENTER to launch the ownCloud installer in English. After that they can close the command-line window at anytime.

Since many users may be uncomfortable with such instructions, one could provide an msiEnglish.bat file that just contains

%1 Productlanguage=1033

User could drag-drop the .msi they want onto that msiEnglish.bat file and it would run the msi installer being displayed in English language, irrespective of any preferred language settings at the Windows operating system.

Of course the best thing would be if ownCloud fixed their desktop client installer to fallback to the Engish language (set it as default) if it can’t find localization strings for the currently prefered language of the user. Have filed an issue at https://github.com/owncloud/client/issues/7825

Fix: Buildbox activation issues on load

Buildbox is a wonderful game authoring tool (that spans the whole nocode-code continuum, including the low-code aspect). It now has a free version too with nice templates and tutorials included.

image

I had an issue with the Windows version (it also has an indentical MacOS-X version since it’s a Qt-based app) where it was complaining about activation issue at startup and couldn’t proceed.

To solve that you can remove activation info (which won’t be removed if you just do uinstall and reinstall) by deleteing the com.eightcell.buildbox subfolder at:

C:\Users\YOUR_PROFILE_NAME_HERE\AppData\Local\eightcell\Buildbox\

Next time you run Buildbox.exe it will show activation dialog and you can enter your registration key (even the free version has one that you can download from your free account at http://buildbox.com)

With the latest Buildbox 3 there seems to exist an extra com.eightcell.buildbox3 subfolder that you could delete or just rename the main.iblicense files in there to main._iblicense. The launch Buidlbox again to see the activation dialog.

image

There probably exists some bug in Buildbox that causes one to repeat this action often.
So you could add a RESET_BUILDBOX_LICENSE.BAT file to your desktop with the following commands to delete the license file:

del "%AppData%\..\Local\eightcell\Buildbox\com.eightcell.buildbox3\main.iblicense"
@pause

Fix: Acer Aspire One (AS1) ZG5 blank screen at startup

Seems Acer Aspire One (AS1) ZG5 can have a recurring problem, esp. if its battery is near its end of life. If it shuts down abruptly its BIOS settings seem to get corrupted and its BIOS instead of discarding them seems to freeze.

Luckily they have a way to update the BIOS via USB key at machine power up. Flashing the BIOS (even to the same version) will fix the issue. Probably resetting the BIOS NVRAM data would do the same, but since you can’t boot this is the way to do it (without fiddling with the hardware directly that is).

The process suggested by ACER in case you come across this issue is the following:

Create a recovery USB drive to update the Bios on the unit.

The specific steps to perform this recovery with the USB drive are:

1. Download & Extract BIOS_Acer_3310_A_AOA110 & AOA150 (found in  https://www.acer.com/ac/en/US/content/support-product/60?b=1)

2. Rename the Bios name from 3310.fd to zg5ia32.fd

3. Copy zg5ia32.fd and Flashit.exe to USB flash drive.

4. Start the restoration process:

  1. Plug the AC Adapter into the unit.
  2. Insert the USB flash drive into a USB port.
  3. Press and Hold down the Fn and the Esc keys together.
  4. Keep these keys held down and press power.
  5. When the unit’s power light comes on release the Fn and Esc keys.
  6. After the keys have been released the power light will start to blink.
  7. Let the unit run and after approximately 1 to 7 minutes, the unit should reboot.
  8. Video should now be restored.

Can also see the process in this video:

https://www.youtube.com/watch?v=iHkGkw9EE8c&feature=emb_logo

See my comment there with the newer links I have above, have fixed the links they had (since they had old broken ACER links they eventually provided the file themselves) so that you download the BIOS from ACER directly, to be safer and to be sure you always get the latest BIOS (aka 3310 at the time of writing).

Categories: Posts Tags: , , , , , , , ,

Fix: “A numeric comparison was attempted” at VS build (Costura.Fody)

After upgrading from Visual Studio 2017 to Visual Studio 2019 I was able to update NuGet packages Fody and Costura.Fody of a solution that needed them (to package assembly DLLs inside console EXEcutables) and the solution was rebuilding fine.

However after I synced the solution via a Git repository on another machine and installed the newer Visual Studio there too, I rebuilt the solution in order to fetch/rebuild NuGet packages too and although everything seemed to rebuild fine, when I was using a plain build instead of a rebuild all I was getting at Errors dialog for each project that was using Costura.Fody:

Error

A numeric comparison was attempted on "$(MsBuildMajorVersion)" that evaluates to "" instead of a number, in condition "($(MsBuildMajorVersion) < 16)".  

To fix this I had to uninstall and reinstall Costura.Fody NuGet package (it wasn’t needed to uninstall/reinstall the Fody NuGet package itself) on the solution’s projects that were using it and then all was rebuilding/building fine again on that other machine.

Fix: Invalid Firmware Image at Dell Inspiron 3537 BIOS update

For some time now I was trying to update the BIOS of an older Dell Inspiron 3537 laptop from inside Windows (with the InsydeFlash application that the respective Dell update package employs), only to get a blue screen saying Invalid Firmware Image upon reboot and the BIOS update was skipped every time.

Since that update was fixing a critical security issue (Intel Security Advisory INTEL-SA-00115 – CVE-2018-3639 & CVE-2018-3640), I decided to do some more research on it. I eventually came to the conclusion that since I had A9 BIOS version, I needed to install BIOS version A10 first (which addresses CVE-2017-5715 and associated Intel Reboot issue), then try the BIOS version A11 update that the Dell Support online was offering.

Luckily there was a Dell BIOS update guide that was suggesting to visit Dell downloads catalog to find older updates, from where I found all Dell Inspiron 3537 updates and was able to locate the A10 BIOS update.

Updating the BIOS from version A9 (the version I had, as displayed at “Current BIOS” field on the InsydeFlash UI) to A10 and then after reboot from A10 to A11 with the respective update executables worked fine. Can confirm the update is done by launching the update once more and then just Cancel.

image

%d bloggers like this: