CrossOver Support - Community Forums

Important Information These are community forums and not official technical support. If you need official support: Contact Us

CrossOver Linux
Discussion about CrossOver Linux

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

How to uninstall completely a software not only the bottle.

I installed an application (SmartPix for register glicemy) in my Laptop Dell running Debian 9.0 Stretch. But it didn't work properly.. Then I uninstall it for I try to reinstall later. When I was to reinstall it says me that already have a copy in a path in the C: drive and it can't continue the new install. I need to know how to delete that path in order that I can to reinstall it. Where can I find this path in the console, like /home/nogueira/.cxoffice ? Where can I find the paht from C:\ ?
thanks in advance

The "bottles" for each application you installed in crossover are in the

/home/nogueira/.cxoffice/

path. Your "c:" drive is probably in a folder like

/home/nogueira/.cxoffice/smartpix/drive_c/

Hope this helps.

Silvio, I found those paths. So it means that if I delete folder smartpix following .cxoffice and I delete the bottle created during the install process, the app Smartpix is completely uninstalled from crossover, do you agree with me?

I think the best way to uninstall a software in Crossover is to remove the entire Smartpix bottle. Open Crossover, on the lower left panel, where you see Bottles, right-click on Smartpix bottle. Then choose delete.

After that, you can install the program again to a fresh new bottle.

Good luck!

I got curious about your case and found out the following link:

http://lglinux.blogspot.com.br/2010/10/how-to-copy-accu-chek-smartpix-data.html

So, it looks like the smartpix device behaves solely as an USB drive. That's why it doesn't need any drivers on Windows. It also means that you don't necessarily need to run their software. As far as I understood the issue, the problem is that some linux desktop managers may have problems with the case sensitiveness and fail to open a web browser to access the data.

Have you tried to access the smartpix device as an USB drive, directly on Linux?

Silvio, I visit that site and I builded the two files that He suggested. The first one I know how to run it. But the other one, lowercase.py (it seems to me a file for Python), I don't know if I need to compile it or how to run it. I tried to run the copysh.sh but it says me:

[i]nogueira@Tone-debian:~$ sh copysh.sh
cp: não foi possível obter estado de '/media/SMART_PIX/REPORT': Arquivo ou diretório não encontrado
chmod: não foi possível acessar '17-07-04': Arquivo ou diretório não encontrado
copysh.sh: 5: cd: can't cd to 17-07-04
copysh.sh: 7: copysh.sh: ../lowercase.py: not found
rm: não foi possível remover 'img/rd.gif': Arquivo ou diretório não encontrado
rm: não foi possível remover 'img/scanning.gif': Arquivo ou diretório não encontrado
rm: não foi possível remover 'img/
.png': Arquivo ou diretório não encontrado
ln: falha ao criar link simbólico 'index.html': Arquivo existe
nogueira@Tone-debian:~$ ^C[/i]

It seems that it was not created the folder /media/SMART_PIX. Yes, the folder of smartPix-software is not created.
But it finds the glicemy reader, because when I insert it in the USB port, the display keeps blinking "PC"
And I don't know what does, how and when to run the other file, lowercase.py .
I am not too expert in Linux...

Oi, Antônio!

You are using Debian, right? Which desktop manager are you using? KDE, Gnome... Do you know how to access a pendrive when you plug it in your USB port? This is going to be the key.

Antonio Carlos Ribeiro Nogueira wrote:

But the other one, lowercase.py (it seems to me a file for Python),
I don't know if I need to compile it or how to run it

Antônio, you don't need to compile it. Python is an interpreted language, but you DO need to have Python installed in your Linux. I guess Debian does not come with it pre-installed, I use Kubuntu, which already comes with it.

Silvio, I am using Gnome Desktop manager. And as regard the Python, it is installed in my Debian 9. At least a good part of the total of Python Packages. If you want, I can post all the python packages installed here. And I know to look for the SmartPix Folder if it was created. I try to locate SmartPix Folder even in graphical tool search and in console mode. I have installed the updatedb and the locate tool.

To run a python file, just type in a terminal:

 python filename.py

I never used Gnome, but as far as I know, Nautilus mounts the pendrive automatically when you plug it in. If this is correct, you can see the path by typing

mount

before and after you insert the pendrive.

It follows the output before to insert the Accu-Chek device (what you name as pendrive):

