作者:Michael

Home / 作者:Michael

VSphere Cilent是一款虚拟平台工具,大多Win10系统在运行VSphere Cilent时都会被提示错误,无法正常运行,这是怎么回事?让小编来给大家分析分析。
原因分析:

Win10系统下无法运行VSphere Cilent,主要是由于Win10的.NET版本是3.5,而VSphere Cilent支持.NET2.0的。

解决方法:

  1. 从一台不是win10的安装了 Microsoft .NET 3.5 SP1的机器里,在这个路径:%SystemRoot%/Microsoft.NET/Framework/v2.0.5010210/,复制system.dll。
  2. 在安装路径里:C:/Program Files/VMware/Infrastructure/Virtual Infrastructure Client/Launcher/

如果是X64系统就是:C:/Program Files (x86)/VMware/Infrastructure/Virtual Infrastructure Client/Launcher/,建立一个文件夹:”Lib”, 将刚才的文件system.dll放在这里。

  1. 编辑C:/Program Files/VMware/Infrastructure/Virtual Infrastructure Client/Launcher/VpxClient.exe.config文件

加入:

  1. 在系统环境变量中建立一个新的环境变量:”DEVPATH”, 值为:C:/Program Files/VMware/Infrastructure/Virtual Infrastructure Client/Launcher/Lib

上述步骤设置完成之后,用户在Win10系统下重新打开VSphere Cilent就能正常运行了。

经历了一次DJI的卖空服务

10/11/2018 | Uncategory | 没有评论

2018年8月24日在DJI Store,官方商城在线订购Osmo三脚架组件1套,按其官方说法预计10-15个工作日发货。但是DJI Store官方迟迟不能发货,至2018年9月15日,也即超过15工作日时间后收到DJI Store邮件,说明其受产能限制,订单将延迟发货,但是无具体时限,DJI单方面意愿给予50DJI 币补偿。随后与DJI在线客服交涉,产生案例号:CAS-2302900-XXXXXX,随后2天左右,客服联系并建议去第三方平台重新购买此产品,并不对产品质量做任何保证。

1、关于订购该产品的订单,DJI Store并无货或没有能力继续生产,而继续让该产品上架,导致我无法及时使用到此产品,属于欺诈销售,并迟迟不能提供合理的处理意见。

2、单方面意见,给我账户所谓的补偿,虚拟DJI币,属于商业霸凌。

3、高级客服对于案例CAS-2302900-XXXXXX处理答复,让我到第三方平台而不是官方旗舰店购买,高级客服的答复像是在面无表情的说笑话,第三方的产品质量能够保证么?是否DJI正品?客服均无法给出答复。

MMDVM Pi-Star to Hampager

08/19/2018 | RADIO | 没有评论

Ref: https://hampager.de/dokuwiki/doku.php?id=mmdvm

MMDVM, MMDVM_HS_HAT, MMDVM_DUAL_HAT with Pi-Star (Pi*)

What do I need?

Hardware

  • MMDVM
  • MMDVM_HS_Hat
  • MMDVM_DUAL_HAT

with Firmware >= 1.4.1

Software

PiStar >= 3.4.16 or MMDVM-Host Version ???

Which Pagers can be used

How to set up Pi* for PROCSAC (DAPNET) with MMDVM_HS_HAT or MMDVM_DUAL_HAT

Already have a working installation of Pi-Star (Pi*)?

Yes, I have already a running Pi-Star:

