Which is also known as "sloppy QA". A build takes very little time to do, comparatively speaking
That entirely depends on how deeply interlaced into the project's sources the calls to StarForce's APIs were.
If it calls from every menu call, for instance, plus device set/reset, that could take a bit of time to strip out those API calls.
Further, if it's a very segmented program and they have a number of static libs with StarForce interlaced with them, it could take a great deal of time and effort to not only disable those calls, but to recompile all of the static libs and re-link the whole project.
Even if it was simply an include statement and a couple of imports which were never called, they'd still have to strip those out and recompile any libs linked against that.
Then they have to run a QA process to make sure nothing was broken accidentally during the process of stripping out that interface, which if you know anything about QA is a nightmare - they have to run the full set of tests again on every subsystem that was changed or every connected subsystem.
Basically, yeah, it takes a lot of time.
This comment was edited on Jul 2, 16:20.