[duxhelp] Re: Unable to emboss
- From: "Mark Mercer" <markm@xxxxxxxxxxxx>
- To: <duxhelp@xxxxxxxxxxxxx>
- Date: Fri, 11 Jun 2004 13:32:31 -0400
Hi Peter,
I would tend to lean towards Read/Write all the time with
"PermissionsCustomized=1" if customizations are present and add the entry in
the registry branch upon install of DBT "PermissionsCustomized=0". The
fewer changes to the registry the better.
As for the Guest Account, is it possible to let the user change the values
for a particular instance of DBT but not write the changes? This would
allow temporary changes to the emboss settings for any user. What do you
think?
Best Regards,
Mark
----- Original Message -----
From: "Peter Sullivan" <peter@xxxxxxxxxx>
To: <duxhelp@xxxxxxxxxxxxx>
Sent: Friday, June 11, 2004 12:58 PM
Subject: [duxhelp] Re: Unable to emboss
> Kevin (Sean, Mark, et al),
>
> Resolved: We'll make the embosser branch of the registry read/write for
all.
> (I will leave it read-only for Guest account unless I hear a shout about
> that.) An administrator will be able to change rights in the usual way,
of
> course, should there be a need to be more restrictive or a need to allow
> Guest write access.
>
> But one question remains: at what point shall we set rights to the
registry
> branch? I suggest setting them only as the branch is created. This
> prevents DBT overwriting any customizations that you may have to set by
> hand. However, it also means that current installations won't be fixed
when
> we post a new build of DBT. Rather, you would have to remove the registry
> branch (using regedit) and then re-create all of your embosser
> configurations.
>
> The obvious alternative is to set permissions every time the branch is
used.
> This, however, would be dangerous in that any administrative use of the
> machine with DBT would cause any permissions customizations to be lost.
>
> Another alternative would be to overwrite rights settings always, if we
can,
> unless we find a specific value (e.g. PermissionsCustomized=1) in the
> registry branch. You would then want to add this value if you customize
> permissions for some reason.
>
> A final alternative would be similar. We could overwrite right settings
> always, if we can, unless we find a specific value (e.g.
> PermissionsInitialized=1) in the registry branch. We would ourselves
write
> this value, so that your customizations would be preserved unless you
> eliminate the setting.
>
> I could use some idea of which of these approaches would cause you the
least
> hassle.
>
> - 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 //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
> * * *
>
>
> * * *
> * 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:
