Dual Boot SnowLeo-Leopard from FireWire Drive doesn not work!

Hello,
I start SnowLeo 10.6.1 from my iMac (upgraded from previous running Leopard OSX) and added a Lacie d2 1Tb Firewire 800 external drive where I want to install OSX 10.5.
By beginning of the install the computer just restarts several times without giving the option to complete the install.
No way to use the Option Key while booting!
I created a single partition on the new drive and inizialized it with the Master GUID Tablefile option for Intel Macs booting volume.
I tried then to do the same thing on a minimac running OSX10.5 and it works!
Thanks for helping

As far as I know, external hard drives do not need drivers - they should just work.
Have you thought of doing this a totally different way:
make sure internal HD is running well and without problems (run Disk Utility or Disk Warrior and repair permissions) and then make a bootable clone on your external using SuperDuper or CarbonCopyCloner? That is, after you use Disk Utility to partition (and, in the process, erase) the external drive.
After the process is finished, test to make sure it works.
I've used this method and it works for me; if you wish or need to start up from the external, either choose it in System Preferences -> Startup disk or hold down option key while booting.

Similar Messages

Can't boot snow leopard from external drive

I have a copy of snow leopard installed on a separate usb hard drive which I use to run some PowerPC programmes under rosetta. I can attach this USB drive to my Mac Pro and also to an Intel Macbook and choose to start up on this external drive without any issues. However when I try restarting my new 2011 iMac on this external usb drive the machine crashes every time with a kernal panic. Is this problem unique to me or does everyone else have this issue with new iMacs. Mine is a 27" 3.4ghz i& with 12ghb ram installed running 10.72. Is their soemthing I can do to resolve this problem?

I have now solved the problem of being able to boot from either Snow Leopard or Lion on a new Mid 2011 iMac. This is how I did it.
1. Attach an external USB drive to an earlier Mac or borrow one from a friend. In my case I used my 2009 Unibody Macbook (which has Lion installed on it but does allow you to install Snow Leopard on an attached device) Put the Snow Leopard install disc in this machine and tell it to install Snow Leopard on your attached USB Drive.
2. Start up the Macbook (or whatever machine you are using) and get it to restart on the attached USB drive so that it boots up in Snow Leopard. Then when Snow Leopard is up and running on the attached external drive, do a software update to bring it up to 10.68 (the current version). This step is important as I found that if I plugged in the external USB drive into the iMac with only operating system 10.6 installed it would cause a kernal panic on start up when I choose to start up on the external USB drive.
3. With Snow Leopard updated to system 10.68 you can now plug it into your iMac and restart the iMac booting into Snow Leopard from the external USB drive. You do this by either going to System Preferences>Startup disk and choosing the external drive, or by holding down the option key when you restart your Mac and choosing the external USB drive.
4. The next step is to make your iMac dual boot now that you know it can run Snow Leopard successfully from an external USB drive. To do this, go into Utilities>Disk Utility and select your main drive. Select the main disk (with Lion on it) and then choose Partition and choose 2 Partitions. Drag the first partition bundary line down to make the second partition size as small as possible. In my case I had a stock 1TB drive and the smallest partition size it would allow me was 70gb. Create the second partition (assuming you have spare space on your drive to allow this to happen). This will then create a second hard drive icon on your desktop. I renamed mine "Snow Leopard startup".
5. Download the free (and excellent) utility Carbon Copy Cloner and use it to copy your Snow Leopard operating sytem from your attached USB external drive to your new partition.
6. That's it! Now you can choose to start up your iMac from either Lion or Snow Leopard using either method mentioned in 3 above.
7. As a final step I suggest your install your Rosetta only programmes in your new Snow Leopard partition so that you can access them easily and keep them all together.

Can't boot Snow Leopard from USB drive made in Yosemite

Hi all,
I have a brand new macbook pro running Yosemite, but some of the software I have will only run in Snow Leopard.
Running Snow Leopard as a Virtual Machine has been clunky, so I wanted to try an alternative and install Snow Leopard onto an external HD and work from that.
I got hold of the Snow Leopard dmg file and created a bootable USB thumb drive (I did this within Yosemite) to try to install it onto the external HD. I used the instructions here:
http://www.maciverse.com/installing-snow-leopard-onto-an-external-hard-drive.htm l
But when I restart the computer and try and boot from the USB drive, I just get the grey background with dark grey apple symbol, indefinitely. The installation process never commences.
What am I not doing right?
Thanks in advance for any insights.

