Working Around no-recovery problems

This will happen if you have files in the last 600 MB of your mac partition. Get a cloner like SuperDuper and an external hard drive that's big enough. Clone your mac partition to the external drive. Reboot from the external drive. Use disk utility on the external drive to erase your mac partition. Nudge the partition to be about 1 GB smaller. Clone your external mac partition to the erased partition to reconstitute it. Now you can install Lion to it. Note this gives you a full backup of your mac partition, so don't lose it.
I bought a 1 TB drive and split it three ways, with a mac partition, a bootcamp partition and a Time Machine partition.

SuperDuper does not backup (clone) the Recovery HD.
However, with Lion 10.7.2 you can use this link (Step 3) to recreate the Recovery HD without reinstalling Lion. All you need is the Lion Recovery Update file. This does work as I've used it several times to recreate the Recovery HD after a SuperDuper restore.

Similar Messages

Does anyone know of a work around for this problem? : iphone 5 will not work on Chryslers uconnect. I found out that they are working on it but have no ETA.   However, they will not help you if your vehicle is older thatn 2008.

Do not get an iphone 5 if you want to use it with a Chrysler product. The Chrysler Uconnect system might pair with your phone but the uconnect system will usually abend and become unusable after a few telephone conversations. I have been to the dealer twice. They have reset the uconnect system twice and I find it works for about 2 to 3 phone calls then it abends and uconnect becomes useless. They had me call Chrysler at 1-800-247-9753. I was told that the iphone five is not compatable at this time with any chrysler uconnect phone through the dash system, even the new vehicles. He had me get on this web site: www.uconnectphone.com as a place to monitor as when it would be compatable. They told me that Samsung seems to be working harder to make it compatible than apple is and they had no idea when it would begin to work. In effect Chrysler was telling me dump the iphone and get a Samsung if you want it to work in a Chrysler. Also, the site would only give you information for Chrysler that were 2008 or newer, they gave the following number to call if your vehicle was older.    I called that number and they told me that Chrysler and Uconnect had no plans at all to make the iphone 5 work, in the future, on any Chrysler older than 2008. So.......If you have a Chrysler or Dodge that is older than 2008 you will NEVER be able to use an iphone5 on the uconnect through the dash system.   Do not buy an iphone if you have an older vehicle. It will never be supported for the $1,000 you paid for this uconnect system on your car. My car is a 2005 Town and Country. I asked both Chrysler and uconnect if their was some sort of work around so I could use my phone. They both told me their was not and that they had no plans to resolve this situation for my vehicle. This means that I need to either get rid of my $42,000 vehicle with low milage or get rid of my Iphone 5. Niether are really good options.
I was also givne the following places to send formal complaints, even though I was told that neither Chrysler, Dodge or Apple were going to do anything to correct my problem:
for email:   [email protected]   or Mail: Chrysler customer Assistance P.O. Box 218004, Auburn Hills, Michigan 48321
If anyone hears of a work around to be able to use an Iphone 5 in a Chrysler or Dodge product, please let me know.

This response is a little late as I just read about your problem. I have a 2012 Dodge Charger and a 2012 Chrysler Town and Country and both worked flawlessly with the iPhone 5s my wife and I had. However, we just upgraded to the iPhone 6 and Uconnect will receive calls but you cannot answer them. You can callout successfully, however. the annoyance being the inability to answer incoming calls in the HandsFree mode.

Temporary work around app store problem

Until apple fixes the problem you can still d/l apps if you can at least get into the app store. If you can, enter whatever app your looking for in the "search" box,,,if that then gives you a drop down menu click on something in that menu and it should take you to the apps,,,this is a round about way of doing it but it will work until apple figures out that many of us here can't access the apps the normal way.

Some users report it's working now.
 Cheers, Tom

Work around for unsupported OS?

I'm rcving a message that InDesign does not support the OS that I'm using, therefore I can't download or use it. Is there a work-around for this problem?

