ATI Rage 128: history, specs and gaming performance

History

Introduced in late 1998, the ATI Rage 128 evolved from the Rage family and competed with NVIDIA’s RIVA TNT and 3dfx Voodoo products. It was among ATI’s early cards offering full 32-bit rendering and an integrated MPEG-2 decoder. Key variants included Rage 128 GL, Rage 128 VR, and the later Rage 128 Pro.

Key specifications (summary)

  • GPU: Rage 128 (Rage R6)
  • Process: ~250 nm
  • Core clock: ~100–125 MHz (varies by model)
  • Memory: 16–32 MB SDRAM/SGRAM
  • Memory bus: 128-bit
  • Interfaces: AGP 2x/4x and some PCI variants
  • APIs: DirectX 6.0, OpenGL 1.2
  • Features: 32-bit color, hardware MPEG-2 decoder

Platforms

The card was used in mainstream PCs (Pentium II/III, AMD K6/Athlon) and was also integrated into several Apple machines (iMac G3 DV, some Power Mac models). OEM vendors like Dell and Compaq offered it as a midrange option.

Gaming performance (overview)

Rage 128 provided solid performance in late-90s titles but was limited by less advanced T&L and driver maturity. Typical results:
  • Quake II — very good (60–80 FPS at 800×600 on capable systems)
  • Unreal / Unreal Tournament — comfortable 40–60 FPS
  • Half-Life — smooth on typical systems
  • Quake III Arena — around 30–40 FPS at 800×600 depending on drivers

Pros & Cons

Pros: 32-bit rendering, decent memory bus, hardware MPEG-2. Cons: driver issues (especially OpenGL), limited T&L performance, quickly surpassed by next-gen GPUs.

Conclusion

Rage 128 is historically significant as a transitional GPU: good image quality and multimedia support for its era, but limited in raw 3D throughput compared to later competitors. It remains an interesting piece of late-90s PC hardware history.

ATI Mach64 Graphics Card – History, Architecture, Supported Systems and Gaming Capabilities

ATI Mach64 is a family of 2D graphics accelerators produced by ATI Technologies in the mid-1990s (starting around 1994). It followed the earlier Mach8 and Mach32 lines and became the technological predecessor to the later ATI Rage series. The primary goal of Mach64 was to accelerate graphical user interfaces, improve Windows performance, and provide enhanced multimedia capabilities. Early models did not feature true 3D acceleration.

History and Evolution

The Mach64 family appeared during the transitional period when PC graphics were moving from basic VGA cards to hardware-accelerated multimedia adapters. The series included many chip revisions with different performance levels and multimedia features. Some versions introduced early 3D functions, which later became the foundation for the ATI 3D Rage line.

Main Chip Variants

  • Mach64 CX, CT, GX – early, primarily 2D-accelerated versions.
  • Mach64 VT – enhanced multimedia/video playback support (YUV to RGB conversion).
  • Mach64 GT / GT-B – early 3D-capable revisions that later evolved into ATI 3D Rage.
  • Mach64 LT – mobile/OEM-oriented versions.

Hardware Specifications

  • Memory bus: 64-bit internal architecture.
  • Video memory: Typically 1 MB, 2 MB, 4 MB or 8 MB (DRAM, VRAM or SGRAM depending on card model).
  • Interface: ISA, VLB (VESA Local Bus), and PCI versions existed.
  • RAMDAC: Integrated RAMDAC in most CT/CX/GX versions; higher-frequency RAMDAC available in “Turbo” models.
  • Video features: Select models supported hardware-assisted video scaling and basic MPEG playback through drivers.

Supported Operating Systems

ATI provided official drivers for a large set of operating systems of that era:
  • DOS
  • Windows 3.1
  • Windows 95
  • Windows 98 / Windows Me
  • Windows NT 3.51 / NT 4.0
  • OS/2
  • Some OEM versions for classic Macintosh systems

Gaming Performance

The gaming capability of the Mach64 series depends heavily on the specific revision:

Excellent Performance in 2D Games

The Mach64 was designed primarily as a 2D accelerator, so it excelled in classic DOS and early Windows titles:
  • Wolfenstein 3D
  • Doom and Doom II (software rendering)
  • Warcraft I & II
  • Command & Conquer
  • Age of Empires (2D elements)
  • Point-and-click adventures, platformers, and many early strategy games

3D Games (Software Rendering)

Early Mach64 models did not contain hardware 3D acceleration, so games requiring 3D APIs ran in CPU-driven software mode. Titles like:
  • Quake
  • Quake II
  • Unreal
  • Duke Nukem 3D (with 3D effects)