You can only do what you are trying from a model that can be booted into Snow Leopard. You have a 2014 model that can only be booted by Mavericks or Yosemite. You cannot run Snow Leopard on your machine except in a VM or a Mac from 2010 or earlier.

Booting from firewire drive does not recognize existing users.

Hello,
I just bought a Lacie firewire drive to have a bootable backup of my Macbook internal drive.
I used SilverKeeper 1.1.4, that comes with the drive, to make a bootable copy.
The copy is bootable but when Tiger startus up fro the firewire drive I get the presentation video and am asked to setup the system including creating a new user.
It is as if the existing Users directory, that was copied, is not recognized by the clonned system.
Running Tiger 10.4.11
Any ideas?
Joaquim

I think this was driver issue

Macbook Pro recent update to Snow Leopard now disc drive doesn't work??

I just updated my Macbook Pro to Snow Leopard 10.6.8 now my disc drive won't work at all! I've read a couple forums here that show everyone had this problem back in 2009 when I guess this first came out...great. How do I fix this? It appears to be a software issue. If I upgrade to mavericks will this fix it? Although I also see that makes your computer very slow! Ugh I need help please!

Two things to try:
1. SMC reset, Directions are here - note the steps are different depending on whether or not the battery can be removed by the user:
http://support.apple.com/kb/ht3964
2. NVRAM / PRAM reset:
http://support.apple.com/kb/ht1379
These steps are worth trying, although the problem may be deeper.
Please post back with your results.

Boot Snow Leopard from Thumb Drive in Single User Mode on Macbook Air

I'm trying to boot from a thumb drive that I transferred the Snow Leopard .dmg on. My macbook air only lets me get into single user mode. Every time I try to boot or enter safe mode or regular mode, the Macbook Air shuts down.

I do have the installation media on my usb flash drive. I'm sure it's leopard, and the problem is that I cannot get passed the apple logo on boot. The laptop turns off after trying to finish the boot for twenty seconds. However, I can get into single user mode. I just can't seem to install the media in single user mode due to my lack of know how.

Intermittent firewire drives,dvd not working,other tales of woe

hi,i have a macally 160gb hard drive thing on fw 400 that only shows up on something like 1 time out of 20 on my PowerBook running 10.4.6.It quite happily shows up on my iBook running 10.3.0 without fail every time.also i tried a target disk mode from the iBook to PowerBook and the iBook did the firewire symbol on its screen but did not show on the PowerBook.My 3rd gen iPod shows up 4 times out of 10 on my PowerBook via FW so its not as far as I can tell a hardware fault with the FW slot on the PowerBook.I just tried resetting nvram which worked for the first time the PowerBook was restarted but ejecting the hard drive and replugging into the PowerBook it took a further 5 times to show up on the Powerbook again.Other odd behaviour at the moment is the PowerBook refusing to read dvds just giving me the "this disk is unreadable by this computer-ignore or eject"message.I've got a horrible feeling it's software reinstall time but i've only got the original version of 10.4 and a dialup connection so getting back up to 10.4.6 is going to be an impossibility for now.If it's any help the last thing i installed on the PowerBook was 10.4.6.about 4 weeks ago and that I downloaded at work to disk thanks to a broadband connection.As for the iBook it's back after a years holiday thanks to a cracked screen that i was quoted £400 to replace-i eventually found a replacement thanks to ebay uk for £20 and fitted myself today.Its great to have 2 macs again but i do have a light patch running down the centre of the screen where everything appears slightly lighter.
Please help......

Have you tried running FireWire Target Disk Mode the other way? Start up the PowerBook in TDM and hook it up to your PowerBook to see if it recognizes it reliably. If not, I'd say it's got to be some kind of hardware issue, perhaps a loose connector or other fault.

