8530 Verizon to Cricket flash + Sync questions

I am awaiting a used Curve 8530 (Verizon, bad ESN) that I bought on Ebay. I intend to flash it to Cricket myself. (It will be my first attempt at this.) I also intend to buy Cricket's voice/text plan and only access the Web using Wi-Fi.
I have the phone software and PRL files -- but phone doesn't come with BB software disk. I need it to sync my calendar and tasks and thought using Outlook was best idea for that. I have XP, Outlook 2000. Since my Outlook software is so old I have learned that I should download desktop manager 4.2.2, which I have found online.
Since my phone is a Verizon phone, do I need to use a Verizon version of desktop manager? Also, do I lose any functionality by using 4.2.2 as opposed to a newer desktop manager version? (Since Outlook is expensive, I'd rather stick with one I have, but am willing to upgrade if necessary to make phone function well.)
Also, I have read that I should use qxdm only when flashing the phone because qpst can cause problems and make phone "unprogrammable," which I am guessing means that phone wouldn't update its PRL file via *228. Other people say they used qpst without a problem. Is this good advice - not to use qpst?
Finally, after much research I have found many different ways to flash a BB to Cricket. This brings up various possibilities: 1) there are many ways to do this and they all work equally well; 2) there are many ways to do it and depending on which way I choose you will get various degrees of functionality as a result; 3) some of the ways I have found will work and some won't.
Although I do not plan on buying a data plan, much less a BB plan, I would nevertheless like the phone "fully flashed" in the event I later decide to pay for the data plan or BB plan.
I would appreciate any additional advice one make have for me. Thank you.

Here's how I solved my problems: Phone arrived and was a Sprint phone. Bought the MSL (unlocking code) for $7.50 on eBay. Then tried to flash phone. Phone software didn't operate as advertised and I spent %40 on flashing. Got Outlook 2003 and syncing is fine. Old phone number ported today but phone would not OTASP (*228 programming), so now have to take it into Cricket store tomorrow. Oh, phone gets weak signal, have to go on my porch to use it. Hopefully when phone properly set up the signal will be stronger. What a headache!

Similar Messages

How do I reboot my machine when it is flashing a question mark folder?

How do I reboot my machine when it is flashing a question mark folder?

Booting From An OS X Installer Disc
1. Insert OS X Installer Disc into the optical drive.
2. Restart the computer.
3. Immediately after the chime press and hold down the "C" key.
4. Release the key when the spinning gear below the dark gray Apple logo appears.
5. Wait for installer to finish loading.
After the installer loads proceed through the installation procedure. If you are reinstalling Snow Leopard then your hard drive will not be erased.

FCP Sound Syncing Question

Hey Everyone,
I have an audio syncing question for you. Any help would be greatly appreciated!
I am cutting in FCP. I logged and captured my footage and with timecode breaks, etc. the tape was cut up, and I was left with eight files, let's call them Footage1-Footage8. I have completed my cut of the piece using the in-camera audio that was linked to the video on the DV tape that I imported. Our sound guy in the field used a DAT recorder to record the production audio and apparently captured the timecode to the audio files, so that it matches the video (i.e. the DAT recorder and our cameras - DVX-100s had synced timecode during the shoot). The DVD he gave me has 20 audio files as .wav, let's call them Audio1-Audio20. My question is, now that I have finished my cut, I would like to replace the current audio tracks with the production audio. How can I sync the audio with the video and replace it in what I've cut. Or perhaps I can't, in which case - how can I sync them up and THEN cut, but I'd really rather have to not do that, lol!
Thanks for your advice!

Sorry about the long winded post, though.
I guess my real question, summarized is - is there a way to sync separately recorded production audio (that has timecode) with the footage that I shot (that has the same timecode as the audio, but also has in camera audio that accompanies the video track - I would imagine I can just "cut" the extra audio tracks, however).
I'm at my bay trying to figure this out, and I've got nothing, and the people I work for don't want to spring for that bwf2xml program you were talking about What's the emote for pulling one's hair out?