were technically playable but performed slowly without dedicated 3D hardware.

Mach64 GT and Later (Early 3D Rage)

The GT and GT-B variants introduced primitive 3D acceleration and improved performance in some Direct3D titles. However, they still could not compete with popular 3D cards such as the 3dfx Voodoo or NVIDIA Riva TNT.

Multimedia Features

Many Mach64 cards included enhanced video playback capabilities. The VT and GX versions supported:
  • Hardware-assisted YUV → RGB conversion
  • Improved scaling for full-screen video
  • Better overall MPEG playback (with driver support)

Conclusion

The ATI Mach64 remains an important historical graphics chip. It offered fast and reliable 2D acceleration and excellent support for DOS and early Windows games. While it was not a strong 3D performer in its base versions, later Mach64 GT derivatives became the foundation of the ATI 3D Rage series. For retro PC builds focused on classic DOS/Windows 95 gaming, the Mach64 is still an excellent and authentic choice.

Compex RL100ATX: History, Specifications, and How to Get It Working Today

Legacy PCI 10/100 Ethernet adapter based on Realtek RTL8139 — overview, driver tips for Windows 98/ME, Linux notes and troubleshooting.

Quick summary

The Compex RL100ATX is a classic PCI Fast Ethernet adapter (10/100 Mbps) that was widely sold in the late 1990s and early 2000s. It is typically built around the Realtek RTL8139 family chipset. Because of the ubiquity of that chipset, the RL100ATX enjoys broad operating-system support and often works “out of the box” on many older systems.

Technical specifications

  • Model: Compex RL100ATX (sometimes listed as RL100ATX 10/100 Base PCI)
  • Interface: 32-bit PCI (PCI 2.x era)
  • Speed: 10/100 Mbps (10Base-T / 100Base-TX)
  • Typical chipset: Realtek RTL8139 family (RTL8139A/B/C)
  • Auto-negotiation: Yes (10/100, full/half duplex)
  • OS support (historical): Windows 98 / ME / 2000 / XP, many Linux kernels

Short history and context

When Fast Ethernet (100 Mbps) became mainstream, chipset vendors such as Realtek produced very low-cost, compact controllers (RTL8139). Small networking companies like Compex soldered those chips onto PCI cards and sold large volumes to OEMs and end users. The RL100ATX is one of those low-cost, high-compatibility adapters that helped desktops move from 10 Mbps to 100 Mbps networking affordably.

Driver and OS compatibility

The important compatibility fact is that the RL100ATX most often identifies itself to the operating system as a Realtek RTL8139 device. That means:
  • Windows ME / 2000 / XP: In most cases the OS contains an appropriate RTL8139 driver and will configure the card automatically.
  • Windows 98 / 98 SE: Windows 98 can sometimes install a built-in driver but may need the Realtek driver INF. Using the “Have Disk…” option and selecting the generic RTL8139 driver usually works.
  • Linux: The kernel module rtl8139 (or 8139too in older kernels) provides broad support; adapters are normally plug-and-play on modern distributions.

Practical installation tips (old machines)

  1. Try the built-in driver first: In Windows 98, when asked for drivers choose “Show all devices” → look for Realtek RTL8139/8139 family drivers.
  2. If you cannot copy files to the machine: use alternative file transfer methods: floppy disk, grab the hard drive and copy files on another PC, write a CD-R, or use a serial/parallel LapLink cable (InterLink) if available.
  3. Windows ME option: Upgrading to Windows ME on the same hardware often brings newer bundled drivers and increases chances of plug-and-play detection for RTL8139 cards.
  4. Linux: Most live CDs or modern installs already include rtl8139 support — the card should work with no extra driver required.
  5. BIOS/IRQ issues: On very old machines, disable unused onboard devices or free IRQs in BIOS if the card is not detected or IRQ conflicts appear.

Troubleshooting checklist

  • No link light: check the cable and switch port; try a different known-good Ethernet cable.
  • Link but no network: confirm IP configuration (DHCP vs static); try pinging the gateway; swap ports on the switch/router.
  • Intermittent drops: test on another switch or directly to another PC (crossover or auto-MDI/MDIX). In Windows, disable checksum/large-packet offload in driver properties if available.
  • Not detected at all: reseat the card, try another PCI slot, check for bent pins, or test card in another machine to verify hardware failure.

Legacy use and modern relevance

The RL100ATX is a legacy device today. For restoration projects, retrocomputing, or small isolated networks it remains useful. However, for modern home/office networks a Gigabit PCIe adapter is recommended because many switches and routers now provide gigabit speeds.

Suggested keywords & tags

