Microsoft Habu says dead after cold boot

[Anarion]

My mouse stays dead when I do cold boot. I always have to replug my mouse
after cold boot, is there any new firmware to fix this problem? My
motherboard is ASUS P5B and operating system is Vista Business 32bit (same
thing in XP). I have tried all kinds of settings in BIOS but no go. This is
really annoying and I doubt that it will do any good for my motherboards usb
sockets.
I have newest drivers and firmware (from Razer) but it has not helped
anything. I can't even find proper support for this damned product! Does
anyone know what will fix this or when Microsoft/Razer releases new firmware
or software that solves this problem? I really need help in this one, thanks.

[Jason Tsang]

Have you tried upgrading your motherboard's bios?
Sometimes, they will silently release fixes in motherboard bios revisions.

--
Jason Tsang - Microsoft MVP

Read my blog for the latest in Media Center topics
(and other topics that interest me)
http://jtsang.blogspot.com

More information by me
http://jtsang.mvps.org
http://www.classicsunveiled.com

Find out about the MS MVP Program -
http://mvp.support.microsoft.com/default.aspx

"Anarion" <Ana...@discussions.microsoft.com> wrote in message
news:E5D0C6C5-EC77-499A...@microsoft.com...

[Anarion]

"Jason Tsang" wrote:

I have. I will always upgrade BIOS if my system does not work as it should
or if I have problems with hardware.

[Roger Khoury]

I have a Habu mouse on Vista Business. I found that I had to update the
firmware a second time after the original install -- it may appear updated,
but still not programmed correctly. Do this from the file "update.exe" in
English > Habu 2.10 -- then unplug and reconnect the mouse.

The Habu config window should show Driver version 2.10 and Firmware version
2.01

Check the Device Manager and verify that there is a Habu entry under Human
Interface Devices.

And support is available from MS for 90 days after purchase. Call:
1-866-833-77088

In the Habu config window you should

"Anarion" <Ana...@discussions.microsoft.com> wrote in message
news:E5D0C6C5-EC77-499A...@microsoft.com...