nogueira@Tone-debian:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1993688k,nr_inodes=498422,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=401084k,mode=755)
/dev/sda6 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=9656)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/119 type tmpfs (rw,nosuid,nodev,relatime,size=401080k,mode=700,uid=119,gid=124)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=401080k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda1 on /media/nogueira/Reservado pelo Sistema type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
nogueira@Tone-debian:~$

And After (with the accu-chek device blinking PC in your display):

nogueira@Tone-debian:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1993688k,nr_inodes=498422,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=401084k,mode=755)
/dev/sda6 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=9656)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/119 type tmpfs (rw,nosuid,nodev,relatime,size=401080k,mode=700,uid=119,gid=124)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=401080k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda1 on /media/nogueira/Reservado pelo Sistema type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
nogueira@Tone-debian:~$

As you can see, there is notheing new before and after I plugged the pendrive, unless the words PC blinking in the display of the Accu-Chek Monitor.

OK, so Gnome is not mounting Accu-Check automatically. No problem. I believe we can mount it.

In my desktop manager (KDE), when I plug in an external storage device like a pendrive an icon appears in the notification area, that people use to call the "system tray", where there is a clock and other icons. Then I click on the new icon and it shows options to open the device in my file manager. Does this happen with Gnome? If so, open it in the file manager.

Let's try another test, more basic. In a terminal, before you plug in the Accu-Check, type

lsusb

then plug it in, wait a few seconds and run the command again. There must be a new device. Let's see if Linux is at least recognizing the device...

The command "lsusb" before to plug in the SmartPix USB Device:

root@Tone-debian:/home/nogueira# lsusb
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 0489:e036 Foxconn / Hon Hai
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 004: ID 0c45:63ee Microdia
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 413c:8160 Dell Computer Corp. Wireless 365 Bluetooth
Bus 001 Device 004: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
Bus 001 Device 003: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@Tone-debian:/home/nogueira#

Now the "susb" output with the SmartPix USB Device blinking the word PC in it's display plugged in:

root@Tone-debian:/home/nogueira# lsusb
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 0489:e036 Foxconn / Hon Hai
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 003: ID 173a:21cc
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 004: ID 0c45:63ee Microdia
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 413c:8160 Dell Computer Corp. Wireless 365 Bluetooth
Bus 001 Device 004: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
Bus 001 Device 003: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@Tone-debian:/home/nogueira#

We may see that is an extra line: [b]Bus 005 Device 003: ID 173a:21cc
[/b]

In the output of the "dmesg" command we can see that SmartPix Device is plugged in:

[22593.084104] usb 5-1: new full-speed USB device number 2 using uhci_hcd
[22593.290361] usb 5-1: New USB device found, idVendor=173a, idProduct=21cc
[22593.290369] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[22593.290374] usb 5-1: Product: Accu-Chek Active USB
[22593.290379] usb 5-1: Manufacturer: Roche Diagnostics GmbH
[22593.290383] usb 5-1: SerialNumber: 08759551
[23227.753021] usb 8-1: USB disconnect, device number 2
[23239.975474] usb 8-2: USB disconnect, device number 3
[23240.928034] usb 8-2: new high-speed USB device number 6 using ehci-pci
[23249.385528] usb 7-5: USB disconnect, device number 3
[23343.152511] usb 5-1: USB disconnect, device number 2
[23418.064203] usb 5-1: new full-speed USB device number 3 using uhci_hcd
[23418.269380] usb 5-1: New USB device found, idVendor=173a, idProduct=21cc
[23418.269388] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[23418.269393] usb 5-1: Product: Accu-Chek Active USB
[23418.269397] usb 5-1: Manufacturer: Roche Diagnostics GmbH
[23418.269401] usb 5-1: SerialNumber: 08759551
root@Tone-debian:/home/nogueira#

But when I look for a mount point, I can't find it as we can see through the "mount" command:

root@Tone-debian:/home/nogueira# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1993688k,nr_inodes=498422,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=401084k,mode=755)
/dev/sda6 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=36,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=699)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/119 type tmpfs (rw,nosuid,nodev,relatime,size=401080k,mode=700,uid=119,gid=124)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=401080k,mode=700,uid=1000,gid=1000)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=401080k,mode=700)
root@Tone-debian:/home/nogueira#

