|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
About The Hard Disk Serial Numberplease help me,
I am looking for the api call code to get the hard disk serial number which is not the phisical one. i am looking for the serial of the producer which is unique and cannot be changed. regards Option Explicit
Private Declare Function GetVolumeInformation _ Lib "kernel32" _ Alias "GetVolumeInformationA" _ (ByVal lpRootPathName As String, _ ByVal lpVolumeNameBuffer As String, _ ByVal nVolumeNameSize As Long, _ lpVolumeSerialNumber As Long, _ lpMaximumComponentLength As Long, _ lpFileSystemFlags As Long, _ ByVal lpFileSystemNameBuffer As String, _ ByVal nFileSystemNameSize As Long) As Long Private Function getDriveVolumeSerial(Optional strDriveLetter As String = "") As String 'will get the drive serial number 'default is the drive that the application is on 'otherwise can do for example: getDriveSerialNumber("D") '------------------------------------------------------- Dim strDrivePath As String Dim Serial As Long Dim VName As String Dim FSName As String If Len(strDriveLetter) = 0 Then strDrivePath = Left$(App.Path, 1) & ":\" Else strDrivePath = strDriveLetter & ":\" End If 'Create buffers VName = String$(255, Chr$(0)) FSName = String$(255, Chr$(0)) 'Get the volume information GetVolumeInformation strDrivePath, VName, 255, Serial, 0, 0, FSName, 255 getDriveVolumeSerial = Trim(Str$(Abs(Serial))) End Function Sub test() MsgBox getDriveVolumeSerial() End Sub RBS Show quoteHide quote "Hüseyin Turan YANIK" <tya***@und.org.tr> wrote in message news:ubjhpDRQGHA.5400@TK2MSFTNGP09.phx.gbl... > please help me, > > I am looking for the api call code to get the hard disk serial number > which > is not the phisical one. i am looking for the serial of the producer which > is unique and cannot be changed. > > regards > > "Hüseyin Turan YANIK" <tya***@und.org.tr> wrote in message Here's one way...... It returns the hard-drive's "hardware" serial number news:ubjhpDRQGHA.5400@TK2MSFTNGP09.phx.gbl... > please help me, > > I am looking for the api call code to get the hard disk serial number > which > is not the phisical one. i am looking for the serial of the producer which > is unique and cannot be changed. > > regards which normally can't be changed. I suppose a firmware update could change it. Never tested. Retrive Low-Level Hard Drive Information http://www.freevbcode.com/ShowCode.Asp?ID=3380 If this is for software piracy protection, keep your customer support staff handy because people will be calling all day and night asking for new licensing info after they buy a new PC or hard-drive. Personally, I go through about 4 per year so I wouldn't/couldn't afford to install something with licensing based on hardware. -- Ken Halter - MS-MVP-VB - Please keep all discussions in the groups.. DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm > If this is for software piracy protection, keep your customer And another thing which the OP should consider.... there are people like me> support staff handy because people will be calling all day > and night asking for new licensing info after they buy a new > PC or hard-drive. Personally, I go through about 4 per year > so I wouldn't/couldn't afford to install something with licensing > based on hardware. who won't tie themselves to licensing based on hardware except from a large, well-established company. If the OP is a one-man operation (or part of a small, non-established company), my concern would be the "bus accident scenario". What is that? Well, if I buy the OP's product and he gets hit by a bus (or some other event transpires which makes him unable to further support the product), what happens when I buy a new computer or replace the hard drive? The answer is, "I'm screwed!" Hence, I won't buy his product in the first place. Rick Very good point!
I have a one man company and have hardware based licensing. Want to become a partner? RBS Show quoteHide quote "Rick Rothstein [MVP - Visual Basic]" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in message news:%2378F7GUQGHA.3460@TK2MSFTNGP15.phx.gbl... >> If this is for software piracy protection, keep your customer >> support staff handy because people will be calling all day >> and night asking for new licensing info after they buy a new >> PC or hard-drive. Personally, I go through about 4 per year >> so I wouldn't/couldn't afford to install something with licensing >> based on hardware. > > And another thing which the OP should consider.... there are people like > me > who won't tie themselves to licensing based on hardware except from a > large, > well-established company. If the OP is a one-man operation (or part of a > small, non-established company), my concern would be the "bus accident > scenario". What is that? Well, if I buy the OP's product and he gets hit > by > a bus (or some other event transpires which makes him unable to further > support the product), what happens when I buy a new computer or replace > the > hard drive? The answer is, "I'm screwed!" Hence, I won't buy his product > in > the first place. > > Rick > > > > well-established company. If the OP is a one-man operation Well, taking on multiple partners that are not local to you (odds of them> > (or part of a small, non-established company), my concern > > would be the "bus accident scenario". What is that? Well, > > if I buy the OP's product and he gets hit by a bus (or some > > other event transpires which makes him unable to further > > support the product), what happens when I buy a new > > computer or replace the hard drive? The answer is, "I'm screwed!" > > Very good point! > I have a one man company and have hardware based licensing. > Want to become a partner? all getting hit by a bus at the same time would be slim to none) would be one way of handling the problem. As for me becoming a partner... well, I don't think I could afford to buy my way into any company, yours or any other (retired, fixed-income, etc). Rick I always could ask my wife or kids to learn how to deal with the licensing.
Then again we might get hit by the same bus! Wasn't serious about the partnership, but now you replied: It wouldn't be buying into the company, it would be improving the product and in return get part of the profit. So there would be no financial costs. It is only a little side job for me, but it is picking up very nicely. RBS Show quoteHide quote "Rick Rothstein [MVP - Visual Basic]" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in message news:%236rzKZUQGHA.3984@TK2MSFTNGP14.phx.gbl... >> > well-established company. If the OP is a one-man operation >> > (or part of a small, non-established company), my concern >> > would be the "bus accident scenario". What is that? Well, >> > if I buy the OP's product and he gets hit by a bus (or some >> > other event transpires which makes him unable to further >> > support the product), what happens when I buy a new >> > computer or replace the hard drive? The answer is, "I'm screwed!" >> >> Very good point! >> I have a one man company and have hardware based licensing. >> Want to become a partner? > > Well, taking on multiple partners that are not local to you (odds of them > all getting hit by a bus at the same time would be slim to none) would be > one way of handling the problem. As for me becoming a partner... well, I > don't think I could afford to buy my way into any company, yours or any > other (retired, fixed-income, etc). > > Rick > > It is a good idea to have a contingency plan in place. As a fellow one man
show, whose been doing this shareware thang for about ten years now, I developed a long time ago a protocol to put into place, to be excecuted by surviving relatives in the event of my untimely demise. Here is some of what I did FYI...or if you want more specific details, email me. I'd be happy to discuss them with you: 1) I have a pre-written index page for my website to be uploaded stating that something had happened to me and I would no longer be able to support my products. 2) I would no longer be accepting new registrations but would have the files available for those who needed replacements. 3) I have in place a program designed to reproduce "lost registration numbers" for existing customers that could be easily operated by surviving relatives. 4) I have paperwork in place to give my parents or surviving them my sibling and when of age my son power of attorney over my buisness accounts and compenstion for all the trouble they will experience in cleaning up after my passing. My lawyer also drafted up my will to specific as such (it's never too early...really). 5) I have ready to go a Paypal account for those customers who wish to donate to the post-running of my biz to whomever takes it over to maintain existing customers...but no new ones. I would only consider continuing the business if I had an agreement with another developer who would take over the projects and compensate my surviving relatives (actually, they would be his boss, but that is something I've not considered at this point, finding a replacement for me). That is about the gist of it. I do sleep a little better at night knowing I've left adiquate instructions and protocols in place as I would not want to dump on my family the respnsibility or the fallout of my biz just hanging out there with no idea or direction about what to do. Hope this helps. - Kev Show quoteHide quote "RB Smissaert" <bartsmissa***@blueyonder.co.uk> wrote in message news:OfQSEiUQGHA.140@TK2MSFTNGP12.phx.gbl... >I always could ask my wife or kids to learn how to deal with the licensing. > Then again we might get hit by the same bus! > Wasn't serious about the partnership, but now you replied: > It wouldn't be buying into the company, it would be improving the product > and in return get part of the profit. So there would be no financial > costs. > It is only a little side job for me, but it is picking up very nicely. > > RBS > > > "Rick Rothstein [MVP - Visual Basic]" <rickNOSPAMnews@NOSPAMcomcast.net> > wrote in message news:%236rzKZUQGHA.3984@TK2MSFTNGP14.phx.gbl... >>> > well-established company. If the OP is a one-man operation >>> > (or part of a small, non-established company), my concern >>> > would be the "bus accident scenario". What is that? Well, >>> > if I buy the OP's product and he gets hit by a bus (or some >>> > other event transpires which makes him unable to further >>> > support the product), what happens when I buy a new >>> > computer or replace the hard drive? The answer is, "I'm screwed!" >>> >>> Very good point! >>> I have a one man company and have hardware based licensing. >>> Want to become a partner? >> >> Well, taking on multiple partners that are not local to you (odds of them >> all getting hit by a bus at the same time would be slim to none) would be >> one way of handling the problem. As for me becoming a partner... well, I >> don't think I could afford to buy my way into any company, yours or any >> other (retired, fixed-income, etc). >> >> Rick >> >> > Another thing small or one-man operators should consider is placing their
source code in escrow so if they are squished by a bus, the code is available should fixes be needed. Dave O. Show quoteHide quote "Kevin Provance" <ca***@tpasoft.com> wrote in message news:eZsK6KYQGHA.2496@TK2MSFTNGP11.phx.gbl... > It is a good idea to have a contingency plan in place. As a fellow one > man show, whose been doing this shareware thang for about ten years now, I > developed a long time ago a protocol to put into place, to be excecuted by > surviving relatives in the event of my untimely demise. Here is some of > what I did FYI...or if you want more specific details, email me. I'd be > happy to discuss them with you: > > 1) I have a pre-written index page for my website to be uploaded stating > that something had happened to me and I would no longer be able to support > my products. > > 2) I would no longer be accepting new registrations but would have the > files available for those who needed replacements. > > 3) I have in place a program designed to reproduce "lost registration > numbers" for existing customers that could be easily operated by surviving > relatives. > > 4) I have paperwork in place to give my parents or surviving them my > sibling and when of age my son power of attorney over my buisness accounts > and compenstion for all the trouble they will experience in cleaning up > after my passing. My lawyer also drafted up my will to specific as such > (it's never too early...really). > > 5) I have ready to go a Paypal account for those customers who wish to > donate to the post-running of my biz to whomever takes it over to maintain > existing customers...but no new ones. I would only consider continuing > the business if I had an agreement with another developer who would take > over the projects and compensate my surviving relatives (actually, they > would be his boss, but that is something I've not considered at this > point, finding a replacement for me). > > That is about the gist of it. I do sleep a little better at night knowing > I've left adiquate instructions and protocols in place as I would not want > to dump on my family the respnsibility or the fallout of my biz just > hanging out there with no idea or direction about what to do. > > Hope this helps. > > - Kev > > "RB Smissaert" <bartsmissa***@blueyonder.co.uk> wrote in message > news:OfQSEiUQGHA.140@TK2MSFTNGP12.phx.gbl... >>I always could ask my wife or kids to learn how to deal with the >>licensing. >> Then again we might get hit by the same bus! >> Wasn't serious about the partnership, but now you replied: >> It wouldn't be buying into the company, it would be improving the product >> and in return get part of the profit. So there would be no financial >> costs. >> It is only a little side job for me, but it is picking up very nicely. >> >> RBS >> >> >> "Rick Rothstein [MVP - Visual Basic]" <rickNOSPAMnews@NOSPAMcomcast.net> >> wrote in message news:%236rzKZUQGHA.3984@TK2MSFTNGP14.phx.gbl... >>>> > well-established company. If the OP is a one-man operation >>>> > (or part of a small, non-established company), my concern >>>> > would be the "bus accident scenario". What is that? Well, >>>> > if I buy the OP's product and he gets hit by a bus (or some >>>> > other event transpires which makes him unable to further >>>> > support the product), what happens when I buy a new >>>> > computer or replace the hard drive? The answer is, "I'm screwed!" >>>> >>>> Very good point! >>>> I have a one man company and have hardware based licensing. >>>> Want to become a partner? >>> >>> Well, taking on multiple partners that are not local to you (odds of >>> them >>> all getting hit by a bus at the same time would be slim to none) would >>> be >>> one way of handling the problem. As for me becoming a partner... well, I >>> don't think I could afford to buy my way into any company, yours or any >>> other (retired, fixed-income, etc). >>> >>> Rick >>> >>> >> > > I've never really understood that concept. Can someone explain it to me in
layman's terms? Thanks! - Kev Show quoteHide quote "Dave" <nob***@nowhere.com> wrote in message news:O0GF4CdQGHA.5248@TK2MSFTNGP09.phx.gbl... > Another thing small or one-man operators should consider is placing their > source code in escrow so if they are squished by a bus, the code is > available should fixes be needed. > > Dave O. > > "Kevin Provance" <ca***@tpasoft.com> wrote in message > news:eZsK6KYQGHA.2496@TK2MSFTNGP11.phx.gbl... >> It is a good idea to have a contingency plan in place. As a fellow one >> man show, whose been doing this shareware thang for about ten years now, >> I developed a long time ago a protocol to put into place, to be excecuted >> by surviving relatives in the event of my untimely demise. Here is some >> of what I did FYI...or if you want more specific details, email me. I'd >> be happy to discuss them with you: >> >> 1) I have a pre-written index page for my website to be uploaded stating >> that something had happened to me and I would no longer be able to >> support my products. >> >> 2) I would no longer be accepting new registrations but would have the >> files available for those who needed replacements. >> >> 3) I have in place a program designed to reproduce "lost registration >> numbers" for existing customers that could be easily operated by >> surviving relatives. >> >> 4) I have paperwork in place to give my parents or surviving them my >> sibling and when of age my son power of attorney over my buisness >> accounts and compenstion for all the trouble they will experience in >> cleaning up after my passing. My lawyer also drafted up my will to >> specific as such (it's never too early...really). >> >> 5) I have ready to go a Paypal account for those customers who wish to >> donate to the post-running of my biz to whomever takes it over to >> maintain existing customers...but no new ones. I would only consider >> continuing the business if I had an agreement with another developer who >> would take over the projects and compensate my surviving relatives >> (actually, they would be his boss, but that is something I've not >> considered at this point, finding a replacement for me). >> >> That is about the gist of it. I do sleep a little better at night >> knowing I've left adiquate instructions and protocols in place as I would >> not want to dump on my family the respnsibility or the fallout of my biz >> just hanging out there with no idea or direction about what to do. >> >> Hope this helps. >> >> - Kev >> >> "RB Smissaert" <bartsmissa***@blueyonder.co.uk> wrote in message >> news:OfQSEiUQGHA.140@TK2MSFTNGP12.phx.gbl... >>>I always could ask my wife or kids to learn how to deal with the >>>licensing. >>> Then again we might get hit by the same bus! >>> Wasn't serious about the partnership, but now you replied: >>> It wouldn't be buying into the company, it would be improving the >>> product >>> and in return get part of the profit. So there would be no financial >>> costs. >>> It is only a little side job for me, but it is picking up very nicely. >>> >>> RBS >>> >>> >>> "Rick Rothstein [MVP - Visual Basic]" <rickNOSPAMnews@NOSPAMcomcast.net> >>> wrote in message news:%236rzKZUQGHA.3984@TK2MSFTNGP14.phx.gbl... >>>>> > well-established company. If the OP is a one-man operation >>>>> > (or part of a small, non-established company), my concern >>>>> > would be the "bus accident scenario". What is that? Well, >>>>> > if I buy the OP's product and he gets hit by a bus (or some >>>>> > other event transpires which makes him unable to further >>>>> > support the product), what happens when I buy a new >>>>> > computer or replace the hard drive? The answer is, "I'm screwed!" >>>>> >>>>> Very good point! >>>>> I have a one man company and have hardware based licensing. >>>>> Want to become a partner? >>>> >>>> Well, taking on multiple partners that are not local to you (odds of >>>> them >>>> all getting hit by a bus at the same time would be slim to none) would >>>> be >>>> one way of handling the problem. As for me becoming a partner... well, >>>> I >>>> don't think I could afford to buy my way into any company, yours or any >>>> other (retired, fixed-income, etc). >>>> >>>> Rick >>>> >>>> >>> >> >> > > Squished - to be smunched resulting in (normally) a severely vertically
challenged individual. Oh, you mean escrow. Basically you give your <item> to a third party that holds it for you, and in the event of <incident you define> performs <desired action on your former behalf>. eBay'ers use this when buying something ... You send your money to an escrow agent, I send you the product. You have x days to tell the escrow agent you accept the product; if that expires the agent sends me your money (for a fee). If you decline the product, the escrow agent returns your money once I've got the product back in my hands. -- Randy Birch MS MVP Visual Basic http://vbnet.mvps.org/ Please reply to the newsgroups so all can participate. "Kevin Provance" <ca***@tpasoft.com> wrote in message I've never really understood that concept. Can someone explain it to me innews:uRLA7EkQGHA.3896@TK2MSFTNGP15.phx.gbl... layman's terms? Thanks! - Kev Show quoteHide quote "Dave" <nob***@nowhere.com> wrote in message news:O0GF4CdQGHA.5248@TK2MSFTNGP09.phx.gbl... > Another thing small or one-man operators should consider is placing their > source code in escrow so if they are squished by a bus, the code is > available should fixes be needed. > > Dave O. > > "Kevin Provance" <ca***@tpasoft.com> wrote in message > news:eZsK6KYQGHA.2496@TK2MSFTNGP11.phx.gbl... >> It is a good idea to have a contingency plan in place. As a fellow one >> man show, whose been doing this shareware thang for about ten years now, >> I developed a long time ago a protocol to put into place, to be excecuted >> by surviving relatives in the event of my untimely demise. Here is some >> of what I did FYI...or if you want more specific details, email me. I'd >> be happy to discuss them with you: >> >> 1) I have a pre-written index page for my website to be uploaded stating >> that something had happened to me and I would no longer be able to >> support my products. >> >> 2) I would no longer be accepting new registrations but would have the >> files available for those who needed replacements. >> >> 3) I have in place a program designed to reproduce "lost registration >> numbers" for existing customers that could be easily operated by >> surviving relatives. >> >> 4) I have paperwork in place to give my parents or surviving them my >> sibling and when of age my son power of attorney over my buisness >> accounts and compenstion for all the trouble they will experience in >> cleaning up after my passing. My lawyer also drafted up my will to >> specific as such (it's never too early...really). >> >> 5) I have ready to go a Paypal account for those customers who wish to >> donate to the post-running of my biz to whomever takes it over to >> maintain existing customers...but no new ones. I would only consider >> continuing the business if I had an agreement with another developer who >> would take over the projects and compensate my surviving relatives >> (actually, they would be his boss, but that is something I've not >> considered at this point, finding a replacement for me). >> >> That is about the gist of it. I do sleep a little better at night >> knowing I've left adiquate instructions and protocols in place as I would >> not want to dump on my family the respnsibility or the fallout of my biz >> just hanging out there with no idea or direction about what to do. >> >> Hope this helps. >> >> - Kev >> >> "RB Smissaert" <bartsmissa***@blueyonder.co.uk> wrote in message >> news:OfQSEiUQGHA.140@TK2MSFTNGP12.phx.gbl... >>>I always could ask my wife or kids to learn how to deal with the >>>licensing. >>> Then again we might get hit by the same bus! >>> Wasn't serious about the partnership, but now you replied: >>> It wouldn't be buying into the company, it would be improving the >>> product >>> and in return get part of the profit. So there would be no financial >>> costs. >>> It is only a little side job for me, but it is picking up very nicely. >>> >>> RBS >>> >>> >>> "Rick Rothstein [MVP - Visual Basic]" <rickNOSPAMnews@NOSPAMcomcast.net> >>> wrote in message news:%236rzKZUQGHA.3984@TK2MSFTNGP14.phx.gbl... >>>>> > well-established company. If the OP is a one-man operation >>>>> > (or part of a small, non-established company), my concern >>>>> > would be the "bus accident scenario". What is that? Well, >>>>> > if I buy the OP's product and he gets hit by a bus (or some >>>>> > other event transpires which makes him unable to further >>>>> > support the product), what happens when I buy a new >>>>> > computer or replace the hard drive? The answer is, "I'm screwed!" >>>>> >>>>> Very good point! >>>>> I have a one man company and have hardware based licensing. >>>>> Want to become a partner? >>>> >>>> Well, taking on multiple partners that are not local to you (odds of >>>> them >>>> all getting hit by a bus at the same time would be slim to none) would >>>> be >>>> one way of handling the problem. As for me becoming a partner... well, >>>> I >>>> don't think I could afford to buy my way into any company, yours or any >>>> other (retired, fixed-income, etc). >>>> >>>> Rick >>>> >>>> >>> >> >> > > Thanks Randy.
I should clarify tho...I understand the concept of escrow. What I don't understand is how it applies to source code holding in the event something happens to me. I am guessing that the end user gives the third party a specified amount of cash in return for the source code to my project in the event something hapens to me. Fine. But if something happens to me, how would I benefit from that? I'm dead, the end user has my code and who gets the cash? Surviving relatives? My company? Shouldn't I get the cash up front so I can at least enjoy it? :) That's the part I am not getting my head around. - Kev Show quoteHide quote "Randy Birch" <rgb_removet***@mvps.org> wrote in message news:u0bGLzkQGHA.4264@TK2MSFTNGP11.phx.gbl... > Squished - to be smunched resulting in (normally) a severely vertically > challenged individual. > > Oh, you mean escrow. Basically you give your <item> to a third party that > holds it for you, and in the event of <incident you define> performs > <desired action on your former behalf>. > > eBay'ers use this when buying something ... You send your money to an > escrow > agent, I send you the product. You have x days to tell the escrow agent > you > accept the product; if that expires the agent sends me your money (for a > fee). If you decline the product, the escrow agent returns your money once > I've got the product back in my hands. > > -- > > Randy Birch > MS MVP Visual Basic > http://vbnet.mvps.org/ > > Please reply to the newsgroups so all can participate. > > > > > "Kevin Provance" <ca***@tpasoft.com> wrote in message > news:uRLA7EkQGHA.3896@TK2MSFTNGP15.phx.gbl... > I've never really understood that concept. Can someone explain it to me > in > layman's terms? > > Thanks! > > - Kev > > "Dave" <nob***@nowhere.com> wrote in message > news:O0GF4CdQGHA.5248@TK2MSFTNGP09.phx.gbl... >> Another thing small or one-man operators should consider is placing their >> source code in escrow so if they are squished by a bus, the code is >> available should fixes be needed. >> >> Dave O. >> >> "Kevin Provance" <ca***@tpasoft.com> wrote in message >> news:eZsK6KYQGHA.2496@TK2MSFTNGP11.phx.gbl... >>> It is a good idea to have a contingency plan in place. As a fellow one >>> man show, whose been doing this shareware thang for about ten years now, >>> I developed a long time ago a protocol to put into place, to be >>> excecuted >>> by surviving relatives in the event of my untimely demise. Here is some >>> of what I did FYI...or if you want more specific details, email me. I'd >>> be happy to discuss them with you: >>> >>> 1) I have a pre-written index page for my website to be uploaded stating >>> that something had happened to me and I would no longer be able to >>> support my products. >>> >>> 2) I would no longer be accepting new registrations but would have the >>> files available for those who needed replacements. >>> >>> 3) I have in place a program designed to reproduce "lost registration >>> numbers" for existing customers that could be easily operated by >>> surviving relatives. >>> >>> 4) I have paperwork in place to give my parents or surviving them my >>> sibling and when of age my son power of attorney over my buisness >>> accounts and compenstion for all the trouble they will experience in >>> cleaning up after my passing. My lawyer also drafted up my will to >>> specific as such (it's never too early...really). >>> >>> 5) I have ready to go a Paypal account for those customers who wish to >>> donate to the post-running of my biz to whomever takes it over to >>> maintain existing customers...but no new ones. I would only consider >>> continuing the business if I had an agreement with another developer who >>> would take over the projects and compensate my surviving relatives >>> (actually, they would be his boss, but that is something I've not >>> considered at this point, finding a replacement for me). >>> >>> That is about the gist of it. I do sleep a little better at night >>> knowing I've left adiquate instructions and protocols in place as I >>> would >>> not want to dump on my family the respnsibility or the fallout of my biz >>> just hanging out there with no idea or direction about what to do. >>> >>> Hope this helps. >>> >>> - Kev >>> >>> "RB Smissaert" <bartsmissa***@blueyonder.co.uk> wrote in message >>> news:OfQSEiUQGHA.140@TK2MSFTNGP12.phx.gbl... >>>>I always could ask my wife or kids to learn how to deal with the >>>>licensing. >>>> Then again we might get hit by the same bus! >>>> Wasn't serious about the partnership, but now you replied: >>>> It wouldn't be buying into the company, it would be improving the >>>> product >>>> and in return get part of the profit. So there would be no financial >>>> costs. >>>> It is only a little side job for me, but it is picking up very nicely. >>>> >>>> RBS >>>> >>>> >>>> "Rick Rothstein [MVP - Visual Basic]" >>>> <rickNOSPAMnews@NOSPAMcomcast.net> >>>> wrote in message news:%236rzKZUQGHA.3984@TK2MSFTNGP14.phx.gbl... >>>>>> > well-established company. If the OP is a one-man operation >>>>>> > (or part of a small, non-established company), my concern >>>>>> > would be the "bus accident scenario". What is that? Well, >>>>>> > if I buy the OP's product and he gets hit by a bus (or some >>>>>> > other event transpires which makes him unable to further >>>>>> > support the product), what happens when I buy a new >>>>>> > computer or replace the hard drive? The answer is, "I'm screwed!" >>>>>> >>>>>> Very good point! >>>>>> I have a one man company and have hardware based licensing. >>>>>> Want to become a partner? >>>>> >>>>> Well, taking on multiple partners that are not local to you (odds of >>>>> them >>>>> all getting hit by a bus at the same time would be slim to none) would >>>>> be >>>>> one way of handling the problem. As for me becoming a partner... well, >>>>> I >>>>> don't think I could afford to buy my way into any company, yours or >>>>> any >>>>> other (retired, fixed-income, etc). >>>>> >>>>> Rick >>>>> >>>>> >>>> >>> >>> >> >> > > I presume such an arrangement would have the escrow agent pass the code on
to a designated individual or the public domain if a negative fate befell the developer. I suppose the arrangement could, depending on the agent, either be paid for up front by the dev, or the release by the escrow agent would require some sort of payment from the recipient(s) post-smoosh. Pretty well the same as giving the code to a lawyer to hold in trust in case something happens. The purpose of this exercise is not to generate cash for you directly from the future release of the code, but rather to create and provide a sensible "insurance policy" for developers concerned about paying now for your non-source code assets (controls, dlls, apps etc) whereby they can get this code if you kick the bucket. -- Randy Birch MS MVP Visual Basic http://vbnet.mvps.org/ Please reply to the newsgroups so all can participate. "Kevin Provance" <ca***@tpasoft.com> wrote in message I should clarify tho...I understand the concept of escrow. What I don'tnews:%23KMczIlQGHA.5552@TK2MSFTNGP10.phx.gbl... Thanks Randy. understand is how it applies to source code holding in the event something happens to me. I am guessing that the end user gives the third party a specified amount of cash in return for the source code to my project in the event something hapens to me. Fine. But if something happens to me, how would I benefit from that? I'm dead, the end user has my code and who gets the cash? Surviving relatives? My company? Shouldn't I get the cash up front so I can at least enjoy it? :) That's the part I am not getting my head around. - Kev Show quoteHide quote "Randy Birch" <rgb_removet***@mvps.org> wrote in message news:u0bGLzkQGHA.4264@TK2MSFTNGP11.phx.gbl... > Squished - to be smunched resulting in (normally) a severely vertically > challenged individual. > > Oh, you mean escrow. Basically you give your <item> to a third party that > holds it for you, and in the event of <incident you define> performs > <desired action on your former behalf>. > > eBay'ers use this when buying something ... You send your money to an > escrow > agent, I send you the product. You have x days to tell the escrow agent > you > accept the product; if that expires the agent sends me your money (for a > fee). If you decline the product, the escrow agent returns your money once > I've got the product back in my hands. > > -- > > Randy Birch > MS MVP Visual Basic > http://vbnet.mvps.org/ > > Please reply to the newsgroups so all can participate. > > > > > "Kevin Provance" <ca***@tpasoft.com> wrote in message > news:uRLA7EkQGHA.3896@TK2MSFTNGP15.phx.gbl... > I've never really understood that concept. Can someone explain it to me > in > layman's terms? > > Thanks! > > - Kev > > "Dave" <nob***@nowhere.com> wrote in message > news:O0GF4CdQGHA.5248@TK2MSFTNGP09.phx.gbl... >> Another thing small or one-man operators should consider is placing their >> source code in escrow so if they are squished by a bus, the code is >> available should fixes be needed. >> >> Dave O. >> >> "Kevin Provance" <ca***@tpasoft.com> wrote in message >> news:eZsK6KYQGHA.2496@TK2MSFTNGP11.phx.gbl... >>> It is a good idea to have a contingency plan in place. As a fellow one >>> man show, whose been doing this shareware thang for about ten years now, >>> I developed a long time ago a protocol to put into place, to be >>> excecuted >>> by surviving relatives in the event of my untimely demise. Here is some >>> of what I did FYI...or if you want more specific details, email me. I'd >>> be happy to discuss them with you: >>> >>> 1) I have a pre-written index page for my website to be uploaded stating >>> that something had happened to me and I would no longer be able to >>> support my products. >>> >>> 2) I would no longer be accepting new registrations but would have the >>> files available for those who needed replacements. >>> >>> 3) I have in place a program designed to reproduce "lost registration >>> numbers" for existing customers that could be easily operated by >>> surviving relatives. >>> >>> 4) I have paperwork in place to give my parents or surviving them my >>> sibling and when of age my son power of attorney over my buisness >>> accounts and compenstion for all the trouble they will experience in >>> cleaning up after my passing. My lawyer also drafted up my will to >>> specific as such (it's never too early...really). >>> >>> 5) I have ready to go a Paypal account for those customers who wish to >>> donate to the post-running of my biz to whomever takes it over to >>> maintain existing customers...but no new ones. I would only consider >>> continuing the business if I had an agreement with another developer who >>> would take over the projects and compensate my surviving relatives >>> (actually, they would be his boss, but that is something I've not >>> considered at this point, finding a replacement for me). >>> >>> That is about the gist of it. I do sleep a little better at night >>> knowing I've left adiquate instructions and protocols in place as I >>> would >>> not want to dump on my family the respnsibility or the fallout of my biz >>> just hanging out there with no idea or direction about what to do. >>> >>> Hope this helps. >>> >>> - Kev >>> >>> "RB Smissaert" <bartsmissa***@blueyonder.co.uk> wrote in message >>> news:OfQSEiUQGHA.140@TK2MSFTNGP12.phx.gbl... >>>>I always could ask my wife or kids to learn how to deal with the >>>>licensing. >>>> Then again we might get hit by the same bus! >>>> Wasn't serious about the partnership, but now you replied: >>>> It wouldn't be buying into the company, it would be improving the >>>> product >>>> and in return get part of the profit. So there would be no financial >>>> costs. >>>> It is only a little side job for me, but it is picking up very nicely. >>>> >>>> RBS >>>> >>>> >>>> "Rick Rothstein [MVP - Visual Basic]" >>>> <rickNOSPAMnews@NOSPAMcomcast.net> >>>> wrote in message news:%236rzKZUQGHA.3984@TK2MSFTNGP14.phx.gbl... >>>>>> > well-established company. If the OP is a one-man operation >>>>>> > (or part of a small, non-established company), my concern >>>>>> > would be the "bus accident scenario". What is that? Well, >>>>>> > if I buy the OP's product and he gets hit by a bus (or some >>>>>> > other event transpires which makes him unable to further >>>>>> > support the product), what happens when I buy a new >>>>>> > computer or replace the hard drive? The answer is, "I'm screwed!" >>>>>> >>>>>> Very good point! >>>>>> I have a one man company and have hardware based licensing. >>>>>> Want to become a partner? >>>>> >>>>> Well, taking on multiple partners that are not local to you (odds of >>>>> them >>>>> all getting hit by a bus at the same time would be slim to none) would >>>>> be >>>>> one way of handling the problem. As for me becoming a partner... well, >>>>> I >>>>> don't think I could afford to buy my way into any company, yours or >>>>> any >>>>> other (retired, fixed-income, etc). >>>>> >>>>> Rick >>>>> >>>>> >>>> >>> >>> >> >> > > Thanks for the clarification Randy. I don't think it really applies to me
considering what I do, but I do appreciate the explaination. :-) - Kev Show quoteHide quote "Randy Birch" <rgb_removet***@mvps.org> wrote in message news:evV152lQGHA.6008@TK2MSFTNGP10.phx.gbl... >I presume such an arrangement would have the escrow agent pass the code on > to a designated individual or the public domain if a negative fate befell > the developer. I suppose the arrangement could, depending on the agent, > either be paid for up front by the dev, or the release by the escrow agent > would require some sort of payment from the recipient(s) post-smoosh. > Pretty > well the same as giving the code to a lawyer to hold in trust in case > something happens. The purpose of this exercise is not to generate cash > for > you directly from the future release of the code, but rather to create and > provide a sensible "insurance policy" for developers concerned about > paying > now for your non-source code assets (controls, dlls, apps etc) whereby > they > can get this code if you kick the bucket. > > -- > > Randy Birch > MS MVP Visual Basic > http://vbnet.mvps.org/ > > Please reply to the newsgroups so all can participate. > > > > > "Kevin Provance" <ca***@tpasoft.com> wrote in message > news:%23KMczIlQGHA.5552@TK2MSFTNGP10.phx.gbl... > Thanks Randy. > > I should clarify tho...I understand the concept of escrow. What I don't > understand is how it applies to source code holding in the event something > happens to me. I am guessing that the end user gives the third party a > specified amount of cash in return for the source code to my project in > the > event something hapens to me. Fine. But if something happens to me, how > would I benefit from that? I'm dead, the end user has my code and who > gets > the cash? Surviving relatives? My company? Shouldn't I get the cash up > front so I can at least enjoy it? :) > > That's the part I am not getting my head around. > > - Kev > > "Randy Birch" <rgb_removet***@mvps.org> wrote in message > news:u0bGLzkQGHA.4264@TK2MSFTNGP11.phx.gbl... >> Squished - to be smunched resulting in (normally) a severely vertically >> challenged individual. >> >> Oh, you mean escrow. Basically you give your <item> to a third party >> that >> holds it for you, and in the event of <incident you define> performs >> <desired action on your former behalf>. >> >> eBay'ers use this when buying something ... You send your money to an >> escrow >> agent, I send you the product. You have x days to tell the escrow agent >> you >> accept the product; if that expires the agent sends me your money (for a >> fee). If you decline the product, the escrow agent returns your money >> once >> I've got the product back in my hands. >> >> -- >> >> Randy Birch >> MS MVP Visual Basic >> http://vbnet.mvps.org/ >> >> Please reply to the newsgroups so all can participate. >> >> >> >> >> "Kevin Provance" <ca***@tpasoft.com> wrote in message >> news:uRLA7EkQGHA.3896@TK2MSFTNGP15.phx.gbl... >> I've never really understood that concept. Can someone explain it to me >> in >> layman's terms? >> >> Thanks! >> >> - Kev >> >> "Dave" <nob***@nowhere.com> wrote in message >> news:O0GF4CdQGHA.5248@TK2MSFTNGP09.phx.gbl... >>> Another thing small or one-man operators should consider is placing >>> their >>> source code in escrow so if they are squished by a bus, the code is >>> available should fixes be needed. >>> >>> Dave O. >>> >>> "Kevin Provance" <ca***@tpasoft.com> wrote in message >>> news:eZsK6KYQGHA.2496@TK2MSFTNGP11.phx.gbl... >>>> It is a good idea to have a contingency plan in place. As a fellow one >>>> man show, whose been doing this shareware thang for about ten years >>>> now, >>>> I developed a long time ago a protocol to put into place, to be >>>> excecuted >>>> by surviving relatives in the event of my untimely demise. Here is >>>> some >>>> of what I did FYI...or if you want more specific details, email me. >>>> I'd >>>> be happy to discuss them with you: >>>> >>>> 1) I have a pre-written index page for my website to be uploaded >>>> stating >>>> that something had happened to me and I would no longer be able to >>>> support my products. >>>> >>>> 2) I would no longer be accepting new registrations but would have the >>>> files available for those who needed replacements. >>>> >>>> 3) I have in place a program designed to reproduce "lost registration >>>> numbers" for existing customers that could be easily operated by >>>> surviving relatives. >>>> >>>> 4) I have paperwork in place to give my parents or surviving them my >>>> sibling and when of age my son power of attorney over my buisness >>>> accounts and compenstion for all the trouble they will experience in >>>> cleaning up after my passing. My lawyer also drafted up my will to >>>> specific as such (it's never too early...really). >>>> >>>> 5) I have ready to go a Paypal account for those customers who wish to >>>> donate to the post-running of my biz to whomever takes it over to >>>> maintain existing customers...but no new ones. I would only consider >>>> continuing the business if I had an agreement with another developer >>>> who >>>> would take over the projects and compensate my surviving relatives >>>> (actually, they would be his boss, but that is something I've not >>>> considered at this point, finding a replacement for me). >>>> >>>> That is about the gist of it. I do sleep a little better at night >>>> knowing I've left adiquate instructions and protocols in place as I >>>> would >>>> not want to dump on my family the respnsibility or the fallout of my >>>> biz >>>> just hanging out there with no idea or direction about what to do. >>>> >>>> Hope this helps. >>>> >>>> - Kev >>>> >>>> "RB Smissaert" <bartsmissa***@blueyonder.co.uk> wrote in message >>>> news:OfQSEiUQGHA.140@TK2MSFTNGP12.phx.gbl... >>>>>I always could ask my wife or kids to learn how to deal with the >>>>>licensing. >>>>> Then again we might get hit by the same bus! >>>>> Wasn't serious about the partnership, but now you replied: >>>>> It wouldn't be buying into the company, it would be improving the >>>>> product >>>>> and in return get part of the profit. So there would be no financial >>>>> costs. >>>>> It is only a little side job for me, but it is picking up very nicely. >>>>> >>>>> RBS >>>>> >>>>> >>>>> "Rick Rothstein [MVP - Visual Basic]" >>>>> <rickNOSPAMnews@NOSPAMcomcast.net> >>>>> wrote in message news:%236rzKZUQGHA.3984@TK2MSFTNGP14.phx.gbl... >>>>>>> > well-established company. If the OP is a one-man operation >>>>>>> > (or part of a small, non-established company), my concern >>>>>>> > would be the "bus accident scenario". What is that? Well, >>>>>>> > if I buy the OP's product and he gets hit by a bus (or some >>>>>>> > other event transpires which makes him unable to further >>>>>>> > support the product), what happens when I buy a new >>>>>>> > computer or replace the hard drive? The answer is, "I'm screwed!" >>>>>>> >>>>>>> Very good point! >>>>>>> I have a one man company and have hardware based licensing. >>>>>>> Want to become a partner? >>>>>> >>>>>> Well, taking on multiple partners that are not local to you (odds of >>>>>> them >>>>>> all getting hit by a bus at the same time would be slim to none) >>>>>> would >>>>>> be >>>>>> one way of handling the problem. As for me becoming a partner... >>>>>> well, >>>>>> I >>>>>> don't think I could afford to buy my way into any company, yours or >>>>>> any >>>>>> other (retired, fixed-income, etc). >>>>>> >>>>>> Rick >>>>>> >>>>>> >>>>> >>>> >>>> >>> >>> >> >> > > On Tue, 7 Mar 2006 20:08:02 -0500, "Randy Birch"
<rgb_removet***@mvps.org> wrote: >Squished - to be smunched resulting in (normally) a severely vertically But will the escrow agent squish (see above) the buyer for the seller>challenged individual. > >Oh, you mean escrow. if said buyer is unhappy with said seller's product? I assume that costs extra. |
|||||||||||||||||||||||
Other interesting topics