Update and Upgrade Pi*’s base system services and packages

  • Login to your Pi* Installation via SSH using Terminal,cmd-Promt or putty (Standard is „ssh pi-star@pi-star“ (you can miss the :22 at the end, because it is the standard port)
ssh pi-star@pi-star [Enter]

Now you will be asked for the Password – Standard-Password is „raspberry“ without „“ or take the password you have changed in Pi-Star Dashboard.

You will see the Welcome Message in ASCII-Signs

Now you have to Enter the following commands:

1. PI* uses a write protection so the command to unlock the filesystem for editing is:

rpi-rw [Enter]

2. Now get the latest Version of Pi* and all needed software components:

sudo pistar-update [Enter]

3. Upgrade the Pi* Installation to the next following Version:

sudo pistar-upgrade [Enter]

Repeat the last command (sudo pistar-upgrade) till you get a message „you have installed the latest Version of Pi* – No update needed“ or a similar message.

It is not possible to directly Upgrade to the newest Version! So you have to repeat the pistar-upgrade several times.

For example: You have installed Pi* Version 3.4.13 and want to get onto Version 3.4.16

You have to use the command „sudo pistar-upgrade“ 3 times to get from 3.4.13 to 3.4.14, than from 3.4.14 to 3.4.15 and 3rd time to get from 3.4.15 to 3.4.16.

The last output in terminal should be:

    You are already running the latest version…
    Sleeping a few seconds before making the disk Read-Only…
    Finished

Upgrade the firmware of your MMDVM-Hardware

for Upgrading MMDVM_HS_Hat board conected to GPIO you have to enter the command:

sudo pistar-mmdvmhshatflash hs_hat [Enter]

for upgrading the original MMDVM-HS_DUAL_HAT board (made by Andy, Florian (DF2ET) and DB9HAT) conected to GPIO you have to enter the command:

sudo pistar-mmdvmhshatflash hs_dual_hat

If you get a message that the flashing process was successfull, the hardest part is done. If not, repeat flashing or ask for help in the „MMDVM-BM“ or „DAPNET User“ Telegram-Messenger Groups.

Do a restart now with

sudo reboot now [Enter]

Configure Pi-Star and enable DAPNET

If not already done you should register on https://www.hampager.de and than Register a New Transmitter.

You will get a „DAPNET AuthKey“ by email if your ticket is arranged by a Team-Member.

Now it`s time to Login into the Pi*-Dashboard!

On a Windows, Mac, or Linux-based computer (not the hotspot itself) that has WiFi enabled, open a browser window and navigate to (trailing slash needed):

  Windows: http://pi-star/
  macOS, iOS, etc.: http://pi-star.local/
  On some mobile devices, the url won't work. In that case, try the Auto AP IP address: 192.168.50.1

Go to Admin Area and hit „Apply Changes“ somewhere, like if you would save any changes – even if you did not change anything. This will reload the page and force Pi* to reload store and reload the Configuration. During this process all missing or by update added sections will be loaded and shown correctly.

Now you should still see the Configuration view and in the „MMDVMHost Configuration“ section, switch on „PROCSAC“ and then click „apply changes“.

The Page will reload – now search for the „POCSAG Configuration“ section and fill out the needed values:

  • Node Callsign POCSAG – Enter the POCSAG node callsign.
  • Radio Frequency POCSAG – Enter the POCSAG radio frequency. Per Andy Taylor in the Pi-Star User Forum : „If we get good buy in from repeater keepers, we could have a really good paging network with great coverage, especially if we all use the same standard frequency.“ In Germany, where are already a lot of repeaters we use 439.987.500MHz, which will be the deafault entry in Pi*!
  • DAPNET AuthKey – Enter your authorization key for the Decentralized Amateur Paging Network. Which you got by Mail after you registered a New Transmitter as I told you on the Beginning of Configure Pi-Star and enable DAPNET

No Pi-Star installed yet:

Please google for a Pi-Star installation guide. A nice one is written by KE0FHS on https://www.toshen.com/ke0fhs/pi-star.htm or visit the main website of the PI-Star-Project under https://www.pistar.uk/

73, DO6DAD

Apple HomePod first look & problem

03/07/2018 | GUIDE | 没有评论

As a chinese user, I ordered an Apple HomePod via Apple officially website. After three weeks, I got my HomePod. There are some problems for using of HomePod in China.

I try servery times on this thing with my Chinese (region) account. It couldn’t work. Always noticed me the error 301009. Right after, I connected with my American (region) account. The Error 301014. I check my itunes ID and change the pay method to Paypal. It works immediately.

I have all my apply music and iCloud subscription on my Chinese account. My solution is to switch to Chinese Account after using the US account finishing the initialization.

Another solution for Error 301014. DO NOT select “Enable Personal Requests” (this is off by default so do not toggle it on)

 

Testing points on a Raspberry Pi

02/06/2018 | RADIO | 没有评论

Below is a list of test points which can be found on Raspberry Pi 2, 3 and some are also on b+.

With the use of a multimeter, these test points can help with troubleshooting hardware issues.

I have yet to find any formal documentation about these test points. However, I do know they exist.

PP3 GND
PP4 GND
PP5 GND
PP6 GND
PP7 5V after polyfuse
PP8 3V3
PP9 1V8
PP10 Goes from 3V3 to 2V on brownout
PP11 DAC_2V5 (for composite video DAC)
PP12 AUD_2V5 (for PWM audio drivers)
PP13 Goes from 3V3 to 2V on ACT activity
PP14 SD_CLK
PP15 SD_CMD
PP16 SD_DAT0
PP17 SD_DAT1
PP18 SD_DAT2
PP19 SD_DAT13
PP20 H5V
PP21 RUN signal (reset)
PP22 Goes from 3V3 to 2V on activity of green (link) ethernet jack LED
PP23 Goes from 3V3 to 2V on activity of yellow (speed) ethernet jack LED
PP24 COMPVID
PP25 AUDIO_L
PP26 AUDI_R
PP27 VBUS (USB 5V power)
PP28 ETH_CLK (25.000 MHz)
PP29 VC_TMS
PP30 VC_TRST_N
PP31 VC_CLK
PP32 VC_TDI
PP33 VC_TDO
PP34 GND
PP35 GPIO6 of LAN9514
PP36 GPIO7 of LAN9514
PP37 CAM_GPIO0
PP38 CAM_GPIO1
PP39 SCL0
PP40 SDA0

Below is an example of how you can use PP9 to confirm that the regulator is supplying 1.8v correctly.

Ground can be sourced from the SD card slot

And the exact location of PP9;

Adafruit has some great information covering the Raspberry Pi power circuitry. link

How to shut down Cortana in Windows 10

01/31/2018 | GUIDE | 没有评论

To shut down Cortana in Windows 10 Pro simply type gpedit.msc in the search box to open the Group Policy Editor. Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Search. Double-click the policy named Allow Cortana.

You can kill Cortana easily in Windows 10 Pro via the Group Policy Editor.

When the policy window appears just click Disable. You’re done!


Here’s where you disable her; feels a bit like killing the Terminator.
If you’re using Windows 10 Home, you’ll need to edit the registry. Do not tackle this step unless you have experience editing the registry. Additionally, you should set a restore point now in case things go sideways. To do that just follow these tips.

It bears repeating: This is dangerous. That said, here’s what you do. Type Regedit into the search box in Windows, and open the Registry Editor. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search.

Here’s where it gets tricky: That final key (Windows Search) might not be present, as it wasn’t on my machine. In that case you’ll need to right-click the Windows directory and select New > Key. Name it Windows Search.

The key Windows Search wasn’t present on our machine, so we had to create it (we did this after for this screenshot).
Now select that new key. In the righthand pane, right-click and select new DWORD and name it AllowCortana. Then right-click that value and make sure it’s set to 0.

allowcortana
Once you’ve created this DWORD value just set it to “0,” which translates to “off.”
Sign out, sign back in and you should notice that Cortana has been replaced with a generic search box—woohoo!

One final note: After all this is done, it’s possible that you’ll look in the Task Manager and find Cortana still sitting there, mocking you. Travis told me he was able to kill the process. When I tried it myself it was not only difficult, but once I did I wasn’t able to search at all on my PC, for anything. Clearly Cortana is a tough cookie. She only consumes 39MB, so consider whether she’s more trouble to kill than she’s worth.