I began working with version 4 Beta by putting it in its own directory setup called PureBasic4. I still have version 3.94 on my PC in a directory called PureBasic.
I decided to see if I could mesh the two together, so I set up a new PureBasic directory on another drive and copied everything from version 3.94 into it first, then copied the files from PureBasic4 over the ones copied from 3.94. It didn't work. I've tried variations of this approach, with different results - either I get a blank messagebox come up with the title "PureBasic - Assembler Eror", or I cannot access the PureLibraries, or I get a conflict where ProgramProcess is reported to be defined differently in Misc2 and Process, or the IDE source pane fails to open.
I was wondering if anyone else has attempted this and been more successful.
ITrouble istalling PV version 4 Beta over 3.94
ITrouble istalling PV version 4 Beta over 3.94
has-been wanna-be (You may not agree with what I say, but it will make you think).
-
Bonne_den_kule
- Addict
- Posts: 841
- Joined: Mon Jun 07, 2004 7:10 pm
-
netmaestro
- PureBasic Bullfrog
- Posts: 8452
- Joined: Wed Jul 06, 2005 5:42 am
- Location: Fort Nelson, BC, Canada
1. Clean everything off and start over.
2. Use the PureBasic 3.94 installer to install 3.94 to your program files directory.
3. Make a new folder on any drive you want.
4. Unzip the beta to that folder.
5. Surf to the beta folder and right-click the PureBasic.exe file, select "Send To" and "Desktop - Create Shortcut".
You will now have two icons for PureBasic on your desktop, a 2d one and a 3d one. The 2d will start 3.94 and the 3d will start 4.0. Neither will start if the other is already running, so close it down to switch back and forth.
-Never copy a 4.0 over top of a 3.94 directory structure
-Never run SmartUpdate on version 4. It will nuke it.
2. Use the PureBasic 3.94 installer to install 3.94 to your program files directory.
3. Make a new folder on any drive you want.
4. Unzip the beta to that folder.
5. Surf to the beta folder and right-click the PureBasic.exe file, select "Send To" and "Desktop - Create Shortcut".
You will now have two icons for PureBasic on your desktop, a 2d one and a 3d one. The 2d will start 3.94 and the 3d will start 4.0. Neither will start if the other is already running, so close it down to switch back and forth.
-Never copy a 4.0 over top of a 3.94 directory structure
-Never run SmartUpdate on version 4. It will nuke it.
BERESHEIT
-
Joakim Christiansen
- Addict
- Posts: 2452
- Joined: Wed Dec 22, 2004 4:12 pm
- Location: Norway
- Contact:
Re: ITrouble istalling PV version 4 Beta over 3.94
Why would you want to do that?oldefoxx wrote:I decided to see if I could mesh the two together...
Re: ITrouble istalling PV version 4 Beta over 3.94
Because it's not supposed to workoldefoxx wrote:[...] so I set up a new PureBasic directory on another drive and copied everything from version 3.94 into it first, then copied the files from PureBasic4 over the ones copied from 3.94. It didn't work. [...]
Good programmers don't comment their code. It was hard to write, should be hard to read.
Why do that?
I have a lot of help files and code pieces that I acquired or created with the earlier version of PB. When the time comes to upgrade to version 4, most people will likely want to mesh the two together so that they retain what they can retain, while getting the latest and greatest. So I figured I would go ahead and see how well it worked with the Beta.
Turns out I can copy a selection of subdirectories from 3.94 over to 4, but so far not the PureLibraries, Compilers, and some others I am hsxitant to try without first backing up the success I've achieved to date. So now I have everything up to 3.94 in one setup, the 4 Beta set up alone, and the partial merge of 4 Beta over 3.94 in a third..
Turns out I can copy a selection of subdirectories from 3.94 over to 4, but so far not the PureLibraries, Compilers, and some others I am hsxitant to try without first backing up the success I've achieved to date. So now I have everything up to 3.94 in one setup, the 4 Beta set up alone, and the partial merge of 4 Beta over 3.94 in a third..
has-been wanna-be (You may not agree with what I say, but it will make you think).
Continuing Success with version 4 over 3.94
As I tried to explain in earlier posts, you cannot simply install version 4 over
version 3.94 without encountering some problems. However, I found that I could selectively add folders from 3.94 to the new purebasic folder, but it was a trial and error process. Once done though, I found that if I select everything in \purebasic\main, I can copy it into \purebasic, and retain the mix with each new version update.
If I paid attention to the contents of the original \purebasic\purebasic.prefs file, I could prevent an automatic overwrite from the new purebasic\main\purebasic.prefs file. You can do this by first selecting just the \purebasic\main\purebasic.prefs file, then picking Invert Selection (just below the Select All option in the Explorer Edit list of actions).
The risk is that in future versions, some of the controls in purebasic.prefs may change, creating an incompatability. So right now I think it would be
better to manually view and edit the contents of the new purebasic.prefs file based on your preferences as you had them set in the old version. This is easily done, since the files are really just text files with a unique extension.
I haven't taken time to figure out what the template.prefs file might be used for. This obviously relates to the Templates option under Tools, but I haven't stumbled onto a help section or example involving Templates with PureBasic yet.
version 3.94 without encountering some problems. However, I found that I could selectively add folders from 3.94 to the new purebasic folder, but it was a trial and error process. Once done though, I found that if I select everything in \purebasic\main, I can copy it into \purebasic, and retain the mix with each new version update.
If I paid attention to the contents of the original \purebasic\purebasic.prefs file, I could prevent an automatic overwrite from the new purebasic\main\purebasic.prefs file. You can do this by first selecting just the \purebasic\main\purebasic.prefs file, then picking Invert Selection (just below the Select All option in the Explorer Edit list of actions).
The risk is that in future versions, some of the controls in purebasic.prefs may change, creating an incompatability. So right now I think it would be
better to manually view and edit the contents of the new purebasic.prefs file based on your preferences as you had them set in the old version. This is easily done, since the files are really just text files with a unique extension.
I haven't taken time to figure out what the template.prefs file might be used for. This obviously relates to the Templates option under Tools, but I haven't stumbled onto a help section or example involving Templates with PureBasic yet.
has-been wanna-be (You may not agree with what I say, but it will make you think).
Hi oldefoxx,
Please don't do this (merge) for real! Even if you get something going now it may have a problem that causes you heartache in the future - and which may have those trying to provide future help/support for you tearing out their hair.
Suggestion: Keep the two distributions apart. With userlibs & residents, take only those that are created for (or -maybe- are known to work with) 4.00.
For code snips and etc (ie non-distribution and non-userlib/resident stuff) then, as you mentioned above, copy the files over. And convert as needed.
Please don't do this (merge) for real!
Even if you get something going now it may have a problem that causes you heartache in the future - and which may have those trying to provide future help/support for you tearing out their hair.Suggestion: Keep the two distributions apart. With userlibs & residents, take only those that are created for (or -maybe- are known to work with) 4.00.
For code snips and etc (ie non-distribution and non-userlib/resident stuff) then, as you mentioned above, copy the files over. And convert as needed.
@}--`--,-- A rose by any other name ..