Build your own RAM: Upgrading an ancient 386 PC to 64MB RAM using custom-built memory

zohaibahd

Posts: 378   +5
Staff
WTF?! If you're a vintage computer enthusiast stuck in the era of 30-pin SIMMs, your memory upgrade options are rather limited. But one enterprising YouTube channel has now shown how to super-size ancient 386 systems to a 'jaw-dropping' 64 megabytes of RAM.

YouTuber Bits and Bolts has created a step-by-step guide for building custom 16MB 30-pin SIMM modules from off-the-shelf components. While that may not sound earth-shattering in 2024, it's a game-changer for a 386DX machine from the '80s.

Let's rewind to the 386 era when 30-pin SIMMs reigned supreme as the memory standard. A typical Windows 3.1 setup needed just 1MB to skate by, often reached using four 256KB sticks. As computing demands increased, 1MB modules became the norm.

Fast forward to Bits and Bolts' ambitious project. After previously modding 30-pin SIMMs to hit 32MB using a clever hack, the maker wanted to blow past that ceiling. The goal was to create 16MB SIMMs, which was the maximum supported by the 30-pin standard, to significantly boost the 386's memory capacity.

Pulling this off required quite some engineering skills. Bits and Bolts first had to verify his specific 386 motherboard could actually handle that much RAM when maxed out. He learned that he could but only if four of the board's eight slots were used. He had hoped to touch the 128MB mark, but 64MB would have to do for now.

The process wasn't without its hurdles. The biggest was sourcing affordable, reliable 16MB 30-pin SIMMs, which are either extremely pricey vintage components or sketchy used modules of unknown quality. Bits and Bolts also had to carefully hack the modules to allow switching between older Fast Page Mode (FPM) and newer Extended Data Out (EDO) RAM modes for compatibility.

After assembling the modules and installing them on the 386 motherboard, the system successfully booted with 64MB of memory. The author tested the memory using Memtest86+, which took 10 hours to complete one pass. A thermal camera and oscilloscope were used to monitor the temperature and voltages of the modules, confirming their stability and safety.

It's all quite remarkable for a nearly four-decade-old system. But Bits and Bolts isn't done yet and has already set his sights on the next target, which is upgrading newer 486 systems beyond their typical ceilings.

Permalink to story:

 
Back in the day...buddy of mine and myself HARD WIRED a memory board to add I think it was
a megabyte to a computer. Then we spent hours troubleshooting our wiring, but it worked!
 
This was not unknown.

There where folks who soldered additional EDO RAM at the back of the often cheap sticks, and thus increasing or even doubling the size of the sticks.

But if I'm correct after a certain amount of megabytes of ram no longer that would be properly cached and thus make it slower. I was toying around with a 386 in my very youth as well and noticed that beyond 16MB things actually got slower rather then equal or better.
 
That beautiful 386 board he has excites me a lot more than the RAM. I have one working 386 and know how scarce they are nowadays!
 
This was not unknown.

There where folks who soldered additional EDO RAM at the back of the often cheap sticks, and thus increasing or even doubling the size of the sticks.

But if I'm correct after a certain amount of megabytes of ram no longer that would be properly cached and thus make it slower. I was toying around with a 386 in my very youth as well and noticed that beyond 16MB things actually got slower rather then equal or better.
It's not that it was slower, it's just that the cache simply didn't take into account the extra memory, so data accesses in the upper memory spaces weren't cached, I think. Also, how the CPU addressed those spaces. That's why "appropriate" limits were established for different CPUs and cache amounts at the time, more or less up to the Pentium 3. It also happened that some games and programs didn't play very well with large amounts of memory, even failing to start.
 
That beautiful 386 board he has excites me a lot more than the RAM. I have one working 386 and know how scarce they are nowadays!
I have one cute and small with a soldered 386SX, but also restoring another one, a lot better, but VERY damaged by a leaky battery. I want to use a TI486DLC/40 with that one
 
Last edited:
It's not that it was slower, it's just that the cache simply didn't take into account the extra memory, so data accesses in the upper memory spaces weren't cached, I think. Also, how the CPU addressed those spaces. That's why "appropriate" limits were established for different CPUs and cache amounts at the time, more or less up to the Pentium 3. It also happened that some games and programs didn't play very well with large amounts of memory, even failing to start.

However, a 386 using dos or ancient W3.11 you could ramp up smartdrive.


4MB of caching.
 
However, a 386 using dos or ancient W3.11 you could ramp up smartdrive.


4MB of caching.
It could also be seen how to use FlexMode currently.
-this example, let's say, only caches up to 8MB of the 64MB.
-modern example with FlexMode, only 16GB of the 24GB installed work in dual channel.
The performance gain is up to where the hardware definition says.
 
Last edited:
I have one cute and small with a soldered 386SX, but also restoring another one, a lot better, but VERY damaged by a leaky battery. Want to use a TI486DLC/40 with that one
Ha! I also have a lone Cyrix Cx486DLC-40 myself. Being a purist, I just CANNOT put it into that 386 board!
 
It could also be seen how to use FlexMode currently.
-this example, let's say, only caches up to 8MB of the 64MB.
-example with FlexMode, only 16GB of the 24GB installed work in dual channel.
The performance gain is up to where the hardware definition says.

You cant use 16GB in a 386 lol. 386 has a limit of 4GB. And getting 4GB in sticks in ancient 386's is quite challenging or likely impossible.
 
You cant use 16GB in a 386 lol. 386 has a limit of 4GB. And getting 4GB in sticks in ancient 386's is quite challenging or likely impossible.
bro, that example in NOT with a 386...
I don't understand how you can think that..
To begin with, the term "dual channel" should have meant something to you, right?
 
I thought the 386 only had 24 bits of address lines attaches, that it could only address 16MB? (32-bit virtual address space, 4GB, but 24 bit physical.) I'm surprised this worked at all! Very cool!

(Oh... per Google, the 386sx chopped the address lines to 24 bit addressing; the 386DX had the proper 32 so it could theoretically access the full 4GB. I mean, in theory, I doubt anyone made a board with the 256 SIMM slots you'd need to do so LOL.)
 
Back