Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


xnguard

Member
  • Content Count

    13
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About xnguard

Contact Methods

  • Website URL
    http://
  1. Working fine so far on XPSP3 (using the installer). I notice you've updated msi2xml to 2.2.1.957, although it's not in the release notes. Thanks for that; it removes the dependency on the deprecated/insecure MSXML4.
  2. Got three pop-ups for device detection during install: "Plug and Play monitor." Drivers auto-installed after a few mouse clicks. Other than that, completely uneventful, and the only thing that didn't work was the .NET 3.5 install. All the other add-ons and hotfixes slid in with no problems. There's definitely something about 3264.
  3. Just FTR, I'm using a legit key. Corporate network, personal laptop, consultant, long story. (At least, I assume it's a legit key. I don't have anything to do with software licensing here. It passes WGA checks for Microsoft/Windows Update, downloads, and the like.) And, in a quick update, it looks like nLite is happily taking the presets I used for SP3 3264 last night and running with them on a vanilla SP2 slipstream. I'm actually seeing it applying Kel's runtimes, Rogue Spear's .NET 2.0 and 3.5-lite, and other cabinets that it wouldn't touch last night. With luck, maybe it'll apply the users, passwords, and other junk that wasn't working before. I bet this one's going to work. If it doesn't, I'll post an update.
  4. Well, I haven't figured out why nLite isn't integrating hotfixes or drivers properly with SP3 3264, but I found my own answer for why I couldn't install sound drivers. There's no UAA support in SP3, none planned before RTM, and the existing UAA hotfix that's included with most HD audio drivers (like the Sigmatel HD) refuses to install on SP3. So, that, at least, isn't nLite's fault. (I'd like to know why SP3 includes SDHC reader support, but not UAA, considering how many more systems have UAA audio devices than SDHC readers hanging off a native system bus.)
  5. NLITE IS NOT FOR CORPORATE USE!!! Yep, that's why I haven't told Desktop Support that I'm using it. ETA: Actually, I should clarify that: personal laptop.
  6. Hi, I'd just like to add that I'm experiencing issues with 3264 and nLite as well. I used nlite and 3244 with no problems, but I can't make a working 3264-slipstreamed install (en_US). I've tried with and without the 3244 presets; I've tried with and without integrated drivers; I've tried with and without integrated hotfixes. What I keep getting is an XPSP3 install that works fine -- no errors at all during nLite's run -- until I try to get sound working on the XP install. The drivers (Sigmatel HD audio on Intel G945) insist that there's no supported hardware present, and the Windows device manager claims that there's an "Unknown PCI" device that I can't install any drivers for. About the only thing I haven't tried is a slipstream of SP3 with no nLite usage whatsoever. That's next. ETA: I'd like to provide logs/presets, but I'm using this in a corporate environment with some sensitive things in the presets, including the corp product key, and I don't have the time to go through the logs or presets and remove the things that corporate security wouldn't want me giving out. Sorry.
  7. Here's another hackish idea: USSF. Not many executables support the peculiar selection of switches that modern MS hotfixen do... EDIT: Or, here's something a little less hackish. At some point after an attempt to identify the hotfix with TrID, try to list the contents with cabextract: That's pretty definitive. But, if it's not definitive enough, here're the contents at the top of "_sfx_manifest_": You'd think that cabarc would be able to extract a cabinet from an SFX, but noooo... Anyhow, cabextract appears to be [L]GPLed. It's over here, and it's available as a DOS or Cygwin binary. Or perhaps a way to use the author's libmspack directly from AutoIt?
  8. Still unofficial, still unsupported. But I've confirmed that it works on Windows Server 2003 R2 SP2.
  9. I'm finding that none of the recent Microsoft hotfixes -- official or unofficial -- are being extracted correctly by UniExtract. I have a perfect, public example: one of the June security hotfixes. The bulletin is here. The patch download (for WinXP SP2) is here. (This applies to both Universal Extractor 1.5 and to Universal Extractor x 1.5.0.1 with updated TrID defs.)
  10. Sorry, not unless someone's willing to provide me hosting space for it. I can put it up on more of the free file hosting services, but that's about it.
  11. I compiled it myself, using the InnoSetup sources that Jared makes freely available on his site.
  12. This is a completely unofficial and unsupported update for Internet Explorer 7 running on XP SP2 (ENU). It's not intended to run on any other platform. It contains the following files: urlmon.dll 7.0.6000.20544 jsproxy.dll 7.0.6000.20520 ieframe.dll 7.0.6000.20544 wininet.dll 7.0.6000.20544 mshtml.dll 7.0.6000.20593 jscript.dll 5.7.0.20550 To the best of my knowledge, these are the most recent, publically-available incarnations of these core IE7 components. This satisfies all the KnowledgeBase errata entries for IE7 that I'm aware of as of right now. So you know what you're getting into: it's been tested on this machine. For a few hours. On a few websites. Obviously, I haven't spent a lot of time on QA testing. And it's not uninstallable. Make a System Restore point, or something. That said, it's over here (MegaUpload).
  13. UNOFFICIAL RELEASE: Universal Extractor x 1.5.0.1! Changelog from 1.5: 1.5.0.1 (06/26/2007): Recompiled UniExtract.au3 with AutoIt v3.2.4.9, packed with UPX 3.00 using --ultra-brute Changed URL in UniExtract.au3 to point to MSXML6.0SP1 (MSXML4 is strongly deprecated) Updated 7-Zip engine to 4.48 beta Updated PeaZip engine to 1.8 Updated TrID defs to 06/12/2007 Updated RAR engine to 3.70 Updated UPX engine to 3.00 Updated InnoUNP engine to 0.19 Removed Spanish, Chinese, Japanese, Thai, Vietnamese translations due to lack of sources This release has sorta-approval from The Man himself; I've tried to strike a balance between making it clear that this isn't one of Jared's official releases, while still making sure his name's well-plastered on it (since he did the actual coding, and I'm merely supplying some butchery). Yes, that's today's release of 7-Zip. Yes, I know that the DLL version string says "4.47". I dinna compile it. Grab it here on MegaUpload (apologies; I don't have hosting). Edit: I should make clear that this release has only been tested on a few machines, in a few scenarios, in English language, on XP SP2 x86. But it's not exactly a striking departure from 1.5. Edit: ...aaaand I forgot to re-recompile UniExtract.au3. The internal strings say "1.6." Please disregard that. That was my first version string before I talked with Jared and he asked me to make it more clear that it wasn't an official release.
×
×
  • Create New...