Jump to content

Coustal

Member
  • Posts

    13
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    France

About Coustal

Coustal's Achievements

0

Reputation

  1. You have to recreate your intall disk not removing the drivers and reinstall everything.
  2. You have removed the standard camera drivers provided by Windows. 'Cameras and Camcorders' is listed under Components/Drivers. Just don't remove it and it will work. Canon cameras not using WIA or Twain (like the G9) need these standard drivers.
  3. If your Canon camera is not designed to use a WIA or TWAIN driver, so if your Canon setup CD does not provide such a driver, then you must not remove the camera drivers from your nLited setup. Windows will be able to detect your camera without external driver. Which does not mean that you won't be able to use CameraWindow and ZoomBrowser, they will work perfectly.
  4. I had the same issue as you, travelling to Kabul during the install. There are several updates (and maybe security updates, would need to check) that deal with time zones. Integrating all of them with nLite lead to the issue. To fix it I just kept the most recent update to integrate with nLite.
  5. Are you using nLite 1.3.0.4? If yes you need to move to 1.3.5 to have this bug fixed. If you can't move because you are using windows 2000 then you need to remove manually all the multiple entries for hotfixes in svcpack.inf before creating the iso.
  6. You can just rename it to svcpack.in_ by hand. You don't need to recompress it with any software.
  7. Interresting update. I tested a more complete ISO which also failed (I stopped it after at least 4 hours blocked at T-13). This one integrates all the same hotfixes, a dozen of addons like .net 1.1 and 2 or directX, and I removed all I don't need. All this was done with 1.3.0.4. Looking at the svcpack.inf I found an incredible amount of duplicates. One hotfixe was listed 2045 times, another 1024 times, others 512, 256, 128, 64, 32, 16, 8, 4 and 2 times each. The total of ducplicates is huge!! I removed all the duplicates and recreated the ISO. Well it installed like a charme under Virtual PC 2007. It stayed around 10 minutes at T-13 and moved on normally. All my addons seem to be present, so everything is fine. So Nuhi, can you please look why this version creates so many duplicates? For me it is confirmed to be a real and big issue.
  8. I also looked into my svcpack.inf where I only added the SP2, the post SP2 hotfixes and IE7 and its 3 hotfixes. This image hangs at T-13, it was created with version 1.3.0.4. I also have many times the same hotfixes, actually tens of times for many hotfixes. Compared to a previous ISO I made in january with 1.3RC I also have several times some hotfixes, but far less times than with 1.3.0.4. This january ISO takes a bit of time at T-13 but still it goes on. So it's a kind of confirmation that there may be a (big) issue of installing several times the same things. And it may not be new, it just never blocked before. This leads another question. It seems that most of the hotfixes get installed at T-13, where I thought they were slipstreamed to the source files, meaning for me no need for a further install. Can someone explain me what I misunderstood? SVCPACK.INF SVCPACK_january.INF
  9. Do you consider hotfixes as addons? If yes ok there are near of 200. If no it takes 2 hours under Virtual PC 2007 only with the hotfixes. Then I added around 10 addons and I stopped the VM after 1 day doing nothing. I never tried addons before 1.3 final, but with hotfixes there is a big regression because it never took 2 hours at this step before. I hardly image it is a windows bug because when I only add the hotfixes up to january (like I did with 1.3RC2) under 1.3.0.4 it still takes 2 hour to go over this step.
  10. I have the same problem using either 1.3RC2 or 1.3.0.4 final. Just adding all the post SP2 hotfixes up to february 2007 for IE6, Outlook Express, WMP9 and XP itself works. But it works far slower than before. It takes at least 2 hours to complete to 'registering components' step, where it used to takes a few minutes with 1.3RC2 and hotfixes up to january 2007. Now adding some addons (like IE7 or wmp11) on top of that completely hangs the install. I did not want to leave it more than 1 day to see if it would complete the install. I had noticed one time that removing the CD made the install continue. But I don't know how to confirm that every thing is installed correctly, so I don't trust it. I was wondering if nLiting from an already nLited windows setup could lead to such problems, so if nLite must be run from an original and complete windows setup. If someone can state on this. I'm also concerned about the fact that nLite 1.3.0.4 does not retreive the previous changes correctly. When I reload the previous changes I selected I always get the same keyboards not removed as I asked, some unattended settings and some tweaks not applied. This does not make me confident in the changes applied to the setup files.
  11. I have the same behaviour. It takes so much time before moving to the devices detection part of the setup! I had not yet isolated that IE7 was the one, I thought it could come from all the hotfixes also integrated.
  12. Thank you both. That's was I was searching for.
  13. Hi, I have integrated with nLite 1.2.1 I guess all the available hotfixes on top of SP2 for IE6, Outlook Express, WM9 and Windows itself (around 150 hotfixes). When I check in Add or Remove Programs after installation I only see 4 hotfixes (KB898458, KB886540, KB928388, KB918093). I don't understand why these ones would be special to see them here and not the others. Is there a way to check that all are really installed?
×
×
  • Create New...