Next WM release any time soon?

[gguruusa]

Originally Posted by TurboFool

...

Nicely said.

If there's something that Bepe's v2 buildos is more clear or easier on...let me know. As far as I'm aware, PPCKitchen's buildos is a superset.

I really fail to understand why people think DCD's kitchen isn't compatible.

[TurboFool]

Originally Posted by gguruusa

Nicely said.

If there's something that Bepe's v2 buildos is more clear or easier on...let me know. As far as I'm aware, PPCKitchen's buildos is a superset.

I really fail to understand why people think DCD's kitchen isn't compatible.

Really the primary thing I'm looking for to improve the build process is something that clearly says to me: THIS is the OEM that killed your build. Currently we just get the error about the default.hv and user.hv and have to look through that screen and figure out which was the last RGU it processed, then dig through all the OEM folders to find which one contains that RGU (or maybe there's an easier method I don't know about?). The only thing that seemed a little easier was in DCD's kitchen it showed me at the bottom of the screen what the last item processed was when it failed. But it failed many, many more times because every duplicated file killed the process. Honestly, though, come to think of it, when it came to a registry error I did have to track down the log file and do the same kind of searching, so perhaps it's no better on that aspect. Still, that's something that needs improvement. It's the ONLY thing that makes the PPCKitchen at all difficult for me.

And I was given the impression by others that DCD's kitchen's not compatible. What would I need to do to drop it into the PPCkitchen and make it work? I would have been much happier today if I had known that. Much easier.

[dcd]

Originally Posted by gguruusa

DCD 20273 vs ppckitchen 20270 is not sufficient to determine whether "20273 is noticeably better than 20270"

I skimmed most of this thread and was going to post exactly that but gguru beat me to it.

I never ran 20270, but really 20273 is hardly any different than 19965. The changes leading up to my 3.2.5 were mostly in OEM. I usually wait for a new CE OS to make a new release and that has probably lead to some confusion for users of my stuff, as to what difference CE OS really makes.

Originally Posted by gguruusa

If there's something that Bepe's v2 buildos is more clear or easier on...let me know. As far as I'm aware, PPCKitchen's buildos is a superset.

only the proxy thing, whats up with that? it may not be an issue for me anymore anyways.

I really fail to understand why people think DCD's kitchen isn't compatible.

agreed. other people have packaged it for ppckitchen before and it worked fine. it is still on my list of things to do but i was waiting for that proxy update.

[TurboFool]

Originally Posted by dcd

agreed. other people have packaged it for ppckitchen before and it worked fine. it is still on my list of things to do but i was waiting for that proxy update.

That would be great. I'm running 3.2.5 right now, which is the first time I've run any of yours, and so far it's quite good. I'd love to more easily combine it with the nueTools and get the best of both worlds. I just wish there was an easy way to get nueWiFiSwitch to work with it.

[chevyforlife]

yeah im stayin out of this
~chevy

[gguruusa]

Originally Posted by TurboFool

Really the primary thing I'm looking for to improve the build process is something that clearly says to me: THIS is the OEM that killed your build. Currently we just get the error about the default.hv and user.hv and have to look through that screen and figure out which was the last RGU it processed, then dig through all the OEM folders to find which one contains that RGU (or maybe there's an easier method I don't know about?). The only thing that seemed a little easier was in DCD's kitchen it showed me at the bottom of the screen what the last item processed was when it failed.

Not sure I understand what you're saying, but .hv errors are detected and shown the same way between the two buildoses. The sorry error messaging is really a function of the sorry tool MS provides to build the hive. Errors that occur during the build should be more explicit than the equivalent in Bepe's buildos. If there are error msgs that don't provide everything you need to know, let me know what they are and what you need additionally.

Originally Posted by TurboFool

But it failed many, many more times because every duplicated file killed the process. Honestly, though, come to think of it, when it came to a registry error I did have to track down the log file and do the same kind of searching, so perhaps it's no better on that aspect. Still, that's something that needs improvement. It's the ONLY thing that makes the PPCKitchen at all difficult for me.

And I was given the impression by others that DCD's kitchen's not compatible. What would I need to do to drop it into the PPCkitchen and make it work? I would have been much happier today if I had known that. Much easier.

What have you tried? There are a couple ways to do it...best is to make a selections.txt for it, then you should be able to apply it to each new kitchen he puts out without much effort.

[gguruusa]

Originally Posted by dcd

only the proxy thing, whats up with that? it may not be an issue for me anymore anyways.


agreed. other people have packaged it for ppckitchen before and it worked fine. it is still on my list of things to do but i was waiting for that proxy update.

Have a build for you to try...sent you an IM awhile ago, but I think it got lost on the way

[TurboFool]

Originally Posted by gguruusa

What have you tried? There are a couple ways to do it...best is to make a selections.txt for it, then you should be able to apply it to each new kitchen he puts out without much effort.

To be perfectly honest, I haven't tried anything with DCD in combination with the PPCKitchen. I took others' word for it that it didn't work. How do I make a selections.txt file that independent of the kitchen I'm choosing? Normally the selections files I make get tied directly to whatever kitchen I chose.

[jpc0480]

Originally Posted by TurboFool

To be perfectly honest, I haven't tried anything with DCD in combination with the PPCKitchen. I took others' word for it that it didn't work. How do I make a selections.txt file that independent of the kitchen I'm choosing? Normally the selections files I make get tied directly to whatever kitchen I chose.

I second that one...

[jpc0480]

This was such a live thread, and now nothing?