Jump to content
21 posts in this topic

Recommended Posts

Ok here is my PPF patch for 8f1111.This patch is for sse2 systems without NX.DX.(test3b kernel/cpuid panic fixed)

 

[Edited: Content in vilotion of DMCA ]

 

Whats does this PPF give you ps2keyboard+ps2mouse+IOATAFamilyW/Plugins+ac97sound+vmwarenetwork+vmwaresound on Intel and non intel hardware

The Extensions.mkext for booting the dvd has nforce support.

I have put MD5Summer in the zip for you to use to check your md5 sums,also I gave you the ppf-o-matic 3.0 patching program for windows and mac osx MD5 sums

 

1111Patches.ppf deff91f1cd9b6eec5dcb4c1dccc5721c

 

macosx_10.4.3_8f1111_for_dtk_userdvd.unpached.MD5 f086fa1cdd01013c9787dfd1e92c2078

 

macosx_10.4.3_8f1111_for_dtk_userdvd.Patched.MD5 a9a6d3144f45871d9691aff21c79a266

Good luck and if this doesnt work for you please dont flame me

Edited by Hagar

I used your patch and I get this error...

 

You need to restart your computer. Hold the Power button down for sevral seconds or press the Restart button.

 

First I applied the Java bootloader patch by Maxxuss, then I applied your patches. I started it up in VMware and it gave me the error after the grey apple.

 

Fixed it. Mounted with Daemon Tools and it worked. Mounting directly in VMware dosen't work.

I used your patch and I get this error...

First I applied the Java bootloader patch by Maxxuss, then I applied your patches. I started it up in VMware and it gave me the error after the grey apple.

 

Fixed it. Mounted with Daemon Tools and it worked. Mounting directly in VMware dosen't work.

 

OK good but to let you know you dont need the boot loader patch with the ppf.it applies it for you along with everything else

applying the boot loader first could cause issues.

I've burned it, but haven't had a chance to try it. The other one you released wouldn't work for me. I'll try it later today and report back to you.

 

Thanks for the work you've put into this project!

 

What exactly happened that made it not work? Maybe I can help you out with it.

What exactly happened that made it not work? Maybe I can help you out with it.

 

I can't quite remember. It was either the reboot problem, or it crashed. I've tried so many things I can't remember, and the DVDRW has been replaced, so I can't go back to it. I'm now trying your new patch, and it's installing as I type this!

 

I really don't know why the SSE3 kernels don't work on my P4 Prescott (which definately has SSE3).

 

I'll let you know when it's fully installed if there are any issues. I had 1099 installed with the Maxxuss patch, and like I reported elsewhere, it took about 1/2 hour to boot into the installer (I had to disable USB), and after I rebooted, it took 1/2 hour to boot as well. Once there, it was rocket fast, and subsequent reboots were like 10.4.1. I got that working only with his last "test" patch (the very last patch he released for that version).

 

Install now 96% of Base System Part 1. I'll report back shortly...

Thats great guys I am glad to help.

