RyanVM

, you could have just asked me to send you the English checksum info . But make sure you're using the QFE versions of the files, not the GDR versions. (I say that because the hotfix installers by default copy the GDR versions to system32, but that's only good if you're installing the hotfix from the EXE. For integrating like we're doing, the QFE version is the better one to use). 13720 is the checksum for the QFE version of extmgr.dll EDIT: Build date is "Mon Oct 25 19:26:47 2004"

QFECheck is going to really hate the different files. The checksums aren't going to match up with their registry entries (not that that can't be worked around). Not to mention that WFP will no longer protect the files since their checksums will different from their security catalogs (can't be worked around).

Also, there seems to be some confusion as to what my pack is intended for. I still get people asking me if I plan to make an SP2 version of my pack . I wondering if I should rename it to make it more clear that the pack for those with SP2 already integrated into their CD. Maybe SP2.1 update pack or something? What do you guys think?

People are continually ignoring the rules even after it's been brought up in the thread

Great work! Thanks! Huh? Cool. Well, if you're just getting started, why are you trying to do more advanced work? You gotta learn to crawl before you learn to walk. Heh, oops. I'll get that added in with the next release. Like my website says, the Lite pack should be OK for non-English users, but I can't make any guarantees. Especially because hp38guser just told me that KB834707 is a language-dependent update.

@The Black Cloud: OMFG, ARE YOU REALLY THAT STUPID???

Great, keep the feedback coming!

You're 100% correct as far as I know.

Sorry, I have very little tolerance for those who blatantly ignore the rules.

Read the rules, id***.http://www.msfn.org/board/index.php?showtopic=18408

The switches for those hotfixes are the same as all the rest of the post-SP2 hotfixes.

You're sure you're integrated the correct drivers for the TV8237?

The best list I'm aware of is my own list at http://www.ryanvm.net/msfn/ The switches for all post-SP2 hotfixes are the same (so far anyway): /q /n /z And of course, they also all support the /integrate command.

Sorry I just think thats funny. I have never and I mean ever had a drive fail, is it the manufacturer and or type or this bogus crud they trying to sell or promote? My first drive I ever personally had is still in use and has been formatted probably over 200 times including low level, its a Seagate. shhhh don't tell my inlaws Only drives I ever had problems with were Maxtor btw Consider yourself lucky. I've personally had 4 drives die on me, all within the last 5 years or so.

Thanks, keep 'em coming

He could be using Win2K... And to the thread starter, use descriptive thread titles. You're much more likely to get help when people browsing the forum have a clue as to what your thread is about. In fact, there's even a rule about that. I'd say you should spend some time reading and familiarizing yourself with them so you don't make the same mistake in the future.

Since you're new here, you should really be versed in the rules before posting. One of the rules is: http://www.msfn.org/board/index.php?showtopic=18408 Please do we who post here frequently a favor by reading those and keeping mind of them in the future. Thanks

Yeah, this one's just a bit cleaned up and more flexible than the last one. EDIT: I just upped a newer version which allows the user to change the Mozilla Version and Gecko Version numbers.

OK, here's a page with links to download some test builds. Please try these out and let me know which ones restart the computer and which ones don't (and the circumstances they were launched under, ie GuiRunOnce, Double click, etc...). http://www.ryanvm.net/msfn/jretestbuilds.html

Alright, check this out. I made it more customizable, so you can now specify independent versions and locales. The INF called be called in a few different ways: Both Firefox & Thunderbird Installed rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 132 "path\to\mozilla.inf" Only Firefox Installed rundll32.exe setupapi.dll,InstallHinfSection Firefox 132 "path\to\mozilla.inf" Only Thunderbird Installed rundll32.exe setupapi.dll,InstallHinfSection Thunderbird 132 "path\to\mozilla.inf" The INF has a [strings] section which can be customized as newer versions are released or if users want to specify a locale other than US English. The string names should be pretty self-explanatory. [Strings] ;DO NOT EDIT THESE STRINGS Clients="SOFTWARE\Clients" MozKey="SOFTWARE\Mozilla" Firefox="Mozilla Firefox" Thunderbird="Mozilla Thunderbird" ;EDIT THESE AS NEEDED FxLocale="(en-US)" FxVersion="1.0" GeckoVersion="1.0.1" MozVersion="1.7.5" TbLocale="(en)" TbVersion="0.9"Now who wants to confirm that this all works as it's supposed to? prathapml, I'm looking your way mozilla.inf

Bingo, the 132 did it. I'm going to make a few changes to the INF, and I'll post it here in a bit. The nice thing about the way I've got it set up is that it's very easy to update when new versions come out. All the user will have to do is edit the string(s) at the bottom and they're done.

Solved it with MCT! It looks like having quotes in the path to the INF caused the problem. So now ya know it. I have issues running it even with no quotes (for example, I try running it straight from c:\ and just call rundll32 setupapi,InstallHinfSection DefaultInstall 128 c:\mozilla.inf Any idea? Also, can you try calling just the individual Firefox and Thunderbird sections to make sure they work right?

Yeah, I could cut those extraneous numbers out, but I like consistency

If you're having issues integrating it with nLite, the problem is on his end, not mine. nLite doesn't use the patched files included with my pack. It ignores them when extracting the CAB file and patches them manually. Take it up with nuhi.

1.) You disabled WFP via the registry key? I state very clearly that WFP remains enabled by default with my pack. The hacked DLL just gives the user the option of changing it via the registry if they so desire. 2.) I've tested the included uxtheme.dll myself and confirmed it works. Want to send the theme you're trying to use so I can test it on my end? 3.) You realize that nLite can integrate my pack directly, right? You can add the CAB like any other hotfix to be integrated (as my directions state).