Jump to content

how do i remove the sse2 patch i have a sse3 prosser


noolol
 Share

20 posts in this topic

Recommended Posts

IM RUNNING 10.4.3 BUILD 0F1111 WITH JAS PATCH 4.1

 

 

You dont have to remove, you have to overwrite with the original.

 

Here is the solution:

Open terminal and type

 

sudo -s

password:

 

copy the attached mach_kernel .orig into your main instalation (where you see folders like Applications, Library, System, Users....etc )

 

again into terminal type these:

 

mv mach_kernel.orig mach_kernel

sudo chmod -R 755 /mach_kernel

sudo chown -R root:wheel /mach_kernel

exit

exit

 

close terminal and reboot. ( and push the easy button.. )

 

here is the file>EDIT: Removed content violating DMCA

Edited by Metrogirl
Link to comment
Share on other sites

  • 3 weeks later...
As maxxuss says "Users with a SSE3 CPU please note, that the SSE3 Emulator does not degrade your system performance in any way; the emulation is just not used if your CPU has the SSE3 instruction set."

 

 

Yepp is true, but I found my mac working better with original core.

 

"mv mach_kernel.orig mach_kernel"

 

this code doesnt work

the mach_kernel.orig is in root of the harddrive. (where you see folders like Applications, Library, System..etc)

 

 

It should work. Why is not working for you?....did you check after you replaced the kernel?...

Link to comment
Share on other sites

Yepp is true, but I found my mac working better with original core.

It should work. Why is not working for you?....did you check after you replaced the kernel?...

 

 

I tried the same thing. it says that the file or directory does not exist.

i tried a bunch of things that would net the same results as what you wrote up there, but it always either came back to the file being write protected (when working outside of the terminal) or the file not existing when pointing to the kernel in the root folder in sudo -s mode too.

Link to comment
Share on other sites

I tried the same thing. it says that the file or directory does not exist.

i tried a bunch of things that would net the same results as what you wrote up there, but it always either came back to the file being write protected (when working outside of the terminal) or the file not existing when pointing to the kernel in the root folder in sudo -s mode too.

 

So if you cannot find maxxuss type mach_kernel, ( because the tutorial says to check for maxxuss kernel ) it means YOU ARE USING the original one.

 

So if you cannot find maxxuss type mach_kernel, ( because the tutorial says to check for maxxuss kernel ) it means YOU ARE USING the original one.

 

 

probable you didnt got the meaning of these:

 

Also you can check if the change was succesfull or not by typing into terminal:

 

strings -a /mach_kernel | grep -i maxxuss

 

 

if still there your SSE2 kernel you getting this message:

 

MAXXUSS No-NX/XD Patch 8F1111A

MAXXUSS CPUID Patch 8F1111A

MAXXUSS SSE3-Emulator v4.1-8F1111A

Link to comment
Share on other sites

if still there your SSE2 kernel you getting this message:

 

MAXXUSS No-NX/XD Patch 8F1111A

MAXXUSS CPUID Patch 8F1111A

MAXXUSS SSE3-Emulator v4.1-8F1111A

 

MAXXUSS RTC Patch 8F1111A

MAXXUSS No-NX/XD Patch 8F1111A

MAXXUSS CPUID Patch 8F1111A

MAXXUSS SSE3-Emulator v4.2b-8F1111A

 

 

not only am i running everything that i dont need, im also running the RTC patch (which i dont know what is for)

so how can i rectify this?

Link to comment
Share on other sites

MAXXUSS RTC Patch 8F1111A

MAXXUSS No-NX/XD Patch 8F1111A

MAXXUSS CPUID Patch 8F1111A

MAXXUSS SSE3-Emulator v4.2b-8F1111A

not only am i running everything that i dont need, im also running the RTC patch (which i dont know what is for)

so how can i rectify this?

 

 

ok so this is what i did.

 

i made a new folder. put the mach_kernel.orig in the /New Folder/

 

then opened the terminal

 

sudo -s

 

mv /New Folder/mach_kernel.orig mach_kernel

 

then i did the chmod and chown

 

then i restarted.

 

 

upon booting up passed darwin, i got [double panic] error and a screen that got progressively darker every time the kernel boot whiped the screen.

 

whats giong on here? whatd i do wrong?

Link to comment
Share on other sites

Whats wrong?...hehehe....you did a new folder......nobody told you to do that ...LOL

 

Just copy that freakin mach_kernel.orig main instalation folder......and do what you have to do....

 

 

would you like me to post a screenshot of what happens so that you can see that i know how to follow directions perfectly?

 

 

its not very hard to drop a file where people tell you to, run the proper commands, and get stuff done.

but when the stuff doesnt work. it DOESNT work.

 

 

thats what me, and about 4 other people are experiencing.

and anyways.. when i made the new folder, i only made the new folder so that the terminal could locate the file. in the end, it ended up being in my root folder anyways.

 

so it still boggles my mind how it stopped working and double paniced on me.

 

also, as soon as i did do that, my wireless internet cut out.

 

 

and after running the check to see if i was in the clear, i didnt get any maxxxuss patch showing up or anything.

Link to comment
Share on other sites

copy the attached mach_kernel .orig into your main instalation (where you see folders like Applications, Library, System, Users....etc )

 

again into terminal type these:

 

mv mach_kernel.orig mach_kernel

no such file or directory

Link to comment
Share on other sites

no such file or directory

 

If you used the JaS 4.2b PPF patch do this:

 

sudo mv /Pacthes/mach_kernel.original /mach_kernel

 

Then repair disk permissions from the disk util. Yes, "Patches" is spelled wrong in the "sudo mv..." command. That's how it was on my system on a clean install with a JaS 4.2b patches dvd.

 

As for the kernel panic...I got that too when I removed the CPUID patch. I just run the full patched kernel and don't bother messing with it anymore.

Link to comment
Share on other sites

If you used the JaS 4.2b PPF patch do this:

 

sudo mv /Pacthes/mach_kernel.original /mach_kernel

 

Then repair disk permissions from the disk util. Yes, "Patches" is spelled wrong in the "sudo mv..." command. That's how it was on my system on a clean install with a JaS 4.2b patches dvd.

 

As for the kernel panic...I got that too when I removed the CPUID patch. I just run the full patched kernel and don't bother messing with it anymore.

i don't know what's wrong but still i have maxxuss' patches

Link to comment
Share on other sites

hya,

 

i did everythning like it was described on my computer. (p4 2.8 prescott).

 

now i cannot boot up osx86 anymore. the boot screen comes up and system restarts. any clues? i forgot to save my old mach_kernel. anyone can send me the patched sse2 and so on mach_kernel and tell me how to get it on my system? would be nice.

 

 

thanks in advance!

Link to comment
Share on other sites

ok.. well what you should have done was make the patches, but just rename them...

 

mach_kernel.001 - RTC patch

mach_kernel.002 - CPUID patch

 

and so on. those are examples.

 

you shouldn't overwrite your original kernel.

because you can press F8 to load darwin console before it goes into MacOSX, and then you can type:

 

mach_kernel.001 -v

 

and it will load that kernel. and if it panics, it will throw a code. so you know what error you're getting.

 

you keep trying different kernels until you find out which one works for you. then you replace the mach_kernel with the one that works for you.

 

dont replace it with a kernel that you havent tested.

i made that mistake and had to format/reinstall.

Link to comment
Share on other sites

 Share

×
×
  • Create New...