|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Or I'm not running a business...but that's the point IBM seems to be missing, too. -----Original Message----- From: Al Barsa [mailto:barsa@barsaconsulting.com] Sent: Saturday, August 24, 2002 9:55 AM To: midrange-l@midrange.com Subject: Re: v5r1 license key Clearly, the IBM licensing system assumes that you are unwilling to scratch your system every 70 days. This is a hole. If you have enough free time and risk tolerance to scratch your system every 70 days, you either have much to much free time on your hands; or are in the wrong business. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com "Metz, Zak" <Zak_Metz@G1.com> To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> Sent by: cc: midrange-l-admin@m Subject: v5r1 license key idrange.com 08/23/2002 12:29 PM Please respond to midrange-l This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Let's say that "someone" is running v5r1 and doesn't have a license key. Without getting into the moral dilemma of the whole thing, let's say that person was willing to scratch their system every, oh, let's say 70 days or so. Would that give this horribly amoral person another 70 days or so per scratch to run without the key? Would it make a difference if the scratch was done from a Save opt 21 vs. IBM media? NOTICE: This E-mail may contain confidential information. If you are not the addressee or the intended recipient please do not read this E-mail and please immediately delete this e-mail message and any attachments from your workstation or network mail system. If you are the addressee or the intended recipient and you save or print a copy of this E-mail, please place it in an appropriate file, depending on whether confidential information is contained in the message. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. NOTICE: This E-mail may contain confidential information. If you are not the addressee or the intended recipient please do not read this E-mail and please immediately delete this e-mail message and any attachments from your workstation or network mail system. If you are the addressee or the intended recipient and you save or print a copy of this E-mail, please place it in an appropriate file, depending on whether confidential information is contained in the message.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.