OK, so lsusb detects it. That's good news. The mount command does not show it up because it is not mounted yet. In Linux, devices remain in the "/dev/" folder. An external storage should appear as "/dev/sdx" and its partitions as "/dev/sdxy". So, now, you need to run (before and after pluging in the device):

ls /dev/sd*

And let's hope that it appears!

Silvio, just to remember, the dmesg command reported:

[ 1.879459] sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
[ 1.880097] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.904285] usb 5-1: New USB device found, idVendor=173a, idProduct=21cc
[ 1.904288] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.904291] usb 5-1: Product: Accu-Chek Active USB
[ 1.904293] usb 5-1: Manufacturer: Roche Diagnostics GmbH
[ 1.904295] usb 5-1: SerialNumber: 08759551

But the command "sudo ls /dev/sd* resulted for both situations (before and after to plug in the Accu-chek device):

nogueira@Tone-debian:~$ sudo ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/sda5 /dev/sda6
nogueira@Tone-debian:~$

I tried also using gparted to know if it would find the /dev/sd but it found just /dev/sda

I am afraid that my Debian Strech 9.0 have some bugs, because when I use the comand iwconfig it shows me:

root@Tone-debian:/home/nogueira# sudo iwconfig
lo no wireless extensions.

wlp12s0 IEEE 802.11 ESSID:"Nogueira13"
Mode:Managed Frequency:2.462 GHz Access Point: C4:6E:1F:9F:66:DC
Bit Rate=120 Mb/s Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=64/70 Signal level=-46 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:664 Missed beacon:0

enp9s0 no wireless extensions.

root@Tone-debian:/home/nogueira#

As you may see, it don't shows me my local IP that should be 192.168.1.109

And in the dmesg, there are some lines that induces me to think that are anythings wrong:

[ 28.710741] sky2 0000:09:00.0 enp9s0: enabling interface
[ 28.710847] IPv6: ADDRCONF(NETDEV_UP): enp9s0: link is not ready
[ 28.757293] IPv6: ADDRCONF(NETDEV_UP): wlp12s0: link is not ready
[ 28.772041] IPv6: ADDRCONF(NETDEV_UP): wlp12s0: link is not ready
[ 28.797025] IPv6: ADDRCONF(NETDEV_UP): wlp12s0: link is not ready
[ 32.101590] input: lircd-uinput as /devices/virtual/input/input21
[ 32.756892] IPv6: ADDRCONF(NETDEV_UP): wlp12s0: link is not ready
[ 33.751491] IPv6: ADDRCONF(NETDEV_UP): wlp12s0: link is not ready
[ 33.802915] wlp12s0: authenticate with c4:6e:1f:9f:66:dc
[ 33.817526] wlp12s0: send auth to c4:6e:1f:9f:66:dc (try 1/3)
[ 33.819866] wlp12s0: authenticated
[ 33.824034] wlp12s0: associate with c4:6e:1f:9f:66:dc (try 1/3)
[ 33.828394] wlp12s0: RX AssocResp from c4:6e:1f:9f:66:dc (capab=0x431 status=0 aid=4)
[ 33.828522] wlp12s0: associated
[ 33.828555] IPv6: ADDRCONF(NETDEV_CHANGE): wlp12s0: link becomes ready
[ 66.490454] Bluetooth: RFCOMM TTY layer initialized
[ 66.490461] Bluetooth: RFCOMM socket layer initialized
[ 66.490468] Bluetooth: RFCOMM ver 1.11
[ 100.552692] fuse init (API version 7.26)
[ 193.167305] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 193.167313] Bluetooth: HIDP socket layer initialized
[ 193.182938] elecom 0005:056E:0061.0003: Fixing up Elecom BM084 report descriptor
[ 193.183292] elecom 0005:056E:0061.0003: unknown main item tag 0x0

What do you think about?

Hmmm... If your Accu-Chek is not being recognized as a storage device, that's bad news... Although as far as I understand, it should, since I read in some sites that it behaves as a storage device... Have you tested it in Windows?

Don't worry about your wireless. It is working, isn't it? iwconfig is not an identical correspondence to ifconfig, it doesn't show the IP address. Try to run ifconfig and you will see the IP address of your wireless connection.

The dmesg warnings are only for IPv6. But the last message (33.828555) says that the link becomes ready, so I guess everything is OK.

Now back to your Accu-Chek, I have 2 suppositions:
1) Your hardware may be defective (you must test it with a Windows computer to be sure)
2) Your Accu-Chek is of a different model and is not an external storage

