Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by ianymaty

  1. ianymaty


    Hi Lego. Take it easy. We are here, waiting patiently for your work so we can work too. (By giving feedback to you)
  2. Set them in your Autounattended.xml http://www.wincert.net/forum/topic/9178-create-your-own-autounattendxml-all-in-one-x86amd64/?hl=unattended
  3. Drivers folder go to the root of the install media. Extract the ISO and create the folder than put the drivers in it. The drivers should be each in its folder and among the bunch of files of each driver should be an inf file in order to be installed by the Driver installer at the first login. After the program starts in All-In-One Integrator go to Updates + Languages tab and use the big green + sign on the left to add the Updates. After added all you need click on the Start button in upper left corner. @izicke The updates are for all languages. Only a few are speciffic to some languages and are named accordinglly Don't worry, "Lurker" is just a tag. It may change in time if/after you have more posts
  4. Wow, too many questions for a first post. Welcome to the forum. :welcome: Let's start step by step. I won't answer to all those question now but I give you some tips for start. First of all start with a fresh untouched ISO. You can download all the updates but you can't integrate them all "as is". For start you can integrate all from General, Hotfix and Security folders without any problem "as is" You can add to that list WU Client cabs from Additional folder and also IE9 and IE9 Updates from Extra folder if you want. If you want IE10/IE11 you need to add IE10/IE11 Prerequisites to the list also. That's all I recommend for start. That will give you a good base to continue with the project. Before continue is recommended to test this in VM and if all is good make a copy of it to not repeat this step if something goes wrong as it's quite lengthy. From now on you work on a copy that have all the updates needed, basically almost an SP2. There are a bunch of Add-ons and switchless installer that you can use to integrate as much as you want/need of the rest of the updates like NET Framework, VC Runtimes, Silverlight etc and other programs you need as Java, Flash etc. The drivers should all go in a folder called "Drivers" in the root of the install media (USB, DVD). You just simply copy the "Drivers" folder after all the integration was done to the root of the media befor create the ISO. If you want/need to integrate into Boot.wim you keep as little as possible from Chipset and MassStorage and eventualy USB3.0 if you have/need it. Note that all drivers should be extracted in INF format not .EXE, 7z or any form of packaging. Now it's a good time to test this again in VM. Hope that helps for a quick start.
  5. @ Simon Hind That's Microsoft way of do things and they sure have the reason. Think to corporations or governments that are in countries with more than one official language, they need this proof thing in all those languages. An example could be Canada where you run the program in English but you need proofing for French too. If you don't need them it's fine but... Do this experiment: Take the clean Office install and extract from SP1 only the "en-us" and "x-none" files to Updates folder. After install it, visit WU for updates. There you go, more updates needed than the one currently KB2760587 offered after correct SP1 integration.
  6. why keep the spanish and french files for proof ? i do not see this a a requirement to install update for proof tool Each language version of Office 2013 includes proofing tools for a set of companion languages. For example, when you deploy the English version of an Office 2013 product, users receive proofing tools for both Spanish and French in addition to English. http://technet.microsoft.com/en-us/library/ee942198(v=office.15).aspx
  7. You don't want/need LAN integrated. There's no use for them at the install process. You connect to network only after the install process is done. So why bother?
  8. Driver integration is tricky. You want to keep as little as possible the number of drivers integrated to avoid such problems. Only integrate drivers that are in Win7 folder as they are tested to be compatible with Win7. Don't use the drivers from other folders of DP's You only need massstorage, chipset (and probably USB3, if you have this in your computer) drivers integrated. All the remaining drivers should go in a folder "Drivers" in the root of the install. In this way just the needed drivers for that particular computer will be installed from the "Drivers" folder and not bloat the driverstore with all the DP drivers.
  9. You already have a thread opened for this problem. Please don't open another. Just bump the old one if you didn't get the answer.
  10. Downloading Windows 7 x64 list Title: Index was out of range. Must be non-negative and less than the size of the collection.Parameter name: indexErrType: ErrorDescription: An unknown error has occurred and has been written to 'Logs\Errors.txt'Exception: Exception: ***********************************Form: frmUpdCatalog (False)Status: [77%] Downloading (298/428): Windows6.1-KB2837108-v4-x64 :: 5.12 MBAnti-Virus: FalseVersion: Exception: Index was out of range. Must be non-negative and less than the size of the collection.Parameter name: indexStackTrace: at System.Collections.ArrayList.get_Item(Int32 index) at System.Windows.Forms.ToolStripItemCollection.get_Item(Int32 index) at System.Windows.Forms.ToolStrip.OnPaint(PaintEventArgs e) at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer) at System.Windows.Forms.Control.OnPrint(PaintEventArgs e) at System.Windows.Forms.Control.WmPrintClient(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) InnerException: Source: mscorlibTargetSite: System.Object get_Item(Int32)Data: System.Collections.ListDictionaryInternalForm History: frmStartup, frmToolsManager, frmAntiVirus, frmUpdCatalog, frmToolsManager, frmUpdCatalog, Open Forms: frmStartup, frmUpdCatalog,
  11. Thanks Rick. That's for installed system. My request was for the new Alfawave's Downloader from Win Toolkit.
  12. This time seems to work as it should. Great work, Thank You!
  13. Please add an option to hide/unhide updates from the list similar to Windows Updates (right click - Hide Update) As of the Additional and Extra most of the users don't have a clue about them and probably don't want to download, make the option to hide them just to make the screen clear. I'm thinking this as a dependent group hide feature so when you hide an update this will hide all updates in that folder including the folder. All the hidden updates should be visible/available in a separate tab of Hidden Updates from where you can restore/unhide the updates if should need. The tab will be visible only if hidden updates exists or permanent visible similar to others (with count number). In my case I only need IE and WUClient so I'll hide the rest as I don't want to download them (saves time and space) and do not want to see them in that list Later if a new update is available that reside in one of the hidden folders, automatically move it to Hidden Updates. Obviously Superseded should work on this Hidden Updates too.
  14. After multiple tests with previous builds that I kept (137 files by now) I finally narrowed down the last build that integrates the English pack OK in this scenario. The last build that works from my collection is:, than my collection jumps to I don't have any builds between those mentioned so I can't help you more but the bug seems to begin sometime than. Hope this follow-up helps nailing this bug. The current test build behaves as in the post above.
  15. Everything that's in the repo will be downloadable through update catalog, don't worry.
  16. As I remember it the update catalog worked better than current WHD implementation. For ex: 1. The new updates were auto-selected and presented on top of the list 2. All supersedded updates that are not in the curent list were moved to "Old" folder That's what I still remember and wish they remain the same.
  17. I don't think a full integrate will be the best choice and frankly who would ever want that? I was thinking that WTK will have acces to the updates repo of WHD and after some time of lacking it it finally have an built in updates downloader. That's all it needs in my opinion from WHD. Who wants the other features of WHD, just use it as separate program.
  18. Please do not open multiple threads on same problem. Answered here
  19. Blue color means that are duplicate drivers. Compare the highlited files and eliminate the duplicate drivers from list.
  20. You mean driverpacks.net? Yes, just extract the content of the packs to "Drivers" folder and keep the folder structure. All drivers should be .inf format NOT .exe or any other package.
  21. Tested with, now the Integrate tab don't show any language added. Tested the result in VM If select English to install in the process of install it errors Other languages seems OK integrated (only tested romanian and hungarian) In the end when other language is used as the install the English is missing from control panel. So the English is only integrated in the first part. Hope all this info helps fixing this.
  22. This is to minimize the install time and avoid problems. All drivers integrated will be loaded into RAM during install so you better keep as little as possible. Loading all the drivers take more time. If I remember correctly if you put a folder named "Drivers" on the root of the install disc or any accessible drive root, after install it will be picked up by RunOnce Installer to install the drivers needed.
  • Create New...