RyanVM

Member
  • Content count

    2,756
  • Joined

  • Last visited

Community Reputation

0 Neutral

About RyanVM

  • Rank
    Like a big surly teddy bear.
  • Birthday 07/21/1983

Contact Methods

  • Website URL
    http://www.ryanvm.net/msfn/
  1. Hey XPero, I've been in your shoes before. It's always good to take a break, but don't be shocked if you eventually start getting the itch to work on it again
  2. Link is dead. Anyone got a mirror?
  3. Either try back later or use the tracker.
  4. Personally, I'd just disable the Webclient service. It serves no real purpose anyway for 99% of users out there.
  5. nuhi said it well. If you're going to use nLite on your CD anyway, just integrate the pack with it too (honestly, I don't know why even MaximumPC thinks otherwise). Just be advised that you're not likely to get much help from me or my forum if something doesn't work right since component removal adds another layer of complexity that I'm not qualified to troubleshoot.
  6. Ding ding ding, we have a winner.
  7. You're wrong because my pack contains IE6 updates which could in theory overwrite those updated IE7 files . As for the ordering, nLite by default doesn't allow overwriting of newer files with older ones, which is probably why things went OK. Or I could be wrong about the reason. nuhi, feel free to correct me if I am
  8. Yes, nLite does know better than you do. You should never, EVER integrate IE7 before my pack. That's a recipe for disaster. EDIT: Same for the MU addon.
  9. Addons exist for integrating both IE7 and WMP11.
  10. FYI, .NET 3.0 includes .NET 2.0 with it, so don't feel compelled to install both individually.
  11. The error you're getting is a known one with WMP10 integration, and it appears to be safe to ignore (it's been known for a long time and doesn't seem to have ever caused any problems). And like boooggy said, there's really no point in integrating WMP10 if you're slipstreaming WMP11 over it anyway. Finally, yes, removing CAT files would break driver signing. That should be rather obvious...
  12. My installer would be kinda pointless if Windows Update didn't detect it... Oh, and VirtualPC = your friend. Instead of waiting for an answer, you could have found out yourself in way less time.
  13. 1.) .NET 2.0 isn't needed if you're installing 3.0. 3.0 includes 2.0. 2.) Try installing 3.0 before 1.1.