similar to: [option] SERIAL 0 ??

The attached message is 2001, but was the top of the list in a Google search for the error message. The same solution fixed a SuSE 9.3 Samba/Cups problem for a Brother MFC 3360C printer. Thanks! Original message: Bill Schoolcraft bill at wiliweld.com Sat Dec 29 13:36:02 GMT 2001 Gustavo Courault <courault at gigared.com> has solved this for me with the following advice

Hello Family, My RedHat-7.2 box prints perfectly to an Epson777 color injet printer which I gave an IP address via a mini printserver attached to the back of the printer. I have a Windows2000 computer hooking into the same RedHat-7.2 box via Samba-2.2.2 fine. I have not been able to get my Windows2000 box to print to the Epson777 color injet via Samba. [question] Since Linux already

Hello Family, (smd.conf file attached) Having had great success with 2.2.2 and my Linux box and Windows-2000 machines I switched to CUPS and now can't print again having made some slight edits in my smb.conf file (attached) for the change to CUPS. [1] I have to reloaded all the Windows drivers again on the Windows-2000 machines and still get the "Startdoc..." error. [2] The

Hello Family, In yesterday's head thumper I had to attempt to (remotely) grab some wedding photo's for my wife from my Win2000 machine to Solaris-8 running Samba-2.2.2 The examples show the following; smbtar -s dumbo -t /dev/st0 -x windows That assumes your backing up a directory, the directory is on your (windows) C:\WINDOWS I just needed a few jpg's from another drive on my

Hello Family, I had encounted that as "user" I couldn't change my own passwd with "smbpasswd" and noticed the permission differences between smbpasswd and passwd. This is Samba-2.2.2 -rwxr-xr-x 1 root root 782415 Dec 28 03:14 /usr/local/samba/bin/smbpasswd -r-s--x--x 1 root root 12244 Feb 7 2000 /usr/bin/passwd Is there a reason why the

Hello Family, [day 2.5] Well, thanks to "Gerald (Jerry) Carter" there has been progress in attempting to print from my Windows2000 machine to my Linux machine running 2.2.2 to an Epson777 inkjet printer on the LAN with a mini print-server on the back of it. I've now got no more RED "access denied" warnings in my Win2k printer setup screen, there is a GREEN "Status:

Gustavo Courault <courault@gigared.com> has solved this for me with the following advice and I have enclosed my smb.conf file in case it may help anyone, I'm running Samba-2.2.2 and CUPS printing to a Epson-777 injet via a Edimax $40 printserver attached to the back of the printer with a static IP address assigned to the printer. My OS is RedHat-6.2 <quote> I uncomment the line

Hello Family, I'm trying to help with a problem where there is a headless/cardless server and we need to create an isolinux image that points the display to the serial port. The original machine that is using this has the ability in the bios to redirect its video to /dev/ttyS0 or such but the machines I have access to do NOT have that ability built into the bios. [question] Is there a way

Hello Family, It took my wife calling me at work to ask for some copies of our wedding pictures (trapped on Windows machine) that are next to the Solaris-8 machine I'm typing this on. Well I said, let me look for "smbmount" and I don't have it compiled on this system so I was going to recompile and saw this: --with-smbmount Include SMBMOUNT (Linux only) support (default=no)

Hello Family, Our sysadmin at work demands that no one have any Samba projects other than the single one on our network due to the "NOISE" that is emitted by Samba. [question] Can I still use the current 2.2.2 with my little test setup and not fall prey to the order to "cease and desist" Samba ? It's one Solaris-8(Intel) and Win2000 and Win98, three total machines. --

Hello Family, I'm having a hell of a time just trying to "see" the shared printer on a Win-XP(pro) box here at home. All my other Windows boxes can not only see it but print to it, my Unix family (all of the relatives) of machines are having no luck. I apologize if this is something simple for Samba has evolved so much that one barely needs to do anything to get stuff working for

Hello, ? I'm trying to configure my system such that I have a TCP port listening which will send all data it receives to a serial port. ie:?? tcp/2112? -->? /dev/ttyS0 My goal would be to be able to: Use netcat to create the listen and redirect to a serial port: ? $ nc -l 2112 > /dev/ttyS0 Then in another window, run minicom at /dev/ttyS0 Then in a 3rd window, ? $ telnet localhost

I have to reinit a firewall that can only be done from its console port, and I do not have an XP system with Hyperterminal on it. So I went through the archive and learned that minicom could do the job for me. I installed it and went to configure it (minicom -s). I can set the speeds, but the challenge is selecting the serial device. I have a Serial-to-USB dongle, and when I connect it,

hello folks! here's my situation: i've got two WTI RPB+ remote power switches (essentially a 5-port power strip which you can control via serial interface to make each of the ports switch on and off independently). they work fine; i plug a DB-9 cable into the back of my machine, fire up minicom, and i have full control. however, my eventual plan is to use these as fencing

I don't have a solution, but I do want to keep this thread alive until we get it resolved. I'm in the same situation. I can print fine, but it says that annoying message. Do you guys print to an LPD unix queue? My linux print server is sending the job to a LPD linux box that is connected to the printer local. (Our printer support requires it that way). Has anyone been able to

Hello, I have a Soekris net4501, which I'm PXE booting using pxelinux. Everything seems to be working splendidly, except for the fact that I can't seem to make pxelinux understand use the net4501's serial console port correctly. The net4501 uses the serial console as its primary interface; I'm using a null modem cable and minicom to operate with it. At boot, its startup

Hi all I have a problem switch in our data centre, which is connected to a linux server via a serial cable. I know I can / could access the switch from my Windows PC back at the office, using hyperterm, but trying to access it using minicom just doesn't seem to work. I have changed the comms in minincom to use /dev/tty0 & the baud rate to 9600, yet I can't seem to connect with

Hallo, we use XEN with IA64. The console is not redirected to /dev/ttyS0. We need this port to configure an external storage with minicom but we cannot use it. We also see with modinfo no 8250 module which should control the serial port. We use XEN 3.0.3. Is there a workaround available? regards Bernd _______________________________________________ Xen-users mailing list

I'm trying to make my little Asus eeePC 901 into a useful navigation tool that I can use on my boat. I'm running Ubuntu with the 2.6.24-21-eeepc kernel. For chart plotting I run SeaClear_2 (SC) under Wine. SC communicates as it should with my GPS via a Keyspan USB to serial dongle, both sending and receiving works with this device. I am also running the small app AISMon under Wine. This

I am having trouble sending sysrq commands over USB serial, and I'm not sure what else to check. I have two identical machines, each with usb-to-serial adapters, joined by a null modem adapter. One runs an agetty, the other minicom. I can log in over the agetty as a user and it works as expected, until I try to send a sysrq. To send a break in minicom, I type [Ctrl]+[a] then [f]. Then I