detecting BCDC .401 in DC emu
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

detecting BCDC .401 in DC emu

Started by exlepra, 18 June, 2004, 17:56:16

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

exlepra

Hi, I am looking for a hubside script for detecting bcdc .401 when its in dc++ emulation mode, and when there are no things like [384K/64K]:[3 sl]  in description.

And a fake tag detecting (hubcount and slot) would be nice too.

DC++k cdm, and DCDM++ does not detect them yet

PtokaX DC Hub 0.3.3.0 build 15.25


thx


NotRabidWombat

I don't think you can detect them. BCDC++ is built off of the DC++ source, so I can't imagine it's hard to perfectly emulate the PK string that typically gives the fakers away.

There is no way to detect fake hubcount in the tag. There should be some scripts to detect fake slots with a search response.

-NotRabidWombat


I like childish behavior. Maybe this post will be deleted next.

exlepra

the B:  appears in the tag only when the emulation is set to bcdc, if it is set to dc++ then its hidden.

SMF spam blocked by CleanTalk