Conference bulova::decw_jan-89_to_nov-90

    
    The only suggestion I have is to check to see if any of the sm.printer
    resources exist in a decw$xdefaults.dat or other *sm*.dat file.   They
    should only exist in decw$sm_general.dat
    
    Are you doing a capture screen or print screen to get the output?
    

    The only file with printer definitions is shown below.
    
    I'm trying to do a capture portion of screen.  I would do a print
    screen, but we don't have a color printer actually on a queue.
    Mine is an LJ250 connected to CSA0: on a VSII/GPX.
    
    regards,
        
    steve
    -----------------------------------------------------------------
    $ search *.dat; print
    
    ******************************
    STOUT$DUA1:[MCAFEE]DECW$SM_GENERAL.DAT;11
    
    sm.printer.aspect_ratio:        1,1
    sm.printer.color:       color
    sm.printer.filename:    sys$login:decw$capture.six
    sm.printer.ribbon_saver:        positive
    sm.printer.storage_format:      sixel
    sm.printer.file_prompt: 1
    sm.printer.rotate_prompt:       1

    I'm getting the same thing.  If I select B&W sixel, the capture
    operation produces a sixel file which prints just fine, in black and
    white.  After changing *only* the Color option, the result is some 
    PostScript Bitmap Image format, the header looks like this:
    
    %!PS-Adobe-2.0 EPSF-1.2
    %%Title: Bitmap Image
    %%Creator: VAS V1.1
    %%BoundingBox: 0 0 128 186
    %%Pages: 1 1
    %%EndComments
    /DEC_IMG_dict 50 dict def
    DEC_IMG_dict begin
    /inch {72 mul} def end
    %%EndProlog
    %%Page: 1 1
    
    

    It's broken for me too.
    
    Is there anybody that this works for?
    
    Regards,
    
    Marios

    Is there a patch available somewhere for this problem? 
    Or should we wait.........the next release ?
    
    		Andr�
    

Hi,

I just upgraded to 5.3-1 and it is still broken - I guess I probably could
have found that out by checking the QAR database but just thought I would
mention it here for anyone else that is wondering.

Peter

P.S.  It wouldn't be nearly as bad (not having it work) if there were some
other workarround (like generating color postscript)  is there any news
on when this will be supported from print screen?

    You can capture the screen with UTOX, save it in SIXEL format and print
    that file (in color).

    The printscreen function cannot capture color sixels in VMS V5.3
    and V5.3-1. A patch, actually 2 patches, that corrects the problem 
    have been produced and will be included in VMS V5.3-2. We are
    working on making the patches available via the CSC for V5.3 and
    V5.3-1 sites. 

    re: .9 and .10
    
     The patch that will correct this problem has been given to me by 
    Decwindows Engineering. I am in the process of putting the patch into
    a VMS installable format. When the patch is complete, I will post
    another note giving the name of the patch. You can then obtain the
    patch from any of the CSCs by referencing the patch name. 

    
     The notice was sent out this morning to all CSC's regrading the
    availability of the patch to correct this problem. If you require this
    patch, contact the CSC and ask for patch DECWPRINT$PATCH01_530 and tell
    them that it is available in the CSSE VOID patch distribution system. If 
    you are an internal user, you can call the CSC also. I think you will have 
    to give them your badge number to get access to the patch. Do not
    contact engineering to try to get this patch.

    
    Hi,
    	Thanks for the quick Patch. We've waited for a long time..
    
    	I've just installed the patch this morning on my system (VS2000)
    under VMS 5.3 . It works fine, Ican do the output on the LJ250.
    	However, I've some little questions and please correct me if
    I'm wrong :
    
    	a) After installing the patch, when logging in and doing a SHOW
    SYSTEM , I've seen 2 new processes :
    		HOANG_SM1
    		HOANG_SM2 
    It seems that there're 2 Sessions processes. I don't remember if
    it already exists with VMS 5.3 . Am I right ?
    
    	b) When capturing a big portion of screen( 1/4 of screen) with
    a lot of colors, it takes about 10mn to produce a file. When printing,
    we don't get all the colors, but only with about 32 colors. Is it
    normal ?
    
    	I know that this is only a patch to correct a big problem, if
    you could get more informations, please HELP..
    
    			Thanks for any input, and thanks again for the
    					patch
    			Dung HOANG
    			TSC EVRY FRANCE

     I will let the moderator comment on that. I do not know the specifics
    of the side effects, if there are any, of this patch. The moderator will
    be able to comment better or find out the information for you .

With the patch applied to 5.3 all I get is a grey scale rendition on 
an lj250, even though color is set in customize.

Has anyone been able to get color sixel to work???

The patch does work.  My printer didn't.

Bruce

    
    Could someone please elaborate on exactly who I contact to get
    the patch?  Like maybe a phone number?  No one around here
    even knows what a CSC is...
    
    thanks,
    
    steve

>Could someone please elaborate on exactly who I contact to get the
>patch?

It depends on your organization and who your software support is 
through.  The phone number will depend on who you're authorized to 
contact.  On the other hand if you'll send me a world writable 
location I'll copy the patch over as long as you understand that it is 
"experimental", no guarantees, etc., etc.

Bruce

>    
>    Could someone please elaborate on exactly who I contact to get
>    the patch?  Like maybe a phone number?  No one around here
>    even knows what a CSC is...
>    
>    thanks,
>    
>    steve


In the phone directory that I have, November 1989, on page 281 the numbers
for (of course it is not under Customer Support Center):

 Field Service - In-DEC Area (Internal customers) 

	CSC/AT (Atlanta, GA)
	Microsystems/PC's/Terminals (also GKS,PHIGS,DECWINDOWS,DECIMAGE,
					  VWS, ect)		1(800)332-8000

	CSC/CS (Hardware)	1(800)525-6570
	CSC/CS (Software)	1(800)525-7100


	Rick

I have been able to reproduce a problem a customer is having after installing
both the color sixel vs postscript patch and the b/w printscreen corruption
patch.  The b/w printscreen patch didn't seem to do a dern thing and although
I now generate color sixel instead of postscript files these color sixel files
are corrupted.

The problem is this:
If I hold the paper at the orientation that it came out of the printer, 
reguardless of what orientation printscreen has turned the image, I see 
horizontal 1/16" rows of black interlaced with 1/16" horizontal lines of 
yellow superimposed over the top of the actual image.  If I type the 
captured file in a DECterm, the resulting graphic is corrupted the same 
as when it is printed.

Since a picture is worth 1k words, here is what a printscreen of a white 
area of the screen looks like.  

each character is	bwwbwwb...
an lj250 pixel		wwwwwww...
			bwwbwwb...
b = black		wwwwwww...
w = white		bwwbwwb...
y = yellow		wwwwwww...
			bwwbwwb...
			wwwwwww...
			ywwywwy...
			wwwwwww...
			ywwywwy...
			wwwwwww...
			ywwywwy...
			wwwwwww...
			ywwywwy...
			:::::::
			.......

(This problem is also discussed in note 2283. of this conference.)

Is there any new information on this?  
Is it something that I am doing wrong?
Is it being addressed?

Thanks,
Jeff

Well, at least someone else is reporting the same problem I've seen 
and I'm not completely daft.  I think it may have to do with the depth 
of a decterm which defaults to 4, but I haven't had a chance to fiddle 
with it.