Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations


Posts posted by Alanoll

  1. The real question I have is...

    The Unattended Guide is a Wiki, why don't you, Paradox, add the information?

    Did i misread this, is there a Vista Unattended Wiki? The XP Wiki is great, and i'de be happy to start contributing to a Vista one, but havn't found it yet?


    Who said anything that the "XP Wiki" is a XP wiki? I believe the title of the project was "Unattended Windows" :P

  2. I've seen this caused when you either improperly or didn't edit one of the needed files properly. The boot sector, setupldr.bin need to modifed to point to the new OS locations (or boot folder locations depending on the OS). TXTSETUP.SIF is only used once SETUP starts.

  3. 1. This is not a warez site! Links/Requests to warez and/or illegal material (porn, cracks, serials, etc..) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/keygens or any other illegal activity will also not be tolerated. You will be banned without notice.

    You sir have admitted to downloading a copy of Windows, and then requesting help. This falls under "Discussion of any other illegal activity".

    Topic Closed.

  4. did you read the license agreement of nLite?

    despite the fact that it'll violate both the nLite license agreement and the microsoft agreement, in a business environment this could lead to bad bad things...

  5. No. The way nLite alters the files, breaks WFP. Turning it off during install will prevent the popups then, but once reenabled...windows periodically runs the scan to check file status, so it will show up again.

    I would suggest not using nLite on any system that isn't your's or on someone's machine that knows what they're doing. You may find all the MS stuff a hassle, but In-Laws especially none tech savvy ones may not even know what you're talking about. I know, I can ramble off a few big words to the faculty at my university (I'm also tech support), and they'll instantly agree with my assesment because of my title and the vocabulary I'm using. Most of the time however, I'm just trying to educate them in that "if it ain't broke, don't fix it". MS's stuff works fine out of the box, as intended.

  6. I'm closing this thread, and then i'll read through for any offenses. I saw one just skimming the thread.

    EDIT:: Re-opening.

    I saw nothing wrong with this thread. I do see ONE user that got a little out of hand.

    *DISCLAIMER* I'm speaking on behalf of MYSELF and NOT MSFN *DISCLAIMER*

    As a side note, I personally don't like ASPECTS of nLite. I love the concept, and the execution is great. I don't like it when people who have no idea what components are, strip them out and then complain their favorite little program doesn't work. Now, I'm not referring to those who are doing trial and error... I'm talking about those that use nLite because "it's the cool thing to do." With the same regard, I don't like how nLite combining the unattending and removals. Now don't get me wrong, it's great having everything in one place, but at the same time that just brings more trouble. Again...from the people that just jump on the band wagon.

    I've always been a fan of the read up on something before you do it. Then find an easier way to do it. You wouldn't go skydiving without getting instruction would you?

  7. http://unattended.msfn.org

    How would you get the install files off your CD to install with? That's what the $OEM$ folder is for.

    like BIRDS had previously stated, I can use something like nLite add-on maker to create a .cab for a program and use nLite to insert it in the HOTFIXES and UPDATES. Hopefully I can do that and not have to create the $OEM$ folder?....I want to verify with a couple of more responses from others before I do this. Thanks

    yes you can, that's the whole point of the CABs

  • Create New...