The ini file is causing Lightburn to end abruptly. I have the software installed on 2 computers and if I copy the ini from computer 2 to one it works for a while but the next day Lightburn ends on computer 1. If I copy the ini file and store it on computer 1 ini another folder and use that the next day as the ini file for computer 1 I get the same result: termination. I must copy the ini file from computer 2 to get the software to operate on com1. There are no issues on comp 2. Sculpfun S10 is the only laser printer on both computers.
Why should you ever copy any ini-file between computers? I doubt that makes sense. Set up both machines individually and then transfer the project files between them.
The ini-file contains computer-specific information like absolute file paths. If you didn’t set up both computers exactly the same (same windows version, same user name, same paths) it is likely to crash at some point.
One comp 1 Lightburn closed after about 5 seconds. It left RAM without any error codes. I was told by support to delete ini and recreate it. This I did and all was well. Rather than set up an Lightburn I copied the ini file. It ran for 10 times, opening and closing on comp 1. Next day the close returned. The laser is not connected to either computer. If copying was an issue then comp 1 would not load.
The ini file only works on the computer it was created. Not on the other. I didn’t get your exact procedure. Better do a fresh installation of LightBurn on either computer, then you should have two running instances.
I had LB running on two computers on comp 1 there was an early termination. Exiting from ram. Uninstalled, rebooted, and installed. Same result. Uninstalled, rebooted, and installed later version. Same result. Repeated, same result. Second computer not involved at this point.
I sent info and details to LB support. They suggested deleting .ini file. The ini file that had only been created on comp 1 was deleted LB ran for more than 10 seconds. I intend to create the files on comp 1 and burn them from comp 2.
Rather than move the laser iI copied the ini file and LB worked for 4 hours with many exits and restarts. All normal with the .ini file from comp 2. LB on comp 1 operated perfectly with multiple restarts with the ini file from comp 2.
2 days later the problem has returned,
I copied the ini from comp 2 and all good for 30 minutes.
Next day same result.
I copied the ini from comp 2 to 2 places, including a temp location. LB runs with the ini file. All good.
3 days later the problem has returned. I deleted the ini and copied the same ini file that had worked 3 days earlier from the temp location on comp 1 to the LB folder. LB exited again. Started LB on comp 2 Copied the new ini file to comp 1 and all good.
This happened twice more.
If the was an issue using the comp 2 ini file, why would LB operate for 4 hours, off and on? Why does the same ini file that worked 2 days earlier not work later?
And how can I get LB to work on comp 1 without crashing after a few seconds.
I think that the ini file worked was just a coincidence. Maybe exactly because there are paths inside the file that lead to a non-existing location which create the error on PC1. Maybe there is some network storage involved on PC1? This could also cause an error.
What’s the difference between both PCs? Same Windows version? Similar tools installed? I suggest updating everything that is available on PC1 to the latest versions and test again.
Thanks for your advice.
The fact the LB works on comp 1 with the ini file one day but not the next is the key question. The original ini file that was only ever on comp 1 cause LB to terminate. The same happens with the imported ini. It seems the is an issue with comp 1 that is unrelated to the source of comp 1. If there was an issue with the ini file comp 1 would never have run for 4 hours, with restarts. On each start I assume it is read completely. Why one day the file works and not the second as was the case with only comp 1 ini file?
1 Like
The ini file might be read completely at a start, but not all options are used. The ini files store the location of the libraries, and some other paths. One thing I can imagine, is that LightBurn crashes when attempting to open a nonexistent path. But LightBurn only tries this at the moment where you want it to access the file. The rest of the time, it works. Just one scneario. There can be many more.
That’s usually hard to debug when using Windows. Can also be a damaged or outdated library file somewhere in the OS. So if you can’t replicate this issue, it will be very hard to find. A clean installation of the machine will be much faster.
The software was uninstalled 3 times and each time the same issue.
Not the software. Windows and drivers. Start with a fresh system. Or maybe the PC doesn’t have the specifications to run LB?
32GB RAM, 2GB SSD. Win 11, latest version AMD Ryzen 9.
The laptop is win 10.
To reinstall a computer system for one program is not logical. It does run for 4 hours. If it a driver issue then it would fail within that time.
I agree. I don’t believe it’s a driver.
I did recently read that a user wasn’t logged into Microsoft OneDrive and because the required file was in a shared directory that wasn’t accessible, the program crashed.
LightBurn recommends local storage for files. Please make a copy of the files that you intend to share between computers and place the copy into an exclusive shared directory that LightBurn doesn’t use.
You may have to unshare some documents folders or some system level folders to defeat the error if this is what is happening.
You can test whether or not cloud storage is related and a contributing factor by disconnecting the the ethernet cable or switching off the wifi to see if the crash can be created on demand.
Files are stored outside OneDrive. Crash happens before I can load a file. Open LB, 5 seconds, crash.
Another user may have had a similar problem. The cure was to delete the last lbprefs file and rebuild the ini file.
I have uninstalled LighBurn from comp 1. I have deleted the files in the appData\Local directory. I rebooted.
I installed LB again. Connected the laser printer.
2 days later LB terminates after 5 seconds. No errrors recorded.
You might be able to track down the problem using Windows Event Viewer (built into Windows) or the Sysinternals Procmon application that you can download here
Hope this helps…
I ran the monitor and Lighburn does not show.
I deteled all ini files and created manually. It runs until the backup is created then crash.
Repeated and created a laser manually with connecting and LB only ran until the old ini file was created then crash.
No record in event viewer.
This is really frustrating. Is there an alternative that will run on my computer?
Ok, it was just a thought. I’m not that surprised it didn’t show anything in Event Viewer as it doesn’t show everything. I’m surprised nothing showed in Procmon though as that shows everything, usually too much, making it difficult to find the “needle in the haystack”. Hopefully the LB guys can help track it down. If I think of anything else I’ll let you know, it must be very frustrating.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.