The HP 692C uses PCL 3, as does almost all the HP ink jets of recent years.
This means that the 690 series will use any printer definition that also uses
PCL 3. I'd pick the closest HP printer to the features of the 69x and go with
it. It works for me.
In other words, PCL 3 is PCL 3 is PCL 3.
Andrea,
Please don't waste your money on the SB Live. This card is
on the list of cards without open source support because
Creative refuses to release the information necessary to
construct a driver. Buying this card doesn't help our
case to get Creative to release the programming specs.
There
> On Mon, 4 Oct 1999, Shannon wrote:
>
> > In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] write
> > s:
> >
> > > The best bargain in the business has got to be the Creative Ensoniq
> > > PCI128. I bought a card at CompUSA for under $30.00. It's based on
> > > the ENS1371 chipset and works we
Hi,
Here's how to get the latest Lyx running with Slink.
1. Download LyX 1.0.4 source tarball via link on http://www.lyx.org/
2. Make sure that the following are installed from the Stable
(Slink) directories.
All sgml components. I included the following:
debiandoc-sgml
perlsgm
> Hi All,
> I'm looking for a good PCI soundcard for my new computer. Preferably
> non-PnP, although I can work with it if necessary. I would like it to
> work under OS/2, Linux, and Win95 (for games). Are there any suggestions?
> Thanks
>
The best bargain in the business has got to be the Cre
> http://www.internatif.org/bortzmeyer/debian/apt-sources/
This is the type of information that should be linked to on the Debian host
site. One should not have to come to the Mailing Lists to find this. The
logical place to put this is with the Gnome Slink update link.
I can see that much of
> On Fri, Oct 01, 1999 at 08:17:41AM -0600, [EMAIL PROTECTED] wrote:
> > How are you doing this? Do you just go get the packages and 'dpkg -i' them
> > or do you use apt? There are a bunch of things I want to upgrade on my
> > system but I assumed that all of the potato packages would have depend
> When I asked a similar question a long time ago (but still when slink
> was stable!) it was explained to me thusly: if you start modifying
> "stable", then you might break it. That means that if one permitted
> regular modifications/upgrades to stable packages, one would have to
> go through th
> Well, it's a bit better than that - particularly if you keep up with the
> various lists (mostly -user and -devel) you should be all right. It's
> more a case of "pay attention and be prepared to fix things if they
> break" than anything else. I'd guess that a fair proportion of
> developers ar
> I've been slowly upgrading my packages from slink to potato, and
> frankly, have never had a single problem. I was nervous about upgrading
> perl, because I've seen all sorts of veiled references to possible
> hosage (although I've never seen a concise statement of the actual
> problem), but eve
Hi,
I know that the basic issues of my question have been asked many times
here previously. But, time goes on and things change. Maybe this all
too important issue needs to be addressed again.
When I talked with some Debian folks at Linux World, they indicated
that Potato was fairly stable and
11 matches
Mail list logo