Hi Rachel,
Unfortunately there are no workarounds for the product which isn't supported for an OS.
Check the System requirements here: http://helpx.adobe.com/x-productkb/policy-pricing/system-requirements-indesign.html
Thanks!
Ankit

Png work-around?

I thought there was a way to work around the png problem by doing a screen capture and saving as a jpeg, then putting the file back into iweb. Has anyone tried this? Can't seem to find the thread that I saw before. My site takes too long to download because of the png conversion. What do you think?
http://www.thedogsmind.com
macbook Mac OS X (10.4.7)
macbook Mac OS X (10.4.7)

I don't think your site is particularly slow. However, yes, you can try to get around the PNG conversion by bringing in your JPGs exactly the size that you will be using them, so that iWeb doesn't have to do any processing of the images.
As far as speed of page loading goes, you can consolidate all your static graphic elements into one jpg by taking a screenshot of the elements once you have them all placed in iWeb. Then delete the separate elements and bring the consolidated jpg screenshot back into iWeb, making sure that it is used at original size without any frames or shadows applied.
I recommend an application called "Downsize". It allows you to specify the resolution as well as the amount of jpg compression to apply to your photos. It also lets you apply drop shadows and simple frames and rounded corners. And then you save all the finished images as jpg ready to go so iWeb uses them as is.
http://www.stuntsoftware.com/Downsize/
Post here if you have any questions about this technique. I hope this helps. Good luck!

Patches not sounding - a work around???

Can anyone else verify this? On Mac Pro with 2GB of RAM, I am also seeing the problem where, after a patch change, the first note/chord makes no sound. The second note/chord works (and usually everything after that, until another patch change, though it only occurs 1/3rd of the time for me).
But after I play through all patches (in this case, using the Rock template), the problem seems to no longer occur. This isn't great, but if this works, at least I can use this in a gig.
Is anyone else seeing this as a work around to the problem?

MainStage Fan wrote:
Thanks, that's what I'm getting at: does this work for everyone as a workaround? (that being, first go through all patches and play them).
This is the work around that I have found as well. For me, the last time I had a gig, I was concerned about playing them through during a rehearsal about an hour or two before the actual gig. I had wondered if I left the machine (and MainStage) running if when I came back, would the patches work the way they are supposed to. Fortunately in this instance I can report that they worked fine for the rest of the gig only requiring the play through just the first time at start up. So I think this is a useable work around for now (and hopefully not a deterrant from Apple to fix the problem). I can't help feeling like I am jumping without a net. If I had to reboot in the middle of a gig for whatever reason, it would be a real pain to disconnect from the FOH system just to go through each patch again to make sure it will properly sound when played.

Work-around to "unknown device" problem

I found a work-around to the "unknown device" problem, a pain to do, but much less painful than any alternatives I've found so far.
In my case, I can connect my Ipod one time. After I eject it, if I reconnect, I get the Unknown Device error. That's where this work-around comes in.
There is an INF file (a Windows hardware configuration file) in the Windows\INF directory that has a name that will be specific to your computer. Once you determine that file, you need to re-install it. Re-installing it allows the Ipod to be recognized the next time it is connected. These are the steps:
1) Determine the file name on your computer. You only need to do this one time, and then remember the name. Using Regedit, navigate to HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-44455354 0000}. Then do an Edit / Find for "ipod" without the quotes, making sure that "Data" is checked and "Match whole string only" is not checked. It should find "Apple iPod USB Driver" in the "DriverDesc" value in one of the sub-keys. There will be another value called "InfPath". The data for that is the file name for the INF file on your computer. On my computer it is oem51.inf. It will be something like that on yours.
2) In Windows Explorer, go to C:\Windows\Inf and find that file. In addition to "oem??.inf", there will be an "oem??.pnf" (same numbers), which is a binary version of the .inf file. Delete that file, or rename it if you prefer. If it exists, step 3 will not work.
3) Right click on the .inf file and select Install. The computer will chug for a few seconds. The .pnf file should reappear and, more importantly, your iPod should now be able to connect one time. At least it does for me.
I hope that Apple puts out a fix for this problem sometime soon. Meanwhile, doing steps 2 and 3 every time I want to connect is annoying, but bearable.

