Jump to content

sublimies

Member
  • Posts

    5
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About sublimies

sublimies's Achievements

0

Reputation

  1. Ok here is the problem I think. Setupmgr.exe left this out for some reason and Nlite wrote it wrong [unattended] UnattendMode=FullUnattended UnattendSwitch="No" OemPreinstall="No" OemSkipEula="Yes" ProgramFilesDir="d:\Program Files" CommonProgramFilesDir="d:\Program Files\Common Files" FileSystem=* WaitForReboot="No" NoWaitAfterTextMode=1 NoWaitAfterGUIMode=1 DriverSigningPolicy=Ignore NonDriverSigningPolicy=Ignore Notice the bold section. That should say Yes. How could Nlite miss that? Or perhaps it has something to do with another setting I used. Go figure
  2. Well I have been using Nlite mostly and have been having trouble with it no getting past the Regional Settings and the OEMWelcome screen. I then replaced the Nlite Winnt.sif with on made by Setupmgr.exe and I can get past the regional settings thing, but I still get windows stopping at the screen letting me know that windows is adjusting my visual settings and once I'm past that I have to deal with the **** OEM welcome. Please some save my sanity. Here is the setupmgr winnt.sif ;SetupMgrTag [Data] AutoPartition=1 MsDosInitiated="0" UnattendedInstall="Yes" [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=No TargetPath=\WINDOWS [GuiUnattended] AdminPassword="XXXXXXX" EncryptedAdminPassword=NO AutoLogon=Yes AutoLogonCount=1 OEMSkipRegional=1 TimeZone=4 OemSkipWelcome=1 [userData] ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX FullName="None" OrgName="None" ComputerName=None [TapiLocation] CountryCode=1 Dialing=Tone AreaCode=909 [RegionalSettings] LanguageGroup=8,10,9 [identification] JoinWorkgroup=MSHOME [Networking] InstallDefaultComponents=No [NetAdapters] Adapter1=params.Adapter1 [params.Adapter1] INFID=* [NetClients] MS_MSClient=params.MS_MSClient [NetServices] MS_SERVER=params.MS_SERVER [NetProtocols] MS_TCPIP=params.MS_TCPIP [params.MS_TCPIP] DNS=No UseDomainNameDevolution=No EnableLMHosts=Yes AdapterSections=params.MS_TCPIP.Adapter1 [params.MS_TCPIP.Adapter1] SpecificTo=Adapter1 DHCP=No IPAddress=192.168.2.102 SubnetMask=255.255.255.0 DefaultGateway=192.168.2.1 DNSServerSearchOrder=68.238.64.12 WINS=No NetBIOSOptions=0
  3. I think I know exactly what you are talking about, well maybe. If you are trying to install an MSI file I have had the same problem. First you can use run("myfile.msi") The path I THINK is run("msiexec /i myfile.msi") That has worked when I'm in windows, but when I install from RunOnceEx it gets an error.
  4. Sounds like a very useful program. Remind me of a program called Driverguide toolkit. Only problem is, even if I know the name of the device how would I find it in the mass of sneaky's driver pack?
  5. Is there anyway to make this driverpack work so if I have a windows install with an unidentified device could scan all possible drivers in the pack? Because I'm not sure what manufacturer it is.
×
×
  • Create New...