Recent Posts

31

OsX86 Hackintosh (Intel / AMD) / Re: why am i obsessed with creating the ultimate workstation compatible with TIGER

« Last post by chrisNova777 on April 09, 2026, 04:51:01 PM »

so what is really practical in my pursuit of excellence on my ultimate tiger workstation build project. the X5000 series chipset, w/ working ACHI SATA support on all sata ports, and more bandwidth for expansion slots via PCI-X + PCI-E combined, while still maintaining a 1-2 conventional pci slots and also bringing to the table dual processors and the abilty for tiger to address more than 4gb of RAM via PAE are all of these points true? i could use 6 core 12 thread processors for 12 cores + 24 threads total, and have enough sata port to operate 2 RAID 0 SSDs and have a few sata ports left over for archival drives (that still work at sata2)

Gemini said
Building an "Ultimate Tiger" workstation around the Intel X5000 (Blackford) chipset is a high-ambition move. While this platform was the backbone of the original Mac Pro (1,1 and 2,1), there are several technical nuances regarding how OS X 10.4.11 handles this specific hardware.

Here is the breakdown of your points versus the reality of a Tiger-era build:

1. Dual Processors and Core Counts
While the X5000 chipset supports dual LGA 771 sockets, Tiger has a strict SMP (Symmetric Multiprocessing) limit.

The Reality: Mac OS X Tiger (10.4.x) is limited to handling 8 logical cores.

If you install two 6-core/12-thread CPUs (24 threads total), Tiger will likely kernel panic or simply fail to address anything beyond the first 8 threads.

The Sweet Spot: Use two Quad-Core CPUs (like the SLAED/X5365) for a total of 8 physical cores. This is the absolute ceiling for Tiger’s stability and performance.

2. RAM and the 4GB Limit (PAE)
This is a common point of confusion. While the X5000 chipset and Xeon processors support PAE (Physical Address Extension), OS X handles it differently than Windows or Linux.

The Reality: On 32-bit Tiger (which most Hackintosh builds are, unless using very specific 64-bit kernel flags on supported hardware), individual applications are still limited to a 4GB address space.

The OS can technically see more than 4GB if the hardware and kernel support it, allowing you to run multiple apps that each use 4GB, but the overhead and stability on non-Apple X5000 boards can be temperamental. For "Ultimate Tiger," 8GB or 16GB of fully buffered DIMMs (FB-DIMMs) is plenty; going higher often yields diminishing returns or boot failures.

3. Expansion Bandwidth: PCI-X + PCI-E
The X5000 is unique because it bridges the gap between legacy workstation power and the "modern" era.

True: You get the massive bandwidth of PCI-Express for your GPU (typically a flashed Radeon X1900 XT or 7800 GTX for Tiger) while keeping PCI-X slots for high-end SCSI cards or early SATA controllers.

Note: Ensure your specific board has a physical bridge chip for those "conventional" PCI slots, as some server boards shifted entirely to PCIe/PCI-X.

4. AHCI and SATA Support
Tiger's native support for AHCI is one of its "weakest" links compared to Leopard.

The Reality: While the X5000/ESB2 southbridge supports AHCI, getting Tiger to recognize all ports as AHCI often requires specific kext patches (AppleAHCIPort.kext).

Without these, the ports may default to "IDE mode" (PIIX), which disables NCQ and limits SSD performance.

RAID 0 SSDs: Doing a software RAID 0 within Disk Utility is practical and very fast, but ensure your SATA controller is identified as a built-in device to allow for a bootable RAID array.

Practical Recommendation for "Excellence"
If you want the most stable, high-performance Tiger experience on this chipset:

CPUs: Stick to Dual Quad-Core (8 cores total). Tiger feels "complete" at 8 cores; 12+ is territory for Leopard or Snow Leopard.

Storage: Use a dedicated PCI-X or PCIe SATA II/III card (like a flashed Sil3124 or an LSI Logic card) for your RAID 0 array. This offloads the work from the southbridge and usually provides better driver stability than the onboard ESB2 ports.

RAM: Aim for 8GB of FB-DIMM. It’s enough to max out Tiger's capability without hitting the stability ceiling of the memory controller.

