DMA Convert

The software ships no adapter of its own for any brand — it loads the leechcore.dll supplied by the vendor of the card you own (not a system driver: it's the library the software uses to read and write through that card). To convert to a different device, or when the vendor ships an updated file, just drop the files in the right place. No client reinstall needed.

Pick one of two placements:

Method	Scope	Best for
Method 1	All apps	One card, configured once
Method 2	A single app	Different cards for different apps

If the same file name exists in both places, the copy in the app folder wins — Windows searches the program's own directory first when loading a DLL.

Method 1 — global

1. Open the install folder configured in the client settings (default C:\HOOZi).
2. Copy the vendor's leechcore.dll (and any companion files) there, overwriting the existing ones.

Method 2 — per app

1. On the app's page in the client, click the gear icon in the upper right → Open app folder.

2. Copy the vendor's leechcore.dll (and any companion files) into that folder.

The device asks for a license key

Current builds have no key input box. Almost all devices can read the key from their own config file instead — keep that file next to leechcore.dll:

• HOOZi devices: the config file is winusb.txt, placed in the install folder (default C:\HOOZi)
• Other brands: the file name is whatever your vendor documents — ask whoever sold you the device if you are unsure

A few devices want the config file in the app folder

Some AS converters, for example: leechcore.dll still goes to the install folder per Method 1, but their leechcore.ini must sit in the app folder (open it as described in Method 2, step 1).

The vendor only shipped a winusb.dll

DMA conversion through winusb.dll is not supported — only leechcore.dll is.

You can try renaming winusb.dll to leechcore.dll and placing it as described above. Not every brand works this way — if it still fails after renaming, that device is simply not supported for now. Known to hit this:

• UrsaMinor — renaming does not work for it, but we wrote a dedicated adapter for it; see below

A dedicated adapter for UrsaMinor

Download both files below and put them in the same folder (the install folder per Method 1, or the app folder per Method 2). For winusb.txt, pick whether memory writes are allowed before downloading:

File	What it is	Download
leechcore.dll	The adapter itself — overwrite the existing file	Download · 11.4 MB
winusb.txt	Config file — same folder as the dll	Memory writes (AllowW=1)Read-only (AllowW=0)

Delete UrsaMinor's own winusb.dll first

The stock winusb.dll that came with UrsaMinor must not stay in the same folder — remove it before dropping these two files in. If you'd rather keep a copy, rename it (e.g. winusb.dll.bak); just don't leave it there under its original name.

Use the downloaded winusb.txt, don't retype it

Leave IP empty and keep Mode as UrsaMinor (including the space after Mode=) — neither should be changed. If a feature that needs memory writes does nothing, check that the file says AllowW=1.

"UDP discovery failed — is the driver loaded?"

If the log shows these two lines (the adapter prints them in Chinese):

INFO   [urs] 准备连接 UrsaMinor (host=<broadcast>)
ERROR  [urs] UDP 发现失败，驱动是否加载？

the adapter could not find your card — most likely a UrsaMinor driver variant we haven't covered yet.

When that happens, open a ticket at hoozi.cc/me/tickets and include a remote-assistance method for your PC (ToDesk or UU Remote — device code plus the one-time password). We'll connect, look at what that card actually reports, and add support for the variant.

Still not working after the convert

Check in this order:

1. Right folder? Method 1 means the install folder set in the client settings, not any folder named HOOZi you happen to find. For Method 2, always open the folder through the gear menu rather than navigating from memory.
2. Did the copy actually overwrite? Check the modified date on leechcore.dll in the target folder — it should be the moment you pasted.
3. Broke right after an update? Go back to the Method 1 folder and check whether leechcore.dll was restored to the official build; if so, just redo the convert.
4. Config file in the right place? See the two sections above.

If it still fails, contact support with the full error text and the brand / model of your device.