Recent Posts

71

OsX86 Hackintosh (Intel / AMD) / why did apple choose the 975X chipset?

« Last post by chrisNova777 on April 07, 2026, 09:04:36 PM »

why did apple pick the 975X chipset + ICH7R ? for the mac pro original platform?
Gemini said
The choice of the Intel 975X Express Northbridge and the ICH7R Southbridge for the original Mac Pro (the "MacPro1,1") in 2006 was a strategic compromise between high-end workstation performance and consumer-grade compatibility during the critical PowerPC-to-Intel transition.

While contemporary PC workstations were moving toward the Intel 5000X (Greencreek) chipset, Apple took a unique path that blended parts of the enthusiast desktop world with server-grade hardware.

1. The Workstation Gap: 975X vs. 5000X
At the time, the "correct" choice for a dual-Xeon system was the Intel 5000X chipset. However, the 5000X was designed primarily for servers and featured high power consumption and heat output.

By selecting the 975X, Apple gained several advantages:

Lower Latency & Heat: The 975X was a high-end desktop/enthusiast chipset. It was more efficient and ran cooler than the 5000-series server chipsets, allowing Apple to maintain the quiet acoustic profile they promised for the Mac Pro.

PCI Express Versatility: The 975X was one of the first chipsets to support dual x8 graphics or a single x16 slot natively, which aligned with Apple’s goal of making the Mac Pro a flexible machine for both video editors (who needed high-end GPUs) and PCIe expansion users.

2. The ICH7R Southbridge: Legacy & Stability
The ICH7R (I/O Controller Hub 7) was the "Southbridge" that handled the computer’s slower communication tasks (SATA, USB, PCI, Audio).

SATA II Maturity: The ICH7R provided four native SATA 3Gb/s ports. This allowed Apple to implement the "cable-free" drive bay system found in the Mac Pro 1,1 without needing complex third-party controllers that might have required unstable drivers during the transition to macOS Tiger (Intel).

Tiger & Leopard Compatibility: Because the ICH7R was a widely used and stable component in the PC world, it was much easier for Apple's engineers to write stable kexts (drivers) for it during the rush to get Mac OS X 10.4.7 ready for the Intel launch.

AHCI Support: The "R" variant (RAID) supported Advanced Host Controller Interface (AHCI), which was crucial for the performance of the SATA drives and the "hot-swapping" feel of the Mac Pro's internal drive sleds.

3. The "Frankenstein" Architecture
The Mac Pro 1,1 was technically an architectural hybrid. It used:

Server-grade CPUs: Two Intel Xeon "Woodcrest" 5100-series processors.

Server-grade Memory: Fully-Buffered DIMMs (FB-DIMMs) with ECC support.

Enthusiast-grade Chipset: The 975X/ICH7R combo.

This combination allowed Apple to offer the ECC memory protection and multi-socket processing required by pros, while using a chipset that was easier to tune for the specific "instant-on" and sleep-wake behaviors expected of a Mac.

Why not use the ICH8R?
By the time the Mac Pro launched in August 2006, the ICH8R was already appearing in PC motherboards. However, Apple chose the ICH7R likely due to validation cycles. Apple had been testing "Marklar" (the secret Intel version of Mac OS X) on ICH7-based developer transition kits (the famous Pentium 4 DTKs) for a year. Sticking with the ICH7R ensured that the first-generation flagship was as stable as possible on day one.

Note for your projects: If you are still working on your "Ultimate Tiger" build, this is exactly why the 975X/ICH7R era is so nostalgic—it represents the peak "Golden Era" of compatibility where high-end PC hardware and early Intel macOS were perfectly aligned.

You said
why didnt they choose the P965?
Gemini said
Choosing the P965 Express chipset (released just before the Mac Pro in 2006) might seem logical because it was "newer," but for a workstation like the Mac Pro, it was a non-starter for several technical and professional reasons.

While the P965 was a massive hit for the consumer "Core 2 Duo" desktop market, it lacked three critical "Pro" pillars that the 975X provided.

1. The ECC Memory Requirement
This was the primary dealbreaker. The Mac Pro was designed to use ECC (Error Correction Code) memory to prevent system crashes during long video renders or scientific calculations.

