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
Happy #MARCHintosh! My virtual Quadra 800 and Compaq LTE 5100 (via PC MacLAN for Windows) are once again participating. You can even print to my Panasonic KX-P2123 printer that is "pretending" to be an Apple LaserWriter 😂. All via GlobalTalk!
If you want to join in on the fun virtually:
* Details for joining GlobalTalk here:
* Once you get access to the spreadsheet, see the Instructions/Links tab. See Line 36 for my setup guide for Windows 11, I used that together with the Debian guide!marchintosh.com/globaltalk.html
There is also a way to get a configuration file of all of the participants via AIRConfig, which is also discussed in the guide! Need to get AIRConfig to your virtual Macintosh? Use a FTP server!
Oookay, the Compaq Presario 5528 is back on the desk! I wanted to spend some more time looking at the MPEG-1 decoder card under Windows 95 OSR 2.5. And I have good news! Time for a quick 🧵
As some may recall, here was the next thing I was going to try: copying over the Windows 95A Media Player to Windows 95 OSR2.5. But as it ends up, that wasn't necessary!! I'll explain.
I noticed something on my Win95 OSR 2.5 install. It looks like the Internet Explorer desktop update installed ActiveMovie Control. And it looks like it is using a default Microsoft software decoder. HOWEVER, notice that standard Windows Media Player is also installed!
Well, looks like we have some modems to test. We better get going 😂. I'm not going to do a full "dial" test, but we will see if we can at least configure them! Time for a 🧵
First things first, just like they taught in science class, always start with a baseline! So, I am going to make a copy of my Windows 98 installation so that we don't foul up the main install, and we'll check out device manager. Looking good! Let's roll.
First modem out the gate is this Creative Modem Blaster V.90 PCI DI5655. We are going to use the Pacman PC to do the testing since it has a very convenient shared ISA/PC slot. In it goes!
My new old stock Tandy 1000 SX is now all configured! As mentioned earlier, I'm going to made a video about it at SOME point. But let's talk about the fun I had today with getting it set up. Was setup 100% trouble free? No. But was it the Tandy's fault? Also, no. Time for a 🧵
The first thing I did was to populate this gorgeous motherboard with a full 640K RAM, and also popped in a NEC V20 processor for the 8088. Flawless! No issues whatsoever with this!
Next up, I jammed in some cards. Network. XTIDE. Multi I/O. Real Time Clock. On boot, we see the XTIDE option ROM screen, so we are now cooking!
Well, after spending way too much time this weekend trying to get my MPEG-1 decoder working on the Presario 5528 from a fresh Windows 95 install, I finally was successful. Let's talk briefly about it in a 🧵 here!
So, first some background: what's the story with MPEG-1 decoders? Well, back when PCs weren't quite powerful enough to play full-motion video, hardware options like this were popular. This machine has a S3 Scenic/MX2 (86C443) chip to do just that.
For this particular system, this chip pairs with an S3 Trio64V+ (8C765) via the S3 Scenic Highway bus. That said, it's fair to say that MOST S3 Trio64V+ cards did NOT pair with a Scenic/MX2, as this MPEG-1 option chip seemed to be FAIRLY short lived.