Large file problems with an external FAT32 formatted drive (solutions???)

I have an external hard drive that was from my PC and formatted as NTFS so it was read only on my Mac. I formatted it to FAT32 so that I could read/write to it from both my Mac and PC.
Now, because it is formatted FAT32, I can only have a 4GB max file which has proved to be a pain to me. Is there not a format that satisfies both platform with unrestricted file sizes?
Thanks in advance.

Well, the answer is: not easily.
NTFS, EXT2, and Mac HFS can all be read and written by Windows, Mac OS X and Linux, with appropriate software. You should probably settle on what you are going to use most, and use that as your preferred filesystem.
For example, if you were going to use the Mac mostly to deal with the disk, format the disk using HFS+. On Windows, buy MacDrive and install it to read/write the Mac-format disk. If you are going to use Windows most of the time, then install MacFUSE and NTFS-3g on your Mac (http://code.google.com/p/macfuse/). et cetera.
There's nothing in the way of a really good cross-platform filesystem. ZFS may eventually become that (one might hope), but that's still not quite there.

Similar Messages

  • Error code 0 when copying a large file to a Mac OS Extended formatted drive

    I always back up my photos manually by dragging a folder containing many folders containing many photos into an external drive that I immediately formatted as Mac OS Extended (Journaled) the day I bought it 2 years ago. I now run into a Error Code 0 when I do this. The "mother" folder is 240 GB in size. As I stated, this drive has been formatted for the Mac, so I don't understand why it's (apparently) running into a problem peculiar to FAT32-formatted drives. My iMac has 16 GB of RAM, of which 10 GB was free, the last time I tried to do this.

    Well, you did mention...
    so I don't understand why it's (apparently) running into a problem peculiar to FAT32-formatted drives
    I kind of had to assume at that point the source drive was the one you formatted as Mac OS Extended two years ago, and the target drive was FAT32. If not, then I'm not sure why you mentioned FAT32 at all.
    In that same thinking, error code 0 is directly related to FAT formatted drives.

  • Portege R500: XP installation with USB external CD/DVD drive - SOLUTION

    Hello all !
    Just wanted to take five minutes to inform you that installing XP on a Portege R500 with USB external CD/DVD drive is possible, even if you already have erased Vista and only with a bootable CD of Win XP in hand.
    First go into your BIOS and check / set first boot device is CD/DVD drive
    Start your installation of win XP from the CD without the F6 thing and let it go his way
    After a while, the installation stops and says "can't find the file xxxx" and you are invited to say where this file is
    You "just" have to replace the drive letter "C:" that is given by default with the drive letter of your CD/DVD (and let the rest just like it is) and the installation will continue until the next "can't find..." and you will again replace the drive letter, etc..
    After a complete "manually assisted automatic" installation, you are welcome in Win XP !
    Next question is "Where can I find my CD/DVD drive letter ?" and the answer is "this is the next letter after your last HDD letter" (I consider you have only your Portege with nothing else plugged than your CD/DVD) so in most cases it will be "E" because C: is the first partition of your HDD and D: is the hidden / recovery partition that win creates.
    But do not worry, if you type the wrong letter you will have as many tries as you wish until you find the good one and for the following "can't find..." it will remain the same.
    I hope these pieces of information will help some of you who want a clean install of win XP starting from a newly formatted HDD.
    With kind Regards,
    Mage.

    What a great information!
    Thanks a lot for this posting.
    I think it could be useful for others here.
    Bye

  • Airport Extreme, Airdisk, and Vista - large file problem with a twist

    Hi all,
    I'm having a problem moving large-ish files to an external drive attached to my Airport Extreme SOMETIMES. Let me explain.
    My system - Macbook Pro, 4gb ram, 10gb free HD space on macbook, running latest updates for mac and vista, external hard drive on AE is an internal WD in an enclosure w/ 25gb free (its formatted for pc, but I've used it directly connected to multiple computers, mac and pc, without fail), AE is using firmware 7.3.2, and im only allowing 802.11n. The problem occurs on the Vista side - havent checked the mac side yet.
    The Good - I have bit torrents set up, using utorrent, to automatically copy files over to my airdisk once they've completed. This works flawlessly. If i connect the hard drive directly to my laptop (macbook running bootcamp w/ vista, all updates applied), large files copy over without a hitch as well.
    The Bad - For the past couple weeks (could be longer, but I've just noticed it recently being a problem - is that a firmware problem clue?) If i download the files to my Vista desktop and copy them over manually, the copy just sits for a while and eventually fails with a "try again" error. If i try to copy any file over 300mb, the same error occurs.
    What I've tried - well, not a lot. The first thing i did was to make sure my hard drive was error free, and worked when physically connected - it is and it did. I've read a few posts about formatting the drive for mac, but this really isnt a good option for me since all of my music is on this drive, and itunes pulls from it (which also works without a problem). I do however get the hang in itunes if i try to import large files (movies). I've also read about trying to go back to an earlier AE firmware, but the posts were outdated. I can try the mac side and see if large files move over, but again, i prefer to do this in windows vista.
    this is my first post, so im sure im leaving out vital info. If anyone wants to take a stab at helping, I'd love to discuss. Thanks in advance.

    Hello,
    Just noticed the other day that I am having the same problem. I have two Vista machines attached to TC w/ a Western Digital 500 gig USB'd. I can write to the TC (any file size) with no problem, however I cannot write larger files to my attached WD drive. I can write smaller folders of music and such, but I cannot back up larger video files. Yet, if I directly attach the drive to my laptop I can copy over the files, no problem. I could not find any setting in the Airport Utility with regards to file size limits or anything of the like. Any help on this would be much appreciated.

  • Copy a small version into a larger file - problem with typing

    Hi,
    I have paste a copy of a Captivat file in a 10px (each side) larger file. Now I got the problem that typing animation is not on the correct place. Take a look:
    the original:
    the pasted version in the 10px larger file:
    Is this a known problem? Is there a way to fix this?

    Hi there,
    I would suggest that you use a screen capture utility such as Snagit to capture your Request Membership box and then insert this into your Captivate slide as an image. This will then enable you to accurately position the graphic and should address the typing problem.
    Best - Mark
    Visit the macrofireball blog

  • Problem with USB External Hard Disk Drive

    I have similar problem with hard disk MK6025GAS in Sweex casing connected via USB as Raistlfiren in this post but I am not sure if it has something to do with kernel. The problem is that when I plug the hard disk via USB it is not even shown with in /dev/ or by fdisk -l. I had similar problems with the drive before but it was always shown in /dev.
    I got same output from dmesg as Raistlfiren in the post before
    # dmesg | tail
    sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
    sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
    Info fld=0x0
    I was browsing net for a lot of time to find a solution but nothing helped a lot. The problem is closes to the one described on Gentoo Forum
    I can see that it is recognized by computer since it is shown with lsusb
    # lsusb
    Bus 001 Device 005: ID 13fd:0540 Initio Corporation
    # lsusb -d 13fd:0540 -v
    Bus 001 Device 005: ID 13fd:0540 Initio Corporation
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    idVendor 0x13fd Initio Corporation
    idProduct 0x0540
    bcdDevice 0.00
    iManufacturer 1 Initio
    iProduct 2 MK6025GAS
    iSerial 3 0010100500000000
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
    Self Powered
    MaxPower 2mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 2
    bInterfaceClass 8 Mass Storage
    bInterfaceSubClass 6 SCSI
    bInterfaceProtocol 80 Bulk (Zip)
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x02 EP 2 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 1
    Device Qualifier (for other device speed):
    bLength 10
    bDescriptorType 6
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    bNumConfigurations 1
    Device Status: 0x0001
    Self Powered
    From the beginning I though and I still think that the partition table is screwed up but the programs like TestDisk and fixdisktable work only with disks shown in /dev/
    Additionally, I have checked the content of /var/log/kernel.log
    Sep 16 22:03:58 hramat kernel: usb 1-2: new high speed USB device using ehci_hcd and address 5
    Sep 16 22:03:58 hramat kernel: usb 1-2: configuration #1 chosen from 1 choice
    Sep 16 22:03:58 hramat kernel: scsi4 : SCSI emulation for USB Mass Storage devices
    Sep 16 22:03:58 hramat kernel: usb-storage: device found at 5
    Sep 16 22:03:58 hramat kernel: usb-storage: waiting for device to settle before scanning
    Sep 16 22:04:03 hramat kernel: scsi 4:0:0:0: Direct-Access Initio MK6025GAS 2.23 PQ: 0 ANSI: 0
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0
    Sep 16 22:04:03 hramat kernel: usb-storage: device scan complete
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] 117210240 512-byte hardware sectors: (60.0 GB/55.8 GiB)
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Write Protect is off
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Mode Sense: 86 0b 00 02
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:04:03 hramat kernel: sdd:<6>sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
    Sep 16 22:04:03 hramat kernel: Info fld=0x0
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Sense Key : 0x0 [current]
    and /var/log/errors.log
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:04:03 hramat kernel: sd 4:0:0:0: [sdd] Assuming drive cache: write through
    Sep 16 22:07:35 hramat kernel: INFO: task async/0:3957 blocked for more than 120 seconds.
    Sep 16 22:07:35 hramat kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    The only thing I understand from these logs is that the disk is blocked, therefore not listed in /dev.
    Assuming the newer kernel problems I could try to use some older live linux CD to see if that would work. I am also thinking of connecting this hard drive directly to my laptop, using live linux CD and maybe check the output of hdparm. Is there anything else I could check or try?
    Thank you for any help or suggestions
    Matej

    Thank you nTia89 for response. Sorry for not providing enough information.
    I believe the problem is not system dependent. I have dual boot with windows and there the disk has also problems. However, I do have Arch32 with Kernel 2.6.30, using Gnome. hal and dbus are also running.
    I did not tried to connect the disk to the computer directly, I will try it today.
    Yesterday I have used SystemRescueCD 0.4.1 with Kernel 2.6.22. I wanted to see if it will be recognized by the system and placed in /dev/. Yes it was. This means that the problem highlighted in Gentoo forum can be true, but it doesn't solve my problem. I have tried to connect the drive several times to Arch and it was not shown in /dev/sd*, in SystemRescueCD it was placed as /dev/sdb. Now I am sure that the partition table is screwed up.
    So I have started to play with the drive in SystemRescueCD with TestDisk and FixDiskTable but without success.
    % fdisk -l
    Disk /dev/sda: 100.0 GB, 100030242816 bytes
    255 heads, 63 sectors/track, 12161 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 1530 12289693+ 7 HPFS/NTFS
    /dev/sda2 1531 6672 41303115 7 HPFS/NTFS
    /dev/sda3 6673 12161 44090392+ f W95 Ext'd (LBA)
    /dev/sda5 * 6673 11908 42058138+ 83 Linux
    /dev/sda6 11909 12161 2032191 82 Linux swap / Solaris
    Disk /dev/sdb: 60.0 GB, 60011642880 bytes
    64 heads, 32 sectors/track, 57231 cylinders
    Units = cylinders of 2048 * 512 = 1048576 bytes
    Disk /dev/sdb doesn't contain a valid partition table
    Manufacturer disk geometry: Heads: 16; Cylinders: 16383; Sectors: 63; Logical Blocks (LBA): 117210240
    TestDisk found only Linux partitions with 43Gb while disk had only one 60Gb partitioned with FAT32/NTFS.
    Also recognized 64 heads, 57231 cylinders and 32 sectors (same as from fdisk -l), which obviously differs from manufacturer disk geometry.
    testdisk.log:
    Thu Sep 17 19:09:26 2009
    Command line: TestDisk
    TestDisk 6.8, Data Recovery Utility, August 2007
    Christophe GRENIER
    Linux version (ext2fs lib: 1.40.2, ntfs lib: 9:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: none)
    Using locale 'C'.
    Hard disk list
    Disk /dev/sda - 100 GB / 93 GiB - CHS 12161 255 63, sector size=512
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32, sector size=512
    Disk /dev/sdb - 60 GB / 55 GiB
    Partition table type: Intel
    Interface Advanced
    New options :
    Dump : No
    Cylinder boundary : Yes
    Allow partial last cylinder : No
    Expert mode : No
    Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57231 64 32
    Current partition structure:
    Partition sector doesn't have the endmark 0xAA55
    Ask the user for vista mode
    Computes LBA from CHS for Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Allow partial last cylinder : Yes
    search_vista_part: 1
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Search for partition aborted
    Results
    interface_write()
    No partition found or selected for recovery
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Search for partition aborted
    Results
    interface_write()
    No partition found or selected for recovery
    simulate write!
    write_mbr_i386: starting...
    Store new MBR code
    write_all_log_i386: starting...
    No extended partition
    Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Current partition structure:
    Partition sector doesn't have the endmark 0xAA55
    Ask the user for vista mode
    Allow partial last cylinder : Yes
    search_vista_part: 1
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Results
    interface_write()
    No partition found or selected for recovery
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    NTFS at 8956/63/32
    heads/cylinder 255 (NTFS) != 64 (HD)
    sect/track 63 (NTFS) != 32 (HD)
    filesystem size 24579387
    sectors_per_cluster 8
    mft_lcn 1024141
    mftmirr_lcn 1650676
    clusters_per_mft_record -10
    clusters_per_index_record 1
    NTFS part_offset=9392094720, part_size=12584646144, sector_size=512
    NTFS partition cannot be added (part_offset<part_size).
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34129 1 1 75201 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=69896224, size=84116272, end=154012495, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34632 2 1 75704 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=70926400, size=84116272, end=155042671, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34668 0 1 75740 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71000064, size=84116272, end=155116335, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34673 1 1 75745 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71010336, size=84116272, end=155126607, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34699 2 1 75771 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71063616, size=84116272, end=155179887, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 34708 2 1 75780 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=71082048, size=84116272, end=155198319, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36338 0 1 77410 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74420224, size=84116272, end=158536495, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36367 0 1 77439 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74479616, size=84116272, end=158595887, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36401 2 1 77473 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74549312, size=84116272, end=158665583, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 36414 2 1 77486 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=74575936, size=84116272, end=158692207, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 37949 1 1 79021 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=77719584, size=84116272, end=161835855, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 37955 1 1 79027 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=77731872, size=84116272, end=161848143, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 37989 1 1 79061 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=77801504, size=84116272, end=161917775, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 38404 0 1 79476 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=78651392, size=84116272, end=162767663, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 39636 2 1 80708 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=81174592, size=84116272, end=165290863, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 41263 1 1 82335 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=84506656, size=84116272, end=168622927, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 41266 1 1 82338 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=84512800, size=84116272, end=168629071, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 41660 0 1 82732 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=85319680, size=84116272, end=169435951, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 42898 0 1 83970 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=87855104, size=84116272, end=171971375, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 43244 1 1 84316 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=88563744, size=84116272, end=172680015, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 44870 2 1 85942 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=91893824, size=84116272, end=176010095, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 44930 2 1 86002 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=92016704, size=84116272, end=176132975, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 46961 0 1 88033 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=96176128, size=84116272, end=180292399, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 47312 0 1 88384 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=96894976, size=84116272, end=181011247, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 48393 2 1 89465 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=99108928, size=84116272, end=183225199, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 49633 2 1 90705 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=101648448, size=84116272, end=185764719, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 50767 1 1 91839 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=103970848, size=84116272, end=188087119, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 51150 1 1 92222 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=104755232, size=84116272, end=188871503, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 51941 1 1 93013 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=106375200, size=84116272, end=190491471, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 52759 0 1 93831 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=108050432, size=84116272, end=192166703, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 53069 1 1 94141 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=108685344, size=84116272, end=192801615, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 53768 0 1 94840 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=110116864, size=84116272, end=194233135, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54287 0 1 95359 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=111179776, size=84116272, end=195296047, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54493 2 1 95565 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=111601728, size=84116272, end=195717999, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54861 1 1 95933 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=112355360, size=84116272, end=196471631, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54890 2 1 95962 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=112414784, size=84116272, end=196531055, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 54953 2 1 96025 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=112543808, size=84116272, end=196660079, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 56330 1 1 97402 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=115363872, size=84116272, end=199480143, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 56334 0 1 97406 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=115372032, size=84116272, end=199488303, disk end=117211136)
    recover_EXT2: s_block_group_nr=0/320, s_mnt_count=31/34, s_blocks_per_group=32768
    recover_EXT2: boot_sector=0, s_blocksize=4096
    recover_EXT2: s_blocks_count 10514534
    recover_EXT2: part_size 84116272
    D Linux 57203 0 1 98275 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    This partition ends after the disk limits. (start=117151744, size=84116272, end=201268015, disk end=117211136)
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Check the harddisk size: HD jumpers settings, BIOS detection...
    The harddisk (60 GB / 55 GiB) seems too small! (< 103 GB / 95 GiB)
    The following partitions can't be recovered:
    D Linux 34129 1 1 75201 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34632 2 1 75704 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34668 0 1 75740 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34673 1 1 75745 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34699 2 1 75771 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 34708 2 1 75780 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36338 0 1 77410 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36367 0 1 77439 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36401 2 1 77473 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 36414 2 1 77486 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 37949 1 1 79021 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 37955 1 1 79027 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 37989 1 1 79061 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 38404 0 1 79476 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 39636 2 1 80708 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 41263 1 1 82335 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 41266 1 1 82338 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 41660 0 1 82732 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 42898 0 1 83970 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 43244 1 1 84316 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 44870 2 1 85942 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 44930 2 1 86002 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 46961 0 1 88033 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 47312 0 1 88384 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 48393 2 1 89465 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 49633 2 1 90705 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 50767 1 1 91839 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 51150 1 1 92222 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 51941 1 1 93013 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 52759 0 1 93831 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 53069 1 1 94141 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 53768 0 1 94840 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54287 0 1 95359 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54493 2 1 95565 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54861 1 1 95933 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54890 2 1 95962 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 54953 2 1 96025 27 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 56330 1 1 97402 26 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 56334 0 1 97406 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    D Linux 57203 0 1 98275 25 16 84116272
    EXT3 Large file Sparse superblock Recover, 43 GB / 40 GiB
    Results
    interface_write()
    No partition found or selected for recovery
    simulate write!
    write_mbr_i386: starting...
    Store new MBR code
    write_all_log_i386: starting...
    No extended partition
    Interface Advanced
    Disk /dev/sdb - 60 GB / 55 GiB
    Partition table type: Intel
    Disk /dev/sdb - 60 GB / 55 GiB
    Partition table type: Intel
    New options :
    Dump : No
    Cylinder boundary : Yes
    Allow partial last cylinder : No
    Expert mode : No
    New options :
    Dump : No
    Cylinder boundary : Yes
    Allow partial last cylinder : No
    Expert mode : No
    Analyse Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Current partition structure:
    Partition sector doesn't have the endmark 0xAA55
    Ask the user for vista mode
    Allow partial last cylinder : No
    search_vista_part: 0
    search_part()
    Disk /dev/sdb - 60 GB / 55 GiB - CHS 57232 64 32
    Search for partition aborted
    Results
    Can't open backup.log file: No such file or directory
    interface_load
    interface_write()
    No partition found or selected for recovery
    simulate write!
    write_mbr_i386: starting...
    Store new MBR code
    write_all_log_i386: starting...
    No extended partition
    TestDisk exited normally.
    fixdisktable first output:
    % ./fixdisktable -d /dev/sdb
    Getting hard disk geometry
    cylinders=57231, heads=64, sectors=32
    end_offset: 2147482624
    FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
    EXT2 partition at offset 56832, length=(41072.398 MB) 43067531264
    Sectors: start= 111, end= 84116382, length= 84116272
    Hd,Sec,Cyl: start(3,16,0) end(28,31,41072)
    Done searching for partitions.
    Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
    1 80 3 16 0 63 32 1023 111 84116273 83 (Interpretted)
    1 80 3 16 0 63 224 255 111 84116273 83 (RAW)
    1: 8003 1000 833f e0ff 6f00 0000 3183 0305
    2: 0000 0000 0000 0000 0000 0000 0000 0000
    3: 0000 0000 0000 0000 0000 0000 0000 0000
    4: 0000 0000 0000 0000 0000 0000 0000 0000
    Do you wish to write this partition table to disk (yes/no)? no
    fixdisktable second output:
    % ./fixdisktable -d -r -v /dev/sdb
    Getting hard disk geometry
    cylinders=57231, heads=64, sectors=32
    end_offset: 2147482624
    FfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSsNnBbUuFfEeSs
    NTFS partition at offset 17483776, length=(17592186043512.582 MB) 184467440727622 49216
    Sectors: start= 34148, end=36028797017147916, length=36028797017113768
    Hd,Sec,Cyl: start(43,5,16) end(16,12,2096265)
    Done searching for partitions.
    Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
    1 80 43 5 16 63 32 1023 34148 -1850199 07 (Interpretted)
    1 80 43 5 16 63 224 255 34148 -1850199 07 (RAW)
    1: 802b 0510 073f e0ff 6485 0000 a9c4 e3ff
    2: 0000 0000 0000 0000 0000 0000 0000 0000
    3: 0000 0000 0000 0000 0000 0000 0000 0000
    4: 0000 0000 0000 0000 0000 0000 0000 0000
    Do you wish to write this partition table to disk (yes/no)? no
    This string "FfEeSsNnBbUu" was repeating there for longer time and it was most probably related to debugging or a verbose mode of fixdisktable
    As I have mentioned I will try to connect the disk directly to the computer and see what will happen.
    Shall I try to correct the disk geometry to the one specified by manufacturer? Is it possible?
    Any suggestions?

  • Unable to transfer large files from MB to External HDs

    Hi,
    This may be an unusual one. My 1st edition Macbook won't let me transfer large files to my external hard-drives, either by USB, Ethernet or wirelessly through my home wi-fi network.
    I've started video editing so I'm importing DVcam tapes through firewire from the camera. A full DV tape translates to about 8-12gb I think.
    Using iMovie and saving the import to my Freecom 3.5inch network harddrive vis USB or ethernet, it fails saying 'Unexpected error, error code 1309'.
    When I try quicktime pro instead to import the tape to the external HD, I get 'Operation could not be completed, An attempt to add a resource to the file failed'. This happens too with my WD 2.5inch external drive.
    However, there is no such problem when I import to the MB's internal harddrive. When I then try and shift the large file off the laptop to an external drive, via USB, ethernet of wirelessly, for editing and save keeping, it fails half way through.
    I have the same problem when I try back-up my 17gb virtual windows machine I use with VMware fusion off the laptop to an external drive.
    I am currently burning an 18gb iMovie project from the MB's internal HD, over 5 DVDs using Toast's disc-spanning and will reimport them to the external, which is really time consuming.
    Also to note, Final Cut Express doesn't have these problems as it seems to break up what would be an 18gb movie file into several smaller files, which my MB is quiet happy to let go onto an external drive. However, the problem re-emerges on Final Cut Ex when I try and import a HDV tape. Possibly FCE isn't breaking them up into small enough pieces for my MB to handle?
    Any ideas why this is happening and what I can do to fix it? Or does this mean a new laptop?

    Irish Apple Fan wrote:
    Hi,
    This may be an unusual one. My 1st edition Macbook won't let me transfer large files to my external hard-drives, either by USB, Ethernet or wirelessly through my home wi-fi network.
    I've started video editing so I'm importing DVcam tapes through firewire from the camera. A full DV tape translates to about 8-12gb I think.
    Using iMovie and saving the import to my Freecom 3.5inch network harddrive vis USB or ethernet, it fails saying 'Unexpected error, error code 1309'.
    When I try quicktime pro instead to import the tape to the external HD, I get 'Operation could not be completed, An attempt to add a resource to the file failed'. This happens too with my WD 2.5inch external drive.
    I'm a bit late to the party, but specifically there's a 4GB file size limit in the FAT32 format that is standard on many external hard drives. I've run across this problem before, and usually it copies over most of the file and then quits when it reaches the limit.

  • Large file folder with question mark is flashing on screen.

    Just turned on computer for the first time and a large file folder with a question mark is flashing on the screen. I am unable to do anything and have restarted and it does the same thing.  Please help!

    It does this when it can't see the operating system. You didn't give much information but I'm assuming it's a brand new mini and you aren't using any external drives for the operating system. If that's the case then yes, reinstall OS X. Put your install DVD into the optical drive and reboot. As soon as you hear the chime, hold down the "C" key on your keyboard (or the Option key until the Install Disk shows up). That will force your Mac to boot from the install DVD in the optical drive.
    If reinstallation isn't possible, or if the problem continues after reinstallation, then you need to exchange it for another, because something is keeping the operating system on the drive from being read.

  • I just updated my latest java but the update is causing problems with some externale devices. So i would like to uninstall this latest java update and get back the previous one. That should solve to problems with my external device

    i just updated my latest java but the update is causing problems with some external devices. So i would like to uninstall this latest java update and get back the previous one. That should solve to problems with my external device.
    Is this possible and how do i do that?
    Anyone who responds thanks for that!
    Juko
    I am running
    Hardware Overview:
      Model Name:          Mac Pro
      Model Identifier:          MacPro1,1
      Processor Name:          Dual-Core Intel Xeon
      Processor Speed:          2,66 GHz
      Number of Processors:          2
      Total Number of Cores:          4
      L2 Cache (per Processor):          4 MB
      Memory:          6 GB
      Bus Speed:          1,33 GHz
      Boot ROM Version:          MP11.005D.B00
      SMC Version (system):          1.7f10
      Serial Number (system):          CK7XXXXXXGP
      Hardware UUID:          00000000-0000-1000-8000-0017F20F82F0
    System Software Overview:
      System Version:          Mac OS X 10.7.5 (11G63)
      Kernel Version:          Darwin 11.4.2
      Boot Volume:          Macintosh HD(2)
      Boot Mode:          Normal
      Computer Name:          Mac Pro van Juko de Vries
      User Name:          Juko de Vries (jukodevries)
      Secure Virtual Memory:          Enabled
      64-bit Kernel and Extensions:          No
      Time since boot:          11 days 20:39
    Message was edited by Host

    Java 6 you can't as Apple maintains it, and Java 7 you could if you uninstall it and Oracle provides the earlier version which they likely won't his last update fixed 37 remote exploits.
    Java broken some software here and there, all you'll have to do is wait for a update from the other parties.

  • Problem with 2 External Drives on my new iMac

    I am having a problem when I daisy-chain a second external HD to my first external HD connected to my new iMac. This is the second external HD I've tried this with, with similar problems arising.
    My setup: OS 10.5.6. First external HD: G-Tech Q 1TB; 2nd External HD: also a G-Tech Q 1TB (the first time I was daisy-chaining a LaCie 250GB drive to my first external drive).
    Problem: when my second external HD is daisy-chained to the first external HD my system starts to go wonky. I can't force quit apps for one. My system hangs. On reboot I don't get past the blue screen. If I remove the daisy-chain all is fine.
    I initially had this problem with another external HD I tried to daisy-chain to the first. Same issue.
    I was trying to partition the second external using Disk Utility. When I hit the Partition button, Disk Utility just hung with the beach ball.
    When I attached a second external the first time I tried to do this all sorts of havoc ensued. A lot of apps were hanging and I couldn't Force Quit them. The whole system seemed to go wonky.
    Can anyone tell me what might be happening here?

    I've been doing a bit of research on these boards about daisy-chaining problems and am reading that sometimes daisy-chaining can overwhelm the Firewire bus and even corrupt data. This is what I had experienced the first time I tried to daisy-chain. Someone recommended a powered Firewire repeater (like this: http://tinyurl.com/kl84n5) would be a better solution.
    Given I've got only 1 Firewire port on my iMac, what do you think?

  • Anyone know if the long standing duplicate files problem with File History has been fixed yet?

    There are loads of public threads about the duplicate files problem
    with Windows 8/8.1 File History backup system.
    From all the threads I've looked at, there seems to be no solution,
    and no acknowledgement from MS that they can even repro the problem
    (which surprises me considerably as there are so many people who
    notice the problem).
    Is anyone aware of whether MS (may) have fixed this for Win10?
    Are MS aware of the problem and if they're able to fix it?
    Dave - with many GB of duplicated files in File History :)

    Hmm, is that the attitude MS would recommend? :)
    Why would I care what Microsoft would recommend?
    Clearly you don't, and you appear to have missed my smiley. Calm down
    Noel, many of us are as annoyed by aspects of modern Windows as you
    are. :)
    I'm all about making Windows actually WORK/./
    Aren't we all? Windows is software I use too many hours every day, I
    along with many millions of others need it to work really well. You
    are not alone.
    When they implement something that doesn't work, and even if it did work doesn't do what's needed - and/beyond that/ they remove features people DO need (such as the GUI for Windows Backup), I see no wrong in advising people of the way things
    really are.
    File History essentially does work - it's saved me a couple of times
    in the past couple of weeks. It just has a highly annoying habit of
    creating 100% duplicates of some files for no apparent reason. If MS
    have fixed that I won't have any known complaints about it.
    If you don't like it, you don't have to use it. I generally like it, I
    just want to see that its fixed.
    Dave

  • Will files saved on an external HD, formatted for Mac, be readable on a Windows machine?

    Will files saved on an external HD, formatted for Mac, be readable on a Windows machine?

    Only if the Windows computer has software such as MacDrive installed or the drive is hooked up to a Mac or AirPort Extreme and shared over a network.
    (60143)

  • Bat file problems with 5.2(3)

    I'm having bat file problems with CCM 4.2(3) with bat version 5.2(3). When adding phone/users getting an error number -2146828279 with this message "Description -Subscript Out of range".

    Hi Denis,
    Just wanted to know if the description contained a comma? There was a bug in a previous BAT version that would affect phone/user inserts if there was a comma.
    CSCsb61425 Bug Details
    Headline BAT insert fails if phone description contains comma
    This was in BAT 5.1.4
    Hope this helps!
    Rob

  • I have a problem with the external sound of my ipod, when I take the headphones the music keeps playing and the ipod recognizes still have a headset connected. how do I get external sound out?

    I have a problem with the external sound of my iPod, when I take the headphones the music keeps playing and the ipod recognizes still have a headset connected. how do I get external sound out?

    - Try insering and removing the headphone plug a dozen times or so.
    - Try cleaning out the headphone jack in the iPod.
    - Resett he iPod. Nothing is lost
    Reset iPod touch: Hold down the On/Off button and the Home button at the same time for at
    least ten seconds, until the Apple logo appears.
    - Restore from backup
    - Restoe to factory defaults/new iPod
    If yu still have the problem that indicates a hardware problem, likely a bad headphone jack. Yu can make an appointment at the Genius Bar of an Apple store to confirm.
    If not underwarranty Apple will only exchange your iPod for a refurbished one for:
    Apple - Support - iPod - Repair pricing
    A third-party place like the following is less expensive. Here is one. Google for more.
    iPhone Repair, Service & Parts: iPod Touch, iPad, MacBook Pro Screens

  • A few months ago I bought an imac 27 inch late 2013 ... ever since I have continuously problems with my external HDD that disconnect all the time and cause problems in other software (Lightroom, Adobe PS CS6) ...

    a few months ago I bought an imac 27 inch late 2013 .. §16GB - and flash memory) - 3,3 Ghz Intel Core 15
    ever since I have continuously problems with my external HDD that disconnect all the time and cause problems in other software (Lightroom, Adobe PS CS6) ... it is not  a HDD problem, because it occurs with my 3TB WD HDD (Time Machine), my 1TB WD and  1TB IOMEGA
    any one have a solution? anyone dealt with this problem in the apple care program?

    You are still under warranty and/or have AppleCare.  Call them.  Let them deal w/it.

Maybe you are looking for