975X: Supported ECC memory natively. This allowed Apple to bridge the gap between a desktop-class chipset and the server-grade Xeon processors.

P965: Was a purely "mainstream" consumer chipset. It did not support ECC memory. Had Apple used the P965, the Mac Pro would have been prone to the "bit-flip" errors that professional workstations are designed to avoid.

2. PCI Express Lane Multiplexing
The original Mac Pro was marketed for its expansion capabilities, particularly for high-end graphics and RAID cards.

975X: Could split its 16 PCIe lanes into two x8 slots (or a single x16). This was "native" to the Northbridge, ensuring high-bandwidth performance for dual-GPU setups or high-speed fiber channel cards.

P965: Could only do a x16 / x4 configuration. The second "long" slot on P965 boards usually ran through the Southbridge at a significantly throttled x4 speed, which would have been an embarrassing bottleneck for a "Pro" machine.

3. Native IDE (PATA) Support
While it sounds like a small detail now, the transition era of 2006 still relied heavily on IDE for optical drives (DVD burners).

975X + ICH7R: The ICH7R Southbridge included a native IDE controller. Apple used this to power the SuperDrives in the top optical bays without needing a third-party chip.

P965 + ICH8R: Intel famously dropped native IDE support with the ICH8 series. PC motherboard manufacturers had to add "janky" third-party chips (like JMicron controllers) to provide IDE ports, which often caused driver instability and "Kernel Panics"—something Apple would never have tolerated in a flagship product.

4. Validation and the "Transition" Timeline
Apple's "Developer Transition Kits" (the modified PowerMac G5s given to developers to prepare for Intel) were essentially built on the 945G/ICH7 architecture.
The 975X was an evolution of that 945/955 lineage. By sticking with the 975X, Apple’s software team didn't have to rewrite the core "plumbing" of macOS for a brand-new, unproven P965 architecture. They chose the stable, mature, high-bandwidth option over the "new and shiny" consumer one.

72

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

« Last post by chrisNova777 on April 07, 2026, 08:56:10 PM »

 It’s the computer that Apple should have built + supported for a decade, but didn't.

EXACTLY

73

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

« Last post by chrisNova777 on April 07, 2026, 08:52:54 PM »

hey its nice when things WORK

why am i obsessed with creating the ultimate workstation compatible with TIGER OSX? supporting the best graphics + disk access transfer speeds possible makes my music software work faster and that supports my creative process for making music with the authentic tools that were available in 2006. also thre was so so much confusing that arose when they discontinued the powermac g4 series + the whole fact that powermac g5's couldnt run os9 and then the abrupt switch to intel processors it left alot of people with a bad taste in their mouths re: compatibility and also what to actually do with the g4s + g5 computers we had spent alot of money on that were suddenly deemed obsolete over night midway thru their worth + lifecycle!

It sounds like you are tapping into a very specific and justified form of "technological closure." The mid-2000s were a chaotic era for Apple users, and building the "Ultimate Tiger" machine is essentially a way to fix the broken promises of that transition period.

Here is a breakdown of why that particular obsession makes so much sense from both a technical and creative standpoint.

1. Resolving the "Transition Trauma"
The period between 2003 and 2006 was arguably the most volatile in Mac history. You had three massive shifts happening simultaneously:

The OS 9 Break: When the PowerMac G5 launched, it dropped the ability to boot into OS 9 natively. For professionals with expensive MIDI setups and plugins, this was a massive "planned obsolescence" hit.

The Architecture Shift: Moving from PowerPC (PPC) to Intel meant that even the high-end G5s people had just spent $3,000 on were effectively dead-ends within three years.

The Software Gap: Tiger (10.4) was the "bridge" OS—the only one that lived comfortably in both the PPC and Intel worlds.

By building a high-performance Tiger workstation now, you are essentially creating the "missing link"—a stable, finalized version of a system that was cut short by corporate pivots.

2. Creative Flow vs. Modern Friction
There is a legitimate argument for using 2006-era tools for music production.

Zero Distractions: A Tiger-era machine isn't constantly pinging you with iCloud notifications, OS update prompts, or subscription-model software nagging.

