Tweet
3.2 to 4.2 upgrade problem (suprise)
Hi, first post (and it's a goodun).
Knowing we were about to purchase a new SMA and upgrade from 3.2063MR2 to 4.2 soon (a corperate decision) I have been lurking here for a while.
When the hasp upgrade was done and the CD's were in my hands I went for it using the instructions provided by that nice Mr Hoedeman.
I thought all went well until at about 95% it stopped displaying an error saying that it could not find 'xxxx file from V3.5'.
No choice to abort or quit, just an OK button.
This occured several times before intallation was complete.
To my knowlege no attempt to intall V3.5 was ever made BUT on investigation I discovered somone from Hexagon had done this years ago.
On first run it gave a choice of probes from a drop down, where is the probe rack?
Our install of 3.2 appears to be intact.
How do I complete this install without compomising our working 3.2?
Would an uninstall of 4.2 work and not touch 3.2?
If so would a thourough trawl through the registry removing all references to 3.5 allow a succesful intal of 4.2?
Or do I call Hexagon and demand somone to come up and clean this mess.
Knowing we were about to purchase a new SMA and upgrade from 3.2063MR2 to 4.2 soon (a corperate decision) I have been lurking here for a while.
When the hasp upgrade was done and the CD's were in my hands I went for it using the instructions provided by that nice Mr Hoedeman.
I thought all went well until at about 95% it stopped displaying an error saying that it could not find 'xxxx file from V3.5'.
No choice to abort or quit, just an OK button.
This occured several times before intallation was complete.
To my knowlege no attempt to intall V3.5 was ever made BUT on investigation I discovered somone from Hexagon had done this years ago.
On first run it gave a choice of probes from a drop down, where is the probe rack?
Our install of 3.2 appears to be intact.
How do I complete this install without compomising our working 3.2?
Would an uninstall of 4.2 work and not touch 3.2?
If so would a thourough trawl through the registry removing all references to 3.5 allow a succesful intal of 4.2?
Or do I call Hexagon and demand somone to come up and clean this mess.
Sorry buddy.
Comment