How to install on a non-default drive.

I have a small solid state C drive which is now full.  All my images are on other drives.  How can I install CS6 onto a different drive and remove everything from my C Drive?

As they have an armv greater that armv6 you can download teh app from market or you can download it directly from: http://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/

Similar Messages

  • HOWTO: Create a Boot Configuration That Has No Driver Signature Checks. Disable Driver Integrity Checks and Install a Custom Non-Signed Driver

    Hello,
    Recently, I had a task where I needed to install a custom non-signed driver onto my Windows 8 64-bit setup. As it is known, Windows has driver enforcement policies that, as a security measure, do not allow you to install non-signed drivers.
    I did not want to alter my current boot configuration so I decided to create a separate boot entry that would have driver signing policies disabled. For some reason I did not find any good source that would contain a step-by-step instruction on completing
    this task, so I decided that I'd better share my experience here.
    Lastly, there are multiple ways how you could turn off driver enforcement policies, but I find the way to do this via boot manager.
    Here's how you can do that.
    1. Press WindowsKey and type 'cmd' (without quotes) to find Command prompt, then click Command prompt icon. If you have User Account Control turned on, hold Ctrl+Shift keys pressed when clicking the icon.
    This will force Windows to ask you for elevation of command prompt. Elevation is necessary for editing Boot Configuration Database (BCD), the database used by Windows boot manager to store boot settings.
    2. In the User Account Control window click Yes to confirm elevation of command shell.
    3. At the command prompt type
    bcdedit
    to list your BCD entries.
    This will give you an output like:
    Windows Boot Manager
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    integrityservices Enable
    default {current}
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    {a329b5ca-fb29-11e1-a74d-f2c962d62240}
    {a329b5c2-fb29-11e1-a74d-f2c962d62240}
    {current}
    {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    toolsdisplayorder {memdiag}
    timeout 30
    Windows Boot Loader
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8prowmc01.vhdx
    path \Windows\system32\winload.efi
    description Windows 8
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8prowmc01.vhdx
    systemroot \Windows
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    The section that starts with Windows Boot Manager lists current settings for the boot menu. Here you find what boot entry is chosen by default, this is the one what you will boot into if you do not select any boot entry in the
    boot menu.
    The following record
    default {current}
    indicates that by default my Windows boots into configuration which I use at the moment (currently booted Windows configuration).
    To find out what exactly is current configuration, look into the list of boot entries, records that contain boot loader configuration and are titled as Windows Boot Loader in the bcdedit output.
    For example, the entry shown above is one of my boot configurations. This is one of the boot entries listed on the boot manager screen when I start my PC and it looks like:
    Windows Boot Loader
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8prowmc01.vhdx
    path \Windows\system32\winload.efi
    description Windows 8
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8prowmc01.vhdx
    systemroot \Windows
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    This record has a unique GUID identifier that can be used to reference this boot entry, which is:
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    If we look at the Windows Boot Manager settings, we'll see this entry is the first in order to be displayed in the boot menu on OS start (I marked the unique bits):
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    It references my VHD drive, a virtual hard drive where my Windwos 8 setup is residing:
    device vhd=[D:]\win8prowmc01.vhdx
    And it also specifies that the boot manager must use UEFI BIOS extension code to access my Windows boot partition:
    path \EFI\Microsoft\Boot\bootmgfw.efi
    3. Now locate the current boot entry.
    Current boot entry contains boot settings used to boot into Windows configuration to which you are currently booted. It is referenced in the list of boot entries as a Windows Boot Loader record that has the {current} keyword inside and may
    look like:
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Because we are more than happy with current configuration and want to base our new boot configuration on these settings, we need to copy this boot entry ({current}) to a new boot entry.
    This is done by running the following command:
    C:\Windows\system32>bcdedit /copy {current} /d "No Driver Signature Check"
    Parameter /d here indicates that the following sequence of characters specifies the display name for the new boot entry that we are creating. The name inside the double quotes will be displayed in the boot menu when you boot your Windows.
    In other words, if you know restart your system, you'll see the new No Driver Signature Check in the boot menu.
    When copied, the entry is automatically given a new GUID identifier, so upon running the command above, you'll see the following line returned (you'll have an other GUID since these are unique identifiers):
    The entry was successfully copied to {a329b5d8-fb29-11e1-a74d-f2c962d62240}.
    4. Make sure the entry has been successfully created.
    Run the same bcdedit. (You may specify /enum or /v, or both /enum /v parameters at the prompt to get more detail about boot entries, but simple bcdedit is just enough to see the new entry):
    C:\Windows\system32>bcdedit
    Windows Boot Manager
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    integrityservices Enable
    default {current}
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    {a329b5ca-fb29-11e1-a74d-f2c962d62240}
    {a329b5c2-fb29-11e1-a74d-f2c962d62240}
    {current}
    {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    toolsdisplayorder {memdiag}
    timeout 30
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    The entry has been created and given a unique a329b5d8-fb29-11e1-a74d-f2c962d62240 ID. It now has exactly same boot settings as the boot entry we used to boot into current configuration of Windows.
    5. Modify created  No Driver Signature Check entry and specify that Windows must have driver integrity checks disabled when booted using this boot entry.
    Any modifications to boot entries are made using /set parameter. To indicate that we modify a specific boot entry, we must specify the GUID for the No Driver Signature Check record, which is:
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    In other words, to edit (add or change) an option for the boot entry, we need to use the following command syntax:
    C:\Windows\system32>bcdedit /set GUID <boot_option> [<option_value>]
    First, we must specify that we don't want integrity checks be made. This is done by adding the loadoptions option and setting it to DISABLE_INTEGRITY_CHECKS value:
    C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} loadopti
    ons DISABLE_INTEGRITY_CHECKS
    The operation completed successfully.
    6. Verify that load option has been added.
    Run the bcdedit command:
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    loadoptions DISABLE_INTEGRITY_CHECKS
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    7. Add the option that turns on test signing mode and disables checks of driver signature.
    Adding the testsigning option and setting it to ON does the trick for us:
    C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} TESTSIGNING ON
    8. Now we have a boot entry that enables Windows not to do integrity checks and digital signature validation.
    We check it by running bcdedit:
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    loadoptions DISABLE_INTEGRITY_CHECKS
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    testsigning Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    9. Type 'exit' without quotes to exit from command prompt, and restart Windows.
    Upon booting you will be present with a new boot option to start Windows in configuration that allows you to install custom non-signed drivers.
    Hope this will help anybody to create their own custom boot configurations.
    Well this is the world we live in And these are the hands we're given...

    Hi,
    Thank you for sharing the solutions & experience here. It will be very beneficial for other community members who have similar questions. 
    Regards,
    Kelvin hsu
    TechNet Community Support

  • Can Creative Cloud apps be installed on a non-boot drive?

    Can Creative Cloud apps be installed on a non-boot drive? If so, how? I want to install on a different drive on my current system because my boot drive (an SSD) is rather full.

    Since I have an SSD drive with rather limited capacty, I did this, and it sort of worked. The Creative Cloud did not give me an option of where to install it. As soon as it installed, I did as instructed above and changed the default. However, Photoshop started installing immediately after I installed the Creative Cloud and did not ask if I wanted to install it. However, it installed correctly in the drive I stipulated in preferences. Photoshop did not install a shortcut onto my desktop, but I had to create one manually.
    I noticed that certain items still installed on my SSD. There is an Adobe folder under Programs on the C drive, and there is also an Adobe folder in my SSD under Users.
    The only other place I discovered to direct files is in the Photoshop preferences for where to store my scratch files.

  • How to install ovi suite to a drive other than C:?...

    how to install ovi suite to a drive other than c:??? my c: drive is almost full with other partitions perfectly free to install it, how do i do that? can i use previous versions of ovi suite to use with my e63? at this point, i'm unable to use ovi suite at all, because there's no room to install it on my c: drive.
    allllllllso there's one more thing, when i originally had tried installing ovi suite on my computer i had more than 1gb free. after installing it i on'ly had 500mb free. i had only intended for it to use a very small amount of space, and since i also use my c: drive for virtual memory i quickly uninstalled it, looking for an option i'd maybe skipped over while installing it the first time. no luck. anyways, when i looked in the add/remove programs control panel the installed size of ovi suite was only 40-50mb. even after uninstalling ovi suite the extra memory space that seemed to all of a sudden taken up by the installation stayed used.
    when looking at the file sizes of everything on my hard drive, (including system files and paging file) there is still a descreprency between the amount of memory used and the size of all files total on the drive. at this point im quite disgusted and disapointed in ovi suite as i'm mostly unable to use it to connect my phone to my computer and i'm also having problems with the CA101 cable as well. i guess i'll have to go check for another cable.
    nokia!!! wake up and fix yo **bleep**!!!!
    anyone have any solutions for the main problem? (installing to a drive other than c? is there support for this option in any of the new beta versions? can that be included in the newest betas? i'm suuuuuure i'm not the only one begging for this option!!!

    Hi ostrenga4, sorry to hear about your experiences.
    When installing Nokia Ovi Suite to PC, Windows makes "system restoration points", which are available to restore operating system to previous condition, if something goes wrong, for example in driver installation.
    You can change install location of Nokia Ovi Suite with following:
    - Download Nokia Ovi Suite install package from Nokia Ovi Suite pages
    - Start Windows Command prompt
    - From Command prompt, navigate to folder containing Nokia Ovi Suite install package, which you downloaded
    - Start Nokia Ovi Suite install package with command line "Nokia_Ovi_Suite_webinstaller.exe /TARGET="D:\TestDir\Test"
    - This results, that Nokia Ovi Suite installer creates folder D:\TestDir\Test (if that doesn't exist) and installs Nokia Ovi Suite there.
    - Unfortunately, Windows Installer still keeps installer cache files and system restoration points in C: drive (or whatever your system drive is)
    As you can see, this is possible, but it is very much recommend to have enough space for installing software into system drive.
    Cheers, Samuli

  • How to install PC companion on other drive?? (My SSD on C: only have 5gb)

    Im using PC companion for Xperia ZL.
    How to install PC companion on other drive??  (My SSD on C: only have 5gb)
    PC companion v2.1 dont ask to install the soft on a drive! lol!
    Its standard any application setup, in the world, offer you a path or drive to choose to install.  Why Sony not add this in the setup?

    Not true - If a program needs to download files to perform certain tasks then it will only install to the C: drive so as in this case when you perform system updates or system repairs the firmware files are downloaded to the root ie: C: drive
    For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled.   Richard P. Feynman

  • How to install AIR in Non-Admin rights PC ?

    Who can teach me how to solve under issue ?
    1.How to transfer AIR file to exe file
    2.How to install AIR in Non-Admin rights computer?
    -->In my company all PC has contorled, i want to install application in any Notebook for Sales Using,they can using AIR offline in anywhere
    Thank you so much!!

    On Mac OS, to install or update an AIR application, the user needs to have adequate system privileges to install to the application directory (and administrative privileges if the application needs to update the runtime). On Windows, a user needs to have administrative privileges.
    IT administrators can install AIR applications silently using standard desktop deployment tools. For more information, see "Enterprise deployment" in the following page:
    http://help.adobe.com/en_US/AIR/1.5/air_admin/WS5b3ccc516d4fbf351e63e3d11c0f5986ec-8000.ht ml#WS5b3ccc516d4fbf351e63e3d11c0f59823a-7fee

  • How to install a samsung clp 310 driver in the time capsule

    how to install a samsung clp 310 driver in the time capsule ?

    You do not install the printer driver on the Time Capsule, you install it on your Mac.
    Check with Samsung Support for details on how to download and install the driver to your Mac.
    Then use System Preferences > Print & Scan to see if your printer is compatbile. Not all printers are compatible with the USB port on the Time Capsule, so if your printer does not appear, it ls likely not compatible for this purpose.

  • How to install SAPOSCOL in non-sap server ?

    Hi,
    Please advise how to install SAPOSCOL into non sap system ? any related document / help ?
    Thank You and Best Regards
    Fernand

    Hi,
    The reason why, i want to install saposcol and sapagent in non sap system because i want to monitoring this serve with system monitoring.
    Finally, i can install with install.cmd from this notes : 704349
    Thank You and Best Regards
    Fernand

  • HOW TO install RAID/ AHCI 975x PUE Driver Guide

    As below on how to install the matrix driver, there is no 'how to install on a system not already preconfigured with raid/AHCI'. This driver creates a F6 Floppy disc, why? because windows will  not recognise your hard in AHCI mode without the driver installed. This is why we get a reboot with AHCI enabled. It gets to a point then when windows loads with no driver it reboots. If you try to load the driver first, the hard ware has not been enabled so there is nothing to install. Reinstall Windows is the only way.
    * 5.  INSTALLING THE SOFTWARE
    5.1 General Installation Notes
    1.  If you are installing the operating system on a system
        configured for RAID or AHCI mode, you must pre-install
        the Intel(R) Matrix Storage Manager driver using the
        F6 installation method described in section 5.3.
    2.  The 'Intel(R) Chipset Software Installation Utility'
        must be installed on the system after a supported
        Microsoft* Windows* operating system has been installed.
    3.  To install the Intel(R) Matrix Storage Manager,
        double-click on the self-extracting and self-installing
        setup file and answer all prompts presented.
    4.  By default, all installed files (readme.txt, help, etc.)
        are copied to the following path:
        <bootdrive>\Program Files\Intel\Intel(R) Matrix Storage Manager
    5.2 InstallShield* Installation from Hard Drive or CD-ROM
    Note: This method is applicable to systems configured for
          RAID or AHCI mode.
    1.  Download the Intel(R) Matrix Storage Manager setup file
        and double-click to self-extract and to begin the setup
        process.
    2.  The 'Welcome' window appears. Click on the Next button
        to continue.
    3.  The 'Uninstallation Warning' window appears. Click on
        the Next button to continue.
    4.  The 'Software License Agreement' window appears. If you
        agree to these terms, click on the Yes button to
        continue.
    5.  The 'Choose Destination Location' window appears.
        Click on the Next button to continue.
    6.  The 'Select Program Folder' window appears.  Click on
        the Next button to continue installing the driver.
    7.  If the InstallShield* Wizard Complete window is shown
        without a prompt to restart the system, click the Finish
        button and proceed to step 8. If it is shown with a
        prompt to restart the system, click 'Yes, I want to
        restart my computer now.' (the default selection) and
        click the Finish button.  Once the system has restarted,
        proceed to step 8.
    8.  To verify that the driver was loaded correctly, refer
        to Section 6.
    5.3 Pre-Installation Using the F6 Method
    Note:
          The Steps 1 and 2 can be skipped if you use the F6 Floppy
          disk utility provided by Intel. This utility can also be
          downloaded from the following website. These methods
          are applicable to systems configured for RAID or
          AHCI mode.
    http://downloadfinder.intel.com/scripts-df/Product_Filter.asp?ProductID=1809   
    1.  Extract all driver files from the installation package.
        See Section 7.2 for instructions on extracting the
        files.
    2.  Create a floppy containing the following files in the root directory:
        iaAhci.inf, iaAhci.cat,
        iaStor.inf, iaStor.cat,
        iaStor.sys, and
        TxtSetup.oem.
    3.  At the beginning of the operating system installation, press F6
        to install a third party SCSI or RAID driver.
    4.  When prompted, select 'S' to Specify Additional Device.
    5.  When prompted, insert the floppy disk you created in
        step 2 and press Enter.
    6.  At this point you should be presented with a selection
        for one of the following depending on your hardware
        version and configuration:
        - Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)
        - Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)
        - Intel(R) 82801FR    SATA RAID Controller (Desktop ICH6R)
        - Intel(R) 82801FR    SATA AHCI Controller (Desktop ICH6R)
        - Intel(R) 82801FBM   SATA AHCI Controller (Mobile  ICH6M)
        - Intel(R) 82801ER    SATA RAID Controller (Desktop ICH5R)
        - Intel(R) 6300ESB    SATA RAID Controller
    7.  Highlight the selection that is appropriate for the
        hardware in your system and press Enter.
    8.  Press Enter again to continue. Leave the floppy disk in
        the system until the next reboot as the software will
        need to be copied from the floppy disk again when setup
        is copying files

    Well I went for it, RAID that is. I borrowed a 300GB SATA II Seagate Barracuda from work to backup to and got started. I shall layout how I did it for those having trouble.
    So my old config was Maxtor SATA II 80 DiamondMax system drive and a Maxtor SATA I 250GB DiamondMax for Data. Now with the 300GB SATA II to backup to and running in IDE mode enhanced with speed disabled in bios. HDTach benchmarking is in above posts for these drives.
    I copied all that data I wanted to extra drive and made a boot floppy and copied the files from the 975xPUE CD for the Intel RAID controller.
    CDROM:\IDE\Intel\ICH7R\Floppy\32
    Now I shut down my system, removed the bachup drive and entered the bios.
    *I set back all my setting to default, no overclock.
    *Integrated peripherals/Onboard JMB361 mode: Disabled JMicron controller
    *Intergrated peripherals/SATA Devices Configuration/SATA Mode/ Set to RAID,
    *SATA Port Speed/Disabled.
    *Set system to boot from CDrom.
    I put in my floppy and the XP CD and rebooted, CTRL +I to enter the Intel RAID setup and first thing I found out was that with my 80GB and 250GB drives in a RAID 0, I was getting 152GB of a logical drive. So I setup the RAID and rebooted.
    80GB+250GB=152GB RAID 0 (I have about 200GB backed up, so I going to have to get another drive, SATA II 300 maybe)
    Now the system booted off the XP CD and as it started to load, it read the floppy and I DID not press F6. I noticed that just before the setup screen the system loaded the driver automatically from the floppy. And low and behold it recognised my hard drive 152GB and I kicked off the install.
    * Note: After Setup had finished formatting the partition, the system loaded the drivers from the floppy again and then started copying files from the CD before restarting to boot from the hard drive. So if you had already removed the floppy, the drivers for the Intel RAID controller would not be loaded and the second stage of install would never get started, blue screen or not recognise you hard drive.
    The rest of the install went very quick and I installed all the drivers and NOW for the juicy bits.
    Ok so I thought, how am I going to read my backup drive which is IDE/SATA on my system if it is in RAID. So I connected the drive to the Jmicron SATA port 5 enabled the JMicron controller in the bios and set it to IDE.
    *NOTE: After I  rebooted the Intel RAID had reverted back to IDE so I had to go back into the bios again and set it back to RAID. When I rebooted I got the Intel RAID slash screen and then the JMicon one showing me the 300GB and asking my to press a button to continue. Quite abit of extra startup time with both enabled.
    Windows loaded fine and both my C: 152GB RAID 0 and D: 300GB were there, but the 300GB was showing as a removable device! I know there is a reg fix for that somewhere.
    Benchmarking: This is the best bit!
    Maxtor Diamond 80GB SATA II and 250GB SATA I = 150GB Logical RAID 0 test with HDTach 3, 8mb test:
               Burst Speed : 320.9 mb/s
               Average Read : 120.3 mb/s
    Now that is some difference from IDE enhanced so well worth the effort!
      IDE:        Burst Speed: 215.3mb/s
                    Average Read: 59.0mb/s
    Now I also tested the Seagate 300GB SATA II drive which is connected to the JMicron controller in IDE mode and the results show that the JMicron does not support SATA II drives but maxes out SATA I: so even if I do buy and extra drive will I be able to add it to the RAID 0 or will I be stuck with SATA I speeds on the JMicrom controller. No doubt I will soon find out.
      Seagate:  Burst Speed: 150.5 mb/s
                    Average Read: 50.5 mb/s
    Thanks for the tip Insomniac34
    Gaucho

  • How to install apps to another hard drive

    I have a late 2012 iMac 21.5 inch.  I boot from an external solid state drive.  However there are apps I would like to install to the internal hard drive.  Whenever I install an app from the app store it by default installs to the boot drive.  I am slowing running out of room on the SSD.  When I move the app to the internal drive, I can't seem to be able put it back on the launchpad or dock, I can only launch from Finder.
    Any ideas how to get things to install the internal drive by default, or

    Well, an USB HD is useless with a PPC computer because you can't boot with it. So, installing OS X onto it is an exercise in futility. Return it for one that has FW or get another one. Amazon is offering an ext enclosure + 1 TB Seagate for $130 USD at http://www.amazon.com/Macally-G-S350SUA-Hi-Speed-FireWire-Enclosure/dp/B000P1NAM O/ref=pdbbs_sr1?ie=UTF8&s=automotive&qid=1240278380&sr=8-1

  • How to install Creative Cloud on any drive other than my System drive...

    You are now chatting with 'Bhagawan'
    Bhagawan: Hello. Welcome to Adobe Technical Support.
    Bhagawan: Hi Steve
    Steve: It appears CC installs on my system drive without asking me. The way I manage my system - this is not acceptable. So, how do I install on the drive I install all my other apps?
    Bhagawan: I understand that you want to install Creative Cloud desktop app. Am I correct?
    Steve: On a particular drive - not my system drive.
    Steve: CC, Photoshop, etc.
    Bhagawan: I will be glad to check and help you with this issue.
    Bhagawan: Steve, creative cloud desktop app can be install only on C drive, but other apps you select for other drive.
    Steve: My C: drive is dedicated to my OS only.
    Steve: It is a special drive that will not work for very long if software companies put their programs on it till it fills up and then everything stops.
    Steve: Didn't Adobe think of this?
    Steve: I have one computer that only has a few MBs left of C:. What do I do on that computer?
    Steve: "left on C:"
    Bhagawan: Give me a minute.
    Bhagawan: Thank you.
    Bhagawan: Steve, I'm really sorry, creative cloud desktop app will be installed on C Drive, since the operating system is installed, but other Creative Cloud apps can be installed other Drive and depends on file size.

    I had the same problem and finally solved it.
    It is "funny" that CC doesn't ask you where to install apps. Or better to say, it asks you but doesn't care. In Creative Cloud desktop app/Preferences there is option to choose where you want apps to be installed, but they are still installed in C:/Program Files/....
    How to install apps on secondary drive in just 3 steps:
    1. Go to page Adobe CC 2014 Direct Download Links – Creative Cloud 2014 Release | ProDesignTools and download all apps that you will need.
    2. Once downloaded, install it. During installation you will be asked where you want app to be installed (just like in any other "normal" installation)
    3. Be happy
    Hope I helped
    Marko

  • How to install ovi suite to D drive?

    How to install Ovi Suite to the D drive?
    The installer does not offer any options. -SS.
    My C drive is full and there is not enough space for the humoungous Ovi suite. As a matter of my personal policy, I never install any application to my C drive. I have created a separate D partition expressly for installing applications.

    You can change install location of Nokia Ovi Suite with following:
    - Download Nokia Ovi Suite install package from Nokia Ovi Suite pages
    - Start Windows Command prompt
    - From Command prompt, navigate to folder containing Nokia Ovi Suite install package, which you downloaded
    - Start Nokia Ovi Suite install package with command line "Nokia_Ovi_Suite_webinstaller.exe /TARGET="D:\TestDir\Test"
    - This results, that Nokia Ovi Suite installer creates folder D:\TestDir\Test (if that doesn't exist) and installs Nokia Ovi Suite there.
    - Unfortunately, Windows Installer still keeps installer cache files and system restoration points in C: drive (or whatever your system drive is)
    Please THANK me by clicking on the ****WHITE STAR** ( Giving KUDOS) the big GREEN BOX to your LEFT .
    It will help me to serve you better !!!!!
    Thanking You

  • NB100 - How to install Windows 7 without CD drive

    Hi. I wondering if some one knows how to install Windows 7 whit out a CD player.
    I have an external HDD.
    Is it posibel to do a image on that one to boot from?

    I'm typing this on an NB100 (Upgraded to 2GB of RAM) running Windows 7 RC .
    Make sure to update your BIOS to the latest version (1.9 I think) and then you can mount the Windows 7 .iso as a virtual drive using Daemon Tools in XP and run it and do a clean install.
    Windows 7 will back up all your documents, music, videos etc in a folder called Windows.old and it will find all the new drivers you need all by itself (at least it did for me). If I remember correctly the only one I had to install again was the Bluetooth Stack.
    All the Toshiba drivers and manuals etc will still be on your hard drive too, I think they're all stored on a small separate partition, which I think is pretty neat.
    It took me a while cus I did as much research and reading up as I could beforehand but in the end it was really easy. Shouldn't take you more than an hour really.
    Windows 7 is also running pretty damn well too. The only problem I have is that sometimes the taskbar disappears after the screensaver has been running, but a friend of mine is having the same problem on his Samsung netbook.

  • How to install Leopard on external Hard-drive

    hi can somebody tell-me how to install Mac OS X 10.5 on to my external Hard drive????

    Well, an USB HD is useless with a PPC computer because you can't boot with it. So, installing OS X onto it is an exercise in futility. Return it for one that has FW or get another one. Amazon is offering an ext enclosure + 1 TB Seagate for $130 USD at http://www.amazon.com/Macally-G-S350SUA-Hi-Speed-FireWire-Enclosure/dp/B000P1NAM O/ref=pdbbs_sr1?ie=UTF8&s=automotive&qid=1240278380&sr=8-1

  • How to install Adobe printer's 'postscript driver' in mac os x

    hello again,
    as posted recently hv a problem with adobe printer's postscript driver (ppd),In Indesign cs4 It shows ppd is missing while making Print File(.ps),
    pls suggest how to install ppd again, i tried to install ppd driver downloaded from adobe website, but it fails to install.
    pls help.

    I guess you didn't read the link I gave you inthe other thread...
    Here's one of the comments that you would have found:
    Short description to the workaround Solutions
    1) Usual workaround for printing with Distiller under SL and InDesign CS4:
    Copy the PPD called “ADPDF9.PPD” (download-link here in this topic) to Library/Printers/PPDs /Contents/Resources/en.lproj
    Works for CS4. Problem: Does NOT work for CS5.
    2) Workaround for InDesign CS5:
    - Go to Applications/Adobe Indesign CS5/Presets
    - Create a folder called “PPDs” (attention: foldername is case-sensitive!)
    - Copy the PPD called “ADPDF9.PPD” (download-link here in this topic) into this folder.
    - PostScript Printer will be useable within InDesign CS5
    Hope that helped and clears up all questions so far.
    Cheers, hi2hello

Maybe you are looking for