[duxhelp] Re: Unable to emboss

  • From: "Mark Mercer" <markm@xxxxxxxxxxxx>
  • To: <duxhelp@xxxxxxxxxxxxx>
  • Date: Fri, 11 Jun 2004 15:52:58 -0400

Hi Peter,

I'm glad you could decipher my original reply.  It's been a hectic week here
and I have not had much time to devote to the beta testing.

Best Regards,
Mark

----- Original Message ----- 
From: "Peter Sullivan" <peter@xxxxxxxxxx>
To: <duxhelp@xxxxxxxxxxxxx>
Sent: Friday, June 11, 2004 3:46 PM
Subject: [duxhelp] Re: Unable to emboss


> Mark,
>
> About PermissionsCustomized=0:
>
> Yes, I'd picked that up from your previous message and am pursuing things
> that way.  It's slightly tricky to set this up so that it won't break
> installations in Windows 98, but otherwise quite simple.
>
> - Peter
>
> -----Original Message-----
> From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx]
On
> Behalf Of Mark Mercer
> Sent: Friday, June 11, 2004 3:44 PM
> To: duxhelp@xxxxxxxxxxxxx
> Subject: [duxhelp] Re: Unable to emboss
>
> Hi Peter,
>
> I agree, setup should handle this.  I would suggest to have setup write
> "PermissionsCustomized=0" on a new install only.  If
> "PermissionsCustomized=1" is already there then leave it alone thus
> preventing overwriting any customizations on an update install.
>
> Best Regards,
> Mark
>
> ----- Original Message -----
> From: "Peter Sullivan" <peter@xxxxxxxxxx>
> To: <duxhelp@xxxxxxxxxxxxx>
> Sent: Friday, June 11, 2004 3:26 PM
> Subject: [duxhelp] Re: Unable to emboss
>
>
> > Kevin, Mark, and Sean,
> >
> > Here is a (hopefully) final thought on this thread:
> >
> > Only an administrator can set rights on HKEY_LOCAL_MACHINE branches,
> insofar
> > as I'm aware.  So I've planned to do all of the rights modifications in
> > SETUP, rather than in DBT.  This is based on the theory that you are
more
> > likely to install with some privilege than to run DBT with it.
> >
> > The plan in fact is to try setting extra rights for the embosser branch,
> but
> > to issue no error or warning if this fails.  It would, I suggest, be too
> > "noisy" to be warning about this.
> >
> > - Peter
> >
> > * * *
> > * This message is via list duxhelp at freelists.org.
> > * To unsubscribe, send a blank message with
> > *   unsubscribe
> > * as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
> > * subscribe, unsubscribe, and set vacation mode and other subscription
> > * options by visiting //www.freelists.org.  The list archive
> > * is also located there.
> > * Duxbury Systems' web site is http://www.duxburysystems.com
> > * * *
>
> * * *
> * This message is via list duxhelp at freelists.org.
> * To unsubscribe, send a blank message with
> *   unsubscribe
> * as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
> * subscribe, unsubscribe, and set vacation mode and other subscription
> * options by visiting //www.freelists.org.  The list archive
> * is also located there.
> * Duxbury Systems' web site is http://www.duxburysystems.com
> * * *
>
> * * *
> * This message is via list duxhelp at freelists.org.
> * To unsubscribe, send a blank message with
> *   unsubscribe
> * as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
> * subscribe, unsubscribe, and set vacation mode and other subscription
> * options by visiting //www.freelists.org.  The list archive
> * is also located there.
> * Duxbury Systems' web site is http://www.duxburysystems.com
> * * *

* * *
* This message is via list duxhelp at freelists.org.
* To unsubscribe, send a blank message with
*   unsubscribe
* as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also
* subscribe, unsubscribe, and set vacation mode and other subscription
* options by visiting //www.freelists.org.  The list archive
* is also located there.
* Duxbury Systems' web site is http://www.duxburysystems.com
* * *

Other related posts: