While Excalibur pretty much works with Vista, there seem to be
instances where (new) odd things happen. I am beginning to suspect
that my decision to locate the client program in c:\program files
\excalibur when I created the first custom client installer (as a
workaround for the problems we were having with the original
excaltrm.exe and XP) may not have been a good idea.
I caught on to this when I tried to copy my dialing directory into a
new installation of Excalibur. It just wouldn't recognize the new directry.exc file. I also noticed the bbs cache directories were not
showing up in c:\program files\excalibur\ either. This really had me
going for awhile.
After some hard drive searching, I found that the cache directories
and the directry.exc file being used were actually living in a hidden C:\Users\<your_account>\AppData\Local\VirtualStore\Program Files
\Excalibur\ directory.
It turns out that Vista has a new security feature which can prohibit
legacy apps from writing to certain system areas, such as the Program
Files directory. Instead, Vista creates a VirtualStore folder where
data can safely be written and accessed, pretty much transparently to
the app. A more detailed account of this process can be found at http://zone.ni.com/devzone/cda/tut/p/id/5538 (specifically see "File
System and Registry Virtualization").
I'm still not really sure if this is the root cause of the latest
glitches or not. However, I decided to redo the custom installers so
that they used C:\Excal again, hopefully avoiding any issues that
might be the result of the above. You can download the new installers
at http://www.tecmecca.net. Of course, if you are running a host
machine I would still advise against having the client installed in
the same directory as the host. Just install into any other non system directory, such as c:\xcaltrm or the like.
Dave - TecMecca
Good info,
I will check this out....
Chris - Insight Media BBS
<excal...@gmail.com> wrote in message
news:9892b038-4d2e-4ad0-abdb-0c1331020c1e@y5g2000hsf.googlegroups.com...
While Excalibur pretty much works with Vista, there seem to be
instances where (new) odd things happen. I am beginning to suspect
that my decision to locate the client program in c:\program files \excalibur when I created the first custom client installer (as a workaround for the problems we were having with the original
excaltrm.exe and XP) may not have been a good idea.
I caught on to this when I tried to copy my dialing directory into a
new installation of Excalibur. It just wouldn't recognize the new directry.exc file. I also noticed the bbs cache directories were not showing up in c:\program files\excalibur\ either. This really had me
going for awhile.
After some hard drive searching, I found that the cache directories
and the directry.exc file being used were actually living in a hidden C:\Users\<your_account>\AppData\Local\VirtualStore\Program Files \Excalibur\ directory.
It turns out that Vista has a new security feature which can prohibit legacy apps from writing to certain system areas, such as the Program
Files directory. Instead, Vista creates a VirtualStore folder where
data can safely be written and accessed, pretty much transparently to
the app. A more detailed account of this process can be found at
http://zone.ni.com/devzone/cda/tut/p/id/5538(specifically see "File
System and Registry Virtualization").
I'm still not really sure if this is the root cause of the latest
glitches or not. However, I decided to redo the custom installers so
that they used C:\Excal again, hopefully avoiding any issues that
might be the result of the above. You can download the new installers athttp://www.tecmecca.net. Of course, if you are running a host
machine I would still advise against having the client installed in
the same directory as the host. Just install into any other non system directory, such as c:\xcaltrm or the like.
Dave - TecMecca- Hide quoted text -
- Show quoted text -
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 374 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 116:35:16 |
| Calls: | 7,951 |
| Calls today: | 2 |
| Files: | 13,008 |
| Messages: | 5,811,697 |