Upgrading from AREV 2.03 to 3.12 (AREV Specific)
At 24 AUG 1999 12:58:34PM Dale Walker wrote:
When I tried the upgrade, I was not able to access my data. I know that AREV is supposed to make a copy of the previous version. But it just didn't happen. I followed the instructions in the installation manual. It looked like something was happening.
For what its worth I'm running Windows 98 on a pentium 233.
This not like updating AREV 2.12.
Help!!
Dale
At 24 AUG 1999 04:02PM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
Can you go into a little more detail? Can you enter the system? Are there error messages? Are there any messages? Was this an upgrade or a trade-up?
Also, ARev doesn't make a copy of anything when doing an upgrade. That's why it prompts you to remind you to do a backup.
At 24 AUG 1999 04:42PM Dale Walker wrote:
It is a tradeup. Tradeups differ from upgrades. According to the documentation, it is supposed to create a new directory and such. and yes, I did make a backup. There were no error messages.
I appreciate your help
Dale
At 24 AUG 1999 08:59PM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
I'm not sure exactly what you did, so I'll just explain a few things about trade-ups. A trade-up installs a fresh ARev system and reads in the EXE information from the old system and transfers it over. This gives you a new system with your old user count and serial number.
After creating this system, you have to move the original system over. This means creating a new application and copying all your windows, programs, menus over, upgrading them, and then attaching your data.
If you haven't done any of this, then it won't work. If you have, the system should give some sort of error message.
Can you log into SYSPROG? How about your application? If you can make it into your application, are your windows and menus there? If not, can you still see the old application? What happens if you SETFILE in the originals and copy them over? What happens if you attach the older data files?
Watch out when you attach in the old system. If you somehow attach over the VOC or SYSOBJ file, it could cause problems. The system shouldn't let you do this, but some quick attach programs can.
At 24 AUG 1999 11:36PM Dale Walker wrote:
A couple of points I am not clear on.
First, All my data is in the old DATAVOL volume. I am running a single user version of AREV. I went through the upgrade process from REV g to AREV1.0 and eventually 2.03. During the tradeup process to 3.12 there was a second directory created off of the root of C: for 3.12 complete with datavol.
I guess my question is: do I attach the old DATAVOL under an alias and copy the files to the new DATAVOL. I really dont want to create an 'application' under anything but SYSPROG since I am the only one using it.
I appreciate the help.
Dale
At 25 AUG 1999 09:18AM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
DATAVOL is an empty subdirectory created as a default directory for you to store your data. If it were me, I'd just copy the stuff from the old DATAVOL to the new DATAVOL. This way, there's a better back-up and you can make all the required field changes without having to worry about it affecting the old one.
At 25 AUG 1999 12:00PM Dale Walker wrote:
Question:
If I just copied the directory from file manager from arev\datavol to the newarev\datavol with a replace option, would it mess things up? I was wondering how revmedia would affect this. And would it affect anything in REVBOOT? or would it not work at all? Or would it be best to create a new volume called (for lack of a better term) TEMP and copy the files there and then attach temp from 3.12 and copy to datavol?
Would it be best to create a menus_old file in datavol and copy the data in menus to menus_old, also the same with templates, etc.?
Thanks,
Dale
At 25 AUG 1999 02:28PM Ed mantz wrote:
I am with Aaron. The easiest thing to do it simply copy the old datvol to the new datvol location provided (make sure your are copying and not moving as you want to leave your old system intact):
1. the only files in the new datavol directory is REVMEDIA.LK & REVMEDIA.OV (which is should be because this is a new install)
and
2. You are pretty sure you will not need to attach the old datavol (by setting an alias to it) WHILE the new datavol is attached. The reason for this is that AREV "names" each volume (or the programmer does) when the volume is creatde. The "name" fo the volume is part of the data stored int he REVMEDIA for that volume. Therefore the new datavol will have the same "name" as the old datavol because revmedia has been copied. AREV will not let u attach two volumes with the same "name".
But since u are really planning to use the new system and I don't see that as a problem and there are ways around the nameing issue anyway.
At 25 AUG 1999 03:28PM Dale Walker wrote:
I appreciate your insights. I somehow feel that I need to copy the menus and templates to an "_old"file in datavol (old) so that I can copy the "rows" to their appropriate tables.
Dale
At 25 AUG 1999 05:58PM Warren wrote:
Isn't there a migration/converion process that has to be run to change from the '.' naming conventions to '_' in dictionary, file names etc? And aren't many of the verb names and system subroutine named differently between 2.03 and 3.12? Does the trade-up have the old 1.x & 2.x names for backwards compatibility?
At 25 AUG 1999 08:46PM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
Well, the way I'd do it is keep the old information in the old datavol and the new information in the new datavol. Since datavol is an empty directory in 3.12, you should be able to just copy it over. Then, rename MENUS to MENUS_OLD and so forth. TEMPLATES you can leave as is, since it's called WINDOWS in 3.12. This way, you have all the old stuff really backed up, and you also have some extra copies so easily available. Don't forget you'll need to do an upgrade on the files before they'll be ready for 3.12.
At 25 AUG 1999 08:58PM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
Yup. Only thing is the old command names aren't installed by default. There's an option during the upgrade application portion or you can run OLDSTUFF
At 26 AUG 1999 10:44AM Dale Walker wrote:
Thanks
Dale