Author | Topic: Running vX and xB on same machine | |
---|---|---|
Richard Hankins | Running vX and xB on same machine on Wed, 18 Feb 2004 16:52:34 -0600 will installing vX affect my copy of 1.82? I want to install vX to look at it, but I do not want to hurt what I already have. Thanks, - Richard Hankins | |
Joe Carrick | Re: Running vX and xB on same machine on Wed, 18 Feb 2004 15:27:24 -0800 No Problem, VX Prerelease simply works using Xbase++ V1.82 - no changes to the V1.82 files. You can either use VX or just use your project scripts with pbuild - either will work. -Joe "Richard Hankins" <rhankins@contactasi.com> wrote in message news:rQLenHn9DHA.3800@S15147418... > will installing vX affect my copy of 1.82? > > I want to install vX to look at it, but I do not want to hurt what I already have. > > Thanks, > > - Richard Hankins > > | |
Thomas Braun | Re: Running vX and xB on same machine on Thu, 19 Feb 2004 07:53:13 +0100 Richard Hankins: > will installing vX affect my copy of 1.82? Yes: README - SNIP --- IMPORTANT NOTE: VISUAL XBASE++ 2.0 PRERELEASE SETUP WILL MODIFY FILES IN YOUR XBASE++ INSTALLATION!! IT IS STRONGLY RECOMMENDED TO FIRST CREATE A BACKUP OF YOUR EXISTING XBASE++ INSTALLATION BEFORE INSTALLING VISUAL XBASE++ 2.0 PRERELEASE! README - SNIP --- I did a separate install of 1.82 and installed VX into this new installation apart from my production environment. This was quite easy since I use the same setup as proposed by Frank++ sometimes ago: - Install each new Xbase++ version into its own directory below \alaska\: \alaska\xpp284 \alaska\xpp294 \alaska\xpp335 (VX-Version) Below each of the dirs above are the common directories like BIN, BOOK, LIB etc... - Create a batch similar to this for each version of Xbase++: rem ****************************** rem Set-Batch for Xbase++ 1.80.284 rem first param can be used to rem set the desired drive letter rem ****************************** @ECHO OFF CLS IF "%1" == "" GOTO DEFAULT IF EXIST %1:\ SUBST %1: /D SUBST %1: D:\ALASKA\XPP284 GOTO :END :DEFAULT IF EXIST O:\ SUBST O: /D SUBST O: D:\ALASKA\XPP284 :END You could even substitute XPP284 with %2 and pass the version string as a second parameter. - Use the environment setting of autoexec.bat (Win9x) or the built-in OS setting (W2k, XP): SET INCLUDE=o:\INCLUDE; SET LIB=o:\LIB; SET PATH=o:\BIN;o:\LIB; Now you can switch your whole environment by simply running the related batch file. HTH Thomas Braun |