Advertisements

Posts Tagged Windows

WiFi not working on Asus T100TA

Today I ran into an issue with my Asus Transformer T100 where the Wi-Fi would not work under Windows 10 and going into Device Manager showed an issue with the Broadcom Serial Bus Driver over UART Bus Enumerator. Opening that shows “This device cannot start. (Code 10)” and the following message:

{Drive not Ready} The drive is not ready for use; its door may be open. Please check drive %hs and make sure that a disk is inserted and that the drive door is closed.

The first thing you will want to do to try to resolve this is to go into the BIOS by shutting the tablet down and then holding volume down + power to boot up into the BIOS. Once there, find “Network Stack” and set it to “Enabled” if it is not already. Save changes and exit.

If this does not resolve your issue, use a working system to download the drivers from Asus’ website and then transfer them to the Asus using a USB stick so you can reinstall the drivers. Optionally, you can use a USB-to-Ethernet adapter to get yourself back on the network and update the drivers.

At this point you should have resolved this. If not, go back and start over to ensure you followed the previous steps correctly. If it’s still not working, you should either restore to a previously-working restore point or reset/reinstall Windows. If that doesn’t help, you may have a hardware issue, so reach out to Asus for further support.

Advertisements

,

Leave a comment

Counterfeit radio programming cables and Windows 10

If you have purchased a cheap programming cable for your radio from Amazon, eBay, or another dealer, you’ve probably run into an issue where the cable initially won’t work, and someone (perhaps the vendor) told you that you have to use an older driver to get it to work. What you have is a cable that uses a counterfeit chipset. The Prolific chips seem to be the most problematic, while FTDI chipsets work very well. This page on miklor.com offers some background information on this subject.

The Miklor Cables & Drivers page talks about this and offers the older Prolific drivers that work well with cables that feature those counterfeit Prolific chipsets. You will run into one of two problems while dealing with them, however.

Under Windows 8 and previous Windows versions, Windows will offer the newer, non-working driver through Windows update. It is sufficient to go in and block the update, as described here, but you may have to do that each time you plug the cable in to a different USB port.

Under Windows 10, it’s a whole different situation. Windows 10 will install all updates offered through Windows Update, and you have the option to defer upgrades, but not to block individual updates. Windows 10 will continue to install the updated driver, which will continue to cause your counterfeit chipset cable to stop functioning.

So, if you’re using the counterfeit chipset cable under Windows 10, do yourself a favor and get a genuine programming cable. You’ll save yourself a lot of headaches and frustration.

A good source for programming software and cables is RT Systems, as they offer both cables and software for radios they support. If you’re only interested in the cable, and you want to use it with the factory software or the open-source software Chirp, look for cables that mention using genuine FTDI chipsets. They aren’t hard to find, but they will cost a little more. For the Baofeng 2-pin models, this cable from Amazon works well. This cable should work for all Baofeng 2-pin cable compatible radios, such as the UV-5R (and variants), the BF-F8+ (and variants), UV-B5 and UB-B6, and UV-82 (and variants). This should also work for all 2-pin cable compatible radios from other manufacturers, as long as they use the same pin out.

You could also try replacing the chipset with a $3 adapter, as described here. A good eBay seller for that adapter is here. Many other people report success. but I tried it with a counterfeit cable for my Baofeng and couldn’t get it to work.

Questions and comments are welcome below.

, , , , , , ,

Leave a comment

Event ID 129 on Windows Server 2012 on HP MicroServer N40L

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.”

Fix:

  • Go to Power Options > Advanced > PCI Express > Link State Power Management and set it to Off.
  • Reboot the server

Source: Event ID 129 – storachi – Reset to device, \Device\RaidPort0, was issued. (blogs.technet.com)

Fully resolved the issue for me.

 

, , , ,

Leave a comment

Installation of IE9 via Windows Update fails with 0x80092004

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.

Source: Installation of IE 9 fails with error code 80092004 (answers.microsoft.com)

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"

Source: How to install ie9 (Internet Explorer 9) on Windows 7 despite 80092004 error (stackoverflow.com)

 

, ,

Leave a comment

Windows 7 USB DVD Download Tool fails on UEFI-boot systems

If your system is set to EFI/UEFI boot, and you try to use the Windows 7 USB/DVD download tool to make a Windows 7 bootable USB stick, it will fail with the following error:

win7_usb_fail

Files copied successfully. However, we were unable to run bootsect to make the USB device bootable. If you need assistance with bootsect, please click the “Online Help” link above for more information.

The reason? Well, I found this post that had instructions on running bootsect.exe manually. I did that, I received this message:

bootsect_efi

This tool can only be run on systems booted using a PC/AT BIOS. This system was booted using EFI or some other firmware type.

So UEFI booting is why the USB creation fails.

