How do think I got this far?
Being a mod, having my real-life credentials, all goes out the door when you ask questions like that with an Evo listed in your devices. Samsung fans tend to be one-way, and unless the question is sugar-coated, you get flamed. Yes - flamed, with a red name tag.
If you can succeed where I failed, please do, the info will be helpful.
And nope, I don't have a Kingdom. I even tried to ask WifelyMon if she wouldn't mind me trading her Shift for the upcoming Kingdom with the bigger screen, 50% faster processor, the ... As she looked at me, my tan increased and the paint around my shadow on the wall blistered a little - so it's not clear to me yet if I'll be able to pull that off or not.
We're talking about filesystems. The last sentence is correct - sorry to be blunt, but it is what it is. Try following symbolic links in Windows via software, not the mouse. You can't - symbolic links in Windows can't get the same name as a real directory path - the links are appended with the suffix: .lnk for link. (If they've fixed this, I'd be wrong - but after being disgusted by it, I've stopped checking for fixes to that.) Paths with links are not the same as hard paths in Windows. They copied what the feature looked like, not how it works. Take working code written for one drive, then distribute its pieces across multiple drives without modifying anything or having to resort to extra code for drive lookups (or dear god using registry entries) - you can't. Check the man page for ln - note there are symbolic links and hard links in Linux - Windows has no clue about the other kind at all. And Windows use of the backslash for directory path separation isn't simply different from the Unix way of using slashes - it's flatly wrong and is a holdover from DOS.
Unix has a much more elegant set of filesystem rules than Windows if for no other reason than it is complete.
Same thing on lots of infrastructure elements, such as networking. Our company builds industrial software, cross-platform for various Unices and Windows. Complex UDP transport operations for interprocess data sharing that run for days on end on Unix won't on Windows and can't - the
window manager actually breaks those transactions if given time, so that all has to be re-coded to use non-transportable Windows shared memory.
It's a big list of things that Windows may seem do, but doesn't do correctly or elegantly at all.
More people eat Micky D's burgers than any other kind, but it doesn't make 'em better at all.
PS - The final bit of full flexibility in achieving full and total memory flexibility and fooling the OS into using internal memory and SD card memory at the same time and just calling it /sdcard fails because - the primary partition on the SD card is FAT32 (Windows file system).