Announcement

Collapse
No announcement yet.

LPRINT ATTACH problem

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Hi Gary,

    Tried this but still Error 68

    Code:
    LOCAL PPP as string
    
    PPP = "\\dispatch1\Epson LX-300+II ESCP"
    
    LPRINT ATTACH UCODE$(PPP)
    
    PRINT ERR

    Comment


    • #17
      Hi Steve,
      Looks like you did as Bob suggested - so back to Bob!

      Comment


      • #18
        If fixed in 6.0.2 and later (broke 6.0.0. and 6.0.1) (Actual facts unknown)
        Code:
        MACRO ATTACH_PRINTER (sPrinter) 
        
          MACROTEMP  sP 
          DIM  sp AS STRING 
        
          SP = sPrinter
        #IF %PB_REVISION AND &h0600) = &h0600  ' if PB CC 6.0 
         #IF (%PB_REVISION AND &h00FF) < &h02  ' if less than fixed version 
              Sp = UCODE$ (SPrinter)           ' required conversion 
         #ENDIF
        #ENDIF
         
          LPRINT ATTACH SP 
        
        END MACRO 
        
        
        
        .... 
        
             ATTACH_PRINTER ("LPT1") 
        
        ....
        Close, I think . You get the idea.

        MCM
        Michael Mattias
        Tal Systems Inc.
        Racine WI USA
        mailto:mmattias@talsystems.com
        www.talsystems.com

        Comment


        • #19
          I don't know if this has any bearing on the LPrint Attach problem but
          I've been using the XPrint Attach for many months. After the last round
          of XP updates, I can no longer connect to my W2K system for printing.
          It worked fine last week.

          Today I couldn't setup a share to the W2K LPT1 printer. The error kept
          coming up that the spooler service wasn't running. Same error when
          trying to get W2K printer status via Printer Control panel.

          Just thought I'd toss that info out there.

          Comment


          • #20
            Could be something to do with Win 7 as the previous installation was XP Pro and I haven't changed anything else.

            Comment


            • #21
              From your Win 7 computer, can you ping the dispatch1 computer?
              Is it possible that during the update something got disconnected between
              the 2 computers ( maybe different IP for dispatch1 that didn't survive the
              update ) or maybe something to do with UAC rights between the 2?

              Comment


              • #22
                Yes can ping it ok.

                Did a clean install. Can print to the printer within windows from any other worstation. Also can print to it with DDOC just can use LPRINT ATTACH

                I remember that this was a problem in the compiler that was fixed but seems it's back for me.
                Last edited by Steve Bouffe; 27 Apr 2012, 05:13 AM.

                Comment


                • #23
                  How about setting it as the default printer and doing LPrint Attach Default ?
                  Then check out what LPrint$ shows as the printer name.

                  Comment


                  • #24
                    FWIW
                    I have found it less troublesome to create a windows printer device and set up the share in the printer device.
                    Of course our workstations are few in number at each location.
                    I am not sure that this will solve your problem.
                    Of course the printer device name spools printout so that way it could help or hurt you depending on your situation.
                    p purvis

                    Comment


                    • #25
                      Could be something to do with Win 7 as the previous installation was XP Pro and I haven't changed anything else
                      Well, changing "only" the operating system is changing a lot; so yes, your problem definitely could be something related to the new O/S and how you have set things up.
                      Michael Mattias
                      Tal Systems Inc.
                      Racine WI USA
                      mailto:mmattias@talsystems.com
                      www.talsystems.com

                      Comment


                      • #26
                        Originally posted by Steve Bouffe View Post
                        Hi Gary,

                        Tried this but still Error 68

                        Code:
                        LOCAL PPP as string
                        
                        PPP = "\\dispatch1\Epson LX-300+II ESCP"
                        
                        LPRINT ATTACH UCODE$(PPP)
                        
                        PRINT ERR
                        what OS is 'dispatch1' running? During a recent upgrade/conversion at work, we found that LPRINT ATTACH commands that would work just fine on shares hosted on 32bit Windows 2003 would fail (Err 68) on 64Bit Windows 2008R2

                        This is a couple months ago, I don't recall what revision of PB/Win 10 we were using. I haven't had a chance lately to test the problem further.
                        Real programmers use a magnetized needle and a steady hand

                        Comment


                        • #27
                          All systems in the network except the server are running Win7 32bit

                          Comment


                          • #28
                            Steve -

                            FWIW - In message #1 and #11 you referred to your printer as
                            Printer_Name_GL = "\\dispatch\EPSON LX-300+II".

                            In message #16 it is
                            PPP = "\\dispatch1\Epson LX-300+II ESCP".

                            Maybe significant, maybe not? Also I see in the 9.05 docs that
                            the printer name cannot exceed 32 characters. The last
                            referenced one was 32 exactly.

                            You might try a shorter name.

                            Skip

                            Comment


                            • #29
                              I recently got a report that one of my programs gives a message to install a printer when the printer is already installed. This is on a Win7 64 bit machine, AMD I think. The program has been used by thousands of people and this is the first complaint of its type. I'll have to look into it, but first I have to find somebody with said OS and machine. Sounds similar to what's been discussed here.

                              Comment


                              • #30
                                Originally posted by Bob Zale View Post
                                Steve, please note the explanation:

                                It must be an ANSI string with a UCODE$() override. Nothing else will work.

                                You are trying to use a wide unicode string with a UCODE$() override. Should be:

                                LOCAL Printer_Name AS STRING


                                Bob
                                Hi Bob,

                                I have the same problem, but it is not resolved bij overriding the Ansi string to Unicode. I used:

                                DIM PrinterName as STRING
                                PrinterName=\\Server\LabelPrinter-1
                                LPRINT ATTACH UCODE$(PrinterName)

                                and get a 'Device Unable' (68) Error.

                                When I redirect the printer with NET USE LPT1: \\Server\LabelPrinter-1 and change the source with:
                                PrinterName="LPT1"

                                then it works fine. But my application has to print to more than one network printer and I do'nt want to SHELL to execute then 'NET USE' command.

                                What is wrong?

                                Comment

                                Working...
                                X