Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About unbound

  • Rank
    New Mac Geek
  1. Your response, although quite smarmy, deserves a reply. Having to eject is not the point. To me data integrity is and always takes priority over system speed. A fast system that loses data is worthless. Removable media should NEVER have write behind enabled, because cards and drives can get removed at any time. Typically 'Write behind' is not used on networks either, because network connectivity can be lost for a number of reasons, and data loss is likely in that case. In Windows, you have to explicitly enable 'write behind' on removable drives, because it is so dangerous. Data gets written righty away, the FAT get's updated right away, not a couple of minutes later when the system finds it convenient. So my question stands... how do I configure OSX to disable 'write behind' on removable media?
  2. "Write behind" is a method of accelerating system performance by keeping data in RAM that is meant to be written to a drive, and writting it later whenever a good opportunity comes up. So you might do a 'File Save', while the computer is really busy doing something else, and instead of the file being immediately written, it just sits in RAM for a while. It may be 5 seconds, or it could be a couple of minutes. The purpose of the 'Eject' command is mainly to force a 'flush' of memory into the drive or card, without any further waiting, so any pending writes are done right away, and the card can be then safely removed.
  3. I work with both PC's and Macs, and there is something that I really, really hate about Mac and OSX: the need to explicitly manually eject removable drives and cards or risk data loss and corruption. On more than one occasion, in the 'heat of the job', I have forgotten to eject a media card before removing it, resulting in having the next card utterly corrupted when it is inserted. I am a photographer that may fill up 6 or 7 cards in a day, and I have to download all that data. What happens is that when you insert a card without having ejected the previous card, the FAT info from the previous card overwrites the FAT on the new card, utterly corrupting the card. The only way that we have found to recover from this disaster is to go to a PC and use some pretty heavy duty file recovery utiliies. I kow someone that had the same thing happen whith an entire removable USB drive when he switched drives. Many GB of data lost. In Windows, by default removable media is tagged for "No Write Behind", so all the data is basically written ASAP and the card put back in a 'current' condition. No 'Eject' is needed. Where the heck in OSX is the 'No Write Behind' setting for removable media??????
  4. unbound

    New Mac Mini

    I checked out the Mac-Mini as soon as it was announced, because I intended to buy one, but got stopped cold by the price. By the time I got done configuring it, the little box was over U$1000, which is pretty darn steep, when you consider that the price does not even include a monitor. I currently travel a lot, and use a G4 Powerbook while on the road. Since I have a monitor at each location, and my home machine needs replacing, I figured I would just get a Mac-Mini, which I could pack in my carry-on case and take with me and use as a pseudo-desktop system at home and at the other workplaces. But adding RAM, a slightly larger drive and AppleCare just sent the price zooming. By all rights the base dual-core should be a sub-$500 unit, no more that $700 loaded. What is the point of this box when a new iMac 17" is about the same price and a better machine? Exactly what is the target market?