Compex RL100ATX, RTL8139, PCI Ethernet, Windows 98 driver, Windows ME, legacy network card

Conclusion

The Compex RL100ATX is a straightforward, widely compatible Fast Ethernet PCI card — a practical choice for older systems. Because it usually uses the Realtek RTL8139 chipset, obtaining drivers or getting it working under Windows ME or modern Linux is rarely a problem. For high throughput modern networks, consider upgrading to a gigabit PCIe card.

Налаштування VLAN та DHCP на OLT BDCOM P3310C

У цій статті розглянемо приклад конфігурації OLT BDCOM P3310C, де клієнтський MikroTik отримує IP по DHCP у додатковому VLAN. Також розберемо типові помилки та способи їх виправлення.

Ситуація

Маємо такі налаштування:

  • Порт GigaEthernet0/1 підключений до клієнтського MikroTik, VLAN 1022 як native (untagged) та VLAN 500 як додатковий тегований VLAN.
  • Порт GigaEthernet0/5 — uplink до DHCP-сервера, де також піднятий VLAN 500.

Проблема: MikroTik не отримував IP через DHCP на VLAN 500, хоча IP на VLAN 1022 отримував нормально.

Діагностика

Першим кроком перевірили MAC-таблицю OLT:

show mac address-table vlan 500

Було видно тільки MAC клієнта на порту g0/1. MAC uplink порту g0/5 відсутній — DHCP DISCOVER не проходив.

Також перевірили конфігурацію VLAN:

show vlan

Спочатку VLAN 500 був прив’язаний до портів g0/1, g0/5 та epon0/x (EPON-порти).

Причина

На BDCOM P3310C, якщо VLAN одночасно присутній на EPON-портах та Ethernet-портах, але немає активної ONU на EPON, L2-трафік між Ethernet-портами не форвардиться. Тому DHCP DISCOVER від клієнта не доходив до uplink.

Також важливо зазначити: просто прописати switchport trunk vlan-allowed 500 на портах не гарантує, що VLAN буде працювати. На BDCOM VLAN потрібно додатково створити глобально і явно вказати, на яких портах він має працювати. Лише після цього трафік VLAN буде коректно комутуватися між портами.

Рішення

  1. Прибрали VLAN 500 з EPON-портів. Тепер VLAN 500 присутній тільки на g0/1, g0/5, g0/6.
  2. Створили VLAN 500 глобально та вказали порти:
    vlan 500
     port g0/1
     port g0/5
    exit
    
  3. Перезапустили порти (shutdown/no shutdown) і очищали MAC-таблицю:
    clear mac address-table dynamic vlan 500
    
  4. Перезапустили DHCP-клієнт на MikroTik для VLAN 500:
    /ip dhcp-client release [find interface=vlan.500]
    /ip dhcp-client renew [find interface=vlan.500]
    
  5. Перевірили MAC-таблицю:
    show mac address-table vlan 500
    

    Тепер з’явилися два MAC — клієнт на g0/1 та uplink на g0/5.

Результат

Після цих змін MikroTik отримав IP через DHCP на VLAN 500, VLAN 1022 також працює без змін. Проблема вирішена.

Висновок

При налаштуванні додаткових VLAN на OLT BDCOM потрібно враховувати особливості L2-бріджу між Ethernet та EPON-портами. VLAN, який одночасно присутній на EPON і Ethernet без активної ONU, може блокувати трафік між портами Ethernet. Також просто прописати switchport trunk vlan-allowed недостатньо — VLAN потрібно створювати глобально та явно вказувати порти, на яких він має працювати. Це гарантує коректну роботу DHCP та іншого трафіку VLAN.

Безпечна розрядка та зберігання акумуляторів 18650 LiitoKala 3000 mAh

Акумулятори типу 18650 LiitoKala 3000 mAh широко використовуються у ліхтарях, повербанках, електроніці та DIY-проєктах. Щоб продовжити термін їхньої служби та уникнути пошкодження, важливо знати, до якої мінімальної напруги можна розряджати елемент і як правильно його зберігати.

Мінімальна безпечна напруга розряду

У технічних характеристиках більшості моделей LiitoKala (наприклад Lii-HG2, Lii-30Q тощо) виробник вказує граничну напругу розряду – 2.5 В на комірку. Це так звана cut-off voltage – мінімальне значення, при якому батарея ще придатна до заряджання.

Проте постійне розряджання до 2.5 В скорочує термін служби акумулятора. Для довготривалої експлуатації рекомендується встановлювати нижню межу:

  • 2.8–3.0 В — оптимальна напруга відсічення для збереження ресурсу;
  • Не залишайте акумулятор надовго з напругою нижче 3.0 В;
  • Використовуйте захисну плату (BMS) або зарядний пристрій із контролем розряду.

