Yes, but you can add a sentence like:
I can not guarantee that the Software will meet your needs or that operate without interruption or without error. Using the software, you assume full responsibility
in your license.
by doing so it significantly increases the difficulty of recovery, no?
1 - disable System Restore
2 - defragment the hard drive
3 - Overwrite data
4 - to defragment the hard drive
5 - Enable System Restore
PureShredLib (flawed)
Well in that case I have edited my first post and added a disclaimer, so who uses it knows that the code may or may not work.Be very careful posting or using something like this. If your app offers such
a function to a user, and that user's data later DOES get recovered anyway,
then you are open to a big lawsuit because your app failed to do its job.
[Edit]
By "added a disclaimer" i mean i added an extra one... It already had one in the header of the code.
Last edited by Inf0Byt3 on Mon Oct 20, 2008 9:26 pm, edited 2 times in total.
A disclaimer is always good for this sort of thing. Reason: people are going
to rely on it to protect their sensitive data, be it tax files, bank details, or
even porn from their partners. So whenever an app is going to be used
that way, it's better to have legal protection in case it fails. You don't
want to be sued by those sorts of people, because they will try.
to rely on it to protect their sensitive data, be it tax files, bank details, or
even porn from their partners. So whenever an app is going to be used
that way, it's better to have legal protection in case it fails. You don't
want to be sued by those sorts of people, because they will try.
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
"PureBasic won't be object oriented, period" - Fred.
How about a disclaimer like:
(I asked my sister about a disclaimer for code of this nature in a forum like this, she said the below should cover you in all cases.)
"By using this code you agree that; The author makes no claim as to suitability, reliability, or use for any purpose and is presenting this code only as experimental or research information and not as working, reliable, functioning, or production code. No gurantee or warranty is either expressed or implied. The user is warned against reliance upon this code as useful for any purpose or upon it functioning as intended or needed. Your use of this code is at your own risk and by your own free will. The author will not be held liable in anyway for any malfunction, damage, mishap, loss, or other actions either adverse or detrimental, or for any monetary, physical, or other damages or loss caused by using the code."
and...you could also add a line like: "But if it works out for you send payment to ...."
<<< this is a joke, not part of the above.
Nice, good job. Thank You
(I asked my sister about a disclaimer for code of this nature in a forum like this, she said the below should cover you in all cases.)
"By using this code you agree that; The author makes no claim as to suitability, reliability, or use for any purpose and is presenting this code only as experimental or research information and not as working, reliable, functioning, or production code. No gurantee or warranty is either expressed or implied. The user is warned against reliance upon this code as useful for any purpose or upon it functioning as intended or needed. Your use of this code is at your own risk and by your own free will. The author will not be held liable in anyway for any malfunction, damage, mishap, loss, or other actions either adverse or detrimental, or for any monetary, physical, or other damages or loss caused by using the code."
and...you could also add a line like: "But if it works out for you send payment to ...."
<<< this is a joke, not part of the above.Nice, good job. Thank You
That indeed looks good.
Still, thinking about how much software on the internet is full of bugs, hell even Windows (TM) screwed things up sometimes and the company behind it is huge, why would anyone bother to attack someone for such a small and useless piece of code? I at least know many programs who didn't do their job correctly and many of them were being sold really expensive.
Still, thinking about how much software on the internet is full of bugs, hell even Windows (TM) screwed things up sometimes and the company behind it is huge, why would anyone bother to attack someone for such a small and useless piece of code? I at least know many programs who didn't do their job correctly and many of them were being sold really expensive.
If you're offering an app and don't already have such a disclaimer, you have bigger problems than worrying about someone else's code.PB wrote:Be very careful posting or using something like this. If your app offers such
a function to a user, and that user's data later DOES get recovered anyway,
then you are open to a big lawsuit because your app failed to do its job.
If everyone who posts a 'tip' in these forums has to also post a disclaimer, we're all in trouble.
If he were 'selling' the tip as a product, he may have to worry.