SWV 6.1 upgrade - Bug or by design?
This issue has been solved. See solution.
vjuhasz
September 21st, 2009
Hello,
I just upgraded from SWV 6.1.4063 to 6.1.4113 by installing the new version over the old one.
- I am running XP SP3.
- My Windows system drive is D:\
- My original datastore before the upgrade was E:\fslrdr
I would have have expected SWV to detect my main datastore on E:\ and keep that after the upgrade.
Instead, for some reason SVW created a new datastore on D:\ and put ALL subsequent layers into that (D:\fslrdr) after the upgrade. The older layers created before the upgrade were kept on E:\, so my system now is running some layers from D:\ and some others from E:\
Is this datastore creation behavior by design or it is a bug? Shouldn't the original datastore on E:\ have been kept intact without messing with the D drive?
Thank you,
Val
I'd say it was a bug, or maybe not
I can see no logical reason for an "upgrade" to be written in a way which ignores previous installation configuration - always assuming, that is, that the location of the fslrdr folder is actually configurable at install time and not the result of a subsequent registry hack.
It's a while since I did an SVS install but the versions I used did not offer an option to configure a datastore anywhere other than on the system drive, and any changes needed a registry hack after install.
So it all depends on whether the author of the installer actually wrote it to preserve any existing settings, or just to check if the default environment is present, and create it if it isn't.
Bottom line is that I would expect any upgrade to preserve installation settings that are configurable at install time, but any hacks after install are outside the scope of the update and it is up to you to handle this.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Seams like a bug to me. You
Seams like a bug to me.
You had HKEY_LOCAL_MACHINE\SYSTEM\Altiris\FSL->DefalutRegRedirect set to your wanted location correct? Which wasn't named FSLRDR but something else?
Just want to make sure so I can look into this.
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
This exists in MP1 but has
This exists in MP1 but has been fixed for SP1.
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
Thank you for all the
Thank you for all the replies.
Is the SP1 already available or when we can expect to be released?
Available
I believe it is already available, as there is an article by Jordan about how some of the changes introduced for Windows 7 support may make some utilities stop working, if they have hard coded locations to some of the resources used by SWV.
By the way, anyone know where the SP1 release can be downloaded from?
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
The customer Preview is out
The customer Preview is out but the final release isn't out yet. I released that article so those that had custom code or enviroments could begin checking to see if SP1 will break something.
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
Would you like to reply?
Login or Register to post your comment.