Jump to content

Sancho

Member
  • Posts

    49
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Sancho

  1. You should only take the patches your OS needs. Not good to smash and grab every file just because it's there.
  2. Clearly there is an error taking place. Best to start over and go through the process again, making sure nothing is awry.
  3. Both options I mentioned are under Hardware Support. Sorry, no clue on how to get it back or what files it takes out.
  4. Sancho

    Windows 2X

    Run nLite on a 2000 source and check off everything for removal. Then do the same for the XP source. Compare each Last_Session.ini for differences. You can save the session and rename it as soon as you check off the boxes, with the options at the bottom.
  5. I had that problem with my digital camera, and I think it might have also needed the Teletext Codec as well. It was either that or Video Capture, one is needed for the camera driver and the other for WIA to work right.
  6. I have a bunch of edits I always put into this file, but they are mostly along the same lines as the stuff originally there because not everything works. nLite also duplicates entries with different values, so I tidy it up a bit.
  7. I figure that you still need to check the tweak (in nLite) to disable the thing from coming up (this option has always been there), so maybe it would be best to automatically include that when the thing is removed.
  8. The image is just too big; normally there are more links there to give it room. I don't think you can do anything unless you somehow found the image and edited it. I always have quicklaunch enabled, but I forgot if it was a regtweak or an nLite setting.
  9. Yeah, that's it. Also, I was thinking about making a topic for these, but I waited to long. The other problem I had was with WIA, and it would also fail to start if I took out the Shell Services. WIA seems to be the only way to get images off my camera, so I need to keep this unchecked for it to work at all. Note that this is for Server 2003 and I haven't tried XP recently.
  10. Sancho

    nLite problem?

    What version of Windows? I have had this problem before, and I don't know the exact cause. It may be the edition of Windows you are using. It's happened a few times when I used Server 2003. It's not really that big of a deal, though, you just need to put a new password in when the time is up. If I'm understanding your problem correctly, all you need to do is go to Run > secpol.msc > Account Policies > Password Policy, then disable everything or set it to 0.
  11. Yes, setting either one or sometimes both AU and BITS services to Manual can cause it to fail. This is extremely retarded and nonsensical, but it's the case. Normally you only need to set Automatic Updates to auto, but just the other day I needed to change the BITS to auto as well (on XP).
  12. I just had the same problem, and man was it a fucking bitch. Two services had similar problems and it took about 20 builds to find the exact causes. For the firewall, it seems you are also required to keep the Dialup checkbox for it to work. I don't know what files are being problematic here, but I tried to get all the files taken out by this one checkbox and none of them seemed like they were specifically for the firewall and didn't match any lists I could find that said the required files for it. I've been using nLite for Server 2003, so I don't know if it affects XP or is just something wrong with the latest nLite versions. I have XP installed from a while ago and it didn't have this issue.
  13. Maybe check out "Driverpacks". Could be more than you need, but it's comprehensive.
  14. I guess it's just created. There are Microsoft utilities to create automated installs and they give you the option of what kind of files to use, and it generates what it needs. The only file I remember being there originally is the unattend.txt and some instructions, which nLite deletes.
  15. kerberos for wireless? where do you get that?
  16. wow, what a wealth of information here So which part do you want to fix? If the nLite setup, post the last_session file first. If just the windows setting fix, here's what I easily found by putting the name of the window and "registry checkbox": A. Select the "Don't display this page at logon" check box in the lower-left corner of the Manage Your Server Wizard. You can configure this setting on a per-user basis by performing the following steps: 1. Start a registry editor (e.g., regedit.exe). 2. Navigate to the HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\srvWiz registry subkey. 3. Double-click (Default), set it to 0 to not display the wizard at logon or 1 to display the wizard at logon (the default), then click OK. 4. Close the registry editor.
  17. no, yes, yes if it works another way nLite uses winnt.sif, so if you didn't do some other method for automated installs then it might be broken.
  18. Sancho

    RunOnceEx.cmd

    You could put it in "$OEM$\$Docs\All Users\Start Menu\Programs\Startup" and add an instruction to delete itself. I'm not sure when cmdlines.txt does its thing exactly.
  19. Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] "NoSaveSettings"=dword:00000000
  20. I always set the start menu popup key to 2 instead of 0, in nlite.inf. (first I "extract -r nlite.in_" and delete the original) Well, actually a good amount of tweaks I need to change, so I keep a copy of the file with all the tweaks done right and only need to monitor for different changes done to the file right after processing a fresh disc.
  21. If nLite doesn't give you the option then you need to edit the file manually. Based off of examples, it looks like you just need to separate the IP addresses for whatever setting by a comma and no space after (in WINNT.SIF). If you have DNS servers set then it should show you how.
  22. First find either (or both) HIVEDEF.INF or NLITE.INF and edit it. Search for MenuShowDelay, change the number at the end. You can get rid of multiple entries, but keep the lowest in the file. NLITE.INF is compressed by nLite after processing the disc alterations, so you need to decompress it, which can be done from the command prompt by using "expand -r nlite.in_". Then delete the original file.
×
×
  • Create New...