Categories

• Announcements
  

  Get the latest news on what's happening.

  151
  Topics
  512
  Posts

  

  excellent, as always!

• General Topics
  

  View tutorials or talk about FOG in general.

  General Tutorials

  1554
  Topics
  12577
  Posts

  

  @msi Sorry maybe I wasn’t clear. Your batch file route can be saved as a .bat (but is probably better saved as a .cmd). You can deploy that as a snapin just as I had outlined.

  The second part of my comment was to the reason why you are doing this. If you have to fix 100 computers that have already been deployed then the snap in route is the correct one. If you are doing this because you will deploy 100 computers in the future, then there may be another path you can take. One example is if you sysprep your reference image, then you can place batch commands in the c:\windows\setup\scripts directory. After windows setup is done, and before the login screen is presented to the user, windows setup looks in that path for a batch file called setupcomplete.cmd. If it finds that file it will run it before the user can login. There is also a way to have the windows unattend.xml file run commands or add users during its execution. Which can do the same things you are doing in your batch file.

  These are all different ways to get the same results. The simplest is to create a batch file snapin like you talked about.

• Technical Help
  

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems

  7074
  Topics
  70361
  Posts

  S

  @x23piracy Try adding nomodeset kernel parameter as a start. Does this help by any chance?

• Developers
  

  Report bugs, request features, or get the latest progress.

  General Feature Request Bug Reports

  1796
  Topics
  17178
  Posts

  S

  @Psycholiquid Thanks heaps! I can’t stop scratching my head. Let me try to sort this. For you to understand, I just picked a couple of git commits from the iPXE repo where changes were made to the efi timer code:

  757ab9 - Wed, 4 May 2016 - Hang on init.xz
  c917687 - Mon, 20 Jun 2016 - Hang on init.xz
  694c18 - Mon, 20 Jun 2016 - Hang on init.xz
  e09331a - Wed, 7 Dec 2016 - Hang on init.xz
  5cf5ffe - Wed, 7 Dec 2016 - No hang on init.xz
  d37e025 - Wed, 25 Jan 2017 - No hang on init.xz
  302f1ee - Thu, 26 Jan 2017 - wont boot at all on my surface
  d46c53c (HEAD revision couple of days ago) - Wed, 13 Sep 2017 - Hang on init.xz

  So to me it looks as if we have a regression here. Worked nicely with some changes made Dezember 16/January 17 but we are back to hang again on the latest versions.

  More to the point - commit 5cf5ffe seems to have fixed the issue. Reading this commit message I can kind of imagine why this stuff is causing problems…

  EFI provides no clean way for device drivers to shut down in
  preparation for handover to a booted operating system. The platform
  firmware simply doesn’t bother to call the drivers’ Stop() methods.
  Instead, drivers must register an EVT_SIGNAL_EXIT_BOOT_SERVICES event
  to be signalled when ExitBootServices() is called, and clean up
  without any reference to the EFI driver model.

  So what to do next?