My iMac (late 2006) no longer boots from FireWire drives, although they contain all the system files.

My iMac (late 2006) no longer starts (boots) from Firewire drives, although they all contain a current system (Mac OS X 10.6.7). If the drives are connected with USB 2, they boot normally. The FireWire drives appear in the Start Volume program, but they do not boot. If I press and hold the Alt key while booting, only the internal drives and the USB drives appear as options. What can I do in order to boot from FireWire drives as I always could in the past?

I'd first recommend doing a SMC reset and if that doesn't work refer to:
http://reviews.cnet.com/8301-13727_7-10333969-263.html
and
http://www.thexlab.com/faqs/firewiretroubleshooting.html
SMC RESET
Shut down the computer.
Unplug the computer's power cord and all 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.
PRAM RESET
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.
Roger

T400s Linux/Windows dual boot with Linux from Esata Flash Drive

This project is about a dual boot Windows/Linux system without using the normal dual boot changes in the bootloader of the windows hard drive. When I started this I found bits and pieces of information on the web but no complete description so I wrote this post.
I have done a dual boot system on my previous Thinkpad where I had partitioned the hard drive between Linux and windows. For this project I wanted to leave the windows hard drive absolutely intact and unaltered, and boot Linux from a flash drive in the esata port on the back of the T400s. Obviously this uses the F12 boot list function key to boot from the flash. The advantage of this is that Windows is totally unaltered and when I need Linux, I plug in the esata flash drive, hit F12 during the boot cycle and select booting from the esata flash drive. The reason for Esata rather than USB is simply speed. I have a nice fast Linux installation.
I used the OCZ esata flash drive but suspect any of the alternatives will work. It did not need the accessory usb cable because the Thinkpad powered the esata flash directly.
To boot from the esata drive I had to make the following changes in the bios
    I left the esata flash plugged in as I went into the bios
    Bios>config>Serial ATA and changed the Sata controller mode option to compatibility
    Restart and back into the Bios
    Bios>startup>boot - in my case the esata flash drive showed up as ATA HDD2 and was excluded from the boot order so I had to un-exclude it and move it to the point in the boot order that I wanted.
Next I downloaded a linux installation iso and put it on a CD - in my case opensuse. Then booted from the CD
From now on this instructions are specific to opensuse and yast but can be generalized to whatever Linux is being used.
In my case yast came up with a good set of suggestions for automatically partitioning the flash drive but then crashed during the partitioning itself. So I rebooted and specified the partitions manually.
    A fat32 partition left as a partition which both windows and Linux could see (in my case about 20% of the drive) (/dev/sdb1)
    An extended partition with the remainder of the drive (/dev/sdb2) which contains the following logical partitions
    A linux Swap partition of 2GB (/dev/sdb5)
    A linux /home partition –the remainder of the drive (/dev/sdb6)
    A linux /root partition of 8GB (/dev/sdb7)
Yast automatically suggested mount points of C,D,E for the windows partitions. Unfortunately because of the way the Thinkpad hard drive was laid out Yast had C assigned the ThinkPad Service partition and D assigned to the SW_Preload (or main windows partition). However there was an edit function that allows for the reversal of those mount points so that the windows C drive is mounted in Linux as Windows/C thereby avoiding confusion. I had already backed up and removed the Thinkpad factory install data so I did not have to deal with that. Yast suggested Windows/E for the mount point of the FAT32 partition on the flash drive, which I accepted.
The yast install configurator made all this manual selection easy, and after the manual configuration the partitioning worked perfectly.
Next step was Linux user configuration which went fine
Next was booting.
In the section management tab
    delete the windows 1 and 2 options (since we are not dual booting directly)
