Update OS 1.5 File Uitil COPY/MOVE

"A physical volume's file SYSTEM (FAT16, FAT32, NTFS, ZFS) and an embedded OS'es file STRUCTURE are two completely different things"

I have no problem with this staement.. just the part that says "this has nothing to do with FAT"

I'm sure he will be back soon.. I've had the playground to myself for too long

Thank you Flumpster!

"Some of the most positive posts about the G on the site are from individuals that have decided not to use it yet".

Still positive about what the G has the potential to become. Will wait and watch - and buy only when it does what I need it to - Im not in the impulse-buying category - and only buy when Im sure that a given piece of gear will do exactly what I want from it. Unfortunately money is in short supply these days - and cant afford any mistakes .

I still believe that Roland will take the G to greater heights - simply because of all that unrealised potential it has, only Im not sure it's going to happen in the timeframe that some of the tireless negative-posters want - no matter what they do or say.

Petitions, and complaints and bug-reports and other instruments of corporate-policy-revival are fine, and work when the underlying production machinery is sound, and well staffed. When it's not - as I suspect it to be the case currently, all these efforts are going to be encountered by helpless shrugs, and half-smiles, and our case silence.

OS 1.5 to me was more of a token release - which is not necessarily a bad thing - it could mean the machinery is being revived - and this was simply a test . There are good things coming, maybe?

Anyway - here's why I post to a thread concerning a device that I dont even own . I can assure you that Im not a Roland/Yamaha/Korg corporate shill - in fact I dont even work for the music industry. I am a serious musician though - and this site (Thanks to the countless hours that Art and the mods put in) - has helped me a lot in understanding key concepts in synth technology and electronic music (there's a wealth of information in here, and it's all searchable) in the past few years. I would hate to see this site damaged or get a bad rep because of a few dissenters - who in their fierce determination to straighten things out at Roland Corp (I guess they're justified in doing so - I have my own axes to grind against Roland - and the corporate mentality in general ) - are doing damage to this community of musicians. All Im talking about again - is striking a balance between the negatives and the positives, y'know?

But of course - this is just me - not sure how others feel about the same.

Peace -

Manish

Manish, you know my way of keeping the balance, you ban a few guys once in a while, and all becomes fine... LOL!!!

"you ban a few guys once in a while, and all becomes fine... LOL!!! "

Can I be next... please, please

Flumpster, I can do a nice trick, I set you a "banned" badge, but you can still post here, I think you will like it! Sort of like you're banned, but not quite. Very cool!

Okay here is a very basic principle that should explain how MOVE should work on the G and how it works everywhere else for those having a hard time with it..

Command RENAME <--

file1 (2GB) exists in folder1 and folder2 is apparently empty

I issue the command

Rename :folder1/file1 to :folder2/file1

as soon as i have pressed the execute or return the file appears in folder2 instantly and the original file1 has not been recopied or physically moved from the space it occupies on the flash drive and also because it remains on the same physical media.

So on a very basic level the file or files being moved regardless of sized have simply been renamed so there was no need to duplicate the data and then delete the old duplicate.

This is what always happens when a MOVE function or command is executed on other devices be it a pc mp3 player or other such devices and is instant.
Hopefully this clarifies and gives a better understanding of how it suppose to work correctly.

"Flumpster, I can do a nice trick, I set you a "banned" badge, but you can still post here, I think you will like it! Sort of like you're banned, but not quite. Very cool! "

I'd rather have one that said "I fought the law but the law won" =]

http://www.youtube.com/watch?v=16u0wwCfoJ4

Flumpster:

"A physical volume's file SYSTEM (FAT16, FAT32, NTFS, ZFS) and an embedded OS'es file STRUCTURE are two completely different things"

I have no problem with this statement.. just the part that says "this has nothing to do with FAT"

My posts were probably obtuse because they're interspersed with random blatherings that may or may not be directly referencing your posts, Flumpster. So I apologize for jumping all over the place.

By "nothing to do with FAT", I mean the way that Roland chooses to treat their file structure (that is, *like* multiple partitions or volumes—not to imply they are actual, physical partitions) is independent of the capabilities of an index-based file system.

Obviously, Roland is capable of rewriting the lines of code overseeing project file structure so that a solitary, obscure function in a late-in-the-game OS update—like moving files from one project to another—behaves differently from any of their other project management functions. Obviously, we've all seen how backing up, saving as, and restoring projects can duplicate a ton of data. It's worked that way for over two years. The entire file structure quite obviously appears to be written around the assumption that projects should be treated *like* partitions—separate Fantom-Gs, if you will. The G's internal project is very separate from any USB flash project, and the rules that govern shuttling data from the internal project to a USB project and back can very easily be applied to shuttling data from a USB project to another USB project. This may be done for consistency's sake, this may be done to share lines of code—hell, the entire file structure may be based around this assumption, especially considering there was *zero need* for pointer-based indexing in the existing file structure until 1.50, and even then, ONLY for one, obscure, random function... which still works exactly as advertised!

OKAY, STOP READING NOW

This is where I'll predictably digress (and you'll zone out and lose interest, which is perfectly fair) and get to my real point, which is who really f@#$ing cares? This is the most pointless (albeit thought-provoking) complaint I've read about the Fantom-G yet.

I will give Quinnx major brownie points for stirring up conversation though.

Has anyone actually called Roland and asked them about this? I'd do it myself, if it weren't for the risk of them rolling their eyes so hard they get whiplash.

I guess this explains it all.

I must do my "mea culpa" here since I've lighted some fire here and there on the thread. But I just did it for pure curiosity. I really would like to understand it a little better. I do now. But I completely agree with TAW: who cares? It seems this is of major importance for Quinnx since apparently he spends much time moving files. I'm fine with that. I just don't want him to misslead no one with one of those "don't work" statements.

"Has anyone actually called Roland and asked them about this? I'd do it myself, if it weren't for the risk of them rolling their eyes so hard they get whiplash. "

I was on hold with Roland UK for 30 mins yesterday, they had 2 support people on phone and 2 before me so I gave up.. I'll try them again today. As for them rollying eyes at me I really couldn't care less.

"and get to my real point, which is who really f@#$ing cares?"

I don't.. as I said in my first post I haven't even installed the update

Did sort of half enjoy it tho in some morbid sort of way.

Stay lucky TAW, no hard feelings.

edit.... still want my "I fought the law" badge