Anyone have any suggestions on a workaround for this?

,

2 Comments

Windows 8 x86 no network connection on VMware Workstation 9

On creating a Windows 8 virtual machine in VMware Workstation 9, the virtual machine will not be able to access the network.

If you go into device manager, the network adapter will be listed with no drivers installed.

To remedy this, edit the .vmx file, and add the following line:


ethernet0.virtualDev = "e1000e"

This solution is from VMware communities – Windows 8 RC internet connection.

,

1 Comment

Screen flickering and horizontal lines when coming out of standby on Windows 8

I upgraded my Dell Latitude E6510 with an Nvidia NVS 3100M  to Windows 8 a short time ago, and noticed something fairly quickly: Whenever my display came back on after being powered off from power saving mode, or the laptop came out of sleep mode, the screen had a very noticeable flickering and some distinct horizontal lines. The best way to explain it was to say that there was something very wrong with the display refresh rate.

The effect would gradually diminish with time, but wouldn’t completely go away. I updated the graphics drivers from the built-in Windows 8 drivers to the latest ODE graphics driver for Windows 8 64-bit (310.90) — that didn’t fix it. I also noticed that putting the display in 40hz mode and then back in 60hz mode didn’t fix it either. I even would have the problem if I shut down completely and powered the laptop back on a few moments later.

I later found this blog post from someone having the exact same issue. He even indicated that he’s had hardware replaced on his notebook, and that didn’t fix the issue. He did, however, find a fix: Dell’s A08 drivers for the NVS 3100M graphics chipset. He posted links to a Dell search for A08 drivers and two drivers that specifically worked:

nVidia Quadro FX 880M – Win7/Vista 32-bit Graphics Driver

nVidia NVS 3100M – Win7/Vista 64-bit Graphics Driver (this is the one I used)

So I uninstalled my existing Nvidia drivers and installed the 64-bit driver linked to above. You know what? It worked. The flickering went away immediately, and it continues to work correctly resuming from standby.

I also recall speaking to someone who had a similar issue, albeit on Windows 7. I’m guessing it was probably related to the drivers as well.

UPDATE: After doing some more testing, I found this: I took a clean install of Windows 8 where the screen flickering was there, reformatted and reinstalled Windows 7 64-bit. After booting into Windows 7, the screen flickering was still there! It would seem that the driver is manipulating the graphics controller to produce this flicker. Installing Dell’s recommended NVS3100M driver for Windows 7 did fix the flickering issue.

Further reading:

Anyone else having the same issue? Have the drivers above worked for you? Please feel free to share your experience in the comments below. 

, , , , ,

6 Comments

Performing a clean install from a Windows 8 upgrade media

If you purchased the Windows 8 upgrade from Windows 7, but would rather do a clean install, here’s a method that I’ve found that has been reported to work.

First, obviously, delete all partitions during the Windows install, supplying your key when requested.

After Windows 8 installs, and if Windows won’t activate, do the following:

Run regedit, and set:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE\MediaBootInstall to 0 (zero)

Open an administrator-level command prompt, and run the following:

slmgr /rearm

Then reboot and run activation again.

, ,

Leave a comment

Windows 8 error code 0x807800C5 during Windows 7 File Recovery backup

The following error appears if you try to include a system image in your backup using the Windows 7 File Recovery backup tool.

0x807800c5

There was a failure in preparing the backup image of one of the volumes in the backup set.

Details: The mounted backup volume is inaccessible. Please retry the operation.

Error code: 0x807800C5

According to this forum

For Win 8 only: The Win 7 back up program included with win 8 does not support backing up a image file to any kind of NAS device (UNIX, Linux) . Internally the program gives an error that the NAS device has an incompatible sector mapping type. You can backup to a hard drive that is attached to a different windows machine and then back up that file to your NAS. Convoluted, but it works.

So, backing up a system image to a Samba share is out of the question. To work around this, disable the creation of a system image in your backup.

I haven’t tried backing up to an NTFS-formatted iSCSI LUN, which might work. If anyone has tried that, I’d be interested to know the results.

, , , , , , , ,

4 Comments

Error code 0x80070544 when attempting to back up Windows 8 onto NAS over Samba

If you use Windows 7 File Recovery to attempt to backup your system to a NAS device, you may receive the following error:

0x80070544: The specified network location cannot be used.

Verify the path points to a correct network location and that the supplied credentials can be used for write access to the folder.

The validation information class requested was invalid. (0x80070544).

The solution to this is rather simple. You have to prefix your username with the name of the machine where the Samba share is located. So, if you are backing up to diskstationbackups, prefix your username with diskstation.

In my case, my username on that device is mike. So instead of using mike as my username, I had to use diskstation\mike.

It works now. Enough said.

, , ,

8 Comments