From toby at inf.ed.ac.uk Thu Sep 1 11:52:19 2005 From: toby at inf.ed.ac.uk (Toby Blake) Date: Thu Sep 1 05:53:06 2005 Subject: [Xprint] more Augment_Printer_List problems In-Reply-To: <200508311205.20459.Rudolf.Kollien@medas.de> References: <200508311205.20459.Rudolf.Kollien@medas.de> Message-ID: > i run into the same problem. After 3h of writing an augment script, > which only returns the user-relevant printers from the more than 200 > printers on our server, i now no more able to print from Firefox. > > I cannot imagine that no Xprint-user ever used the augment > configuration option? Why this bug still exists, when this error > already was reported in March 2004??? > > Is there any config option to specify a "special" spool comand? > > Any hints to solve the problem are welcome. I changed the source code to solve this bug in my case. I modified src/xprint_main/xc/programs/Xserver/Xprint/spooler.c and added my own LIST_QUEUES_xxxx and DEFAULT_SPOOL_COMMAND_xxxx and added a new spooler type to xpstm[], which I can call with the -XpSpoolerType agument to Xprt. It's not ideal, given that this is supposed to be configurable, but it serves as a workaround for the moment. Toby From Rudolf.Kollien at medas.de Thu Sep 1 16:27:12 2005 From: Rudolf.Kollien at medas.de (Rudolf Kollien) Date: Thu Sep 1 09:28:09 2005 Subject: [Xprint] more Augment_Printer_List problems In-Reply-To: References: <200508311205.20459.Rudolf.Kollien@medas.de> Message-ID: <200509011527.12845.Rudolf.Kollien@medas.de> Is this already reported as a bug? The workaround is ok until the next release. Unfortunately i install and update from rpm (it's easier to manage on 75 workstations). So i'm not able to patch the source. Rudolf Am Donnerstag, 1. September 2005 11:52 schrieb Toby Blake: > > i run into the same problem. After 3h of writing an augment script, > > which only returns the user-relevant printers from the more than 200 > > printers on our server, i now no more able to print from Firefox. > > > > I cannot imagine that no Xprint-user ever used the augment > > configuration option? Why this bug still exists, when this error > > already was reported in March 2004??? > > > > Is there any config option to specify a "special" spool comand? > > > > Any hints to solve the problem are welcome. > > I changed the source code to solve this bug in my case. I modified > src/xprint_main/xc/programs/Xserver/Xprint/spooler.c and added my own > LIST_QUEUES_xxxx and DEFAULT_SPOOL_COMMAND_xxxx and added a new > spooler type to xpstm[], which I can call with the -XpSpoolerType > agument to Xprt. > > It's not ideal, given that this is supposed to be configurable, but it > serves as a workaround for the moment. > > Toby -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 155 bytes Desc: not available Url : http://mozdev.org/pipermail/xprint/attachments/20050901/9ebf3f4b/attachment.bin From toby at inf.ed.ac.uk Thu Sep 1 15:35:46 2005 From: toby at inf.ed.ac.uk (Toby Blake) Date: Thu Sep 1 09:36:23 2005 Subject: [Xprint] more Augment_Printer_List problems In-Reply-To: <200509011527.12845.Rudolf.Kollien@medas.de> References: <200508311205.20459.Rudolf.Kollien@medas.de> <200509011527.12845.Rudolf.Kollien@medas.de> Message-ID: > Is this already reported as a bug? I haven't reported it, but I seem to remember the original post from 2004 saying they'd reported it as a bug. > The workaround is ok until the next release. Unfortunately i install > and update from rpm (it's easier to manage on 75 workstations). So > i'm not able to patch the source. All our s/w distribution is done via rpms too - you just need to create your own rpm - you'll need to get hold of the source rpm (.srpm or .src.rpm), patch that and then recompile. Cheers Toby From gernot at kurasc.kyoto-u.ac.jp Wed Sep 14 14:49:14 2005 From: gernot at kurasc.kyoto-u.ac.jp (Gernot Hassenpflug) Date: Wed Sep 14 00:49:55 2005 Subject: [Xprint] xplsprinters OK but xphellloworld fails Message-ID: <4327ABCA.6040309@kurasc.kyoto-u.ac.jp> Dear list-members, I am using SPARC Solaris 2.8 with GISWXprint. Before now, I used the downloadable tarball for Solaris with the run_xprint_tarball.sh script as normal user. This method worked well, using Xprt and the lpr system (we use lpc control-based printing). However, I wished to use the GISWxprint package, so I patched my Solaris box ("fukao21") with the relevant SunSolve patch clusters and installed. So far so good. After reboot script /etc/init.d/xprint starts Xprt. Mozilla and Firefox show me a long list of printers in the print dialog select box. However, nothing actually prints (except the xp_ps_spooldir_tmp_Xprintjobs@fukao21:33, and printing to file). I get the error message "psfukaop1: unknown printer". On the other hand, lpc shows me that the printers are enabled, and furthermore I can print with lpr command to any printer. I tried the xplsprinters command and I see all the printers listed, such as psfukaop1@fukao21:33, and xp_ps_spooldir_tmp_Xprinterjobs@fukao21:33. However, typing "xphelloworld -printer psfukaop1" gives the same error as when I try to print with Mozilla or Firefox. It is true that on this Solaris setup lpc is used instead of lpstat to get the list of available printers from /etc/printcap (and not from /etc/printers.conf), but Xprint >=009 apparently has the ability to use a number of commands and select the one which gives a valid spool as output: as indicated by the printer list I get in Mozilla. The old method of using the tarball also no longer works now! So I suspect that the patches also managed to change something that Xprt expects to find, which was OK before.... So I respectfully ask - where can I continue looking for the issue here? I do not lay the blame at the feet of Xprt, since the older tarball version worked before From gernot at kurasc.kyoto-u.ac.jp Wed Sep 14 16:35:40 2005 From: gernot at kurasc.kyoto-u.ac.jp (Gernot Hassenpflug) Date: Wed Sep 14 02:36:21 2005 Subject: [Xprint] Re: xplsprinters OK but xphelloworld fails (solved) Message-ID: <4327C4BC.2090802@kurasc.kyoto-u.ac.jp> Dear list-members, The problem with xprint on SPARC Solaris 8 is solved for now: The following patches in the Recommended cluster: 109320-16 109320-14 affect the lp system files. Backing out of these patches enables xprint to send jobs to printers again. Note that the patches only disrupt sending of jobs, not the fetching of the available printers. Best regards, Gernot Hassenpflug From jfl at robinlea.com Mon Sep 26 08:00:46 2005 From: jfl at robinlea.com (John Francis Lee) Date: Sun Sep 25 20:01:28 2005 Subject: [Xprint] Top of page missing Message-ID: <1127692846.8133.89.camel@ws8.kic.muangchiangrai.net> Hello, I use xprint to with LinuxTLE (Thai Language Extension) which is FC3. The rpm is xprint-20040707release-0.9.001.5.tlc I have two problems when printing : 1. the top of the page is truncated 2. webpages' text is often missing, although buttons and geegaws are not, when printing from Firefox. Any help appreciated. -- John Francis Lee 1/9-10 Thanon Trairat Muang Chiang Rai 57000 Thailand From jstumpel at planet.nl Mon Sep 26 16:25:14 2005 From: jstumpel at planet.nl (Jan Willem Stumpel) Date: Mon Sep 26 09:26:16 2005 Subject: [Xprint] Magnified PostScript file; strange gv behaviour Message-ID: <4337F6BA.1040600@my.home> I noticed Bug 4307 (Magnified PostScript file, when viewing with gs/gv) on the xprint.mozdev.org buglist. This bug occurs on my system also (it did not before, but I do not know which upgrade was responsible). The .ps files produced by xprint are very strange. When viewed (with gv) at magnification=1.000 the image is too large. You can see only part of the page. But if you select other magnifications (2.000, 0.500, 0.250) the size of the letters does not in fact change. Measured with a ruler on the screen, they stay exactly the same size. At the small magnifications you see fewer of them; they are bounded by a white area (representing "the paper") which shrinks if the "magnification" is reduced, but the few remaining letters in it stay the same size. This occurs with gv and also with evince (another ps viewer). Unfortunately I do not know enough about Postscript to diagnose this further. But this effect does not occur with ps files from other sources (or indeed with prints from Mozilla using PostScript/default). With those other ps files, reducing / enlarging the magnification in gv does shrink / blow up the letters properly. The actual prints on paper are OK by the way. But it would be nice if xprint could generate viewable ps files again. Regards, Jan From jstumpel at planet.nl Mon Sep 26 22:21:58 2005 From: jstumpel at planet.nl (Jan Willem Stumpel) Date: Mon Sep 26 15:23:00 2005 Subject: [Xprint] user-level documentation Message-ID: <43384A56.1030507@my.home> Is there any user-level (not developer-level) documentation for xprint? I do not think so. Otherwise poster John Francis Lee would not have had so many problems (unanswered on this list, for many months) printing Thai. People on the list could at least have said: RTFM! But there is no FM. I think the user manual should be written before any coding is done. Many authorities in software engineering think so also: http://rdenney.bizland.com/FYI/Requirements%20Mgmt/User%20Manual%20as%20SRS.htm It is late in the day, but maybe user-level docs can still be produced for xprint. I am very willing to lend a hand. Problem is, I am just a user, and I simply do not understand all this ddx and ppd stuff. For xprint to be accepted by ordinary users (and even by Linux distributors) good documentation is absolutely needed. This should be the first priority above anything else. I said so before on this list. Regards, Jan http://www.jw-stumpel.nl/stestu.html#T9 From dparsons at debian.org Tue Sep 27 16:48:19 2005 From: dparsons at debian.org (Drew Parsons) Date: Tue Sep 27 01:49:01 2005 Subject: [Xprint] user-level documentation In-Reply-To: <43384A56.1030507@my.home> References: <43384A56.1030507@my.home> Message-ID: <1127800100.3547.46.camel@pug.anu.edu.au> On Mon, 2005-09-26 at 21:21 +0200, Jan Willem Stumpel wrote: > Is there any user-level (not developer-level) documentation for > xprint? I do not think so. Otherwise poster John Francis Lee would > not have had so many problems (unanswered on this list, for many > months) printing Thai. People on the list could at least have > said: RTFM! But there is no FM. > All that's really available is the FAQ, http://xprint.mozdev.org/docs/Xprint_FAQ.html Other docs are listed at http://xprint.mozdev.org/docs/, including links to HP's docs, but I suspect they won't be directly useful for John's problem. > I think the user manual should be written before any coding is > done. Many authorities in software engineering think so also: > Yes, not a bad idea. Unfortunately it's a tricky exercise for us to do. Roland seems to be the only one with a broad and deep enough understanding of what Xprint is doing internally to be able to do it correctly. > It is late in the day, but maybe user-level docs can still be > produced for xprint. I am very willing to lend a hand. Problem is, > I am just a user, and I simply do not understand all this ddx and > ppd stuff. Yes, I'm frustrated by not being much more than a user too, as far as Xprint is concerned, albeit one that's had the opportunity to get Xprint integrated into Debian. Maybe you could start by consider the FAQ as the "user docs". Which parts of the FAQ would need to be altered to be more useful for users? Drew From dparsons at debian.org Tue Sep 27 17:06:53 2005 From: dparsons at debian.org (Drew Parsons) Date: Tue Sep 27 02:07:38 2005 Subject: [Xprint] Top of page missing In-Reply-To: <1127692846.8133.89.camel@ws8.kic.muangchiangrai.net> References: <1127692846.8133.89.camel@ws8.kic.muangchiangrai.net> Message-ID: <1127801213.3547.64.camel@pug.anu.edu.au> On Mon, 2005-09-26 at 07:00 +0700, John Francis Lee wrote: > Hello, > > I use xprint to with LinuxTLE (Thai Language Extension) which is FC3. > The rpm is xprint-20040707release-0.9.001.5.tlc > > I have two problems when printing : > 1. the top of the page is truncated > 2. webpages' text is often missing, although buttons and geegaws are > not, when printing from Firefox. > Hi John, as always it's helpful if you can provide urls of pages which are not working satisfactorily. The one you gave previous, www.dailynews.co.th, prints from my Debian system, except the font size is uncomfortably small. I can't account for truncating the top of the page. I think text may go missing if there isn't a full set of properly registered fonts, though I'd have thought your LinuxTLE would have taken care of that. RedHat has traditionally opposed the use of Xprint, although the LinuxTLE sounds like the right thing you've been after for running a Thai system. The new Debian stable release ("sarge") was released in June. Have you had a chance yet to test it and compare? The initial set-up screen starts with a list of languages to install with, and Thai is one of the languages listed. Xprint on Debian has it's own set of problems, which are by no means minor, so I can't guarantee you'll prefer it. But I'm not seeing the two particular problems you've mentioned here. It might be worth checking which locale you're running under, since that can affect font handling (run "locale", check LANG, or look in /etc/environment). If you're in a Thai 8-bit locale (or worse, ASCII or latin1), do you get different results using a Thai UTF-8 locale instead? Sorry I can't give a more definitive answer. Drew From toby at inf.ed.ac.uk Tue Sep 27 10:14:57 2005 From: toby at inf.ed.ac.uk (Toby Blake) Date: Tue Sep 27 04:15:31 2005 Subject: [Xprint] user-level documentation In-Reply-To: <43384A56.1030507@my.home> References: <43384A56.1030507@my.home> Message-ID: > For xprint to be accepted by ordinary users (and even by Linux > distributors) good documentation is absolutely needed. This should > be the first priority above anything else. I said so before on this > list. I agree to a certain extent, but I have my doubts about the overall readyness of xprint for serious usage. I say this because I've posted to this list in recent months about - Augment_Printer_List not working as specified in the documentation (cannot use '|' in command as per example, printer list mysteriously reversed) - Using Augment_Printer_List *at all* results in Xprt not being able to detect the spooler and hence results in no printing. This was first reported in March 2004 - a patch (which didn't work) was suggested at that time. I didn't receive any replies to my posts about these problems. I patched the source code myself to get round these problems, but they did lead me to have serious doubts about the reliability of the Xprint code and the existence of an active support community (e.g. this list). Lately, I've been seeing numerous postscript errors when printing from Xprint to HP printers - as a result of the postscript produced by Xprint. I haven't posted any of these details to the list, as it didn't appear to be active enough to warrant the effort. It's slightly disappointing, as I would certainly like to use a working Xprint, but I suspect I may have to conclude that it's simply not yet in a state where it's ready for serious usage and development isn't active enough to become so. I hope I'm wrong though, as it's potentially a very very useful bit of s/w. Regards Toby Blake University of Edinburgh From jfl at robinlea.com Tue Sep 27 17:30:14 2005 From: jfl at robinlea.com (John Francis Lee) Date: Tue Sep 27 05:30:59 2005 Subject: [Xprint] Top of page missing In-Reply-To: <1127801213.3547.64.camel@pug.anu.edu.au> References: <1127692846.8133.89.camel@ws8.kic.muangchiangrai.net> <1127801213.3547.64.camel@pug.anu.edu.au> Message-ID: <1127813414.8133.186.camel@ws8.kic.muangchiangrai.net> Hi Drew, On problem 1, this I see with OpenOffice and with Foxfire, pretty much all the time. Sometimes if I print more than one copy the second or third will show more of the stuff truncated on the first page on the first copy. Pretty expensive printing. On problem 2, try hotmail... regular screen or printable view. [jfl@ws8 c]$ locale LANG=th_TH LC_CTYPE="th_TH" LC_NUMERIC="th_TH" LC_TIME="th_TH" LC_COLLATE="th_TH" LC_MONETARY="th_TH" LC_MESSAGES="th_TH" LC_PAPER="th_TH" LC_NAME="th_TH" LC_ADDRESS="th_TH" LC_TELEPHONE="th_TH" LC_MEASUREMENT="th_TH" LC_IDENTIFICATION="th_TH" LC_ALL= The Thais like TIS-620. I don't believe that there is yet a genuine unicode specification for Thai. It has to do with fonts that require special character handling, such as vowels consonants and tone marks that have one defined sequence among several possible. UTF-8 works great sometimes. TIS-620 is what all the machines in Thailand use "out of the box". So now I can at least print English and Thai equally badly :) I appreciate all the hard work that's been put into linux and x and xprint, but none of my customers take my machines seriously. They all prefer "real" computers... those that run Microsoft software. Here in Thailand, where Microsoft software "sells" at the same price as linux who can blame them? Nobody has ever given a thought to why Microsoft software "just works" from the users point of view. Or had to. The linux solution is rapidly getting as (more?) bloated than the Microsoft solution... it just doesn't work as well. Don't get me wrong... I like linux and I use it. But I'm just a perverse old coot anyway. On Í., 2005-09-27 at 16:06 +1000, Drew Parsons wrote: > On Mon, 2005-09-26 at 07:00 +0700, John Francis Lee wrote: > > Hello, > > > > I use xprint to with LinuxTLE (Thai Language Extension) which is FC3. > > The rpm is xprint-20040707release-0.9.001.5.tlc > > > > I have two problems when printing : > > 1. the top of the page is truncated > > 2. webpages' text is often missing, although buttons and geegaws are > > not, when printing from Firefox. > > > > Hi John, > > as always it's helpful if you can provide urls of pages which are not > working satisfactorily. The one you gave previous, www.dailynews.co.th, > prints from my Debian system, except the font size is uncomfortably > small. > > I can't account for truncating the top of the page. I think text may go > missing if there isn't a full set of properly registered fonts, though > I'd have thought your LinuxTLE would have taken care of that. > > RedHat has traditionally opposed the use of Xprint, although the > LinuxTLE sounds like the right thing you've been after for running a > Thai system. The new Debian stable release ("sarge") was released in > June. Have you had a chance yet to test it and compare? The initial > set-up screen starts with a list of languages to install with, and Thai > is one of the languages listed. > > Xprint on Debian has it's own set of problems, which are by no means > minor, so I can't guarantee you'll prefer it. But I'm not seeing the > two particular problems you've mentioned here. > > It might be worth checking which locale you're running under, since that > can affect font handling (run "locale", check LANG, or look > in /etc/environment). If you're in a Thai 8-bit locale (or worse, ASCII > or latin1), do you get different results using a Thai UTF-8 locale > instead? > > Sorry I can't give a more definitive answer. > > Drew > > _______________________________________________ > Xprint mailing list > Xprint@mozdev.org > http://mozdev.org/mailman/listinfo/xprint -- John Francis Lee 1/9-10 Thanon Trairat Muang Chiang Rai 57000 Thailand From jstumpel at planet.nl Tue Sep 27 19:33:03 2005 From: jstumpel at planet.nl (Jan Willem Stumpel) Date: Tue Sep 27 12:35:53 2005 Subject: [Xprint] user-level documentation In-Reply-To: References: <43384A56.1030507@my.home> Message-ID: <4339743F.90403@my.home> Toby Blake wrote: > I agree to a certain extent, but I have my doubts about the > overall readyness of xprint for serious usage. > > I say this because I've posted to this list in recent months > about > > - Augment_Printer_List not working [..] At least you seem to know /something/ about the inner workings of xprint. This knowledge may be invaluable for constructing the user-level doc that we need. This user-level doc should begin (as any good user-level doc should) with some existential questions: why does this program exist, what does this program do, and why you should use it. Do you (or does anyone) happen to know why xprint exists at all? This is a serious question. xprint is only needed for multilingual prints from Mozilla & Co.; but why is a server needed for this? Why is it a bright idea to involve the X server in printing? This is not at all meant sarcastically, I just do not know why a program running in X (like Mozilla) shouldn't be able to produce its own Postscript without involving the X server; as I understand it, the X server's job is to produce pixels on the screen, not to generate Postscript code. There is an alternative, called freetype printing. It does not work as well as xprint does (when you have negotiated xprint's quirks) but it could (I suppose) be improved. Does anyone know why the freetype development path has been abandoned (by whom? the Mozilla folks? Debian? I don't know) and the xprint path chosen instead? Regards, Jan From jstumpel at planet.nl Tue Sep 27 20:02:41 2005 From: jstumpel at planet.nl (Jan Willem Stumpel) Date: Tue Sep 27 13:03:45 2005 Subject: [Xprint] user-level documentation In-Reply-To: <1127800100.3547.46.camel@pug.anu.edu.au> References: <43384A56.1030507@my.home> <1127800100.3547.46.camel@pug.anu.edu.au> Message-ID: <43397B31.8090501@my.home> Drew Parsons wrote: > All that's really available is the FAQ, > http://xprint.mozdev.org/docs/Xprint_FAQ.html But isn't this FAQ atrocious? It just boasts about how good xprint is from a technical point of view. But when it comes to explaining things like ddx, it does not go beyond expanding the acronyms, as in Q: What does "DDX" mean ? A: "DDX" is a short term for "Device Dependent X" - the device-specific layer of a Xserver ("DIX"(="Device Independent X") is the counterpart). What sense am I, a user, supposed to make of this? Open Source without documentation is even worse than closed source. Regards, Jan From cloos at jhcloos.com Thu Sep 29 01:31:48 2005 From: cloos at jhcloos.com (James Cloos) Date: Thu Sep 29 00:32:36 2005 Subject: [Xprint] Magnified PostScript file; strange gv behaviour In-Reply-To: <4337F6BA.1040600@my.home> (Jan Willem Stumpel's message of "Mon, 26 Sep 2005 15:25:14 +0200") References: <4337F6BA.1040600@my.home> Message-ID: >>>>> "Jan" == Jan Willem Stumpel writes: Jan> I noticed Bug 4307 (Magnified PostScript file, when viewing with Jan> gs/gv) on the xprint.mozdev.org buglist. This bug occurs on my Jan> system also (it did not before, but I do not know which upgrade Jan> was responsible). Just for reference, this also affects printing via gs, where that is used. I'm at gs 8.51. -JimC -- James H. Cloos, Jr. From jstumpel at planet.nl Thu Sep 29 20:24:36 2005 From: jstumpel at planet.nl (Jan Willem Stumpel) Date: Thu Sep 29 13:25:36 2005 Subject: [Xprint] Magnified PostScript file; strange gv behaviour In-Reply-To: References: <4337F6BA.1040600@my.home> Message-ID: <433C2354.4050607@my.home> James Cloos wrote: > Jan> I noticed Bug 4307 (Magnified PostScript file, when viewing with > Jan> gs/gv) on the xprint.mozdev.org buglist. This bug occurs on my > Jan> system also (it did not before, but I do not know which upgrade > Jan> was responsible). > > Just for reference, this also affects printing via gs, > where that is used. Do you mean you get magnified printing also *on paper* ? That, I think, is a different problem, which can be cured by tweaking the default-printer-resolution settings in /etc/Xprint/C/print/attributes/printer and/or /etc/Xprint/C/print/attributes/document Bug 4307 refers to the screen display in postscript viewers (like gv) only. Regards, Jan From Hassenpflug.Ismail at mb3.seikyou.ne.jp Tue Sep 13 06:39:25 2005 From: Hassenpflug.Ismail at mb3.seikyou.ne.jp (Hassenpflug.Ismail@mb3.seikyou.ne.jp) Date: Wed Oct 26 16:46:51 2005 Subject: [Xprint] PDF raster driver for Solaris available? Message-ID: <200509130538.j8D5ctDc004898@sings2.sings.jp> Dear list members, At work, I am using GISWxprint (v009.001) on a SPARC Sunblade 100 running Solaris 2.8, in Firefox 1.06 and Mozilla 1.7.11 happily, with one exception. I cannot figure out how to obtain the "xp_pdf_spooldir_tmp_Xprintjobs@" in my printer select dialog popup when printing from these applications. The ps version works extremely well, but there does not appear to be a pdf spool directory in: "/opt/GISWxprint/server/etc/XpConfig/C/print/models/". I see only the following: "CANONC3200-PS/ HPLJ4050-PS/ PSdefault/ PSspooldir/ SPSPARC2/". However, on my home x86 dexktop and work x86 laptop running Debian GNU/Linux (testing and unstable, respectively) with xprint (v009 and v1:0.10.alpha1-12, respectively), I see that in addition to the above models, I have available: "PS2PDFspooldir-GS/ GSdefault/" and an extra two Canon and one HP printers. In the printer dialog box, I have the option of selecting "xp_pdf_spooldir_tmp_Xprintjobs@". I scoured the mozdev site, read the FAQ, googled for information on solaris, xprint, pdf, but could not find any information as to whether this service was available or not. In the CVS SRC tree on the website of xfree86desktop.org there does not appear to be anything in the pdf subdirectory of "/xprint/src/xprint_main/xc/programs/Xserver/Xprint". Maybe the feature depends on other packages being available too, such as ghostscript (which I have)? I could not figure out how to search this Xprint mailing list, but tried to look for threads that included the keywords solaris, pdf, to no avail. I would really like to know what the issue is here, and whether I can in fact obtain pdf output with xprint under solaris if I set the configuration correctly. If this information is available elsewhere, please point this out to me, I gladly admit my ignorance. Many thanks in advance. Gernot Hassenpflug -- Gernot Hassenpflug (gernot@rish.kyoto-u.ac.jp) Tel: +81 774 38-3866 JSPS Fellow (Rm.403, RISH, Kyoto Uni.) Fax: +81 774 31-8463