Solved

How to configure a scanner Epson Perfection 1670 on Suse 9.1

Posted on 2004-10-11
69
987 Views
Last Modified: 2013-12-27
I have a scanner Epson Perfection 1670 and my distro is Suse 9.1. Please can you tell me how to configure it. When i log in as a root the scanner works. But if a log in as user the scanner doesn't work. I would need an instruction step by step.
Regards
0
Comment
Question by:Anro50
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 35
  • 34
69 Comments
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12277483
You have a problem with file permissions: When you are running as root user, you can access all files and devices. As normal user the USB device that is associated with the scanner is not accessible to you. You can fix this by adding a line to one of the hotplug configuration files so that the next time you connect this scanner, the hotplug system will make the device read and writeable for the user who owns the Desktop.

The file you need to change is:  /etc/hotplug/usb/sane-hardcoded.usermap
I'm not at my Linux system right now, so I cannot give you step by step instructions. If you can wait a few hours. I'll be back with more information.
0
 

Author Comment

by:Anro50
ID: 12278033
ok. I wait. thank you very much
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12283081
Sorry for the delay, it took me a bit longer to get access to my Linux machine.

Open the file /etc/hotplug/usb/sane-hardcoded.usermap and add the following line:

desktopdev 0x0003 0x04b8 0x011f 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0

You may have to restart the hotplug service. To do this, run the following command as root:

/etc/init.d/hotplug restart

After that, reconnect your scanner (or powercycle the scanner). Can you now scan as normal user?

0
Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

 

Author Comment

by:Anro50
ID: 12288895
No... I am sorry but it doesn't work. The scanner is always dead as user.
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12289007
Is it possible that you have two Sane installations on your system (e.g. one from SuSE and one compiled from sources)?

Try this in a terminal window:

export SANE_DEBUG_SNAPSCAN=128
scanimage > /tmp/scan.log 2>&1

Look through the file /tmp/scan.log for any indication of an error and post e.g. 20 lines before the error, and maybe 5 lines after the error. If you end up with an empty file, try the same as root user and see if you get any content in this file. If you do, this would be another indication for two Sane installations.
0
 

Author Comment

by:Anro50
ID: 12289712
The file scan.log in /tmp is empy. Anyway I have only one sane. Sane 1.0.14 after updating from 1.0.13-73.
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12290900
How did you update? Did you compile the software yourself? If so, did you remove 1.0.13 before you installed the new version?
0
 

Author Comment

by:Anro50
ID: 12292172
No. I updated via rpm. This is the change I made in snapscan.conf:

#------------------------------ General -----------------------------------

# Change to the fully qualified filename of your firmware file, if
# firmware upload is needed by the scanner
firmware /usr/share/esfw30.bin

# If not automatically found you may manually specify a device name.

# For USB scanners also specify bus=usb, e.g.
/dev/usb/scanner0 bus=usb

# For SCSI scanners specify the generic device, e.g. /dev/sg0 on Linux.
# /dev/sg0

#---------------------------------------------------------------------------
# No changes should be necessary below this line


And the same I did in snapscan.conf.rpmnew (which is the file that appeared in /etc/sane.d after updating:

#------------------------------ General -----------------------------------

# Change to the fully qualified filename of your firmware file, if
# firmware upload is needed by the scanner
firmware /usr/share/esfw30.bin

# If not automatically found you may manually specify a device name.

# For USB scanners also specify bus=usb, e.g.
/dev/usb/scanner0 bus=usb

# For SCSI scanners specify the generic device, e.g. /dev/sg0 on Linux.
# /dev/sg0

#---------------------------------------------------------------------------
# No changes should be necessary below this line
#-
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12292604
OK, let's find out why the backend does not get loaded. The backends are loaded by a "meta backend", which is called DLL. All Sane modules provide debugging information, so we can also collect debug information from the DLL backend:

export SANE_DEBUG_DLL=128
scanimage > /tmp/dll.log 2>&1

This should give you about 20 lines or so of output. Please post the complete output here.
0
 

Author Comment

by:Anro50
ID: 12299783
That's the /tmp/dll.log :

[snapscan] Scanner warming up - waiting 10 seconds.
[snapscan] Scanner warming up - waiting 35 seconds.
P6
# SANE data follows
2552 3507
255

What is odd to me is that the file is 25.6MB, but there are only those lines. The rest of the file is empty.

Otherwise, the file scan.log is empty

What about uninstall sane.rpm and try the tar.gz ?
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12303257
This does not make any sense. With SANE_DEBUG_DLL set, you should get something like this (this is with the EPSON backend, so it's different from what you should see, but your output should be similar):

khk@specht:~> scanimage
[sanei_debug] Setting debug level of dll to 128.
[dll] sane_init: SANE dll backend version 1.0.11 from sane-backends 1.0.14
[dll] sane_init: reading dll.conf
[dll] add_backend: adding backend `epson'
[dll] sane_get_devices
[dll] load: searching backend `epson' in `/usr/lib/sane'
[dll] load: trying to load `/usr/lib/sane/libsane-epson.so.1'
[dll] load: dlopen()ing `/usr/lib/sane/libsane-epson.so.1'
[dll] init: initializing backend `epson'
[dll] init: backend `epson' is version 1.0.242
[dll] sane_get_devices: found 0 devices
scanimage: no SANE devices found
[dll] sane_exit: exiting
[dll] sane_exit: calling backend `epson's exit function
[dll] sane_exit: finished


Try this instead:

env SANE_DEBUG_DLL=128 scanimage > /tmp/dll.log 2>&1

The output you provided is from a successful scan. This is why your file is so big, it does contain binary information that was retrieved from the scanner.



0
 

Author Comment

by:Anro50
ID: 12306543
Here is the content of /tmp/dll.log after env SANE_DEBUG_DLL=128 scanimage > /tmp/dll.log 2>&1 from the shell as root:

[sanei_debug] Setting debug level of dll to 128.
[dll] sane_init: SANE dll backend version 1.0.10 from sane-backends 1.0.14
[dll] sane_init: reading dll.conf
[dll] add_backend: adding backend `avision'
[dll] add_backend: adding backend `snapscan'
[dll] sane_get_devices
[dll] load: searching backend `snapscan' in `/usr/lib/sane'
[dll] load: trying to load `/usr/lib/sane/libsane-snapscan.so.1'
[dll] load: dlopen()ing `/usr/lib/sane/libsane-snapscan.so.1'
[dll] init: initializing backend `snapscan'
[dll] init: backend `snapscan' is version 1.4.37
[dll] load: searching backend `avision' in `/usr/lib/sane'
[dll] load: trying to load `/usr/lib/sane/libsane-avision.so.1'
[dll] load: dlopen()ing `/usr/lib/sane/libsane-avision.so.1'
[dll] init: initializing backend `avision'
[dll] init: backend `avision' is version 1.0.92
[dll] sane_get_devices: found 1 devices
[dll] sane_open: trying to open `snapscan:libusb:004:002'
[snapscan] Scanner warming up - waiting 10 seconds.
[snapscan] Scanner warming up - waiting 35 seconds.
[dll] sane_open: open successful
[dll] sane_control_option(handle=0x80536a8,option=0,action=0,value=0xbfff61f0,info=(nil))
[dll] sane_control_option(handle=0x80536a8,option=0,action=0,value=0xbfff6158,info=(nil))
[dll] sane_get_option_descriptor(handle=0x80536a8,option=0)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=1)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=2)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=3)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=4)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=5)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=6)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=7)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=8)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=9)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=10)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=11)
[dll] sane_control_option(handle=0x80536a8,option=11,action=0,value=0x8050458,info=(nil))
[dll] sane_get_option_descriptor(handle=0x80536a8,option=12)
[dll] sane_control_option(handle=0x80536a8,option=12,action=0,value=0x805045c,info=(nil))
[dll] sane_get_option_descriptor(handle=0x80536a8,option=13)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=14)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=15)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=16)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=17)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=18)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=19)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=20)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=21)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=22)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=23)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=24)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=25)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=26)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=27)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=28)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=29)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=30)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=31)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=32)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=33)
[dll] sane_get_option_descriptor(handle=0x80536a8,option=34)
[dll] sane_control_option(handle=0x80536a8,option=9,action=0,value=0xbfff6154,info=(nil))
[dll] sane_control_option(handle=0x80536a8,option=10,action=0,value=0xbfff6154,info=(nil))
[dll] sane_control_option(handle=0x80536a8,option=9,action=0,value=0xbfff61ec,info=(nil))
[dll] sane_get_option_descriptor(handle=0x80536a8,option=11)
[dll] sane_control_option(handle=0x80536a8,option=11,action=1,value=0xbfff61e8,info=0xbfff6158)
[dll] sane_control_option(handle=0x80536a8,option=10,action=0,value=0xbfff61ec,info=(nil))
[dll] sane_get_option_descriptor(handle=0x80536a8,option=12)
[dll] sane_control_option(handle=0x80536a8,option=12,action=1,value=0xbfff61e8,info=0xbfff6158)
[dll] sane_start(handle=0x80536a8)
[dll] sane_get_parameters(handle=0x80536a8,params=0xbfff6220)
[dll] sane_read(handle=0x80536a8,data=0xbfff6240,maxlen=32768,lenp=0xbfff61e0)
P6
# SANE data follows
2552 3507
255
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12306650
The scanner works. Did you do this as normal user?

With which program does scanning as normal user not work?
0
 

Author Comment

by:Anro50
ID: 12306692
I did it as root. As normal user the shell told me i had no permission.
I use xsane and kooka.

I would have liked to post the content of /usr/lib/sane/libsane-snapscan.so.1 but i can't copy/paste it.
It is a bit odd to me. The vendor and the type of scanner are not recognized.

I have tried also to comment avison in dll.config and uncomment epson. But it doesn't work.
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12307006
We know that it works as root user, so the log does not provide any information about why it fails when you run it as normal user.

What exactly is the error message you get when you run this as normal user? The 1670 uses the snapscan backend and not the epson backend. This means the only backend you need to uncomment in dll.config is "snapscan".

There is no value in pasting the contents of /usr/lib/sane/libsane-snapscan.so.1 - this is a dynamic library, a binary file.

Again, what's the exact error message you get. What do you get when you run this command as normal user:

env SANE_DEBUG_DLL=128 xsane > /tmp/dll.log 2>&1

(Or, use kooka instead of xsane).
0
 

Author Comment

by:Anro50
ID: 12307329
tonio@linux:~> env SANE_DEBUG_DLL=128 xsane > /tmp/dll.log 2>&1
bash: /tmp/dll.log: Permission denied
tonio@linux:~>

xsane: it opens a small window with the message: No Devices Avaible. The programm doesn't start.

Kooka: the programm starts but the box on the down left is empty.
0
 

Author Comment

by:Anro50
ID: 12307345
tonio@linux:~> kooka
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+I) to an unnamed action.
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+H) to an unnamed action.
QLayout: Adding QComboBox/PREVIEWFORMATCOMBO (child of QVButtonGroup/unnamed) to layout for Previewer/unnamed
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12307368
The error message is because you initially run this as root, so the file /tmp/dll.log is owned by root and you as a normal user cannot write to it. You can either remove the file as root user before you start this, or just use a different file name (e.g. use ... > /tmp/dll_2.log 2>&1)

Both programs don't find any scanners, and by having the log file we can probably figure out why.
0
 

Author Comment

by:Anro50
ID: 12308181
I renamed the /tmp/dll.log file as root. Then rebooted. Then tried kooka again as normal user. Nothing:

tonio@linux:~> kooka
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut                                            (Ctrl+I) to an unnamed action.
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut                                            (Ctrl+H) to an unnamed action.
QLayout: Adding QComboBox/PREVIEWFORMATCOMBO (child of QVButtonGroup/unnamed) to                                            layout for Previewer/unnamed

Idem with xsane: No Devices Available
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12308348
You need to use the command from above:

env SANE_DEBUG_DLL=128 kooka > /tmp/dll.log 2>&1
0
 

Author Comment

by:Anro50
ID: 12309315
Nothing. As normal user:

tonio@linux:~> env SANE_DEBUG_DLL=128 kooka > /tmp/dll.log 2>&1
tonio@linux:~>

The programm starts but the box on the down left is empty
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12309375
What's in the file /tmp/dll.log?
0
 

Author Comment

by:Anro50
ID: 12309871
[sanei_debug] Setting debug level of dll to 128.
[dll] sane_init: SANE dll backend version 1.0.10 from sane-backends 1.0.14
[dll] sane_init: reading dll.conf
[dll] add_backend: adding backend `snapscan'
[dll] sane_get_devices
[dll] load: searching backend `snapscan' in `/usr/lib/sane'
[dll] load: trying to load `/usr/lib/sane/libsane-snapscan.so.1'
[dll] load: dlopen()ing `/usr/lib/sane/libsane-snapscan.so.1'
[dll] init: initializing backend `snapscan'
[dll] init: backend `snapscan' is version 1.4.37
[dll] sane_get_devices: found 0 devices
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+I) to an unnamed action.
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+H) to an unnamed action.
QLayout: Adding QComboBox/PREVIEWFORMATCOMBO (child of QVButtonGroup/unnamed) to layout for Previewer/unnamed
[dll] sane_exit: exiting
[dll] sane_exit: calling backend `snapscan's exit function
[dll] sane_exit: finished
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12310299
Good. this shows that it's using the correct backend, which is sucessfully loaded.

Now try this:
env SANE_DEBUG_SNAPSCAN=128 kooka > /tmp/dll.log 2>&1

What does this print in /tmp/dll.log?
0
 

Author Comment

by:Anro50
ID: 12310567
[sanei_debug] Setting debug level of snapscan to 128.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.37
[snapscan] add_usb_device(/dev/usb/scanner0 bus=usb)
[snapscan] add_usb_device: Detected (kind of) an USB device
[snapscan] snapscani_usb_open(/dev/usb/scanner0)
[snapscan] add_usb_device: error opening device /dev/usb/scanner0: Invalid argument
[snapscan] add_usb_device(libusb:001:002)
[snapscan] add_usb_device: Detected (kind of) an USB device
[snapscan] snapscani_usb_open(libusb:001:002)
[snapscan] add_usb_device: error opening device libusb:001:002: Access to resource has been denied
[snapscan] sane_snapscan_get_devices (0xbfffee18, 0)
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+I) to an unnamed action.
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+H) to an unnamed action.
QLayout: Adding QComboBox/PREVIEWFORMATCOMBO (child of QVButtonGroup/unnamed) to layout for Previewer/unnamed
[snapscan] sane_snapscan_exit
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12314155
Run this command as root:
chmod 666 /dev/usb/scanner0

Does this fix your problem?
0
 

Author Comment

by:Anro50
ID: 12320007
No ...
0
 

Author Comment

by:Anro50
ID: 12320055
That's what I got from /tmp/dll.log after:

- chmod 666 /dev/usb/scanner0

- reboot

- tried xsane and Kooka

[sanei_debug] Setting debug level of snapscan to 128.
[snapscan] sane_snapscan_init
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.37
[snapscan] add_usb_device(/dev/usb/scanner0 bus=usb)
[snapscan] add_usb_device: Detected (kind of) an USB device
[snapscan] snapscani_usb_open(/dev/usb/scanner0)
[snapscan] add_usb_device: error opening device /dev/usb/scanner0: Invalid argument
[snapscan] add_usb_device(libusb:001:002)
[snapscan] add_usb_device: Detected (kind of) an USB device
[snapscan] snapscani_usb_open(libusb:001:002)
[snapscan] add_usb_device: error opening device libusb:001:002: Access to resource has been denied
[snapscan] sane_snapscan_get_devices (0xbfffee18, 0)
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+I) to an unnamed action.
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+H) to an unnamed action.
QLayout: Adding QComboBox/PREVIEWFORMATCOMBO (child of QVButtonGroup/unnamed) to layout for Previewer/unnamed
[snapscan] sane_snapscan_exit
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12325206
Sorry for the delay. We now know that the scanner is not accessed with the /dev/usb/scanner0 device file, but instead with the libusb:001:002 device. This is managed by the resource manager in SuSE 9.1. Please run the following command as normal user to see which devices you should have access to:

/sbin/resmgr list

Does this list /proc/bus/usb/001/002 ? (This is the USB device that corresponds with libusb:001:002). If not, there is something wrong with the desktopdev program, that's supposed to register this device for you.

Just one more thing: You are running the scanner program as the user who's logged into the KDE Desktop?
0
 

Author Comment

by:Anro50
ID: 12328511
tonio@linux:~> /sbin/resmgr list
rw-- /dev/audio
rw-- /dev/mixer
rw-- /dev/dsp
rw-- /dev/sequencer
rw-- /dev/video
rw-- /dev/modem
rw-p /dev/cdrom
rw-p /dev/cdrom1
rw-- /dev/cdrecorder
rw-p /dev/dvd
rw-p /dev/dvd1
rw-- /dev/sr0
rw-- /dev/sr1
rw-- /dev/sr2
rw-- /dev/sr3
rws- /dev/scanner
r--- /dev/console
rw-- /dev/pilot
tonio@linux:~>

And yes I always run the scanner program (kooka or xsane) as the user who has logged into the KDE Desktop
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12330750
This shows that the scanner is not part of the devices that you have access to, but it also shows that the resmgr is running.

Try the following: With the scanner connected, run the command scanimage -L command to get the libusb device name (e.g. libusb:001:002). Convert this device name to a path (e.g. /proc/bus/usb/001/002 for this example. You start with /proc/bus/usb/ and add the two numbers that scanimage -L reports with a '/' as delimiter). Then run the following command as root user:

 /sbin/resmgr add /proc/bus/usb/001/002 desktop usb

Then try to scan as normal user again. Does this work? The scanner should now also be reported when you run the resmgr list command.

This should be taken care of automatically by the hotplug script /etc/hotplug/usb/desktopdev, which should be triggered by the line that you added to /etc/hotplug/usb/sane-hardcoded.usermap. Can you please make sure that you added the line correctly to this file. You can also email the complete file to me. You can find my email address on my profile page (just click on my user name that's printed with every comment).
0
 

Author Comment

by:Anro50
ID: 12341376
Sorry but it doesn't work. At this point I think that the best and more comfortable solution is a sort of on-fly configuration. Once that the snapscan.conf file is configured with the right path to the firmware, if you need use kooka or xsane you just open the Superuser Control Center with su and give permission to the folder "usb" in /proc/bus/. It takes less than a minute and when you exit and are back as normal user, xsane and kooka work perfectly well. Anyway: i think also that this is a bug in Suse 9.1.
Which file do you need ? sane-hardcoded.usermap ?
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12341429
I can assure you that this is not a bug in SuSE 9.1. It works for me without any problems (with several EPSON scanners).

Yes, I asked for sane-hardcoded.usermap (this is the file wher you should have added the entry for your scanner).
0
 

Author Comment

by:Anro50
ID: 12346689
maybe I didn't understand. After running
/sbin/resmgr add /proc/bus/usb/004/002 desktop usb (004:002 beeing the entry of my scanner)

shall I add the line
/proc/bus/usb/004/002

in the file
sane-hardcoded.usermap ?
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12351385
No, I was talking about the line that I gave you in my second comment (10/11).
0
 

Author Comment

by:Anro50
ID: 12352267
Ok. I am sorry but the scanner is always dead. I will send you the file as soon as the mail server is up again. It seems down right now.
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12352584
I got the file, and it's OK. The record for your scanner was already in the file, but adding it a second time does not hurt.

Let's find out why the resmgr is not working. When you run the command from above, what happens? Do you get an error message? Does the output of /sbin/resmgr list change?
0
 

Author Comment

by:Anro50
ID: 12356141
tonio@linux:~> su
Password:
linux:/home/Tonio # /sbin/resmgr add /proc/bus/usb/004/002 desktop usb
success
linux:/home/Tonio # exit
exit
tonio@linux:~> /sbin/resmgr list
rw-- /dev/audio
rw-- /dev/mixer
rw-- /dev/dsp
rw-- /dev/sequencer
rw-- /dev/video
rw-- /dev/modem
rw-p /dev/cdrom
rw-p /dev/cdrom1
rw-- /dev/cdrecorder
rw-p /dev/dvd
rw-p /dev/dvd1
rw-- /dev/sr0
rw-- /dev/sr1
rw-- /dev/sr2
rw-- /dev/sr3
rws- /dev/scanner
r--- /dev/console
rw-- /dev/pilot
rw-- /proc/bus/usb/004/002
tonio@linux:~> kooka
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+I) to an unnamed action.
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+H) to an unnamed action.
QLayout: Adding QComboBox/PREVIEWFORMATCOMBO (child of QVButtonGroup/unnamed) to layout for Previewer/unnamed
[snapscan] Scanner warming up - waiting 10 seconds.
[snapscan] Scanner warming up - waiting 35 seconds.
libkscan: WARNING: Trying to copy a not healty option
libkscan: WARNING: Trying to copy a not healty option

and the scanner works. But when I roboot:

tonio@linux:~> kooka
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+I) to an unnamed action.
kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Ctrl+H) to an unnamed action.
QLayout: Adding QComboBox/PREVIEWFORMATCOMBO (child of QVButtonGroup/unnamed) to layout for Previewer/unnamed

and it doesn't work anymore.
0
 

Author Comment

by:Anro50
ID: 12356158
Sorry, I forgot to add

tonio@linux:~> /sbin/resmgr list
rw-- /dev/audio
rw-- /dev/mixer
rw-- /dev/dsp
rw-- /dev/sequencer
rw-- /dev/video
rw-- /dev/modem
rw-p /dev/cdrom
rw-p /dev/cdrom1
rw-- /dev/cdrecorder
rw-p /dev/dvd
rw-p /dev/dvd1
rw-- /dev/sr0
rw-- /dev/sr1
rw-- /dev/sr2
rw-- /dev/sr3
rws- /dev/scanner
r--- /dev/console
rw-- /dev/pilot
tonio@linux:~>:
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12358849
Good, so resmgr does work. The next question is why does this command not get executed when you connect your scanner?

Can you please check the file /etc/hotplug/usb/desktopdev and see if you find the resmgr command in there.
0
 

Author Comment

by:Anro50
ID: 12360811
#!/bin/bash
# This adds a USB device to the "desktop usb" group.
# You just need to create an entry "desktopdev ..." in a usermap file
# and it will be picked up automatically.

if [ -x /sbin/resmgr -a ! -z "$DEVICE" ]; then
      if [ "${ACTION}" = "add" ]; then
            /sbin/resmgr ${ACTION} ${DEVICE} desktop usb && exit 0
      else
            /sbin/resmgr ${ACTION} ${DEVICE} desktop && exit 0
      fi
fi
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12363466
What does this command print?
cat /proc/sys/kernel/hotplug

(It should be /sbin/hotplug). Does the path that's printed exist?

Run the following command as root:
/etc/init.d/hotplug restart

Do you get any error messages?
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12363493
You can enable debugging for the hotplug system by editing the file /etc/sysconfig/hotplug
You need to be root to edit the file. Set the variable HOTPLUG_DEBUG to "yes". To keep the hotplug messages separate from the other system messages, you can also set the HOTPLUG_SYSLOG variable to "file". All messages will then be written to the file /var/run/hotplug.
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12363497
Forgot to ask my question: What messages do you see when you plug the scanner in?
0
 

Author Comment

by:Anro50
ID: 12363806
tonio@linux:~> cat /proc/sys/kernel/hotplug
/sbin/hotplug
tonio@linux:~> su
Password:
linux:/home/Tonio # /etc/init.d/hotplug restart
disabling Hotplug                                                    done
enabling Hotplug                                                     done
linux:/home/Tonio #

When I plug the scanner in I don't get any message
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12364402
Not even in the log file (which BTW is /var/log/hotplug.log and _NOT_ /var/run/hotplug as I stated in an earlier comment - never believe the comments in a config file :-) ?



0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12364413
You should (with a lot of other messges) see something like this:

/etc/hotplug/usb.agent[2409] Setup 'desktopdev ' for 'USB product 4b8/806/100' (from /etc/hotplug/usb/sane-hardcoded.usermap)

(of course with a different product ID).
0
 

Author Comment

by:Anro50
ID: 12368197
Difficult to find :). I tried to find the error messages. Are those ones ?

/etc/hotplug/usb.agent[2739] Loading of desktopdev skipped, because we have module 'desktopdev' already loaded
/etc/hotplug/usb.agent[2739] No drivers for 'USB product 4b8/11f/110' (from /etc/hotplug/usb/tascam_fw.usermap)/etc/hotplug/usb.agent[2739]

Setup 'desktopdev desktopdev ' for 'USB product 4b8/11f/110' (from /etc/hotplug/usb/sane-hardcoded.usermap)

/etc/hotplug/usb.agent[2739] No drivers for 'USB product 4b8/11f/110' (from /lib/modules/2.6.5-7.108-default/modules.usbmap)
/etc/hotplug/usb.agent[2739] No drivers for 'USB product 4b8/11f/110' (from /etc/hotplug/usb.usermap)
/etc/hotplug/usb.agent[2739] No drivers for 'USB product 4b8/11f/110' (from /etc/hotplug/usb/ISDN.usermap)

/etc/hotplug/usb.agent[2739] No drivers for 'USB product 4b8/11f/110' (from /etc/hotplug/usb.handmap)

/etc/hotplug/ieee1394.agent: line 22: VENDOR_ID: Bad invocation: $VENDOR_ID is not set
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12368348
Yes, these are the messages. When you edit the file in sysconfig, it's easier to find them because all of the hotplug messages will then be written to one log  file. After the line that starts with "Setup ...", do you see a line that looks identical, but starts with "Run..." ?
I'm not sure where the error message in the last line comes from. The scanner is a USB device, and the Firewire subsystem should not get envolved.
0
 

Author Comment

by:Anro50
ID: 12369023
Maybe you mean this one:

/etc/hotplug/usb.agent[2739] Setup 'desktopdev desktopdev ' for 'USB product 4b8/11f/110' (from /etc/hotplug/usb/sane-hardcoded.usermap)
/etc/hotplug/usb.agent[2739] Run 'usb/desktopdev' for 'USB product 4b8/11f/110' (from /etc/hotplug/usb/sane-hardcoded.usermap)
Unable to connect to resource manager: Connection refused
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12369750
Now we're getting somewhere... I've never seen this before, but I'll investigate.
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12375911
I only found one reference to this error message, and it's in German: http://lists.suse.com/archive/suse-linux/2003-Sep/4070.html
The proposed workaround is to add a line to /etc/resmgr.conf to explicitly allow access for your own user id:
You can do this by adding this line:
allow desktop user=user_id
Replace user_id with your user name. According to the page you need to log out and back in again to activate this.

If this does not work, do this to see if resmgr is running:

ps auxww | grep resmgr
Do you see something like this? There may be more output.
root      1748  0.0  0.0  1588  664 ?        Ss   Oct20   0:02 /sbin/resmgrd
0
 

Author Comment

by:Anro50
ID: 12379135
I added the line :

# This is the default set of devices people logged in on the desktop get
# access to:
class desktop
allow desktop user=tonio

but it doesn't work :(

this is the output :

tonio@linux:~> ps auxww | grep resmgr
root      4028  0.0  0.2  1588  664 ?        Ss   12:17   0:00 /sbin/resmgrd
root      4153  0.0  0.5  2600 1252 ?        S    12:17   0:00 /usr/sbin/powersaved -d -e /etc/powersave.conf -a resmgr -v 3
root      5146  1.3  7.5 30660 18676 ?       S    12:19   0:01 kdeinit: kwrite /etc/resmgr.conf
tonio     5243  0.0  0.2  2616  736 pts/3    R+   12:20   0:00 grep resmgr
tonio@linux:~>
0
 

Author Comment

by:Anro50
ID: 12379161
Shall I add that I don't see any reference to usb scanner in /etc/resmgr.conf ? This is the whole file.

# This is the default set of devices people logged in on the desktop get
# access to:
class desktop
allow desktop user=tonio
#
# Standard multimedia devices
add /dev/audio            desktop
add /dev/mixer            desktop
add /dev/dsp            desktop
add /dev/sequencer      desktop
add /dev/video            desktop
#
# Modem device
add /dev/modem         desktop
#
# CD-ROMs - giving permission to open the corresponding SCSI
# device is highly useful for CD writers such as cdrecord.
add /dev/cdrom            desktop paride
add /dev/cdrom1            desktop paride
add /dev/cdrecorder      desktop
add /dev/dvd            desktop paride
add /dev/dvd1            desktop paride
add /dev/sr0            desktop
add /dev/sr1            desktop
add /dev/sr2            desktop
add /dev/sr3            desktop
#
# Dito for SCSI scanners, which all use /dev/scanner symlink.
add /dev/scanner      desktop scsi
#
# make /dev/console accessible read-only
add /dev/console   desktop read-only
#
# Allow access for pilot utils
add /dev/pilot            desktop

#
# This rule grants access to users logged in locally
#
allow desktop          tty=/dev/tty[1-9]* || tty=tty[1-9]* || tty=:0

# For serial gphoto cameras.
# add /dev/ttyS0 desktop
# add /dev/ttyS1 desktop
#
# Sample rules, do not enable by default:
#
# This rule denies access to users uucp and news
#
# deny  desktop            user=uucp || user=news
#
# This rule gives access to all members of group wheel
#
# allow      desktop            group=wheel
#
# To make resmgr work with ssh, for instance, add the following
# line to /etc/pam.d/sshd:
#       session    optional   pam_resmgr.so fake_ttyname
# When a user logs in, a resmgr session will be opened, and
# access will be granted automaticially to all resource classes
# matched via access control statements in resmgr.conf.
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12379193
The scanner is not handled automatically, because there is no standard path for the scanner device (it always contains the  vendor ID and product ID). The config file only contains "simple" paths (e.g. /dev/pilot), for dynamic paths you use a mechanism like the script /etc/hotplug/usb/desktopdev.

I'll keep on looking. I'm sorry that we have not come up with a solution yet. Did you add any software to your system that did not come from the SuSE CD/DVD/ftp site?
0
 

Author Comment

by:Anro50
ID: 12380694
Don't worry khkremer :) I appreciate very much your kindness and patience in dealing this problem (and I always have the solution at hand: launch the super user File Manager and give permission to the "usb" folder in /proc/bus/). Shall I add that I have the same problem with a scanner Epson Perfection 1260Photo in a Desk pc with Suse 9.1 which worked perfectly well when I used Mandrake 9.2 ? But leave this problem alone.

Anyway: yes I installed some programs - Lopster, Vlc, Mplayer, Xmule, Overnet (eDonkey) - and most of them were downloaded from the site of Packman, e.g they are Suse rpm. I didn't install any tar.gz program. Anyway: the scanner didn't work already *before* I installed anything
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12385957
Did you setup your scanner with Yast, or did you configure Sane manually? I think I run YaST's scanner configuration once when I first installed it. Maybe it's doing something with the system that is not done when you just configure Sane manually... Again, I'm running 9.1 and I have a number of EPSON scanners connected, and they all get configured correctly for the Desktop user.
0
 

Author Comment

by:Anro50
ID: 12387764
Yes I set up the scanner with Yast, but I got a message about the firmware which has to be loaded. That' what I did adding the path to the firmware in /etc/sane.d/snapscan.conf
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12419788
I haven't abandoned this question. I'm actually in contact with somebody from SuSE to get some more information. Stay tuned.
0
 

Author Comment

by:Anro50
ID: 12419948
Ok. Thank you very much.
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12426942
Here is a workaround:
Edit the file /etc/hotplug/usb/sane-hardcoded.usermap and replace desktopdev with scanner and create a new file /etc/hotplug/usb/scanner with this content:

#!/bin/bash

if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
then
        chown root "${DEVICE}"
        chgrp scanner "${DEVICE}"
        chmod 660 "${DEVICE}"
fi


Make the file executable (chmod 755 scanner). This script assumes that your computer knows about a group named "scanner", add this to the file /etc/group, give it a unique group id (the number after the password entry). Mine looks like this:

scanner:x:102:root,khk

If you don't want to mess with the group setting, you could also use 777 as file mode, and remove the chgrp line.


You can find some background information on this page that I created for older versions of SuSE (never thought that this is still useful :-)
http://khk.net/sane/libusb.html

This shold at least make the scanner accessible for a normal user again. It's still not a fix for the problems with resmgr, but you probably don't insist on fixing this :-)
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12426981
AAARRRGGGHHH... I screwed up the first sentence of the instructions I just gave you:

It's supposed to read: Edit the file /etc/hotplug/usb/sane-hardcoded.usermap and replace "desktopdev" with "scanner" for the entry for your scanner (you had two records for your scanner, you can remove one and just modify the other) and create a new file /etc/hotplug/usb/scanner with this content:

Sorry about this.
0
 

Author Comment

by:Anro50
ID: 12432313
Following your instructions what I did is this:

- in /etc/hotplug/usb/sane -hardcoded.usermap I add the line

scanner 0x0003 0x04b8 0x011f 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0

and deleted the second line:

desktopdev 0x0003 0x04b8 0x011f 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0

then I created a new file in /etc/hotplug/usb/ called "scanner" and typed into it :

#!/bin/bash

if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
then
        chown root "${DEVICE}"
        chgrp scanner "${DEVICE}"
        chmod 660 "${DEVICE}"
fi

so I have a script for the shell.

Now I have to menage the file "group" in /etc/. But I didn't understand what I have to do. This is the content of the file:

root:x:0:
bin:x:1:daemon
daemon:x:2:
sys:x:3:
tty:x:5:
disk:x:6:
lp:x:7:
www:x:8:
kmem:x:9:
wheel:x:10:
mail:x:12:
news:x:13:
uucp:x:14:tonio
shadow:x:15:
dialout:x:16:tonio
audio:x:17:tonio
floppy:x:19:
cdrom:x:20:
console:x:21:
utmp:x:22:
at:x:25:
public:x:32:
video:x:33:tonio
games:x:40:
xok:x:41:
trusted:x:42:
modem:x:43:
ftp:x:49:
postfix:x:51:
maildrop:x:59:
man:x:62:
sshd:x:65:
ntadmin:x:71:
nobody:x:65533:nobody
nogroup:x:65534:nobody
users:x:100:

Can you please tell me exactly what I have to do  ?  
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12432425
As I said, if you don't want to mess with the groups file, just use this script:

#!/bin/bash

if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
then
        chown root "${DEVICE}"
        chmod 666 "${DEVICE}"
fi


[ I wrote "777", but "666" is good enough, we don't need the execute bit set. ]

This will change the owner of the device to root, and the file mode to 666 whenever the scanner is connected.

From your description, it's not clear if you've removed both instances of the record for your scanner. There was one in the first line, and then one more in the block of EPSON devcies (device ID 0x4b8) - this is from the email you sent me. If you need more help with this, let me know. If you are not sure, you could actually remove all other entries from this file but the one that you just created: If you are not planning on using any other scanner, this would work. You can always restore the file from the SuSE RPM package (or, just rename the original file).
0
 

Author Comment

by:Anro50
ID: 12433057
Well. Now I have:

- one file in /etc/hotplug/usb called "scanner" with content:

#!/bin/bash

if [ "${ACTION}" = "add" ] && [ -f "${DEVICE}" ]
then
        chown root "${DEVICE}"
        chmod 666 "${DEVICE}"
fi

- one file in /etc/hotplug/usb called "sane-hardcoded.usermap" with content:

scanner 0x0003 0x04b8 0x011f 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0101 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0102 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0105 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0201 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0205 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0305 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0401 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0405 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0505 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0601 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0605 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0705 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0805 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0901 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x0a01 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x1005 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x1105 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x1205 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x1305 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x2005 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x03f0 0x2205 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0400 0x1000 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0400 0x1001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x043d 0x002d 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x043d 0x003d 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0458 0x2001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0458 0x2007 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0458 0x2008 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0458 0x2009 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0458 0x2011 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0458 0x2013 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0458 0x2015 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0458 0x2016 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0458 0x2018 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0458 0x201b 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0300 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0301 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0302 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0303 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0340 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0341 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0345 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0346 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0347 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0360 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0361 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0364 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0371 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0377 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0380 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0381 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0382 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0461 0x0383 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0475 0x0210 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x049f 0x001a 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x049f 0x0021 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x1a20 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x1a2a 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x2022 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x2040 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x2060 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x207e 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x20b0 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x20be 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x20c0 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x20de 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x20fc 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a5 0x20fe 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a7 0x0211 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a7 0x0221 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a7 0x0224 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a7 0x0224 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a7 0x0226 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a7 0x0229 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a7 0x022c 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a7 0x0231 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a7 0x0311 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a7 0x0321 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a7 0x0331 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x2201 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x2202 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x2204 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x2205 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x2206 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x2207 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x2208 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x220a 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x220b 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x220c 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0

and a file in /etc called "group" with content:

root:x:0:
bin:x:1:daemon
daemon:x:2:
sys:x:3:
tty:x:5:
disk:x:6:
lp:x:7:
www:x:8:
kmem:x:9:
wheel:x:10:
mail:x:12:
news:x:13:
uucp:x:14:tonio
shadow:x:15:
dialout:x:16:tonio
audio:x:17:tonio
floppy:x:19:
cdrom:x:20:
console:x:21:
utmp:x:22:
at:x:25:
public:x:32:
video:x:33:tonio
games:x:40:
xok:x:41:
trusted:x:42:
modem:x:43:
ftp:x:49:
postfix:x:51:
maildrop:x:59:
man:x:62:
sshd:x:65:
ntadmin:x:71:
nobody:x:65533:nobody
nogroup:x:65534:nobody
users:x:100:


Is it All Right ?

I can't reboot right now. I will tell you if it works. But did I follow in the right way your instruction ?
desktopdev 0x0003 0x04a9 0x220d 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x220e 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x220f 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x2210 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x2212 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x2213 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x2215 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04a9 0x3042 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b0 0x4000 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0101 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0102 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0103 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0104 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0105 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0106 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0107 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0109 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x010a 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x010b 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x010c 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x010e 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x010f 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0110 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0112 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0114 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x011b 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x011c 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x011d 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x011e 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0801 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04b8 0x0802 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04c5 0x1029 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04c5 0x1041 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04c5 0x1042 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04f9 0x010f 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x04f9 0x0111 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0002 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0003 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0006 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0007 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0008 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0010 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0210 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0218 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0219 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x021c 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x021d 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x021e 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0400 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0401 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0409 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x0873 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x055f 0x1000 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05cb 0x1483 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05d8 0x4001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05d8 0x4002 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05d8 0x4003 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05d8 0x4004 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05d8 0x4006 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05d8 0x4009 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x20a7 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x20c9 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x30ce 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x30cf 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x30d4 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x30d8 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x40b3 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x40b8 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x40ca 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x40cb 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x40dd 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05da 0x40ff 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05e3 0x0120 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x05e3 0x0120 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0638 0x0268 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0638 0x0a10 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0638 0x0a20 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0681 0x0005 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0681 0x0010 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0686 0x400d 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x0001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x0002 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x0100 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x2061 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x208d 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x208f 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x2091 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x2093 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x2095 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x2097 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x20fd 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06bd 0x20ff 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x06dc 0x0014 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0001 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0005 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0007 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x000f 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0010 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0011 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0012 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0013 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0014 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0015 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0016 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0017 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0400 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0401 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0403 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x07b3 0x0413 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x0a82 0x4600 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x1606 0x0010 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x1606 0x0030 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x1606 0x0060 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x1606 0x0070 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x1606 0x0130 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x1606 0x0160 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0
desktopdev 0x0003 0x1606 0x0230 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00 0x00 0x0


0
 

Author Comment

by:Anro50
ID: 12433080
sorry ! I just paste again the content of a file at the end of the message. My mistake.
0
 
LVL 44

Accepted Solution

by:
Karl Heinz Kremer earned 500 total points
ID: 12435415
Looks OK.
0
 

Author Comment

by:Anro50
ID: 12437786
BINGO ! YOU GOT IT ! It works perfectly well ! Thank you very much for all khkremer. You would deserve at least 1.000.000 points. Thank you very much again !
0
 
LVL 44

Expert Comment

by:Karl Heinz Kremer
ID: 12437852
I have no idea why SuSE makes things more complicated by using the resmgr. It works perfectly with just using the hotplug support. They probably want to make sure that you can only scan if you are logged into the console, but for most users this is not a problem.
Have fun with your scanner.
0

Featured Post

Connect further...control easier

With the ATEN CE624, you can now enjoy a high-quality visual experience powered by HDBaseT technology and the convenience of a single Cat6 cable to transmit uncompressed video with zero latency and multi-streaming for dual-view applications where remote access is required.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you are having problems installing printer drivers, or if documents repeatedly get stuck in the print queue even after re-installing the printer drivers, then follow these steps to solve the problems. Please note that the steps are shown both for…
It started not too long ago. It was at first annoying. My keystrokes seemed to be randomly generated, not the ones I typed on the keyboard. For some reason this only happened in certain applications (especially browsers such as IE11, Firefox and Chr…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question