Moral or legal dilemma
I am working from home whenever I can. That's the beauty of what I do. So long as I have internet access at home (I do) and access to a computer at home (I have four) I don't NEED to be at the office all the time. Perhaps 40% of my time MUST be based at the company for all my R&D, repair work and production. The other 60% is writing manuals, writing software and dealing with email and suchlike. Now GuruJr has arrived (five weeks old and doing well!), the more I can get done at home working flexible patterns, the less time I spend at the office means I can give more assistance to my wife during the early months.
Here's the dilemma. I have Office, email and most of my utilities and apps on my computer at home, all legitimate and all licenced to me personally. The one package I DON'T have is VB6 which I use to write apps for our product range (computer based simulators for military and police firearms training).
I have ONE copy installed at work. I want to use VB6 at home. I cannot find another copy anywhere and Microsoft assure me it is obsolete and I need VB .Net - which I don't! I don't need any .Net functionality (all our systems are stand-alone) and I'm au fait with VB6 and see no reason to change (and then have to port all my old code).
I can't remove VB from my works machine and install it on a laptop which I then cart to and from home, because much of what I do needs specialised hardware cards installed and this just ain't 'do-able' on a laptop. The EULA states that the software is licenced to ONE user (me) and for installation on ONE PC. I could uninstall it from the machine at work when I leave, and then re-install it on one of the home PCs to work from home, and then reverse the process when I go into the office, but this is a royal pain in the keester as I'm sure is obvious.
My second thought was to fit caddies to the work and home computers, and use one hard disk and install VB onto that and then swap the drive between work and home as necessary, but as VB needs to install a whole pile of stuff in the windows\system folder and the machines have different hardware and apps installed, that causes problems. Besides, swapping ONE hard drive means one dead machine at the other end. The home setup is no problem...there are three other PC's. The problem is at work is others have to use apps on my machine from time to time. There is also the issue of using different OS's and the EULA issue for the OS if I transfer a drive between locations. At work I (reluctantly) use XP pro, and at home I prefer 98 as it is more stable and the same CPU and memory spec (2GHz, 384Mb) runs 98 about twice as fast as it does XP.
I then thought of fitting caddies and putting VB and all my working files on a second drive (D drive) and just swapping the 'VB' drive, leaving the apps, OS and data intact on both machines. Technically there is only ONE user (me) and it is only installed and used on ONE machine. Not always the same machine, but only ever one machine.
The problem is, the files that get copied to the system folder! Even installing to a 'D drive', the main system drive needa a lot copied to it. Then there are registry entries. Some of these are just OCX controls or the run-time libraries, but several hundred files are necessary system files. So, to use the 'D drive' on both machines, I still need to install VB completely from the CD on each machine so that the registry and system files are there.
So how do I get round this? My arguement is this: Even with VB correctly installed on the two machines, if the D drive is removed, the installation is not complete and VB will not work. VB can only ever be used un the machine that the drive is fitted to.
But, and here's the BUT...the registry on BOTH machines AND the windows\system folder contains stuff necessary to make VB work. Any audit of software or communication of the registry to and from Microsoft will reveal that I (aparrently!) have the same software on BOTH machines.
I contacted M$ and asked them if I could purchase another licence for VB6, figuring that if I had TWO licences, then I could do a full install on TWO PCs simultaneously. They said no, sorry, we do NOT sell VB6 licences any more. I was told I COULD purchase a full (Enterprise) copy of Visual Studio.Net and then 'downgrade' the licence to VB6 but that would cost me a LOT of money and I don't like paying M$ prices for something I don't want!
One last point. Even if the software is fully installed on two machines, one at work and the other at home, I can only EVER be in front of one machine (using one copy) at a time. Technically I COULD be using VB at home while someone used it at work, but as the only person in the company who uses VB, that can't happen!
Suggestions? Ideas? Comments? Thoughts? All constructive input gratefully welcomed, but all 'solutions' must have no financial cost...them bastards in Seattle are NOT getting another penny from me for this 'obsolete' product!!!!