Installing SigmaStudio on a networked PC
With some networks, the users' My Documents folder is mapped to a network drive for backup purposes. This is supposed to be transparent to each user, but it may cause your SigmaStudio installation to fail. If you get a message like the one below, this may be the cause:
Here's a workaround:
Ask your network administrator to set up a local user account on your PC. Be sure it has local administrator privileges.
Make a new folder in the root of your C drive, such as C:\haha.
Copy your SigmaStudio install file to that folder.
Log off the network and on to your local machine account.
Run the SigmaStudio install from there. It should complete without error.
Open your local My Documents folder, find and copy the new Analog Devices folder with its contents to C:\haha.
Log back onto your network and move your Analog Devices folder from C:\haha to the mapped My Documents folder.
I've originally needed to use this workaround to install SigmaStudio 3.4. I didn't notice this issue with versions 3.5 up to Beta 3.74, but just now I had to use the workaround to install the release version 3.7. If you need it, hope it works for you.
Bob
install
3.7
my_documents
network
3.4
Hi Bob,
We re-introduced the requirement that you be an admin to run the installer in 3.7 release. This is because the installer package is now being generated by a more centralized software team in ADI so we can conform to their standard practices. We're checking with them at the moment if we can provide some better support for networked multi-user machines.
Thank you for posting this. The issue remains in SigmaStudio 3.9 and 3.10 beta. It was a minor inconvenience once the workaround was discovered, but certainly doesn't start thing off on the right foot for Analog Devices.
Hello cbrew,
Thank you for posting your update above, letting us all know that the issue remains. Network arrangements do vary from place to place, according to local policies. Where I work, I can't even get iTunes to install and function properly. Since SigmaStudio updates every few months, I found it easier to use my personal laptop for SigmaDSP development. This also affords battery operation to eliminate ground-loop hum during critical tests.
Best regards,
Bob
Hello cbrew,
I just successfully installed SigmaStudio 3.11 on my work machine with no need for the workaround. I don't know if ADI's installer and/or the network here is what changed, so I'm wondering if you have tried installing v. 3.11.
Bob
A footnote to this discussion: My friend researching a Microchip forum for why his programming module wasn't working turned up some very good advice: Computers dedicated to embedded programming and similar engineering activities often react badly to standard company IT practices. Therefore, work with your IT department to isolate these machines and allow you some autonomy to manage them.
Bob
I've run in to this problem on my local machine as well using v3.11, and clear back to v3.8 or so. The difference is I am using an SSD for my OS drive and My Docs is redirected to D: on my HDD data drive. I have found it easiest to physically unplug the 2nd HDD which forces Win7 to revert to its default location for User files. Once the install is complete, I can replug the HDD and Windows seems to remember my 2nd drive location. Then I just move my Sigma files to the new location and all is well.
If ADI expects the Sigma line to be around for a while, seems to me they should make this a more robust and transparent process by having a Software Update in the Help pull-down. Ideally, it would take into account these various scenarios brought up here.
Hello chuckwin,
Having a "check for updates" or similar feature is an excellent idea, perhaps ADI could find a way to implement it someday. SigmaStudio 3.xx has been around for as long as I've been using it (I started three years ago with version 3.3), so it's getting rather long in the tooth. I wonder what the development team has in store for SigmaStudio 4.0!
Best regards,
Bob
Hi Bob,
Yes it's nice that ADI has created this line of products for us old-school analog guys trying to survive in audio by becoming digital guys. I started on the Alesis 1kM about 15 years ago then migrated to the Sigma ADAU1446 back in 2008 with Sigma Studio v3.1. It has become an indispensable tool for us in creating pro and consumer products. Sigma Studio alone has saved countless hours of development time compared to the line-by-line methods of coding with early gen dsps like the 1kM. I can only imagine there are plenty of designers out there who feel the same. And the fact that there is now a SHARC for SigmaStudio indicates a trend that's here to stay.
Given all that, it would seem to me that ADI sees where this is all going and realizes they need to make the Sigma development environment more robust if they want to attract the next generation of designers. I'd imagine v4.0 will be very cool when deployed, but it's just a fact of life that it will be buggy. So providing an easier way to get updates would certainly cut down on their support calls and bolster their customers' experiences.
Best Reg
chuck
Please log in to reply.