DSP and Latency: Professional audio cards from that era (like the Digi 002 or Delta 410) were designed to talk directly to the hardware. On a modern system, layers of "security" and driver abstraction can actually introduce micro-latencies that weren't as prevalent in a well-tuned legacy setup.

The "Instrument" Factor: When your DAW (like Reason 3) and your OS are locked in a specific version, the computer stops being a "general-purpose device" and becomes a dedicated instrument. You learn its quirks and its ceiling, which often forces more creative decision-making.

3. The "Tiger" Performance Sweet Spot
Tiger (10.4.11) is widely considered one of the leanest, fastest versions of macOS ever released. It lacked the heavy "eye candy" and background metadata indexing (Spotlight was brand new and much lighter) that started to bloat the OS in Leopard and beyond.

Using modern hardware (Intel Core 2 Duo E8600, SATA SSDs via PCIe with SATA2 disk speeds) to run an OS that was originally struggling to run on G4 chips with IDE drives creates a "God Mode" experience.

 You’re getting:

Instantaneous UI: Windows and menus snap open because the hardware is overkill for the software's requirements.

Maximized Throughput: Using PCIe-based SATA controllers (like the Sil3132) allows you to hit the ceiling of what the software can actually process, ensuring that disk-heavy sample libraries load faster than they ever did on a 2006-era mechanical drive.

Building this isn't just about nostalgia; it’s about optimization. You are taking the best software environment from a specific era and finally giving it the "lungs" (hardware) it needs to breathe properly. It’s the computer that Apple should have supported for a decade, but didn't.

amen to that
Gemini said
It really is the ultimate "tech justice" project. There is something incredibly satisfying about taking a operating system that was once held back by hardware transitions and finally letting it run at full throttle.

Since you're bridging that 2006 era with much faster modern components, are you finding that the older plugins and DAW versions handle the extra "headroom" gracefully, or do you have to throttle things back to keep the timing sample-accurate?

74

OsX86 Hackintosh (Intel / AMD) / Motherboards that will work with SATA II + MACOSX TIGER without additional hw

« Last post by chrisNova777 on April 07, 2026, 07:05:04 PM »

this is a list of motherboards that have SATA controllers that are supported by OSX TIGER to unleash the full ACHI + NCQ + Hot plug features of SATA II. motherboards with controllers older than these will only be used at SATA1 speed + tech. some newer wont work aswell it only works with specific types of ICH controllers.

01. Abit AW9D-MAX (975X + ICH7R) ATX;
02. Abit AL8 (945P + ICH7R) ATX;
03. ASUS P5W DH Deluxe (975X + ICH7-DH) ATX;
04. ASUS P5WD2 Premium (955X + ICH7R) ATX;
05. ASUS P5WD2-E Premium (975X + ICH7R) ATX;
06. ASUS P5LD2 Deluxe (945P + ICH7R) ATX;
07. ASUS P5LD2-VM DH (945G + ICH7-DH) Micro-ATX;
08. ASUS P5W64 WS Professional (975X + ICH7R) ATX;
09. ASUS P5M2-M/C (Intel 3000 + ICH7R) Micro-ATX;
10. DFI LanParty UT iC7975X (975X + ICH7R) ATX;
11. Gigabyte GA-G1975X (975X + ICH7R) ATX;
12. Gigabyte GA-8I955X Royal (955X + ICH7R) ATX;
13. Gigabyte GA-8I955X Pro (955X + ICH7R) ATX;
14. Gigabyte GA-8I945P Pro (945P + ICH7R) ATX;
15. Gigabyte GA-8I945GMF (945G + ICH7R) Micro-ATX;
16. Gigabyte GA-8I945GMF-RH (945G + ICH7R) Micro-ATX;
17. Intel D975XBX "Bad Axe" (975X + ICH7R) ATX;
18. Intel D975XBX2 "Bad Axe 2" (975X + ICH7R) ATX;
19. Intel D955XBK (955X + ICH7R) ATX;
20. Intel D945GTP (945G + ICH7R) Micro-ATX;
21. Intel D945PWM (945G + ICH7-DO) Micro-ATX;
22. Intel D945PSN (945P + ICH7R) ATX;
23. MSI 975X Platinum (975X + ICH7R) ATX;
24. MSI 955X Platinum (955X + ICH7R) ATX;
25. MSI 945P Neo2-DH (945P + ICH7-DH) ATX;
26. MSI 945GZM5 v1.0 (945G + ICH7R) Micro-ATX;
27. Supermicro PDSML-LN2 (Intel 3000 + ICH7R) Micro-ATX;
28. Supermicro PDSME (Intel 3000 + ICH7R) ATX;
29. Supermicro PDSM4+ (E7230 + ICH7R) ATX;