Mac book pro flashing a question mark folder

What does it mean when my mac book pro is flashing a question mark folder and will not boot

There are four general causes of this issue:
1. The computer's PRAM no longer contains a valid startup disk setting when there aren't any problems with the disk itself. This can be checked for by pressing the Option key and seeing if the drive appears.
2. The internal drive's directory structure has become damaged. This requires usage of an alternate bootable system to perform the repair.
3. Critical system files have been deleted. This requires usage of an alternate bootable system to reinstall them.
4. The internal drive has died or become unplugged. This is the most likely case if the computer took a sharp impact or there are unusual sounds coming from the hard drive's location.
(86432)

My old iMac (screen sits on a white dome) opens with a tiny folder that flashes a question mark, instead of a login to user's desktop

My old iMac (screen sits on a white dome) opens with a tiny folder that flashes a question mark, instead of a login to user's desktop, when booting up after a forced shutdown. How do I get my operating system working again? Thanks --Jim

The blinking question mark indicates that the firmware could not find a valid Operating System on your machine.
Your harddrive may have failed. Your filesystem may have be come corrupted.
Try these things.
-- try to boot up from the installation disc.
The startup manager will list all of your bootable partitions then give you a choice of which to boot. Hold down the option key then power on. Continue holding down the option key until you see the startup manager. This brings up the startup manager. Click on your hd or disc. Click on right arrow key.
-- Sometimes if volumes don't appear in Startup Manager (what you get when you hold down the Option key at startup), you need to reset the Mac's PRAM, NVRAM, and Open Firmware. Shut down the Mac, then power it up, and before the screen lights up, quickly hold down the Command, Option, P, and R keys, until the Mac has chimed twice more after the powerup chime.
Then, before the screen lights up, hold down Command-Option-O-F until the Open Firmware screen appears. Then enter these lines, pressing Return after each one:
reset-nvram
set-defaults
reset-all
"The reset-all command should restart your Mac. If so, you have successfully reset the Open Firmware settings."
http://support.apple.com/kb/TS1812?viewlocale=en_US
Should the fail...
Try taking the battery out for 10 minutes. Put battery back in. Cross fingers. Power the machine back on.
How to eject a cd from the internal cd drive:
eject cd
List of devices:
devalias
List of variables:
printenv
More than you ever wanted to know about open firmware
http://www.firmworks.com/QuickRef.html

Folder w/flashing gray question mark

Hello,
I have tried every and all the suggestions given here for when all that shows is a folder with a flashing gray question mark. I was told that the reason for the flashing question mark is the hard drive is no longer working. I have a lot of things on my computer and would like to make a back up of them, before I have it repaired. Is there anything else I can try to be able to reboot it and get all my files out of there? I'd appreciate any help or suggestions. Thank you very much!

Aqua
Re: Folder w/flashing gray question mark
Feb 1, 2013 1:52 AM (in response to Arranques)
Pram Reset shouldn't do that.
How to use FireWire target disk mode...
http://support.apple.com/kb/HT1661
http://en.wikipedia.org/wiki/Target_Disk_Mode
Can you or I be more specific?
I know how to set up to get to the T mode. What I'd like to know is, once I'm there, what is it that I'm supposed to do? And can I be more specific about what? I just looked at the disc I inserted to be able to startup, and it is Tiger. So the OS is Tiger and did have the computer partition. I had Tiger on one side and Leopard on the other. I know, it keeps getting more complicated as I go along. Thank you for the links.

White screen with a flashing folder & question mark

My IMac froze today and when I turned it off and then back on, it just sticks on a white screen with a flashing folder & question mark... Help?

Reinstall Snow Leopard without erasing the drive
Do the following:
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.
Reinstalling Lion Without the Installer
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alterhatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion: Select Reinstall Lion and click on the Continue button.
Note: You can also re-download the Lion installer by opening the App Store application. Hold down the OPTION key and click on the Purchases icon in the toolbar. You should now see an active Install button to the right of your Lion purchase entry. There are situations in which this will not work. For example, if you are already booted into the Lion you originally purchased with your Apple ID or if an instance of the Lion installer is located anywhere on your computer.

