Working off of network drives (MobileMe, thumb drives...)

[Juddbert]

Mike

There is a wealth of information online that details the Mountain Lion / NAS problems you, and others, are experiencing. For the record, my own NAS setup would seem to support Keith’s very detailed explanation. I have a 2TB NAS (Western Digital) drive that’s connected to a Billion Bipac 7800N broadband router. I’ve had a similar problem to the issue you’ve described, but with Adobe Photoshop files. My iMac and MacBook Pro both run Mountain Lion, and I’ve seen the problem on both machines. However, I also have an old PowerBook G4 running Scrivener 2.3.1 on OS 10.5 (Leopard), and that’s saving .scriv files to the network drive without any problems whatsoever.

Incidentally, your irascible and petulant responses to the developer’s attempts to assist say far more about you than they do about Scrivener. Just thought I’d mention it...

[AmberV]

Indeed, I have some types of files that I cannot use over a network file server either. If you are feeding your input/output through a straw, in a program that is used to a bucket, you're going to have problems. If a format doesn't work well, then you adopt check-out/in procedures with your work group, or just remember to backup copies to the network when you're done if it is yourself. You must understand that no computer professional would expect all Mac programs to operate with equal quality across a network file share. This is why many offices that deal in high disk usage formats have a policy about people not working off of the file server.

[wmike1503]

Mike

There is a wealth of information online that details the Mountain Lion / NAS problems you, and others, are experiencing. For the record, my own NAS setup would seem to support Keith’s very detailed explanation. I have a 2TB NAS (Western Digital) drive that’s connected to a Billion Bipac 7800N broadband router. I’ve had a similar problem to the issue you’ve described, but with Adobe Photoshop files. My iMac and MacBook Pro both run Mountain Lion, and I’ve seen the problem on both machines. However, I also have an old PowerBook G4 running Scrivener 2.3.1 on OS 10.5 (Leopard), and that’s saving .scriv files to the network drive without any problems whatsoever.

Incidentally, your irascible and petulant responses to the developer’s attempts to assist say far more about you than they do about Scrivener. Just thought I’d mention it...

Thank you for your personal comments - you know nothing about me but you feel qualified to comment on me personally.

Over and out.

[brookter]

The only evidence you have given so far of the 'real' you is that of rudeness, irascibility and arrogance in response to genuine attempts to help you.

Was that not the impression you wished to give? Then change the way you write.

Over and out.

[Juddbert]

Mike
...(omitted for clarity)
Incidentally, your irascible and petulant responses to the developer’s attempts to assist say far more about you than they do about Scrivener. Just thought I’d mention it...

Thank you for your personal comments - you know nothing about me but you feel qualified to comment on me personally.

Over and out.

Mike

If I’ve offended you then I apologise; that was not my intention. I made the observation, albeit in a clumsy fashion, to draw your attention to the fact that requests for assistance are generally best received when not accompanied by a welter of negative comments and churlish responses. Scrivener is, and remains, a superb example of independently developed software. It’s the result of one man’s vision, a man who has devoted years of effort to build what is generally lauded as the best writer’s software available — on any platform. Scrivener is used by a host of commercially successful novelists: just take a look at the testimonials: and yet you feel at liberty to rail about “major failings”, “very disappointing”, “it’s obvious to me that Scrivener cannot cope”, and other disparaging comments. You responded to Katherine’s attempts to assist with a dismissive “Ridiculous.” Well, I’m sorry Mike, but I consider that to be just plain rude.

You state that I know nothing about you. That’s not entirely true. I know enough from reading your posts to be able to form a first impression and, in my world, first impressions count.

I hope you find what you’re looking for.

Roy

[ScriverTid]

I apologise if this has already been covered here, but there are 18 pages to this topic and I don't have the energy to read them all!

Just to make two suggestions:

1. The problems reported with memory sticks MAY be caused by never having reformatted them, from FAT16 or FAT32 to Mac OSX format? I've used scores of them, I always reformat, and never had a problem.

2. Someone reported a disaster with Dropbox, that someone else managed to empty their Dropbox folder and they lost everything? It happened to me once (my own fault!) but I discovered when panic mode was subsiding, that Dropbox archive everything you've had in the folder and keep it for 30 days, including individual files you have deliberately trashed. So, you don't lose anything with Dropbox - just download from the archive anything you want : in my case that was everything (huge sigh of relief).

