How truong310100/soft works
Project Type and Purpose
• This “Soft” repository is not a web or server application but a curated toolkit for Windows administrators and power users. It aggregates:
• Batch scripts (.cmd), VB scripts (.vbs), and Python scripts (.py)
• Portable executables (.exe) for utilities like 7-zip, AnyDesk, CrystalDiskInfo
• Configuration files (JSON, .reg) and Office/Windows activation tools
• Document templates under signatureHHH/Form
• Purpose: streamline device setup, driver installation, license activation, system checks, and document generation on Windows.
File‐Structure Analysis
• Top‐level:
• Run.cmd, Setup.vbs – entry points
• Apps/ – container for all modules
• README.md – placeholder with Git instructions
• Under Apps/:
• Activation tools (ActivateAIOToolsv3.1.3/) – nested folders of scripts, binaries, license files
• CheckingDevice/ – subfolders for BackupApp (Python + JSON), CrystalDiskInfo (binaries + CSV data)
• signatureHHH/ – Python‐based doc generator plus Word template library
• Assorted standalone installers and helper scripts (.cmd, .vbs, .reg, .exe)
a. Main Components
1. Entry Layer
– Run.cmd / Setup.vbs (invoked by user)
2. Module Layer
– Activation Module (scripts + binaries + license data)
– CheckingDevice Module
• BackupApp (Python + data JSON)
• CrystalDiskInfo (exe + SMART CSV data)
– Document Generation Module (signatureHHH/Form + Python exe)
– Utility Scripts & Installers (7-zip, AnyDesk, Wi-Fi drivers, etc.)
3. Data Layer
– License configuration files (.xrm-ms, .reg)
– Device data (SMART CSV under CheckingDevice)
– Template docs (.docx)
b. Relationships & Interactions
– User → Entry Layer (Run.cmd kicks off setup)
– Entry Layer → Module Layer (calls specific scripts)
– Activation Module scripts call binaries and read/write license data
– BackupApp Python reads JSON, writes folder backups
– CrystalDiskInfo exe reads device SMART data and stores CSVs
– Document Gen Python exe reads templates → outputs .docx
c. Architectural Patterns & Principles
– Modular separation by function (Activation, Backup, Monitoring, Doc Gen)
– File-system–centric “service” approach: each module is self-contained in its subfolder
– Use of portable executables to avoid system installation dependencies
d. Key Technologies
– Windows Batch (.cmd), VBScript (.vbs), Python (PyInstaller exe)
– Portable COTS tools (7-zip, AnyDesk, CrystalDiskInfo)
– JSON for config, CSV for device data