Startup stuck on a Flashing Folder/Question Mark

Aloha,
I have been looking for a solution to my problem for several months now and have never found a solution.
One day my computer froze so I forced a shut down by holding the on/off button.
When I turned on the machine again the folder/question mark appeared.
I have tried all the hot keys.
Option-only shows the refresh and forward buttons but no options.
I thought my hard drive failed, so I bought a new one and installed it.
When I placed the OS DVD in to install a fresh copy I still got the flashing folder/question mark.
I don't know what to do, any suggestions?

sione wrote:
I don't know how to get to the system preferences if i can't get past the flashing folder/question mark.
Correct you'll not be able to...
The question mark appears when the boot loader cannot find a valid OS system/partition.
Here is what I would try:
1. Boot from the OSX installer by inserting the disk into the Mac then power-off. Power-on the Mac and immediately press and hold the "C-key" until you get the installer Language screen. Select your language and continue. The next screen should be the Welcome screen, go to the top and select Utilities/Disk Utilities from the tool bar. Once Disk Utilities is open select your internal (if it appears) then select the first aid tab. In the first aid pane select to run "Repair disk". If "Repair Disk" results in errors then run it again until it reports no errors found. Once "Repair Disk" is complete with no errors then press and run "Repair Permissions". Once complete reboot to test the Mac.
2. If the above does not work then try booting with the Startup Manager, by pressing and holding the "option-key" during boot. The GUI Startup Manager will appear and you can select the drive you wish to boot from.
3. Alternately press the "X-key" during boot.
4. And lastly before we give you the bad news... make sure that the mouse or track-pad button is not being pressed or stuck during system boot.
If none of these works then you most likely have a bad drive. And you'll need to replace it. You do have a back up right?
Do you have another Mac, to use for troubleshooting?

Installed Leopard, boots sporadically - Flashing Folder / Question Mark

I have installed Leopard onto my PowerMac G4. It was working for a few months, now it won't boot up most of the time. I am getting the flashing folder/question mark when I turn the computer on.
This problem doesn't occur all of the time. I was messing around with the two internal hard drives, switching them around inside the machine, and whatever I did must have worked because the computer booted up just fine. All of my files were in tact and everything looked normal. This lasted for about a day. Now my computer is back to the flashing folder on startup.
What could be causing this problem, and how can I fix it? Thanks!

Thanks for helping me, I really appreciate it.
It is the strangest thing. Sometimes it will recognize the hard drive and boot up normally. Other times it hangs on the Apple logo with the spinning wheel. And other times it doesn't recognize the drives at all and gives me the flashing folder. Same thing when I try holding down the option key and use the device manager. Sometimes it will see the drives, and other times it doesn't show anything.
I have replaced the hard drives, the hard drive cables and the PRAM battery. I am running out of ideas! Anything else that you can suggest would be greatly appreciated.

Flashing Folder/Question Mark on Startup

I have been having an issue with my machine for the past couple days, and cannot find the Install Disks to remedy this situation (my OSX 10.4.4 disks will not recognize), so ANY help would be appreciated.
I have been able to troubleshoot using FireWire target disk mode. I've run DiskUtility and DiskWarrior on this machine from another machine and everything checks out with the hard drive, but I keep getting the Flashing Folder/Question Mark on Startup. Safe boot (Shift key at startup AND Shift-Command-V) do not work. Resetting the NVRAM / PRAM does not work.
Suggestions?
I don't need the info on the machine, as I am trying to set this up fresh for my wife.

But I was going on the assumption, as it was an internal drive (not an external data only drive), he had an OS installed, since his problem seemed to be that out of the blue he was getting the flashing folder question mark on startup. He had written +"I have been having an issue with my machine for the past couple days...."+ implying that it had booted normally before that.
Anyway, you're probably right; I'm just puzzled: how would his once bootable OS disappear just like that? Obviously something I'm not understanding here.

