Olympus E-500?
I noticed on the Aperture camera page that the E-1 was a supported camera but there was no mention of any other model from Olympus even though the supported files include the Olympus file format.
Does that mean any Olympus camera that shoots RAW is supported? I was thinking about buying an E-500 and I'm a little concerned that Aperture won't support it.
PB 12 Rev D, PB 15/1GB RAM Mac OS X (10.4.3) iPod Nano(Black 4GB)
This question (and very similar ones) come up a LOT. It's really not safe to assume a camera will work, unless it is explicitly listed. Aperture gets its RAW support from Mac OS X, which lists supported cameras here:
http://www.apple.com/macosx/upgrade/cameras.html
If it says RAW, then you can use the camera with RAW files. If the camera is not, you probably cannot.
Similar Messages
-
Can anyone confirm if it works with Olympus e-500?
I'm really wanting to dive in to this software - I have about 4k photos, but I want to see if it will work with the e-500.
Thanks in advance!I own a brand new Olympus E-500 and Aperture 1.0.
There's no support for the RAW format in Aperture yet. Only Adobe Photoshop with the Camera RAW 3.3 plug-in and the original Olympus Master Software are able to open the RAW images from the E-500.
RAW images from my Nikon Coolpix 5400 are also not supported.
As I understand the System software has to support the image formats, not Aperture. I am sure Mac OS X 10.4.4 will add some cameras. You find a list of supported cameras here: http://www.apple.com/macosx/upgrade/cameras.html
G5 2x 2,7 GHz Mac OS X (10.4.3) -
Aperture 1.1 and Olympus E-500 RAW files
Hi there.
My problem:
RAW data from my Olympus E-500 isn´t supported by Aperture 1.1
After importing RAW files there´s no image data and the preview displays "unsupported image format"
I wonder why, since that camera is listed in the compatibility list under http://www.apple.com/macosx/upgrade/cameras.html
Even if it is not listed in the compatibility list of apertures supported RAW filetypes, in my understanding aperture should deal with those files if the OS supports the camera. But this understanding seems to be wrong..
I know that RAW files can be quite different in structure, so files generated by the E-1 seem not to be the same as RAW files generated by the E-500.. even if they have the same files extension. But I wonder that even the E300 is supported but not the E500.
Does anybody knows if there is a workaround for this or if there is a chance to use Aperture with these files in the near future?
Thanks for any information.
G5 Dual 2.5 GHz, 4GB RAM Mac OS X (10.4.6)I know that RAW files can be quite different in
structure, so files generated by the E-1 seem not to
be the same as RAW files generated by the E-500..
even if they have the same files extension. But I
wonder that even the E300 is supported but not the
E500.
You are indeed correct that the .ORF raw files generated by the E-1 and the E-300 are different from those generated by the E-500. Olympus must take the responsibility for this. I will assume that they had some good reason for changing the file structure between camera models, but I don't know what it is and have difficulty imagining what it could be. When the E-500 was released, there was considerable discussion about this on several forums (notably the Olympus SLR forum at dpreview.com) as there were several other software programs (sorry, can't remember which specific ones) that also had been working well with .ORF files from the E-1 and E-300, but did not support E-500 .ORF files.
Why Apple has not added support for the E-500 raw files is another good question, and I hope you've posted your request as feedback for the Aperture team. I am using Aperture and an E-1, and have been enjoying the combination ever since Aperture 1.0 was released. The raw conversions for the E-1 have definitely improved since 1.1 was released, so Apple knows something about .ORF files. I hope that you will also get to experience that (soon) when support for the E-500 files is added. I'm not aware of any workaround at this time, but will post here again should I come across one.
Let's hope that Apple has not simply assumed that all .ORF files are equal, and has not noticed that you have a problem. -
Olympus E-500 raw file problem with long exposures
Hi,
This topic has come up before, but wasn't resolved. Maybe its somewhere else, but I can't find it.
http://discussions.apple.com/thread.jspa?messageID=4994383�
Raw files from my Olympus E-500 with exposures over 3.2s come up with overexposed looking previews in Aperture. I think there is some automatic noise reduction (dark frame) info in these files, since they are 16.68Mb instead of the normal 13.47Mb. Apparently Aperture doesn't know what to do with these larger files.
Is there a known way around this within Aperture? The files open fine within Olympus Master 2 and Raw Photo Processor.
I've pasted a screen shot here with some links to raw files:
http://www.mso.anu.edu.au/~grant/wp/2007/10/raw-problems-with-aperture/
cheers
GrantYea, I've had that issue also and figured out the DNG workaround. Filed a bugreport with Apple on Nov 2nd, 2006. It sat with what looked like no attention right up until I got an e-mail on Oct 26th, 2007 (notice the date) saying that the issue was fixed in 10.5. I had already preordered Leopard so was hoping this was right. It wasn't. It's still borked. Logged notes back into the issue saying it wasn't.
Perhaps if more E-500 users report this it'll get more attention.
http://bugreport.apple.com -
Olympus E-500 is Still Not Supported iPhoto6 10.4.5 OSX
Please add RAW File support for this camera NOW!
"On the other hand : the fact that OSX / iSync can't find available services on my SLVR over Bluetooth is clearly a problem caused by Apple...
...my SLVR complies with (all) Bluetooth-communications-standards, since it can sync with Windows PCs and swap files with other Bluetooth devices (non-Motorola GSMs for insatance) flawlessly...
You are totally wrong... the fact it works with Windows does not mean that it's not Motorola's fault. In facts, if you think correctly:
- Mac OS X has no such problems with all other bluetooth devices/phones
Motorola only did check that his phone worked in Windows (if not, they wouldn't have released it). This means that Windows seems tolerant to whatever bug the Motorola phone has. This is quite typical... lots of other devices have hard bugs that were never discovered by their manufacturer because their only test bed is one peer: Windows, which has bugs too.
This does not mean that Apple can't do anything: Apple will have to understand what the bug is and why Windows does not trigger the bug then try to workaround it. Apple already does that kind of stuff in its system. This is a good short term policy (to make the user happy) but a pretty bad one long term as that means that Apple has to put lots of "hacks" throughout the system to "mimic" Windows bugs.
You should complain to Motorola not having a more robust testing process. -
Olympus E-510 Camera Raw support
I've been using and Olympus E-500 and CS2 suite and have had no problem bringing in raw files (ORF) into Photoshop. However, I just started using the new Olympus E-510 and the raw files from this camera cannot be imported into Photoshop.
Does anyone know of a plug-in that will allow me to bring in the E-510's raw files (or does anyone know when an Adobe update will happen to include the E-510)?
Thanks very much.The E-510 apparently is not yet supported, but probably within a couple of months.
(I had been reading about a magenta cast for near blown highlights for this camera at the DPReview Oly DSLR forum. I seem to remember some users checking these highlights with ACR, but I could be mistaken. Check it out.)
Unfortunately for you, it will only be supported by CS3's ACR version 4.x. You will need convert to DNG to be able to use ACR3.x with CS2. When the 510 is supported, you'll be able to download the DNG converter. -
Olympus Photoshop Plugin w/Mac OS 9.2
Hi, I recently picked up an old Mac from a friend with OS 9.2 and Adobe Photshop 6. I have an Olympus E-500 camera, and need to install the plugin so that photoshop can read the .ORF file from the camera (it's RAW format). I can't get the mac to an internet connection, but I do have a thumb drive to transfer data. Can anyone walk me through the process of installing this plugin? BTW, this is my first Mac, so I'm new to the navigation.
HI, shadowjak. The plug-in you need is here. (Note: this link is a direct download — the file will be downloaded as soon as you click on it in this message.) Put it in the Import/Export folder inside Photoshop's main Plug-ins folder. You will then use the Import command in Photoshop's File menu to import and open your .orf files, the same as if you were scanning an image into Photoshop. I don't know whether or not you'll be able to open your .orf files in Photoshop by double-clicking them, but I'd be surprised.
I've tested to see whether the plug-in enables the .orf Import command in Photoshop 5.0.2, and it does; removing the plug-in makes that command disappear. I don't have an .orf file to test with, but if this all works in PS 5.0.2, I'd expect it to work in PS 6. Here are Olympus's installation instructions:
http://www.olympusamerica.com/files/Rawplugin_install.pdf -
RAW - Manufacturers should know you want to use Aperture.
It seems to me that we should also be telling our cameras manufacturers to quickly release whatever proprietary RAW information Apple needs in order to support a particular camera.
Here's something I posted earlier this morning.
"In very simple terms...
In order to add support for various camera RAW files, Apple has to ask the camera manufactures to supply proprietary information about how to process and read the RAW files. Each and every single camera has a different "proprietary process" it must use to handle the RAW file that the camera produces.
So that means that Apple is at the mercy of the manufacturers in order to get that information. Now most manufactures would prefer that you purchase or use their own software to work on the RAW files that their camera produces... it's an extra revenue stream for them. Because of this, it's not hard to imagine that they are a bit reluctant to divulge what is proprietary information that they spent time and money on creating. It's well documented that Nikon in particular is very reluctant about releasing such information.
If Adobe has support for a particular camera that Apple does not, then that means that Adobe has already gone through the trouble of asking the manufacture for the information that is needed, reached an agreement and signed the appropriate licensing contracts, exchanged whatever compensation was agreed upon, and then went to work making the software for ACR so it can read that particular cameras RAW files. As you can imagine, it's a process that takes some time to hammer out... more than likely because it involves more lawyers than engineers!
So... be sure you let Apple know that you would like them to add support for a particular camera, but just as important, make sure that your cameras manufacturer knows that you would like them to allow Apple to support their cameras with Apple's software."
-Robert
PowerMac G5 Quad 2.5Ghz Mac OS X (10.4.4) 4.5GB RAM, Nvidia 7800 GT, 600GB RAIDApple aren't entirely at the mercy of manufacturers, for example the open source dcdraw - http://www.cybercom.net/~dcoffin/dcraw/ - has been used my many developers, including Adobe.
dcdraw supports a pretty extensive list of cameras and is basically the work of one developer. I hope Apple have looked at this software, I can't see why they couldn't make use of it in Aperture. I can understand new software supporting a short list of cameras, but I'd expect the number of cameras to ramp up quickly.
Current support list (taken from dcdraw site 12 Jan 2006):
Adobe Digital Negative (DNG)
AVT F-145C
AVT F-201C
AVT F-510C
AVT F-810C
Canon PowerShot 600
Canon PowerShot A5
Canon PowerShot A5 Zoom
Canon PowerShot A50
Canon PowerShot Pro70
Canon PowerShot Pro90 IS
Canon PowerShot G1
Canon PowerShot G2
Canon PowerShot G3
Canon PowerShot G5
Canon PowerShot G6
Canon PowerShot S30
Canon PowerShot S40
Canon PowerShot S45
Canon PowerShot S50
Canon PowerShot S60
Canon PowerShot S70
Canon PowerShot Pro1
Canon EOS D30
Canon EOS D60
Canon EOS 5D
Canon EOS 10D
Canon EOS 20D
Canon EOS 300D
Canon EOS 350D
Canon EOS Digital Rebel
Canon EOS Digital Rebel XT
Canon EOS Kiss Digital
Canon EOS D2000C
Canon EOS-1D
Canon EOS-1DS
Canon EOS-1D Mark II
Canon EOS-1D Mark II N
Canon EOS-1Ds Mark II
Casio QV-2000UX
Casio QV-3000EX
Casio QV-3500EX
Casio QV-4000
Casio QV-5700
Casio QV-R51
Casio QV-R61
Casio EX-S100
Casio EX-Z50
Casio EX-Z55
Casio Exlim Pro 505
Casio Exlim Pro 600
Casio Exlim Pro 700
Contax N Digital
Creative PC-CAM 600
Epson R-D1
Foculus 531C
Fuji FinePix E550
Fuji FinePix F700
Fuji FinePix F710
Fuji FinePix F800
Fuji FinePix F810
Fuji FinePix S2Pro
Fuji FinePix S3Pro
Fuji FinePix S20Pro
Fuji FinePix S5000
Fuji FinePix S5100/S5500
Fuji FinePix S5200
Fuji FinePix S7000
Fuji FinePix S9000/S9500
Imacon Ixpress 16-megapixel
Imacon Ixpress 22-megapixel
ISG 2020x1520
Kodak DC20 (see Oliver Hartman's page)
Kodak DC25 (see Jun-ichiro Itoh's page)
Kodak DC40
Kodak DC50
Kodak DC120 (also try kdc2tiff)
Kodak DCS315C
Kodak DCS330C
Kodak DCS420
Kodak DCS460
Kodak DCS460A
Kodak DCS520C
Kodak DCS560C
Kodak DCS620C
Kodak DCS620X
Kodak DCS660C
Kodak DCS660M
Kodak DCS720X
Kodak DCS760C
Kodak DCS760M
Kodak EOSDCS1
Kodak EOSDCS3B
Kodak NC2000F
Kodak ProBack
Kodak PB645C
Kodak PB645H
Kodak PB645M
Kodak DCS Pro 14n
Kodak DCS Pro 14nx
Kodak DCS Pro SLR/c
Kodak DCS Pro SLR/n
Kodak P850
Kodak P880
Kodak KAI-0340
Konica KD-400Z
Konica KD-510Z
Leaf Aptus 17
Leaf Valeo 11
Leaf Valeo 22
Leaf Volare
Leica Digilux 2
Logitech Fotoman Pixtura
Minolta RD175
Minolta DiMAGE 5
Minolta DiMAGE 7
Minolta DiMAGE 7i
Minolta DiMAGE 7Hi
Minolta DiMAGE A1
Minolta DiMAGE A2
Minolta DiMAGE A200
Minolta DiMAGE G400
Minolta DiMAGE G500
Minolta DiMAGE G600
Minolta DiMAGE Z2
Minolta Alpha/Dynax/Maxxum 5D
Minolta Alpha/Dynax/Maxxum 7D
Nikon D1
Nikon D1H
Nikon D1X
Nikon D100
Nikon D2H
Nikon D2Hs
Nikon D2X
Nikon D50
Nikon D70
Nikon D70s
Nikon E700 ("DIAG RAW" hack)
Nikon E800 ("DIAG RAW" hack)
Nikon E880 ("DIAG RAW" hack)
Nikon E900 ("DIAG RAW" hack)
Nikon E950 ("DIAG RAW" hack)
Nikon E990 ("DIAG RAW" hack)
Nikon E995 ("DIAG RAW" hack)
Nikon E2100 ("DIAG RAW" hack)
Nikon E2500 ("DIAG RAW" hack)
Nikon E3700 ("DIAG RAW" hack)
Nikon E4300 ("DIAG RAW" hack)
Nikon E4500 ("DIAG RAW" hack)
Nikon E5000
Nikon E5400
Nikon E5700
Nikon E8400
Nikon E8700
Nikon E8800
Olympus C3030Z
Olympus C5050Z
Olympus C5060WZ
Olympus C7070WZ
Olympus C70Z,C7000Z
Olympus C740UZ
Olympus C770UZ
Olympus C8080WZ
Olympus E-1
Olympus E-10
Olympus E-20
Olympus E-300
Olympus E-500
Olympus SP500UZ
Panasonic DMC-FZ30
Panasonic DMC-LC1
Panasonic DMC-LX1
Pentax *ist D
Pentax *ist DL
Pentax *ist DS
Pentax Optio S
Pentax Optio S4
Pentax Optio 33WR
Phase One LightPhase
Phase One H 10
Phase One H 20
Phase One H 25
Phase One P 20
Phase One P 25
Pixelink A782
Polaroid x530
Rollei d530flex
RoverShot 3320af
Sigma SD9
Sigma SD10
Sinar 12582980-byte
Sinar STI format
SMaL Ultra-Pocket 3
SMaL Ultra-Pocket 4
SMaL Ultra-Pocket 5
Sony DSC-F828
Sony DSC-R1
Sony DSC-V3
STV680 VGA
Apologies for the large list, but I think its size illustrates the point.
2.1GHz iMac G5, 867MHz 12" Powerbook G4 Mac OS X (10.4.4) -
DNG Converter Doesn't Recognize NEF for D7000
I have been lon time user of Adobe DNG Converter with Olympus E-500 but I recently got the new Nikon D7000. I have Elements 9 and I am using DNG Converter 6.3.0.79. I download the Elments Verison of the Camera Raw update that came out in December 2010. When I open up my DNG Converter it doesn't recognize any of the NEF files on my camera. I must missing somthing but not sure what it might be. Do I need to add a profile somewhere for it to see the NEF extention? I am bit at a loss.
Thanks for any helpWhat do you mean by reinstall? Do I reinstall PSE 9 and then apply the patch or do I just do the patch again? I have installed the patch a couple of times and nothing is different. There is something wrong with the installation because now my Olympus RAW files do not show up either and they did as of yesterday prior to the installation of the 6.3 update.
And yes I can load the NEF into Elements but I like the batch convert option for RAW files.
Thanks everyone for your help.
Kevin -
MacBook won't recognize my camera
I have a MacBook white unibody 2010 running the latest OSX and when I connect my Olympus E-500 to my Mac it will not recognize it. It shows up under USB in system preferences but it wont show in iphoto, image capture, or my desktop. It plugs into windows computers fine but my Mac doesn't seem to recognize it. Anyway to fix this? Thank you!
Hi iDerion,
Welcome to the Apple Support Communities!
I understand that it can be very frustrating when your computer is not recognizing your camera. In this situation I would recommend troubleshooting the connection with iPhoto. Please use the following article for troubleshooting instructions.
iPhoto: Troubleshooting Camera Connections
Have a great day,
Joe -
Our Olympus E-500 writes images in RAW files (.orf) at 314 dpi. The Olympus software opens the .orf files at 314 dpi but Photoshop Elements RAW converter opens the files at 240 dpi.
How do we open the RAW .orf files at it's native 314 dpi??
We have the current version of the RAW converter.
PSE 5.02
Win XP
thank youThere is no "native" resolution. The pixel count is what matters. The DPI setting just tells the software how to print it and is, otherwise, and arbitrary number.
I'm not sure that you can set this number in Camera Raw when hosted by Photoshop Elements. The interface is slightly different and I only see 8/16-bit depth as an option. 240 dpi might be the default (and only) option in Elements.
However,you can change it at any time in Photoshop by going to Image>resize>Image Size and unchecking the "resample image" box and typing in a new number.
John -
Strange RAW processing problem
I've just jumped into the Mac world recently with a Mac Pro (which I absolutely love). I've been watching Aperture since it was announced. A friend of mine has been using it for a while. He has Cannon cameras and so he is golden. However, I was playing with it the other day to get a feel before I decided to purchase. I loaded up a set of RAW files from my Olympus E-500 and was ready to play. Unfortunately several of my shots ended up looking like this on screen:
http://PhilU.smugmug.com/photos/103737186-M.jpg
Lightroom (Adobe's RAW processing has always been excellent) shows the same problem images just fine:
http://PhilU.smugmug.com/photos/103737163-M.jpg
This is on Aperture 1.5 on 10.4.8.
This seems to be an issue with long exposures that have the "Noise Reduction" (dark fram subtraction) turned on. I had a few long exposures with it turned off that looked fine and also some shorter exposures with it turned on that looked fine. That's just speculation though.
Has anyone else run into this? Is there anything I can do to make it work?Yea, same for me in all apps using the core RAW functionality (Preview, iPhoto, Aperture, etc.)
I had thought this thread was dead long ago. I did get it submitted as a bug on http://bugreport.apple.com back then - it is still in "Open" status. Hope they get a chance to take a look at it.
The upside is that the workaround I mentioned before is still in effect. I also noticed that the last RAW update included a DNG fix so that files converted with the newer versions of the DNG converter are read properly. Would still be nice to have native ORF working properly (it does work fine most of the time, just not with images of the particular combination listed above). -
Colour differences & LR not deleting from hard drive
Hi,
I am running a Dell Dimension 1100, a NEC MultiSync 70 monitor, Xp SP 2 home, Olympus Master 2 and a full version of Lightroom 1.0,Photoshop CS2, and use a Olympus E-500 DSLR.
I have a slight issue with how Lightroom shows the colours of my pictures when i am comparing Olympus Master 2 v. Lightroom 1.0. Most pictures its hard to tell the difference without going back and forth constantly, but when i look at my pictures of flowers or landscapes, my pictures look so much more vibrant in Olympus Master compared to Lightroom. Is this a settings issue? or perhaps something else?
Also.....
when deleting pictures from Lightroom, it asks me if i wish to delete from the hard drive or just remove from Lightroom, when i choose delete from hard drive, after it says its done, if i go look at the folder its still there :/.
any help would be apprieciated, I am a novice dslr user and still learning how to use the softwares out thereAre you shooting images in raw or jpeg mode?
I assume that Olympus Master 2 is the raw processing software bundled with your camera. If so, then you are asking why Olympus software renders pictures differently than Lr. This question has been asked (and answered) many times but it boils down to the fact that the Olympus default rendering could be far different than that chosen by Lr. Also, Olympus may embed proprietary information in the raw image useful to Master 2 but entirely unknown to Lr.
If you want Lr to operate more like Master 2, then create a Lr preset (with the appropriate adjustments -- likely a saturation boost), then apply this preset when importing.
Finally, the camera raw engine (ACR) used by Lr is noted for producing images more muted than that produced by software bundled with cameras. In my opinion this is a good thing since the default rendering that many cameras produce is not at all natural. But the powerful Lr develop module allows me to create any interpretation I choose. Including a head spinning contrast and saturation boost. -
I have a Cannon G2 and recently took some RAW photos for the first time. Unfortunately, my Iphoto 6 doesn't want to recognize and import them, in spite of the camera being on the list as recognizable. I get this error message:
The following files could not be imported (they may be an unrecognized file type or the files may not contain valid data).
Then it lists the file path of each image. If I do a spotlight search for these images, i can see the images themselves in the spotlight window, leading me to believe they aren't corrupt.
Any ideas? I'm going to attempt to bring them in to Photoshop and convert them to JPEG but I'm still curious in that my camera should be allowed to download RAW files to IPhoto6. Thanks in advance.Ah, but there is a second and much shorter list of cameras for which RAW format is actually supported. I've been dealing with this for an Olympus E-500 and was guided to the same list you saw, which says it's a supported camera. I'm guessing that the statement that RAW support may require additional software is the operative one here, although that was not clear to me.
Adobe Photoshop CS2 supports RAW, for a steep price. Adobe has a public beta of Lightroom, which is free until the release version of the program comes out. It supports your camera's RAW format, but is somewhat slow compared to iPhoto. Apple's Aperture looks to be a great program, but it offers RAW support for the same limited list of cameras as iPhoto. If you go to photography sites such as dpreview.com, you can find discussions of other RAW converters, some of which are free. However, I don't know which of them run on a Mac. (Fortunately, I already had Photoshop.)
Here's the link to the RAW-supported cameras in iPhoto:
http://docs.info.apple.com/article.html?artnum=303554
Fred
Here
G4 "Quicksilver" Mac OS X (10.4.6) 1.5 GB RAM
G4 "Quicksilver" Mac OS X (10.4.6) 1.5 GB RAM
G4 "Quicksilver" Mac OS X (10.4.6) 1.5 GB RAM -
V1.5.1, Contact Printing Color Management Broken (?)
I'm finding the color to be off significantly when trying to print contact sheets in v1.5.1 (yes, I'm using color management and color managed printing with custom made printer profiles).
The same images print fine if they are printed on their own through Aperture. It's only when printing contact sheets. All images are from Canon 1DsM2 raw files.
It all worked fine under v1.5.0.
Anyone else finding this?
Here's a sample:
This shows Aperture with the Print Window:
http://www.jonroemer.com/ftp/ContactSheet03.jpg
This shows what happens when hit "preview" and what it looks like when it prints (Epson R2400):
http://www.jonroemer.com/ftp/ContactSheet04.jpgI'm finding the color to be off significantly when
trying to print contact sheets in v1.5.1 (yes, I'm
using color management and color managed printing
with custom made printer profiles).
The same images print fine if they are printed on
their own through Aperture. It's only when printing
contact sheets. All images are from Canon 1DsM2 raw
files.
It all worked fine under v1.5.0.
Anyone else finding this?
Here's a sample:
This shows Aperture with the Print Window:
http://www.jonroemer.com/ftp/ContactSheet03.jpg
This shows what happens when hit "preview" and what
it looks like when it prints (Epson R2400):
http://www.jonroemer.com/ftp/ContactSheet04.jpg
Yep wouldn't you know it. I made contact sheets from 1.5 just after I installed it on my machine and they came out great! The client calls me two days ago and asks for another set of contact prints, I fire up Aperture 1.5.1 to re-print the contacts.... Hey! What's happened to my color!
It's true, if I print one image, the color is just fine, once I try and print more than one image on a contact sheet, KERPOW! The color is way off, not even remotely close.
You don't even need to print the images, you can do a "Save as PDF" or "Preview" and see the same effect on screen.
I confirmed that it happens to both RAW and JPEG files from my Olympus E-500.
PowerMac G5 Quad 2.5Ghz Mac OS X (10.4.8) 4.5GB RAM, Nvidia 7800 GT, 600GB RAID, Aperture 1.5.1
Maybe you are looking for
-
An exercise of a text book of java. Count the number of letter 'a' appearing in a word. I can't do that. Here is my program, please help. import kenya.io.InputReader; import java.util.StringTokenizer; public class e47{ public static void main ( Strin
-
PO workflow process raises event but subscription does not fire
Hi: We are sending POs electronically in XML (11.5.10.2). The PO reaches the supplier correctly. The workflow process to send the PO to the supplier completes successfully. The workflow diagrammer shows that the process fully completes. The last task
-
How do you turn a string into an integer?
how do you turn a string into an integer? for ex, if i wanted to turn the string "5" into the integer 5, how would i do that?
-
Display moves with my mouse.
I've never seen this happen before and I can't seem to find this anywhere in the support pages.. when I log in my display is normal at first but then after everything on the desktop loads up, my display suddenly gets bigger and it moves in the opposi
-
REquire our help gurus on scenario: There are three Org Units- A the Main Department and B, C Child Department. We have maintained Chief position A012 to all Units 'A', 'B' and 'C'. Org Units B and C as said earlier reports to (002) to A. Is it pos