Quote:
|
Originally Posted by MTUSUPPORT
You guys are correct as to why this has been done. We have had some companies rip our database off in the past. This is why this new version is protected. We placed alot of money and effort into cleaning up this database, and this is why it is now protected.
|
I guess that is ok, but for what hoster costs versus just "ripping off" kjpro special liscencing and all of that other proprietary jazz, I think a legitimate hoster user should be allowed a special copy to fix bucket so importing their own library with their own format method so when importing typing and cut and pasting one at a time can be illiminated. I can see safeguarding something that is 99% accurate compared to anything else, sorry to slam you, but I had to do a lot of editing when I imported my discs and I was going to try to send in corrections when I ran in to them, but holy moses it took me nearly six months just to import I did not want to spend a year to import and report, I know I am being rough I am sorry, but I don't think the bucket needs or deserves the protection it is getting, sorry.
Seve