Flashing folder question mark on boot

I started my computer today, and I hear this high-pitched noise and then clicking sounds. Then I see the flashing folder question mark. Could this be hard drive failure? Or is it the DNSChanger virus? I've tried to access the Recovery, but Command-R and the Option key don't work. When I use Option, all I see is a white screen with a pointer.

Compukid wrote:
When I tried Option, it showed a white screen and the cursor.
That's the firmware driven, no drive means either OS X is fried and can't boot, or the drive is dead, or it may be that something is wrong with the Mac or a cable, which if the drive is still good, will work later or in a SATA to USB adpater on another Mac or PC with MacDrive installed. You won't know that unless it's pulled out of the machine.
When I tried to move the mouse (a wireless one, if that helps), it did not move.
Can't use a wireless mouse, as the drivers load with OS X and OS X isn't booting, use the wired one or the trackpad.

IPad Mini 2 and iPhone 5s message syncing question

My friend and I were on vacation in Japan over the last two weeks. He took his Verizon iPhone 5s with him to Japan, but left his iPad Mini at home. While in Japan, his nephew sent him a text message. It was received on the iPad Mini which had service, but not on the iPhone which did not have service in Japan. The Verizon phones apparently aren't compatible with the cell systems in Japan. He never connected it to wifi either which was an option. My question is should the messages received on the iPad sync once he has returned home? My thought is that they would not, but I wondered if anyone had a definitive answer.

What are you trying to accomplish? Connecting a phone to a Mac is only supported for tethering.
Barry

Log file sync question

Metalink note 34592.1 has been mentioned several times in this forum as well as elsewhere, notably here
http://christianbilien.wordpress.com/2008/02/12/the-%E2%80%9Clog-file-sync%E2%80%9D-wait-event-is-not-always-spent-waiting-for-an-io/
The question I have relates to the stated breakdown of 'log file sync' wait event:
1. Wakeup LGWR if idle
2. LGWR gathers the redo to be written and issue the I/O
3. Time for the log write I/O to complete
4. LGWR I/O post processing
5. LGWR posting the foreground/user session that the write has completed
6. Foreground/user session wakeup
Since the note says that the system 'read write' statistic includes steps 2 and 3, the suggestion is that the difference between it and 'log file sync' is due to CPU related work on steps 1, 4, 5 and 6 (or on waiting on the CPU run queue).
Christian's article, quoted above, theorises about 'CPU storms' and the Metalink note also suggests that steps 5 and 6 could be costly.
However, my understanding of how LGWR works is that if it is already in the process of writing out one set of blocks (let us say associated with a commit of transaction 'X' amongst others) at the time a another transaction (call it transaction 'Y') commits, then LGWR will not commence the write of the commit for transaction 'Y' until the I/Os associated with the commit of transaction 'X' complete.
So, if I have an average 'redo write' time of, say, 12ms and a 'log file sync' time of, say 34ms (yes, of course these are real numbers :-)) then I would have thought that this 22ms delay was due at least partly to LGWR 'falling behind' in it's work.
Nonetheless, it seems to me that this extra delay could only be a maximum of 12ms so this still leaves 10ms (34 - 12 -12) that can only be accounted for by CPU usage.
Clearly, my analsys contains a lot of conjecture, hence this note.
Can anybody point me in the direction of some facts?