In the boot loader installation tab
    uncheck boot from mbr ( this stops the install from installing Grub and dual boot on the windows c drive
    check boot from root partition (this installs grub and all associated files in the Linux root partition (/dev/sdb6)
I believe that the correct procedure at this point is to click Boot Loader installation details which will bring up the Grub device map. In the device map there will be a line for the fixed hard drive (aka the windows drive) and a line for the esata flash drive. When the installer started up these were in hard drive and esata drive order. However when we boot directly from the flash the esata drive will be grub drive hd0 and the fixed hard drive will be grub hd1. The device map order needs to be changed to reflect this ie the esata drive should be first not second.
I did not do this and ended up initially doing Grub command line editing to boot and later manually editing the grub files using information I had previously learned the hard way and through google.
At this point let the installer go ahead and install Linux. After doing this it should come back and tell you to reboot. Do not do it yet because we need to install the MBR into the flash drive.
I suspect that there is a way of doing this in Yast running from the Live CD but it was not obvious to me so I used the manual method that I have used before.
Open a root terminal
Mount /dev/sdb6 to /mnt/sdb6 (my linux root)
Touch /mnt/sdb6/boot/grub/flag
The purpose of this is when we go looking later at the grub command prompt we need an easy to find unique file
Start grub and do the following
#grub
            grub> find /boot/grub/flag
                (hd1,5)    -- the result of the find in my example
            grub> root (hd1,5)   -- using the result of the find in my example
            grub> setup (hd1)   -- install mbr -- my example parameters - if you get this wrong you will trash some other drive!!!
                  hopefully grub announces success
            grub> quit
Reboot and select the flash drive. In my case I still had the grub devicemap wrong and had to edit the grub commands during boot to tell grub how to find the correct partition and then edit them again after booting
Typical linux install issues that we all always seem to have and can be solved with a little (or a lot of) google research.
As I said at the beginning I now have an untouched windows installation and a nice fast Linux installation. I hope that this will be of some use to someone.

Hi chrissh
i tried this exact procedure... on the exact same notebook (T400s). However, as soon as I set the
   Bios>config>Serial ATA to "compatibility", I cannot use my default Windows installation! I immediately get the "blue screen of death".
I doubt I did anything differently since this is the first step of your procedure and my laptop is brand new!
any idea?

Booting from FireWire Drive

I have a LaCie 160MB (F A Porsche style) external firewire drive.
I have been able to create a bootable clone of my iBook HD using Disk Utility and the Restore function.
I have been able to create a bootable partition by installing the System Software onto it.
But I have not had success using SilverKeeper or SuperDuper! Does anybody know why? I would really like to use the features of one (or another if available) of these applications.
Thanks.
-Ted

Below is LaCie's Tech Support Reply. What is interesting is that they suggest Carbon Copy Cloner (instead of Silverkeeper). Also interesting is that it worked. I hope this helps some of you.
Ted
Hi Ted--
Thanks for contacting LaCie Technical Support. All of our firewire
drives can be used as boot volumes. Due to differences in operating
systems and Macs, we are unable to provide support for booting from
firewire drives other than the following information:
1. Make sure the Mac is bootable via firewire. All Macs with built-in
firewire can be booted from an external drive except:
-Blue and White G3s
-PCI-Graphics G4s. This can be determined by looking in the Apple
System Profiler. The PCI Graphics G4s use the same motherboard as the
B&W, except with a G4 processor shoehorned in.
2. The drive must be connected to a native port. It will not work if
the drive is connected to an add-on card.
3. The Mac must have the latest firmware installed. The proper updater
can be found and downloaded from here:
http://docs.info.apple.com/article.html?artnum=86117
Download and read the instructions carefully. It is possible to kill a
Mac if the update is interrupted. Then, perform the update. If the
firmware is already current, the updater will report this.
4. Format the drive fresh using either Apple's Disk Utility in OS X or
Silverlining in OS 9. Use the Mac OS Extended (HFS+) format only.
(Journaling may be enabled on OS 10.3.)
5. If making an OS 9 boot drive, you can just copy the System Folder
over to the root of the boot volume. To be bootable, the System Folder
must be blessed, i.e. has a happy Mac face on it. If it does not, you
can try to force it to bless by removing the Finder from the folder and
moving it to the root. Then, move the Finder back. The folder should
now be blessed. If not, then there is probably an issue with the System
Folder.
6. In making an OS X boot drive, the ONLY two recommended solutions
are:
--install from the OS X install disk, preferably the one which came with
the Mac. You will not be able to make a successful boot drive using an
older disk set. A newer disk set should also be fine.
--use a utility, such as Carbon Copy Cloner, to perform a copy of an
existing OS X install. It is not possible to do this manually. There
are issues with permissions, hidden files, and files in use that cannot
be manually overridden. If you are using a disk image, you will still
need to use a utility, such as Carbon Copy Cloner, to copy the files out
from the image to the root of the new boot volume. A simple drag and
drop will not include the necessary hidden files, such as the boot
loader and the kernel.
If the volume does not appear as a Start Up Disk, try booting with the
Option key held down and see if the drive shows in the boot drive
selection screen.
If the volume does not show, or the kernel panics on boot, chances are
the OS install was not performed properly.
In general, CD/DVD drives are not bootable via firewire, but will work
under certain circumstances, usually booting from OS X to OS X. They
should not be relied upon as such. To boot from one, hold down the
Option key while booting. If the boot CD shows on the screen, you may
select it and continue the boot.

Can I dual boot snow leopard and mountain lion if I've installed boot camp on my drive

Can I dual boot snow leopard and mountain lion if I've installed boot camp on my drive

Yes as I said before. If your model Mac came with Snow Leopard and you are now running Mt Lion and have Windows installed in a Boot Camp Partition all you have to do is make the Mt Lion partition smaller, take the free space and make it another Mac partition and you should be able to install Snow Leopard into that partition.
I have Snow Leopard, Lion and Mt Lion installed on my MBP. No Windows in a Boot Camp partition because I run Windows XP in a Virtual Machine on both Lion and Mt Lion.

Time Machine Data Transfer - From FireWire Drive to Time Capsule - HELP!

Time Machine Data Transfer - From FireWire Drive to Time Capsule - HELP!
I've been searching for weeks for a solution to my problem. Here's the story I've come across since I installed Leopard on Oct. 26, 2007.
I first installed Leopard on my Early 2006 MacBook and set up Time Machine with a 200GB external FireWire drive. Since then, things have been fine, until Time Machine started deleting the oldest backups. I'm a pack-rat and hated this feeling of losing data. So, I now have a few months worth of backups on my 200GB FireWire drive.
The Time Capsule is released, I finally talk myself into getting one and transferring my old data from the 200GB drive to my 1TB TC.
I did some researching through forums about how to move data from one Time Machine drive to another, so I took the concept and wanted to apply it to my Time Capsule. I made a DMG image of my 200GB drive, in order to move the data. I figured if I can make an image, copy it, and open it on the Time Capsule - all will go smoothly - just as some had mentioned they've done with external drives.
Now, I have a 164GB DMG image of my Time Machine, with no hope in sight of gaining it back. I've tried taking the image, using Disk Utility, and restoring my original 200GB external with the imaged Time Machine data, but whenever I do, I come across error messages.
In Disk Utility, I've done the following steps:
* Disk Image is found on Time Capsule
* I select the 200GB drive and select 'Restore'
* I drag and drop the Disk Image to the 'Image' field
* I drag and drop the 200GB drive into the the 'Restore' field
* Select 'Erase Destination'
* Select 'Restore'
* I get the warning message that I'll erase the drive - I proceed
* I enter my password
Error message pops up:
"Restore Failure: Could not find any scan information. The source image needs to be imagescanned/scanned for restore."
I select the image in Disk Utility, then proceed with the following steps:
* Click on "Image" then down to "Scan Image for Restore"
* I enter my password
After hours of waiting, I get another error message:
"Unable to scan. (Broken pipe)."
I'm going to see, after transferring the DMG to the Time Capsule, if I can drag-and-drop the files from the Time Capsule drive onto the 200GB hard drive.
IF anyone has any more suggestions, please let me know!

32 updates on this Mac since December 2007 - Hardware, software, OS...
They keep coming at about 6 or 7 a month. Some of them I don't care about, but several are essential. 10.5.3 has been seeded to the testers a couple of times and will probably show up in the next few weeks. Jaguar wasn't worth a d*mn until 10.2.6, Panther about 10.3.4, Tiger about 10.4.4 - I'd say we are ahead or on schedule Too bad I can't get Apple to fix Spaces. I wish they'd focus on what I want but I guess some take more time than others.
2007-12-18 00:32:39 -0800: Installed "GarageBand Update" (4.1.1)
2007-12-18 00:32:43 -0800: Installed "QuickTime Broadcaster" (1.5.2)
2007-12-18 00:33:07 -0800: Installed "Security Update 2007-009" (1.0)
2007-12-18 00:33:29 -0800: Installed "QuickTime" (7.3.1)
2007-12-19 09:32:03 -0800: Installed "MacBook MacBook Pro Software Update" (1.1)
2007-12-23 23:57:32 -0800: Installed "Security Update 2007-009" (1.1)
2008-01-16 09:18:07 -0800: Installed "iMovie Update" (7.1.1)
2008-01-16 09:18:14 -0800: Installed "Front Row Update" (2.1.2)
2008-01-16 09:18:45 -0800: Installed "iTunes" (7.6)
2008-01-16 09:19:31 -0800: Installed "QuickTime" (7.4)
2008-01-29 21:33:14 -0800: Installed "Keynote Update" (4.0.2)
2008-01-29 21:33:23 -0800: Installed "Pages Update" (3.0.2)
2008-01-29 21:33:31 -0800: Installed "Numbers Update" (1.0.2)
2008-02-02 01:18:43 -0800: Installed "iWeb Update" (2.0.3)
2008-02-05 20:12:17 -0800: Installed "iPhoto Update" (7.1.2)
2008-02-15 09:03:49 -0800: Installed "iLife Support" (8.2)
2008-02-15 09:04:17 -0800: Installed "QuickTime" (7.4.1)
2008-02-15 09:04:51 -0800: Installed "Leopard Graphics Update" (1.0)
2008-02-19 23:44:37 -0800: Installed "Keyboard Firmware Update" (1.0)
2008-02-25 19:24:33 -0800: Installed "iTunes" (7.6.1)
2008-03-03 17:14:18 -0800: Installed "GarageBand Update" (4.1.2)
2008-03-03 17:14:31 -0800: Installed "iPhoto Update" (7.1.3)
2008-03-12 18:11:36 -0700: Installed "AirPort Utility" (5.3.1)
2008-03-18 10:03:57 -0700: Installed "Safari" (3.1)
2008-03-20 13:00:58 -0700: Installed "Security Update 2008-002" (1.0)
2008-03-20 13:01:04 -0700: Installed "Time Machine and AirPort Updates" (1.0)
2008-03-21 22:49:16 -0700: Installed "Digital Camera RAW Compatibility Update" (2.0)
2008-04-03 00:50:22 -0700: Installed "Front Row Update" (2.1.3)
2008-04-03 00:50:50 -0700: Installed "QuickTime" (7.4.5)
2008-04-03 00:51:58 -0700: Installed "iTunes" (7.6.2)
2008-04-08 17:16:02 -0700: Installed "Keynote Update" (4.0.3)
2008-04-08 17:16:08 -0700: Installed "MacBook Pro EFI Firmware Update" (1.5)

Mac SE FDHD with dead HDD - boot and run from floppy drive alone? HDD type?

Hello!
I picked up a Mac SE FDHD a few months back - a model with a Superdrive and hard drive, as well as 4 MB of RAM. It came with a keyboard and mouse, but no floppies of any kind. Upon testing, I discovered that the hard drive did not work - the "flashing question mark folder" appears at startup, and the disk setup utility on the system 6 install disks I created using a more modern mac can't detect it. I don't hear HDD seek sounds either. Everything else works fine, as far as I can tell. The reason I want to use this old Mac is simply to boot it up and run a few favorite old programs (such as MacPaint and many old games), so I don't want to put too much money into it.
I discovered my parents still owned a old, 170 MB "LaCie Tsunami" SCSI external drive, used with our long-failed Mac II, and decided to use as the SE's boot drive, as a cheap workaround to avoid buying a "new" drive. However, after a rather odd turn of events (described below for information purposes), it turns out that the 50-pin SCSI drive itself functions, but in the process, I think I killed the enclosure. Unless this drive can replace the internal drive of the SE, (or get lucky and find a compatible drive somewhere), I'll need to run the SE from its single floppy drive.
I figure that since the original Mac had 128k of memory, a single 800k floppy, and no hard drive, and yet can still run OS 7, the SE should be able to run system 6 from floppies somehow. The question is how? Is there a tutorial online somewhere on how to set this up?
Furthermore, as far as the hard drive is concerned, is the SE's internal drive a standard 50 pin SCSI HDD, and thus likely compatible with the one from the LaCie?
Thanks for any suggestions, and for helping this "Old time Mac Newbie" out!
-Dan
PS: What happened to the LaCie drive - for information purposes:
WHen I attached to the LaCie drive to the SE and booted the OS 6 install disks, t worked - OS 6 installed to it just fine. However, it turns out that a "dormant" copy of Norton utilities reactivated when I booted to the SCSI drive, and encrypted the disk's partition table. (Why it was not encrypted BEFORE installing and booting OS 6, I don't know) Having not used the drive for 17 years , and thus not knowing the password, I had to reformat it. I have a Sawtooth G4 with an Apple SCSI card - but no cable that would go from the PCI card's SCSI port to the external enclosure. THus, I removed the drive from the enclosure, mounted it in the G4 internally, and formatted it as Mac OS Standard (with OS 9 drivers) using Mac OS 10.3. Upon re-installing the drive in its SCSI enclosure, I found that it no longer works - Norton was erased, but the SE gives me a "Sad Mac" icon upon boot. Furthermore, after borrowing the correct SCSI cable, I found the enclosure now kernel panics my G4 when attached. The drive itself, when mounted internally in the G4, still functions perfectly. Thus, it seems that either the enclosure is dead, or something about OS X's reformat is renders the HDD incompatible with the enclosure...

"I removed the drive from the enclosure, mounted it in the G4 internally, and formatted it as Mac OS Standard (with OS 9 drivers) using Mac OS 10.3."
I just re-checked Disk Utility's format options under Panther and only see "Mac OS Extended (Journaled)" or "Mac OS Extended." I don't see an option for formatting Mac OS Standard. Are you certain that you formatted the drive as a Mac OS Standard (HFS) volume? If it's a Mac OS Extended (HFS+) volume, that would explain why it won't work when connected to the SE. When using external SCSI enclosures having a hard drive or optical drive, I always opted to connect an "active" SCSI terminator to the unused SCSI port on the enclosure. It seemed to provide stability, because I never had a problem with any of them. Does the LaCie enclosure have a built-in termination switch or do you plug in a terminator to the opposite SCSI port on the back? As for installing/using the 170 MB hard drive in the SE, it must have a jumper installed on its TE pins, if it's the last device connected to the SE's SCSI ribbon cable. Additionally, the HDD must have a unique SCSI address, The factory default is usually 0, which doesn't necessarily require a jumper. If another address is desired, a jumper or two installed across specific pins will accomplish that. If the LaCie enclosure had a switchable SCSI address button on the back (you change it by pressing in with a ball point pen), there were small wires from it that were connected to the drive's address pins in a specific way. Did you disconnect/re-connect these when you re-installed the drive in the enclosure? Also, if the enclosure has a termination switch, did you re-connect its wires to the drive's TE pins?

Can I erase the boot camp partition and dual boot snow leopard and mountain lion instead

Can I erase the boot camp partition and dual boot snow leopard and mountain lion instead

Please don't double post. Look at your other thread.
If you want to get rid of Windows and the BC partition use the Boot Camp assistant program to remove the Win/BC partition. Don't do it manually with Disk Utility Use the BC A program.

I have an older IMac 5. I installed snow Leopard on. Now my DVD drive is not working. Discs go in but it dosn't boot up or show in finder. Then disc won't eject unless i shut down and restart. HELP !

I have an older IMac 5. I installed snow Leopard on. Now my DVD drive is not working. Discs go in but it dosn't boot up or show in finder. Then disc won't eject unless i shut down and restart. HELP !

Snow Leopard cannot run on a PPC G5 Mac as it requires an Intel processor. Please confirm what Mac you have.

Dual Boot SnowLeo-Leopard from FireWire Drive doesn not work!

Similar Messages

Maybe you are looking for