search for: aprinter

Displaying 16 results from an estimated 16 matches for "aprinter".

Did you mean: printer
2002 Oct 14
1
WIN40 printer driver on Solaris not being installed?
...ks \ --localstatedir=/var/samba \ --with-ssl=/usr/local/ssl \ --with-sslinc=/usr/local/ssl/include \ && make I use the following commands to install the printer drivers: smbclient //localhost/print$ -c 'mkdir WIN40;put /usr/company/printdrv/DEFPRTR2.PPD WIN40/APrinter.PPD; put /usr/company/printdrv/ADFONTS.MFM WIN40/ADFONTS.MFM; put /usr/company/printdrv/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV; put /usr/company/printdrv/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP; put /usr/company/printdrv/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD; put /usr/company/printdrv/ICONLIB.DLL WIN40/ICONLIB.DLL; put...
2004 May 26
2
duplicate domains in browse list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i recently upgraded some of my servers from 3.0.2a to 3.0.4 after the upgrade my browselist shows duplicate entries for the domains. one domains is managed by a samba PDC(providing WINS too) and two samba BDC's. the other domains are managed by one samba PDC. 'smbclient -N -L <WINS_SERVER>' shows: - --- Workgroup
2002 Aug 08
1
Can not access linux printer from windows
All, I have a linux machine running Mandrake 8.2 and a windows machine running Windows 2000. The printer (aprinter) is installed on the linux machine and I am trying to access it from windows. I can access all the linux directories and files from my windows machine and even setting up 'Network Printer' on windows also went through fine but when I try to print a test page, I get this message 'Access...
2015 Aug 05
0
EFI: HP + syslinux = crash
[ merging a few sub-threads into one ] > Weird as it sounds I was able to send debug info to COM2 > (redirected to a pipe) on EFI64 VMware workstation clients. Ports 0x3f8 and 0x2f8 are so hardwired into my brain from back in the old BBS-days that I did not expect them NOT to work. Apparently some firmware engineers have this problem too. ;-) >>>> > If there is
2014 May 31
1
syslinux (pxelinux.0) debug prints
>Message: 6 >Date: Fri, 30 May 2014 07:35:30 -0400 >From: Gene Cumm <gene.cumm at gmail.com> >To: Wissam Shoukair <wissams at mellanox.com> >Cc: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com> >Subject: Re: [syslinux] syslinux (pxelinux.0) debug prints >Message-ID: > <CAD0Rxem_P4kOycVcSZUuaTjdKe=Gm5MLTjO6P6dMkbtsLOrVNQ at
2015 Aug 05
2
EFI: HP + syslinux = crash
On 05-08-15 15:28, Gene Cumm wrote: >>> 0x2f8 is a BIOSism. > >> Is this a problem? The example in the comments said 0x3f8 which is COM1. > > It means that a BIOS IO port for a UART won't work for EFI. No value > for DEBUG_PORT will do anything unless someone's got some translation > "glue" to take the attempts to open the UART and use an EFI handle
2015 Aug 05
2
EFI: HP + syslinux = crash
>>> > On 05-08-15 12:05, Gene Cumm wrote: >> >>? > I recompiled with this in mk/devel.mk <http://devel.mk>: >>? >? GCCWARN += -DDEBUG_PORT=0x2f8 -DCORE_DEBUG=1 >> >> 0x2f8 is a BIOSism. > Is this a problem? The example in the comments said 0x3f8 which is COM1. It means that a BIOS IO port for a UART won't work for EFI.? No
2015 Aug 05
1
EFI: HP + syslinux = crash
On 05-08-15 10:01, Patrick Masotta wrote: >>>> > Okay, the code in efi/ uses Print() from gnu_efi, but generic code from > core/ like core/elflink/load_env32.c prints their messages and debugging > stuff using printf(). These messages end up nowhere. This may explain > why I never saw anything beyond a certain point, even with debugging > turned on. >
2002 Jul 12
1
Restricting Access to Samba Shared Printers?
Is it possible (and if so, how) within Samba to restrict printers to be using by only certain users/groups? We have a printer dedicated to printing our checks that was using one of those '4 PCs -> 1 printer' devices. We've been constantly having problems with transmissions getting garbled when using the printer sharer (everything's fine if a PC is directly connected), and
2015 Aug 04
8
EFI: HP + syslinux = crash
On 04-08-15 17:38, Oscar Roozen wrote: > Okay, the code in efi/ uses Print() from gnu_efi, but generic code from > core/ like core/elflink/load_env32.c prints their messages and debugging > stuff using printf(). These messages end up nowhere. This may explain > why I never saw anything beyond a certain point, even with debugging > turned on. I was busy adding some code to dprintf.h
2015 Aug 05
0
EFI: HP + syslinux = crash
>>> Okay, the code in efi/ uses Print() from gnu_efi, but generic code from core/ like core/elflink/load_env32.c prints their messages and debugging stuff using printf(). These messages end up nowhere. This may explain why I never saw anything beyond a certain point, even with debugging turned on. <<< isn't it redirected at all?? >>> I was busy adding some
2015 Aug 05
3
EFI: HP + syslinux = crash
On 05-08-15 12:05, Gene Cumm wrote: > > I recompiled with this in mk/devel.mk <http://devel.mk>: > > GCCWARN += -DDEBUG_PORT=0x2f8 -DCORE_DEBUG=1 > > 0x2f8 is a BIOSism. Is this a problem? The example in the comments said 0x3f8 which is COM1.
2011 Jun 09
1
[printer]
Hello, I have configured samba as a PDC for Windows XP machines. It is running as domain. I haven't configured security = paramter but I assume it defaults to value 'user' . In this case if I have to share ALL printers on this system for anonymous printing, can I use security = share inside [printer] section and guest = ok then will it allow printing from local accounts on windows XP
2015 Aug 04
2
EFI: HP + syslinux = crash
On 04-08-15 14:42, Patrick Masotta wrote: > I think we solved a bug but we found a new one. > AFAIK you were not able to retrieve anything after loading syslinux.efi > Now you retrieve ldlinux.e32, libcom32.c32, etc but it crashes when loading a png. > If this is the case then the multi-nic issue is solved; the new code is able to > find the NIC that booted syslinux.efi and then
2000 Apr 03
0
2.0.7pre3: misc issues
...> The setting of the writeable parameter doesn't seem to have any effect > on access to the printer so what does setting writeable = no actually > do? it doesn't do anything :) ---------- if this is true then the following example, and its comment, in man smb.conf [aprinter] path = /usr/spool/public writeable = false printable = true guest ok = true is misleading. The same is true for occurrences in PRINTER_DRIVER.txt and Faxing.txt. I think it's better to take out every writable/read only/write o...
2000 Mar 18
3
Samba 2.0.7pre2 snapshot released.
Hi all, I just released Samba 2.0.7pre2, available from : ftp://samba.org/pub/samba/alpha/samba-2.0.7pre2.tar.gz This is the second snapshot of the code that should become the official Samba 2.0.7 and is feature complete (ie. I'm only going to accept bug fixes, not more features). This is *not* production code, but should work well as a file and print server, and contains fixes for all