I'm running Suse 10.0 x86_64 and KDE 3.4.2 Level b. I have reinstalled
PageStream5.0.2.12 Pro with no resolution of a network problem.
Possibly relevant history: Installed HP3800 printer with USB cable and it
worked. Disconnected usb, leaving the printer setup. Connected a crossover
cable and I finally got PageStream & network working.
Updated some graphics libraries. Power went down while running PageStream.
Some nodes deleted on power up. I don't know for certain either is related.
But PageStream will no long connect to usb or network. It will not even
calculate the page--no increase in processor or memory usage.
I can use the printer setups to create PS files which work fine when delivered
to the printer, either thru Evince or from
http://npi98c232/hp/device/this.LCDispatcher?nav=hp.Print .
From Yast the printer setup tests okay. From internet cups facility
(http://localhost:631/printers) I am able to print test pages. From other
programs (Mozilla, OpenOffice.org) I am able to print to the printer.
How can I check out what PgS is or is not doing? Is there some protocol I am
missing?
Any suggestions would be appreciated. Should I try downloading the whole Feb.
28 file?
--
No Jesus, No life. Know Jesus, Know life!  The beginning of Wisdom is
 the Fear of the Lord. The wages of sin is death, but the gift of God is
 eternal life through Jesus Christ our Lord!http://Quest4Life.net/glsmith/
http://MSGen.net/http://Quest4Life.net/http://JustForSomeone.com/

Gary Lee Smith wrote:

>I'm running Suse 10.0 x86_64 and KDE 3.4.2 Level b. I have reinstalled
>PageStream5.0.2.12 Pro with no resolution of a network problem.
>Possibly relevant history: Installed HP3800 printer with USB cable and it
>worked. Disconnected usb, leaving the printer setup. Connected a crossover
>cable and I finally got PageStream & network working.
>Updated some graphics libraries. Power went down while running PageStream.
>Some nodes deleted on power up. I don't know for certain either is related.
>But PageStream will no long connect to usb or network. It will not even
>calculate the page--no increase in processor or memory usage.
>I can use the printer setups to create PS files which work fine when delivered
>to the printer, either thru Evince or from
>http://npi98c232/hp/device/this.LCDispatcher?nav=hp.Print .
>>From Yast the printer setup tests okay. From internet cups facility
>(http://localhost:631/printers) I am able to print test pages. From other
>programs (Mozilla, OpenOffice.org) I am able to print to the printer.
>How can I check out what PgS is or is not doing? Is there some protocol I am
>missing?
>Any suggestions would be appreciated. Should I try downloading the whole Feb.
>28 file?
>
>
This seems as yes. May be, that more -- you should reinstall system
(have you backup?)
Anything in filesystem have not repaired during automatically fsck on
filesystem.
Which of kind of this you use? I had used ext2, ext3, xfs and ReiserFS.
For me the best showed last.

Bertold

Bertold,
Thank you. It could be the system, but I think not. I am using ext3 with
journaling and it seems to hold up well. This version of Linux did away with
my Raid 1 setup, which I loved.
I had used a download of pagestream I had on my drive, and I just downloaded
and tested the newest download. Nothing appears on the network. In fact,
pagestream does not even try to build a print file. However, everything else
I have tried, even Scribus, DOES print. I even deleted my .PageStream5 file,
letting it create another--still no network/usb printing.

On Wed April 12 2006 1:32 pm, Bertold wrote:
> >How can I check out what PgS is or is not doing?  Is there some protocol I
> > am missing?
> >Any suggestions would be appreciated.  Should I try downloading the whole
> > Feb. 28 file?
> >  
>
> This seems as yes. May be, that more -- you should reinstall system
> (have you backup?)
> Anything in filesystem have not repaired during automatically fsck on
> filesystem.
> Which of kind of this you use? I had used ext2, ext3, xfs and ReiserFS.
> For me the best showed last.
>
> Bertold

--
No Jesus, No life. Know Jesus, Know life!  The beginning of Wisdom is
 the Fear of the Lord. The wages of sin is death, but the gift of God is
 eternal life through Jesus Christ our Lord!http://Quest4Life.net/glsmith/
http://MSGen.net/http://Quest4Life.net/http://JustForSomeone.com/

On Wednesday 12 April 2006 11:13 am, Gary Lee Smith wrote:
> I'm running Suse 10.0 x86_64 and KDE 3.4.2 Level b. I have reinstalled
> PageStream5.0.2.12 Pro with no resolution of a network problem.
> Possibly relevant history: Installed HP3800 printer with USB cable and it
> worked. Disconnected usb, leaving the printer setup. Connected a
> crossover cable and I finally got PageStream & network working.
> Updated some graphics libraries. Power went down while running PageStream.
> Some nodes deleted on power up. I don't know for certain either is
> related. But PageStream will no long connect to usb or network. It will
> not even calculate the page--no increase in processor or memory usage.
> I can use the printer setups to create PS files which work fine when
> delivered to the printer, either thru Evince or from
>http://npi98c232/hp/device/this.LCDispatcher?nav=hp.Print .
> From Yast the printer setup tests okay. From internet cups facility
> (http://localhost:631/printers) I am able to print test pages. From other
> programs (Mozilla, OpenOffice.org) I am able to print to the printer.
> How can I check out what PgS is or is not doing? Is there some protocol I
> am missing?
> Any suggestions would be appreciated. Should I try downloading the whole
> Feb. 28 file?

Hi. One thing to check is for temporary pagestream files in /tmp. Namely, do:

rm /tmp/slps*

(although it probably pays to check first and make sure it is really only
referring to pgs temp files).

Apparently they are supposed to be removed automatically by PgS, but they
aren't -- at least on my system. Normally they don't interfere with printing
and right now there are 23 such files in my /tmp directory. However, I have
had a case where apparently one (or more) of the files was corrupt and
prevented PgS from printing. Quite frustrating as there was no error, just
nothing happened. Sounds to me like this could be it.

Tim Doty

Tim,
No doubt this was the case! The power outage must have corrupted one of the
tmp/slps* files (over a hundred! some from --WAY-- back). It now works with
the network! Thank you so much!
Doing dgb PageStream5Pro in a Konsole, I did get an "empty form" message,
but I could not connect it with anything. I'm guessing this was the result
of the corrupted slps file. I used File Manager (root) to view the /tmp/slps
files and most had names I recognized without looking at them. None were not
from PageStream, but I'd rather be cautious, like you suggested.

On Wed April 12 2006 6:03 pm, Tim Doty wrote:
> Hi. One thing to check is for temporary pagestream files in /tmp. Namely,
> do:
>
> rm /tmp/slps*
>
> (although it probably pays to check first and make sure it is really only
> referring to pgs temp files).

--
No Jesus, No life. Know Jesus, Know life!  The beginning of Wisdom is
 the Fear of the Lord. The wages of sin is death, but the gift of God is
 eternal life through Jesus Christ our Lord!http://Quest4Life.net/glsmith/
http://MSGen.net/http://Quest4Life.net/http://JustForSomeone.com/

On Wednesday 12 April 2006 09:04 pm, Gary Lee Smith wrote:
> Tim,
> No doubt this was the case! The power outage must have corrupted one of
> the tmp/slps* files (over a hundred! some from --WAY-- back). It now works
> with the network! Thank you so much!
> Doing dgb PageStream5Pro in a Konsole, I did get an "empty form" message,
> but I could not connect it with anything. I'm guessing this was the result
> of the corrupted slps file. I used File Manager (root) to view the
> /tmp/slps files and most had names I recognized without looking at them.
> None were not from PageStream, but I'd rather be cautious, like you
> suggested.

I'm glad that worked for you. I must've beaten my head against the wall for a
month before I got it sorted out. I'll remember the solution for a long time
to come...

Note to Deron: those "temp" files don't seem to be very temporary... ...and
clearly can still impact PgS after they're "done".

Tim Doty

> > No doubt this was the case! The power outage must have corrupted one of
> > the tmp/slps* files (over a hundred! some from --WAY-- back). It now works
> > with the network! Thank you so much!
> > Doing dgb PageStream5Pro in a Konsole, I did get an "empty form" message,
> > but I could not connect it with anything. I'm guessing this was the result
> > of the corrupted slps file. I used File Manager (root) to view the
> > /tmp/slps files and most had names I recognized without looking at them.
> > None were not from PageStream, but I'd rather be cautious, like you
> > suggested.
>
>I'm glad that worked for you. I must've beaten my head against the wall for a
>month before I got it sorted out. I'll remember the solution for a long time
>to come...
>
>Note to Deron: those "temp" files don't seem to be very temporary... ...and
>clearly can still impact PgS after they're "done".

Hi!

Glad you got it worked out Gary! Thanks Tim!

Yes, I've already been working on a solution to try and get these files
deleted when done and be a bit more robust when something goes wrong.

>Tim Doty

Deron Kazmaier - support@pagestream.org
Grasshopper LLC Publishing -http://www.pagestream.org
PageStream DTP for Amiga, Linux, Macintosh, and Windows