Good Job patching and getting it to install :(

Hardware Overview:

 

Machine Name: Apple Development Platform

Machine Model: ADP2,1

CPU Type: ADP2,1

Number Of CPUs: 1

CPU Speed: 2.67 GHz

L2 Cache (per CPU): 1 MB

CPU Features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM SSE3 MON DSCPL TPR

Memory: 1 GB

Bus Speed: 533 MHz

Boot ROM Version: EV91510A.86A.0475.2005.1110.1243 (Intel Corp.)

 

Intel Graphics Media Accelerator 900:

 

Chipset Model: GMA 900

Type: VGA-Compatible Controller

Bus: Built-In

VRAM (Total): 256 MB

Vendor: Intel (0x8086)

Device ID: 0x2582

Revision ID: 0x0004

Displays:

Display:

Status: No display connected

CPD-100ES:

Resolution: 1024 x 768 @ 85 Hz

Depth: 32-bit Color

Core Image: Supported

Main Display: Yes

Mirror: Off

Online: Yes

Quartz Extreme: Supported

OK good but to let you know you dont need the boot loader patch with the ppf.it applies it for you along with everything else

applying the boot loader first could cause issues.

 

I realized that while it was installing. The reason why I didn't think it installed right was because I mounted the .iso with the thing in VMware. Then I mounted it with Daemon and it worked fine. I did apply the patch twice, and with a whole 5 minutes of testing it last night it showed that it was unbeliveablely slow. Does your ppf delete the the AppleTPMACPI?

 

I am going to test it out some more right now.

Thats great guys I am glad to help.

Good Job patching and getting it to install :(

 

To save space on my 3GB drive, I deleted a bunch of "non-essential" items in my Library, Application, and System folders. My 300 MB free went to over 1 GB free!

 

Hey, who needs mach_kernel anyway lakdhlkjdflkjal;sgflkasjflkj KERNEL PANIC

 

:(

I realized that while it was installing. The reason why I didn't think it installed right was because I mounted the .iso with the thing in VMware. Then I mounted it with Daemon and it worked fine. I did apply the patch twice, and with a whole 5 minutes of testing it last night it showed that it was unbeliveablely slow. Does your ppf delete the the AppleTPMACPI?

 

I am going to test it out some more right now.

 

No it doesnt you can delete it yourself.

I got the DVD patched ok, and burned it and it gets me to the Press any key to install Mac OS X or f8 for advance startup options, and if I press Enter, it thinks for a second, and the gives me the same option. The first time it booted, it looked like it was going to work, and now it is stuck in that loop. Anything I can do to get it to run?

I got 10.4.1 to run perfect, but wanted to try 10.4.3. Its a Dell Precision 360 BTW, case that matters.

i dont get it. im on an sse3/nx/pae athlon x2 3800+ yet no matter wat i do, only YOUR ppf patch for sse2 nonx works and i can get past the damned kernel panic error. im gonna try installing with this first, then copying over orginial mach_kernel seperately.

i dont get it. im on an sse3/nx/pae athlon x2 3800+ yet no matter wat i do, only YOUR ppf patch for sse2 nonx works and i can get past the damned kernel panic error. im gonna try installing with this first, then copying over orginial mach_kernel seperately.

 

I know why.The reason is that maxxuss only released the sse3 kernel patched for nx.the test3b sse2 kernl is patched for cpuid also.your amd doesnt have the cpuid the kernel is looking for.the cpuid limit is used my pentiums with htt.

 

I would get the same panic untill I disabled the cpuid limit in the bios.

 

here is the info on CPUID straight from intels site

 

CPUID Maximum Value Limit

 

Common Options : Enabled, Disabled

 

Quick Review

 

When the computer is booted up, the operating system executes the CPUID instruction to identify the processor and its capabilities. Before it can do so, it must first query the processor to find out the highest input value CPUID recognizes. This determines the kind of basic information CPUID can provide the operating system.

 

The maximum CPUID input value determines the values that the operating system can write to the CPUID's EAX register to obtain information about the processor.

 

Intel processors from the Pentium Pro onwards have a maximum CPUID input value of only 02h or 03h. The only exception is the Intel Pentium 4 with Hyper-Threading Technology (HTT).

 

Older operating systems like Windows 95/98 and Windows Me were released before the Intel Pentium 4 with HTT and are therefore not aware of such a processor. They are not capable of handling the extra CPUID information provided by the processor with EAX input values greater than 03h.

 

This is where the CPUID Maximum Value Limit BIOS feature comes in. It allows you to circumvent problems with older operating systems that do not support the Intel Pentium 4 processor with Hyper-Threading Technology.

 

When enabled, the processor will limit the maximum CPUID input value to 03h when queried, even if the processor supports a higher CPUID input value.

 

When disabled, the processor will return the actual maximum CPUID input value of the processor when queried.

 

It is recommended that you leave it at the default setting of Disabled. You should only enable it if you intend to use the Intel Pentium 4 processor with Hyper-Threading Technology with an operating system that does not support it.

 

Please note that this BIOS feature only allows the Intel Pentium 4 processor with Hyper-Threading Technology to work with operating systems that do not support it. It does not enable the processor's advanced capabilities for such operating systems.

×
×
  • Create New...