VOGONS


First post, by Orkay

User metadata
Rank Member
Rank
Member

I got an Intel EtherExpress 16 with a RPL ROM chip, so now I'm using that to experiment with the elusive Remoteboot service in Windows NT Server. RPL is an intriguing precursor to PXE that's not well documented in modern years, but I'm hoping to change that in time.

20160709_055041.jpg

When a workstation is not yet configured to boot using the Remoteboot server, an adapter record is created in the Remoteboot Manager which can be converted into a workstation record; thus the administrator doesn't need to know the MAC address of the NIC.

VNC_Remoteboot.png

Following the overwhelming documentation in the Windows NT Server Resource Kit, I copied an existing installation of MS-DOS 6.22 to the appropriate directory, ran rplenabl.exe on the client, and restarted to boot from the network card.

20160709_060941.jpg
20160709_060959.jpg

So far, I've got a rather barebones MS-DOS 6.22 profile set up. The virtual hard drive provided is read-only the way I have things set up now, but it almost seems like it's possible to make it writable in order to fine-tune profiles. Maybe not. 😒 Either way, I'll make occasional progress updates as I struggle to further understand this mysterious portion of retro networking. Reading Microsoft's seemingly mishmash documentation on this sure explains that Sun Microsystems commercial with the scuba diver's system failure!

Reply 2 of 6, by Orkay

User metadata
Rank Member
Rank
Member
h-a-l-9000 wrote:

It also worked with Windows 95 (many years ago).

Yes, that's what I'm hoping to get working on here as well, either for installing Windows 95 over the network (which I did similarly with a network client floppy disk) or having it run a Windows 95 environment that resides on the server.

Reply 3 of 6, by chinny22

User metadata
Rank l33t
Rank
l33t

This looks really cool! I never even knew this existed till now, look forward to seeing how it all works

Reply 4 of 6, by ynari

User metadata
Rank Member
Rank
Member

By the time NT 4 came around, RPL was already on the wane. It'd been part of previous versions of NT, Lan Server (OS/2), and Lan Manager for years.

NT 4 introduced a specific Terminal Server version, and the ability to run programs remotely, rather than download a whole operating system locally to run reduced RPL's usefulness. Obviously they're useful for different purposes, though.

Also DHCP/Bootp are generally easier to use and included by default in many network adapter's firmware. I've used those a number of times to install operating systems on devices with no removable media, where they're located somewhere physical access is awkward.

Reply 5 of 6, by hyoenmadan

User metadata
Rank Member
Rank
Member

RPL was killed together with Netware, as it was a feature and which was used primarly by Netware diskless workstation citizens. RPL is almost an anecdotal chapter in NT world, purposely made to compete with Netware in the disk less station world. As soon as DHCP/PXE, a better alternative, was available over a normal TCPIP architecture, RPL was finally displaced completely.

Reply 6 of 6, by brassicGamer

User metadata
Rank Oldbie
Rank
Oldbie

I, also, had never heard of it and, functionality-wise, it provides a number of advantages over something like RIS, which I think can only be adapted to deploy as low as Win98, but not < 95. It's quite well documented here, it seems.

I'm going to have a go at this myself. I'm looking to set up a gaming LAN, and had the idea of using one software image that I could deploy to 3 or more computers, all running DOS (Pentium II-class machines). In principle this would make the process of keeping the image consistent a lot easier!!

Check out my blog and YouTube channel for thoughts, articles, system profiles, and tips.