Tony Hasler wrote:
Metalink note 34592.1 has been mentioned several times in this forum as well as elsewhere, notably here
http://christianbilien.wordpress.com/2008/02/12/the-%E2%80%9Clog-file-sync%E2%80%9D-wait-event-is-not-always-spent-waiting-for-an-io/
The question I have relates to the stated breakdown of 'log file sync' wait event:
1. Wakeup LGWR if idle
2. LGWR gathers the redo to be written and issue the I/O
3. Time for the log write I/O to complete
4. LGWR I/O post processing
5. LGWR posting the foreground/user session that the write has completed
6. Foreground/user session wakeup
Since the note says that the system 'read write' statistic includes steps 2 and 3, the suggestion is that the difference between it and 'log file sync' is due to CPU related work on steps 1, 4, 5 and 6 (or on waiting on the CPU run queue).
Christian's article, quoted above, theorises about 'CPU storms' and the Metalink note also suggests that steps 5 and 6 could be costly.
However, my understanding of how LGWR works is that if it is already in the process of writing out one set of blocks (let us say associated with a commit of transaction 'X' amongst others) at the time a another transaction (call it transaction 'Y') commits, then LGWR will not commence the write of the commit for transaction 'Y' until the I/Os associated with the commit of transaction 'X' complete.
So, if I have an average 'redo write' time of, say, 12ms and a 'log file sync' time of, say 34ms (yes, of course these are real numbers :-)) then I would have thought that this 22ms delay was due at least partly to LGWR 'falling behind' in it's work.
Nonetheless, it seems to me that this extra delay could only be a maximum of 12ms so this still leaves 10ms (34 - 12 -12) that can only be accounted for by CPU usage.
Clearly, my analsys contains a lot of conjecture, hence this note.
Can anybody point me in the direction of some facts?It depends on what you mean by facts - presumably only the people who wrote the code know what really happens, the rest of us have to guess.
You're right about point 1 in the MOS note: it should include "or wait for current lgwr write and posts to complete".
This means, of course, that your session could see its "log file sync" taking twice the "redo write time" because it posted lgwr just after lgwr has started to write - so you have to wait two write and post cycles. Generally the statistical effects will reduce this extreme case.
You've been pointed to the two best bits of advice on the internet: As Kevin points out, if you have lgwr posting a lot of processes in one go it may stall as they wake up, so the batch of waiting processes has to wait extra time; and as Riyaj points out - there's always dtrace (et al.) if you want to see what's really happening. (Tanel has some similar notes, I think, on LFS).
If you're stuck with Oracle diagnostics only then:
redo size / redo synch writes for sessions will tell you the typical "commit size"
redo size + redo wastage / redo writes for lgwr will tell you the typical redo write size
If you have a significant number of small processes "commit sizes" per write (more than CPU count, say) then you may be looking at Kevin's storm.
Watch out for a small number of sessions with large commit sizes running in parallel with a large number of sessions with small commit sizes - this could make all the "small" processes run at the speed of the "large" processes.
It's always worth looking at the event histogram for the critical wait events to see if their patterns offer any insights.
Regards
Jonathan Lewis

Flashing gray question mark after 10.5.8 update?

This isn't so much a post to ask for help, as it is just trying to see if anyone got the same result and what you had to do to resolve it.
Yesterday I updated to 10.5.8 and it did it's install and then restarted the system. Upon restart, it did the initial start-up charm and then loaded up to a gray screen with a flashing folder icon with a question mark on it.
I called Apple support and we walked through repairing the disk with the disk utility, so on and so forth, and I'm still stuck with the same screen. The support agent says the next step is to fully reinstall the OS X...
So that's my next step. I'm currently waiting for a friend of mine with a MacBook to come over so I can put my iMac into Target Disk Mode and pull some files before deleting everything.
Anyone else?

You may not need to erase your drive. See:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

Aperture 3 library syncing question

