tesa Useful Batch Files - Active List / Non Active List Requests

[Ashenfire]

Useful Batch Files Request

 

Purpose

For enthusiasts or people looking for neat, cool, interesting batch files to add to their collections.

For enthusiasts to share programming ideas without snotty attitudes and rating systems like stack exchange.

For enthusiasts to advertise creations that are related to D.O.S 3.0 through Win 10.

Whats Needed

Over the course of time, new batch files will be added to the roster, courtesy of the Homechicken Software Lab.

Over the course of time, other people might want to add their batch files to the list.

These will be considered ACTIVE and must be approved.

Non-Active are batch programs that do not meet the active criteria however, are still useful in the library of knowledge, to share.

Criteria for items to be approved; before appearing on the ACTIVE listing.

• Ability to ELEVATE user rights for installation purporses.  Mostly, the program relies on more than one file or program to operate.
• Ability to function if NOT elevated and does not require an install program.  Mostly, the program is independent and in the path statement.
• Citations of work.  For instance I had trouble with a space counter and I didn't want to do the work so I looked up how, and now there is a fella named JEB who probably is on stack exchange, I don't remember original area.  The point is the batch file called  SPCCOUNT.BAT has a remark file noting where I got the code.  In fact 95% of the code was not altered.  Of course, the spccount.bat will be re written when I have more time. 
• No hidden 'phone home' code.  This is deplorable, dishonorable and makes it hard for people to trust third party code because they are not judged by a master code editor or trusted source.
• No code that relies on .com or .exe, xhtml, vbs, powershell, etc; unless they are D.O.S. native or native to the kit.  The focus is to enjoy BATCH programming, not a 'honey to do list' that tells other files what to do.
• No links, hidden or shown, that have the ability to append to other user code and turn it into advertising links or evolve into malware.
• Make your batch files easy to abort from memory.  This means if you somehow can store your code in EMS, or page the memory; it MUST unload from memory when the user aborts the program.
• No left over setup, configurations, etc,  in the registry; if the user uninstalls the batch program.
• Do not dump program files or even links on the users desktop without providing an option to do so.
• Do no install program code inside the actual WINDOWS folder structure.
• Give the user the choice to accept a suggested install location or they provide their own.  No issue here, HCS-SDK covers that anyways.
• Designers do not have to use the kit templates if they don't want to however; any program they make must have the ability to be FOUND via common path statement or a windows .lnk file.   The HCS-SDK actually utilizes Visual basic .vbs files in its INSTALL to add proper path statements to newly installed files.
• No REM statements, ini statements, registry statements, links, path statements, CVS, CFG; etc advertising how to get illegal warez, drugs; or where to do an illegal transaction.

Criteria for items to be appear on a  Non-Active Listing:

• Citations of work.  Still need to show love for your fellow designers.
• No hidden 'phone home' code.  This is deplorable, dishonorable and makes it hard for people to trust third party code because they are not judged by a master code editor or trusted source.
• No links, hidden or shown, that have the ability to append to other user code and turn it into advertising links or evolve into malware.
• Rename the batch file with a .NAC extension to notate useful code not following Active criteria.  This prevents a downloader from accidently executing the code and blaming others for destroying their computer rig; or complaining that it is not working.
• NAC code does not have to be complete.  It can just be a one liner with a designer's written understanding of how code should be.
• NAC codes must be in English.  Sorry.  Any translators for tutorials, NAC code are appreciated, they just are unavailable right now.
• No REM statements, ini statements, registry statements, links, path statements, CVS, CFG; etc advertising how to get illegal warez, drugs; or where to do an illegal transaction.

This forum  is looking forward to enthusiasts to share knowledge in a friendly atmosphere with no attitude of 'divine self' or putting down others because their expression of code or ideas are different than someone elses.

 

Edited February 19, 2021 by Ashenfire
Grammar

[Ashenfire]

Start with Sticky Notes for Windows 7 and 10, and other sticky programs.