Hi,
I’m trying to automate LightBurn installation using the command
LightBurn-v1.7.06.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-
and it works fine but is there a way to activate the driver options as well?
I would like the FTDI and EZCAD2 drivers to install silently too.
Best Regards Peter
…use the
/VERYSILENTcommand-line switch with the installer executable, which will prevent the installation progress window, installation wizard, and background window from displaying.
This is something a network administrator would use setting up a bunch of machines. How many machines are you installing on? Do not know about the EZCAD2 driver, but the FTDI should be a similar command. Google installing Windows deivers for the proper syntax.
EDIT: I just noticed Ubuntu in your bio. I (don’t want to) know nothing about UNIX/Linux installations. Sorry!
If you’re running Ubuntu, you can’t run a windows application or software unless you have some kind of windows simulator running under Ubuntu.
None of the Chinese software application will run natively on Ubuntu.
Thank you, I am using a Windows machine for Lightburn and it is installing silently but doesn’t include the drivers, so I need to install them separately.
It sort of works, but the EzCad driver isn’t picked up at the first install using
"c:\Program Files\LightBurn\EzCad2Driver\dpinst-x64.exe" /Q /SE /SW
and Lightburn won’t connect. If I run the command a second time manually then it works. Any ideas?
Logging with /C might help. dpinst based driver installs put the driver into Windows’ driver store, and will autodetect on first plug and play. Maybe adding /A will help? Depending on your method of autoinstall, you may need to deal with the UAC side of things twice; once for the initial LB install, and a second for the dpinst.
Regarding the FTDI driver, the installer puts SerialDriver.exe in the install dir, and will shellexec it as the original user if you select install ftdi drivers. It then deletes the file when you close the installer. SerialDriver.exe is a “Free Extractor” wrapper, which is tool from ~2010 that takes a zip file and creates a self extracting exe, which in this case is used to extract another, older version of dpinst (signed in 2010 by Microsoft) to finally install the FTDI drivers!
I don’t quite understand the logic behind running 2 entrirely different processes to invoke dpinst to install an inf, but I’m guessing it’s something to do with licensing.
I remember now why I retired! Thanks @fins for being current on this Windows stuff.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.