AW: Problem with Studio 4.3.0.0 Windows 2003 Terminal Server an Print Spooler

[sethpaien]

Hi,

For the Omnis telling you that the default printer has changed, you can
change this behaviour using :

Calculate $root.$prefs.$printernotify as kPrtNoteAuto (or kPrtNoteMsg or
kPrtNoteNoMsg)





2010/1/8 Andy Hilton <andyh at totallybrilliant.com>

> Keith
>
> I think you are closest at this point !
>
> My guess is that Omnis will have some internal 'preference' to do with a
> stored printer setup, and even when starting the app, this default is
> causing a hang when trying to locate the equivalent printer setup in
> Windows....or something like that - which simply carries on hanging whenever
> there is a print type operation going on - remember that old chestnut which
> still occurs where Omnis tells you that the default printer has changed ? I
> mean who cares, but it is a pain for web versions of Omnis in particular as
> you can't see that they are trying to tell you something !! I don't know
> what causes that either but I would be prepared to bet large that they are
> all tied up to the same root cause - and this has been an issue with Omnis
> for decades going back to Classic days too....
>
> I think the clever boys at Mitford would do well to dig deep into the core
> and find out what that printing part is doing as clearly it is an issue that
> Omnis has carried for a very long time.....
>
> Andy
>
>
> On Jan 8, 2010, at 8:29 AM, Keith Bartlett wrote:
>
> > Hi Rudolf
> >
> > Very strange....  The only other time I've experienced delays when
> printing is if there is a bad mismatch between the printer configuration
> stored on the layout and the actual printer selected.  But as you've not
> even loaded a library it's not that.
> >
> >
> > Sorry can't think of anything else at the moment.
> >
> > Cheers
> > Keith
> >
> >
> > On 8 Jan 2010, at 13:13, Rudolf Bargholz wrote:
> >
> >> Hi Keith,
> >>
> >> Problem is, I have removed all printer drivers other than the "Microsoft
> XPS Driver". Not just printer links drivers are deleted but also the driver
> files, and the problem still occurs.
> >>
> >> We have many sites running this setup successfully as well, which does
> not seem to impress the customer though :-) First time I have had this kind
> of problem.
> >>
> >> Regards
> >>
> >> Rudolf Bargholz
> >> ________________________________________
>
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
>