Stocks A to Z / Stocks B / Berkshire Hathaway (BRK.A)
No. of Recommendations: 0
I have a Dual Boot Mac-Windows problem which really baffles me. The problem is on the Mac side and I am a pure Windows guy. I could ask on the "macuser" forum, but I hate to register anywhere unless there is absolutely no other way. I know that a lot of the active posters are computer geeks (plus who knows how many of the not posting ones). So sorry for asking this:
I have an iMac, dual boot (Catalina+Win10), 100% used as a Windows machine, but recently installed iMovie to do a bit of video editing. To make data exchange easier yesterday I deleted under Windows one of the internal SSD's 7 partitions, recreated it and formatted it with ExFat to share files between both OS. Result:
- Files I create on that partition under Windows I can read/write under MacOS
- Files I create on that partition under MacOS are not visible under Windows
(And no, activating "Show invisible files" does not help; for Windows it's as if they don't exist)
That concerns only that internal SSD's ExFat partition, not if I go around it and exchange files via ExFat formatted USB stick.
I apologize for this super OT question.
No. of Recommendations: 0
It is probably some sort of obscure permissions issue.
There are a couple of Windows command line commands that you can try. They solve all of my weird file problems.
Sorry, I don't have them at hand, but you can google them.
1st sets you as the owner of all files in a directory.
2nd removes all permission restrictions.
OTOH, I have run into another Windows file problem that I have not been able to fix. A file shows up in the directory listing but when I try to delete it, it says "No such file".
No. of Recommendations: 1
While it is not directly responsive to your question, a debugging tactic would be to mount the partition from Linux and inspect it there - at least you would get an idea of whether the Linux filesystem drivers interpreted it sensibly. You could do this from a USB Linux distribution, or probably from WSL using the 'wsl --mount' option though I haven't touched WSL in ages.
No. of Recommendations: 6
... I know that a lot of the active posters are computer geeks ...
There are quite a few more over at the Mechanical Investing board. As with here, folks are generally helpful if a post is marked OT.
Jim
A couple of random thoughts, cribbed from one of those evil AIs, and re-interpreted by me and therefore probably even less reliable.
Allegedly, MacOS and Windows use different default allocation bock sizes on large drives (Mac smaller).
It could make a difference which OS was used to format the partition for that, or other reasons. Rumour has it that formatting under Mac is more compatible
Allegedly, there are two types of allocation tables, GUID/GPT and MBR. The latter is sometimes more common on external media, and sometimes more universally compatible. Check which was used.
So maybe format it again using the macOS Disk Utility, ensuring you use the MBR partition scheme?
No. of Recommendations: 0
GUID/GPT and MBR ... It could make a difference which OS was used to format the partition ...
So maybe format it again using the macOS Disk Utility, ensuring you use the MBR partition scheme?
Thanks (to oddhack too), but using GUID or MBR is a decision you have to make right at the beginning as it's not about how one single partition is used, but about the whole disc's partition scheme. So all partitions would need to be deleted, dual boot and all partitions with their contents recreated again.
Btw: I regret and apologize for posting in desperation this far too OT question and hope it does not set a bad precedent. I suggest who has another tip sends it via private message ("Privately email Said only" underneath the posting text box).
No. of Recommendations: 0
To end this and give feedback: Though it was not about GUID versus MBR (I was not willing to initialise/erase the whole drive to change it's partition style) Jim's "Rumour has it that formatting under Mac is more compatible" and formatting just this one partition again under MacOS was the (still mysterious) solution :)
