Thanks to this thread I've fixed it to not have to use a bat file as the default browser anymore, made it Vista/Win7 compatible (hopefully..? Someone tell me if it works.), and unrelatedly made it enable User Scripts, as well.
http://logicplace.com/pc/projects/ch...ionManager.bat

Maybe I should start updating in/a mod should move this to the tools forum instead, seems more appropriate. :S

Ask and ye shall receive.

Originally Posted by devilslackey

Ask and ye shall receive.

Thanks. :]

BIG update today. I was missing a few things in the manifest wizard, so I redid the whole thing, and made it a command based manifest editor! Woo..that was fun to do in batch. :S
When you create a new extension, it'll start that thing; just type help for a list of commands. I debugged it as best I could, but I would guess there still might be one or two obscure ones, so post them if you find them.

is this only for WinXP?

Looking at the code (and based on his comments above) it's Win7/Vista/XP compatible.

Nice work Waha.

*her
Yeah it should be thanks to that one post of yours, but I don't have Win7 or Vista to test it on, so I can't be sure until someone that does tests it. *hint hint*
After all the only compatibility check I added was for registry edits, I'm just hoping that BATCH hasn't changed much from XP to Vista to Win7.

It hasn't. I haven't tested ALL features but what I did worked just fine. And I looked it over and it correctly matches all Win7/Vista paths (files and reg keys).

Also I don't think it's necessary to kill explorer, I'm pretty sure all those reg changes are on the fly.

Originally Posted by devilslackey

It hasn't. I haven't tested ALL features but what I did worked just fine. And I looked it over and it correctly matches all Win7/Vista paths (files and reg keys).

Also I don't think it's necessary to kill explorer, I'm pretty sure all those reg changes are on the fly.

Sorry, that was for when it had to change the default browser, I forgot to take it out. ^^;

Updated for Chrome dev version 3.0.189.0

Updated the packing system, chromium_extension.py is no longer needed (and no longer works anyway.)
"Run Chrome ... by default" options now affect .crx files.
Creating a new extension creates it in a new Projects folder in Chrome\User Data\Default, this is where the packaging system looks for extensions to pack, as well. You must pack and install an extension to test it. You can however edit the files in Extensions after installing it once.

EDIT: Fixed a couple bugs in the manifest error, mostly in deleting content from a content_script declaration, also in trailing commas.