I would like to apologize for posting this message. I promise that it did work and did seem to be the solution at the time I posted it, but it helps me no longer. My Ipod was recognized several consecutive times after I posted this with no work-around, but then it became an unknown device again, and there it stays, seemingly forever.
I am a highly skilled and experienced Windows system programmer, and this has me stumped. I apologize for any time that my message may have wasted for others. I have also tried every other solution that has been posted here and elsewhere, and none work.
I would recommend that Apple pay me a lot of money to find and fix this problem. Short of that, they should pay someone else to fix it. To have this many fatal problems for so many people should be considered unacceptable. Until a fix is available, I shall just be happy that I got as much onto my Ipod as I did before it became unavailable.

Work around for server not found problems on FF36

I have found a work around for all the people having server not found problems with FF36.
If you manually set your network adapter DNS to an external DNS server (as opposed to your local ISP) then the problem goes away. I set mine to use the two google DNS servers:
Preferred: 8.8.8.8
Alternate: 8.8.4.4
Not a clue why this works but it is 100% successful on my desktop PC, whereas before I could hardly connect to a webpage with FF36 without multiple page refreshes and much frustration, even though FF35 was fine and rolling back to FF35 was also fine.
Something has changed in FF36 and either the way it handles DNS or the way it works with some network adapters.
It is nothing to do with add-ons, profiles or firewall software as I have tried all of these things and only the DNS change made a difference. I even copied over a full working profile and the program files directory for Mozilla from my portable which was having no problems and the problem still existed on the desktop, which is why I started looking at the network adapater since everything else between the working PC and the non working one was identical.
Hopefully this will help the developers to pin down the real cause of the problem and fix it in the next release.

