"Don't Panic" + scim

Well, I decided to change the OS on one of my computers from Ubuntu to Arch, after the install I did pacman -Syu and found that I'm using the "newer" version "Don't Sweat". Cool.... but.
Scim usually installs easily using the instructions from the archlinux website:
http://wiki.archlinux.org/index.php/Sma … d_platform
This time it's a no go. I have Korean (hangul) input working fine so long as my LC_CTYPE is set to ko_KR.utf-8. This however makes the panels and  titlebars absolutely HUGE. I mean almost 40px titlebars are big enough for the blind to see. What gives? Any ideas or is this some sort of bug in "Don't Panic"?
Last edited by necrolin (2007-08-02 14:41:54)

OK, so I was playing with the system and I noticed something strange which is probably related. When I have my LC_CTYPE set at en_US.UTF-8 then I have Korean fonts listed when I go into the change font dialog, but SCIM doesn't work.... erghhhh.
When I change LC_CTYPE to ko_KR.UTF-8 then my Korean fonts disappear from the listings and I get Chinese fonts listed????!!!! And SCIM works, but the screen is all messed up because it's leaving too much space for the fonts. Example, in the terminal everything looks double or even triple spaced.
Any ideas?

Similar Messages

  • 2007.08 Don't Panic Isos released, installation feedback

    Hi Arch community,
    5th August, 23:00 CEST (Central European Summer Time)
    Arch Linux Don't-Panic 2007.08 ISO release
    Get Archlinux ISOs in /iso/2007.08/{i686,x86_64}
    on your favorite mirror.
    http://wiki.archlinux.org/index.php/Mirrors
    or
    http://www.archlinux.org/download/
    Please don't forget to check md5sums.
    It's mostly a 2.6.22.x Iso with some fixes to last Linuxtag Isos.
    Changelog to last Duke-Linuxtag2007 installation ISO:
    - kernel 2.6.22.1 usage
    - fixed: update mkinitcpio for new .22 firewire layout
    - fixed: update hwdetect for new rtc_sys and firewire stuff
    - Memory requirements bumped to 128MB!
    - Serial console support in install environment
    - USB Keyboard issues fixed
    Setup changes:
    - fixed: "" around CONSOLEFONT and CONSOLEMAP
    - fixed: dhcp rc.conf entry
    - fixed: not generated glibc locales
    for fixed bugs reference:
    http://bugs.archlinux.org/task/7410
    greetings
    tpowa
    Last edited by tpowa (2007-08-05 20:57:38)

    Installation feedback:
    I installed Arch in virtualbox on a Windows XP host and after it initially hung up on boot (enabling acpi and apic was necessary), everything worked fine.
    I was very pleased to see the pacman mirror selection dialog, apart from a "missing" pacman -Sy (I wondered why I couldn't install xfce4...everything was set up perfectly and it took me a while until I realized, that the local package database only includes the current repository) there was no need for post-configuration for the base system. I haven't checked for rankmirrors this time, but
    Setting up X and xfce4 was done quickly and I had no further problems.
    I was using the FTP-install-image.
    Edit: Stay away from Safari for windows, it will not send or copy text fields containing a '[' or ']', it just cuts away everything following this character.
    Last edited by wuischke (2007-08-06 19:36:03)

  • "Don't Panic" paniced on first boot

    I thought this was kind of funny, I upgraded to the new kernel (and thus to "Don't Panic") and after a reboot I was greeted with a kernel panic... It was easily solved by defining "rootfstype=" kernel parameter but it was kind of ironic

    It is called don't panic, isnt it ? Dont worry
    Last edited by Insane-Boy (2007-08-01 14:36:59)

  • Kernel don't panic

    Hi.
    I have recently installed archlinux on my machine by network instalation.
    Since then I am running and I can't get rid of the " don't panic " kernel.
    I have updated the databases and all but shoudn't it change by default?
    Regards,
    /Dex.

    Name           : initscripts
    Version        : 2008.08-1
    URL            : http://www.archlinux.org
    Licenses       : GPL 
    Groups         : base 
    Provides       : None
    Depends On     : glibc  bash  awk  grep  coreutils  sed  udev>=118  net-tools 
                     ncurses  kbd  findutils 
    Optional Deps  : None
    Required By    : None
    Conflicts With : None
    Replaces       : None
    Installed Size :  96,00 K
    Packager       : Pierre Schmitz <[email protected]>
    Architecture   : x86_64
    Build Date     : Qui 14 Ago 2008 09:45:57 UTC
    Install Date   : Sáb 16 Ago 2008 20:14:05 UTC
    Install Reason : Explicitly installed
    Install Script : Yes
    Description    : System initialization/bootup scripts

  • Corrupt boot-archive? Don't panic :-)

    One of my Solaris 10 (update 05) servers runs on a piece of HP hardware, which seems to have some sort of memory error which every now and then causes the box to panic.
    After a panic today, the system wouldn't boot, instead it complained about the boot-archive being corrupt, and its gzip-checksum being incorrect.
    To solve it i booted into the failsafe mode, which worked, from there i mounted the /a partition and tried to run:
    bootadm update-archive -R /a
    which returned without any errors within a second. However it didn't actually update the boot archive.
    My guess is that the boot-archive (which seemed of a reasonable size) was so corrupted that the bootadm update-archive couldn't read it, and apparently, if it cant be read, it wont return any error nor fix it.
    I also tried to move the old boot_archive to a new location and re-run bootadm update-archive, but that didn't work either since the archive didn't exist.
    The solution in the end was to rename the boot-archive:
    mv /a/platform/i86pc/boot_archive /a/platform/i86pc/corrupt_b_archive
    and then reboot the machine into failsafe-mode again, upon booting into failsafe mode a second time, it discovered that the disk didn't have a boot-archive, and created one for me.
    After this i just had to reboot and now the system booted normally.
    Hope this helps someone someday.. :-)
    .7/M.

    Thanks for the info. One question: I've tried to boot to failsafe several times on two different machines running Solaris 10 u8 x86 on HP hardware, but it never works. I have /var as a separate data set - does your system? I seem to remember a bug mentioned where this is a problem with /var as a separate dataset?

  • IMac 1TB drive replacement program: notifications sent in error (don't panic)

    An hour ago I received a note like this:
    Dear Apple Customer,
    Product Serial Number(s): XXXXXX
    Case ID: 11111
    Follow Up Number: 1111
    Thank you for submitting a refund request. We need a repair receipt and banking details to complete your refund.
    Please contact the service center that replaced your hard drive and obtain a receipt, if you do not already have it.
    Reply to this email and attach a scan of the receipt. Do not change the subject line.
    This made me unhappy, as I thought I'd completed the refund request process for my defective drive two weeks ago.
    I wrote a snarky blog post, posted a question here that was removed for violating posting rules (guilty), and replied to the email with a complaint. Then I received this note:
    Dear Apple Customer,
    The prior communication you received from Apple stating the need for additional information was in error.
    We completed your refund for a hard drive replacement as part of the iMac 1TB Seagate Hard Drive Replacement Program.
    Refund Amount: 281.25
    Credit Memo Number: 111111
    Case ID: 11111
    Follow Up Number: 111111
    You will receive your refund in four-to-six weeks.
    So the original notice was a mistake. I assume I'm not the only person who got it. If you got the notice, and haven't received a correction, try replying and ask if it was sent in error.

    Thanks for the report!

  • Before You Upgrade to 10.5.2 - If It Ain't Broken Don't Fix

    *DO NOT UPGRADE MID PROJECT.*
    *DO NOT UPGRADE BEFORE CLONING YOUR BOOT DRIVE.*
    *DO NOT UPGRADE IF IT AIN'T BROKEN*
    Some else wrote this:
    Here's a list of known new features:
    http://docs.info.apple.com/article.html?artnum=307109
    1. The combo update is found here:
    http://www.apple.com/support/downloads/macosx1052comboupdate.html
    And may help with fixing issues with the Software Update version of 10.5.2, or the "delta" version designed just for 10.5.1.
    2. Wait until your mission critical apps have all been tested with it.
    3. Wait until any hardware you use has been tested with it.
    4. Wait until any system addons you use have been tested with it.
    5. Only upgrade after backing up your data at least twice, dismounting and disconnecting those backups.
    6. Disable all third party modification utilities before updating, unless you know the version of those utilities is compatible with the update.
    7. Make sure your hard drive has at least 9 GB + an arbitrary 15% of the disk space free before applying the update + double the update's file size. This will ensure that your update does not overfill your hard disk.
    8. Only upgrade after repairing permissions before and after applying the update.
    9. If you do find issues please report them to http://bugreporter.apple.com/ or http://www.apple.com/macosx/feedback/
    10. If you would like to find out how to troubleshoot after applying the update, wait a couple weeks for people to get their hands on it to see if they can reproduce your issues.
    11. Don't be too quick to blame it on the update, many issues with corrupted files, antiquated drivers, corrupted cache files, and logfiles can make issues surface immediately after applying the update.
    And above all, don't panic, and start a new topic thread if you need troubleshooting:
    http://discussions.apple.com/forum.jspa?forumID=1219&start=0
    All the people on this board are here to help you, and we don't want blame to be cast before a solution is attempted to be found, as then we can't know if you really want a solution to your problem.

    And if people DO read it, it will be too late as they already upgraded and are only here to report issues, not look for solutions to issues BEFORE they happen.
    Too many people think that all this high end editing stuff should "just work." You have to treat your system right....you have to have a little technical know-how. This isn't easy folks.
    Shane

  • My mac book pro is frozen on a grey screen with an apple in the middle. It is not responding to restarting and has white letters that says panic(cpu caller 0xffffff8027259241) and so on

    panic(cpu 0 caller 0xffffff8027259241) : "Unable to find driver for this platform: \ "ACP\".\n"@/SourceCache/xnu/xnu-2050.20.9/iokit/Kernel/IOPlatformExpert.cpp:154 8
    Debugger called: <panic>
    Backtrace (CPU 0), Frame : Return Address
    0xffffff80a0b1bde0 : 0xffffff8026e1d626
    0xffffff80a0b1be50 : 0xffffff8027259241
    0xffffff80a0b1be60 : 0xffffff802723081b
    0xffffff80a0b1bea0 : 0xffffff802723033e
    0xffffff80a0b1bf30 : 0xffffff802722c2d0
    0xffffff80a0b1bf70 : 0xffffff8027230e99
    0xffffff80a0b1bfb0 : 0xffffff8026eb2957
    BSD process name corresponding to current thread: Unknown
    Mac OS version:
    Not yet set
    Kernel version:
    Darwin Kernel Version 12.2.1 : Thu Oct 18 16:32:48 PDT 2012; root:xnu-2050.20.9~2/RELEASE_X86_64
    Kernel UUID: 0AFA55FD-872F-3BBE-214EB586A16D
    Kernel slide:              0x0000000026c00000
    Kernel text base:       0xffffff8026e00000
    System uptime in nanoseconds: 507642361

    Press the Power button and hold it down until the computer turns off. Restart. Do you still get the same result? If so, then try booting into Safe Mode, then restart normally. A safe mode startup takes considerably longer than a normal one, so don't panic. You will also see a progress bar at the beginning.

  • Apple Care works? For me don't

    Apple Care is not working for me.
    I call then and they are saying that they can't unfortunately resolve my problem.
    I have an Imac 21.7 and it's with an yellow mark behing the glass of the monitor.
    I bought the computer on agost 20th, and they are saying that I've bouthg my computer on may 2nd.
    <Edited by Host>

    And remember, don't panic.  The only thing you are entitled to now is free phone support 90 days from August 20th, and that's what you need to remind AppleCare/Customer Relations.  Hardware support, AppleCare purchasing to extend to 3 years from date of purchase is still available until May 19th, 2012 at the minimum, and if you get the right person at AppleCare/Customer Relations, August 19, 2012.  After which point all AppleCare coverage is on a case by case basis for both hardware and software without warranty.  Note, a warranty is only a warrant against manufacturer defects.  It does NOT cover accidents, or things Apple considers normal wear and tear.  You can read that on the http://www.apple.com/support page.  I do recommend buying AppleCare, if only for the simple reason you will get unlimited phone support to explain things about Apple software from Apple itself.  If limited time manufacturer defect should surface, that's what AppleCare is also good for.  But don't expect accidental spills, falls, or bumping of the computer to be covered.  This as rkaufmann says is a user to user forum.  We can just explain our experiences to you.  For Apple directly you must call AppleCare/Customer Relations.

  • Why did I have a kernel panic?

    I was in the process of disconnecting my Nikon D40 (a procedure I have done many times without incident). Usually I shut the camera off and pull out the USB connector once the volume disappears from my desktop, with no problem. This time, as soon as I shut off the camera, I got a strange "You must restart your computer" message I'd never seen before (I've had the computer almost 3 years). Discovered this was a "kernel panic" message.
    Why did my computer do this? The only thing that's changed on it recently is that I installed Adobe Air although I don't believe I was running any Air applications at the time. At the time I was running Photoshop Elements, Nikon Picture Project, Firefox and a feed reader called Feedpopper. Again I have run all these programs without trouble for several years.
    Here is the message from panic.log:
    Wed Dec 31 13:57:16 2008
    panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
    CR0: 0x8001003b, CR2: 0x0000001e, CR3: 0x00d99000, CR4: 0x000006e0
    EAX: 0x00000000, EBX: 0x0311ec00, ECX: 0x0039a412, EDX: 0x01f06520
    CR2: 0x0000001e, EBP: 0x0b8b3d58, ESI: 0xe00002ed, EDI: 0x02017e00
    EFL: 0x00010202, EIP: 0x1fbd8654, CS: 0x00000008, DS: 0x00000010
    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0xb8b3b88 : 0x128d08 (0x3cc0a4 0xb8b3bac 0x131de5 0x0)
    0xb8b3bc8 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc)
    0xb8b3cd8 : 0x19aeb4 (0xb8b3ce8 0x0 0xe 0x390048)
    0xb8b3d58 : 0x538d3c (0x311ec00 0xe00002ed 0xe00002ed 0x1f)
    0xb8b3db8 : 0x8ed0e0 (0x1f5e000 0x2017e00 0xe00002ed 0x1f)
    0xb8b3e68 : 0x8eda23 (0x1f5e000 0x30a2918 0x0 0x0)
    0xb8b3ec8 : 0x8eda77 (0x1f5e000 0x0 0x0 0x1fbd254)
    0xb8b3ee8 : 0x8e68d4 (0x1f5e000 0x0 0xb8b3f58 0x1fbd238)
    0xb8b3f08 : 0x39b3c3 (0x1f5e000 0x0 0x1 0x38169e)
    0xb8b3f58 : 0x39a595 (0x1fa8600 0x0 0x0 0x19e23a)
    0xb8b3f88 : 0x39a2cb (0x1fc03c0 0xb8b3fd4 0x134c09 0x135eb4)
    0xb8b3fc8 : 0x19ad2c (0x1fc03c0 0x0 0x19e0b5 0x2837458) Backtrace terminated-invalid frame pointer 0x0
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.AppleUSBEHCI(2.7.5)@0x8e3000
    dependency: com.apple.iokit.IOUSBFamily(2.7.5)@0x534000
    dependency: com.apple.iokit.IOPCIFamily(2.2)@0x59c000
    com.apple.iokit.IOUSBFamily(2.7.5)@0x534000
    Kernel version:
    Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386
    Message was edited by: ebedgert

    Perhaps try it again and see if it was just a bad alignment of the planets last time. You could also post more of the log to see which thread it was that actually crashed and what was happening. In the meantime this will keep you busy:
    [I got a black screen telling me I had to reboot in many languages, what was it?|http://www.dslreports.com/faq/4970] Also has detailed description of what happens during a KP.
    [Apple docs: What's a kernel panic? (Mac OS X)|http://docs.info.apple.com/article.html?artnum=106227]
    [Topic : kmosx: Kernel Panics? Don't panic too !|http://discussions.apple.com/thread.jspa?threadID=121923]
    [X-Lab: Resolving Kernel Panics|http://www.thexlab.com/faqs/kernelpanics.html]
    [Tutorial: Avoiding and eliminating Kernel panics|http://www.macfixit.com/article.php?story=20060911080447777]
    [Tutorial: An introduction to reading Mac OS X crash reports|http://www.macfixit.com/article.php?story=20060309075929717]
    [12-Step Program to Isolate Freezes and/or Kernel Panics|http://macosg.com/group/viewtopic.php?t=800]
    [Texas Mac Man's post on kernel panics|http://discussions.apple.com/thread.jspa?threadID=1723768&tstart=0]

  • 10.5.8 released, and please don't say it just damaged your reputation

    Link for people running 10.5.0 through 10.5.7:
    http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate
    Link for people running 10.5.7 (may differ in size from Software Update application version), also known as Delta Update:
    http://support.apple.com/downloads/MacOS_X_10_5_8Update
    With any update or upgrade release of any operating system, it is important remember the following cardinal rules:
    1. Backup your data. Backup your data. Backup your data. Get the gist? If you don't backup your data at least twice, you may find yourself without recourse if something wasn't tested with the operating system. There is always a chance something may not work.
    2. Dismount and disconnect the hardware that is not made by Apple. Some third party hardware may not be up to date with its firmware to be able to handle the update.
    3. Quit all open applications. Some applications may get surprised if the operating system is running changes under the hood, and not know how to react.
    4. Not always necessary, but repair permissions as preventive repair. Applications -> Utilities -> Disk Utility.
    5. Make sure your hard disk is less than 85% full. This arbitrary amount has been found to avoid most system slowdowns.
    6. Check the system requirements of the update.
    7. Check all your software installed, including drivers have been tested with the update. If it hasn't, don't upgrade your machine.
    8. Make sure third party system modification software is up to date before installing the update, or remove it until you can update the system first, and then install their update.
    9. Read the entire readme that came with the update. It should emphasize most of the points I've made.
    And above all, don't panic, if you hear others here have had trouble with the update, this is a help ward, and most people come here either to help, or to find help. People who have no problems rarely have reason to come in, except to help.

    .

  • Windows 7 gadgets not displaying properly. Black squares or don't appear at all with blue exclamation marks next to it.

    My gadgets on Windows 7 have suddenly stopped working properly since 2 days ago. I have tried:
    System restore
    UAC is ON
    cmd scannow (no results),
    tried the registry thing, didn't work either.
    How to fix this? 
    That's how it looks...
    http://i15.photobucket.com/albums/a360/Katjushka_/fuckedgadgets.jpg

    I do not personally recommend the alternate work-around of deleting any registry keys and/or reducing any of your internet security zones.  I have found fixes to it in a more secure way below, as I consolidated and cleaned up countless snips from many
    forums all over the place (cited sources of where I could remember I found the concepts); Here's my research notes: full disclaimers, hold me harmless, and always backup first!
    IE11 BUG:
    This bug in the public release version of Internet Explorer 11 (aka IE 11 aka IE11 RTM gold release) causes Windows 7 Gadgets to bug out.
    Specifically, with IE11 installed on Windows 7, due to a bug in IE11, increasing DPI past 110% triggers SOME of the Gadgets to glitch, bug out, completely disappear, etc.  This bug can be worked-around and "fixed" by modifying its Sidebar gadget.xml
    <autoscaleDPI>...  described in detail below.
    This bug is irrelevant to Windows 8 / 8.1 because Microsoft removed the beloved Gadgets entirely in Win8 due to so many third-party evilware writers embedding malware into their "free" downloaded Gadgets (note to the best of my current knowledge,
    using the standard Microsoft Gadgets included with Windows 7 are all perfectly safe).
    To reiterate, notice the following Microsoft article is only talking about potential malware in third-party downloaded Gadgets, and specifically I do NOT see where it mentions any problems using any of the official Microsoft build-in Windows 7 gadgets, cited
    from:  http://technet.microsoft.com/en-us/security/dn261332
    BUG FIX:
    Option 1: Set DPI back to 100% Smaller Fonts (default) or maximum 110% and the Gadgets come back to life and work fine upon relog.
    Option 2: If you need greater than 110% DPI, and want Gadgets to work, then... For each broken Gadget, modify its protected file:  gadget.xml   (as detailed below).
    FIRST, TEMPORARILY CHANGE DPI BACK TO 100% (DEFAULT) JUST SO YOU CAN SEE THE HIDDEN/GLITCHED GADGETS IN ORDER TO FIX THEM.
    Note as a side-effect, after the "fixed" Gadgets in question come back they may look smaller in comparison with the ones that were not affected by the DPI bug (because this fix locks their DPI at default 100% whereas your others are dynamically changed).
    Located in:  C:\Program Files\Windows Sidebar\Gadgets
    Inside that folder, find the glitched Gadget you want to fix, go into its specific folder, and edit its gadget.xml, Remove the following tag completely:
    <autoscaleDPI><!--_locComment_text="{Locked}"-->true</autoscaleDPI>
    Deleting that tag from the gadget.xml file resolves the issue even if the DPI is set to 125%. Setting the tag to allow autoscale doesn't help.  BE CAREFUL not to leave a blank line!
    Concepts:
    1. Make backup of effected gadget.xml somewhere
    2. Task Manager -> End Process of "sidebar.exe" to unlock all Gadget's files
    3. Take temporary ownership and give yourself RW permission to modify Gadget's files
    4. Put all Gadget file ownership and RW permissions back to "TrustedInstaller" for security
    5. Change DPI and relog to relaunch Gadgets
    Details:
    From Security Tab in Properties of file you want to change >>Click Advanced >>Select Owner >>Click Edit >>Click Other users or Groups >>Click Advanced >>Click Find Now, make yourself owner, then add write access for yourself.
    Launch NOTEPAD or similar editor as ADMIN, to modify the gadget.xml file (the folder structure itself is still permissions-protected, but I strongly suggest you leave that alone and just use admin for editing this one file this one time)
    Put Ownership and all permissions back to what they were (First, set read-only for everyone EXCEPT leave RW alone for the TrustedInstaller service, and THEN set Owner back to TrustedInstaller).
    NOTE: TrustedInstaller does not exist in the "visible" users and groups as it runs as an NT Service.  Don't panic. To restore its special ownership:
        Right mouse button click on the file and choose Properties
        Click Security tab
        Click Advanced button
        Click Owner tab
        Click Edit button
        Click Other User or Group and type in:  NT SERVICE\TrustedInstaller
        Search and click Ok on all dialogs until all property dialogs are closed etc.
    Cited from http://blogs.msdn.com/irenak/archive/2007/01/30/sysk-277-how-to-bring-back-the-trustedinstaller.aspx
    Double-confirm you set all regular users and groups permissions are reverted defaults back to what they were (read-only), and the *ONLY* Owner/RW is TrustedInstalled, to lock it back down for security reasons! E.G. to avoid future vulnerability!
    To test:
    I fixed my Clock gadget.xml but left the Calendar alone.  Changed DPI to 125% and relog off/on and notice Clock now works, but yes it looks slightly smaller than the working Calendar Gadget which isn't effected by this bug.  Repeat process for Calender
    if you want it smaller to match, but it works fine bigger. Repeat this process for all of your favorite broken Gadgets using IE11 on Windows 7.
    Notes:
    1.) Personally I view this as a work-around not a true fix, but considering Microsoft officially discontinued Gadgets as mentioned earlier, it's possible this bug may take a very long time, if ever, to be officially fixed.
    2.) IE11 also bugs out a lot of other things such as Outlook 2003 spellcheck, and other general software compatibility issues, especially in Windows 7, so it's probable that some or all of IE11's bugs should be eventually fixed in the future - thereby as a
    side effect may also officially fix Gadgets some day too.
    3.) Other concepts cited here: http://social.msdn.microsoft.com/Forums/ie/en-US/448f9665-c043-48d2-9049-b74131bab7b1/gadgets-not-working-with-ie11-win7-pro-sp1-not-win81-preview?forum=iewebdevelopment
    Good luck!

  • FTP install, Don`t pacnic, unable to downlaod packages.txt

    Hello everyone.
    I am trying to install Archlinux using FTP install from the last 'don`t panic' CD, but the installer is unable to download the file 'packages.txt' from any of the servers. I tryed to update pacman and to install again, but I got the same error again. What can I do to solve the problem. I just formated the hard drive and now I am using links from install CD to post the topic.
    Regards.

    Thank you, byte.
    I have no more CDs now I will have to wait till tomorrow. So it will and it is not possible to install arch using older CD`s, is that true. Or the problem is in me. I wanted to tune the base packages, not much, but I wanted to fill the power . As far as I know, that is not possible in the newest release of the install CD, and the setup is installing all the base packages, is that true again.
    Regards.

  • Newbie to apple forum - panic today,

    my iMac has SBBOD and black screen apart from when screensaver kicks in. Do I need to panic?

    You could try an SMC reset and PRAM reset:
    SMC Reset
    Shut down the computer.
    Unplug the computer’s power cord and disconnect peripherals.
    Press and hold the power button for 5 seconds.
    Release the power button.
    Attach the computers power cable.
    Press the power button to turn on the computer.
    Reset PRAM
    Shut down the computer.
    Locate the following keys on the keyboard: Command, Option, P and R.
    You will need to hold these keys down simultaneously in step 4.
    Turn on the computer.
    Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    Release the keys.
    Don't panic - yet.

  • I just got my iPhone 4s yesterday and I let the battery die and then I fully charged it . It has been off charging for 2 minutes and has already dropped to 98% all that I have done is reply to 2 texts

    So I bought my iPhone 4s last night and first thing I did was update to iOS 5.0.1 then inlet the battery die. It charged all night and was at 100% in just 2 minutes it drained down to 98% have I done something wrong? All I did was reply to two text messages. All my other phones wouldn't lose battery for a good 30 mins

    Give it a chance. It takes a while for the battery condition to find its feet.  And - just a personal hint - don't panic over a couple of percent on the battery readout.

Maybe you are looking for