Висновок: мінімальна безпечна напруга — 2.5 В, але для максимальної довговічності бажано обмежитись 2.8–3.0 В.

Чи можна зберігати акумулятор при 4.2 В?

4.2 В — це повний заряд (100%) для літій-іонного елемента. Хоча технічно це безпечно, тривале зберігання при такій напрузі прискорює старіння батареї через хімічні реакції в електроліті та катоді.

Як напруга впливає на старіння

Рівень заряду Напруга (приблизно) Втрата ємності за 1 рік при +25°C*
100% 4.20 В ≈ −20%
80% 4.00 В ≈ −10%
50% 3.75 В ≈ −4%
40% 3.70 В ≈ −2%

*Дані базуються на тестах Panasonic, LG, Samsung.

Оптимальна напруга для зберігання

  • Зберігати при 3.6–3.8 В (40–60% заряду);
  • Температура зберігання — 15–25°C;
  • Уникати перегріву та високої вологості.

Коли допустимо тримати 4.2 В

Якщо плануєте використати акумулятор у найближчі дні або тижні — залишати 4.2 В можна. Але для зберігання понад місяць краще розрядити до приблизно 3.8 В.

Підсумок

  • Мінімальна напруга розряду: 2.5 В (технічна межа), оптимально — 2.8–3.0 В.
  • Оптимальна напруга зберігання: 3.6–3.8 В.
  • Не рекомендується: тримати акумулятор повністю зарядженим (4.2 В) тривалий час.

Дотримання цих простих правил допоможе продовжити життя акумулятора 18650 у 2–3 рази, уникнути деградації ємності та забезпечити стабільну роботу пристроїв.

Working with crontab in Linux

1. Show list of all tasks

Display all cron jobs for the current user:

crontab -l

2. Add a new task

Edit your crontab file:

crontab -e

Add the following line at the end of the file to run a command every day at midnight:

0 0 * * * php /full/path/to/index.php

Replace /full/path/to/index.php with the actual path to your script.

3. Edit a task

Run:

crontab -e

Then modify the desired line in the editor.

4. Delete a task

Also via:

crontab -e

Just delete the task line and save changes.

To delete all cron jobs at once:

crontab -r

Warning: This removes all crontab entries for the user without confirmation.

Useful Examples

Every 5 minutes:

*/5 * * * * php /home/user/script.php

Every day at 6:30 AM:

30 6 * * * php /home/user/script.php

Every Monday at 7:00 AM:

0 7 * * 1 php /home/user/script.php

Log output to file:

0 0 * * * php /home/user/index.php >> /home/user/logs/cron.log 2>&1

>> appends output; 2>&1 combines stderr and stdout.

Check if cron is running

systemctl status cron

If stopped, start it:

sudo systemctl start cron

Other tips

Edit crontab for another user:

sudo crontab -u username -e

System-wide cron jobs:

  • /etc/crontab
  • /etc/cron.daily/
  • /etc/cron.hourly/
  • /etc/cron.weekly/
  • /etc/cron.monthly/

Source: https://aiblocklab.com/en/articles/linux-server-tutorials/working-with-crontab-in-linux

🔐 How to Securely Encrypt and Decrypt Any File in Linux

In today’s digital world, ensuring the confidentiality of your sensitive data is more important than ever. Whether you’re backing up documents, transferring files, or protecting personal information, encrypting your files is a critical security step. In this article, we’ll explore how to securely encrypt and decrypt any file using the Linux terminal — leveraging robust, open-source tools like gpg and openssl.


🔧 Symmetric Encryption with gpg

The simplest and most effective method for encrypting files locally is symmetric encryption, where the same password is used for both encryption and decryption.

🔒 Encrypt a File with a Password

gpg -c myfile.txt

You’ll be prompted to enter a passphrase. The resulting file will be myfile.txt.gpg.

🔓 Decrypt the File

gpg -o myfile_decrypted.txt -d myfile.txt.gpg

You’ll be prompted for the same passphrase to decrypt the file.

Best For: Local file protection or sharing with someone you trust enough to share a password with.


🔐 Asymmetric Encryption (Using Key Pairs)

For secure communication or file exchange between users, asymmetric encryption is recommended. This method uses a pair of keys: a public key for encryption and a private key for decryption.

Step 1: Generate a Key Pair

gpg --full-generate-key

Choose:

  • Key type: RSA and RSA
  • Key size: 4096 bits (recommended)
  • Expiration: Set if desired
  • User information: Name and email

Step 2: List Available Keys

gpg --list-keys

