Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/03/2014 in all areas

  1. 1 point
  2. Maybe you would like to try programming a massive program whilst doing a degree with exams and coursework. Most of those bugs will be to do with drivers. This is precisely why I'm starting from scratch. The code at the moment is old and crappy to the point things keep breaking when I try to fix and add a new feature. It's doing my head in lol! I'm balancing my time between programming v2, fixing v1 and prob playing Watch Dogs too The code on v2 is looking completely different than v1. It's so much more neater, tidier and quicker but much more importantly, easier to work with I even have a Visual Studio extension ReSharper (I think) which is making sure I code well too. It picks up way too many things on v1 to fix them all Point is, I'm doing my best.
    1 point
  3. you could also: put the vbcredist_aio_x86_x64.exe in "wim":\temp\vbcredist_aio_x86_x64.exe create "wim":\windows\setup\scripts\setupcomplete.cmd with this code in it: @echo offset startupcmd="%programdata%\microsoft\windows\start menu\programs\startup\runonce.cmd"> %startupcmd% echo @echo off>>%startupcmd% echo start /w "%systemroot%\temp\vbcredist_aio_x86_x64.exe /y">>%startupcmd% echo del /f /q %systemroot%\temp\vbcredist_aio_x86_x64.exe>>%startupcmd% echo del /f /q "%%~f0" 2^>nul ^& exit
    1 point
  4. You can stick it in your autounattend.xml file. I do it like this: 1. Create the $OEM$ folder in the Windows source to dump the switchless into the %SystemRoot%\Temp folder, like so: (Windows installer source root)||-- $OEM$ | |-- $$ | |-- Temp2. Copy the switchless to "Temp". 3. Set up your autounattend.xml to do a "SynchronousCommand" under "FirstLogonCommands" in the "Microsoft-Windows-Shell-Setup" settings, "oobeSystem" pass. Here's a snippet from my autounattend.xml (Win7 Ultimate x64) using the VB/C++-only installer: <?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>%SystemRoot%\Temp\VBCRedist_AIO_x86_x64.exe /ai</CommandLine> <Description>Microsoft Visual B/C++ Redistributables (AIO)</Description> <Order>1</Order> </SynchronousCommand> </FirstLogonCommands> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/win7dvd/grmculxfrer_en_dvd/sources/install.wim#Windows 7 ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>You can run multiple commands as well if you only install certain components. For example, to do VC++ 2005 and 2008 only executing the /ai5 and /ai8 switches: <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>%SystemRoot%\Temp\VBCRedist_AIO_x86_x64.exe /ai5</CommandLine> <Description>Microsoft Visual C++ 2005 Redistributable</Description> <Order>1</Order> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <CommandLine>%SystemRoot%\Temp\VBCRedist_AIO_x86_x64.exe /ai8</CommandLine> <Description>Microsoft Visual C++ 2008 Redistributable</Description> <Order>2</Order> </SynchronousCommand> </FirstLogonCommands>Add as many commands as you need, just bumping the "<Order>" number for each successive entry. Notes: -- You can change the install directory to whatever you want, so long as you put it in the proper $OEM$ folder structure. I chose Windows\Temp so the installer gets auto-deleted after use. -- It must go under the "oobeSystem" pass to launch after user creation, or else you'll get the same errors as before. -- Same method should work for most programs that have the same requirement of being run after user creation. -- There are probably other methods of doing it which other posters could elaborate, but this one has worked flawlessly for me with this particular switchless. And is good if you already use autounattend.xml and want to keep things nicely consolidated there. -- WSIM automates creation of autounattend.xml graphically if you don't want to deal with raw XML syntax. Download the Windows ADK from Microsoft (http://www.microsoft.com/en-us/download/details.aspx?id=30652) if you need that tool.
    1 point
×
×
  • Create New...