Screen capture error

Hi there, after upgrading a MacPro to 10.6.8 I get an error when I make a screen capture using the standard cmd/shift/4 in the Finder. A dialog panel is stating that the screen capture can't be saved. Now I have to launch ScreenCapture and work from thare. However it is working on my MacBookPro running 10.6.8. What am I missing?

Anyone?

Similar Messages

[iPhone SDK beta 7] screen capture error?

As of beta 7 of the SDK, I get the following error when I try to capture a screenshot of my device via Xcode: "Could not communicate with the device, connection failed".
Anyone else encounter this? Or is it working for you?
Thanks.
Message was edited by: Abra Dabra

Me, too. Xcode 3.1. I am using the old-fashioned screen capture technique (holding power while pressing home), but it's not nearly as nice and the fact I can't do the other worries me a bit.
Has anyone been able to do this since iPhone 2.1 came out?

Screen capture error, using "ctrl command shift 4"

when I captured the screen using "ctrl command shift 4", the captured picture is cracked. but when using "command shift 4", the captured picture is fine.
like below
How can I fix it?

use CMD Shift 4
better still use a FREE screen capture APP like ducklink
http://www.ducklink.com/p/free-screen-capture-tool-on-mac/
Best one is the APP SnapNDrag I use all the time.
http://download.cnet.com/SnapNDrag/3000-2094_4-40913.html

Quicktime Screen capture error on start

I am opening quicktime and wanting to do a "New Screen Recording" and it goes straight to an error then closes the window not being able to adjust the settings within the screen recording. Is there a preference file I can trash to reset the settings?

dj2x
same as before? If so, let's make this THE thread then.
Let's try to get specific, shall we?
----------- I just HAVE to put this here, due diligence and such ---------
Quoted from  Apple's "How to write a good question"
To help other members answer your question, give as many details as you can.
Include your product name and specs such as processor speed, memory, and storage capacity. Please do not include your Serial Number, IMEI, MEID, or other personal information.
Provide the version numbers of your operating system and relevant applications, for example "iOS 6.0.3" or "iPhoto 9.1.2". <-QUICKTIME version?
Describe the problem, and include any details about what seems to cause it.
List any troubleshooting steps you've already tried, or temporary fixes you've discovered.
Now,
What OS version?
What version QT?
Is this error new? First time tried?
If not new, what can you think of that might have occurred since your last joy with screen recording?
3. When you click [OK], what happens?
Enough for now
CCC

Error Message When Importing Quicktime Screen Capture to FCE

As I said in the subject I'm having issues importing a Quicktime Screen Capture into Final Cut Express. I keep getting this message.
File Error: 1 file(s) recognized, 0 access denied, 1 unknown
I figure it has to be a quick fix for this simple problem. And it's probably just my first time.
Thanking you in advance
Neo
Message was edited by: Neo Dot Com

QuickTime Screen Recordings are H.264 video files. You need to convert this to +QuickTime Apple Intermediate Codec+ in order to use it in FCE. MPEG Streamclip (free) can do this for you.

Getting time expired error in labview while getting screen capture

Hello,
I have to capture a screen shot for Agilent's Spectrum analyzer, ESA series. But Whenever i run the program i always get time expired before operation is completed. I am attaching the program and also screen-shot of program. If anyone can solve this problem i would be very glad.
Thanking you all...
Pals
Solved!
Go to Solution.
Attachments:
PSA Screen Capture via GPIB.jpg ‏39 KB
VISA Read Binary Block Data to File.jpg ‏48 KB
PSA Screen Capture via GPIB.llb ‏91 KB

Hi,
I tried to increase the time out but it didnt work. i am trying to read 1 byte at a time... So is it ok?
Thanks so much....
Attachments:
PSA Screen Capture via GPIB.jpg ‏39 KB
VISA Read Binary Block Data to File.jpg ‏48 KB

Screen shot error?

I just recently bought a MacBook white and the first couple of days, the screen shot process was working. Yesterday I tried to take a screen shot and this bubble pops up. The bubble says, *Screen capture failed* the attempt to take a screen capture has failed. The error is 'Unable to create type string.'
Does anyone know how I can fix this error? Your help would be greatly appreciated.

HI and Welcome to Apple Discussions ...
Try deleting this file. com.apple.grab.plist /Users/YourName/Library/Preferences. Drag that file from the Preferences folder to the Trash, empty the Trash and restart your MacBook. Now try a screen capture.
Carolyn

Screen Muncher Error Message

Hello!
This is my first post, hope you could help me.
So, when I downloaded Screen Muncher, an error message showed up (Error starting ScreenMuncher: Class 'net.rim.device.api.ui.Virtual Keyboard' not found.)
I have BlackBerry Bold 9000.
I looked for other screen capturing applications but none of them worked. Hope you could help!
Thanks a bunch!
Dee

Welcome to the Community !
I think it is best to contact the developer for issues with the Screen Muncher app itself. There is an email address of the developer on the Screen Muncher page in BlackBerry World.
A like is always appreciated,
but a nomination for BB Elite even more :-)
You can also contact me on Twitter: @ndsmyter

Automator Stop Capture error

I was trying to make a screen capture service, but have been hitting errors in the Start Capture and Save Capture actions. I tried to make a service as simple as New Screen Capture > Wait for User Action > Stop Capture, but it gives me an error on the Stop Capture action (even though it does stop the recording). The error just says "can't make missing value into type alias."

Clicky23 wrote:
Cool, at least that lets the workflow keep going. It's still not returning the video
Here's a script that returns the new Quicktime video to the next action, even if the user has already opened other video.
on run {input, parameters}
    tell application "QuickTime Player" to if exists document 1 then
        try
            set screenRecordingDoc to first document whose its current screen compression's name is not ""
            set allDocs to name of documents
            try
                stop screenRecordingDoc -- to stop capture
            end try
            repeat 5 times
                my waitSec(1)
                if not (exists screenRecordingDoc) then exit repeat
            end repeat
            repeat with tDoc in (get documents)
                if name of tDoc is not in allDocs and file of tDoc is missing value then -- a new doc name ("Untitled x") in the list of names, and this document is not a file
                    return contents of tDoc -- return the new Quicktime video
                end if
            end repeat
        end try
    end if
    return {} -- no screen capture or no document
end run
on waitSec(n)
    do shell script "sleep " & n
end waitSec

Screen capture function (Shift-Command-3 or 4) doesn't work

When I try to do a screen capture using the built-in utility, I hear the camera-click, but then get an error message saying the capture couldn't be completed because of this error: "unable to create type string". How do I fix this?
Note: I normally use Grab, but find having to convert tiffs to jpg/png annoying; I was hoping to use the built-in screen grab instead.
This problem has been happening for months, through many boots/reboots. I've repaired permissions to no avail. Any ideas?
Thx!

Lyssa is correct try restarting the Mac first, I always assume that users do this to try to fix anomalies.
Creating a new user is fairly easy and non disruptive to the Mac or the way you log in. You can simply delete the user when finished troubleshooting or keep it for later troubleshooting.
To create a new account (just to let you know how to do it).
1. Open Sys/Prefs/Account (yes accounts sorry I was thinking Tiger OS).
2. Click on the Lock at the bottom left of the window.
3. Put in your password (which should be the admin account).
4. Now the + add user button should no longer be greyed out, select the + button.
5. Give the user a name, shortname, and password. Then press Create Account.
6. Select the Keep Automatic Login when prompted.
7. Exit out of Sys/Prefs
Now to log in to the user, go to the blue Apple menu at top left corner of Desktop, Select Log off "User". You'll be prompted with a log in selection screen. Select the newly created user, enter the password then test the Screen shots.
To delete the user.
1. Open Sys/Prefs/Accounts
2. Unlock as you did previously.
3. Select the newly created user then press the - Delete User button.
4. When prompted, select the "Delete the home folder" option then press OK. And your done.
Message was edited by: iyacyas

How to capture errors records in flat file in BDC

hi ,
    i would like to know how to capture error records while uploading a flat file to screen through BDC .
appreciatable solutions are rewarded.
thanks,
shan

Hi shan,
write this code, it will solve your problem.
DATA : BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
DATA : I_MSG LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : BEGIN OF I_ERR OCCURS 0,
          MATNR(18),
          FLAG(1),
          MSG(100),
       END OF I_ERR.
DATA :V_LINES TYPE I.
LOOP AT ITAB.
REFRESH BDCTAB.
PERFORM SCREEN USING: 'SAPLMGMM' '0060'.
PERFORM FIELD USING: 'RMMG1-MATNR' ITAB-MATNR,
                      'RMMG1-MBRSH' ITAB-MBRSH ,
                      'RMMG1-MTART' ITAB-MTART,
                      'BDC_OKCODE' '/00'.
PERFORM SCREEN USING: 'SAPLMGMM' '0070'.
PERFORM FIELD USING: 'MSICHTAUSW-KZSEL(01)' 'X' ,
                     'MSICHTAUSW-KZSEL(02)' 'X' ,
                     'MSICHTAUSW-KZSEL(09)' 'X' ,
                     'BDC_OKCODE' '=ENTR'.
PERFORM SCREEN USING: 'SAPLMGMM' '0080'.
PERFORM FIELD USING: 'RMMG1-WERKS' ITAB-WERKS,
                     'BDC_OKCODE' '=ENTR'.
PERFORM SCREEN USING: 'SAPLMGMM' '4004'.
PERFORM FIELD USING: 'MAKT-MAKTX' ITAB-MAKTX,
                      'MARA-MEINS' 'EA' ,
                      'MARA-MATKL' '001',
                      'BDC_OKCODE' '/00'.
PERFORM SCREEN USING: 'SAPLMGMM' '4004'.
PERFORM FIELD USING: 'BDC_OKCODE' '/00'.
PERFORM SCREEN USING: 'SAPLMGMM' '4000'.
PERFORM FIELD USING: 'MAKT-MAKTX' ITAB-MAKTX,
                      'MARA-MEINS' 'EA',
                      'MARC-EKGRP' '001',
                      'MARA-MATKL' '001',
                      'BDC_OKCODE' '=BU'.
CALL TRANSACTION 'MM01' USING BDCTAB
                        MODE 'A'
                        MESSAGES INTO I_MSG.
FINDING LAST MESSAGE IN THE I_MSG TABLE*****
DESCRIBE TABLE I_MSG LINES V_LINES.
ACCORDING TO THE V_LINES NUMBER TABLE WILL BE READ****
READ TABLE I_MSG INDEX V_LINES.
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
   ID              = I_MSG-MSGID
   LANG            = '-D'
   NO              = I_MSG-MSGNR
   V1              = I_MSG-MSGV1
   V2              = I_MSG-MSGV2
   V3              = I_MSG-MSGV3
   V4              = I_MSG-MSGV4
IMPORTING
   MSG             = I_ERR-MSG
EXCEPTIONS
   NOT_FOUND       = 1
   OTHERS          = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF I_MSG-MSGID EQ 'M3' AND I_MSG-MSGNR EQ '800'.
I_ERR-FLAG = 'S'.
ELSE.
I_ERR-FLAG = 'E'.
ENDIF.
I_ERR-MATNR = ITAB-MATNR.
APPEND I_ERR.
CLEAR I_ERR.
ENDLOOP.
WRITE:/ 'SUCCESS RECORDS' COLOR COL_POSITIVE.
SKIP.
WRITE:/ 'MATERIAL' COLOR COL_HEADING, 20 'MESSAGE' COLOR COL_HEADING.
LOOP AT I_ERR WHERE FLAG EQ 'S'.
WRITE:/ I_ERR-MATNR, 20 I_ERR-MSG.
ENDLOOP.
SKIP 2.
WRITE:/ 'ERROR RECORDS' COLOR COL_NEGATIVE.
SKIP.
WRITE:/ 'MATERIAL' COLOR COL_HEADING, 20 'MESSAGE' COLOR COL_HEADING.
LOOP AT I_ERR WHERE FLAG EQ 'E'.
WRITE:/ I_ERR-MATNR, 20 I_ERR-MSG.
ENDLOOP.
*&      Form SCREEN
     SCREEN
form SCREEN using P_PROG P_SCREEN.
BDCTAB-PROGRAM = P_PROG.
BDCTAB-DYNPRO = P_SCREEN.
BDCTAB-DYNBEGIN = 'X'.
APPEND BDCTAB.
CLEAR BDCTAB.
endform.                    " SCREEN
*&      Form FIELD
   FIELD
form FIELD using FNAME FVAL .
BDCTAB-FNAM = FNAME.
BDCTAB-FVAL = FVAL.
APPEND BDCTAB.
CLEAR BDCTAB.
endform.                    " FIELD
Thanks,
Murali

Screen Captures vanish

I am trying to take a screen capture using shift-apple-4.
I here the camera click, but the image is no where to be found. It does not appear on the desktop, or in the dock. Any thought????
David

I'm guessing that you, like me, get a crash such as the following when attempting to run a capture. Select "Developer" in your CrashReporterPrefs and then try your capture. You should get an error message which you can send to Apple.
You can also confirm by executing the following command; note the output:
$ *screencapture ~/Desktop/foo.png*
2007-10-28 23:44:51.617 screencapture[797:10b] * _NSAutoreleaseNoPool(): Object 0x111230 of class NSCFString autoreleased with no pool in place - just leaking
Stack: (0x929ac28f 0x928b9962 0x913fd311 0x913fd37d 0x913fd3d1 0x913fba6c 0x913fbb32 0x91360da8 0x2f5b 0x5ef5 0x6213 0x6861)
2007-10-28 23:44:51.619 screencapture[797:10b] * _NSAutoreleaseNoPool(): Object 0x112040 of class NSCFString autoreleased with no pool in place - just leaking
Stack: (0x929ac28f 0x928b9962 0x928c4aca 0x913fd39d 0x913fd3d1 0x913fba6c 0x913fbb32 0x91360da8 0x2f5b 0x5ef5 0x6213 0x6861)
2007-10-28 23:44:51.620 screencapture[797:10b] * -[NSCFString _getValue:forType:]: unrecognized selector sent to instance 0xa016aa70
2007-10-28 23:44:51.620 screencapture[797:10b] * _NSAutoreleaseNoPool(): Object 0x111bc0 of class NSCFString autoreleased with no pool in place - just leaking
Stack: (0x929ac28f 0x928b9962 0x913fd311 0x913fd37d 0x913fd411 0x913fba6c 0x913fbb32 0x91360da8 0x2f5b 0x5ef5 0x6213 0x6861)
2007-10-28 23:44:51.621 screencapture[797:10b] * _NSAutoreleaseNoPool(): Object 0x111e50 of class NSCFString autoreleased with no pool in place - just leaking
Stack: (0x929ac28f 0x928b9962 0x928c4aca 0x913fd39d 0x913fd411 0x913fba6c 0x913fbb32 0x91360da8 0x2f5b 0x5ef5 0x6213 0x6861)
2007-10-28 23:44:51.621 screencapture[797:10b] * _NSAutoreleaseNoPool(): Object 0x111d80 of class NSCFString autoreleased with no pool in place - just leaking
Stack: (0x929ac28f 0x928b9962 0x928c4aca 0x913fd432 0x913fba6c 0x913fbb32 0x91360da8 0x2f5b 0x5ef5 0x6213 0x6861)
2007-10-28 23:44:51.622 screencapture[797:10b] * _NSAutoreleaseNoPool(): Object 0x111bf0 of class NSException autoreleased with no pool in place - just leaking
Stack: (0x929ac28f 0x928b9962 0x913fd462 0x913fba6c 0x913fbb32 0x91360da8 0x2f5b 0x5ef5 0x6213 0x6861)
2007-10-28 23:44:51.622 screencapture[797:10b] * _NSAutoreleaseNoPool(): Object 0x111df0 of class _NSCallStackArray autoreleased with no pool in place - just leaking
Stack: (0x929ac28f 0x928b9962 0x929134f8 0x913f626b 0x9241609b 0x913fd46a 0x913fba6c 0x913fbb32 0x91360da8 0x2f5b 0x5ef5 0x6213 0x6861)
2007-10-28 23:44:51.623 screencapture[797:10b] * _NSAutoreleaseNoPool(): Object 0x112470 of class NSCFString autoreleased with no pool in place - just leaking
Stack: (0x929ac28f 0x928b9962 0x928c4aca 0x913f61ee 0x9241609b 0x913fd46a 0x913fba6c 0x913fbb32 0x91360da8 0x2f5b 0x5ef5 0x6213 0x6861)
2007-10-28 23:44:51.625 screencapture[797:10b] * _NSAutoreleaseNoPool(): Object 0x1126c0 of class NSConcreteMutableData autoreleased with no pool in place - just leaking
Stack: (0x929ac28f 0x928b9962 0x928cdbc0 0x928cd921 0x913f6202 0x9241609b 0x913fd46a 0x913fba6c 0x913fbb32 0x91360da8 0x2f5b 0x5ef5 0x6213 0x6861)
2007-10-28 23:44:51.625 screencapture[797:10b] * Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* -[NSCFString _getValue:forType:]: unrecognized selector sent to instance 0xa016aa70'
2007-10-28 23:44:51.627 screencapture[797:10b] Stack: (
2436850283,
2453758107,
2436879466,
2436872812,
2436873010,
2436238760,
12123,
24309,
25107,
26721
Trace/BPT trap

Screen captures to .AVI

I have a lot of 1024 x 768 screen captures that I need to add titling and an audio track to. My final output needs to be a 1024 x 768 .avi. I am using Premiere Pro CS3 and each time I try to export the movie I either get an error or the video comes out as a 720 x 480 that has been cropped on all 4 sides. I would like to know what to do to get the finished video that I need to complete my project.
Thanks for any help
Al

Al Brassell wrote:
> Jeff and Craig,
>
> In my earlier post I stated that my output was being cropped on all 4 sides. I have realized that the reason for that was my source/output were not matched. I have now matched my source/output and I'm still getting slightly cropped on the left and right. All I wamt to do is output a video that will be 1024 x 768 and play in Windows Media Player on most corporate PCs. I'm guessing that the format should be .wmv as this is what I see in a lot of disc based training videos from such vendors as Total Training. The link to a screenshot of my dialog box is:
>
>
>
> I also have an Adobe Connect account if that will help.
>
> Thanks,
>
> Al
1024 x 768 is a 4:3 aspect ratio. Changing your output to 1068 x 768
which is a widescreen resolution may nip that problem in the bud.

Is there a screen capture tool in Photoshop Elements 9?

Is there a screen capture tool to take a screen shot of a window in another application or of Web page?

Thank you for telling us about ALT+PrintScreen. I'm 44 and I've been using computers since I was 13, have built my own computers, have built websites and dabbled in programming and I didn't know that.
This reminds me of 1997 when I still had my first PC I bought off the shelf: a Compaq Presario 433. The father of a friend of mine was a Linux nut back then and he worked for Texas Instruments. So computers were his life. Well, I remember when he screwed up the end of some long command line he had typed into his PC. I think he said, "Argh, I gotta type that all over again." I said, "No you don't." I stepped over and held down the F1 key (I think it was; it's been a long time) and his command line quickly reappeared letter by letter so he just had to backspace the error at the end. He gawked at the screen and I didn't have to look at him to know he was blushing.
There are probably a lot of other ALT and CTRL key combos I'm unaware of, but would find useful every day. Like how to make this message post without having to grab the mouse and hit "Add Reply".

Mavericks Screen Capture causes spinning beach ball

Trained by experience never to install a brand new operating system on top of a perfectly functioning one (unless I want to risk many wasting times and losing productivity), to test out the new Mac OS, I installed Mavericks on an external FireWire drive by upgrading a fresh install of Snow Leopard, updated to its maximum version. Nothing else was on the volume, for I had used Disk Utility to securely erase and content and overwrite the volume with zeros.
Immediately after the Mavericks, I looked at the System Profile, taking some screen captures of selected windows. While Mavericks successfully captured the screens, it failed to display them when I selected one and hit the space bar. Instead, mavericks presented a perpetually spinning beach ball that prevented me from doing anything else on the Mac. I was forced to shut down.
Upon restart back into Mavericks, I encountered the same problem. I had to force power off again.
After rebooting into Mountain Lion on my internal hard drive, I ran a complete series of hard drive maintenance utilities involving all the tools I have, including Disk Utility, Drive Genius, Disk Warrior, and Tech Tool Pro. All ran successfully and reported no problems. I then capped things by running iDefrag to eliminate file fragmentation and to optimize the volume. With several hours of labor invested in preparing the external hard disk, downloading Mavericks' installer, running the Mavericks installer, performing all the pertinent maintenance routines I could think of, and finally optimizing the volume, which has no other software on it besides the new Apple operating system, I restarted the Mavericks volume. I then took a fresh screen capture, selected it, pressed the space bar, and I still got that infernal spinning beach ball.
I let it run for at least half an hour as I returned to watching a football game, hoping things would finally get cleared up. They did not. The ball still spun. I could not even get to the Finder to peek into the Force Quit command under the Apple icon. So, as originally condemned, I was compelled to hold down the power button to regain control of my computer, which this new, appropriately named operating system had wrested from me.
Anyone having a similar problem? Anyone aware of a sure-fire solution, other than to avoid relying on this new operating system, which must be my policy until such glitches get fixed?
At least you know now why I consider it unwise to install a brand new OS atop of one that has served you well.

OK, it’s Wednesday now, late afternoon, following a long yesterday, spent exclusively on getting Mavericks installed, a day which continued well into night, approaching the sun rise, until I collapsed. No one can tell me that the Mavericks installation is without errors! Your mileage may differ, if you’re lucky. But if you had to go through what I just did, you’ll long for the days of System 7, when all you had to do was shove a half-dozen floppy disks into a floppy drive to get your Mac up and running without such angst.
SHORT ANSWER:
After many twists and turns that Apple should have foreseen and not inflicted upon customers, I finally managed to get Mavericks installed on my external Firewire hard drive.
I did follow your lead, Baltwo, that the nature of the problem might lay in corrupt preferences files on the primary Account, but, as I attempted a couple of days, I modified your suggestion that I cherry-pick which plist files might be good vs. which might be corrupt, by deleting the whole **** account. A couple of days ago, my intuition told me that doing that was the wiser way to proceed; today I felt compelled to do exactly that, because I had no other choice.
The reasons I had to do that is elaborated upon below.
LONGER EXPLANATION and DETAILS:
As I explained in the message I composed on Tuesday morning, I felt so insecure that I did not obtain a well-functioning operating system that I had decided to start the installation all over from scratch.
It took all day Monday to again use Disk Utility to securely erase the volume and prepare it for the new installation. When I tried to short-cut the process by doing a Quick Erase, the volume refused to accept the installation of Snow Leopard 10.6.3 from the DVD. On top of that, I again encountered difficulties in installing Snow Leopard from the DVD, because the installer just could not close the deal. The gauge runs up to the 99% mark, and it hangs there saying that it is “Moving items into place.” Sure, it is!
I’m a patient guy, so I let the installer do its thing for about four hours while I watched the World Series game. (Yeah, Red Sox!) But by the time the game was over, so was my patience. I had to Force Power Off the Mac and restart it.
Since I have no confidence in an operating system whose installer failed to do its job properly, I felt that I had to do more. Before I did that, though, I did a Google search to find out if my experience was unique. It is not! The forums are full of people who have complained about this very same hanging problem ever since the Snow Leopard DVD was released. Great, I thought. Now what do I do?
I decided to the Apple support site and download the 1.x GB combo updater to Snow Leopard 10.6.8 in the hopes that the upgrade process would cure whatever issues cropped up during the incomplete installation by the DVD. After downloading that combo disk image, installing 10.6.8, restarting the Mac under 10.6.8, and getting all the software updates applicable to that version, a few tests, supplemented by a running a whole barrage of maintenance utilizes to fix permissions, repair the disk, rebuilt the directory, seemed to indicate that I did finally achieve a solid installation of Snow Leopard 10.6.8 and all its trimming.
To save myself any future agony of having to go through this kind of winding road installation again, I used SuperDuper to create a disk image of the entire volume. That disk image is stored on another Firewire volume, ready to burned at some future date onto a BluRay disc for safe-keeping and backup.
With Snow Leopard safely installed on the volume and sporting one user Account, I was ready to use the Mavericks installer package that I had downloaded last Saturday, when I first began this process, to upgrade to Apple’s latest and greatest OS. Unfortunately, the installation process failed in the same way that the Snow Leopard installer failed. The installer just could not get over the hump of closing the deal. Once I got the installer started, I went to bed.
Four hours later, the installer still had not completed its job, again getting to the 99% mark, and just hanging there. Again, I had to Power Off the Mac. Upon restarting with the Option held down, I elected to start up using the built-in Recovery feature.
That seemed to work, but only sort of. I was able to get a Mavericks desktop, but the User account had absolutely no privileges to do a **** thing. It could not open its own Home folder to see what was in it. It could not complete the screen capture process, because I had no permission to save the picture anywhere, like on the Desktop.
In System Preferences, I tried to increase the size of the cursor, but that failed. In Finder preferences, I tried to make the hard drives show up on the desktop, but that failed, too. I ran permissions in Disk Utility; that did no good. Nothing worked! I could not even change anything related to my User account, because I had no permission to do so. Imagine that: my only account was an Administer account to which I had no access. I would not have thought such a thing could be possible.
I was caught in a loop, stranded on a Mobius Strip, walking on the wild side, surfing the waves of a brand new operating system corrupted by its own installation process.
Not a good thing at all.
Since the first installment had also resulted in a bizarre set of user accounts ending up with QuickLooks being declared the winner of a new account the system decided to create for me, I think it is reasonably safe to conclude that there is some kind of a bug, or flaw, in the Apple upgrade / installation procedure that needs some attention by Apple system engineers. None of this kind of stuff I have delineated at some length should be happening to anyone who owns a Mac.
And, Baltwo, even though I had kept uppermost in my mind your suggestion about creating a new account merely to ferret out which preference files might be corrupt and which might be OK, I decided that I did not want to take any chances at all with this extremely messed User account, which had worked fine in Snow Leopard, but had somehow got corrupted during the upgrade. So, as before, I decided to (1) create a brand new Administrator account; (2) log out from the useless User account in which I had no privileges whatsoever; (3) log in with the brand new Adminstrator; and (4) delete that useless User account entirely, completely, and forever.
At first, I was a little hesitant about deleting the first Administrator account that existed in my Users and Groups pane. I did not even know if such a thing could be done. So, I referred to my David Pogue reference books, and I did a Google search for “Delete Home User Mac” to see what others knew about this. Everyone described the standard way to delete an account; no one even mentioned any prohibition about deleting the original User account. So, I went ahead and deleted it, without encountering the slightest problem in doing so. I even followed up with before and after Terminal commands to see if that useless User account was truly gone, and it definitely went poof. Since I lacked permissions to create any documents at all within that former Home folder, getting rid of it was easy. I think that the System was just as glad to trash it as I was.
Hopefully, whatever corruption occurred during the Mavericks installation and upgrade process was restricted to the preference files associated with that messed-up, original Administrator account so that I can begin exploring Mavericks with a perfectly pristine operating system. Before I start tweaking it or adding stuff to it, my next step will be to use SuperDuper to create a disk image of the entire volume, so that, in the future, I will have a clean set of system of file to install on this external Firewire volume, or on any other internal hard drive I choose to install Mavericks later on. A Bluray disc will contain that disc image for safekeeping when it’s time to remove it from the destination volume where it gets created.
As to the tardiness of my reply, it is caused by the exorbitant amount of time—four days!—it took me to trek along this twisting, winding path of installing Mavericks, as well as a glitch in the mismatch of similarly looking User Names associated with similarly looking Apple ID accounts and similarly looking User Names associated with nearly identical Email Addresses that do not convert from one to the other, as, for example, mac.com does to me.com.
As I learned from Apple Staff who responded to my report that I was being locked out of the Apple Discussions community, there are four pieces of information that must match up for each Apple ID account, and my data had slipped out of sync. Now I know why, during Apple’s changeover in the formatting of the Apple Discussions section, I lost all those “points” I had accumulated in helping others, not that I track such things, and I could not find where my previous discussions were.
That’s also why I may be able to award anyone points for helping me in this thread, but I’m dialing in under the “other” Apple ID, not the one I used to create this topic. Close readers will observe the slight difference.
Thanks a lot, Baltwo. You get the credit for pointing me in the right direction.

Screen capture error

Similar Messages

Maybe you are looking for