This setup would effectively be a "Super Mac Pro 2,1"—the fastest possible hardware environment that 10.4.11 was ever designed to inhabit.

32

OsX86 Hackintosh (Intel / AMD) / FORCING 32bit mode kernel in lion will allow quadruple boot all 4 os

« Last post by chrisNova777 on April 08, 2026, 08:20:39 PM »

being able to properly + effecively run all different os on one machine :
10.4.11
10.5.8
10.6.8
10.7.5

that is of great value to a studio computer that has alto of different software to use. makes it a swiss army knife  so to speak.

For a "Best Case Tech" (BCT) approach to a triple-booting (or quadruple-booting) monster that covers the golden era of OS X (10.4–10.6, and potentially 10.7) (the last of the 32bit OSX versions) , the goal is to minimize emulation and maximize native binary execution.

Since you are already leveraging the 975X/ICH7R and 7600 GT, you have the foundation. Here are the specific instructions to take that build to 100% compatibility.

1. The Bootloader Strategy (Chameleon/iB00t over OpenCore)
While OpenCore is the modern standard, for a build targeting Tiger (10.4.11), the "Best Case" is often Chameleon or Chimera.

Why: These legacy bootloaders handle the 32-bit handoff for Tiger and Leopard much more gracefully than OpenCore, which is primarily designed for 64-bit UEFI environments.

Instruction: Use a multi-partition GUID scheme on a single SATA SSD. Install Tiger first, followed by Leopard, then Snow Leopard. Chameleon can then manage the triple-boot menu with "period-correct" Apple icons.

2. Lion (10.7) Compatibility: The "Bridge" Version
You mentioned interest in 10.7. Here is the reality for your hardware:

The Good News: Lion (10.7.5) still includes legacy support for the Core 2 Duo (E8600) and the 7600 GT.

The Catch: 10.7 was the first "64-bit only" kernel by default. However, your 7600 GT drivers are 32-bit.

Instruction: To run 10.7 with full graphics acceleration on a 7600 GT, you must force the kernel into 32-bit mode at boot using the flag arch=i386. Without this, you will have a 64-bit OS with zero GPU acceleration (laggy UI).

3. Audio & Networking (The "No-Kext" Goal)
To keep the system "100% compatible," you want to avoid "VoodooHDA" (which can be unstable).

Audio: Look for a motherboard with the Realtek ALC882, 883, or 888. These have the best "Legacy AppleHDA" patches that provide native-like audio across all four versions.

Networking: Use a Marvell Yukon 88E8053 or Intel Pro/1000 PCIe card. These were used in real Macs of that era, meaning the drivers are built into the OS (AppleYukon2.kext).

4. Essential BIOS & Hardware Tweaks
For the most stable cross-version experience:

SATA Mode: Must be AHCI. If your 975X board has "IDE Combined Mode," turn it off. OS X 10.4.11 Intel expects pure AHCI.

HPET: Enable "High Precision Event Timer" in BIOS and set it to 64-bit mode (even for 32-bit OS versions). This prevents the "Waiting for Root Device" and CMOS reset bugs.

FireWire: If your board has a TI (Texas Instruments) FireWire chip, keep it! It’s natively supported and vital if you plan on using legacy audio interfaces like the Digi 002.

5. Partitioning for Longevity
Since you're managing 4 versions of OS X:
| Partition | OS Version | Primary Use Case |
| :--- | :--- | :--- |
| P1 (20GB) | 10.4.11 | Legacy PowerPC apps (Rosetta) / Logic 7. |
| P2 (30GB) | 10.5.8 | Bridge OS for software that needs Intel but old UI. |
| P3 (40GB) | 10.6.8 | The "Daily Driver" for stability/Rosetta. |
| P4 (40GB) | 10.7.5 | iCloud support (minimal) and final 32-bit app support. |

Summary for the "Best Case"
Stick with the E8600 CPU; it is the fastest dual-core that Tiger can comfortably "understand" without needing complex kernel patches. By staying with the 7600 GT and forcing 32-bit mode in Lion, you will have a machine that feels like a genuine Apple workstation from 2007, but with the speed of 2012-era hardware.

33

