Chronological Thread 

< Chronological >      < Thread >

---

Thanks for the quick response!

You are right. The 'LCDd -d MtxOrb .' does seem to work
fine.

I don't find any reference to '.' in the docs. Any
explanation?

dosowski0474 AT vax2.winona.msus.edu
wrote:
>
> On Sun, 14 Feb 1999, Scott Gilbert wrote:
>
> > Wow, I just realized that when I specify the device, it
> > complains about the parameters, but it doesn't segfault, and
> > now appears to be running healthily. This leads me to
> > believe that, by default, it is using the wrong device
> > (which causes the segfault), and when the correct device is
> > specified, that device is used even though it complains that
> > the parameters are invalid.
> >
> > Boy, I am confused. Does anyone have any
> > suggestions/ideas/insights on all this?
>
> There is something weird about it. Try doing 'LCDd -d MtxOrb .'
> I think I remember reading about that somewhere, but can't seem to find it
> now.
>
> --
> Dale Osowski
> dosowski0474 AT vax2.winona.msus.edu
> http://www3.winona.msus.edu/dosowski0474
>
> -----------------------------------------------------------
> To unsubscribe from this list send a blank message to
> lcdproc-unsubscribe AT lists.omnipotent.net


-----------------------------------------------------------
To unsubscribe from this list send a blank message to
lcdproc-unsubscribe AT lists.omnipotent.net

---

• [lcdproc] 0.4Pre3 Segmentation Faults ??, Scott Gilbert, 02/14/1999
  • [lcdproc] 0.4Pre3 Segmentation Faults ??, dosowski0474 AT vax2.winona.msus.edu, 02/14/1999
    • [lcdproc] 0.4Pre3 Segmentation Faults ??, Scott Gilbert, 02/14/1999
      • [lcdproc] 0.4Pre3 Segmentation Faults ??, dosowski0474 AT vax2.winona.msus.edu, 02/14/1999
    • [lcdproc] 0.4Pre3 Segmentation Faults ??, Scott Scriven, 02/14/1999
  • <Possible follow-up(s)>
  • [lcdproc] 0.4Pre3 Segmentation Faults ??, William Ferrell, 02/14/1999

---

Archive powered by MHonArc 2.6.18.