Can not create printer with my own ppd file

Question

I have a printer model that is not covered in Solaris Print Manager.
I downloaded a foomatic-PPD file. Followed the steps (from Solaris 10 administration guide) to add printer. (lpfilter -f $ name -F $ filter didn't succeed, so I manually did lpfilter -f foomatic -F foomatic.fd)
After printer is added, and it's idle, I tried to print a job, but it says:
UX:lp: ERROR: The LP print service could not read your request file
To fix: see if the spooling file system is full.
I have also tried to add a new entry in /usr/lib/lp/model/ppd/ppdcache and the new entry points to my ppd file.
Add printer through Soloaris print manager, I got the exact same message.
Any tips?
# lpadmin -p paper -v /dev/printers/0 (1)
# lpadmin -p paper -I postscript (2)
# lpadmin -p paper -m standard_footmatic (3)
# lpadmin -p paper -n /path/Lexmark-Optra_E312-Postscript.ppd.gzmake(4)
# lpadmin -p paper -D "Color printer on third floor, rm 3003" (5)
# cd /etc/lp/fd
# for filter in *.fd;do
> name=`basename $ filter .fd`
> lpfilter -f $ name -F $ filter
> done (6)
# accept paper
     destination �paper� now accepting requests
# enable paper     (7)
printer �paper� now enabled
# lpstat -p paper (8)
printer paper is idle. enabled since Feb 28 11:21 2004...

Answer 1

I haven't played with this myself, but from looking at the documentation and what you have done:
1. is this a locally attached printer (serial port , usb, etc.) or a network printer? You are using standard_foomatic that is for locally attached printers, but your description seems to indicate that the printer is on the network. If it's a network printer, then the netstandard_foomatic script should be used.
2. Is the content type of postscript appropriate for this printer? The docs use that but that may not be correct. Is the Optra E312 a postscript printer?
3. althought the built-in ppd files are in the .gz format (and unzipped as needed), the docs indicate that the "home brewed" ppds should be just plain .ppd.
Not sure if any of this is relevant, but that's my 2 cents.