[Rollin' Rog]

Sorry, that support number should have been:

1-866-833-7088

"Roger Khoury" <rog...@yahoo.com> wrote in message
news:85B2E8C0-51C4-4CB5...@microsoft.com...

[Anarion]

I bought this at November... But I tried updating firmware again but it still
does same thing. It does not recognize any mouse/Human
Interface Devices at device manager when this thing occurs. There's only
Freescale USB JW32 ICP Device (and all other usb devices I have) under
Universal Serial Bus controllers thing. But when I replug my mouse it
disappear and USB Composite device replaces it (if it was not there already).
Is it normal that there is two entries, Habu mouse and USB Human Interface
Device, under Human Interface Devices?

[Rollin' Rog]

Yes there should be multiple HID entries in the Device Manager. This key
supports other devices as well -- such as keyboards.

I don't believe the firmware is updating correctly.

Are you installing the Vista drivers from this page>

http://www.razersupport.com/index.php?_m=downloads&_a=viewdownload&downloaditemid=63&nav=0,7

On the page above there are two downloads. You can ignore the first:
http://www.razerzone.com/drivers/Habu/English_Habu(2.10)D.zip

This contains only the driver software, not the firmware.

The one you want is:

http://www.razerzone.com/drivers/Habu/English_Habu(2.10).zip

This contains both the software and firmware folders.

You want to follow the instructions on the page after you have that.

A clean firmware install produces a device detection error and requires a
trip through the Device Manager -- per their directions. My mouse did not
work correctly even after this. A second install of the firmware (file
"update.exe") was necessary. This produced no error. Only then did it begin
working. Prior to that I had a "no mouse detected" error every time I tried
to make a configuration change through the Habu Config window.

I believe I only saw this in the Device Manager under "other devices" during
the original, error interrupted install:

Freescale USB JW32 ICP Device

It was this device that then had to be installed using the update driver
menu in the Device Manager by pointing the install routine back to the
firmware folder.

"Anarion" <Ana...@discussions.microsoft.com> wrote in message

news:37D7FE9F-C0B6-473A...@microsoft.com...

[Anarion]

Hmmm... My mouse is recognized by Habu config software correctly (it shows
firmware 2.01). Mouse works but I have to plug it out and then back after
every system power on so it would stay dead if I do not first plug it out and
then put it back. It does not do this if I do restart.

[Rollin' Rog]

Is the port you have it plugged into, the same one from which the drivers
and firmware were originally installed?

I'd still try running the update.exe file again, then disconnect and
reconnect to the same port.

If no luck, remove the drivers and start clean from another port.
You may have some USB detection issues which are hard to resolve here.

You may need a USB hotfix:
http://support.microsoft.com/kb/933442/en-us >
http://thehotfixshare.net/download/index.php?dir=Language%20Neutral/Vista/ >
http://thehotfixshare.net/download/index.php?dir=Language%20Neutral/Vista/&file=Windows6.0-KB933442-x86.msu

http://support.microsoft.com/kb/925528/en-us

You can also try that support number. I don't know how they determine when
the 90 day period begins. I had to call it originally; the first person you
talk to asks you to read the product id from the bottom of the mouse and
tells you whether you qualify. If you do, you are handed off to a second
person who will want to remote connect to your system.

"Anarion" <Ana...@discussions.microsoft.com> wrote in message

news:F24E39F6-D3D2-44AC...@microsoft.com...

[Rollin' Rog]

I would also open up the BIOS/CMOS setup interface and confirm that all USB
options are enabled there. The "cold boot" issue makes it seem as if
something is amiss there and data is not being preserved on shutdown. You
can try reloading the setup defaults if you want.

"Rollin' Rog" <rog...@hotmail.com> wrote in message
news:O9z9ZdOi...@TK2MSFTNGP05.phx.gbl...

[Anarion]

I have tested every setting under usb configuration at BIOS and it will do
the same thing.

[Rollin' Rog]

Well, given this statement: "It does not recognize any mouse/Human
Interface Devices at device manager when this thing occurs." -- It does not
sound like this is a "Habu" mouse problem particularly, but somthing amiss
with the Vista USB device detection itself. If you run services.msc is the
Plug and Play service there set to "automatic" and started?

You can try the "hotfixes"; I don't think they can hurt. If one should cause
further problems you should be able to remove it from Add/Remove programs.
And always good to ensure a System Restore point is set before installing
any.

There is also a procedure for removing and reinstalling the entire USB
device tree, including "hidden" devices. I don't know whether that would
help you.

The directions here were written for XP but I believe they apply equally
well to Vista:
USB CLEANUP

First set a System Restore point and test it: start > run: msconfig >
Launch System Restore.

The standard approach to these problems is to remove all the USB devices in
the Device Manager and let Windows reinstall them. But there is a special
technique to it.

I am uploading a registry patch you will need to download, unzip and run.
Confirm the merge to the registry.

http://forums.techguy.org/attachments/100544d1173412107/usbghosts.zip

It is the patch described in JohnWill's note here:

http://forums.techguy.org/hardware/449735-usb-problem.html#post3435808

Once you have installed the patch, follow the rest of his instructions.

Note: in some cases Windows does not have the proper install path for the
information files required. If the New Hardware Wizard prompts you for an
install location, point it to:

c:\windows\INF

This is a hidden directory, so you will need to have "show Hidden Files"
enabled in Folder Options > View to see it.

"Anarion" <Ana...@discussions.microsoft.com> wrote in message

news:558E068C-272D-4881...@microsoft.com...

[Anarion]

Hmm... Human Interface Device Access was set to manual but plug and play was
automatic. I will change that immediately.

"Rollin' Rog" wrote:

> Also
>
> Run services.msc and verify that the Human Interface Device Access and Plug
> and Play services are set to Automatic startup and started

>
> "Anarion" <Ana...@discussions.microsoft.com> wrote in message

> news:558E068C-272D-4881...@microsoft.com...

[Anarion]

One more thing that might be interesting. Sometimes, maybe once a every 14
day, it works without pluggin it out. When this happens mouse will stay lit
after BIOS identifies all devices. Normally my mouse only flashes and no
led/light will remain on. If this happens (and this is usually the case) it
will only recognize that Freescale this only. This happened in Windows XP Pro
too. Any other device works (for example I am able to boot with my USB
stick) so I think that this mouse does not like my motherboard and how it
handles devices that are some sort of "hybrid mouse keyboards".

[Anarion]

I changed it to automatic but it didn't help. This problem only happens with
this mouse and only with this mouse. All other usb devices mouses that I have
are recognized correctly. If my mouse does not stay lit after POST it will
not work unless I replug it.

[Rollin' Rog]

Do I understand correctly that this "Business" edition of Vista is part of a
dual boot or was not the original installed operating system?.

I do recall that on my Dell XP machine, when I first installed the Razer
mouse I chose a USB port other than the one Dell assigned to the previous
mouse. The Razer was not recognized. Only when I switched to the actual
"mouse" port did it get recognized. Does your system have an original
"mouse" port?

Anyway, the only thing I can think of here is that you have a resource issue
with the USB mouse detection once Windows begins assigning resources. This
can be caused by so-called "ghost" USB entries. These are devices that were
recognized at one time, resources were allocated for them, but they are no
longer perceived as connected.

This is what the "cleanup" drill is designed for. Other than that I'm afraid
I'm out of ideas. I can't even tell you for sure whether it's a "Windows"
problem, or one with the motherboard/BIOS.

"Anarion" <Ana...@discussions.microsoft.com> wrote in message

news:3FB8D9F3-07E1-4885...@microsoft.com...

[Anarion]

I had XP Pro installed and same problem but now I had only Vista Business
installed (no dual boot). You can not switch USB port for your mouse after
installing Razers drivers because Habu CP does not recognize it, if you
change USB port for your mouse you have to reinstall CP. And when I mean not
recognized I mean that my mouse doe not work at all, no light or anything. If
it stays lit after BIOS POST it will work but that happens maybe 1-2 times
per every 14 days. I think that my motherboards BIOS does not recognize this
mouse correctly (exactly the same problem as described here:
http://www.razersupport.com/index.php?_m=downloads&_a=viewdownload&downloaditemid=31
) I wonder if that profile button thing works for Habu also?

[Rollin' Rog]

There is another Habu thread in this group regarding possible damage to the
mouse cord. Any chance that could be an issue?

I have both the Razer Copperhead and the Habu. I do see that the
Copperhead's cord is thinner than the Habu -- so I don't know why it should
be an ongoing problem.

I understand the issue with switching ports -- but if the computer had a
designated mouse port to begin with, it might be worthwhile to clean install
the Habu to that port. If not, I'm sure it would make no difference.

"Anarion" <Ana...@discussions.microsoft.com> wrote in message

news:063D2CB3-A3C9-4C4E...@microsoft.com...

[Anarion]

I don't think that it is a cable problem because I have had this issue since
the very day I bought this mouse. I am beginning to think that there is no
solution for this problem apart from firmware update for my mouse or BIOS
update that would fix this. But since Razer products are known to have cold
boot problems I think that I can blame Razers poor software engineers for
this problem.

[Funkifeva]

I have the same issue. Firmware is updated properly for the mouse yet after
a reboot it does not detect the device until it is unplugged and replugged
back into the usb port. VERY annoying. Works fine once that procedure is
performed.

[aaron...@gmail.com]

I've been having the same issue over some Razer mouses altogether not just Habu. I've tried the Razer Copperhead, Deathadder and now Habu. All 3 have had cold boot issues on both my Windows 7 32b and 64b(now primarily). Drivers firmwares, all updated and played around with for days at one stage. Been thru heaps of forums and the advice had mostly been the same. Update firmware... well for my scenario, I ended up wasting a couple of hundreds on mouses when spending $15 on a generic optical mouse has saved me plenty of headaches.
Its bad enough that the computer can rarely crash, but its worse of a pain when you gotta replug your damn mouse everytime you boot and especially when you've set up your station neatly with cables and stuff all tucked behind. My Habu was using driver ver 2.21 and firmware ver 2.03 at the last time I used it.

[Aaron]

Edit: I remember a trick to deal with these mices. Move the mice around and click its buttons between booting up and login screen during its USB Detection round. Usually successful in booting up and detecting the mouse but it will usually reset back to its default settings. Again just as annoying to do especially since you've set it the way you want but up to you.