Step 3: Encrypt a File for a Specific User

gpg -e -r "User Name or Email" myfile.txt

This command will create myfile.txt.gpg, encrypted with the recipient’s public key.

Step 4: Decrypt the File

gpg -d myfile.txt.gpg > myfile_decrypted.txt

The recipient’s private key must be available on the system to decrypt.

Best For: Secure communication and file exchange between multiple parties.


🔧 Alternative: Using openssl

For those who prefer OpenSSL, here’s how to use AES-256 encryption:

🔒 Encrypt

openssl enc -aes-256-cbc -salt -in myfile.txt -out myfile.txt.enc

🔓 Decrypt

openssl enc -d -aes-256-cbc -in myfile.txt.enc -out myfile_decrypted.txt

You’ll be asked to provide the same password for decryption.


🛡️ Security Tips

  • Use strong, unique passphrases — at least 12+ characters with a mix of letters, numbers, and symbols.
  • Avoid storing passphrases in plaintext.
  • When sharing files, prefer asymmetric encryption over symmetric if possible.
  • Back up your private keys in a secure location.

📦 Conclusion

Encrypting files via the Linux terminal is both powerful and straightforward with tools like gpg and openssl. Whether you’re an individual protecting personal data or a business sharing confidential documents, these methods help ensure your information stays safe.

Why Did Monero’s Price Soar to $392.72?

Monero (XMR) is a privacy-focused cryptocurrency that ensures full transaction anonymity by concealing the sender’s and receiver’s addresses, as well as the transferred amount.
It utilizes technologies like ring signatures, stealth addresses, and the RingCT protocol to guarantee that all transactions remain private and untraceable.

In May 2025, the value of XMR reached $392.72, driven by several key factors:

1. End of a Multi-Year Accumulation Phase

Analysts have noted that Monero broke out of a prolonged accumulation phase, showing significant price growth.

2. Growing Demand for Privacy

As global regulators tighten control over cryptocurrencies, the demand for anonymous transactions is increasing.
Monero, being the leading privacy coin, is becoming increasingly attractive to users who prioritize financial privacy.

3. Limited Availability on Exchanges

Due to Monero being delisted from several centralized exchanges, including Binance and Kraken, its availability has become restricted.
This scarcity of XMR on the market contributed to upward pressure on its price.

4. Technical Indicators and Market Sentiment

Technical analysis shows Monero is in a strong uptrend.
Indicators such as the Directional Movement Index (DMI) point to a clear advantage for buyers, supporting continued price growth.
(Source: reddit.com)


🔮 Future

Considering current market trends and technical indicators, Monero’s price is expected to reach new highs in the coming months.
Forecasts suggest it could surpass $525.64 by the end of 2025.
(Source: the-crypto-news.com)


✅ Conclusion

Monero remains one of the most reliable cryptocurrencies for ensuring transaction privacy.
Its growing popularity, limited supply, and technological advantages contribute to its increasing value.
However, investors should remain cautious and consider potential regulatory risks and market volatility.

How to test server for vulnerabilities

To check open ports on the server use Nmap program. To install Nmap use command:

sudo apt install nmap

This command check server IP for open ports:

sudo nmap -sC -sV -v IP_ADDRESS

For fast scan all ports with Nmap use command:

sudo nmap -sS -v IP_ADDRESS -p-

Scan directories on host:

ffuf -w ~/SecLists/Discovery/Web-Content/directory-lists-lowercase-2.3-small.txt:FUZZ -u "http://IP_ADDRESS/FUZZ" -ic -c -e .php

Scan Subdomains:

ffuf -w ~/SecLists/Discovery/Web-Content/directory-lists-lowercase-2.3-small.txt:FUZZ -u "http://DOMAIN.COM/" -H 'Host: FUZZ.DOMAIN.COM' -fw SIZE

-fw – filter words 522

-fs – filter size SIZE

Install Bitwarden to your server

Bitwarden is an open-source password manager that helps you store, manage, and share your login credentials securely. You can use it personally or as a team/organization.

To install Bitwarden on your server use next steps:

1. Update your server

sudo apt update && sudo apt upgrade -y

2. Install Docker + Docker Compose

sudo apt install docker.io docker-compose -y
sudo systemctl enable --now docker

3. Add your current user to docker group

sudo usermod -aG docker $USER

4. Go to Bitwarden Github repository: https://github.com/bitwarden/server and copy and run installation commands on your server:

curl -s -L -o bitwarden.sh \
    "https://func.bitwarden.com/api/dl/?app=self-host&platform=linux" \
    && chmod +x bitwarden.sh
./bitwarden.sh install
./bitwarden.sh start