[Dehelix]

Well. I did it. I mangled my synched files by moving them to a cloud drive. Hey ho. At the time I did it I was rapidly running out of space on my SSD in my MacBook Air and it seemed like the most sensible solution. Dropbox was taking up an inordinate amount of valuable space on my SSD and then suddenly voila! Tons of space. Everything was fine for a time as I only use Scrivener on my Mac.

I am not a real writer, just lifelong dabbler. Since I learnt to write fifty years ago. Consequently I have at least six books on the go.

I noticed problems occurring whenever Scrivener got an update. Files that needed to be updated hit errors mostly saying that there was not enough space on the drive to complete the action. Everything is still there of course. I am sure I still have txt files I can open. It's just the Scriv files that are messed up.

Eventually as Scrivener developed and got more and more complicated (for me) as features were added and the synch issue got worse, I jumped ship to Ulysses. I recreated my binder structure for my most finished book and saved files into it. It now works a treat but I miss the flexibility of Scrivener.

Now however the long awaited day has arrived and Scrivener IOS has arrived. Hurrah!

What do I do? Wait until I can afford to buy one of those plugin memory cards that expand my Airs memory and I can move Dropbox back onto an Internet drive? Or, do I buy Scrivener IOS and work solely from my IPad until I buy the plugin memory card?

At the end of the day will I have to delete my original Scriv files as they are now too messed up to fix? I am thinking I will need to start again. Create new binders and upload the text files into them. It won't be a bind as I will be rediscovering stuff written years ago. I have a mind that likes that kind of task.

So to clarify, the questions are:

(A) - do I hold off until Dropbox is back on my SSD or
(B) - can I try and get some of the Scrivener experience back by just using it on my IPad or
(C) will doing so cause even more mess down the line? Or
(D) Buy the memory card, move Dropbox back and only then pick up Scrivener IOS and recreate my folder structure.

There you go. A nice simple problem!

[Silverdragon]

I can't give you a complete answer, but option "(B) - can I try and get some of the Scrivener experience back by just using it on my IPad" is certainly possible.

If you don't mind manually transferring projects via iTunes, you can live without Dropbox on your Mac. You will need to have the latest [2.8] version of Scrivener on your MacBook in order to work with a project created on your iPad. I have no answer as to whether your older projects can be recovered; someone from the Official Tech Support Team would be better for that.

[Dehelix]

Thanks Silverdragon. I just watched an overview of Scrivener IOS on YouTube that gives me some hope of resurrecting my projects.

[rdale]

The latest dropbox app updates have a feature called "selective sync", which lets you... wait for it... selectively sync just some of the folders that have been uploaded to the dropbox serve. If you keep your Scrivner files all under one folder (as is necessary with the iOS version), then only syncing that folder should prevent the rest of your dropbox data from filling up your internal drive.

[WrittenInAVacuum]

After posting a question about iCloud (and frankly same question on Google Drive) I found this thread (which is a decade old).

Is this still the case with version 3?

[lunk]

Yes.
The project format hasn’t changed.

[tarzanofmars]

A military saying that all should learn and implement:
If you have two, you have one, if you have one, you have none.

My Scrivener project is backed up on my macbook, it is backed up on a thumbdrive, and it is backed up on google drive, every time I work on it.

I write for an evening, clicking 'save' several times throughout, then I drag/drop the backup (in zip form of course) to the thumbdrive and drag/drop it to google drive every time I finish for the day.

You will lose it if you only have it backed up in one place. Sometimes I even throw it on a 2nd thumbdrive I have on my desk.

[devinganger]

A military saying that all should learn and implement:
If you have two, you have one, if you have one, you have none.

My Scrivener project is backed up on my macbook, it is backed up on a thumbdrive, and it is backed up on google drive, every time I work on it.

I write for an evening, clicking 'save' several times throughout, then I drag/drop the backup (in zip form of course) to the thumbdrive and drag/drop it to google drive every time I finish for the day.

Oh, good, you're using Google Drive the correct way with a Scrivener file -- to store a copy of the .ZIP backup file.