So, this is fun! I connected a DOS PC to a Windows XP system using a null modem cable. I can browse the web and share files!
The first thing we had to do was install a custom "null modem". Here's the config file for it, and it is also available here: github.com/cml37/dos-util…
From there, we get to add a new modem. Go to "Control Panel", then "Phone and Modem Options." Then fill in the area code, etc. if you get asked to do such!
Next, go to the "Modems" tab. Click "Add". Select "Don't detect my modem...", then "Next", then "Have Disk..." Browse to the location of mdmnull.inf that you downloaded from the previous step.
Choose "Null Modem for epppd for DOS", then "Next", then select your COM port." Then "Next", and finish out the wizard.
Next go to "Network Connections" in Control Panel. Click "Create a new connection". Choose "Set up advanced connection", then "Next". Click "Accept Incoming Connections", then "Next".
Choose "Null Modem for epppd for DOS", then "Next". Then "Do not allow virtual private connections", then "Next." For "User Permissions", just click "Next".
Click "Properties" on "Internet Protocol (TCP/IP)". At this point, I suggest specifying a range of allowed TCP/IP addresses as you see here. From there, finish out the wizard!
Okay, now for the DOS side. First, download dosppp06 and extract epppd.exe and copy it to your DOS PC, you can grab it from here: ibiblio.org/pub/micro/pc-s…
Also go and download Arachne for DOS (I actually used an older version in my first screenshot, but I think this version will be better: glennmcc.org/arachne/)
Now, connect up your null modem cable from the Windows XP PC to the DOS PC!
Next up, on the DOS PC, we are going to load epppd.exe, the DOS packet driver. Here is how I did that
And now, go ahead and run the arachne installer and launch Arachne.
Once installed and launched, Arachne will prompt you for configuration. Choose the packet wizard. Then "Detect packet driver". Then "continue".
For best success, choose "Manual setup" for the next step. Then put in the IP address of the connection, and your gateway and netmask. For the nameserver, I just used Google's (8.8.8.8).
If you need to find your IP address, you can go and look at "properties" for the "unauthenticated user" on the WinXP side, look at the "Details" tab and the "Client IP address"
So, how about file sharing? I set up a NFS server using OpenMediaVault and used the XFS DOS client. I have a video for that! You'd just want to update xfs.bat to use the epppd packet driver, that's it!
And, by the way, I also tried the above procedure using Windows 2000 and it worked too!
Two corrections: for User Permissions, you will want to choose "Guest". Then, when done with the wizard, click on the new connection, go to the Users tab, and select "Always allow directly connected devices such as palmtop computers to connect without providing a password"
See last tweet in the thread! For user permissions, need to choose "Guest"
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Let's test this Microchannel 3Com network card that I picked up for my IBM PS/2 Model 70 386 (with a 486 upgrade). Time for a quick 🧵
So, this card is a 3Com EtherLink/MC TP. As per usual, the Ardent Tool of Capitalism has a nice writeup on the card, as well as drivers! Looking at the drivers disk, it appears we have LAN Manager, NDIS, and Netware drivers. Pretty limited, but this is an older card.
Time to get this installed. And of course, this is Microchannel, so, on powerup, the PS/2 is immediately angry. I did copy the "adapter configuration file" to my PS/2 Reference disk. Running auto configure, the card gets detected, and we can see the settings. Nice!
Last week, I triaged and repaired around 20 or so LTE 5000 systems that I picked up at the System Source swap meet. Today, I spent some time swapping around parts and "making them better." Let's talk about it briefly in a 🧵 here!
By far, the most common repair needed was screen sliders, latches, casings, and bezels. I spent a fair amount of time replacing and "placing" these based on what I had in stock, or based on spare parts machines from the haul. It's the little things that count 😂
Also, I had some very "yellow" keyboards that I went ahead and swapped out with spares. Might as well!
Last week, at the System Source swap meet, I picked up a bunch of interface cards! Additionally, I have this Microchannel network card that arrived in the mail. Let's test these cards out on the Pacman PC! Time for a long 🧵
As I was thinking about which PC to use to test these, the Pacman PC ended up being ideal. Its motherboard has ISA, PCI, and AGP support! Some of you might remember this CYS Tech CYSMBD-694X motherboard that I picked up from Ali Express a little while back:
We're going to use Windows 98 SE to test. To ensure that I don't clutter my install with a bunch of driver install fun, I am going to make a backup copy of Win98SE that we will use for our purposes today.
Here's some good news for BlueSCSI/ZuluSCSI owners who want wireless networking in DOS and Win3.1x: Michael Brutman (author of mTCP) has taken my DaynaPORT DOS packet driver and greatly improved it! I'm using it to browse the web. Let's talk about how in a 🧵 here!
First, some context: several months ago, I started down the path to get my BlueSCSI working in DOS, and made a very alpha driver to do such. As per usual, I then abandoned the project 😂
Then, Michael found out about the project, and greatly improved upon it! There is a beta version that you can find here: . Although the driver is currently beta, it is very well written, and is working great for me!github.com/mbbrutman/dayn…
I had a total blast testing my newly-acquired fleet of LTE 5000 series systems! Over the past four days, I was able to make 20 working systems from my haul of (I believe) 26 systems. Let's have a BRIEF outbrief in a 🧵 here!
First, just LOOK at everything!! Everything you see here either will go in a system (HDD, FDD, CD-ROMs, battery shells), is a spare part, or a conversation piece (PCMCIA cards without dongles 😂). And, oh, for the six systems that contributed to parts, look at all of the screws!
Here are the "failed" parts. Several failed or flaky mobos. Two bad processor cards. Several bad DC to DC cards. Only one bad FDD, which is miraculous. And of course, that one keyboard that took a lot of abuse, too much to repair.
Day 4 LTE 5000 (and probably some LTE Elite!) cleanup and testing. I'll just do highlight reel, I am sure you guys have seen enough at this point 😂. Let's do this! 🧵
First, we have doubled downstream testing power 😂. Now let's talk about the system on the right...
So, as you can see, the screen is bad, but I think the effect is lowkey cool! Also, this system had a bad processor card and DC to DC card. That's been fixed. The HDD caddy had the logic board for a HDD and was missing the cover. Someone has been in here!!