|
Posted by Andrew DeFaria on August 12, 2006, 6:28 pm
Please log in for more thread options This is a multi-part message in MIME format.
--------------050306000808080204040500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Jerry Boyle wrote:
> Bert,
>
> Could you confirm whether or not the account you use has administrator
> privileges (Control Panel -> User Accounts then look for "Computer
> administrator" under the account name). If it does, that would
> definitely eliminate any update permission issues.
>
> I'm still not totally convinced that this isn't a Q2007 issue,
> especially after Bert's latest response. Has anyone who has Q2007
> running under Windows XP confirmed that they can turn off the qopen
> sound? If not, could we please have a guinea pig so that Q2007 can be
> conclusively eliminated as a suspect.
Sure. Send me a copy of Q2007 and I'll check it out for ya! ;-)
> There are also a couple of areas that I don't completely understand
> that no one has mentioned: sound schemes and registry locking. Either
> might explain why only Quicken sounds are affected.
>
> (1) Windows has sound schemes. I run with a single user account with
> administrator privileges and I have 3 sound schemes under the Sounds
> tab of the Sounds and Audio Properties form: an unnamed scheme (my
> active scheme -
> the only one I ever use), another named No Sounds, and one named
> Windows Default. When I bring up this form the Sound Scheme field is
> selected and it's quite easy to inadvertently change the scheme,
> especially with a wheel mouse. I'm not sure what effect it has on
> Quicken if you change the sound scheme (especially between
> installation of two Quicken releases).
>
> My account named "Administrator", which I seldom use, has only the No
> Sounds and Windows Default sound schemes, the latter of which is
> active. Neither has any Quicken sound entries. So it's my guess that
> Quicken installs its sound entries under the currently active sound
> scheme of the account that does the Quicken installation. Even if you
> installed Q2007 and a prior release under different sound schemes that
> shouldn't cause your problem unless there are quirks in Control Panel
> or Q2007. Both probably should just use the current sound scheme.
This is because Sound Schemes are a per-user setting thus stored under
HKEY_USERS not HKEY_LOCAL_MACHINE.
> A big assumption above is that Q2007 behaves like prior releases,
> which it may not! You really need to browse your registry and confirm
> that you have only the qopen.wav entries shown in Andrew's program.
Technical nit: It's a reg file - not a program.
> [You can safely ignore any Most-Recently-Used list entries (look for
> "MRU" or "mrulist" in the entry)]. If you find any additional entries
> this is a likely source of your problem.
>
> (2) Locking of registry entries. I know nothing about how Windows
> locks and unlocks its registry entries.
It doesn't. Registry entries have ACL (Access Control Lists) much like
the security settings for files. And ACL isn't a lock as per se - it's a
permissions thing...
> But I do know that locks on Windows files are sometimes not released
> properly even if the process that used the file
> terminates.
This is a totally different thing. Programs can lock files but they
cannot lock ACL entries. Registry entries can't be locked but their
permissions could be set such that the current user cannot modify them.
Also, when a program locks a file and another program attempts to gain
access to it and lock it it is put into a wait queue until the first
program releases the lock. Bert did not report that he attempted to
change the sound and got suspended...
> The symptom is that you can't delete the file. Sometimes a simple
> reboot lets you delete it, sometimes a Safe Mode reboot works, and
> sometimes you have to boot in command prompt mode.
You can't delete the file because the OS imposes a restriction that you
cannot remove a file that somebody else has currently open. Windows does
this. Unix, OTOH, doesn't. BTW, you need not go to extremes and reboot
or reboot into safe mode to fix this problem. You can use Sysinternals
Process Explorer to find the process that has the file opened and either
forcefully close that file or kill that process.
> Have you tried turning off one of the other Quicken sounds? If you can
> do this successfully it begins to look like a locked, corrupted or
> possibly a duplicate entry for your qopen sound.
>
> If you have a registry locking issue Andrew's program will probably
> bypass the lock.
Again, it's not a program - it's a reg file. It doesn't run anything nor
is it code. And it will not bypass any lock (especially since there is
no lock to be locked). It will equally fail to apply if the current user
does not have permissions to modify that registry entry. Hopefully it
would report an error.
> If that doesn't work Control Panel and/or Andrew's program might work
> if you boot in Safe Mode.
You're grasping at straws.
> As a last resort you can boot into Safe Mode with Command Prompt mode
> and type "regedit" to edit the registry directly. To exit this mode
> type "exit", then Ctrl-Alt-Delete and select Shutdown.
I highly doubt any of this is necessary.
> Before you use Andrew's program or try to edit the registry you should
> probably browse it to see what qopen.wav entries you have. Post back
> if you want to do this and need help with it.
>
> Based on my limited knowledge of Windows and Quicken, access
> permissions, sound schemes, registry locking, corrupted or duplicate
> registry entries and anomalies in Q2007 are the only things that can
> cause your problem. There may be other possibilities that people in
> one of the Windows NGs might be aware of.
Well you are correct WRT limited knowledge... However the "trick" of
renaming the file surely would work as how can even Quicken play a sound
from a file it cannot find?
--
Andrew DeFaria <http://defaria.com>
C:DOS C:DOSRUN RUNDOSRUN
--------------050306000808080204040500
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Jerry Boyle wrote:
<blockquote
cite="midEEmDg.598450$Fs1.148548@bgtnsc05-news.ops.worldnet.att.net"
type="cite">Bert,<br>
<br>
Could you confirm whether or not the account you use has administrator
privileges (Control Panel -> User Accounts then look for "Computer
administrator" under the account name). If it does, that would
definitely eliminate any update permission issues.<br>
<br>
I'm still not totally convinced that this isn't a Q2007 issue,
especially after Bert's latest response. Has anyone who has Q2007
running under Windows XP confirmed that they can turn off the qopen
sound? If not, could we please have a guinea pig so that Q2007 can be
conclusively eliminated as a suspect.<br>
</blockquote>
Sure. Send me a copy of Q2007 and I'll check it out for ya! <span
class="moz-smiley-s3"><span> ;-) </span></span><br>
<blockquote
cite="midEEmDg.598450$Fs1.148548@bgtnsc05-news.ops.worldnet.att.net"
type="cite">There are also a couple of areas that I don't completely
understand that no one has mentioned: sound schemes and registry
locking. Either might explain why only Quicken sounds are affected.<br>
<br>
(1) Windows has sound schemes. I run with a single user account with
administrator privileges and I have 3 sound schemes under the Sounds
tab of the Sounds and Audio Properties form: an unnamed scheme (my
active scheme -<br>
the only one I ever use), another named No Sounds, and one named
Windows Default. When I bring up this form the Sound Scheme field is
selected and it's quite easy to inadvertently change the scheme,
especially with a wheel mouse. I'm not sure what effect it has on
Quicken if you change the sound scheme (especially between installation
of two Quicken releases).<br>
<br>
My account named "Administrator", which I seldom use, has only the No
Sounds and Windows Default sound schemes, the latter of which is
active. Neither has any Quicken sound entries. So it's my guess that
Quicken installs its sound entries under the currently active sound
scheme of the account that does the Quicken installation. Even if you
installed Q2007 and a prior release under different sound schemes that
shouldn't cause your problem unless there are quirks in Control Panel
or Q2007. Both probably should just use the current sound scheme.<br>
</blockquote>
This is because Sound Schemes are a per-user setting thus stored under
HKEY_USERS not HKEY_LOCAL_MACHINE.<br>
<blockquote
cite="midEEmDg.598450$Fs1.148548@bgtnsc05-news.ops.worldnet.att.net"
type="cite">A big assumption above is that Q2007 behaves like prior
releases, which it may not! You really need to browse your registry and
confirm that you have only the qopen.wav entries shown in Andrew's
program. </blockquote>
Technical nit: It's a reg file - not a program.<br>
<blockquote
cite="midEEmDg.598450$Fs1.148548@bgtnsc05-news.ops.worldnet.att.net"
type="cite">[You can safely ignore any Most-Recently-Used list entries
(look for "MRU" or "mrulist" in the entry)]. If you find any additional
entries this is a likely source of your problem.<br>
<br>
(2) Locking of registry entries. I know nothing about how Windows locks
and unlocks its registry entries.</blockquote>
It doesn't. Registry entries have ACL (Access Control Lists) much like
the security settings for files. And ACL isn't a lock as per se - it's
a permissions thing...<br>
<blockquote
cite="midEEmDg.598450$Fs1.148548@bgtnsc05-news.ops.worldnet.att.net"
type="cite"> But I do know that locks on Windows files are sometimes
not released properly even if the process that used the file<br>
terminates.</blockquote>
This is a totally different thing. Programs can lock files but they
cannot lock ACL entries. Registry entries can't be locked but their
permissions could be set such that the current user cannot modify them.
Also, when a program locks a file and another program attempts to gain
access to it and lock it it is put into a wait queue until the first
program releases the lock. Bert did not report that he attempted to
change the sound and got suspended...<br>
<blockquote
cite="midEEmDg.598450$Fs1.148548@bgtnsc05-news.ops.worldnet.att.net"
type="cite"> The symptom is that you can't delete the file. Sometimes
a simple reboot lets you delete it, sometimes a Safe Mode reboot works,
and sometimes you have to boot in command prompt mode.<br>
</blockquote>
You can't delete the file because the OS imposes a restriction that you
cannot remove a file that somebody else has currently open. Windows
does this. Unix, OTOH, doesn't. BTW, you need not go to extremes and
reboot or reboot into safe mode to fix this problem. You can use
Sysinternals Process Explorer to find the process that has the file
opened and either forcefully close that file or kill that process.<br>
<blockquote
cite="midEEmDg.598450$Fs1.148548@bgtnsc05-news.ops.worldnet.att.net"
type="cite">Have you tried turning off one of the other Quicken
sounds? If you can do this successfully it begins to look like a
locked, corrupted or possibly a duplicate entry for your qopen sound.<br>
<br>
If you have a registry locking issue Andrew's program will probably
bypass the lock.</blockquote>
Again, it's not a program - it's a reg file. It doesn't run anything
nor is it code. And it will not bypass any lock (especially since there
is no lock to be locked). It will equally fail to apply if the current
user does not have permissions to modify that registry entry. Hopefully
it would report an error. <br>
<blockquote
cite="midEEmDg.598450$Fs1.148548@bgtnsc05-news.ops.worldnet.att.net"
type="cite"> If that doesn't work Control Panel and/or Andrew's
program might work if you boot in Safe Mode.<br>
</blockquote>
You're grasping at straws.<br>
<blockquote
cite="midEEmDg.598450$Fs1.148548@bgtnsc05-news.ops.worldnet.att.net"
type="cite">As a last resort you can boot into Safe Mode with Command
Prompt mode and type "regedit" to edit the registry directly. To exit
this mode type "exit", then Ctrl-Alt-Delete and select Shutdown.<br>
</blockquote>
I highly doubt any of this is necessary.<br>
<blockquote
cite="midEEmDg.598450$Fs1.148548@bgtnsc05-news.ops.worldnet.att.net"
type="cite">Before you use Andrew's program or try to edit the
registry you should probably browse it to see what qopen.wav entries
you have. Post back if you want to do this and need help with it.<br>
<br>
Based on my limited knowledge of Windows and Quicken, access
permissions, sound schemes, registry locking, corrupted or duplicate
registry entries and anomalies in Q2007 are the only things that can
cause your problem. There may be other possibilities that people in one
of the Windows NGs might be aware of.<br>
</blockquote>
Well you are correct WRT limited knowledge... However the "trick" of
renaming the file surely would work as how can even Quicken play a
sound from a file it cannot find?<br>
<pre>-- </pre>
<a href="http://defaria.com">Andrew DeFaria</a><br>
<small><font color="#999999">C:DOS C:DOSRUN RUNDOSRUN</font></small>
</body>
</html>
--------------050306000808080204040500--
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML Sitemap