[duxhelp] Re: Unable to emboss

  • From: "Peter Sullivan" <peter@xxxxxxxxxx>
  • To: <duxhelp@xxxxxxxxxxxxx>
  • Date: Mon, 7 Jun 2004 14:36:16 -0400

No problem, Kevin.  I'd like to make this easy on you.  I just thought that
preventing "Restricted Users" from adding/removing/modifying embosser
configurations might be a feature to you.  And I certainly wouldn't want to
add more work for myself only to make the product less useful.

I have just committed code that makes it possible for "Power Users" to get
all access they need.  And, as we haven't yet started regression testing for
beta 4, that should make it in for beta 4.

The fate of the other change -- to allow access for "Restricted Users" is
less certain.  I have to discuss with some others how we can do this.

- Peter

-----Original Message-----
From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx] 
Sent: Monday, June 07, 2004 2:34 PM
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] Re: Unable to emboss

Sorry to be so demanding - but like Sean said, I don't want to have to go
around to 20+ computers every time a new embosser configuration is desired.

Kevin-- 

-----Original Message-----
From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx]
On Behalf Of Peter Sullivan
Sent: Monday, June 07, 2004 1:19 PM
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] Re: Unable to emboss

Kevin,

What I've tried to say is that the reason "Users" cannot even select an
embosser is due to a coding error that I can fix.  So, to answer your
present question: yes, the fix I'm already at work on should allow Users
read-only access to the embosser configuration list.

It will take more than a simple coding change to allow "Users"
read/write
access to that key.  In particular, it will require that, when the key is
created, read/write access is granted to all Users.  This will mean at
minimum a change to the SETUP program in addition to DBT.  But so far, it's
2-0 that this is required.  So I'll get to work.  It just may be that this
part won't be rolled out until after the read-only access is there.

- Peter

-----Original Message-----
From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx]

Sent: Monday, June 07, 2004 2:13 PM
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] Re: Unable to emboss

I would say "No" - I have users that will need to use custom settings now
and then (say for printing braille labels) and I'd like them to be able to
setup their own configurations.

On a side note, you say that Users should currently be able to select from a
list of embosser configurations stored in the registry (key below).
At
present, none of the embossers I've installed as administrator were
available to members of the Users group.  Will this be changed/fixed
following the code fix you mention?

Kevin-- 

-----Original Message-----
From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx]
On Behalf Of Peter Sullivan
Sent: Monday, June 07, 2004 1:02 PM
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] Re: Unable to emboss

Kevin, Mark, and all lurkers-to-thread,

If you are at all familiar with regedt32, you can perhaps help me out.
I've
found that HKEY_LOCAL_MACHINE\Software\Duxbury Systems, Inc.\Embosser and
all sub-trees have read/write permission for "Power Users" and read-only
permission for "Users".  If this is the same for your installation, then I
think that we can conclude a few things:

1. DBT isn't opening the registry in this instance with a technique that
allows us what permissions we should get.  In other words, there's a coding
problem that should be simple to fix.
2. Without a design change, we'll find that "Power Users" and
"Administrators" will be able to add/modify/remove embosser configurations,
but "Restricted Users" will only be able to select and use a configuration.

My question for those of you who have some concerns in this area is
this: is
it OK for "Restricted Users" to be restricted in this regard?

- Peter

-----Original Message-----
From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx]
On
Behalf Of Mark Mercer
Sent: Monday, June 07, 2004 1:56 PM
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] Re: Unable to emboss

Hi Peter, Kevin and All:

I verified Kevin's report.  No embossers at all are installed even with the
power users group enabled under Windows 2000 Pro upon startup.  No embosser
changes are saved unless administrative privileges are enabled.  If a new
user has administrative privileges all previously installed embossers show
up.

Best Regards,
Mark

----- Original Message -----
From: "Peter Sullivan" <peter@xxxxxxxxxx>
To: <duxhelp@xxxxxxxxxxxxx>
Sent: Monday, June 07, 2004 1:44 PM
Subject: [duxhelp] Re: Unable to emboss