Silvio, does my Accu-Chek device should work as an usb external device even in windows? If I plug in in my laptop running windows 10 it should behave like an pendrive? Shall I see their content like a pendrive? I will try it and after I tell you what happens.
As far the command ifconfig it is working properly, but in root user.

Oi, Antônio! It is strange to talk to you in English (the official language for this forum), while I can clearly deduce that you are a native Portuguese language speaker as well as myself... 😊

I made a little research and found out that Roche has developed too many different devices:

https://www.accu-chek.com.br/br/servicos-ao-consumidor/manual-de-produto/monitorizacao.html

Which one of these are yours?

As far as I could find out, there is at least a device that works with Linux, and that is Accu-Chek Mobile:

https://brunocornec.wordpress.com/2016/01/25/diabete-and-linux/

I sincerely hope that this is your case...

Hi Silvio, I am glad to know you are Brazilian as my self. And I will take the chance to ask your email in order we can to communicate in our native language. It is much more convenient to us despite other people won' t took advantage of the information we exchange about Accu-Chek devices as USB store devices.
Well, the model of my Accu-chek device is the "Accu-chek Active". Not the "Novo Accu-Chek Active". I am affraid that the Accu-Chek Mobile has not yet here in Brazil. At least I never had heard about it.
I didn't tested yet to try mount the usb partition of my Accu-Chek Active in the Windows 10 Operational System. I will try tomorrow. In windows I have the app SmartPix Software offered by Roche. But I will may to check if my Accu-chek Active is working properly as a USB Store Device.

Hey guys!

I'm a French speaker and I have often decided on using French with others on this forum. It's cool if you do the same with your own language, Portuguese or otherwise, at least that's my experience. Nobody ever complained when I did so for myself, so I can't see a problem if you do it too.

Since I'm posting here, I wonder if either of you looked at this:

https://www.codeweavers.com/support/wiki/mac/faq/usbtoserial

I'm not sure this applies to the device in question, but since it might, I thought I would mention it.

It is OK to me to continue our communications through this forum, in English, so that as much people as possible may benefit from it.

Antonio, maybe you could contact Roche support and ask them which of their devices can behave as an external storage?

Also, J-P Simmard's suggestion is worth a try. It looks like some devices may work as a serial device.

If nothing else works, there is a less than ideal solution: you may run Windows under a Virtual Machine. I have had success with Virtualbox, for instance, running USB devices. The problem is that you will need a Windows license and it will take up the space of a Windows installation in your hard drive.

Hi Silvio, lets then to continue in English at all. Ok, I tried to mount it in the Windows 10 and the system try to mount but it don't show me any partition mounted. But when I click on the icon to unmount USB partitions, it is shown there and I may click on it to unmount the partition...
I have tried also the suggestion of the site https://www.codeweavers.com/support/wiki/mac/faq/usbtoserial, but it showed me nothing when I compareed the two txt files.
Well, I am defining that I am arriving at the final end of the line... I want to take advantage to thanks of your help.

Yes... We need to wait for someone who has an Accu-Chek device and knows how to do it, to reverse engineer their protocol and develop a Linux driver...

Last try: is the Virtual Machine solution acceptable for you?

Silvio, I think it's not worth this attempt (Virtual Box) because I already test it in the Windows 10 Operational System (not virtual) and as I explained above, it showed me the same behavior as in Linux (I am not so sure if you understand what I explained above about the attempt to mount it in the Windows 10. My Laptop has dual boot).
I think that I should try to insist in to make the app SmartPix to work under crossover.

OK, in Windows the storage mode did not work, this only means that probably your Accu-Chek does not behave as an external storage, but uses some particular protocol instead.

I suggest that you try to install the Smart Pix software in Windows and see if it communicates with your Accu-Chek. This way we would make sure that your unit is not defective.

OK Silvio, I will try to run SmartPix with this Accu-Chek in Windows 10 and I will post here if works or not.

1 to 26 of 26

Please Note: This Forum is for non-application specific questions relating to installation/configuration of CrossOver. All application-specific posts to this Forum will be moved to their appropriate Compatibility Center Forum.

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi01LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzA4NjEzODE4LCJjc3JmX3Rva2VuIjoiOGNlemt5VjZrS3FFV3FhOSIsImdkcHIiOjB9