Well done. Thanks for finding that.
That is not only assigned but has an approved patch included in the scheduled Fx36.0.1 release so it should be fixed in few days, watch out for the upgrade.
* Bug 1093983 - DNS resolver should not use 'ANY' to get cached records for TTL <sup>[https://bugzilla.mozilla.org/show_bug.cgi?id=1093983#c35 c#35]</sup>
* https://wiki.mozilla.org/Firefox/Channels/Meetings/2015-03-03#Schedule_Update
With the bug now fixed it would not really be appropriate to add further comment. I do now see another related bug assigned but not being fast tracked, so if all goes well that will probably land in Firefox 39.
* Bug 1138242 - DNS: Request A and AAAA record types rather than ANY when obtaining TTL on Windows

Portrait Printing Problem Work-Around

One of the problems that appeared with iCal 2 (I'm using 2.0.2 for this work-around) in Tiger is the inability to print Month and Week views in Portrait mode. iCal automatically rotates the paper to landscape mode, even if you create custom paper sizes opposite to the customary sizes (ie: 11.00" wide by 8.50" tall should print sideways in Portrait mode).
In attempting to outsmart iCal, I created a custom paper size that was "square" - 8.50" x 8.50". Unfortunately, it printed on 8.50" from left to right in Landscape mode, leaving a 2.5" white spot on the right side of the still wrongly oriented paper.
However, on the next attempt to print, with the "square" paper selected, I found that selecting "US Letter" will give you the desired Portrait mode. This works for an size paper, and works with after selecting an custom made "square" paper size.
Here's the step-by-step process:
1. Open any application (other than iCal) with a "Page Setup..." option in the File Menu (Safari works just fine) and select "Page Setup...".
2. Select the "Paper Size" pop-up and choose "Manage Custom Sizes..."
3. Click the "+" button in the bottom left corner to create a new Custom Page Size.
4. Name your new size by double-clicking on "Untitled" and typing. I called my page size "iCal Square".
5. Now set the Page Size to 8.50 Width and 8.50 Height. Any two identical sizes seem to work, and you can use more familiar sizes for non-US papers.
6. Select "OK" to close the Custom Page Sizes dialog, then select "OK" to close the Page Setup dialog.
7. Now open iCal. (Note: If iCal is already open, Quit iCal and open it again. This seems to help the print dialog recognize your new or modified Custom Page Sizes.)
8. Choose "Print..." from the File Menu. Select your new Custom Page Size from the "Paper" pop-up. It should appear at the bottom of the list.
9. Press "Cancel" to close the dialog without printing.
10. Now choose "Print..." again. Your "Paper" selection should be the Custom Page Size you selected ("iCal Square" in my case). Re-selecting US Letter (or your preferred paper size) will give you a Portrait version of the Month or Week view. (Note: If you select Day or List view, it will revert back to Landscape when you re-select Month or Week.)
Since iCal defaults to Month View, this work-around does not work to create Landscape versions of the List and Day views.
Until Apple adds Page Setup back into iCal, this two-step work-around should do the trick.
Erik

It has been pointed out at www.macosxhints.com in response to my post there that you can manually override the iCal settings by navigating to the iCal application, Ctrl/Right-Click and choose Show Package Contents, then navigate to Resources/monthview.aplmodel/Contents/Resources/model.xml/
I would recommend backing up the file before trying anything. But it is possible with TextEdit to simply modify the 2nd line of the file:
<model name="Month" localized-name="Name of the month model" version="0.1" description="View of a full month" source="APLMonthSource" timerange="month" orientation="landscape">
You can change the orientation setting to "portrait" or simply delete the the orientation text and iCal will default to Portrait Mode without my previous workaround.
Again, back-up the file first before you mess around too much.

Printing Problem Solved (Temporary Work-around)

I've posted before, and others have posted here and elsewhere, about problems printing with Aperture since upgrading to Leopard. In my case, it's been with an Epson R1800.
Well, believe it or not, with the help of Epson support on the phone, I've figured this out. First of all, there is definitely a problem with Aperture's (or Leopard's) color management. What used to work (setting a color profile in the Aperture print dialog, and selecting "no color management" in the printer dialog) definitely does not work correctly at this point.
If you want color management, what you have to do is select "System Managed" in the Aperture print dialog, and select (for Epson) "Color Controls - Epson Standard" in the Epson dialog. What this does is select the standard Epson profile for the paper you have selected. For example, if you've chosen Epson Premium Glossy Photo Paper, the printer driver will use the "SPR1800 Premium Glossy" profile (Epson's standard profile for that paper, assuming you've downloaded it). Of course, that gives you Epson's version of what you want to print. If you have created your own profiles, using a spectrophotometer for example, you need to get the printer driver to apply YOUR profile instead of Epson's.
Here's how to apply your profile: Open Colorsync (in the Utilities folder), and select "Printers" in the Devices menu. Under the printer model, Stylus Photo R1800, in my case, select the profile for the paper you're interested in, say "SPR1800 Premium Glossy", and look on the right side of the window at "Current Profile:". Click the down arrow, and select "Other". Navigate to the profile you've created, and click "Open". This will set the profile you've created as what the printer driver will use when it thinks it's applying the SPR1800 Premium Glossy profile. Set other paper profiles (e.g., "SPR1800 Enhanced Matte") to whatever profile you've created for those papers.
Now, when you select "System Managed" in the Aperture dialog, and "Color Controls - Epson Standard" in the Epson dialog, it will apply your own profile.
Hopefully, Apple will fix the problem with color management, and we'll be able to go back to color management as it was before. In the meantime, this is the only work-around I've found.

I was/am totally a Mac guy, meaning my roots were System 7 based, and my knowledge of all things UNIX is being built slowly as needed in the OS X world. While I can make Photoshop & Aperture (and the GUI portions of OS X) stand on their heads and do backflips for treats I can't, with much conviction, speak on the roots of UNIX drivers. I think, and someone please correct me if I'm wrong, that Gutenprint drivers are CUPS 'compatible' drivers, but not necessarily "CUPS" drivers in that they work with other printing platforms as well. Here are some sources of info:
http://gimp-print.sourceforge.net/
http://www.cups.org/
The Gutenprint drivers may be the CUPS drivers for the Epson printer, I don't know for sure. On the Canon site, there are two drivers available for download for the Pro9000. One labeled standard, the other labeled CUPS. By default, when adding the printer, my system uses the CUPS driver. I can actually have the Pro9000 added twice, once with the CUPS driver, once with the standard driver. I spoke with an Canon engineer the other day, and contrary to the advice you get from the standard phone support reps, he told me to definitely use the CUPS driver when printing RAW or 16-bit images from Photoshop or Aperture, as it's the only way to do 16-bit printing.
Message was edited by: KBeat

Getting a "sticky" for all LP8 problems and work arounds/solutions?

Any chance we could get a sticky on this? It would be a lot faster than going thru the "Search Forum" option.
List the known issues
List the fix/work around for the issue
Rob

We asked for that in the L7 forum for years and got little in terms of a response (see below). And definitely no sticky!
Sure, there are a few knowledge base documents that describe issues with L8, but in general, acknowledging known problems is not something Apple does, unfortunately. How do I know this? Well, experience. And also, from what they have to say about their software in the Getting Started guide:
"Experience has shown that such system _problems are rarely caused by a defect in Apple programs or hardware products_. All Apple hardware and software is _rigorously tested_ by a diverse range of musicians and studio users, from a variety of fields and uses, who look for any faults or problems.
This doesn’t mean that the possibility of errors can be completely ruled out; problems can crop up periodically. This is not unexpected—as the various applications, operating system versions, and drivers—are all developed, and improved in parallel by unrelated programming teams. This can lead to occasional compatibility problems. _Apple provides fixes in the form of software updates, as soon as such problems are identified._ Apple is always grateful to users who report any problems."
(emphasis added by iSchwartz)
If that isn't a profound mixture of truths, half-truths, and flat-out lies.
Now... there is some kind of "tips" board somewhere amongst Apple's Discussion Forums. When the subject of having a sticky came up once on the L7 board a while ago, a mod suggested that I submit tips/workarounds for inclusion on that board. I checked it out and it's a freekin' nightmare to find anything. And "submitting" tips means that someone has to approve it, and who knows if that person would be Logic-savvy or not. So there it is...

How can I work around a DVD burning problem

Steve Grisetti: How can I work around a DVD burning problem?
Question: Does PSE and PE -7 solve this problem or make any difference at all?
Joanna

This article, from the FAQ list at the top of this forum, is valid for all versions, since it may be a problem for any.
http://www.adobeforums.com/webx/.59b5f52c
The problem is not so much with Premiere Elements as it is with challenges faces in the operating system registry. Basically, DVD burner programs, like Nero, which are installed on your computer at the factory, refuse to share access to the DVD burner with other programs.

ITunes 7 crash problem work-around

Until Apple fixes the never-should've-been-released iTunes 7, this is what I've come up with as a work-around: Go back to iTunes 6.0.5
Simpler said then done.
1) First thing is remove that godforsaken iTunes 7 from your Applications folder.
2) Next thing you need to do is delete your iTunesX.pkg file from HD>Library>Receipts so that when you try to install 6.0.5 your computer doesn't block the installation because it thinks iTunes already is installed.
3) Third, go to your Music folder and create a new folder (call it "For when Apple fixes iTunes 7" or something like that); move the iTunes folder into this new folder, otherwise when you start up iTunes 6 it will tell you that all your music is formatted for iTunes 7 and the program won't even open.
4) Fourth, go here and download iTunes 6.0.5
http://www.apple.com/downloads/macosx/apple/itunes605.html
5) Install iTunes 6.0.5
6) Open iTunes 6.0.5
7) In iTunes, Click on File>Add to library... go to that iTunes folder that you stuck in that new folder called "For when Apples fixes iTunes 7" in step 3. Highlight all the albums you want and click Choose or Open or whatever it says
8) Depending on the volume, it will take a while to copy all the music files. It's a two-step process: first they appear in your iTunes library greyed out, then eventually they are fully copied and become live.
Good luck!
G5 iMac Mac OS X (10.4.8)

