Turning it off means you just have to try and be in control - same as all previous versions of Windows OS.  Means using some common sense - not much different than we've had to do under XP or before.

 

May not be the best thing to do from the security standpont but I disabled it as soon as I installed Vista (and Windows 2008).

 

There's a ton of articles on the controversy of turning it off or leaving it on.

 

My personal choice was to disable and take my chances making my best guess based upon the many years working with this stuff. It was just too annoying and I didn't want to kick the new computer - not yet, It's got to run my xmas show

UAC isn't exactly an anti-anything, it's more of a nanny to sit there and ask if you really want to do it.

I work with vendors that tell me that UAC, Antivirus, anti-spyware, and network backups are the reason that thier software doesn't work, and tell me to stop everything. I just ask them if they are going to support all of the security issues that arrise from the lack of protection and backups.

 

For my Vista 32 everything runs well enough. Sequencer asks me each time I start if that's what I wanted to do, and says that it crashed when I close the program. Other than that, it's just like XP, possibly a bit better.

 

You did do the Vista Patch AND THEN installed 1b? Right?

 

The following only applies to error 339: If the current version gives you a 339 error you can try to download the offending file name in the error message directly from Microsoft (don't get it anywhere else though... there are lots of fakes out there).  Do let me know what file name it complained about if it isn't one of the usual suspects (MSCOMM32, MSCOMCTL, MSCOMCT2).

 

5% of the "error 339" cases still exist on one file or another.  We are working on a "reg-free COM" version of Aurora.  While that doesn't mean a whole lot to non developers, it is actually quite cool... when we get it to work the program will not install any of the offending OCX files -AND- it will not even need to be installed at all (you could copy it to a thumb drive and it would run on any computer you attach the drive to without installation).  This will become the default distribution of Aurora once we get it working.

 

I'm probably in alot different situation than most based on experience and the resources I have at hand. Could end up writing a book why I've made the choice that I really don't need the UAC babysitting for myself. Don't feel threatened at all by "deadbolt on their screendoor disabled"

 

My Vista box is pretty much dedicated to Aurora along with just a few odds and ends that I might utilize in support of Aurora. I run AV software on all my nodes that the normal home user wouldn't have since my home network is also a test bed for support of a global network of over 500 servers and 10000 workstions and I also beta test for a major AV software vendor.  Not the normal home setup.

 

I wouldn't disable UAC without weighing the risk.

There's tons of tech articles indicating the pros and cons of disabling UAC.. Everyone has the oppertunity to evaluate the risk and make the choice based upon their own situation.

At least Microsoft gave us the option and freedom to choose.

Haven't tried it myself - but perhaps http://blogs.techrepublic.com.com/window-on-windows/?p=635 - http://blogs.techrepublic.com.com/window-on-windows/?p=635  will provide a starting point.

My guess is that the MSCOMM32 is just missing. I had to download it and place it in the correct location... and... and something else that I don't remember specifically.

http://www.afreeocx.com/ocx/info/mscomm32_ocx.html - http://www.afreeocx.com/ocx/info/mscomm32_ocx.html

It needs to be in the "C:\Windows\System32" directory.

 

Try to run the setup program again but right click and "Run As Administrator" (I think that even though I'm a domain admin, I still had to do that.

So cool! Another running install now.

 

Any other problems?

Just the annoying UAC pop up, asking me to allow, but that's not unique to Aurora. It's only a Vista nuance.