Skip navigation
All Places > Licensing and Installation > Blog > Author: mitchdale

I recently received a license file for Questa Core, the installation of which had me wrapped around the axel for a few minutes.  Spoiler alert: it was the line endings.


I'm consulting at a painfully small startup, which explains why every computer here is a Windows machine. Having a long and storied history in ASIC design, when confronted with the Windows OS, I will do my design and development work using Cygwin ( For those of you not familiar with Cygwin, it is "a large collection of GNU and Open Source tools which provide functionality similar to a Linux distribution on Windows." I think Cygwin is great, but you can expect to encounter Windows (DOS, really)/Unix line-ending interoperability problems.


Why am I telling you this. Because my experience with Cygwin has implanted some sort of watch-dog process in my brain. When confronted with very weird results for what should be a minor and straightforward effort, the watch-dog gets triggered, and it sends this message to my brain: "Maybe it's a line-ending issue."


And it was. Our license server (FlexLM) is hosted on a Windows computer. But the license was in Unix format. And try as I might, I couldn't get the license server to start *or* produce a log file.


LSS (long story short), my internal watch-dog got triggered, I ran Cygwin's unix2dos utility on the license file, and Bob's your uncle (that's British for "that fixed everything". No, I don't know why it means that).


So, is the moral of this story "When in doubt, maybe it's the line-endings!"? Not so fast.


A subsequent search of supportnet, Flexera's website, and even Google yielded no mention of this license file issue . Am I one of only a handful of people to encounter this? I would think this issue would be much more common these days. Have any of you, esteemed readers, ever tripped over this issue. Please let me know.


But in the meantime, when in doubt, maybe it's the line-endings.