Somehow the audio output setting in audio midi setup got set to 96000Hz. I changed back to 44100Hz and this seems to have fixed my crashing problem.
I hope this helps some other frustrated peeps.
Normally, you only have to worry about this changing when 3rd party apps are installed, but it sure seems like either the iTunes 7 or Quicktime update were the culprits this time. Another symptom that this setting may be incorrect is that you get no sound at all from flash content.

VPN Startup problem after a reboot - a work-around

Hi Folks.
I'm posting this info for those that have problems with Mac OS X 10.4.x server, running a VPN.
(Seems to affect OS X 10.4.4 - 10.4.7 from what I've tested).
I've discovered that lots of people are having troubles after they reboot such a server... The VPN service is running, but if you try to VPN into the server, it won't "authenticate" properly.
I found simply Stopping the VPN service, and then Starting the VPN service, fixes the issue.
That's good to know... But what if you're at home when you discover the VPN isn't running properly? Read on...
Now, while only a work-around... It's enough to get many people running on their VPNs again.
What about automating the process? I'm glad you asked...
Since ServerAdmin commands can be run from Terminal, you can automate a command to run at set periods. I'm no "terminal guru", so I've just set a scheduled task in Remote Desktop 3, to send some unix commands to my VPN server.
The commands are simply as follows, and you need to specify in Remote Desktop, that they run as User: root.
The commands to run:
serveradmin stop vpn
serveradmin start vpn
Set that to run periodically (e.g. once a week, if you reboot your VPN server weekly, for example), and you're set.
(I set this up on a server admin workstation on the LAN, in a secure room, which is always on, with Remote Desktop running).
I'm sure there are probably other ways of scripting such a stop/restart -- perhaps if you have some other ideas, you could post them here?
Hope this info helps someone else running a VPN... If so, drop me a line...
Cheers,
Derek

I had the exact same issue. I just restarted my server for the first time since set up (1 month ago) and VPN stopped working. Then I restarted VPN services and it kicked back into working order. what gives?
Nothing changed on the server, except for a nice little restart.

Lock Up In Halo - Via Chip Said To Be Problem... Work Around?

I'm experiencing system stalls... approximately 20 seconds while playing HALO. The game will stall then pick right back up.
Microsoft blaims the VIA chipset for this problem.
I'm hoping their is a work around.
I have the lastest drivers from VIA and Nvidia as well as the latest firmware for the MOBO. I can't seem to locate the video card BIOS on the website... and I know live update does it but I hate live update.
SYSTEM:
Windows 2000 Pro SP 4 (no updates listed on windowsupdate)
MSI KT3-Ultra-ARU (MS-6380E v. 1)
-- BIOS Ver 5.7 (stalls with all BIOS version and yes I tried them all)
-- VIA Hyperion Ver 14.51
MSI Nvidia Geforce3 Ti200 Pro TD-128 (MS-8851)
-- Detonator Ver 53.03
-- BIOS version unknown (I did update the firmware once)
Athlon XP 1700+
768MB DDR 266 (Micron)
80GB Western Digital SE
40GB Maxtor ATA 100 7200RPM 2MB
SONY 500A DVD+-RW
LG CD-ROM
Thanks,
Mike

Typical microsoft, there are thousands of via-boards sold but ms only says 'not our fault'. Great support indeed...
You may try >this but I really don't know if it solves your prob.
Virus scanners or firewall active?

Working Around no-recovery problems

Similar Messages

Maybe you are looking for