Forums

Hi there,

Thanks very much for playonlinux, it helps me a lot!

I'm running 4.2.2 on Ubuntu 12.04 LTS, mostly using Wine 1.7.14-imm32_bug25361 now.

My problem is that I mostly install a lot of applications on one virtual drive (default), since each virtual drive contains some overhead.  Every time I want to make a new shortcut, it takes a minute or so to scan the virtual drive, while i just wanted to browse to the exe.  The finally, you make the shortcut, and it scans the drive again!  One thing that I installed was MingW, with a lot of exe's, taking very long to scan.

I suggest you put two buttons in the dialog: Browse and Scan. no need for a selection list and a Next button, that takes two clicks!  On the Scan button you should be able to use the same code you have now.

Thanks again, keep up the good work!

Regards,

Chris

I have to agree. It takes a very long time. Maybe we can warn the users:

 

"Scanning the virtual drive ..."

to

> "Scanning the virtual drive ... (this may take some time)"

hello guys,

 

If you're scanning your hard drive (used chkdsk /r for example), that process will take in excess of 2 hours depending on size of your drive and errors found. it typically stops updating around 10 or 11% and suddenly jumps to 100 when done.

 

thanks and regards

 

hello guys,

 

If you're scanning your hard drive (used chkdsk /r for example), that process will take in excess of 2 hours depending on size of your drive and errors found. it typically stops updating around 10 or 11% and suddenly jumps to 100 when done.

 

thanks and regards

 

Quote from namangarg

This has nothing to do with chkdsk or any filesystem! It's scanning (searching in) the wineprefix's virtual drive path for .exe files so you can choose which one you want to create a shortcut for. The scanning takes place even if the wineprefix is in a EXT filesystem, where chkdsk would never work!

Regarding the issue, it still persists on Ubuntu 22.04 with PlayOnLinux 4.3.4-2, even with a Ryzen 9 7950X3D and a PCIe-based SSD. I don't actually know if it only scans the wine's environment C: drive or every drive configured on that enviroment. In any case, after removing all virtual drives but C: and checking again how long takes the scanning process, it's still too slow.