[
From Delhi’s Barsati to India’s First Indigenous PC: The Unforgettable Genesis of HCL
New Delhi, India – [Date] – In an era devoid of startup accelerators, venture capital, and readily available bank funding, six visionary engineers in 1976 embarked on a journey that would forever alter India’s technological landscape. With a mere Rs 1.87 lakh, cobbled together from personal savings, loans, and even the sale of a car, Shiv Nadar, Ajai Chowdhry, Arjun Malhotra, Yogesh Vaidya, Subhash Arora, and D.S. Puri defied convention to establish Microcomp, the precursor to what is now globally recognized as HCL. Their initial workspace? A humble barsati in Delhi’s Golf Links.
This remarkable tale transcends the mere birth of a technology company; it chronicles the ingenious transformation of limited resources, bureaucratic hurdles, and formidable technical challenges into a fertile ground for indigenous computing innovation.
Six Engineers, Rs 1.87 Lakh, and One Big Idea
The founders shared a profound conviction: the microprocessor was poised to revolutionize computing. This belief, a rare commodity in 1970s India, formed the bedrock of their ambitious undertaking. However, translating this belief into a thriving enterprise was a monumental task. India’s technology sector was heavily regulated, demanding licenses for computer manufacturing—a prerequisite the fledgling team initially lacked. Their innovative solution involved partnering with UP Electronics Corporation, which possessed the necessary manufacturing permit, ultimately leading to the formation of Hindustan Computers Limited.
The early days were far from glamorous. Operating out of a small Delhi barsati, the team embarked on an audacious gamble: selling a computer that had yet to be fully built. Armed with brochures and mock-ups, their sales force traversed India, convincing prospective clients to invest in a product that existed more as a concept than a tangible machine. This unorthodox strategy, almost unimaginable today, yielded astonishing success. Early adopters included prestigious institutions like IIT Kharagpur and IIT Madras, whose faith validated the potential of an Indian company to conceptualize, develop, and market indigenous computing technology. This early triumph serves as a powerful reminder for aspiring innovators: true innovation often stems not from abundant resources, but from the foresight to seize an opportunity before it becomes apparent to all.
When Computers Occupied Entire Rooms
To appreciate the groundbreaking nature of HCL’s early work, one must contextualize it within the computing landscape of the time. The 1970s in India were dominated by behemoths like the IBM 1401, machines that demanded dedicated data centers and extensive air conditioning. Leasing an IBM 1401 could set a company back approximately Rs 5 lakh annually.
HCL’s answer, the HCL 8C introduced in 1978, was a paradigm shift. Priced at a more accessible Rs 3 lakh, it was compact enough to adorn an office desk and required no specialized cooling. Built around the Rockwell PPS-8 microprocessor, the HCL 8C was meticulously designed to cater to the computing needs of medium-sized businesses. Crucially, a significant portion of the system was developed by Indian engineers from the ground up. This included the design of the motherboard and input-output boards, as well as the development of the operating system, device drivers, BASIC interpreter, and Sort/Merge package. This was a remarkable engineering feat, especially considering the absence of many fundamental software development conveniences prevalent today.
No Mentor, No Modern IDE, and Barely Any Debugging Infrastructure
The development of the HCL 8C offers perhaps the most profound educational insights. The engineers operated without the luxury of modern development environments, lacking the ability to instantly write, compile, and test code. Their work was intimately intertwined with the hardware. Initially, the development system comprised little more than the Rockwell PPS-8 processor and memory. Programs were painstakingly loaded into memory byte by byte using rows of toggle switches. Imagine the ordeal of debugging software under such conditions, where a mere power fluctuation could erase a program from memory, necessitating its complete re-entry.
While the team eventually transitioned to PROM chips for a more stable approach, the fundamental challenge persisted: the hardware itself was still under development. This led to an ingenious solution: one engineer crafted a Rockwell PPS-8 simulator on an IBM 360 at the Delhi University Computer Centre. This innovation allowed software development to proceed independently of the physical HCL hardware. Further enhancing efficiency, a cross-assembler was created, enabling programmers to write code using assembly-language commands rather than the tedious direct manipulation of binary strings. For today’s computer science students, concepts like simulators, assemblers, and integrated development environments are commonplace; in the 1970s, their creation was an engineering challenge in itself.
When Debugging Meant Carrying Boxes of Punched Cards
The development process was further compounded by the primitive computing infrastructure of the era. Programs for the IBM 360 systems were submitted via 80-column punched cards, each card representing a single line of code. Engineers would meticulously prepare boxes of these cards and transport them to the Delhi University Computer Centre, submitting their jobs to a batch queue and patiently awaiting results. A single punching error could derail an entire program, forcing a resubmission. With sometimes only two runs available per day, a programming error that today would take seconds to rectify could consume hours.
This arduous process led the team to discover the less-congested IBM 360 at the Physical Research Laboratory in Ahmedabad. They would travel from Delhi, sometimes staying for a month to develop software, before returning to test it on their own system. These journeys, undertaken in third-class railway compartments, involved lugging large boxes of punched cards, punctuated by grueling 36-hour debugging sessions. The sheer patience and perseverance required, unimaginable for students accustomed to instant gratification from laptops and cloud computing, ultimately forged the HCL 8C.
The Engineering Behind India’s Early Indigenous Computer
The HCL 8C was not merely an assembly of imported components. The development team engineered much of the system themselves. The motherboard and I/O boards were designed and fabricated using discrete components, while the operating system, device drivers, BASIC interpreter, and Sort/Merge software were custom-written for the machine. Although the microprocessor and memory chips were imported, the vast majority of the development represented a monumental indigenous engineering endeavor. The software, written in efficient machine code, enabled the HCL 8C to effectively compete with far larger systems.
The rapid sales of the HCL 8C brought a new challenge: customer demand for software enhancements. With the original software stored in ROM, updates were cumbersome. The team innovated once again, adopting EPROM technology, which allowed customers to easily replace older chips with updated software versions. The old EPROMs could then be erased with ultraviolet light and reused. This seemingly technical detail underscores a fundamental truth in engineering: true innovation extends beyond the initial product, embracing the continuous cycle of improvement driven by user feedback.
What Students Can Learn from the HCL Story
The HCL narrative offers invaluable lessons for future engineers, computer scientists, entrepreneurs, and researchers:
1. Start with Curiosity, Not Perfect Resources
The founders lacked comprehensive resources, yet their idea, technical knowledge, and willingness to experiment fueled their success. The HCL story challenges the mindset of waiting for ideal conditions, emphasizing that curiosity and persistence are paramount in utilizing available resources effectively.
2. Learn Beyond the Textbook
The HCL 8C engineers navigated hardware, machine language, software, simulation, and system design simultaneously. This interdisciplinary approach is increasingly vital today, exemplified by fields like robotics and AI, where a blend of diverse knowledge areas is crucial for impactful innovation. The most potent projects often emerge from the intersections of disciplines.
3. Failure Can Become an Engineering Tool
The HCL team encountered numerous failures, from disappearing programs to faulty punched cards and hardware delays. Instead of succumbing to these obstacles, they ingeniously developed tools and processes to overcome them. The PPS-8 simulator and cross-assembler stand as testaments to transforming problems into opportunities for innovation.
4. Build for a Real Problem
The HCL 8C was not technology for technology’s sake. Its core purpose was to democratize computing for Indian businesses by offering a smaller, more affordable, and less infrastructure-dependent alternative to systems like the IBM 1401. This principle remains vital: the most impactful innovations address genuine problems.
5. Your First Workplace Does Not Determine Your Future
Starting in a barsati with limited infrastructure, the HCL founders ultimately contributed to the rise of a major Indian technology enterprise. This powerfully conveys that the current environment does not dictate the magnitude of problems one can aspire to solve.
Disclaimer: This article is based on historical accounts and inputs provided for the HCL founders and HCL 8C development; some historical details may vary across contemporary accounts.
