WM 6.5 Kitchen QVGA and VGA Developer Edition

[joojoobee666]

Originally Posted by focus-pl

Which files are responsible for sound, speaker, wmp etc? Sounds are not working in this sys with 0415 muis..

Are they working with 0409?

[MassStash]

just as i suspected, it was a user error on my part lol jdume's update works perfectly. steeerange tho that's for sure. Thaaaaaaank you jdume, and joojoo for the files of course. I'm sure I'll be needing assistance messing with this in the near future, now that works haha

can the msxipkernal be spinlocked for ervius?

[joojoobee666]

Originally Posted by MassStash

can the msxipkernal be spinlocked for ervius?

Well, there are no files in the MSXIPKernel that can be spinlock patched, but the OEMXipKernel? Sure, patch it all day long.

[MassStash]

Originally Posted by joojoobee666

Well, there are no files in the MSXIPKernel that can be spinlock patched, but the OEMXipKernel? Sure, patch it all day long.

icic, thank you sir. Which files exactly do you usually spinlock? just OEMdrivers and the NK, or nething else?

[joojoobee666]

Originally Posted by MassStash

icic, thank you sir. Which files exactly do you usually spinlock? just OEMdrivers and the NK, or nething else?

smem.dll should get patched too. (OEMXIPKernel)

[fort13]

Cant't build rom with new 21859 xip in PPCKitchen for Apache(stuc past the main splash screen). Even with old 21857 xip. be a problem in SYS_21859_Common?
same with all the XIPs for 2053, that you posted here for Apache (((

[joojoobee666]

Originally Posted by fort13

Cant't build rom with new 21859 xip in PPCKitchen for Apache(stuc past the main splash screen). Even with old 21857 xip. be a problem in SYS_21859_Common?
same with all the XIPs for 2053, that you posted here for Apache (((

Hmm, I have not had any other reports of XIP problems from the 2185x files. I did have some issues with the 23053 and Apache reported. I posted an updated XIP here for that ->http://forum.ppcgeeks.com/showpost.p...postcount=8085

As far as the 2185x stuff, I would imagine that if there was something wrong with the Common files, I would have known. Best bet is to put your buildlog up at pastebin.com so we can all take a look-see.

[fort13]

I tried every 23053 XIP that you posted here for Apache - unsuccessfully.
here my buildlog http://pastebin.com/m72d5de0a

[Wizzard]

joojoo,

It appears that there are some Apaches that are no longer tolerant of the new system changes????

Is there a chance that 23053 and 23414 had something new in them that the Apache doesn't like??

Maybe they are just worn out from all of the flashing???

[joojoobee666]

Originally Posted by Wizzard

joojoo,

It appears that there are some Apaches that are no longer tolerant of the new system changes????

Is there a chance that 23053 and 23414 had something new in them that the Apache doesn't like??

Maybe they are just worn out from all of the flashing???

Originally Posted by fort13

I tried every 23053 XIP that you posted here for Apache - unsuccessfully.
here my buildlog http://pastebin.com/m72d5de0a

Wheew. I don't know, though I doubt they are worn out. That build log looked good to me. But the one thing I can see is that the Apache Core is patching services.exe with a services.exe from 19716. I don't know why that was setup to work that way. That could possibly be why the Apache has been so intolerant lately? Also, I see the build log has the 21859 XIP. So let's try a few things:

1. Extract your Apache_Core.rar to a folder in the Kitchens directory.
2. Edit your DeviceBase text file to reflect the fact that you are NOT using a rar file by removing the [Archive]
3. Delete the Patches folder from the Apache_Core folder (not the rar)
4. Cook a ROM that way, see if it boots. If it does NOT boot, then move on to 5.
5. Use a KNOWN working 2185x XIP, should work fine for a test.