Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to the Power Users community on Codidact!

Power Users is a Q&A site for questions about the usage of computer software and hardware. We are still a small site and would like to grow, so please consider joining our community. We are looking forward to your questions and answers; they are the building blocks of a repository of knowledge we are building together.

Delete "dosdevices" folder created by WINE from Windows

+1
−0

I have a backup of a Linux Mint install circa 2016. Individual files were copied using Ubuntu to an NTFS drive. Now I'm tar-ing and archiving the files, and trying to delete what's left.

I made the tar, and pressed delete, and got this very scary message:

Image_alt_text

I hastily pressed "skip", deeply worried about my C and D drives.

I found the culprit:

Image_alt_text

This appears to be a link created by WINE to map HDDs to WINE. And the filenames appear to be illegal in Windows.

https://ubuntuforums.org/showthread.php?t=1727532

How can I safely remove this in Windows? (I have WSL, but not everyone does.)

(Somewhat moot in my case, because I'm formatting the drive, but this isn't always easy.)

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

1 answer

+0
−0

Sorry, I don't know the answer to "remove this in Windows", and this is too long for a comment.

The root cause is that Linux gives the user more power in working with files, and Windows is less permissive. In Linux, you can put pretty much anything in filenames other than /. In Windows, many other things like : are arbitrarily forbidden (because Windows wants to reserve those for special use). But Windows never had a robust file handling logic, so it does not deal gracefully with its assumption being validated. Their engineers assumed that if you just block those file names in the Windows UI, that guarantees they'll never exist, and for some reason never considered that another system like Linux (or even a Windows virus) could create these.

Actually, they probably anticipated a problem like this with Linux, and deliberately left it there. The hope is that less knowledgeable users will blame Linux, and learn to avoid it like the plague, which protects the market share of Windows.

Basically, this is a situation where Linux can be used to create files that break Windows. I believe that even in WSL you can create this situation if not careful.

The easy solution is to boot from a Linux partition or Live USB, and use the more extensive file handling features to clean things up. You can use a user friendly distro like Ubuntu or Mint which will have a self-explanatory GUI. You can deal with it by deleting the files, renaming them, or putting them in something like a TAR archive (uncompressed but faster and simpler than zip). Tars can be mounted in Linux so that their contents appear like a normal directory, whereas Windows will see the single TAR file and won't bother to look at what's inside. Although when running Wine games off a mounted Tar, the performance overhead might be an issue.

I know you asked for a Windows solution. But your reason is that not everyone has WSL, whereas it's "not difficult" to get a live USB and boot from it. Well, the steps are easy, but it does sound confusing to many people.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »