Version of FOG, boot file being used, OS being captured, model of problematic host, Kernel version being used with fog, HDD type, and any other details would greatly help us help you.
@Wayne-Workman As the old newsmanβs adage goes: βI donβt make the news. I just report it.β If you accept the the MS EULA when Windows is installed, you are bound by all of the nonsense that follows.
since the /tmp/mydrivers link is created make sure you can list the contents of ls /ntfs/Drivers If both checkout then just issue the copy command manually cp -R /tmp/mydrivers/* /ntfs/Drivers That should copy the files to the windows π drive.
So, make a github account, fork the fog project, download your fork to your local work space, Make your changes. Commit your changes, push your changes. Then do a pull request with the main repo. The devs will look it over and either merge or not, often with comments when they donβt.
Personally, I install smart notebook on every image. Then I leave a copy of the installer on the C:\ drive for actual smartboards. We just run the installer and choose βSmartboard Driversβ so it works with the smartboard.
@Jbob Thank you! Iβve been building some EXEs with SFX maker, and this will simplify things greatly for me. Just gotta upload my office 2016 pro exe I complied and test it.
Also, @Sebastian-Roth when things are hash tagged wiki, after I add them I edit the hash tag and remove the hash symbol. Just an FYI so you can do the same if you wanted.
Anything beyond 800x600 is not guaranteed to (and often doesnβt) work on a lot of monitors. We also found 800x600 scales best to different aspect ratios.