RetroTech Chris Profile picture
Jan 4 11 tweets 6 min read Read on X
Let's take a few minutes and look at this newly written Modern Generic SVGA driver for Windows 3.1. We'll check it out in Oracle VM Virtualbox 5.2.44 first in a 🧵 here (I do plan to try real hardware next!) Image
Image
Image
First, I will say this is off to a GREAT start. The author has done a nice job at logging some of the issues that are present... and this driver has A LOT of promise! Image
Installation is pretty easy! Copy over vbesvga.drv and vbevdd.386 that you can download from the releases page of the project to your windows\system directory: github.com/PluMGMK/vbesvg…Image
From there, you have to modify system.ini in your windows directory. I updated the video driver, added the right file under the 386 Enhanced section, and also added a special section for the driver itself. I started out with some pretty ambitious defaults 😂 Image
Image
Image
I noticed on first fire up that the .386 driver name didn't quite match the instructions, so I renamed it. Image
Alright, here we go. Looks like my settings were a little ambitious 😂. Let's scale down to 1024x768 with a depth of 16 Image
Image
Hey, look at that! Colors are rich! A few observations:
1) the "stray green lines" are a common bug with network file sharing and some vid drivers, we can turn that off.
2) Perf is a little slow, but WOW, this is a GREAT start
3) Something is up with the MS office logo bkgrnd. Image

Image
Another issue, and this is a known one: switching back to full screen from DOS windows has issues. I have the same problem with the standard "SVGA256 VESA patch" that I use with Win 3.1x, so this is parity as far as I am concerned.
How about 8 bit color depth? Well, it's a little more nuanced, but I am sure it will get there! Image
For comparison, this is what the virtual machine looks like with the "SVGA VESA Patch". There are a couple versions of the patcher that are mentioned here: forums.virtualbox.org/viewtopic.php?…
Anyway, that's my first take! I look forward to having a look as this progresses. And, yes, I think I will get out some real hardware next! You can also read more details about the project here:

@threadreaderapp unroll github.com/PluMGMK/vbesvg…Image

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with RetroTech Chris

RetroTech Chris Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @RetroTechChris

Jan 4
We're going to reach "Productivity Level 1000" in Windows 3.11 for Workgroups with this newly-developed
Win3.1 video driver, now running on my eMachines T2341. Let's talk about it in a 🧵 here! Image
Image
Image
So, for starters, I learned about this driver today, and tried it in virtualization. I wanted to try it on real hardware too!
To get things started, I booted Windows 98 to see what the "max" video resolution would be for this card. And it looks to be 1600x1200. Okay! So, I set the parameters accordingly using the same manner discussed in my earlier thread. Image
Image
Read 8 tweets
Jan 2
Haha, oops. I'm testing out the LTE 5000 fleet, and it looks like I gave two of them the same name 😅. I renamed one system, but I bet it will take a router reboot to fix this! Image
Image
Image
Image
Actually, wait a minute! Why the hell did I harcode the IP address? I bet that I did that and cloned it, probably was having some issue. Okay, easy fix 😂 Image
Ugh, maybe not. Okay, this system has been flaky, I think I'm going to reload Win3.11 on it Image
Read 23 tweets
Dec 26, 2024
I have some updates on my Windows 3.1 16-bit NABU Application, and also on my 486 DX2/66 which I wanted to get in a position to drive the NABU. Let's do a quick 🧵 Image
Image
So, first, for the 486, I got a 9 pin connector that follows the right standard to work with this system. My DTC controller card uses the DTK standard. I installed in the bottom slot. We talked about different serial connector standards here: Image
As for the application, I added support to download files from the Internet to feed the NABU! The website has to be HTTP (I don't support HTTPS/SSL), but it works well! Files get cached locally and don't get downloaded again if present on disk. Image
Image
Image
Read 4 tweets
Dec 24, 2024
It's not every day that I write a Windows 3.1 16-bit application, but yesterday was one of those days 😂. Let's talk about it, and discuss the NABU a bit, in a 🧵here. Image
Image
Image
So, a few days ago, I mentioned that I was getting my 486 ready to run something, and that I needed an extra serial port. And then I disappeared for a few days 😅.
Well, that "something" is the NABU software adaptor, which is needed to run the NABU, since NABU originally ran over the cable network. There are several great options out there for modern machines, with the flagship one being available here: nabu.ca
Read 18 tweets
Dec 21, 2024
I'm getting this 486 DX2/66 ready to do an activity that will require two serial ports. However, when I went to connect up a second serial device, it wasn't getting detected. However, the IDC cable is not defective, and the serial port is good. What could be wrong? 🧵 time! Image
Image
The issue? When it comes to these serial connectors, there are actually two different standards! There is AT-Everex, and DTK/Intel. If you get a multimeter out, you can figure out what type of connector you have! Image
Image
And, apparently my DTC 2278 controller uses the DTK/Intel standard. And perhaps the manual for this card would flag that, not sure. We do have this jumper setting guide, it doesn't say anything about it, but that is not surprising. Image
Image
Read 4 tweets
Dec 20, 2024
I had a bunch of 512KB PDSO40 chips (used for video memory upgrades) laying around and decided to go around and upgrade some of my PCs. Somehow, 3 of the 4 I upgraded ended up being Packard Bells 😂. And I used up my spare chips, so that is good! Let's look at it in a 🧵 here! Image
Image
Image
Image
First, I upgraded the Western Digital video card in my 486 DX2/66 that we have see a lot of lately. Unfortunately, this doesn't give me any additional useful video modes. If I try to bump to high color for 1024x768, it bumps me down to 256 colors. Oh well. I'll leave it 🤷‍♂️ Image
Image
Image
Image
Next up was the Packard Bell Legend 305CD. And, wow, this did help, let's talk about how... Image
Image
Image
Image
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(