In 2004, a blogger explored creating a striped RAID array using four USB floppy drives under OS X. Driven by curiosity and a desire for slightly faster floppy access, they used the then-available Disk Utility to create a RAID 0 set. While the resulting "RAID" technically worked and offered a minor performance boost over a single floppy, the setup was complex, prone to errors due to the floppies' unreliability, and ultimately impractical. The author concluded the experiment was more of a fun exploration of system capabilities than a genuinely useful storage solution.
Microsoft's older USB mice often included a small USB-to-PS/2 adapter. This adapter wasn't just a passive wiring converter; it contained active circuitry that translated USB signals into PS/2 signals. This allowed the mouse to function on computers with only PS/2 ports, and importantly, enabled support for the "Wake-on-Mouse" feature in some systems, which required a PS/2 connection. The adapter effectively made the USB mouse appear as a PS/2 device to the computer's BIOS, enabling this functionality even on motherboards lacking USB wake support. Therefore, discarding the seemingly insignificant adapter meant losing the potential for wake-on-mouse capabilities.
Hacker News users discuss the intricacies of the Microsoft USB-to-PS/2 adapter, focusing on its active conversion of USB signals to PS/2 rather than simple pin mapping. Several commenters praise the adapter's sophistication, highlighting its ability to handle higher polling rates than standard PS/2 and even emulate multiple PS/2 devices from a single USB port. Some express surprise at learning this detail, having previously assumed passive conversion. Others reminisce about similar PS/2 to serial port adapters, while some debate the technical challenges and cleverness of the implementation. The discussion touches on the historical context of transitioning between these technologies, the complexities of bidirectional communication, and the surprising amount of intelligence packed into this seemingly simple adapter.
Ken Shirriff created a USB interface for a replica of the iconic "keyset" used in Douglas Engelbart's 1968 "Mother of All Demos." This keyset, originally designed for chordal input, now sends USB keystrokes corresponding to the original chord combinations. Shirriff's project involved reverse-engineering the keyset's wiring, designing a custom circuit board to read the key combinations, and programming an ATmega32U4 microcontroller to translate the chords into USB HID keyboard signals. This allows the replica keyset, originally built by Bill Degnan, to be used with modern computers, preserving a piece of computing history.
Commenters on Hacker News largely expressed fascination with the project, connecting it to a shared nostalgia for early computing and the "Mother of All Demos." Several praised the creator's dedication and the ingenuity of using a Teensy microcontroller to emulate the historical keyset. Some discussed the technical aspects, including the challenges of replicating the original chord keyboard's behavior and the choice of using a USB interface. A few commenters reminisced about their own experiences with similar historical hardware, highlighting the significance of preserving and interacting with these pieces of computing history. There was also some discussion about the possibility of using this interface with modern emulators or virtual machines.
This project demonstrates a workaround for Firefox's lack of WebUSB support by leveraging its native messaging capabilities. A small native application acts as a bridge, receiving commands from a web page via native messaging and interacting directly with USB devices. The web page communicates with this intermediary application using a custom, WebUSB-like JavaScript API, effectively emulating WebUSB functionality within Firefox. This allows web developers to write code that interacts with USB devices in a consistent manner across browsers, handling the Firefox difference behind the scenes.
Hacker News commenters generally expressed frustration with Firefox's lack of WebUSB support, echoing the author's sentiments. Some pointed out that the Mozilla Developer Network (MDN) documentation misleadingly suggests WebUSB is supported, while others shared workarounds and alternative solutions, including using Chrome or a native messaging host. A few commenters questioned the security implications of granting websites access to USB devices, highlighting potential vulnerabilities. The complexity of adding WebUSB support in Firefox was also discussed, citing issues like sandboxing and driver interaction as potential roadblocks. One commenter offered a personal anecdote about the challenges of debugging WebUSB issues due to inconsistent browser implementations.
ACCESS.bus, developed by ACCESS Co., Ltd., was a short-lived attempt to create a low-cost, low-power alternative to USB in the late 1990s, primarily for connecting peripherals like keyboards and mice. Leveraging the already established I²C protocol, it aimed for simplicity and minimal hardware requirements. Despite backing from major Japanese manufacturers and some limited adoption in devices like digital cameras and PDAs, ACCESS.bus ultimately failed to gain significant traction against the rapidly growing dominance of USB, fading into obscurity by the early 2000s. Its failure was largely due to USB's broader industry support, superior performance for higher-bandwidth devices, and its eventual standardization and adoption across diverse platforms.
Several Hacker News commenters discussed ACCESS.bus's technical merits compared to USB. Some argued that while ACCESS.bus offered advantages like cheaper connectors and isochronous data transfer crucial for audio, its downfall was due to poorer marketing and industry support compared to the Intel-backed USB. Others pointed out that ACCESS.bus's use of a 7-bit addressing scheme limited it to 127 devices, a significant constraint compared to USB's much larger capacity. The conversation also touched upon the complexity of ACCESS.bus drivers and its apparent susceptibility to noise, alongside its prevalence in specific niches like high-end audio equipment in Japan. A few commenters reminisced about using ACCESS.bus devices and noted the lack of readily available information about the technology today, contributing to its "forgotten" status.
This post details how to access the Qualcomm Quectel BG96 modem embedded within the RAK5010 WisBlock Core module via USB. The BG96 exposes multiple serial ports over USB, but only one is typically configured for user interaction. The post explains how to use minicom to interact with the modem on its default port and outlines the process of switching to other ports, specifically the diagnostic port, using AT commands. This access allows for deeper interaction with the modem, enabling activities like firmware updates and more granular control, which are not possible through the default port. The author emphasizes the importance of switching back to the default port after completing tasks on the diagnostic port to restore normal functionality.
Several commenters on Hacker News discussed practical aspects of using the RAK5010 and similar devices. Some questioned the practicality of USB tethering for IoT applications, citing power consumption concerns and suggesting alternative solutions like direct TCP/IP connections over cellular. Others shared personal experiences and insights, including one commenter who detailed their success using the RAK7200 with a Quectel modem and another who noted the complexities and lack of clear documentation around AT command interactions for specific modem features. A few comments also touched upon the security implications of exposing the modem via USB, particularly in commercial deployments. The overall sentiment reflected interest in the technical details but also a pragmatic awareness of the challenges involved in this approach.
The Flea-Scope is a low-cost, open-source USB oscilloscope, logic analyzer, and arbitrary waveform generator. Designed with affordability and accessibility in mind, it utilizes a Cypress FX2LP microcontroller and features a minimalist design detailed in a comprehensive, publicly available PDF. The document covers hardware schematics, firmware, software, and usage instructions, enabling users to build, modify, and understand the device completely. The Flea-Scope aims to be a practical tool for hobbyists, students, and professionals seeking a basic, yet versatile electronic test instrument.
Commenters on Hacker News generally praised the Flea-Scope for its affordability and open-source nature, finding it a compelling option for hobbyists and those needing a basic tool. Several pointed out its limitations compared to professional equipment, particularly regarding bandwidth and sample rate. Some discussed potential improvements, including using a faster microcontroller and enhancing the software. The project's use of a Cypress FX2 chip was highlighted, with some expressing nostalgia for it. A few users shared personal experiences using similar DIY oscilloscopes, and others questioned the practicality of its low bandwidth for certain applications. The overall sentiment was positive, viewing the Flea-Scope as a valuable educational tool and a testament to what can be achieved with limited resources.
This blog post from 2004 recounts the author's experience troubleshooting a customer's USB floppy drive issue. The customer reported their A: drive constantly seeking, even with no floppy inserted. After remote debugging revealed no software problems, the author deduced the issue stemmed from the drive itself. USB floppy drives, unlike internal ones, lack a physical switch to detect the presence of a disk. Instead, they rely on a light sensor which can malfunction, causing the drive to perpetually search for a non-existent disk. Replacing the faulty drive solved the problem, highlighting a subtle difference between USB and internal floppy drive technologies.
HN users discuss various aspects of USB floppy drives and the linked blog post. Some express nostalgia for the era of floppies and the challenges of driver compatibility. Several commenters delve into the technical details of how USB storage devices work, including the translation layers required for legacy devices like floppy drives and the differences between the "fixed" storage model of floppies versus other removable media. The complexities of the USB Mass Storage Class Bulk-Only Transport protocol are also mentioned. One compelling comment thread explores the idea that Microsoft's attempt to enforce the use of a particular class driver may have stifled innovation and created difficulties for users who needed specific functionality from their USB floppy drives. Another interesting point raised is how different vendors implemented USB floppy drives, with some integrating the controller into the drive and others requiring a separate controller in the cable.
The Steam Brick is a conceptual handheld gaming PC designed for minimalism. It features only a power button and a USB-C port, relying entirely on external displays and controllers. The idea is to offer a compact and portable PC capable of running Steam games, shifting the focus to user-chosen peripherals rather than built-in components. This approach aims to reduce e-waste by allowing users to upgrade or replace their peripherals independently of the core computing unit.
HN commenters generally found the Steam Brick an interesting, albeit impractical, project. Several discussed the potential utility of a dedicated Steam streaming device, particularly for travel or as a low-power alternative to a full PC. Some questioned the choice of using a Raspberry Pi Compute Module 4, suggesting a Rockchip RK3588 based device would be more powerful and efficient for video decoding. Others highlighted the project's complexity, especially regarding driver support, and contrasted it with commercially available options like the Steam Deck. A few appreciated the minimalist aesthetic and the focus on a single, dedicated function. There was also some discussion of alternative software options, such as using a pre-built Steam Link OS image or exploring GameStream from Nvidia. A significant point of discussion revolved around the lack of a hardware reset button, with many suggesting it as a crucial addition for a headless device.
Summary of Comments ( 7 )
https://news.ycombinator.com/item?id=43699301
Hacker News users reacted with a mix of nostalgia and amusement to the 2004 article about creating a striped RAID array from USB floppy drives. Several commenters reminisced about the era's slow transfer speeds and the impracticality of the setup, highlighting the significant advancements in storage technology since then. Some appreciated the ingenuity and "mad science" aspect of the project, while others questioned its real-world usefulness. A few pointed out the potential data integrity issues with floppy disks, making the RAID setup even less reliable. The dominant sentiment was one of lighthearted appreciation for a bygone era of computing.
The Hacker News post titled "USB Floppy Disk Striped RAID Under OS X (2004)" links to a archived blog post about creating a striped RAID array using USB floppy drives. The discussion on Hacker News is fairly brief, consisting of only a few comments, and doesn't delve deeply into the technical aspects.
One commenter expresses amusement and nostalgia, calling it "peak 2000s," highlighting the era's fascination with pushing the boundaries of then-current technology, even if the results were impractical. They also mention how the project embodies the hacker spirit of playful experimentation.
Another comment points out the absurdity of the setup in terms of performance, noting that the combined throughput of multiple floppy drives would still be incredibly slow compared to even a single hard drive of the time. This comment underscores the impracticality of the project while still acknowledging the ingenuity and entertainment value.
Finally, a commenter reminisces about the era of modifying and experimenting with hardware, contrasting it with the more locked-down nature of modern devices. This comment adds a layer of reflection on how technology has evolved and the changing landscape of user involvement with hardware.
In summary, the comments are primarily focused on the nostalgic and humorous aspects of the original blog post, reflecting on the ingenuity and sometimes impractical nature of early 2000s tech experimentation. There is no substantial technical discussion or debate in the comments.