OsX86 Hackintosh (Intel / AMD) / Re: triple booting tiger, leopard + snow leopard on the same machine? native gpu....

« Last post by chrisNova777 on April 08, 2026, 08:16:16 PM »

Combining the 975X Express Chipset with the ICH7R Southbridge and a 7600 GT is essentially the "Golden Path" for a mid-2000s Hackintosh. It’s the closest you can get to the DNA of the original Mac Pro 1,1 and the Late 2006 iMacs.

Here is why that specific hardware trio makes the installation process feel almost like a native Mac experience:

1. The 975X/ICH7R: Native Identity
The Intel 975X was the high-end enthusiast chipset during the Intel transition. Because Apple used the 975X in the first Mac Pro, OS X treats this hardware with "native" respect.

ICH7R Storage: This is the big win. The SATA controller on the ICH7R is natively supported by Apple’s AppleICH7SATA.kext. You often don't need third-party injects or modified kexts to see your hard drives in the Disk Utility of a Tiger or Leopard installer.

PCI Bus Stability: Unlike later chipsets (P35, P45) which sometimes require "LPC" patches to get power management working, the 975X is usually recognized "out of the box."

2. The 7600 GT: The Driver King
As you noted, this GPU is the linchpin. Since the 7600 GT was an actual BTO (Build to Order) option for the early Mac Pros:

No "NVinject" or "GraphicsEnabler": If you use a card with a compatible Device ID, you can often get full QE/CI acceleration with zero effort.

Resolution Support: It handles the 1920x1200 resolution of a 23-inch Cinema Display over DVI natively, including the proper EDID handshake that later "experimental" drivers sometimes struggle with.

3. The "Legacy Triple Threat" Performance
Using this combination allows you to bypass the most common Hackintosh headaches:

ComponentWhy it makes it "Easy"975X NorthbridgeProvides a highly compatible memory controller and PCIe lane management that OS X 10.4 expected.ICH7R SouthbridgeNative SATA and USB 2.0 support. No "waiting for root device" errors or USB dropouts.7600 GT GPUProvides the essential Core Image/Quartz Extreme across all three OS versions (Tiger to Snow Leopard).

Comparison: Why not 965 or G31?
While the 965 chipset (like the P965) was popular, it often used the ICH8 or ICH9 southbridge. While those work, they frequently require more tinkering with IOATAFamily patches in Tiger. The ICH7R is the last "true" legacy-friendly controller for 10.4.11.

One Small Caution for 10.4.11:
Even with the 975X, ensure your BIOS is set to "Enhanced" or "AHCI" mode for the SATA ports. Some 975X boards (like the ASUS P5W DH Deluxe) have multiple SATA controllers (JMicron vs. Intel). Sticking to the Intel ICH7R ports is the secret to that "easy" installation you're looking for.

It’s a "period-correct" powerhouse that avoids the "Frankenstein" feel of trying to force Tiger onto newer Core i-series hardware.

34

OsX86 Hackintosh (Intel / AMD) / triple booting tiger, leopard + snow leopard on the same machine? native gpu....

« Last post by chrisNova777 on April 08, 2026, 08:12:12 PM »

7600GT gpu is the key to tripple boot hackintosh that can support tiger 10.4.11 + leoaprd 10.5.8 aswell as snow leoaprd 10.6.8

Gemini said
The NVIDIA GeForce 7600 GT is indeed a legendary "bridge" card in the Hackintosh community. It occupies a unique sweet spot because its drivers were written during the transition from PowerPC to Intel, making it one of the few cards that offers full hardware acceleration across the most iconic "classic" versions of OS X.

Why the 7600 GT is the "God-Tier" Bridge Card
The 7600 GT is essentially the highest-performing card that maintains a native 32-bit driver architecture while still being recognized by 64-bit Snow Leopard kernels.[/size]

1. OS X 10.4.11 (Tiger)
Support: Native.

The Benefit: Tiger was the first version of OS X to run on Intel (10.4.4+). Because the 7600 GT was a flagship consumer card during this transition, the drivers are highly stable. You get full QE/CI (Quartz Erasure and Core Image), which is mandatory for a usable UI and Core Audio performance in apps like Reason or early Pro Tools.

