Installing VB6 on a USB drive?
Does anyone know if it's possible to install/run VB6 on a USB drive? The installer doesn't seem to want to put vital files on the drive, and will only let me put them in System32 where, of course, I can't take them with me. Is a portable install possible? Has anyone tried this?
Before installing you'll get the oportunity to select where VB should be installed, as well as selecting tools, helpfiles and so on. Nevertheless, lots of components are placed in the system map and registered the common way.
With some 'hands on' you could move those components to your removable disk and alter the registration with regsvr32.exe. However, the registry is where it is, so you could never bring the disk to another machine and get it working, unless you don't register the components there as well.
But it seems to me, that giving this a try will cause lots of problems until getting it working.
No, because not only does Visual Basic use the System folders but it also requires Registry access on the machine from which it was installed.
Originally Posted by Crimplato
Microsoft MVP (Visual Basic)
Just out of curiosity, why would you want to do this?
Have you considered just copying the VB run-time application from msdn.microsoft.com to your device?
i would certainly like the same thing as requested installing on many machines isn't very useful. cant someone make a registry updating file thing which basically does the same as a fresh install? (so it fakes an install or something)
I'm not too sure that this type of installation would be within the guidelines of MS' licensing laws. You are trying to
bypass the limit by faking the installation of vb6 on a usb jump drive and being able to run it on several systems.
Either purchase more licenses or do an installation to your systems hard drive.
oh ok. just seemed like a good sounding feature if it were portable.
Its valid if you install it to a system or laptop. Installing to a laptop is best if you need the portability.
my laptop is linux, i havn't got it to work in wine i thought maybe a portable version would help it work in wine
It would be even more complex for a protable install since VS uses some shared directories/file.
C:\Program Files\Common Files\Microsoft Shared\VS98 - for ex.
Taken from the EULA in VB6...
'You may install copies of the SOFTWARE PRODUCT on an unlimited number of computers provided that you are the only individual using the SOFTWARE PRODUCT.'
It doesn't say anything about removable drives...
Bernie's right. the idea supports the EULA completely, only i have access to my usb drive its passworded
You could make is semi-portable by installing it on more than one computer and using the usb as the target for all installations. This way the system files will be installed in the correct folders on each computer while the user files will be installed on the usb drive.
It will be a little tedious to perform the installation more than once, but you will only have to do it once for each machine.
Just make sure to place your project files on the usb drive also.
A very simple method would be to use regmon and filemon to monitor the install. (These may be obtained from www.sysinternals.com)
Then build a reg file to build the nessasary registry keys. You may need to modify the registry entries to conform to the new path to include a new drive letter for each machine as this would change depending upon how many drives were configured.
Copy all of the required files to the usb drive, maintaining respective file trees.
Build a batch file to copy the required files to the Windows and System32 directories as needed.
Build the nessasary shared working directories and start menu items etc...
Register the DLLs.
You should now have a working routine that would allow you to utilize the installion on the USB drive.
You should also build a procedure to reverse this process after have finished using VB at that location.
This would not only leave a clean PC but allow you to retain any personalizations and working space you had established.
I would also suggest that you maintian seperate working areas for each OS type you will be using. As each may or may not function with any modifications made by a previous OS.
Thanks for the clarification. Guess as long as its only your systems its ok according to the EULA.
Originally Posted by Bernie
We only have the MSDN subscription so I didnt have access to the EULA and I was too lazy to search for it on M$. Guess
thats what I get for being lazy.
-- Android Development Center
-- Cloud Development Project Center
-- HTML5 Development Center
-- Windows Mobile Development Center