Here’s a question for my Amateur Radio friends out there:
How important are RF power considerations when operating mobile HF?
Here’s why I’m asking: I’m looking into HF, and mobile HF is going to be an option I explore. My owners manual (see below) says to keep the power below 10 watts for CB (29 MHz). I currently operate VHF up to
50 watts with no issues, but I know 2 meter and 10/11 meter are well different.
I’ve heard second- and third-hand stories of people killing their ECMs from high power output, so that’s why I’m throwing the question out. I’m not keen on making my VW into a 5-figure paperweight, and I’m okay with keeping it under 10 watts, but I want to know your thoughts and opinions. Note: I’m looking for information strictly related to the possible effect on the vehicle electronics, not human RF exposure. That’s a different topic entirely.
My intention is to connect the radio’s power supply directly to the vehicle battery (both positive and negative), and use a mount that provides electrical grounding of the antenna as well.
Here’s the page from my owners manual:
So let me know your thoughts and opinions below. Post your call only if you’re comfortable doing so. Please let me know your thoughts, what bands you operate mobile on, what power levels, and what (if any) your installation considerations are.
Storage Spaces driver.
Symptoms of this issue:
- Hard drive activity light solid on
- Occasional disk hangs
- Event ID 129 in Windows logs storahci “Reset to device, \Device\RaidPort0, was issued.”
- Go to Power Options > Advanced > PCI Express > Link State Power Management and set it to Off.
- Reboot the server
Fully resolved the issue for me.
There are two ways to fix this, and I found I had to do both steps to make it work.
1) Open Internet Explorer. Go to Tools > Internet Options > Advanced > Reset and reset all settings. Try the update again.
2) Open an administrator-level command prompt, and run the following:
FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-*9.*.mum /c "cmd /c echo Uninstalling package @fname && start /w pkgmgr /up:@fname /norestart"
gpart create -s gpt adaX
gpart add -t freebsd-ufs adaX
Also reference this post for more info:
Miklor has an excellent tutorial which explains the situation with counterfeit Prolific cables, and how to get the correct driver installed and working.
In short, it’s simply a matter of installing the correct cable driver (the older Prolific driver), plugging in the cable, and then choosing the correct driver in Device Manager. In Linux, the cables seem to work fine with no issues.
There are a couple of additional things to keep in mind:
1) After installing the working driver, make sure you continue to plug the cable into that same USB port. Plugging it in to a different port will cause the Windows driver to reload. If you do, just update it with the working driver again.
2) Windows Update may offer an update to your “outdated” Prolific driver. Just block or hide this update.
3) If you plug the Prolific cable into your radio with the wrong driver installed, the LED will turn red. You ARE transmitting a carrier. Keep that in mind. Make sure your radio is tuned to an in-band, unused frequency before plugging the cable into your radio if you’re not sure of the driver situation, or just check Device Manager, as the wrong driver will show a yellow exclamation mark.
Here’s a photo of the led gone red from the wrong drivers installed:
Have anything else to add to this? Please feel free to leave a comment below. Thank you!
However, the radio exhibits some really strange display issues when you tune above 499Mhz. Take a look at the two videos below for a demonstration.
It’s also worth noting that the UV-B6 antenna that mine came with was only indicated for use up to 480Mhz. Yours may be the same.
If you have anything to share about this, please do so in the comments section below. Thank you!
- Server: smtp-mail.outlook.com
- Port: 587
- Encryption: TLS
- Server: imap-mail.outlook.com
- Port: 993
- Encryption: STARTTLS
- Server: m.hotmail.com
- Use SSL: Yes
It seems that Fallout 3 does not handle being run on a processor with more than 2 cores, which leads to random freezing.
Fix: Edit the fallout.ini file in “C:Users(your name)DocumentsMy GamesFallout 3″ (Windows 7 and above)
[General] section, locate the
bUseThreadedAI=0 line and change it to
Below that, add
Save the file and restart Fallout 3.
Note that if you’re having issues where Fallout crashes after starting a new game, it’s most likely due to incompatible video hardware, most notably trying to run it with Intel-based graphics.
Skype for OpenSUSE (download link) may have no audio and frequently crash. This issue is caused by missing packages for the audio subsystem.
Solution: install the packages alsa-plugins-pulse-32bit and pavucontrol
sudo zypper in alsa-plugins-pulse-32bit pavucontrol
Please feel free to leave any feedback in the comments section below.
During some tests of Ubuntu in a virtual machine, I ran across an issue I’ve seen before, but never been able to fix, until now.
If you have a RAID array that contains a swap partition, you will not be able to delete it in the Ubuntu installer. Here’s the situation:
And if you try to delete the RAID array (“delete MD device”), here’s the error message:
An educated guess at the problem would be that the swap is in use, and as such, not able to be deleted. You’re right, but it’s (almost) not that simple. But let’s hit CTRL-ALT-F2 to get a console open, and try to turn off swap:
Yet it still won’t delete.
Okay, let’s try to force-stop the MD array. First, let’s find out for sure which MD devices there are. Doing this:
ls -l /dev/md
linux:0 -> ../md127
So we know the device is md127. Let’s try to force-stop it now:
mdadm --stop --force /dev/md127
Gives this message:
mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process, mounted filesystem or active volume group?
Well, what now?
Note: If you’re jumping back to the installer, don’t do an mdadm –stop /dev/md127. That’s going to confuse the installer. Just swapoff and then return to the installer and delete the software raid.