> ... But then reality rears its ugly head again.  I find that things
work
> just as you've described if I turn my rights down to "restricted
user".
It
> may not even be necessary to go that far.  So yes, we do have a
problem
> here.  Reference #1105.
>
> - Peter
>
> -----Original Message-----
> From: duxhelp-bounce@xxxxxxxxxxxxx
[mailto:duxhelp-bounce@xxxxxxxxxxxxx]
On
> Behalf Of Loeffler, Kevin J.
> Sent: Monday, June 07, 2004 1:36 PM
> To: duxhelp@xxxxxxxxxxxxx
> Subject: [duxhelp] Re: Unable to emboss
>
> Mark and all,
>
> Yes, we are running the build from 24-May-2004.  I just tried to set
the
> embosser profiles on one of our desktops running under the
Administrator
> account and had no problems.  I was able to save the global embosser
setup
> and a document embosser setup with a test file.
>
> Does everybody else running XP use their systems under an
administrative
> account?  Does the latest build of Duxbury require administrative
access
to
> some of its'
> components?  After I
> installed the beta on our machines, I specifically went and assigned
full
> permissions (to the Users group) on the Dbtdocs and Duxbeta folders as
well
> as "C:\Windows\Duxbury.ini" in order to make sure our users could
change
> settings.  From what I learned above, it would appear that there may
be
> other restrictions in place under XP that I need to circumvent to
allow
> users to run the program and make settings changes.
>
> Ironically, our XP systems are not locked down as well as our NT 4
systems
> were with v10.4, so I don't understand why there would be a
permissions
> problem under XP.
> If use of the latest
> build of Duxbury requires administrative access to some component,
then
this
> will be a problem for users in a corporate environment.  I certainly
won't
> grant all of our users administrative access to our systems - that
defeats
> the whole security mechanism of XP.
> It is possible that I
> have enabled some security feature that slips the mind at present and
that
> none of the other beta testers have done so, although I don't really
think
> that this is the case (but I've been wrong before).  Is any body else 
> running the beta under XP in a domain (and NOT logging on with an
account
> that has administrative privileges)?
>
> Kevin--
>
> -----Original Message-----
> From: duxhelp-bounce@xxxxxxxxxxxxx
[mailto:duxhelp-bounce@xxxxxxxxxxxxx]
> On Behalf Of Mark Mercer
> Sent: Monday, June 07, 2004 12:01 PM
> To: duxhelp@xxxxxxxxxxxxx
> Subject: [duxhelp] Re: Unable to emboss
>
> Hi Kevin,
>
> I was able to install the Thiel Impacto 600 as a share with no problem
under
> Windows XP Home and Windows 2000 Professional.  I'll check with
Windows XP
> PRO.  The dbt.elt file for beta 3 limits the lines per page for the
Impacto
> 600 to 25, so I can't setup DBT exactly as you have yours.  Are you
sure
> about the latest beta build Monday, May 24, 2004?  I had a problem in
beta
2
> in the device settings tab and the only way to get out was to cancel
and
> that removed the embosser.
>
> Best Regards,
> Mark
>
> ----- Original Message -----
> From: "Loeffler, Kevin J." <loeffler@xxxxxxxxxx>
> To: <duxhelp@xxxxxxxxxxxxx>
> Sent: Monday, June 07, 2004 11:46 AM
> Subject: [duxhelp] Re: Unable to emboss
>
>
> > With or without a file open, select Global->Embosser Setup.  Click
on
> > New.  Create a new setup
> > name (i.e., THIEL).  Set the Embosser Model to Thiel Impacto 600,
> select
> > Send to printer (our
> > share is \\server\Thiel).  Change to the Device Settings tab and set
> the
> > rightmost cell placement
> > to 42, click OK.  Set Lines per page to 26 and check the Emboss in 
> > Interpoint checkbox.  Click OK.
> >
> > Opening up the Global->Embosser Setup menu immediately after the
above
> > shows NO embosser listed
> > in the setup listing.  The same applies for creating an embosser
setup
> > entry using Document->
> > Embosser Setup (with a file open, obviously).
> >
> > Kevin--
> >
> > -----Original Message-----
> > From: duxhelp-bounce@xxxxxxxxxxxxx
> [mailto:duxhelp-bounce@xxxxxxxxxxxxx]
> > On Behalf Of David Holladay
> > Sent: Monday, June 07, 2004 11:36 AM
> > To: duxhelp@xxxxxxxxxxxxx
> > Subject: [duxhelp] Re: Unable to emboss
> >
> > I am not familiar with any reports of "missing embosser
> configurations".
> > Many have complained of the inability to delete the last
> configuration.
> > Could you be specific as to the steps you take to get to this 
> > frustrating situation?
> >
> > -- David Holladay
> >
> >
> > At 10:28 AM 6/7/2004 -0500, you wrote:
> > >I have several users who have (a) opened old Duxbury files and (b) 
> > >created new files in the latest beta build who are unable to emboss

> > >at all.  Both the
> global
> > >and document
> > >embosser settings disappear immediately after being created.  I've
> had
> > >the users save
> > >the document after setting the embossers up and then reopen it and
> the
> > >embossers are
> > >nowhere to be found.  Opening up the embosser settings (either one)

> > >immediately after creating the profile reverts back to no embosser 
> > >configured.  Am I missing something, or is anyone else running into

> > >this problem?  We are running Windows
XP
> > Pro
> > >and use a networked
> > >Thiel Impacto 600 (which doesn't matter - setting the embosser to
use
> > >LPT1 also results in
> > >a lost embosser profile).
> > >
> > >Kevin--
> > >
> > >-----------------------------------
> > >Kevin J. Loeffler
> > >System Administrator
> > >TAEVIS
> > >Purdue University
> > >509 Harrison Street
> > >West Lafayette, IN 47907-2025
> > >Office phone: (765) 496-2856
> > >Email: loeffler@xxxxxxxxxx
> > >http://www.taevisonline.purdue.edu
> > >
> > >* * *
> > >* 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 http://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 http://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 http://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 http://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 http://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 http://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 http://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 http://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 http://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 http://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 http://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 http://www.freelists.org.  The list archive
* is also located there.
* Duxbury Systems' web site is http://www.duxburysystems.com
* * *

Other related posts: