Had to run the compiler in a XP VM, but it really was that simple. My sound
card now has its original ID again and it's working with HT's drivers.
-Connor
On Fri, Jan 23, 2015 at 2:06 AM, Connor Ness <connor...@gmail.com> wrote:
> Hello,
>
> I recently used the existing utility located at
>
> http://www.alsa-project.org/main/index.php/Xonar_EEPROM_Failure
>
> to change the hardware ID on my HT Omega Claro II to spoof Asus' Xonar
> drivers into believing I had a D1 to test certain features included in
> their software, but not HT Omega's. It worked, but now I wish to return the
> card to its original ID and back to the original drivers.
>
> However, the device ID for the Claro II is not listed in the menu. I
> noticed this when I first ran the utility, but I went ahead anyway,
> planning to figure out how to revert back later. I did have the forethought
> to grab the original device ID though, so my question is this:
>
> Would adding support for the Claro II to the restoree.exe be as
> straightforward as adding
>
> { 0x7284, 0x9787, "HT-Omega Claro II" },
>
> to the source restoree.c and recompiling?
>
> Thank you for your time
>
> -Connor
>
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user