Xfburn - "No burners are currently available"

[HoskaPamma]

I have a problem with Xfburn on Mint 20.3 Cinnamon, installed it from the repo (version 0.6.2-1) and launching it instantly shows an error message:

No burners are currently available

Possibly the disc(s) are in use, and cannot get accessed.

Please unmount and restart the application.

If no disc is in the drive, check that you have read and write access to the drive with the current user.

The thing is, I tried Brasero and PowerISO and both of them detect and can use my USB CD/DVD/BD read+write drive (why don't I use them? I found them a bit unreliable as I tested them). Also I have VLC installed (Flatpak) and it too can use the USB drive just fine.

My USB drive:

Code: Select all

lsusb

Bus 001 Device 011: ID 0411:01dc BUFFALO INC. (formerly MelCo., Inc.) Ultra-Slim Portable DVD Writer (DVSM-PC58U2V)

Code: Select all

inxi -Fxzd

Optical-1: /dev/sr0 vendor: BUFFALO model: Optical Drive rev: 2.00 dev-links: cdrom,cdrw,dvd,dvdrw 
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running

(I don't know why this doesn't list BD features/capabilities)

The "Disks" program in Mint shows this:

Code: Select all

Device: /dev/sr0 (Read-Only)

PowerISO shows the drive as

Code: Select all

/dev/sg0

I dunno why, but it still works. Brasero doesn't show the device name.

Does all other software read/use the drive through /dev/sg0 but Xfburn tries to use /dev/sr0 which might be read-only and thus complains?

I haven't tried K3b because it wants to install a mile long list of KDE packages and some people say that one should avoid installing KDE stuff. Also, the mint/ubuntu repo has a really old version and there doesn't seem to be a flatpak or appimage for it.

I also tried to open Xfburn with elevated rights:

Code: Select all

pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xfburn

but the same error message appears.

So, any idea what's going on with Xfburn, why can not it find my drive while all others do just fine? Thanks!

[ThaCrip]

I suspect the following may help you (as this person (in the link below) also has a Buffalo USB based burner)...

Code: Select all

udevadm info --name=/dev/sr0 --query=all

does yours show "ID_TYPE=floppy" in there? ; if so, proceed to do the following...

1) edit /etc/udev/rules.d/70-persistent-cd.rules as root
2) add a new line... SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="xxxxxxx", ENV{ID_TYPE}="cd", ENV{GENERATED}="1"
3) replace "xxxxxxx" with the serial number of your device from the above lines
4) save and restart xfburn, and also unplug and replug the device.

source (if you want more info) = https://askubuntu.com/questions/232026/ ... -in-xfburn

p.s. Xfburn works fine for me on my internal DVD burners (Sony Optiarc 7240s and Liteon iHAS-324B on my main PC. my backup computer has some much older CD and DVD burners... Liteon 24102b (CD-RW drive from about 2001) and Liteon 1673S (DVD burner from about the year 2005)). but occasionally ill have to click the 'refresh' icon, which then makes it see the disc, for it to proceed to burn etc otherwise it just won't erase/write to disc.