I want to move to Aperture, but I need some advice first. (I have considered Aperture in the past, but my expectations and demands were unrealistic. Now I am trying to be as realistic as possible about what I want from Aperture.)
I have learned that Aperture 3 in fact supports syncing libraries between computers. Before I attempt this however I want to find out from you people whether what I want to do will work.
First let me describe my situation.
I have Mac Pro which contains the following types of files dating from 1997:
RAW + JPEG pairs from my DSLR, mirrorless, and compact cameras
JPEG solo images from DSLR, mirrorless, and compact cameras
TIFFs, PSDs, and JPEGs from film scans
TIFFs, PSDs, and JPEGs that are saved, edited versions of the above (edited files have the same filename as the original, plus a few letters added to indicate which changes have been made; s = sharpened, a = converted with ACR, c = cropped, w = web resolution, etc.)
AVI, MOV, MP4, and MTS (AVCHD) movies shot with various digital cameras
There are 160,383 files in total, although the number of photographs is probably less than 100,000 due to RAW + JPEG pairs counting as two files. The total space used is ~1.2TB. The files are on an internal 2TB RAID volume, which is constantly backed up to an external Time Machine RAID.
The files are all organized into folders by year up to 2009, and inside each year's folder are sub-folders that organize the pictures by event. All photos taken after 2009 are organized either by event or by subject matter, depending on which seemed more relevant to the particular shoot. I have been using Adobe Bridge to sort them. After they are sorted, I use a wonderful gem called ChronoSync to sync the JPEGs only (but not the RAWs, TIFFs, PSDs, or movies) to my MacBook Pro. That way I have my photos with me in the field in case I want to make some prints, upload to Flickr/Facebook, etc.
However, I am feeling many limitations of this workflow -- hence why I am considering Aperture.
Here are the main things I want to do with Aperture. Please tell me if this will work, and what any gotcha's might be.
I want to have a "master" Aperture library on the Mac Pro. I will add all my existing files into the master library in a 'referenced' fashion -- they will remain where they are in the current directory structure on the 2TB RAID.
I want to also maintain a "satellite" Aperture library on the MacBook Pro that contains only the JPEG versions of these files. I would use ChronoSync to copy over all the referenced JPEGs such that they exist in the same places in the directory structure of the laptop as they do on the desktop (i.e. /Users/me/Pictures/etc.), so that hopefully when Aperture looks for them it can find them. (I am guessing that I would create the "satellite" library by simply copying the "master" library to the laptop, rather than creating a fresh library there.)
I want to use the "satellite" library on the MacBook Pro to perform tagging, adding location data, rating, further organizing, etc. and then sync those changes back to the "master" library on the Mac Pro.
I know that Aperture 3 has the ability to sync/merge libraries, but my questions are:
If the "satellite" library has only the JPEGs available on the local drive, then will any metadata changes made in the "satellite" library properly sync back to the JPEG+RAW pairs in the "master" library? I.e. will Aperture still apply changes in metadata to both the RAWs and JPEGs, even though the RAWs were not present on the "satellite"?
Will Aperture allow me to group other versions of the file besides the RAW and JPEG on the master library? Will metadata to just the JPEG also be applied to these other versions upon syncing, as described above?
Is it a "two-way sync" -- i.e. will changes made to the master library also sync back to the satellite library? (If not, that's OK with me, because presumably after merging the satellite into the master, I can delete the satellite library, then re-copy the master back to the laptop to make a new satellite library -- I am also going to have copy over any new JPEG files to the laptop as well, so I don't mind copying one extra file [the new satellite library].)
I'm sure I've forgotton something important here but, my time is limited so I'll leave it at this for now and post any other questions later. Thanks for any tips, I know this is a complicated issue.
-=DM=-

I still need to do some experimenting to see if the file references are volume-specific or if they are volume-blind -- i.e. if they just use paths starting with "/[path]" instead of paths starting with "/Volumes/SpecificDriveName/[path]".
I am not sure I understand you fully - what kind of file referencing are you speaking of?
If you use managed master image files, the master images are stored inside the Aperture library, and if you move the complete library to a new drive, then thereferences to files inside the package still work. So obviously Aperture uses relative pathes here.
If you use referenced master image files - let's for example assume the Aperture library is on Volume A, the referenced master image files are on Volume B, and you move your Aperture library now from A to Volume C: If you open the Library on Volume C, it will still find the master image files on Volume B, so the library stores the absolute path for referenced masters. This even works with referenced masters on network volumes, but I really cannot recommend to store the masters on remote volumes; you will have to make sure the volume is mounted, when you launch Aperture.
Is that what you were asking about? if not, please rephrase your question.
Regards
Léonie

8530 Verizon to Cricket flash + Sync questions

Similar Messages

Maybe you are looking for