Disk utility is for different version than OS X

Hi. I updated my OS from Leopard to Snow Leopard. The OS version is now 10.6.8. But when launcing my disk utility I get an error message saying that "the version of Disk Utility cannot be used with current Mac OS X version. You have a Disk Utility version 10.5.8."
Does anyone know why the Disk Utility did not get updated with OS update and how to update it manually?

If you moved Disk Utility from the Applications -> Utilities folder, it might not get updated. The same is true with any prebundled applications, or installed applications. Many are coded only to work from their preinstalled locations. If clutter is an issue, use Aliases, the Finder sidebar, and Dock to make shortcuts to these programs. http://www.charlessoft.com/ Pacifist lets you extract software from installers, and then running the appropriate combo update from* http://www.macmaps.com/jaguarleopard.html over the existing system (10.6.8 combo over a 10.6.8 system will ensure any Apple software is up to date if it is in its prescribed folder.

Similar Messages

Teststand deployment utility used for different versions of TestStand

I am in a situation where I developed a test sequence in TestStand 3.5 and used the deployment utility to deliver an installer to a customer with TestStand 2010 Base deployment Engine. We are seeing the following error "This installer installs file to the TestStand directory. You must first install TestStand or the TestStand runtime engine version 3.5 to create the TestStand directory."
My question becomes, is it even possible to make an installer with TestStand 3.5 and have someone else use with TestStand 2010 Base deployment engine? What then needs to happen to get past the error if it is possible?
Thanks,
Bill
John 3:16

No you cannot use 3.5 sequences on the 2010 engine.
You need to install the 3.5 engine on that machine. The license will still work and you will need to use the version selector to go between the two. You can include the engine in your installer build.
TestStand is a scripting language. Because sequence files are not compiled it is possible to use unsupported functions on the wrong version. Therefore, the engine just won't run other versions. Also, you need to switch versions because they use different adapters, engines, dlls, folders, etc... The version selector changes settings on your machine for all those things for that version.
Hope this helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Can't use this version of Disk Utility.app with this version of os x question

can't use this version of Disk Utility.app with this version of OS X 10.9.2

Hi barcolana,
If you are having issues using Disk Utility on your Mac running OS X Mavericks 10.9.2, you may want to make sure that you are booting to Recovery before using Disk Utility; you may find the following article helpful:
Apple Support: Resolve startup issues and perform disk maintenance with Disk Utility and fsck
http://support.apple.com/kb/ts1417
Regards,
- Brenden

Can i set up my drive as encrypted with different partitions for different versions of osx?

i have some questions about setting up an encrypted drive with different versions of osx installed on separate partitions, and how this choice effects time-machine and the emergency recovery disk.
I have a new/refurbished macbook pro with a SSD. it already has mavericks installed. i want to fully wipe the drive and reinstall everything my self because I'm odd like that.
first wiping the current drive
Does the recovery partition get wiped if i use disk-utility to reformat the drive. Even thought the recovery partition does not show up as a partition, when i look at it with disk-utility? i would like to know I've wiped all partitions so that no little bugger gets left with out me knowing. Disk-utility does not show the recovery partition and this makes me concerned it might not wipe it.
Does mavericks automatically make a recovery partition during the installation process? Or do i need to make a new 1gb partition for the recovery disk?
Can i have two different partitions on my drive with separate installations of OSX on it? (one for work that i don't update the system os till my current project is done, and the other for experimenting with new software.)
will time machine back up both of the partitions or just one?
can i accomplish all this from a bootable usb drive or do i need to do this in target disk mode?
do i need to use a more capable utility than the stock apple "disk-utility"?
when reformatting the drive should i format it as encrypted or let file vault do this after i install mavericks?
how much does encryption slow down performance for things like photo/video/music production?

Do a backup before you do anything.
Does the recovery partition get wiped if i use disk-utility to reformat the drive
It shouldn't
Does mavericks automatically make a recovery partition during the installation process?
Yes.
Can i have two different partitions on my drive with separate installations of OSX on it?
Yes.
will time machine back up both of the partitions or just one?
It will as long as one partition is not excluded in the Time Machine/Options.
do i need to use a more capable utility than the stock apple "disk-utility"?
No, just boot into the Recovery Volume (command - R on a restart).
file vault do this after i install mavericks?
I would let File Vault do that.

Disk Utility - Which is latest version?

I have found different versions of Disk Utility on my iMac, the latest of which I find is Version 11.1 (252.3).
Can anyone advise me please if this is the latest version? If it is not I will need to update DU and scrap all previous versions.
I'm running MacOS 10.5.3.

Version 11.1 (252.3) is the latest.
-mj

Could there be independent VI paths for different versions of LabVIEW?

Hello,
When jumping between different versions of LabVIEW (6.1, 7.1, 8.5) it is annoying that the current path for one becomes the current path for the other.
If I am working with LV 7.1 in a folder dedicated to 7.1 VI's, and then open LV 8.5, I don't want 8.5 to go to that 7.1 folder by default. Alternately. if I was working in LV 8.5, closed it out, and then I click on a 7.1 VI, I don't want it to open in LV 8.5.
I've tried changing the path options in each version of LabVIEW, but that doesn't seem to help. Is there any way of isolating these folder paths from one another? One of our newer LV guys accidently opened some 7.1 code in 8.5.1 and then saved it. Luckily, I had archived code to return to, but it could have been a disaster.
Thanks for any ideas,
McSynth

You're actually asking two different questions.
The first question has to do with which version of LabVIEW gets launched when you double-click a file. This is an operating system thing. The one that gets launched is the last one that got used. (Your first question will be: can this be changed? Answer: Change the operating system. Or, play around with the registry each time you quit out LabVIEW.)
The second question has to do with search paths. These are independent. However, a VI will contain information about its subVIs in terms of where to find them. This is not a function of LabVIEW, as it is a function of the VI. Thus, it will make no difference which version of LabVIEW you use to open the VI. You can, if you wish, modify the search paths that LabVIEW uses to find VIs for each version of LabVIEW from the Tools->Options menu. However, this will not eliminate the problem, and your best bet is to keep those backups frequent.

How can I distribute an application using Reprot generation Toolkit for MS Office for different versions of MS Office?

I want to create an application which uses the Report Generation Toolkit for Microsoft Office. The office version of the target machine depends on what my customer has installed.
From several discussions I have seen that the installer detects which version I have on my development machine. I'm not able to hold three or four machines with different versions (97,2000,2002,XP).
I decided to do the following software architecture:
I create a LLB MakeReport.llb with a VI called MakeReport.vi. With VI server I will start MakeReport.vi in MakeReport.llb. Over a named queue I will send a command from my application to MakeReport.vi. Then the report will be
printed.
I will create this LLB by saving MakeReport.vi with File>>Save with options...>>Application distribution. All neccessary VIs will be in the LLB.
I will hold different directories for each version. I can create different version of the LLB. During installation of my application the LLB for the right version will be copied from the CD to the application folder.
I know I will be restricted in testing my report in only one version and hoping it will be good in the other versions.
I think that the difference lays only in the word and excel related llbs.
1. Will my software architecture work or is it obviously wrong?
2. How will I get all versions from the toolkit CD?
3. Which is the registry key I must read to get the right version (a minor question, if somebody knows I do not need to search for myself).
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Lookout saves the files in .csv form which can be opened in Excel. I did make some progress by using the "append table to report" vi which allowed me to put values into an array and then those values were entered into my template on my report vi.
Where I am stuck now is I want to be able to put values into my template from a .csv file, not from an array I have to manually put numbers in.
Once those values are in my template I want to pull summed values from the template and place them into a final excel file for printing.
I have attached examples of the files I am working with to help you better understand what I am trying to do.
I hope that makes sense.
Jason Phillips
Attachments:
HourlyTotalsTemplate.xls ‏120 KB
eb_rain_gauge_ss.csv ‏23 KB
EastBankHourlyRainReport.xls ‏28 KB

Robohelp - TFS Mapping issue for different versions

Hi,
I'm using Adobe Robohelp 9 with Team Foundation Server 2012 on Windows 7 - 64 bit. I've also installed Microsoft Visual Studio Team Foundation Server 2012 MSSCCI Provider. I've mapped all the project folders on my machine. We create HTML help (.chm) for our application.
I have different versions for each module of our entire product on Team Foundation Server 2012 (As we have multiple modules in our product), for example x+1, x+2, x+3 and so on.
Each module has different Robohelp projects for every version/branch. This means, if the Online help for any module from any version is changed, we update it in the respective version of the Online help project.
When we move on to the next version, due to binary files, the next version contains the same path and properties of previous version. We need to have different project for single module for the next version. For this, I have changed the TFS project path of every .xpj project for every version. For example, if I'm working on version x+2, then I've changed the TFS project path from x+1 to x+2 manually on x+2 version/branch and then started working on it.
As these Robohelp projects (for each module) are mapped to my local folder on C drive, it shows a single workspace mapped with same path on my machine. This should be the ideal condition for my all projects as follows:
But sometimes when I try to update any file from version x+2 and then check-in my changes, the changes are getting checked-in to the previous version, i.e. x+1. And if I see the workspace of the x+1 version, it shows one more wrong workspace added below the correct one. This new workspace contains the Source control folder path of x+1 version and the Local folder path of x+2 version. That means, my robohelp project folder of x+2 version from my local drive is getting mapped to TFS folder of version x+1. That is why all the changes done in Robohelp project files from x+2 version are going in to x+1 version.
The strange here is when I try to check-in my changes in x+2, it shows the correct path of x+2 version. But they all go to x+1 version, which should not happen.
If anyone can help me in this problem, it would be a great help!
Thanks in advance and waiting for solution,
Dipali

So, if I understand correctly, you create a duplicate of the project and
check that in on a different location in TFS. That is the way to go.
My guess is that the XPJ still references the old version's path. Try
checking out the XPJ with TFS and open in with notepad. Search for
'vc::cookie'. Check that the path there points to the correct path of
the project in TFS. It probably still references the old path and so
RoboHelp will check it in at the old path.
Kind regards,
Willam

Disk Utility - Solution for a Weird MediaKit Partition "too small" Error

I found a very suggestive article, could be a silver bullet for this kind of problem.
*http://ubuntuforums.org/showthread.php?t=760190*
+*quote from SWedd*+
+In my case, it was caused by the Apple_Bootstrap partition (created during Ubuntu install), of format unknown to OSX. This partition was positioned right after my Macintosh_HD partition. To enlarge my Macintosh_HD I needed to use diskutil to erase the Apple_Bootstrap partition to a blank "MS-DOS" partition. Then I could use Disk Utility to Delete the MS-DOS partition. After that I could resize my Macintosh_HD freely.+
In my understanding, if you failed to increase the size of a certain partition, it might mean a partition just after that partition is corrupted or broken (whether or not it is corrupted, you can know it by using command "diskutil info ...").
With command "diskutil eraseVolume ..." you can erase the partition in question, then with "diskutil mergePartitions ..." merge the partition you want to increase in size and the partition you just erased. Now you can increase the size without any error.
Anyway, diskutil can do several things which Disk Utility can't do.
To resort to diskutil is sure worthwhile.
Message was edited by: Shigerello

Welcome to the Apple forums and thanks for the information.
Warning:
The terminal command
diskutil
should be used with care, as with most terminal commands.
A good rule to remember is "If you do not know what something will do, do not do it."
For information on diskutil, in a terminal enter
man diskutil

Standby database on different version than prod.

Is it possible to have a standby database running on a different version of Oracle than the production database?
In this case I have production DB on the following version:
7.3.4
8.1.7.4.0
9.2.0.4.0
9.2.0.6.0
Would it be possible to run the a stand by DB in 10g?

From the docs posted previously, which you clearly didn't read
Oracle Data Guard is available only as a feature of Oracle Database Enterprise Edition. It is not available with Oracle Database Standard Edition. This means the same release of Oracle Database Enterprise Edition must be installed on the primary database and all standby databases in a Data Guard configuration.
Rhetorical question: Now what would same release mean?
Sybrand Bakker
Senior Oracle DBA

Can client dynamically link to shared libraries for different versions ?

Can Oracle client dynamically link to Oracle shared libraries if the versions are different ?
Hi:
I apologize for this newbie question:
We are using PRO C to generate the client C code.
We can compile both dynamic and static versions of our Oracle client.
Our question is:
is it possible to compile a dynamically linked Oracle client in say version 10.1.0.2 and actually run the application against say version 8.1.7.0 environment ?
That is, can an Oracle client dynamically link to the Oracle shared libraries if the versions are different ?
If it is possible, then how to modify the makefile
to enable Oracle client to reference different versions
of shared libraries ?
Thanks
JL

What you describe is not supported.

Disk Utility "waiting for the drive"

I'll be calling Applecare on this, but would like to know if anyone else has experienced this problem:
I have a 2 month old MBP with the following model Super Drive:
HL-DT-ST DVDRW GSA-S10N (according to System Profiler, it can write to all formats including -R, +R, DL). From another thread, I assume this is an LG?
I decided to test the drive - made a short 40 second movie and created a disk image. Upon opening Disk Utility and inserting a DVD (Verbatim +R), I got the following: "waiting for the drive" for 5 minutes. Ejected the disk and tried again - same result.
On the third try, it actually recognized the DVD, but only gave me the option to burn at 4x or 8x. I usually burn at the slowest speed available (2x), so I cancelled, ejected the disk and tried again. Fourth and fifth tries: no action, just "waiting for the drive".
I then tried to use Toast with the Super Drive; before inserting the disk, I set Toast to burn at 2x, but once I inserted the disk, Toast recognized it, but changed the available burn options to 4x or 8x.
Next I connected my external burner and got the options to burn at 2.4x, 4x, or 8x both in Disk Utility and Toast.
I then used the same disk on my iMac; tried both the Super Drive and my external burner (using both Disk Utility and Toast with both) and got the following burn options:
iMac Super Drive/Disk Utility: 2.4x, 4x, 8x
iMac/external burner/Toast: 2x, 4x, 6x, 8x
There seem to be a couple of issues:
The "waiting for the drive" problem (what could possibly cause this?)
The "non-availability" of a slow burn speed of the Super Drive
And a third problem: this DVD drive is the slowest I've ever experienced; it took 50 seconds for the icon to appear on the desktop after inserting the DVD vs. 7 seconds on the iMac (this is the DVD I burned using Toast/exterbal burner,testing it on a TV and the iMac). It played fine on all three.
Has anyone encountered a similar "waiting for the drive" issue and/or the fact that this drive takes a very long time to recognize/read a DVD?
Appreciate any input!

I spoke with a product specialist at Apple and it was agreed that we'd wait to see if the problem persisted; at that time, we'd talk about getting the drive replaced.

Disk utility asks for password for authopen when creating images

I just upgraded to Mountain Lion from Lion 10.7.4.
Now, whenever I use disk utility to create a image from a CD/DVD, I get a dialog window saying that :
authopen is trying to open the chosen file.
Type your password to allow this.
I never saw this dialog in Lion. Why am I getting this message?
Also, after upgrading to ML I cannot eject the CD/DVD after my cdr or dmg file is created. I have to wait a few minutes. In Lion I only had to wait a few seconds.
I tried the usual permissions repair, reboot, etc.
*By the way I have been using Macs since the good old days of G3, before the iPod was invented, so I am not totally clueless here. My forum ID got messged up so I had to create a new Apple ID.

To get around this issue, the group name needs to be changed to 'everyone' in the sys.openfile section of /etc/authorization. You will still need to authenticate, but you do not need to have admin credentials:
<key>sys.openfile.</key>
        <dict>
            <key>class</key>
            <string>user</string>
            <key>comment</key>
            <string>See authopen(1) for information on the use of this right.</string>
            <key>default-button</key>
            <dict>
                <key>ar</key>
                <string>فتح</string>
                <key>ca</key>
                <string>Obrir</string>
                <key>cs</key>
                <string>Otevřít</string>
                <key>da</key>
                <string>Åben</string>
                <key>de</key>
                <string>Öffnen</string>
                <key>el</key>
                <string>Άνοιγμα</string>
                <key>en</key>
                <string>Open</string>
                <key>es</key>
                <string>Abrir</string>
                <key>fi</key>
                <string>Avaa</string>
                <key>fr</key>
                <string>Ouvrir</string>
                <key>he</key>
                <string>פתח</string>
                <key>hr</key>
                <string>Otvori</string>
                <key>hu</key>
                <string>Megnyitás</string>
                <key>it</key>
                <string>Apri</string>
                <key>ja</key>
                <string>開く</string>
                <key>ko</key>
                <string>열기</string>
                <key>nb</key>
                <string>Åpne</string>
                <key>nl</key>
                <string>Open</string>
                <key>pl</key>
                <string>Otwórz</string>
                <key>pt</key>
                <string>Abrir</string>
                <key>pt-PT</key>
                <string>Abrir</string>
                <key>ro</key>
                <string>Deschide</string>
                <key>ru</key>
                <string>Открыть</string>
                <key>sk</key>
                <string>Otvoriť</string>
                <key>sv</key>
                <string>Öppna</string>
                <key>th</key>
                <string>เปิด</string>
                <key>tr</key>
                <string>Aç</string>
                <key>uk</key>
                <string>Відкрити</string>
                <key>zh-Hans</key>
                <string>打开</string>
                <key>zh-Hant</key>
                <string>打開</string>
            </dict>
            <key>default-prompt</key>
            <dict>
                <key>ar</key>
                <string>يحاول __APPNAME__ فتح الملف الذي تم اختياره.</string>
                <key>ca</key>
                <string>__APPNAME__ està intentant obrir l’arxiu seleccionat.</string>
                <key>cs</key>
                <string>__APPNAME__ se pokouší otevřít vybraný soubor.</string>
                <key>da</key>
                <string>__APPNAME__ forsøger at åbne det valgte arkiv.</string>
                <key>de</key>
                <string>__APPNAME__ versucht, die gewählte Datei zu öffnen.</string>
                <key>el</key>
                <string>Η εφαρμογή __APPNAME__ προσπαθεί να ανοίξει το επιλεγμένο αρχείο.</string>
                <key>en</key>
                <string>__APPNAME__ is trying to open the chosen file.</string>
                <key>es</key>
                <string>__APPNAME__ está intentando abrir el archivo seleccionado.</string>
                <key>fi</key>
                <string>__APPNAME__ yrittää avata valittua tiedostoa.</string>
                <key>fr</key>
                <string>__APPNAME__ essaye d'ouvrir le fichier sélectionné.</string>
                <key>he</key>
                <string>״ __APPNAME__״ מבקש לפתוח את הקובץ הנבחר.</string>
                <key>hr</key>
                <string>__APPNAME__ pokušava otvoriti odabranu datoteku.</string>
                <key>hu</key>
                <string>A(z) __APPNAME__ megpróbálja megnyitni a kiválasztott fájlt.</string>
                <key>it</key>
                <string>__APPNAME__ sta cercando di aprire il documento prescelto.</string>
                <key>ja</key>
                <string>__APPNAME__ は、選択中のファイルを開こうとしています。</string>
                <key>ko</key>
                <string>__APPNAME__이(가) 선택된 파일을 열려고 합니다.</string>
                <key>nb</key>
                <string>__APPNAME__ prøver å åpne den valgte filen.</string>
                <key>nl</key>
                <string>__APPNAME__ probeert het gekozen bestand te openen.</string>
                <key>pl</key>
                <string>__APPNAME__ próbuje otworzyć wybrany plik.</string>
                <key>pt</key>
                <string>__APPNAME__ está tentando abrir o arquivo escolhido.</string>
                <key>pt-PT</key>
                <string>O __APPNAME__ está a tentar abrir o ficheiro escolhido.</string>
                <key>ro</key>
                <string>__APPNAME__ încearcă să deschidă fișierul ales.</string>
                <key>ru</key>
                <string>Программа «__APPNAME__» пытается открыть новый файл.</string>
                <key>sk</key>
                <string>__APPNAME__ sa pokúša otvoriť vybraný súbor.</string>
                <key>sv</key>
                <string>__APPNAME__ försöker öppna den valda filen.</string>
                <key>th</key>
                <string>__APPNAME__ กำลังพยายามเปิดไฟล์ที่เลือก</string>
                <key>tr</key>
                <string>__APPNAME__, seçilen dosyayı açmaya çalışıyor.</string>
                <key>uk</key>
                <string>Програма «__APPNAME__» намагається відкрити вибраний файл.</string>
                <key>zh-Hans</key>
                <string>“__APPNAME__”正试图打开所选文件。</string>
                <key>zh-Hant</key>
                <string>“__APPNAME__”正在嘗試打開所選檔案。</string>
            </dict>
            <key>group</key>
            <string>everyone</string>
            <key>shared</key>
            <false/>
            <key>timeout</key>
            <integer>300</integer>

Disk Utility works for FAT but fails for Mac OS Extended

Hi Folks,
I have a 2TB WD My Book drive that I am trying to format as Mac OS Extended for Time Machine. Disk Utility will cheerfully format it as FAT (the FAT drive shows up in finder and seems to work fine), but won't format it as Mac OS Extended. I'm trying to figure out whether this is a hardware error, or whether I am doing something wrong.
To format it for Mac OS Extended, I am going into the partition tab, removing the current (FAT) partition, and adding a new Mac OS Extended partition. When I do this, Disk Utility shows the new partition as "grayed out" and it does not mount in Finder.
If I run Verify and Repair, I get the following errors:
Verify and Repair volume “Untitled 1”
Checking Journaled HFS Plus volume.
Invalid node structure
Invalid B-tree node size
Invalid record count
Invalid B-tree node size
The volume could not be verified completely.
Volume repair complete.Updating boot support partitions for the volume as required.Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
Am I doing something wrong here, or does this sound more like a hardware failure?
Thanks!

@kbd1: Yes, if I erase the disk from the erase tab and format it as MS-DOS (FAT) the disk works just fine. If I erase and format it as Mac OS Extended, I get the same errors listed above and it doesn't mount.
@Thomas: Yes, if I set the format to GUID I get the same errors. I've even tried setting up two partitions: one FAT and one GUID and the FAT one mounts and the GUID one doesn’t.
So, from both of your responses it sounds like hardware, which makes sense. What is strange to me is that it works as a FAT drive...
Message was edited by: terpfan

Disk Utility asks for installation disc - what are my options?

I have a 17" inch macbook pro intel core 2 duo running OS X 10.6.8. I believe it's from 2007. I am out of the country in PERU right now, editing a film on my Macbook. I accidentally dropped the Mac, which smashed in a corner edge of it but things still seem to work. However, when I run Disk Utility, it says "The disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair the disk". It also says the problem is an "invalid volume free block count (It should be 2306734 instead of 2306728)".
I don't have the original installation discs and am wondering what my options are for repairing the Mac. It makes me nervous knowing there's a kink in the computer. I'd rather nip it in the bud. If I knew where to acquire the startup disc, it's possible I could have a friend bring me when he visits. But I'd rather not buy them new/it new (if even they still sell them). And I don't see any listings on ebay. Does the Mac OS X installation disc have to be from this exact model, including a 17 inch Macbook Pro? Are any other discs compatible? Do I have any other options for repairing the Mac?
Thanks...

Thanks much Oglethorpe. This is what I shall do if I get no other reponses offering other/easier solutions. I just spent 30 mins on the apple site, seems impossible to find the exact product/model online and no email customer support appears available. And I can't make calls to the states to the apple store. But 'praps I can have said friend call them and order...

Disk utility is for different version than OS X

Similar Messages

Maybe you are looking for