these specific boards would be extremely usefull for advanced users as it leaves more slots open for further expansion purposes

75

OsX86 Hackintosh (Intel / AMD) / Re: Tiger only supported Sata1 (1.5gb/s) disk speeds and works best with ICH7R

« Last post by chrisNova777 on April 07, 2026, 04:28:16 PM »

https://www.ebay.ca/itm/303567423153

if u live in canada heres a SIL3132 PCIE x1 card for only 10$

i just bought two of them for my "ultimate tiger osx workstation" project

76

General / Miscellaneous / Re: site host / domain transfer complete | site updates

« Last post by chrisNova777 on April 07, 2026, 04:19:55 PM »

another big thank you to PAUL M****** who just randomly became our highest DONATOR of all time!
donating a huge amount today that was very unexpected but very appreciated thank you very much sir for your contribution!!!!! 

oldschooldaw user name: zzefiro
thank you sir!

77

OsX86 Hackintosh (Intel / AMD) / Re: even if u have no PCIE slots SIL3124 on PCI133 still benefits OSX TIGER+

« Last post by chrisNova777 on April 06, 2026, 11:57:18 PM »

whats the max size for fat32 partition under windows 9x
Gemini said
Under Windows 9x (specifically Windows 95 OSR2, Windows 98, and Windows Me), the theoretical and practical limits for FAT32 partitions are shaped by the architectural constraints of the era.

The Standard Partition Limit
While the FAT32 file system itself can theoretically support volumes up to 2TB, Windows 9x has a practical ceiling of 127GB (or approximately 137,438,953,472 bytes).

This limitation isn't strictly a "FAT32" issue, but rather a result of the 28-bit LBA (Logical Block Addressing) used in the standard IDE/ATA drivers of the time. Once you exceed 127GB, the addressing system runs out of bits to map sectors, which can lead to catastrophic data corruption as the system "wraps around" and begins overwriting the beginning of the disk.

Key Constraints and Factors
Scandisk and Defrag: Even if you use third-party drivers to bypass the 127GB limit, the built-in Windows 9x utilities like Scandisk and Disk Defragmenter are 16-bit applications. They typically struggle or crash on partitions larger than 32GB or 64GB because they cannot handle the massive amount of cluster information in memory.

Cluster Size: FAT32 uses clusters to manage data. On a large partition, a 32KB cluster size is standard. If the partition is too large, the number of clusters becomes too high for the 16-bit FAT tables to track efficiently under 9x.

The 32GB "Format" Limit: While Windows 9x can read and write larger partitions, Windows 2000 and XP introduced an artificial 32GB limit when formatting new FAT32 partitions to encourage users to switch to NTFS. To create a 120GB FAT32 partition for a Windows 98 build, you generally need to use the 98 FDISK utility or a third-party tool.

Recommended Best Practice
For maximum stability on vintage hardware, it is generally recommended to keep partitions at or below 32GB. If you are using a larger drive (like an 80GB or 120GB HDD), splitting it into several 32GB logical drives ensures that Scandisk and other system tools remain functional and prevents the "out of memory" errors common in late-90s DOS-based environments.

You said
whats the max size of afat32 partition under windows 98SE when connected to a SIL3124 card
Gemini said
When using a Silicon Image SiI3124 controller on Windows 98SE, you are stepping outside the standard IDE/ATA limitations, but you still face the architectural ceilings of the operating system itself.

The 128GB Threshold
The primary hurdle for Windows 98SE is the 28-bit LBA (Logical Block Addressing) limit. Standard Windows 98SE drivers cannot "see" or safely address storage space beyond 128GB (137GB decimal).

While the SiI3124 chip itself is a professional-grade SATA II controller that supports 48-bit LBA (allowing for Terabytes of storage), the Windows 9x driver is the bottleneck.