2. OS X 10.5.8 (Leopard)
Support: Native.

The Benefit: Leopard was the last "Universal" OS that supported both PowerPC and Intel. The 7600 GT drivers here are arguably the most mature. It handles the translucent menu bar and Time Machine animations without breaking a sweat, which is vital if you're using those 23-inch Cinema Displays.

3. OS X 10.6.8 (Snow Leopard)
Support: Native (32-bit mode) / Legacy (64-bit mode).

The Benefit: This is where the 7600 GT shines for your "Ultimate Snow Leopard" build. While Snow Leopard pushed toward 64-bit, it still included the 32-bit drivers for the 7000-series NVIDIA cards.

Crucial Note: Since you are using a Gigabyte G41 and an E8600, the 7600 GT ensures that you don't run into the "black screen" or "no acceleration" issues common with newer Fermi or Kepler cards that dropped Tiger support entirely.

[!IMPORTANT]
The 64-bit Ceiling: The 7600 GT drivers were never compiled for a full 64-bit kernel in later OS versions (Lion 10.7+). This is why it is the "hard stop" card. If you go any newer than the 7600 GT (like an 8800 GT or 9800 GT), you often lose the rock-solid stability in Tiger.

Pro-Tip for your G41/E8600 Build:
Since you’re aiming for the Ultimate Tiger experience, ensure your 7600 GT is the PCIe version. Some early 7000-series cards were AGP, which obviously won't fit your G41MT-S2PT. Given your interest in "period-correct" aesthetics, the single-slot reference design of the 7600 GT also keeps the inside of your case looking clean and authentic to the 2006-2007 era.

35

Leopard (Oct 2007) / my issue with the early 2008 imac

« Last post by chrisNova777 on April 08, 2026, 07:00:11 PM »

what chipset was my early 2008 imac /w 2.8ghz penryn processor
i bought this machine originally thinking it came with TIGER as i had experience usjng the white Imacs + a few silver imacs form 2007 they all shipped with tiger but this imac shipped with leopard 10.5.2 when i opeend it up. i was all bummed out i wanted to run 10.4.11

Gemini said
The Early 2008 iMac (model identifier iMac8,1) with the 2.8GHz "Penryn" Core 2 Duo used the Intel Mobile PM965 Express chipset.

This was paired with the ICH8-M Southbridge. Because this model was a bridge between eras, it has some interesting technical quirks that are relevant if you are pushing the hardware today:

Key Technical Specs
Northbridge: Intel PM965 (Crestline).

Front Side Bus (FSB): 800MHz.

RAM Architecture: It uses PC2-6400 (800MHz) DDR2 SDRAM.

Memory Ceiling: While Intel’s official spec for the PM965 was often lower, this specific iMac can actually address up to 6GB of RAM (one 4GB stick and one 2GB stick).

Why the PM965 Matters
The choice of the PM965 chipset was significant because it was one of the first to allow for a relatively smooth transition to the 45nm Penryn processors while still using DDR2 memory.

A Note on Storage
Even though the ICH8-M Southbridge is capable of AHCI, Apple's firmware on these models can be notoriously picky about how it presents the SATA interface to non-macOS operating systems. If you're looking at this for a project involving legacy software or alternative OS installs, keep in mind that the internal bus is SATA II (3.0 Gb/s), so an SSD upgrade will be snappy but will max out around 250-270 MB/s.

It’s a classic "tank" of a machine, especially with that 2.8GHz Penryn—it was a massive jump in efficiency over the older 65nm Merom chips.

You said
i have this imac and its got 6gb ram installed
Gemini said
That is the perfect configuration for that machine. Since the iMac8,1 has a hardware limitation that prevents it from fully utilizing 8GB, the 6GB setup (a 4GB + 2GB pairing) is the absolute "sweet spot" for performance.

If you’re still putting that machine to work, here are a few things to keep in mind regarding that specific memory and chipset combo:

Asymmetrical Dual Channel: You lose the slight performance boost of "matched" dual-channel mode (which you'd get with 2GB + 2GB), but the extra 2GB of raw capacity is a far better trade-off for modern web browsing or multitasking.

The "Penryn" Advantage: Your 2.8GHz Core 2 Duo is a 45nm chip, which runs significantly cooler than the older 65nm versions. This helps prevent the internal fans from ramping up too early when the RAM is under heavy load.

SSD Synergy: If you haven't swapped the original mechanical HDD for a SATA SSD yet, that is the single biggest upgrade you can pair with your 6GB of RAM. Even though the PM965 chipset caps you at SATA II (3.0 Gb/s), the near-instant seek times make the iMac feel like a much newer machine.

Are you running a patched version of a newer macOS on it, or are you keeping it on a legacy version like Snow Leopard or El Capitan?

You said
but theres no way to get full SATA2 or ESATA on this imac thats whats always held it back u need to work on a network with a backend server over the gigabit ethernet to make proper work with this machine or you would have to invest in FW800 disk drives + cables and deal with FW800 disk speed transfers rather then SATAII + ESATA which really gimps the use of this imac in my opinion. the RAM Limitation (6gb limit) and the lack of ESATA, lack of Thunderbol
Gemini said
You've hit the nail on the head regarding the "Apple Tax" of that era. The iMac8,1 is a beautiful piece of industrial design, but from a high-speed data perspective, it’s effectively an island.

The frustration with the PM965/ICH8-M implementation in this chassis is that the hardware could do more, but the physical I/O wasn't there to support it.

The Storage Bottleneck
The Internal SATA Trap: While the chipset supports SATA II (3.0 Gb/s), the internal architecture was designed for a single HDD and an optical drive. Since there are no spare headers, you're stuck with one internal drive unless you pull the DVD drive for a secondary SATA caddy. Even then, you’re still limited to internal storage.

No ExpressCard/PCIe Expansion: Unlike the MacBook Pros of that same year (which had ExpressCard/34 slots), the iMac gave you no way to add a dedicated eSATA controller.

The FireWire 800 "Band-Aid": You're right—FW800 was Apple’s professional solution at the time, but it’s a "dead-end" tech. While it's technically faster than USB 2.0, its real-world throughput (~60-70 MB/s) is a fraction of what a native SATA II or eSATA connection (~250-270 MB/s) provides.

The "Server-Backbone" Strategy
Your approach of using Gigabit Ethernet to a backend server is actually the most logical way to bypass the hardware limitations.

Gigabit Throughput: A well-optimized Gigabit connection can hit around 110-125 MB/s.

The Irony: This makes your network connection faster than a FireWire 800 drive and nearly as fast as the real-world sustained speeds of a mid-2000s mechanical SATA II drive.

The "God-Tier" Comparison
If you compare this to the D975XBX2 workstation board you mentioned earlier, the difference is night and day. On a workstation board, you have the luxury of discrete PCIe lanes. You could drop a dedicated SATA III or eSATA card into a 975X board and completely bypass the ICH7 limitations. The iMac, by comparison, is a "closed box" that forces you to live within the thermal and routing constraints Apple chose in 2008.

It really highlights why those early iMacs, despite having great Penryn processors, eventually became "utility" machines rather than primary production powerhouses once file sizes for audio and video started to balloon. You're basically fighting the lack of PCIe expandability, which is the one thing no amount of RAM or CPU power can fix.

36

OsX86 Hackintosh (Intel / AMD) / Re: why am i obsessed with creating the ultimate workstation compatible with TIGER

« Last post by chrisNova777 on April 08, 2026, 04:04:23 PM »

so back to the ultimate tiger workstation project. i was guided towards the e8600 based on single thread scores but we discussed teh original platform for tigers development + support was the 975X chipset with ICH7R but the macpro1,1 was rolled out with XEON cpus on a slightly different architecture 5000 chipset was it?

Gemini said
You've got a sharp eye for that mid-2000s transition period. You’re exactly right—while the consumer side (iMacs and Mac minis) was living on the 945/975X chipsets, the MacPro1,1 moved into the workstation territory with the Intel 5000X (Greenlow) chipset.

Here is how that architecture breaks down compared to the consumer gear of the Tiger era:

The Mac Pro 1,1 Architecture (Intel 5000X)
The MacPro1,1 used Dual-Independent Buses (DIB). Instead of every component fighting for one pipe to the CPU, each of the two Xeon sockets had its own dedicated path to the Northbridge.

Chipset: Intel 5000X Northbridge + ICH7R Southbridge.

CPUs: "Woodcrest" Dual-Core Xeons (5100 series).

Memory: This was the biggest departure. It used FB-DIMMs (Fully Buffered), which were essentially DDR2 modules with an "Advanced Memory Buffer" chip. They were famously hot and power-hungry, but they allowed for massive capacities and error correction (ECC) that the consumer 975X boards couldn't touch.

PCI Express: The 5000X provided significantly more lanes, allowing the Mac Pro to have four PCIe slots without the bandwidth "starvation" common on the consumer G41 or 975X boards.

Why the E8600/G41 Setup Wins for "Ultimate Tiger"
While the 5000X/Xeon platform was the "official" powerhouse, your Core 2 Duo E8600 on a later chipset (like the G41) actually offers a superior experience for 10.4.11 for a few specific reasons:

1. The Clock Speed Advantage
Tiger is notoriously "single-threaded" in its feel. Most apps from 2005–2007 weren't optimized for four or eight cores. The E8600 sits at a native 3.33GHz with a massive 6MB L2 cache. The stock Xeons in the MacPro1,1 topped out at 3.0GHz. Even with a Xeon swap, you're dealing with slower FSB (Front Side Bus) speeds compared to the E8600's 1333MHz.

2. Instruction Sets
The E8600 is a Wolfdale (45nm) chip. It’s more efficient and runs significantly cooler than the 65nm Woodcrest Xeons. It also supports SSE4.1, which—while Tiger doesn't use it natively—makes the machine much more capable if you ever dual-boot or use "backported" software.

3. The RAM Latency "Penalty"
FB-DIMMs in the 5000X chipset introduced extra latency because of the buffer chip. Your G41 build uses standard DDR3 (or DDR2 depending on the specific board), which provides much snappier memory access times. In a "Tiger" environment, low latency usually beats high capacity every time.

4. Southbridge Consistency
The beauty of your project is that the ICH7R (the Southbridge) is the common denominator. Since the original Mac Pro and the high-end 975X boards used ICH7, Tiger has the built-in kexts to handle your SATA and USB ports with almost zero "hackery."

By using the E8600 on a G41/ICH7 setup, you're essentially building a "super-clocked" version of the 2006 iMac, bypassing the heat and complexity of the Xeon workstation platform while keeping the core compatibility that makes Tiger stable.

You said
with Intel 5000X TIGER becomes capable of having more than 4GB of RAM is that correct?

Gemini said
You’ve hit on one of the most interesting "hidden" features of the Tiger era. Yes, that is correct. While most people think of 10.4 Tiger as a strictly 32-bit OS limited to 4GB of RAM, the Intel 5000X chipset (and the G5 before it) allowed Tiger to break that ceiling.

However, how it handles that extra memory is a bit "fragmented" compared to modern systems.

How Tiger Breaks the 4GB Barrier
On the Mac Pro 1,1 with the 5000X chipset, Tiger 10.4.x can officially support and "see" up to 16GB of RAM (and unofficially more). It manages this through a specific architecture:

The 32-bit Kernel: The Tiger kernel itself always remains 32-bit. This means the OS "core" can only use a 4GB slice of memory for itself and its drivers.

64-bit Userland: Tiger was the first version of OS X to allow 64-bit non-GUI processes. If you were running a command-line tool, a scientific calculation, or a background render engine (like those found in high-end audio or video suites), that specific process could address its own massive pool of RAM beyond the 4GB mark.

PAE (Physical Address Extension): The Intel 5000X chipset uses PAE to allow the 32-bit kernel to manage a much larger physical memory map. It’s essentially "paging" the extra RAM so that while no single 32-bit app can see more than 4GB, the total system can have many apps running that collectively use 8GB, 16GB, or more.

The "Tiger Catch" for Audio and Design
Since you're using this for a workstation, there is one major caveat to keep in mind for your project:

1. GUI Apps are still 32-bit
In Tiger, the "WindowServer" and the Carbon/Cocoa frameworks (which draw the buttons, menus, and windows) were still 32-bit. This means Pro Tools, Logic 7, Photoshop CS2, and Reason are all still 32-bit applications. They will each be limited to a maximum of 4GB of RAM (often closer to 2.5GB or 3GB in practice) no matter how much you put in the machine.

2. The Benefit of 8GB+ on Tiger
Even if your favorite DAW can't use 16GB, having it available on the 5000X chipset (or even your G41 project if the board supports it) is still useful because:

Disk Caching: Tiger will use the "extra" RAM to cache files, making your audio samples and project files load much faster from the disk.

Multi-Tasking: You can have Photoshop, a DAW, and a web browser open simultaneously, and each one gets its own "full" 4GB bucket of RAM without fighting the others.

Summary for your "Ultimate Tiger" Build
While the 5000X chipset allows for massive RAM, your E8600/G41 build is likely limited by the G41 chipset's physical ceiling (usually 4GB or 8GB depending on the motherboard).

If you find a G41 board that supports 8GB of DDR3, that is the "sweet spot" for Tiger. It gives you enough overhead to run a massive DAW project in one corner and a high-res design file in the other without the OS ever having to swap to the hard drive. Going beyond 8GB on Tiger is technically possible on the 5000X Mac Pro, but you hit diminishing returns very quickly since the apps themselves can't "reach" that extra space.

37

General / Miscellaneous / BIG THANK YOU to all users who have donated to oldschooldaw!

« Last post by chrisNova777 on April 08, 2026, 03:00:59 PM »

thanks again 

38

midi - Parallel (PC) / Re: MusicQuest MIDIEngine 2Port/SE (1993) for windows 3.1 + windows 95/

« Last post by chrisNova777 on April 08, 2026, 02:54:19 PM »

The Music Quest 2Port/SE occupies an interesting spot in MIDI history. To answer your question directly: no, it is not "Roland MPU-401 compatible" in the way most vintage enthusiasts mean today (Intelligent Mode).

While Music Quest’s ISA cards (like the PC MIDI Card) were famous for being 100% Roland-compatible clones, the 2Port/SE is a parallel port (printer port) interface that uses Music Quest's proprietary MIDIEngine technology.

1. Is it MPU-401 Compatible?
Hardware Level: It is not a hardware MPU-401 clone. Because it connects via the parallel port rather than the ISA bus, it cannot "map" itself to the standard MPU-401 I/O port (330h) and IRQ (2/9) at a BIOS/hardware level.

Software Level (Windows): In Windows 3.1 through Windows 98, it is effectively compatible because Music Quest provided drivers that allow Windows to see it as a standard MIDI device. Any Windows software using the "MME" (Multimedia Extensions) API will work fine.

DOS Level (The Dealbreaker): It will not work with DOS games that specifically look for an "Intelligent Mode" MPU-401 (like Gateway or early Sierra titles). It requires specific driver support within the application (e.g., Cakewalk for DOS or Voyetra).

2. Did the packaging/manual claim compatibility?
The marketing language was very carefully phrased to avoid lawsuits while still attracting Roland users.

The Claims: The packaging and manual typically branded it as a "Professional MIDI Interface for IBM compatibles." Rather than claiming to be an MPU-401, they marketed it as an alternative or an upgrade to the MPU-401 standard.

"Industry Standard" phrasing: You would often see phrases like "Compatible with all Windows multimedia software" or "Supported by leading sequencers."

The Nuance: Music Quest often highlighted that their PC MIDI Card (the ISA version) was "100% MPU-401 compatible," which sometimes led to consumer confusion. However, for the 2Port/SE, the manual focuses on its MIDIEngine architecture, dual ports (32 channels), and SMPTE sync capabilities—features the original MPU-401 lacked.

39

Windows Vista (Jan 2007) / Re: lets talk about windows vista (2007) the 32bit version for a second

« Last post by chrisNova777 on April 08, 2026, 02:17:01 PM »

40

Windows Vista (Jan 2007) / Re: lets talk about windows vista (2007) the 32bit version for a second

« Last post by chrisNova777 on April 08, 2026, 02:15:51 PM »

so is that the same as chrome 138? does the version indicate compatibility with chrome?

Gemini said
Yes, the version number indicates exactly which "engine" the browser is using. As of April 2026, here is how the versioning works for Supermium and how it relates to Google Chrome:

1. The Version Number = The Engine
When you see Supermium 138, it means the browser is built on Chromium 138.

Compatibility: This means that to any website you visit, your Vista machine looks like it is running a modern version of Chrome from late 2025/early 2026.

Extensions: Because it is based on Chromium 138, you can install almost any extension from the Chrome Web Store (like uBlock Origin or Dark Reader), and they will function just as they would on a Windows 11 machine.

2. Supermium vs. Official Chrome (April 2026)
In the current landscape, Supermium stays a few versions behind the "bleeding edge" of Google's official releases to ensure stability on older kernels.

Browser   Version (April 2026)   Status
Google Chrome (Official)   147   Current "Stable" release for Win 10/11.
Supermium (Legacy)   144 (Stable) / 138 (ESR)   Current for XP/Vista/7.
The move from version 138 to 144 in the Supermium project is actually a major milestone because Chrome 139 was the version where Google originally planned to fully remove "Manifest V2" (which breaks many classic ad-blockers). Supermium's developer has intentionally kept support for these older extension types while moving the engine forward to the 144 codebase.

3. Why version 138/144 matters for your build
For your "Ultimate Tiger" or "Snow Leopard" style builds, these specific versions are the "sweet spot":

Web Standards: Version 138+ supports WebGPU, HTTP/3, and TLS 1.3.

The "User Agent": Websites see you as a modern visitor. You won't get those annoying "Your browser is no longer supported" banners that usually plague Vista.

The 32-bit (ia32) Factor: Supermium is one of the only projects actively compiling a version 138/144 engine for 32-bit systems. Most modern browsers have abandoned 32-bit entirely.

Quick Advice for Installation:
If you are putting this on your Vista setup:

Look for the "R" numbers: (e.g., 138.0 R9). These "Releases" are the developer's way of saying "I've patched the Chrome 138 engine specifically for Vista bugs."

SSE2 Requirement: Ensure your CPU is at least a Pentium 4 or newer. Since you’re using an Intel E8600, you’re in the clear—that chip handles these modern instructions easily.

In short: Yes, Supermium 138/144 is "Modern Chrome" in a vintage suit. It’s the closest thing to a time machine for your browser.

You said
chromium 138 is higher then the version im stuck with on mojave i think is that true?

Gemini said
That is absolutely true. If you are running macOS 10.14 Mojave, your version of Chrome is significantly older than version 138.

The Mojave "Version Ceiling"
For official Google Chrome on macOS Mojave, you hit a dead end a long time ago.

Last Official Version: Chrome 116 (released in August 2023) was the final version to support macOS 10.13 (High Sierra) and 10.14 (Mojave).

The Gap: By moving to a browser based on Chromium 138, you are jumping forward over 22 major versions of the engine.

Why this is a "win" for your legacy hardware
It’s a bit of a paradox: your older Windows Vista/7 machines (via Supermium) are technically running a more modern, secure web engine than your "newer" Mojave machine is capable of running officially.

On Mojave, you are stuck with an engine from 2023 that:

Lacks the latest CSS/UI features (like the stretch keyword or new animation functions introduced in 138).

Is missing 2.5 years of security patches and zero-day fixes.

Will eventually trigger "unsupported browser" warnings on sites that require the newest Chromium features.

Can you get 138 on Mojave?
While Google won't give it to you, the Mac community has similar "backport" projects to what you're using on Windows:

Chromium Legacy: This project (often found on GitHub) backports modern Chromium versions to older macOS releases like Mojave and even Lion/Mountain Lion.

OpenCore Legacy Patcher (OCLP): Since you're into Hackintoshing and hardware optimization, you're likely aware of OCLP. It’s the primary way most Mojave users "skip" the version ceiling by spoofing a newer OS or actually upgrading to Monterey/Ventura on unsupported hardware.

Bottom Line: Your Windows Vista/7 boxes running Supermium 138 are currently "fresher" on the web than a standard Mojave install. It really highlights how vital those community-driven backports are for keeping older professional workstations (like your audio rigs) alive.