on a side note... with the command line burning programs (sudo apt install wodim (which is 'cdrecord')) I got it to overburn a music CD as instead of 80min you can burn a little over that etc. a example command I used... cdrecord dev=/dev/sr0 -v -overburn -dao -pad -audio /location/to/wavfiles/*.wav ; but as for how much over 80min you can go, it varies. but I would say you can probably get at least 30 seconds over, maybe a 1min or so, but beyond that your starting to roll-the-dice. WARNING: they claim it's possible to damage ones CD/DVD burner by overburning too far etc, but I am not sure how true that is. but on the side of caution I would not overburn too far to be extra safe. say within 30 seconds or so you will probably be fine from my best guesstimate which is usually nice on those occasions you go just a little over 80min and instead of having to remove a song, you just use the overburning option.

[all41]

fyi:
here are the results of udevadm info --name=/dev/sr0 --query=all on this machine
with a generic external dvd drive for comparison:

Code: Select all

uno@una:~$ udevadm info --name=/dev/sr0 --query=all
P: /devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/host6/target6:0:0/6:0:0:0/block/sr0
N: sr0
L: -100
S: disk/by-id/usb-HL-DT-ST_DVDRAM_GSA-T50N_4B5A38393632333534353320-0:0
S: dvdrw
S: disk/by-path/pci-0000:00:14.0-usb-0:7:1.0-scsi-0:0:0:0
S: dvd
S: cdrw
S: cdrom
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/host6/target6:0:0/6:0:0:0/block/sr0
E: DEVNAME=/dev/sr0
E: DEVTYPE=disk
E: MAJOR=11
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=2253553740
E: ID_CDROM=1
E: SYSTEMD_MOUNT_DEVICE_BOUND=1
E: ID_CDROM_CD=1
E: ID_CDROM_CD_R=1
E: ID_CDROM_CD_RW=1
E: ID_CDROM_DVD=1
E: ID_CDROM_DVD_R=1
E: ID_CDROM_DVD_RW=1
E: ID_CDROM_DVD_RAM=1
E: ID_CDROM_DVD_PLUS_R=1
E: ID_CDROM_DVD_PLUS_RW=1
E: ID_CDROM_DVD_PLUS_R_DL=1
E: ID_CDROM_MRW=1
E: ID_CDROM_MRW_W=1
E: SYSTEMD_READY=0
E: ID_VENDOR=HL-DT-ST
E: ID_VENDOR_ENC=HL-DT-ST
E: ID_VENDOR_ID=13fd
E: ID_MODEL=DVDRAM_GSA-T50N
E: ID_MODEL_ENC=DVDRAM\x20GSA-T50N\x20
E: ID_MODEL_ID=0840
E: ID_REVISION=RQ01
E: ID_SERIAL=HL-DT-ST_DVDRAM_GSA-T50N_4B5A38393632333534353320-0:0
E: ID_SERIAL_SHORT=4B5A38393632333534353320
E: ID_TYPE=cd
E: ID_INSTANCE=0:0
E: ID_BUS=usb
E: ID_USB_INTERFACES=:080250:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usb-storage
E: ID_PATH=pci-0000:00:14.0-usb-0:7:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_7_1_0-scsi-0_0_0_0
E: ID_FOR_SEAT=block-pci-0000_00_14_0-usb-0_7_1_0-scsi-0_0_0_0
E: DEVLINKS=/dev/disk/by-id/usb-HL-DT-ST_DVDRAM_GSA-T50N_4B5A38393632333534353320-0:0 /dev/dvdrw /dev/disk/by-path/pci-0000:00:14.0-usb-0:7:1.0-scsi-0:0:0:0 /dev/dvd /dev/cdrw /dev/cdrom
E: TAGS=:seat:uaccess:systemd:

This drive works perfectly in xfburn--in fact I've never ever had a problem using xfburn with any drive.
Try this--close out xfburn
navigate to .config/xfburn
.config is a hidden diretory in your username/home directory--ctrl+h to see them
rename the .config/xfburn directory to .config/xfburn.old
With the drive plugged in reopen xfburn--the .config/xfburn directory will get recreated with fresh default settings.
Does that help the problem? If you want to see deeper information regarding how Linux interprets your drive's info:

Code: Select all

apt install wodim

then:

Code: Select all

wodim prcap

reveals information regarding the drive's capabilities that is seen by Linux

[HoskaPamma]

does yours show "ID_TYPE=floppy" in there?

Nope, it shows: "ID_TYPE=generic". Should I still use your udev fix?

[HoskaPamma]

... With the drive plugged in reopen xfburn--the .config/xfburn directory will get recreated with fresh default settings.
Does that help the problem?

Unfortunately no.

wodim prcap

Code: Select all

wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/cdrw
Using /dev/cdrom of unknown capabilities
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   : 
Vendor_info    : 'BUFFALO '
Identification : 'Optical Drive   '
Revision       : '2.00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE 
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
wodim: No such file or directory. Cannot open 'prcap'.

udevadm info --name=/dev/sr0 --query=all

Code: Select all

P: /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host5/target5:0:0/5:0:0:0/block/sr0
N: sr0
L: -100
S: dvdrw
S: disk/by-path/pci-0000:00:14.0-usb-0:2:1.0-scsi-0:0:0:0
S: dvd
S: disk/by-id/usb-BUFFALO_Optical_Drive_303042323031343031333133
S: cdrw
S: cdrom
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host5/target5:0:0/5:0:0:0/block/sr0
E: DEVNAME=/dev/sr0
E: DEVTYPE=disk
E: MAJOR=11
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=131165592110
E: ID_CDROM=1
E: SYSTEMD_MOUNT_DEVICE_BOUND=1
E: ID_CDROM_CD=1
E: ID_CDROM_CD_R=1
E: ID_CDROM_CD_RW=1
E: ID_CDROM_DVD=1
E: ID_CDROM_DVD_R=1
E: ID_CDROM_DVD_RW=1
E: ID_CDROM_DVD_RAM=1
E: ID_CDROM_DVD_PLUS_R=1
E: ID_CDROM_DVD_PLUS_RW=1
E: ID_CDROM_DVD_PLUS_R_DL=1
E: ID_CDROM_BD=1
E: ID_CDROM_BD_R=1
E: ID_CDROM_BD_RE=1
E: ID_CDROM_MRW=1
E: ID_CDROM_MRW_W=1
E: ID_CDROM_MEDIA=1
E: ID_CDROM_MEDIA_BD_RE=1
E: ID_CDROM_MEDIA_STATE=complete
E: ID_CDROM_MEDIA_SESSION_COUNT=1
E: ID_CDROM_MEDIA_TRACK_COUNT=1
E: ID_CDROM_MEDIA_TRACK_COUNT_DATA=1
E: ID_VENDOR=BUFFALO
E: ID_VENDOR_ENC=BUFFALO
E: ID_VENDOR_ID=0411
E: ID_MODEL=Optical_Drive
E: ID_MODEL_ENC=Optical\x20Drive
E: ID_MODEL_ID=01dc
E: ID_REVISION=0200
E: ID_SERIAL=BUFFALO_Optical_Drive_303042323031343031333133
E: ID_SERIAL_SHORT=303042323031343031333133
E: ID_TYPE=generic
E: ID_BUS=usb
E: ID_USB_INTERFACES=:080550:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usb-storage
E: ID_PATH=pci-0000:00:14.0-usb-0:2:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_2_1_0-scsi-0_0_0_0
E: ID_FOR_SEAT=block-pci-0000_00_14_0-usb-0_2_1_0-scsi-0_0_0_0
E: DEVLINKS=/dev/dvdrw /dev/disk/by-path/pci-0000:00:14.0-usb-0:2:1.0-scsi-0:0:0:0 /dev/dvd /dev/disk/by-id/usb-BUFFALO_Optical_Drive_303042323031343031333133 /dev/cdrw /dev/cdrom
E: TAGS=:systemd:uaccess:seat:

udevadm info --name=/dev/sg0 --query=all

Code: Select all

P: /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg0
N: sg0
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg0
E: DEVNAME=/dev/sg0
E: MAJOR=21
E: MINOR=0
E: SUBSYSTEM=scsi_generic
E: USEC_INITIALIZED=131165607050
E: ID_PATH=pci-0000:00:14.0-usb-0:2:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_2_1_0-scsi-0_0_0_0
E: ID_FOR_SEAT=scsi_generic-pci-0000_00_14_0-usb-0_2_1_0-scsi-0_0_0_0

[HoskaPamma]

1) edit /etc/udev/rules.d/70-persistent-cd.rules as root
2) add a new line... SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="xxxxxxx", ENV{ID_TYPE}="cd", ENV{GENERATED}="1"
3) replace "xxxxxxx" with the serial number of your device from the above lines
4) save and restart xfburn, and also unplug and replug the device.

Went ahead and did this even if mine was not ID'd as a floppy. Now Xfburn starts without an error and the device is detected. Hooray! Many thanks, for all of you who bothered to answer and help!

I wasn't able to burn an image to a disc, I couldn't choose the speed and burn mode. Now trying to burn a data composition, this time was able to choose speed and mode and now it is burning. I'll have to test more but now Xfburn seems a little unreliable as well. And I see that Xfburn doesn't have a burn after verification feature, PowerISO has it. PowerISO seems to be the best software, for me at least, though it doesn't function perfectly either. I wish K3b could be installed as Flatpak or AppImage, it would be interesting to test that as well.

[Schultz]

I wasn't able to burn an image to a disc, I couldn't choose the speed and burn mode.

Try clicking the refresh button.

Untitled.jpg (33.28 KiB) Viewed 3709 times

[HoskaPamma]

I wasn't able to burn an image to a disc, I couldn't choose the speed and burn mode.

Try clicking the refresh button.

I tried that. That was the way I was able to burn the data composition. I dunno why it didn't work when trying to burn an iso file. Will have to test more. Though the verification feature in PowerISO is drawing me towards using that program.

[ThaCrip]

1) edit /etc/udev/rules.d/70-persistent-cd.rules as root
2) add a new line... SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="xxxxxxx", ENV{ID_TYPE}="cd", ENV{GENERATED}="1"
3) replace "xxxxxxx" with the serial number of your device from the above lines
4) save and restart xfburn, and also unplug and replug the device.

Went ahead and did this even if mine was not ID'd as a floppy. Now Xfburn starts without an error and the device is detected. Hooray! Many thanks, for all of you who bothered to answer and help!

I wasn't able to burn an image to a disc, I couldn't choose the speed and burn mode. Now trying to burn a data composition, this time was able to choose speed and mode and now it is burning. I'll have to test more but now Xfburn seems a little unreliable as well. And I see that Xfburn doesn't have a burn after verification feature, PowerISO has it. PowerISO seems to be the best software, for me at least, though it doesn't function perfectly either. I wish K3b could be installed as Flatpak or AppImage, it would be interesting to test that as well.

You can still verify the data burned with Xfburn with command line as I talked about this back in June 2021 here... viewtopic.php?p=2026996#p2026996

but generally speaking... if your burning a ISO etc, unless you have a faulty CD/DVD, there is a high probability the data is good (in fact, I have been burning CD's since 1998, DVD's since I think 2005, and never had one fail from a faulty disc). but I guess if it's higher sensitivity data you can't afford to take a chance on, it's probably worth taking the extra step to verify the data.

personally I trust Xfburn for whatever that's worth as it's simple and straight to the point. the most obvious bug/issue with Xfburn is one generally has to click the 'refresh' icon to get it to access the CD/DVD properly before burning/erasing etc as I mentioned in my first post and then Schultz had a nice little picture there to make it crystal clear.

[HoskaPamma]

Burned data composition (iso and md5 checksum files of the iso files) on a BD-RE disc and checked all checksums and they match, so that was successful. But, trying to erase the BD-RE, pushing the refresh button, Xfburn just says "Inserted disc is already blank". Xfburn works the worst of all the burning programs I have now tried. Going to use PowerISO in the future.. and if that doesn't work, I guess it's windows programs that I have to rely upon. A bit disappointed about the quality of the linux burning software.

[ThaCrip]

Burned data composition (iso and md5 checksum files of the iso files) on a BD-RE disc and checked all checksums and they match, so that was successful. But, trying to erase the BD-RE, pushing the refresh button, Xfburn just says "Inserted disc is already blank".

I can't comment on BluRay burning but Xfburn works well on CD/DVD stuff.

I guess it's windows programs that I have to rely upon.

If your going to use Windows software, IMGBurn (i.e. https://www.majorgeeks.com/files/details/imgburn.html ; I linked here instead of the official IMGBurn website because that installer does not include the junk the one on official site does) is definitely my 'go to' program on there as it has verification etc. it's just great software, assuming you can get it working through Wine on Linux.

[HoskaPamma]

I guess it's windows programs that I have to rely upon.

If your going to use Windows software, IMGBurn is definitely my 'go to' program on there as it has verification etc. it's just great software, assuming you can get it working through Wine on Linux.

That was what I was using when my daily driver was Windows (now only on dual boot for some games). Thanks for your help again.

[ThaCrip]

That [IMGBurn] was what I was using when my daily driver was Windows (now only on dual boot for some games). Thanks for your help again.

Hell, I just got IMGBurn (the windows burning program) working on Mint v20.3-Xfce with a bit of info I found after digging plus a bit of my own testing as here is what one needs to do to get it working (as previously, by default, it has problems finding ones SATA DVD burners and still does but I got a work-around etc)...

1)Install Wine (i.e. https://wiki.winehq.org/Ubuntu ; then after that's done issue 'sudo apt install wine-desktop-files' so you get the Wine entries in your Mint menu)

2)Load up "Configure Wine" from Mint menu... on 'Applications' tab click 'Add application' then guide it to the 'imgburn.exe' file (should be located in the 'Program Files (x86) > ImgBurn' folder) and click 'open'. then with the 'ImgBurn.exe' highlighted in the 'Applications' tab, you should see "Windows Version:", switch it from 'Use global settings' to 'Windows XP', then click 'Apply', then ''OK'. then after maybe 5-10 seconds the Wine processes will completely close.

3)Start ImgBurn (if it fails to start see "IMPORTANT NOTE" below!). once ImgBurn starts up it will probably say "Searching for SCSI / ATAPI devices..." and just under that it will have a error saying, "No devices detected!". so at this point ImgBurn is still useless. but to fix this, in ImgBurn go to...Tools > Settings > I/O. then for 'Interface' select 'SPTI - Microsoft' and under that you will see "SPTI Device Enumeration Method" and change that to "Device Interface" then click 'OK'. it should now see your SATA DVD burners and ImgBurn should now work as expected.

IMPORTANT NOTE: if ImgBurn fails to start I seem to have found a reliable way, at least on my Mint v20.3-Xfce system, to get it to start up. basically you can either load up another Wine program FIRST (then start ImgBurn), OR, if you don't have any other Wine(Windows) programs installed, load up ' Configure Wine' from the Mint menu and just let it sit there and then start up ImgBurn and it should load! ; because I noticed when Wine is completely closed/not running at all, and you try to load ImgBurn, it always (or nearly always) fails to start up. but when a wine process is already active (which running another Windows program or leaving 'Configure Wine' running etc) and then start up ImgBurn it seems to always work.

NOTE: if for whatever reason ImgBurn seems 'frozen', you can immediately shut it down (along with ALL other programs using Wine) by issuing 'wineserver -k' (without the ') from terminal and press ENTER and it will immediately stop.

it would be nice if the OP could confirm whether his USB based DVD burner works with this method or not as all I confirmed is that standard SATA based DVD burners work. on a side note... I do have a external USB 3 based device (which connects to IDE/SATA ports on internal DVD burners) that I could connect to a internal DVD burner and see how that fairs, but I suspect it will work.

p.s. I tested ImgBurn by burning the Clonezilla ISO to a CD-RW disc (which already has a previous version of Clonezilla on it) and it erased the disc and burned the new ISO, then the 'verify' process confirmed the burned data was successful.

for the record... I got the 'SPTI" idea in ImgBurn from searching online, but the method of getting ImgBurn to consistently load up I discovered myself as it took me a while to discover that running another windows program in wine, or leaving the 'wine configuration' screen active temporarily, was the key to get ImgBurn to load up consistently as I think before I discovered that in why it seemed like sometimes it would work and other times it would not work at all is because I think when it was working, even though I closed my open windows program (Foobar2000 in my case(as it's one of the major reasons I got Wine installed)) and then loaded up ImgBurn and it was working, is because after closing my open windows program there is some delay before Wine actually completely shuts down, so there is probably a small open window to get ImgBurn to start during this small window of time, which is probably why it seemed sort of random for me initially on why ImgBurn was starting and not starting and then not running at all etc. but that simple trick seems to get ImgBurn to consistently load up now.

EDIT (March 31st 2022): bottom line... use PlayOnLinux (sudo apt install playonlinux) paired with Wine v6.0.1(x86(32bit) or amd64(64bit) will work, but x86 takes up less storage space so I would generally stick with that), switch Wine to WinXP mode (it defaults to Win7 mode and will hang on splash screen if you don't change it to WinXP), then from within ImgBurn go to 'Tools > Settings > I/O' and change it to 'SPTI - Microsoft' and select either 'Device Interface' or 'Drive Letter' and your all set.

[HoskaPamma]

it would be nice if the OP could confirm whether his USB based DVD burner works with this method or not

Many thanks for the detailed information about Wine, and ImgBurn. As it is, I still don't have Wine installed. I had it on my test Mint installation where I tried all kinds of stuff worry free before installing Mint as my daily driver. Unfortunately I wasn't able to get anything working with Wine and I think I messed something up with it. At that time Linux itself was a completely new experience for me and I was learning everything from scratch, so it may be that I was just overwhelmed by everything at that point and could not get it working. I remember that I was trying to make SubtitleEdit work and could not do it. It includes a portable VLC and ffmpeg (added by me) and also a separate tesseract tool/executable for OCR stuff (comes with SubtitleEdit). It might be hard to make everything work together. I also tried to make it work with Mono (as instructed on the help page) but it wasn't stable with that, some things were not working.

I have to try Wine again some day, in a VirtualBox Mint installation first, to see if I can make it work before messing my normal Mint with it. I'm basically still on a (long?) journey of changing from Windows to Linux world and I still have a bit of ToDo's to go through. For example, I still have Windows software that I'm trying find replacements, e.g. video player (PotPlayer -> ?), audio tagging (Mp3tag -> Puddletag?), music player (like you, foobar2000 -> ?), text editing (Notepad2/Notepad++ -> ?). I also have an "amalgamation" of Exact Audio Copy + REACT2 + CueTools + a heavily customized script for music ripping that I'm probably not going to be able to find any replacement in Linux world, unless, if there's an AccurateRip and/or CTDB ripper/verification software in Linux, then I might be able to switch to native software, writing a new script for the whole ripping process. But I digress, sorry. If I ever get around to install Wine and test ImgBurn with it, I will post my findings here.

I still don't know what is the correct/preferred way to install Wine on Mint. Should I use ubuntu/mint repo, or add Wine repo for newer versions, and do I have to install some additional packages, like winetricks? And what is Bottles and would it be easier to use than just Wine? And then have to learn how it all works, like how to run programs that need .NET, which doesn't seem to be that easy. A discussion for a new forum topic I guess, not here.

[ThaCrip]

Many thanks for the detailed information about Wine, and ImgBurn. As it is, I still don't have Wine installed. I had it on my test Mint installation where I tried all kinds of stuff worry free before installing Mint as my daily driver. Unfortunately I wasn't able to get anything working with Wine and I think I messed something up with it. At that time Linux itself was a completely new experience for me and I was learning everything from scratch, so it may be that I was just overwhelmed by everything at that point and could not get it working. I remember that I was trying to make SubtitleEdit work and could not do it. It includes a portable VLC and ffmpeg (added by me) and also a separate tesseract tool/executable for OCR stuff (comes with SubtitleEdit). It might be hard to make everything work together. I also tried to make it work with Mono (as instructed on the help page) but it wasn't stable with that, some things were not working.

I have to try Wine again some day, in a VirtualBox Mint installation first, to see if I can make it work before messing my normal Mint with it. I'm basically still on a (long?) journey of changing from Windows to Linux world and I still have a bit of ToDo's to go through. For example, I still have Windows software that I'm trying find replacements, e.g. video player (PotPlayer -> ?), audio tagging (Mp3tag -> Puddletag?), music player (like you, foobar2000 -> ?), text editing (Notepad2/Notepad++ -> ?). I also have an "amalgamation" of Exact Audio Copy + REACT2 + CueTools + a heavily customized script for music ripping that I'm probably not going to be able to find any replacement in Linux world, unless, if there's an AccurateRip and/or CTDB ripper/verification software in Linux, then I might be able to switch to native software, writing a new script for the whole ripping process. But I digress, sorry. If I ever get around to install Wine and test ImgBurn with it, I will post my findings here.

I still don't know what is the correct/preferred way to install Wine on Mint. Should I use ubuntu/mint repo, or add Wine repo for newer versions, and do I have to install some additional packages, like winetricks? And what is Bottles and would it be easier to use than just Wine? And then have to learn how it all works, like how to run programs that need .NET, which doesn't seem to be that easy. A discussion for a new forum topic I guess, not here.

I also used PotPlayer on Windows before switching to Linux but I typically just use the default Celluloid paired with MPV (just issue 'sudo apt install mpv') as Celluloid uses MPV for hardware acceleration if available as you can check to see if it's trying to use that by going to the options in Celluloid and look for 'hwdec=yes' under the 'extra mpv options' under 'miscellaneous' etc. for a alternative to Celluloid with a bit more details... SMPlayer is a good but Celluloid is simple and straight to the point as it's what I typically use for a while now. but I get there is a bit of a adjustment period when your used to PotPlayer etc and might not like the change initially, but after a while, I got used to it and don't miss PotPlayer at all anymore.

but if you like Foobar2000 I would install Wine just for that as it's a major reason I am using Wine. also, I personally don't install either 'mono' or 'gecko' stuff on my Wine installation. but it might be required in certain cases but for what little I use Wine for (basically Foob2000 and ImgBurn and playing some games) I don't have problems not using it. also, all of the conversion stuff works fine on Foobar2000 to through Wine. as you just install the proper encoders etc. if you want Apple AAC encoding in Foobar2000 you can get that but you have to manually set it up to a degree like you do on Windows.

basically Foobar2000 works well even though visually it might be slightly different looking compared to on Windows and a small glitch like if you hover mouse over a music file shown in there and it gives you that little popup text showing more info about it and you try right clicking with that active, your right click won't register. so you just make sure your right click before that popup appears about 1 second later, so things work as you would expect. but in terms of general use, it's largely the same as Windows. but I do notice it does not see any CD/DVD drives but this is typically not a problem for me as I got other ways if I need to get data off of a audio CD into Foobar2000. but I typically keep all of my audio as FLAC and then convert to MP3 etc as needed with Foobar2000.

as for the proper Wine installation, there are basically two ways...

Option 1)what the Mint team suggests... "apt install wine-installer" (just that simple command and that's it) (which is v5 series of Wine, so it's older than the newest one which is v7.0 which was released earlier this month). I guess one could say this is potentially 'safer' than the Option 2 below. but I personally would not worry about problems with Option 2 as I use Option 2.

or...

Option 2)if you want the newest stable version of Wine (currently v7.0) on Mint v20.x you simply do the following seven steps exactly (excluding the number and ")" stuff obviously )...

Code: Select all

1)sudo dpkg --add-architecture i386
2)wget -nc https://dl.winehq.org/wine-builds/winehq.key
3)sudo apt-key add winehq.key
4)sudo add-apt-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ focal main'
5)sudo apt update
6)sudo apt install --install-recommends winehq-stable
7)sudo apt install wine-desktop-files

that's the official installation instructions from the official Wine website (i.e. https://wiki.winehq.org/Ubuntu ) except 'step 7' I included because it gives you the proper Wine entries in the Mint menu to make things easier to configure etc as without that you won't have them.

but with 'winetricks' you can just type that into the terminal (there is a 'winetricks' entry in the Mint menu but it's not located on the 'Wine' part like one would expect) and press enter and a GUI will pop up which I think gives you extra options of certain things to install etc. like to run a older game I play on Wine/Lutris combo etc I got to issue 'winetricks physx' from terminal (but this can be done through the GUI I think) which installs NVIDIA's Physx software which that particular game I play needs it. you can even uninstall stuff to which works similar to what it does in Windows with the 'Uninstall Wine Software' in the Mint menu Wine section.

so while Wine won't work on all windows software, it works on a fair amount of it from the looks of things

but, like you said, you can play around with this stuff in a virtual machine first

[HoskaPamma]

Many thanks again ThaCrip! I'll have a go at Wine some day. The "Bottles" software looks promising and perhaps it's easier to use Wine with that.

[vsh]

I suspect the following may help you (as this person (in the link below) also has a Buffalo USB based burner)...

Code: Select all

udevadm info --name=/dev/sr0 --query=all

does yours show "ID_TYPE=floppy" in there? ; if so, proceed to do the following...

1) edit /etc/udev/rules.d/70-persistent-cd.rules as root
2) add a new line... SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="xxxxxxx", ENV{ID_TYPE}="cd", ENV{GENERATED}="1"
3) replace "xxxxxxx" with the serial number of your device from the above lines
4) save and restart xfburn, and also unplug and replug the device.
...

Hi!
Thank you very much, your advice helped, I use "usb-HLDS_Inc_SuperMulti_RW"!
Since "xfburn" did not work, I used an old "Brasero".

[ThaCrip]

I suspect the following may help you (as this person (in the link below) also has a Buffalo USB based burner)...

Code: Select all

udevadm info --name=/dev/sr0 --query=all

does yours show "ID_TYPE=floppy" in there? ; if so, proceed to do the following...

1) edit /etc/udev/rules.d/70-persistent-cd.rules as root
2) add a new line... SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_SERIAL}=="xxxxxxx", ENV{ID_TYPE}="cd", ENV{GENERATED}="1"
3) replace "xxxxxxx" with the serial number of your device from the above lines
4) save and restart xfburn, and also unplug and replug the device.
...

Hi!
Thank you very much, your advice helped, I use "usb-HLDS_Inc_SuperMulti_RW"!
Since "xfburn" did not work, I used an old "Brasero".

Honestly, in my opinion, your better off using ImgBurn since it's the best general burning software there is

plus, with that after burning it can run a 'verify' just to make sure what you burned is good. but since I got some Liteon burners I run the DVD+R (or -R) through KProbe (which is also Windows software but works on Linux through Wine as I got mine setup through PlayOnLinux using Wine v4.0.4 which still works with ASPI mode) to check burn quality with PI/PIF (PIF's are more important than PI in general).

but on KProbe scan (set it's read speed to 8x), you generally want PI's to be 280 max (although more of a high quality burn will probably be in the ball park of 10-20 PI peaks and I have a smaller amount of suspect discs that goes quite a bit over 280 but PC burners probably have better error correction than a typical home player etc) and it seems when it comes to PIF's '4' spikes or less is optimal (but if you go a little over '4' it's not the end of the world). but out of a fair amount of DVD's I burned lately (on new old stock (my guesstimate is the discs themselves are probably at least 13+ years old and could be up around 17 years old since I think they stopped making 8x media a rather long time ago now) I got from Ebay (200 disc (4x 50-packs) which basically came out to $0.20 a disc so I got a bit of a deal) which is Verbatim 8x certified discs with 'MCC 003' media code, so it's quality media) only about 4-6 might have been suspect burn quality as one in particular I tested (which was burned on my old IDE Liteon 1673s drive, which I generally don't use on this media since my two newer burners burn it better), which had the most PIF's (41.5k total which is fairly high (not a good thing) and PIF peaks were about 6-16 near end of the burn), while it still reads the data on the couple of DVD burners I tested, you can see my 7240s drive has trouble reading it given it slows down throughout the disc (so it takes longer to read as I did not time it but it was probably 7min+) instead of reading at max all the way through which typically takes very close to 5 minutes flat if a disc is reading at max speed. but on my iHAS324B burner that did not slow down at all and read the disc at max speed when copying data from DVD back to hard drive. I even used 'sha256sum' to make sure the burned file was identical to original on my hard drive and both the 7240s and iHAS324B passed without issue. but generally speaking when I burn those 'MCC 003' discs both drives don't have problems but it seems my Liteon iHAS324B is a bit safer (than the 7240s) burning those 'MCC 003' discs as I use 8x burn speed which is the max allowed as my 7240s allows '4x, 6x, 8x' burn speed and my iHAS324B allows '6x, 8x' burn speed on 'MCC 003' media.

but here is the disc scan picture I did on the particular disc that was burned on 1673s at 8x (which is my worse all-around burn quality so far as a handful of other discs I burned had much higher PI's (like with peaks about 500-700 range very early in the disc (280 or less keeps it within spec), about first 5%, maybe 10% of the disc, and then smooths out back to more normal range etc) but in terms of PIF's this is definitely the worst all-around disc I seen so far of the discs I bought recently which are new old stock etc) and then scanned with iHAS324B (at 8x)...



but for comparison here is one on the more higher quality side of things (burned on my iHAS324B @ 8x and then scanned on same drive at 8x)...



NOTE: click picture(s) to see more detail.

side note: I did make a disc scan of some discs I had to send back to Amazon earlier this month because they might have changed the formula or I got a bad batch of discs or newer discs may require a bit more updated drive firmware to burn properly etc because on those same discs (i.e. Verbatim DVD-R Azo 16x (MCC03RG20 media code), which are normally quality discs) in the past, as I still have a batch I bought in Jan 2014, they still burn great to this day. but anyways, on the handful of discs I burned from the 100-pack I got from Amazon before sending them back I made a disc scan of a disc that actually outright failed to verify in ImgBurn (i.e. so outright corrupt data) and where it failed to read the discs was late into the disc at which point the PIF's on the disc scan I made were in the 10-30 or so range with a single spike of 76. so this might give me a ball park estimate on the point I will see outright failure to read the data from the disc. because even the scan I posted above that was burned on my Liteon 1673s drive (which I got in 2005) is still noticeably better than that disc that had actual corrupt data on it. but I like to keep my burns much closer to high quality side than so-so side. because quality DVD recordable media (Verbatim Azo(Azo uses Mitsubishi dye) and TY (Taiyo Yuden) media as these are the two brands that are the safest generally speaking) will likely last at least decades before failure given I got media I burned 10-15 years ago or so that still scans well to this day on KProbe etc as my general reasoning is if those discs have not noticeably degraded by now, they will likely last at least decades before actual failure to read the data occurs. that's why in terms of general high importance data backup, DVD+R (or -R) (at least the quality media like Verbatim Azo or Taiyo Yuden (although other brands might be good enough to)) is a great alternative to regular hard drive storage for long term data storage.

p.s. I even used ImgBurn to overburn a Verbatim 80min CD-R (burned a standard audio CD at 16x) to 82:14:66 (82min15sec) recently with success and plays on my original audio CD player which has a April 1991 mfg date on it without issue (on this it shows up as 82min12sec).

side note: CD-R's have C1/C2 error scans stuff to but I can't check those since none of my burners can do proper CD scans of CD-R's. but chances are they are fine and I don't really use CD-R's for data either, pretty much just burning standard audio CD's. EDIT (Apr 30th 2022): apparently my old Liteon 24120b (Dec 2001 mfg date) CD-RW drive can do proper C1/C2 tests with KProbe as you can see it reacts differently (i.e. actually shows a steady stream of C1 info) unlike when I try it with my Liteon iHAS324B DVD burner which only works with DVD scanning basically. but, in short, one of the Verbatim (CMC Magnetics media code) CD-R's (100-pack for about $18) I bought and burned at 16x recently (the AUDIO CD I mentioned above that's 82:14:66(82min15sec) in length) is solid... C1 = 31 peak with 6.75 average and 31.7k total. C2 = 0. from what I read a 'good burn' should report not even a single C2 error. even checking another disc I burned from that same batch of media, and even has a small visible flaw when looking at the write surface with my eyes, is good as it's similar to the other one. I checked another and this one was the best yet (i.e. 28 C1 peak, 4.00 average, 18.5k total. C2 = 0), so there is probably some level of quality fluctuation on these Verbatim CD-R's but if these handful of scans I have done so far is a ball park indication of the entire 100-pack of CD-R's, I am not worried about quality