..:: PCSX2 Forums ::..

Full Version: DEV9ghzdrk-- deprecated dependency
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I just installed the latest dev build of PCSX2 on a new WinX machine and while resolving an issue completely new to me (error 126: the specified module could not be found) as I had installed Wireshark on my main machine for a computer course, WinPcap came included.

I went to the website https://www.winpcap.org/install/default.htm to install the library and found that the project has ceased development and they were directing people to use the Npcap library instead. https://nmap.org/npcap/

I installed the WinPcap library, checking if there any issues with later WinX OS versions and it resulted in these registry errors I haven't ever seen before on loading the plugin:
Quote:Error opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\Configuration\ComponentIdError opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\PropertiesError opening registry key: SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\Descriptions\Connection

Available TAP-WIN32 adapters [name, GUID]:

I uninstalled it and installed the new Npcap library, having to use the Install Npcap in WinPcap API-compatible Mode for the DEV9ghzdrk plugin to work. Hopefully this mode doesn't allow for the DLL hijack shenanigans that were ripe with NSIS prior to v3 (Jul 2016)--
WinPcap 4.1.3 (last version) was released March 2013. While this workaround works for now, Nmap.org may remove that legacy option in the future, so rewriting the plugin to work with Npcap natively may be something to consider for the next (1.8) milestone.
Maybe you can contact lowlyocean, he's the only one updating the DEV9ghzdrk plugin lately.
Thanks for the tip. I didn't know the best person to contact despite searching both the forum and the git. That said, he doesn't have an account here, and there is not a way to directly contact another person in github. What would you say is the best way to proceed? Post the issue to his fork of the PCSX2 git?
Quote:Post the issue to his fork of the PCSX2 git?
I'd go with that.
Unfortunately he doesn't have an issue tracker up on his fork of the PCSX2 git, so that's out. My next idea is to post an issue to the main but include a @ mention/shoutout for him to make sure he's notified.

github link: https://github.com/PCSX2/pcsx2/issues/2846