VSpec issue

[Keith Graham]

Hi,

I recently installed Vspec on a new Windows 7 computer. When I click the BeSS check button on the bottom of the right hand column, I get a Runtime Erroe 75 that states the path/file access error. I copied the same settings from the Vspec program on my XP computer, but I probably missed something. Can someone please point me in the right direction to fix this?

Thanks,

Keith Graham

[Ken Harrison]

Keith,
I'm running VSpec 4.1.4 on a Win7 64 laptop....no issues...
Did you install as "Administrator"???

[Keith Graham]

Hi Ken,

Thanks for the reply.

When the box came up to install as Administrator, I clicked Continue. The only other options were Skip and Cancel, so I figured Continue was the correct choice.

I did reinstall the program but still be the runtime error 75.

Keith

[Ken Harrison]

Keith,
Other than the BeSS issue, is the rest of the program working OK for you?

[Keith Graham]

Yes, all else works fine.

I did find that if I open the BeSS Query in Assistant I get the same message when I click on the Query button.

This works perfect on my XP computer. I do know that the Windows 7 computer will not let the XP computer access the C drive - something about not having permissions. (I have been tearing out my hair on this for a few days now) And when I attempt to download images from my observatory XP computer, the 7 computer will not let the images come through the C drive. So I am wondering if BeSS is attempting to run the query through the C drive. If so, this may be the problem.

Cheers,

Keith

[Keith Graham]

I found a "work around" solution to my issue. I have been having that problem with the C drive on my new Windows 7 computer where it simply refuses to allow access permissions. I figured that Vspec was trying to communicate with BeSS, and when BeSS sent back the information for the telluric check, my C drive refused to let it in. I learned that the User file is a bit more permissive, so I installed VSpec in that folder and Voilla, it worked.

So the issue was (is) with my new computer. I am trying to get this resolved with Dell and hopefully will have some luck with a resolution in the near future.

Cheers,

Keith

[Ken Harrison]

Keith,
Glad you managed to achieve some success.
If and when you get a final resolution, I'd love to hear the result.

[Valerie Desnoux]

Keith,
Very interessing and important finding there.
Yes, querying beSS with an object name BeSS will return an xml file (extension .pl), stored in the BeSS_VO directory in Vspec main directory. Vspec parses it and load the list from where you can either upload all or individual spectrum of the object.
I moved recently to a new computer with Win8 and I also had issues, coming from the Windows xml parsing dll which has evolved. I'm on 64 bits as well. The good news is that I was able to re-install and compile the code of Vspec. I'm testing a new upgrade.
Hope will be available in 2 to 3 weeks.
Valerie

[Keith Graham]

Hi Valerie,

Have you had any luck with your new upgrade? I mentioned previously that I found a "cure" for the BeSS issue, but I now have another issue with another Windows 7 computer (exactly the same make, model, and OS as the first). I can get the program booted and I can select a profile from the working directory. That profile will appear in the blue box, but when I click OK, I get the dreaded "Run time error 75 Path/file error" message.

I tried using vesrions 3.88, 4.14. and 4.22 all with the same results. Now, this is with Vspec installed in the Users folder as I did with the first computer. If I install Vspec in the Program Files (86) folder, the profile will appear in the next screen after I click OK. However, I will get the run time error if I try to access BeSS.

I have tried compatibility with Windows XP SP3 and Windows 7, both with the same results. What I am so puzzled about is why it will work on one computer but not on another identical computer.

XP was soooo nice with none of these issues.

Cheers,

Keith

[Keith Graham]

Hello Again,

Well, I got around this glitch and will pass on what I found. Unfortunately I cannot go into detail because dumb me simply did not record what I did as I was doing it. I then got distracted on another project and when I came back to this one, the procedure had escaped my memory banks.

However, all is not lost. I think the problems line within the Properties/Security/Advanced tabs. WIthin the Advanced tab are the Permissions and Owner tabs. I THINK I did something to grant Full Control for each Name. Only problem is that now, although Full Control is shown I can not change any of them as they are all greyed out. Of course I do not want to change them even if I could because the program now works. Only issue is that it is installed in the User folder, not the Program(86) folder. But I do not care about that because Vspec now works as it should.

I do not know why MS has to make things so darned difficult. With XP, I simply installed the program and was up and running in minutes. With 7 they just may have become too paranoid about security.

Cheers,

Keith