I opened a thread on the official eMule board titled Batch To Find Ip, Gateway, Ports (useful to find needed data to setup a router), but I cannot edit it, because the forum stops me to add links; this is a security limitation, I think (I could edit that message in the past, I guess they forbid users to add links to old messages because this is used for spam). I'll avoid breaking things here and there by removing links, creating new topics etcetera, so I will leave it as it is there.
Removed old ARZ versions (from 0.7 to 0.13) from "Files": they were in .bat format and that was not enough for the GNU General Public License. Code is still on the code page.
I opened a thread on the official eMule board titled Batch To Find Ip, Gateway, Ports (useful to find needed data to setup a router), but I cannot edit it, because the forum stops me to add links; this is a security limitation, I think (I could to edit that message in the past, I guess they forbid users to add links to old messages because this is used for spam). I'll avoid breaking things here and there by removing links, creating new topics etcetera, so I will leave it as it is there.
search_one_file_through_all_mounted_drives
On Simon Sheppard website, I read that Tab Completion is disabled by default, it has been known to create difficulty when using a batch script to process text files that contain TAB characters So this is a readability versus usability tradeoff.
On Simon Sheppard website, I read that Tab Completion is disabled by default, it has been known to create difficulty when using a batch script to process text files that contain TAB characters So this is a readability versus usability tradeoff.
Ideally, people should just downaload, doubleclick on arz-<version>.zip and doubleclick on arz.bat to run this script and get results, but this is far from true. Downloads are discouraged if not blocked by web browsers, and security mechanisms inside the newer versions of Windows may block ARZ in a way that people may think it just doesn't work. In example: in Windows 11, as administrator, if I doubleclik on arz.bat a command prompt window appears and immediately disappears, if I unpack arz-22.zip,...
Ideally, people should just downaload, doubleclick on arz-<version>.zip and doubleclick on arz.bat to run this script and get results, but this is far from true. Downloads are discouraged if not blocked by web browsers, and security mechanisms inside the newer versions of Windows may block ARZ in a way that people may think it just doesn't work. In example: in Windows 11, as administrator, if I doubleclik on arz.bat a command prompt window appears and immediately disappears, if I unpack arz-22.zip,...
Ideally, people should just downaload, doubleclick on arz-<version>.zip and doubleclick on arz.bat to run this script and get results, but this is far from true. Downloads are discouraged if not blocked by web browsers, and security mechanisms inside the newer versions of Windows may block ARZ in a way that people may think it just doesn't work. In example: in Windows 11, as administrator, if I doubleclik on arz.bat a command prompt window appears and immediately disappears, if I unpack arz-22.zip,...
I plan to add an italian translation of all the documentation files in the future.
My project, Analisi Rete di Zangune (ARZ), is released under the GNU General Public License version 3, so it is free software, but it is not in the public domain: you cannot do whatever you want with ARZ, you have to respect the GNU General Public License version 3. You can read the full text of the GNU General Public License version 3 here, it is a complex text, but this FAQ list may help. In particular, if you share my program, then you have to say I written it and you have to let people who get...
I believe it could be interesting to tag my code with a Javadoc's like syntax. In my comments I will add a keyword with an "at" sign before it, like this: :: Find the default gateway :: @FindGateway this may be helpful to find the part of the code you need in the whole text. Do not assume I will adhere to Oracle documentation strictly.
ARZ 0.22. I will release it on eMule Content Database as soon as they fix them, I do not believe it will be soon, if ever. arz-0.22.zip.
I opened a thread on the official eMule board titled Batch To Find Ip, Gateway, Ports (useful to find needed data to setup a router), but I cannot edit it, because the forum stops me to add links; this is a security limitation, I think (if I remember it correctly, it could be possible to edit that message in the past, I guess they forbid users to add links to old messages because this is used for spam). I'll avoid breaking things here and there by removing links, creating new topics etcetera, so...
NETSTAT/ANO shows output immediately. A : display All connections and listening ports. N : display addresses and port numbers in Numerical form. O : display the Owning process ID associated with each connection. removing the N option is slower, but probably unavoidable.
This should be definitely the best solution, according to the case of commando67 that I faced on IRC this evening: commando67 joined #eMule-Italian, matry's AnalisiRete (a .NET arz equivalent) failed to find useful information, I suggested him to launch arz, the program gave me a fake result because of commando67 unzipped eMule in a folder but he had (or has) another eMule version installed, I spent a lot of time to undestand that I helped him to forward two different ports, when we changed ports...
Actually arz searches the preferences.ini file and scans that file to find eMule ports. A different approach can be to search for listening ports in Windows, in example this command NETSTAT -A can be useful, but eMule has to be open.
NETSTAT/ANO seems to be the fastest to show output. A : display All connections and listening ports. N : display addresses and port numbers in Numerical form. O : display the Owning process ID associated with each connection. but how to chatch eMule here?
NETSTAT/ANO seems to be the fastest to show output. A : display All connections and listening ports. N : display addresses and port numbers in Numerical form. O : display the Owning process ID associated with each connection. but how to chatch eMule here?
[0.11] is a quick and dirty workaround: I moved the dummy variable definition. A proper fix requires rewriting half of the program to remove the eMuleRegistryConfigValue variable dependency; maybe too much work for the goal (supporting users who mess up things with installations and uninstallations).
[0.11] is a quick and dirty workaround: I moved the dummy variable definition. This moves the problem from avoiding a crash to avoiding to give false or missing results. A proper fix requires rewriting half of the program to remove the eMuleRegistryConfigValue variable dependency; maybe too much work for the goal (supporting users who mess up things with installations and uninstallations).
[0.11] is a quick and dirty workaround: I moved the dummy variable definition. A proper fix requires rewriting half of the program to remove the eMuleRegistryConfigValue variable dependency; maybe too much work for the goal (supporting users who mess up things with installations and uninstallations).
[0.11] is a quick and dirty workaround: I moved the dummy variable definition. A proper fix requires rewriting half of the program to remove the eMuleRegistryConfigValue variable dependency; maybe too much work for the goal (supporting users that mess up things with installations and uninstallations).
[0.11] is a quick and dirty workaround: I moved the dummy variable definition. A proper fix requires rewriting half of the program to remove the eMuleRegistryConfigValue variable dependency; maybe too much work for the goal.
Missing registry key HKCU\Software\eMule causes ARZ to fail
Related to issue Missing registry key HKCU\Software\eMule causes ARZ to fail because if arz won't search the preferences.ini then it won't care about the registry key, too.
Related to Missing registry key HKCU\Software\eMule causes ARZ to fail because if arz won't search the preferences.ini then it won't care about the registry key, too.
Missing registry key HKCU\Software\eMule causes ARZ to fail
Related to a thread called "Port finding part possible rewrite", because if arz won't search the preferences.ini, then it won't care about the registry key, too.
Fixed in [0.17], new FindGateway routine: FOR /F "TOKENS=3" %%G IN (' ROUTE PRINT ^|FINDSTR ":" ^|FINDSTR ".*\."' ) DO ( SET Gateway=%%G )
draft
main
main
Dunno, but if it works, then I should use FOR /F "TOKENS=2 DELIMS=[]" %%I IN ( 'TRACERT -d -4 %ComputerName% ^|FIND "["' ) DO ( SET LocalIp=%%I )
It's well known the used route depends on the application, anyway according to Microsoft (again Microsoft Knowledge Base 894564) you may have a program that uses the first connection in the network connections list. You may want to make sure that a certain network connection is at the top of the list and I cannot see any reason that would suggest eMule to choose a route that is not the first one in the list.
Dunno, but if it works then I should use FOR /F "TOKENS=2 DELIMS=[]" %%I IN ( 'TRACERT -d -4 %ComputerName% ^|FIND "["' ) DO ( SET LocalIp=%%I )
Dunno, but if it works then I should use FOR /F "TOKENS=2 DELIMS=[]" %%I IN ( 'TRACERT -d -4 %ComputerName% ^|FIND "["' ) DO ( SET LocalIp=%%I )
Dunno, but if it works then I should use :::batch FOR /F "TOKENS=2 DELIMS=[]" %%I IN ( 'TRACERT -d -4 %ComputerName% ^|FIND "["' ) DO ( SET LocalIp=%%I )
Years ago, I opened a thread on the official eMule board titled Batch To Find Ip, Gateway, Ports (useful to find needed data to setup a router), but I cannot edit it anymore, because the forum stops me to add links; this is a security limitation, I think. I'll avoid breaking things here and there by removing links, creating new topics etcetera, so I will leave it as it is there.
Years ago, I opened a thread on the official eMule board titled Batch To Find Ip, Gateway, Ports (useful to find needed data to setup a router), but I cannot edit it anymore, because the forum stops me to add links, this is a security limitation, I think. I'll avoid breaking things here and there by removing links, creating new topics etcetera, so I will leave it as it is there.
Here you will find an eD2K link to ARZ 0.22, I will release it on eMule Content Database as soon as they fix them, I do not believe it will be soon, if ever. arz-0.22.zip.
Here you will find an eD2K link to ARZ 0.22, I will release it on eMule Content Database as soon as they fix them, I do not believe it will be soon, if ever. arz-0.21.zip.
I just released version 0.22, that enhances code readability by using tabs instead of just a space for indentation. If I edit the page by clicking the Edit button on top right of it and I copy and paste onto CudaText 1.223.6.0, everything works fine; but if I just copy the text and I paste onto Notepad, it will change tabs with four spaces and it won't respect newlines. I had to take that into consideration to avoid problems and to be sure users can just right-click on arz.bat to check the code.
draft
main
Use TABs or four spaces for indentation in code
As I wrote we need a bit of attention, because we used some tricks, like the use of the caret (^), to break lines In particular, lines 115 and 116 of version 0.21 are DIR/B "%~dp0"^ |FIND "preferences.ini">NUL and four spaces here will not work well, so I opted for using TABs.
As I wrote we need a bit of attention, because we used some tricks, like the use of the caret (^), to break lines In particular, lines 115 and 116 of version 0.21 are DIR/B "%~dp0"^ |FIND "preferences.ini">NUL and four spaces here will not work well, so I opted for using TABs.
summary: Use multiples of four spaces for indentation in code --> Use TABs or four spaces for indentation in code
0.22
Use TABs or four spaces for indentation in code
Use TABs instead of spaces for indentation in code
Use TAB instead of spaces for indentation in code
Indeed, the default "discussion" would be better than the word "forum", anyway I do not plan to change this soon (if I do that, then I should update the documentation, too). An idea is to change the forum URL with a redirect to the discussion URL. In example: http://sf.net/p/arz/f to redirect to: http://sf.net/p/arz/discussion No, at least not here on SourceForge, at least not for now. It seems that the link has to be at least 3 characters long, so f cannot be a redirection. It's not a good practice...
Indeed, the default "discussion" would be better than the word "forum", anyway I do not plan to change this soon (if I do that, then I should update the documentation, too). An idea is to change the forum URL with a redirect to the discussion URL. In example: http://sf.net/p/arz/f to redirect to: http://sf.net/p/arz/discussion No, at least not here on SourceForge, at least not for now. It seems that the link has to be at least 3 characters long, so f cannot be a redirection. It's not a good practice...
Switched from wont-fix to rejected. Hardly ever people should use "wont-fix" (at least when dealing with copyleft projects), because circumstances or developers or anything else can change in the future. In general, we can't say too much about the future.
Switched from wont-fix to rejected. Hardly ever people should use "wont-fix" (at least about copyleft projects) because circumstances or developers or anything else can change in the future. In general, we can't say too much about the future.
Indeed, the default "discussion" would be better than the word "forum", anyway I do not plan to change this soon (if I do that, then I should update the documentation, too). An idea is to change the forum URL with a redirect to the discussion URL. In example: http://sf.net/p/arz/f to redirect to: http://sf.net/p/arz/discussion No, at least not here on SourceForge, at least not for now. It seems that the link has to be at least 3 characters long, so f cannot be a redirection. It's not a good practice...
Switched from "Problem" to "defect". A problem is something that causes you trouble, a defect is something that does not work as it should. The right place to discuss a problem of the project that is not a defect is a new argument in the discussion board, so tickets about problems that are not defects and that are opened into the issue tracker should be set to invalid. In example, check issue SmartScreen and browsers protections block ARZ: I can't fix that, because it does not depend on me, so this...
Many projects (like SourceForge itself) use more than one tool for bug reporting and feature requests, but this is confusing. In Issues you can report bugs and ask for a new feature in the same issue tracker, you just need to change Type field to "Enhancement" if you want to ask for a new feature. The difference between a bug and a missing feature seems to be not so clear to all users, too. More than this, the term "bug" is not so common between non tech savvy users, so "problem" appears a better...
Many projects (like SourceForge itself) use more than one tool for bug reporting and feature requests, but this is confusing. In Issues you can report bugs and ask for a new feature in the same issue tracker, you just need to change Type field to "Enhancement" if you want to ask for a new feature. The difference between a bug and a missing feature seems to be not so obvious to all users, too. More than this, the term "bug" is not so common between non tech savvy users, so "problem" appears a better...
Switched from "Problem" to "defect". A problem is something that causes you trouble, a defect is something that does not work as it should. The right place to discuss a problem that is not a defect of the project is a new argument in the discussion board, so tickets about problems that are not defects and that are opened into the issue tracker should be set to invalid. In example, check issue 8 (SmartScreen and browsers protections block ARZ): I can't fix that, because it does not depend on me, so...
Switched from wont-fix to rejected. Nobody should use "wont-fix" (at least, not in copyleft projects) because circumstances or developers or anything else can change in the future. In general, we can't say too much about the future.
Switched from wont-fix to rejected. Nobody should use "wont-fix" (at least not in copyleft projects) because circumstances or developers or anything else can change in the future. In general, we can't say too much about the future.
Switched from build to revision.
Switched from build to revision.
Even if most of the fields in Issues are prebuilt by SourceForge, the meaning of them needs an explanation. STATUS FIELD MEANING unread : nobody that can modify the issue status read that issue yet (the reporter should leave this by default); open : it is still not clear if it is a valid one or not, the issue is under discussion; accepted : who modified the issue status believes this issue is valid, but either there is no solution or interest or time to close this issue; pending : someone is working...
Switched from "Problem" to "defect". A problem is something that causes you trouble, a defect is something that does not work as it should. The right place to discuss a problem that is not a defect of the project is a new argument in the discussion board, so tickets about problems that are not defects and that are opened into the issue tracker should be set to invalid. In example, check issue 8 (SmartScreen and browsers protections block ARZ): I can't fix that, because it does not depend on me.
Switched from wont-fix to rejected. Nobody should use "wont-fix", at least not in copyleft projects, because circumstances or developers or anything else can change in the future. In general, we can't say too much about the future.
Switched from wont-fix to rejected. Nobody should use "wont-fix", at least not in copyleft projects, because moods or developers or anything else can change in the future. In general, we can't say too much about the future.
Switched from wont-fix to rejected. Nobody should use "wont-fix", at least not in copyleft projects, because time or developers or anything else can change in the future. In general, we can't say too much about the future.
Switched from wont-fix to rejected. Nobody should use "wont-fix", at least not in copyleft projects, because time or new developers or anything else can change in the future. In general, we can't say too much about the future.
Many projects (like SourceForge itself) use more than one tool for bug reporting and feature requests, but this is confusing. In Issues you can report bugs and ask for a new feature in the same issue tracker, you just need to change Type field to "Enhancement" if you want to ask for a new feature. The difference between a bug and a missing feature seems to be not so obvious to all users, too. More than this, the term "bug" is not so common between non tech savvy users, so "problem" appears a better...
Indeed "severity" is too long for SourceForge, graphical demonstration:
Generally speaking, maybe the short versions of the URLs are not that good, or at least they should be just a redirect to a full path (they cannot, read before). Anyway, SourceForge uses "p" instead of "projects" in URLs when you are in a tool page (in example in this forum).
Indeed, the default "discussion" would be better than the word "forum", anyway I do not plan to change this soon (if I do that, then I should update the documentation, too). An idea is to change the forum URL with a redirect to the discussion URL. In example: http://sf.net/p/arz/f to redirect to: http://sf.net/p/arz/discussion No, at least not here on SourceForge, at least not for now. It seems that the link has to be at least 3 characters long, so f cannot be a redirection. A single discussion can...
search_one_file_through_all_mounted_drives
New ARZ versions will be released .zip files instead of .bat files. In this way I can add useful files to the ARZ package. The name convention will be the GNU one anyway. I will include these files: arz.bat : Analisi Rete di Zangune (ARZ) executable; AUTHORS.txt : who wrote this program; ISSUES.txt : defects, enhancements and about these two; CHANGES.txt : for advanced users and programmers; FAQ.txt : questions and answers; INSTALL.txt : how to install this program; LICENSE.txt : GNU General Public...
New ARZ versions will be released .zip files instead of .bat files. In this way I can add useful files to the ARZ package. The name convention will be the GNU one anyway. I will include these files: arz.bat : Analisi Rete di Zangune (ARZ) executable; AUTHORS.txt : who wrote this program; ISSUES.txt : defects, enhancements and about these two; CHANGES.txt : for advanced users and programmers; FAQ.txt : questions and answers; INSTALL.txt : how to install this program; LICENSE.txt : GNU General Public...
I will test version [c:0.22] a bit before publishing. This release should fix this minor issue, but still I have to update ISSUES.txt in the compressed archive.
0.22
I will test version [c:0.22] a bit before publishing. This release should fix this minor issue, but still I have to update ISSUES.txt file in the archive.
0.22
I will test version [c:0.22] a bit before publishing. This release should fix this minor issue, but still I have to update ISSUES.txt and the LICENSE.txt files in the archive.
Use multiples of four spaces for indentation in code
0.22
Here you will find an eD2K link to ARZ 0.21, I released it on eMule Content Database (broken website, I hope they will fix it, soon or later). arz-0.21.zip.
Here you will find an eD2K link to ARZ 0.21, I released it on eMule Content Datab (broken website, I hope they will fix it, soon or later). arz-0.21.zip.
Back to the original problem, an idea is to check if an IPv4 address is given in the same block where the MAC address is. In example here: Scheda LAN wireless Connessione rete wireless: Suffisso DNS specifico per connessione . . : localdomain Descrizione . . . . . : Scheda di rete Broadcom 802.11g Indirizzo fisico . . . . . . . . . . :00-31-00-13-FF-4E DHCP abilitato . . . . . . . . . . . . . . . . . . : Sì Configurazione automatica abilitata: . . . . . . . : Sì Indirizzo IPv4 . . . . . . : 192.168.1.9...
Start to search from subdirectories of the current directory of ARZ
Even if most of the fields in Issues are prebuilt by SourceForge, the meaning of them needs an explanation. STATUS FIELD MEANING unread : nobody that can modify the issue status read that issue yet (the reporter should leave this by default); open : it is still not clear if it is a valid one or not, the issue is under discussion; accepted : who modified the issue status believes this issue is valid, but either there is no solution or interest or time to close this issue; pending : someone is working...
Even if most of the fields in Issues are prebuilt by SourceForge, the meaning of them needs an explanation. STATUS FIELD MEANING unread : nobody that can modify the issue status read that issue yet (the reporter should leave this by default); open : it is still not clear if it is a valid one or not, the issue is under discussion; accepted : who modified the issue status believes this issue is valid, but either there is no solution or interest or time to close this issue; pending : someone is working...
Even if most of the fields in Issues are prebuilt by SourceForge, the meaning of them needs an explanation. STATUS FIELD MEANING unread : nobody that can modify the issue status read that issue yet (the reporter should leave this by default); open : it is still not clear if it is a valid one or not, the issue is under discussion; accepted : who modified the issue status believes this issue is valid, but either there is no solution or interest or time to close this issue; pending : someone is working...