With standard drivers: You should not exceed a 120GB partition. Attempting to use a larger drive or partition will result in "wrap-around" data corruption once the 128GB mark is passed.

With 48-bit LBA Patches: If you use a third-party patch (such as the well-known Rudolph Loew's patch), Windows 98SE can theoretically handle FAT32 partitions up to 2TB.

Critical Constraints for the SiI3124
Even if you patch the OS to see the full size of a modern SATA drive, there are two major "soft" limits to consider for a stable build:

1. The Scandisk/Defrag Memory Wall
The 16-bit versions of SCANDISK.EXE and DEFRAG.EXE included with 98SE will fail on very large partitions.

32GB to 64GB: Usually the "sweet spot" for stability.

127GB+: Scandisk will likely report "Out of Memory" errors because it cannot track the massive number of clusters in a FAT32 table of that size.

2. The PCI Bus Saturation
The SiI3124 is a fast SATA II controller, but when plugged into a standard 32-bit PCI slot (like those on an ASUS P5PE-VM), it is capped at a theoretical maximum of 133MB/s.

While the card supports NCQ and Hot-Plug, using a massive partition (e.g., 500GB) doesn't provide a speed advantage; it only increases the time the system spends "thinking" during boot-up or disk repair cycles.

Recommendation for Your Setup
For a high-performance Windows 98SE build using that specific card:

Primary Partition: Keep your boot partition (C:) at 32GB. This ensures all native 98SE utilities work perfectly.

Extended Partitions: If you have a larger SATA drive, use FDISK (or a tool like Partition Magic) to create additional logical drives (D:, E:, etc.) in 32GB or 64GB chunks.

Total Disk Size: If you haven't patched the system for 48-bit LBA, do not use a physical drive larger than 120GB, regardless of how many partitions you make.

78

OsX86 Hackintosh (Intel / AMD) / use SIL3124 to host a FAT32 partition to move data between OSX + Win98se

« Last post by chrisNova777 on April 06, 2026, 11:56:35 PM »

also for those people who wnat to dual boot between osx + windows using a SIL3124 card allows you to format a partition to be 32b or 64gb or even 96gb and use that as a partition to move data between the different OS installation reboots..

so does this mean using hte sil3124 card will allow me to have a drive of data that is shared between the two operating systems? that wil be accessible by the sil3124 card regardless which os i boot into?
Gemini said
Yes, that is exactly what it means. Using the SiI3124 card in the P5PE-VM allows the controller to act as a universal storage bridge that stays active regardless of which OS you boot into.

However, since you're dealing with the massive gap between OS X Tiger (2005) and Windows 98 SE (1999), the "sharing" part depends entirely on how you format that drive.

The Strategy: The Shared "Data Partition"
To make this work seamlessly, you should create a dedicated partition (or use a secondary drive) specifically for shared files.

File System Choice: FAT32 is your only native option.

Tiger: Can read and write FAT32 perfectly (appears as "MS-DOS FAT" in Disk Utility).

Windows 98: Native home territory for FAT32.

The Constraint: You will be limited to a 4GB maximum file size. This is usually fine for audio projects or documents, but if you have massive disk images or video files, they won't fit.

Accessibility Breakdown
Feature   OS X Tiger 10.4.11   Windows 98 SE
SiI3124 Driver   Native/Sonnet Driver   Silicon Image 9x Driver
Shared Drive Visibility   Appears on Desktop as "Untitled" (or your name)   Appears in My Computer as D: or E:
Hot-Swap Support   Yes   Limited (Safe to do only if no files are open)
Large Drive Support   Up to 2TB (GPT)   Requires 48-bit LBA Patch for >137GB
Critical "Gotchas" for the Shared Drive
Avoid NTFS and HFS+: * Windows 98 cannot see your Tiger boot drive (HFS+) without expensive, obscure third-party software (like old versions of Paragon HFS for Windows).

Tiger can only read NTFS; it cannot write to it natively.

Stick to FAT32 for the shared "transfer" space.

The 137GB Barrier in Windows 98: Even if the SiI3124 chip supports large drives, Windows 98 SE natively "blindly" wraps around data after 137GB, which will corrupt your Tiger data if you aren't careful. Since you have an X6800, you likely already have a patched setup, but ensure you have an LBA48 patch installed in Win98 before pointing it at a large shared SATA drive.

The "Boot" vs "Storage" Logic: I recommend keeping your OS installations on their own separate drives/partitions and using a third partition on the SiI3124 for the "Shared Exchange." This prevents one OS from accidentally touching the system files of the other.

Suggested Partition Map
Partition 1: HFS+ (Tiger OS - Invisible to Win98)

Partition 2: FAT32 (Win98 OS - Visible to Tiger)

Partition 3: FAT32 (Shared Data - Read/Write for both)

Does your SiI3124 card have two internal ports or four? If it has four, you could even just dedicate a cheap 120GB SSD purely to the "Shared Data" role to keep things physically separate and safe.

You said
it seems fat32 would be the only format for the partition that both os could see? right?
Gemini said
That is exactly right. For a "no-hassle" bridge between OS X Tiger and Windows 98 SE, FAT32 is the only filesystem that both operating systems can read and write to natively without needing third-party drivers or unstable "hacks."

While it's the most compatible, there are a few "rules of the road" you'll need to follow to keep your data safe between the two environments.

The FAT32 Compatibility Matrix
Feature   OS X Tiger (10.4.11)   Windows 98 SE
Read Support   Native   Native
Write Support   Native   Native
Max File Size   4GB   4GB
Max Partition Size   2TB (GUID) / 32GB (MBR)*   127GB (Native Limit)**
*Tiger Note: If you format the drive in Tiger's Disk Utility, it will let you create a FAT32 partition larger than 32GB. However, Windows 98 might struggle to "see" the full size if the partition table isn't set to Master Boot Record (MBR).

**Win98 Note: Windows 98 has a built-in "Scandisk" and "FDISK" limit of 127GB. If your shared partition is larger than this, you must use the 48-bit LBA patch, or Win98 will eventually corrupt the data once you write past that 127GB mark.

How to Set Up the "Bridge" Partition
To ensure both the X6800 side (Win98) and the Tiger side see the drive perfectly, follow this setup order:

Initialize as MBR: Use Tiger’s Disk Utility to partition the drive. Go to the "Options" button under the Partition tab and ensure Master Boot Record (MBR) is selected, not GUID. Windows 98 cannot read GUID partition tables.

Format as MS-DOS (FAT): This is Tiger’s name for FAT32.

The "Naming" Rule: Keep the drive name short (8 characters or fewer) and avoid spaces or special characters (e.g., call it DATA or BRIDGE). Windows 98 can sometimes get confused by "Long File Names" in the volume label.

Are there any alternatives? (The "Why Use FAT32" logic)
Technically, other formats exist, but they are "Radioactive" for your specific builds:

NTFS: Windows 98 can't see it at all. Tiger can see it but can't write to it.

HFS+ (Mac OS Extended): Windows 98 can't see it. You could use a very old version of "MacDrive" on Win98, but it is notoriously unstable on fast Core 2 CPUs like your X6800 and often causes Blue Screens (BSODs).

ExFAT: Neither OS supports this. ExFAT wasn't introduced until late in the XP era and was never back-ported to 98 or Tiger.

One Final Pro-Tip for the SiI3124
Since the SiI3124 is a "PCI" card, Windows 98 will treat any drive attached to it as a Removable Drive by default. In your Windows 98 Device Manager, go to the properties of the disk drive under the SiI3124 and ensure "Removable" is unchecked and "DMA" is checked. This will ensure Tiger doesn't accidentally "lock" the drive in a way that prevents Win98 from mounting it properly after a reboot.

79

Mac OS 9 (Oct 1999) / matrox g400 was hacked to work on macos9 on powermac g4's

« Last post by chrisNova777 on April 06, 2026, 10:46:17 PM »

the Matrox Millennium G400 is a legendary card in the world of legacy hardware, and it occupies a very specific, almost "mythical" spot in Power Mac history.

The reason it’s often omitted is that, unlike the ATI or NVIDIA cards of the era, there was never an official retail "Mac Version" of the G400. However, it is famous in the hobbyist community for one specific reason: it is one of the few Matrox cards that can actually be "hacked" to work.

Here is the deal with the G400 on a Power Mac G4:

1. The "Witchy" Flash (The Hobbyist Hack)
Back in the early 2000s, a firmware hacker nicknamed "Witchy" released a custom Mac ROM for the PC version of the Matrox G400.

The Process: You had to take a standard PC G400 (Single or DualHead), put it in a PC, and use a DOS utility to "flash" the Mac BIOS onto the card.

The Result: Once flashed, the G400 would actually trigger Open Firmware and show a boot screen on a Power Mac G4.

2. Performance in Mac OS 9
When the G400 works, it is actually quite impressive for its era:

2D Quality: Matrox was famous for its incredibly sharp analog signal. If you are using a CRT or an early LCD via VGA, the G400 often looks cleaner than the stock ATI Rage 128 cards.

Environment Mapped Bump Mapping (EMBM): The G400 was one of the first cards to support this, and a few Mac games (like Expendable) actually supported it.

3. Why it isn't usually recommended anymore
Even though you can get a G400 running, it has some major drawbacks for a modern-day G4 project:

Lack of Quartz Extreme: In Mac OS X Tiger, the G400 drivers do not support hardware acceleration for the UI. This makes the OS feel sluggish compared to an ATI Radeon.

Driver Stability: The Mac drivers for the G400 were never "official" from Matrox; they were essentially beta drivers that were leaked or adapted. They are prone to crashing in certain OS 9 games.

Hardware Risk: Many PC G400s use 5V AGP signaling. If you try to force a 5V card into a later "Mirrored Drive Doors" (MDD) G4, you risk damaging the motherboard. It is safest only in the early "Sawtooth" or "Digital Audio" G4 models.

Summary
The G400 was omitted because it requires a custom firmware flash to even be recognized by a Mac. If you enjoy the "Hackintosh" style of hardware modding and want to experiment with flashing ROMs, the G400 is a fun project. But for a build where you want "set it and forget it" stability, an ATI Radeon 7000 or 9000 remains the more practical choice.

Are you looking to experiment with flashing a PC card, or are you trying to find a card that works natively out of the box?

80

OsX86 Hackintosh (Intel / AMD) / Re: Tiger only supported Sata1 (1.5gb/s) disk speeds and works best with ICH7R

« Last post by chrisNova777 on April 06, 2026, 06:38:34 PM »

ok so your saying ICH7 was the gold standard but it only ever supported SATA 150 transfer speeds?
Gemini said
This is a classic "gotcha" in the retro-computing world. You've hit on the exact reason why the ICH7 is simultaneously loved and hated.

The Short Answer:
Yes, the base ICH7 was limited to SATA 150 (1.5Gbps) in many real-world Mac implementations, but the chipset itself is a bit more complicated.

1. The Confusion: Desktop vs. Mobile
Desktop ICH7 (82801GB): Technically supports SATA II (3Gbps) speeds. However, it does not support AHCI. Because it lacks AHCI, it often defaults to IDE/Legacy mode, which can bottleneck your performance depending on the drivers you use.

Mobile ICH7-M (82801GBM): This is the "Gold Standard" I mentioned for compatibility, because it was in every 2006-era Mac (MacBook, Mac mini, iMac). But here is the catch: Apple (and Intel) limited the mobile version to SATA 150 (1.5Gbps) to save power and maintain stability with early SATA drives.

2. The AHCI Problem
This is where the "R" matters:

ICH7 (Base): No native AHCI support. You are stuck in "Legacy IDE" mode. Even if the hardware can technically push more data, the lack of AHCI means you lose NCQ (Native Command Queuing), which makes SSDs feel much slower.

ICH7R / ICH7-M / ICH7-DH: These variants do support AHCI.

3. Why it feels like the "Gold Standard" anyway
Even though the base ICH7 is often capped at 1.5Gbps, Hackintoshers call it the gold standard because it is the most compatible.

In the "Ultimate Tiger" era, stability was more important than raw speed.

A drive running at a stable 1.5Gbps (SATA I) is better than a drive on an ICH8R running at 3Gbps (SATA II) that kernel panics every 20 minutes because the AHCI drivers are flaky.

How to get SATA II (3Gbps) on your project:
Since you specifically want SATA II speeds for your boot drive on Tiger/Leopard/Snow Leopard:

Don't use the base ICH7: If your board has the base ICH7, you will likely be capped at 1.5Gbps or forced into IDE mode.

Use the ICH8R (with the 10.6 Backport): As we discussed, if you use the 10.6 drivers in 10.5.8, you "unlock" the 3Gbps speed and AHCI support that the base ICH7 lacks.

The SiI3132 is still the winner: A Silicon Image 3132 card is a SATA II (3Gbps) card. It bypasses all the Intel chipset limitations and gives you the full speed across all three OS versions natively.

Summary
If you use the onboard ICH7, you are choosing compatibility over speed (often stuck at 150MB/s).
If you use a PCIe SATA card (SiI3132) or a patched ICH8R, you are choosing speed (300MB/s), but you have to do the "kext legwork" we talked about.

Is your current "Ultimate Tiger" board using the base ICH7, or are you looking at an ICH8/G41 board specifically to get that 3Gbps jump?

You said
ICH7R / ICH7-M / ICH7-DH: ok show me some motheboards that feature these exaft chipsets that might be cheaply purchased on ebay
Gemini said
Finding a motherboard with the ICH7R or ICH7-DH (Digital Home) is the smartest move for your "Ultimate Tiger" project because these specific variants support AHCI, which the base ICH7 lacks.

Since these were premium chipsets in 2006, they are usually found on high-end LGA 775 boards. On eBay, you can often find these "orphan" boards or CPU/Motherboard combos for $30–$60.

1. The "Digital Home" Choice (ICH7-DH)
The ICH7-DH was the heart of Intel’s "Viiv" platform. These boards are fantastic for Hackintoshing because they were designed for media center PCs and almost always have AHCI enabled.

Intel D945GTP / D945GCFG1: These are classic Intel-branded desktop boards. They are extremely "plain" but very stable. The D945GCFG1 was often found in Gateway or Dell enthusiast desktops of that era.

ASUS P5W DH Deluxe: This is a legendary board in the retro community. It uses the i975X chipset paired with the ICH7-DH. It’s highly sought after because it has built-in Wi-Fi and excellent overclocking for Core 2 Duos.

Gigabyte GA-8I945P-G-RH: A solid mid-range board that features the ICH7-DH. Gigabyte boards from this era are famous for having very "Hackintosh-friendly" BIOS options.

2. The "Enthusiast" Choice (ICH7R)
The ICH7R was the workstation/RAID version. These boards often feature more SATA ports (usually 4–6) and better power delivery for quad-core CPUs.

ASUS P5B Series: While the standard P5B uses the ICH8, the ASUS P5B Deluxe and P5B-E often use the ICH8R or high-end ICH7R variants.

Abit AW9D-MAX: If you find this at a flea market or a cheap "Buy It Now" on eBay, grab it. It’s one of the most beautiful boards ever made (blue LEDs, heat pipes) and uses the i975X + ICH7R combo.

Intel D975XBX / D975XBX2 ("Bad Axe"): These were Intel's flagship workstation boards. They are rock-solid and feature the ICH7R. They were the "workhorse" boards used by many early developers in the Hackintosh scene.

3. The "Workstation" Choice (ICH7-M)
Technically a laptop chip, the ICH7-M (Mobile) actually appeared on some rare "MoDT" (Mobile on Desktop) motherboards. These are rare but "magical" because they are 100% native to the Mac drivers.

AOpen i975Xa-YDG: A very rare board that allowed you to put a laptop Core Duo / Core 2 Duo into a desktop. It uses the ICH7-M and is essentially a Mac mini in a desktop form factor.

Summary Shopping List for eBay:
Search for these models or keywords to find the best deals:

"Intel D975XBX" (Great for ICH7R stability)

"ASUS P5W DH" (The best for ICH7-DH features)

"LGA 775 i945P" (Broad search—look at the photos for "ICH7R" printed on the chip or board)

"Dell Dimension 9100 / 9150 Motherboard" (Often uses the ICH7R and can be found for under $25 as a replacement part).

One Critical Warning: If you buy a Dell or HP "OEM" board from eBay, make sure it comes with the proprietary front panel adapter or that you are comfortable re-wiring the power button pins, as they don't use standard headers!