| Author |
 Topic  |
|
macke
Senior Member
Sweden
46 Posts |
 Posted - Dec 03 2006 : 11:37:33 PM
|
I searched the forum and discovered that several people have had issues with running VAX on Windows Vista. I too am one of them. Of course there is the "trying to write to places where I'm not allowed to write to"-bug regarding the VAX cache. But I'm having a few other issues, such as some features not working (sort of random it seems). Most notably the settings dialog isn't working. No matter if I run VS as administrator or regular user, no worky.
This obviously means that I can't change any settings comfortably and more importantly, I can't enter my license details. Can we expect Vista support soon? |
- Marcus Stade - |
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 04 2006 : 08:54:03 AM
|
Which IDE and version of VA are you using?
Which version of Vista are you using? Hopefully this will not matter, but it might.
Running Vista Buisness RTM here, with VS2005 professional and VA 1541, installed to the default location.
I ran the VA installer as Administrator, and I have run VS2005 as Administrator as well. I am not seeing any problems with the VA options dialog.
Using the VAssistX menu I can open the options dialog quite happily, changes I make are accepted and saved, and when I reload the IDE the changes are still there.
How are you trying to load the VA options dialog?
What, if anything, is happening? |
zen is the art of being at one with the two'ness |
 |
|
|
macke
Senior Member
Sweden
46 Posts |
Posted - Dec 04 2006 : 10:43:24 AM
|
quote:
Originally posted by feline
Which IDE and version of VA are you using?[/br]
VS2005 Team Edition for Developers, VA 1541 (default install location), Windows Vista Ultimate RTM.
Installer ran with admin priviligies, and I've tried running VS2005 with and without admin privs. Obviously it works best with admin privs, so that it can write the cache and what not, but it's not 100% as previously noted. I've tried opening the options dialog both from the VAX menu and the toolbar. Other than some controls (most notably the toolbars) flashing to gray and then rendered correctly again, nothing happens. |
- Marcus Stade - |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 04 2006 : 2:07:43 PM
|
I have not really looked at Vista myself, but VA is running and working for me, so there are no fundamental problems.
Is your primary drive C: or something else?
Is VA and the IDE installed to C: or some other drive?
Logically this must be some form of permissions problem, either with the file system or the registry. Can you download and run filemon:
http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx
and run it while you try to open the VA options dialog? Due to the amount of activity it reports I filtered it to only show me paths including "visual assist". Even then there was quite a bit of activity, but the key entries seem to relate to the two files:
C:\\Program Files\\Visual Assist X\\VATE.dll
C:\\Program Files\\Visual Assist X\\VAOpsWin.dll
can you see if you are getting errors trying to access these files please?
If this does not show anything then it may be a registry level problem, and regmon should help here:
http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/Regmon.mspx |
zen is the art of being at one with the two'ness |
|
|
|
dcaton
Junior Member
USA
17 Posts |
Posted - Dec 04 2006 : 4:08:14 PM
|
feline:
FYI, Filemon and RegMon have been superceeded with Process Monitor, which combines the functionality of both plus better filtering capabilities. There's a link on the home page of sysinternals.com.
I'm having the same problem as macke. Vista Ultimate RTM, VS 2005 Team Suite, VA 1541. Also installed the latest Platform SDK although that shouldn't make any difference. Running VS with admin privledges of course, and the VA directory has full permissions for all users. I also have the VS SDK installed, but that also should make no difference.
Alt+G just beeps and I can't open the VA options dialog via either the menu or toolbar. Attempting to do so creates an errors.log file in the VC8 subdirectory with this entry:
Exception: VAS::423 12/4/2006 15:52:03 0xfb0
I saved the log of file and registry access generated by procmon, but I don't see any way to attach a file to a reply. Let me know if you want me to email it to you. |
Don |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 05 2006 : 08:49:26 AM
|
To send us files can you please use:
http://www.wholetomato.com/support/contact.asp
referencing this thread in the description, so we can match it up.
macke can you look for the file "C:\\Program Files\\Visual Assist X\\vc8\\errors.log" on your system please?
You are both running the same OS and same version of the IDE, I am wondering if there is something about this IDE, or Vista Ultimate that is the problem.
I will look into this exception dcaton and see if it offers any clues, thank you for these details.
As for Process Monitor, I will have to look into that at some point  |
zen is the art of being at one with the two'ness |
|
|
|
dcaton
Junior Member
USA
17 Posts |
Posted - Dec 05 2006 : 10:00:35 AM
|
quote:
Originally posted by feline
To send us files can you please use:
http://www.wholetomato.com/support/contact.asp
referencing this thread in the description, so we can match it up.
macke can you look for the file "C:\\Program Files\\Visual Assist X\\vc8\\errors.log" on your system please?
You are both running the same OS and same version of the IDE, I am wondering if there is something about this IDE, or Vista Ultimate that is the problem.
I will look into this exception dcaton and see if it offers any clues, thank you for these details.
As for Process Monitor, I will have to look into that at some point
I don't know what's different between all the different versions of Vista. I've been running Vista for a week or so and it seems snappier than XP, but I haven't discovered what's "ultimate" about this particular version yet (maybe if it had an interface to my coffee machine...).
The OS is the same, but I'm running VS Team Suite and macke is running VS Team Edition for Developers. You never know, but I doubt that's significant though. The core IDE is the same for all versions of VS, and also for other MS products like SQL Server 2005, the CLR debugger, MS Document Explorer, the VS Macro IDE and for 3rd parties that are licensed to distribute the "premier partner edition" of VS. Only the installed packages are different.
Let me know if there's anything else I can try or help you with. |
Don |
|
|
|
macke
Senior Member
Sweden
46 Posts |
Posted - Dec 05 2006 : 10:24:49 AM
|
My error log contains the following:
Exception: VAS::423 12/5/2006 16:15:43 0x47c
Exception: VAS::423 12/5/2006 16:15:43 0x47c
I have yet to check things with FileMon. I'll try to make time for that later on tonight. |
- Marcus Stade - |
|
|
|
macke
Senior Member
Sweden
46 Posts |
Posted - Dec 05 2006 : 11:15:21 AM
|
Adding salt to the wounds:
It seems as though only the suggestion box works (the one with the question marks). Regular intellisense requires invoking via ctrl+space. This used to be invoked, probably VAX version, by simply pressing spacebar in most situations. Example:
VB.NET
Select Case <-- This space used to invoke regular intellisense |
- Marcus Stade - |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 05 2006 : 12:10:16 PM
|
dcaton I have the trace and log files, thank you for that. On an initial scan nothing really leaps out at me as bad, but I did notice someone looking for a manifest file, and not finding one.
The immediate problem is that VA seems to have successfully accessed the options dialog dll. I am off to check out this error log, but as a quick test, are both of you running the new Aero interface? Since I am running Vista inside a VMWare machine I do not have access to Aero, and to be honest I am not that interested in it
However I have seen manifest files uses to turn on the XP styles in winXP, so can either of you try changing your display settings to classic and see if it makes a difference?
Apparently I am using the "Windows Vista" theme here, but I am not sure if Aero is supposed to show up in the pick list if it is available on your graphics card.
macke can I get back to you on this listbox problem, once we have the options dialog working? They might have a common cause. |
zen is the art of being at one with the two'ness |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 05 2006 : 1:00:03 PM
|
The error log line is not that helpful on its own. Can someone please try the following test:
Make sure all IDE's are closed.
Run regedit and set the value:
HKEY_CURRENT_USER \\ Software \\ Whole Tomato \\ Logging = 1
then load the IDE, try to load the VA options dialog, and then close the IDE. The registry key tells VA to generate a log file. This key should be set back to zero after the IDE has closed, but you might want to check this actually worked, given the odd problems going on here.
Can you then send the two files:
c:\\va.log
c:\\Program Files\\Visual Assist X\\Startup.log
via the form:
http://www.wholetomato.com/support/contact.asp
dcaton you can simply reply to the email from our bug tracking system if that is easier with these files attached.
Hopefully there is enough logging in the options dialog to help. |
zen is the art of being at one with the two'ness |
|
|
|
dcaton
Junior Member
USA
17 Posts |
Posted - Dec 05 2006 : 4:07:33 PM
|
quote:
Originally posted by feline
dcaton I have the trace and log files, thank you for that. On an initial scan nothing really leaps out at me as bad, but I did notice someone looking for a manifest file, and not finding one.
The immediate problem is that VA seems to have successfully accessed the options dialog dll. I am off to check out this error log, but as a quick test, are both of you running the new Aero interface? Since I am running Vista inside a VMWare machine I do not have access to Aero, and to be honest I am not that interested in it
However I have seen manifest files uses to turn on the XP styles in winXP, so can either of you try changing your display settings to classic and see if it makes a difference?
Apparently I am using the "Windows Vista" theme here, but I am not sure if Aero is supposed to show up in the pick list if it is available on your graphics card.
macke can I get back to you on this listbox problem, once we have the options dialog working? They might have a common cause.
Yes, I'm running the Aero interface. It's a matter of personal taste of course, but I think it's more visually appealing than the XP interface. These things are mostly fluff though, I doubt anyone is going to become more productive with Aero than any other interface scheme.
In any case, turning it off makes no difference. It's probably a permissions or security issue. VA really needs to store its information in the application data folder, not in the installation directory. It ought to be a very simple thing to fix though, I had to do it in some of my own software and it only took a few minutes.
I just uploaded the log files you requested. |
Don |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 06 2006 : 08:37:59 AM
|
Storing our files in a different directory is on our list of things to do:
case=169
I stopped thinking anything was a "quick and easy" fix in VA some time ago
I have the log files, thank you for this. Hopefully they will help. |
zen is the art of being at one with the two'ness |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 06 2006 : 12:22:54 PM
|
I have asked one of the developers to have a look at this
case=3973 |
zen is the art of being at one with the two'ness |
|
|
|
dwulff
New Member
4 Posts |
Posted - Dec 06 2006 : 6:39:07 PM
|
Just to throw my hat in on this one: I am experiencing the exact same problem. Trying to open the VAX options dialog does nothing. I guess therefore it is running as a trial version and will expire in a few weeks? Is there another way I can enter the license information to prevent it expiring?
Vista Ultimate RTM (x64 version)
VAX 10.3.1541.0 (downloaded about an hour ago)
VS 2005 Team Developer Edition
VSTS Team Explorer is the only other addon installed
Do you have any leads on what is or could be causing this problem?
Let me know if you would like me to turn on logging and send in my log files too. With a cursory glance it looks like VAX is writing to its cache files ok, and doesn't appear to be limited by security settings. I don't want to open a new support ticket if this is something you are already tracking. |
Edited by - dwulff on Dec 06 2006 6:41:42 PM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 07 2006 : 10:23:54 AM
|
dcaton and macke, are either of you running the x64 version of Vista, or are you both using the 32 bit version?
I believe that there are various differences between the 32bit and 64bit versions of Vista. So far none of us can reproduce this problem, but so far none of us have tested on a 64bit version of Vista. |
zen is the art of being at one with the two'ness |
|
|
|
dwulff
New Member
4 Posts |
Posted - Dec 07 2006 : 10:25:31 AM
|
| (For the record, I have been using VAX with XP x64 and the same VS configuration as above for 12-18 months with no issue.) |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 07 2006 : 10:28:24 AM
|
dwulff did you upgrade your machine to Vista, or did you do a clean install?
In an ideal world this should not matter, but I am searching for any common element here that might give us another clue. |
zen is the art of being at one with the two'ness |
|
|
|
dwulff
New Member
4 Posts |
Posted - Dec 07 2006 : 10:30:28 AM
|
| It is a clean install on a new machine. AFAIK you cannot upgrade to the 64 bit version of Vista, only the 32 bit version. |
|
|
|
dcaton
Junior Member
USA
17 Posts |
Posted - Dec 07 2006 : 10:38:15 AM
|
quote:
Originally posted by feline
dcaton and macke, are either of you running the x64 version of Vista, or are you both using the 32 bit version?
I believe that there are various differences between the 32bit and 64bit versions of Vista. So far none of us can reproduce this problem, but so far none of us have tested on a 64bit version of Vista.
32 bit. Vista 64-bit won't run unsigned device drivers, and I just figured that getting 64-bit signed device drivers for the things my system needs would be an exercise in futility.
I also have SQL Server 2007 installed, which uses the core VS components, so you might try installing that and see if it makes any difference. I also have the VS SDK (November '06 release) installed, which may or may not be significant.
And I have the latest Platform SDK for Vista installed. That changes some of the default include directories in VS (if you run VCIntegrate.exe in \\Microsoft SDKs\\Windows\\v6.0\\Setup). Shouldn't make any difference either, but you never know...
Aside from that, I don't think there's anything particularly unusual about my system. Do you have a debugging version of VA that I could run that would give you more information? |
Don |
|
|
|
dcaton
Junior Member
USA
17 Posts |
Posted - Dec 07 2006 : 10:40:07 AM
|
quote:
Originally posted by feline
dcaton and macke, are either of you running the x64 version of Vista, or are you both using the 32 bit version?
I believe that there are various differences between the 32bit and 64bit versions of Vista. So far none of us can reproduce this problem, but so far none of us have tested on a 64bit version of Vista.
Forgot to mention, this was a clean install of Vista, not an upgrade.
Also, I didn't install the sp beta for VS 2005 on this machine (yet). |
Don |
|
|
|
dwulff
New Member
4 Posts |
Posted - Dec 07 2006 : 11:10:53 AM
|
| To add to Don's information, I too have SQL Server 2005 installed on the same machine with the SQL Server Management Studio, with SP1 applied. I have not installed any other updates, service packs, SDKs, or beta software at this time. |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Dec 07 2006 : 9:30:21 PM
|
For all users which experience this problem:
Do you have a value named "Color:0" at HKEY_CURRENT_USER\\Software\\Whole Tomato\\Visual Assist X\\VAOpsWin\\Custom Colors ?
If so, what is the value?
|
|
|
|
dcaton
Junior Member
USA
17 Posts |
Posted - Dec 07 2006 : 10:27:22 PM
|
quote:
Originally posted by sean
For all users which experience this problem:
Do you have a value named "Color:0" at HKEY_CURRENT_USER\\Software\\Whole Tomato\\Visual Assist X\\VAOpsWin\\Custom Colors ?
If so, what is the value?
That's the problem! There are no values for the Custom Colors key at all, and the 'LastPage' value under VSOpsWin isn't there either.
I copied these keys from the VA installation on my laptop (which is still running XP) and now the options dialog works.
Apparently, whatever sets the default reg values for those keys isn't working.
FWIW, all he values under the VANet8 key are ok (as compared with my laptop), and that key has the same permissions level as the VAOpsWin key. |
Don |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Dec 07 2006 : 11:20:06 PM
|
| Thanks for the confirmation. We've now reproduced the problem in house and have a fix which will be in the next build. |
|
|
|
alvint
Starting Member
USA
1 Posts |
Posted - Dec 08 2006 : 2:12:09 PM
|
| Is there an ETA on this new build? |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Dec 08 2006 : 3:18:30 PM
|
| Some time next week hopefully. For now can you try creating the registry keys manually, or email me via the forum so that I can email you a dll with the fix in it? |
zen is the art of being at one with the two'ness |
|
|
|
macke
Senior Member
Sweden
46 Posts |
Posted - Dec 08 2006 : 9:00:33 PM
|
Great to hear about the progress! I've sent you files from ProcMon but I guess those are useless now. I won't spam your inbox with the other files you requested unless you ask for them.
Unlike dcaton, I don't have a second VA installation anywhere, so I could definatly benefit from either a reg-file which adds these keys to the registry or an early fix build (preferrably the former as I guess I won't have much to gain from getting the fix now or some time next week).
If anyone would like to share all these "default value" keys I'd be most grateful! |
- Marcus Stade - |
|
|
|
dcaton
Junior Member
USA
17 Posts |
Posted - Dec 08 2006 : 9:07:26 PM
|
quote:
Originally posted by macke
[If anyone would like to share all these "default value" keys I'd be most grateful!
This should get your options dialog working again:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\\Software\\Whole Tomato\\Visual Assist X\\VAOpsWin]
"LastPage"=dword:0000000b
[HKEY_CURRENT_USER\\Software\\Whole Tomato\\Visual Assist X\\VAOpsWin\\Custom Colors]
"Color:0"=hex:ff,ff,ff,00
"Color:1"=hex:ff,ff,ff,00
"Color:2"=hex:ff,ff,ff,00
"Color:3"=hex:ff,ff,ff,00
"Color:4"=hex:ff,ff,ff,00
"Color:5"=hex:ff,ff,ff,00
"Color:6"=hex:ff,ff,ff,00
"Color:7"=hex:ff,ff,ff,00
"Color:8"=hex:ff,ff,ff,00
"Color:9"=hex:ff,ff,ff,00
"Color:10"=hex:ff,ff,ff,00
"Color:11"=hex:ff,ff,ff,00
"Color:12"=hex:ff,ff,ff,00
"Color:13"=hex:ff,ff,ff,00
"Color:14"=hex:ff,ff,ff,00
"Color:15"=hex:ff,ff,ff,00
|
Don |
|
|
|
macke
Senior Member
Sweden
46 Posts |
Posted - Dec 08 2006 : 10:21:26 PM
|
It works, thanks a lot Don!
I've yet to report wether this fixes the other issues mentioned. However, this is certainly a flying start!
EDIT: Suggestion box seems to be working as expected again (awesome). Will do further testing tomorrow. |
- Marcus Stade - |
Edited by - macke on Dec 08 2006 10:26:16 PM |
|
|
|
macke
Senior Member
Sweden
46 Posts |
Posted - Dec 11 2006 : 08:24:04 AM
|
Suggestion box stopped working again. I don't know what changed since the last time I ran the IDE, but today the box just stopped working. It's been like this all day, so it never worked initially and then just gave up. What happens is that the suggestion box appears, but as soon as you type something (to shrink it) it disappears. The default intellisense box that appears when VAX is disabled works as expected.
Options in the VAX options dialog doesn't seem to make any difference to the suggestion box. Setting it to not appear doesn't matter, it still shows. I've not tried the updated build of VAOpsWin.dll yet, which I guess might resolve at least part of this (correctly reading/writing registry keys). I'll report back with more information as I have it.
One thing I noticed is that VAX more or less always shows this message in the status bar:
"VA X: Waiting for other instance of Visual Studio to flush DB..."
This seems to be regardless of wether I actually have another instance of VS running or not. |
- Marcus Stade - |
|
|
|
Topic |
|
Vista RTM issues
