68 pin SCSI drive recognition issue - PCI / adaptec 2930

I installed an Fujitsu 73GB 10K scsi drive to it.
Do I really need the PMU reset to see this installed HD?
Thanks

Resetting the PRAM is the usual method to get the computer to recognize new hardware. Hold down the command-option-p-r keys as you start and hold until you hear the chimes three times.
John

Similar Messages

  • SCSI drive recognition

    I recently added drives to my G4 and moved the PCI SCSI card to a new slot. After rebooting the system now registers my 40G SCSI drive as new hardware and I cant seem to figure out how to save the info on the disk. I even moved it back to the original PCI slot, but no go! I really need to get the data off this disk, what should I do?
    G4 Gigabit Ethernet   Mac OS X (10.4.8)  

    I recently added drives to my G4 and moved the PCI SCSI card to a new slot. After rebooting the system now registers my 40G SCSI drive as new hardware and I cant seem to figure out how to save the info on the disk. I even moved it back to the original PCI slot, but no go! I really need to get the data off this disk, what should I do?
    To be clear, I just need to get the drive to mount without erasing it. None of the options offered allow me to do that.
    G4 Gigabit Ethernet   Mac OS X (10.4.8)  

  • Best 68 Pin SCSI Card for Mac OS 9 on 933 mHz Quicksilver G4?

    Hello,
    I'm looking for a SCSI card that will support 68 pin SCSI drives (15K Cheetahs) on a Mac G4 Quicksilver running Mac OS 9 ONLY (Not Classic. I only installed OS 9 from the retail disc and am NOT using Mac OS X). I have Adaptec 2940UW and Adaptec 2940U2W cards which work on my Blue and White G3 with SCSI drives. However those Adaptec cards do not work on the G4....at least you can't boot from a SCSI drive on them.
    I would like a card that may also work in OS X in case I change the purpose of the machine later as I have those original install discs. I have read of some folks using the ATTO UL4D with success in OS X, but wanted to know if anyone knows if it will work in OS 9.2.1 only or Classic. I called ATTO Tech and they weren't sure, and some old web pages I have read only mention OS X. Hence, I'm unsure if it's compatible with OS9. I would appreciate any feedback from SCSI users. Also, if there are other cards that you think would work with my setup, please advise.
    Thanks,
    Jeff

    PowerDomain 39160
    Supported Operating Systems
    Macintosh OS 8.6
    Macintosh OS 9.0
    Macintosh OS 9.0.2
    Macintosh OS 9.0.3
    Macintosh OS 9.0.4
    Macintosh OS 9.1
    Macintosh OS 9.2.x
    Mac OS X 10.1.x
    Mac OS X 10.2.x
    Mac OS X 10.3.x
    Mac OS X Server 10.1.x
    Mac OS X Server 10.2.x
    Mac OS X Server 10.3.x
    Key Differentiators
    Takes full advantage of 64-bit PCI
    Connectivity for up to 30 SCSI peripherals with one card
    System Environment
    Desktop
    Number of devices
    Combination of 30, internal and external
    Bus System Interface Type
    64-bit PCI
    External Connectors
    (2) 68-pin Very High-Density Ultra160/m SCSI
    Internal Connectors
    2 68-pin Ultra 160
    1 50-pin Standard
    Data Transfer Rate
    320 MB combined (160 MB on each channel)
    System Requirements
    PCI-based Power Macintosh
    Mac® OS 8.6 or later, Mac OS X 10.1.x or 10.2.x
    Blue & White G3 or G4
    PCI expansion slot
    SCSI peripheral(s)
    http://www.adaptec.com/en-us/support/_eol/scsi_mac/apd-39160/

  • 2008 R2: OS(systemState/C: Drive) backup issues with VSS - 0x80042316 & 0x81080101 & 0x80080005 & 2155348001

    Hi-
    Looked thru the thread related to my questions and found nothing that applies yet.
    Example:
     http://social.technet.microsoft.com/Forums/en-US/4e4472b9-8e6f-4fdc-a287-1cc8c0f6de09/windows-2008-r2-backup-fails-with-event-521-error-code-2155348001?forum=windowsbackup
    http://social.technet.microsoft.com/Forums/en-US/e8c910f7-f0dd-4613-beae-b98894fb6f23/windows-server-2008-std-backup-fails-constantly-with-error-code-2155348001?forum=windowsbackup
    Here are details of the issues....
    Backup - OS error - system image:
    External disk - USB
    Mon - Fri @ 6PM.
    Windows SystemState
    OS(C:)
    Last backup failure...
    Start time: 8/11/2014 6:01:32 PM
    End time: 8/12/2014 4:51:29 AM
    Duration: 10:49:56.4414784
    [Critical error WINIMAGE_UNABLE_VSS] Unable to create VSS snapshot
      - Additional information: Refer to the log for more details
      - Troubleshooting link:
    http://kb.backupassist.com/errormap.php?BA2512
    The backup operation stopped before completing.
    Detailed error: ERROR - The shared restore point operation failed with error (0x81000101)
    The creation of a shadow copy has timed out. Try this operation again.
    Log of files successfully backed up:
    C:\Windows\Logs\WindowsServerBackup\Backup-12-08-2014_04-41-00.log
    Log of files for which backup failed:
    C:\Windows\Logs\WindowsServerBackup\Backup_Error-12-08-2014_04-41-00.log
    NOTE:
    The errors logs are not there?
    Windows Backup timed-out before the shared protection point was created.
    ERROR - The shared restore point operation failed with error (0x81000101)
    The creation of a shadow copy has timed out. Try this operation again.
    Event Viewer Log:
    Sequence of Events...
    1.
    The Block Level Backup Engine service has successfully started.
    2.
    Backup operation that started...
    Log Name:      Application
    Source:        Microsoft-Windows-Backup
    Date:          8/12/2014 4:51:06 AM
    Event ID:      521
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      mdnfile.Auxiant.local
    Description:
    The backup operation that started at '?2014?-?08?-?12T09:41:00.492000000Z' has failed because the
    Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed
    with following error code '2155348001'.
    Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
    --> Suggestion are to check Virus scanner or consult DPM forum...
    3.
    OS Job failed with errors...( Backup Assist is 3rd party backup - wrapper round Wbadmin/Win Backup)
    Log Name:      Application
    Source:        BackupAssist
    Date:          8/12/2014 4:51:51 AM
    Event ID:      5634
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      mdnfile.Auxiant.local
    Description:
    Backup job OS backup failed with errors.
    Critical error: Unable to create VSS snapshot
    Destination: External disk
    Start time: 8/11/2014 6:01:32 PM
    End time: 8/12/2014 4:51:29 AM
    Duration: 10:49:56.4414784
    Destination: External disk
    Start time: 8/11/2014 6:01:32 PM
    End time: 8/12/2014 4:51:29 AM
    Duration: 10:49:56.4414784
    4.
    Backup Assist reports via Win backup - Snapshot in progress
    Log Name:      Application
    Source:        BackupAssist
    Date:          8/12/2014 4:52:20 AM
    Event ID:      5634
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      mdnfile.Auxiant.local
    Description:
    Backup job Data backup failed with errors.
    Ultra critical error: Volume Shadow Copy Error 0x80042316 - snapshot set in progress
    Destination: Local directory
    Start time: 8/12/2014 4:52:10 AM
    End time: 8/12/2014 4:52:12 AM
    Duration: 00:00:02.7300000
    5.
    The Block Level Backup Engine service has stopped.
    6.
    Later...we tried manually stopping VSS and SWPRV services - only VSS had the issue.
    WBengine was not running...
    C:\>sc stop swprv
    SERVICE_NAME: swprv
            TYPE               : 10  WIN32_OWN_PROCESS
            STATE              : 3  STOP_PENDING
                                    (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
            WIN32_EXIT_CODE    : 0  (0x0)
            SERVICE_EXIT_CODE  : 0  (0x0)
            CHECKPOINT         : 0x0
            WAIT_HINT          : 0x0
    C:\>sc query swprv
    SERVICE_NAME: swprv
            TYPE               : 10  WIN32_OWN_PROCESS
            STATE              : 1  STOPPED
            WIN32_EXIT_CODE    : 0  (0x0)
            SERVICE_EXIT_CODE  : 0  (0x0)
            CHECKPOINT         : 0x0
            WAIT_HINT          : 0x0
    C:\>sc query wbengine
    SERVICE_NAME: wbengine
            TYPE               : 10  WIN32_OWN_PROCESS
            STATE              : 1  STOPPED
            WIN32_EXIT_CODE    : 0  (0x0)
            SERVICE_EXIT_CODE  : 0  (0x0)
            CHECKPOINT         : 0x0
            WAIT_HINT          : 0x0
    C:\>sc query vss
    SERVICE_NAME: vss
            TYPE               : 10  WIN32_OWN_PROCESS
            STATE              : 3  STOP_PENDING
                                    (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
            WIN32_EXIT_CODE    : 0  (0x0)
            SERVICE_EXIT_CODE  : 0  (0x0)
            CHECKPOINT         : 0x0
            WAIT_HINT          : 0x0
    C:\>sc stop vss
    [SC] ControlService FAILED 1061:
    The service cannot accept control messages at this time.  
    Log Name:      Application
    Source:        VSS
    Date:          8/12/2014 9:20:33 AM
    Event ID:      8225
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      mdnfile.Auxiant.local
    Description:
    The VSS service is shutting down due to shutdown event from the Service Control Manager.
    7.
    VSS still having issues here...not stopping!
    Log Name:      Application
    Source:        VSS
    Date:          8/12/2014 9:42:33 AM
    Event ID:      11
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      mdnfile.Auxiant.local
    Description:
    Volume Shadow Copy Service information:
    The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started.
    Most likely the CPU is under heavy load. [0x80080005, Server execution failed]
    8.
    Not sure why this is started again?
    Plus a DCOM timeout...
    Log Name:      Application
    Source:        Microsoft-Windows-Backup
    Date:          8/12/2014 9:31:13 AM
    Event ID:      753
    Task Category: None
    Level:         Information
    Keywords:     
    User:          SYSTEM
    Computer:      mdnfile.Auxiant.local
    Description:
    The Block Level Backup Engine service has successfully started.
    Event Xml:
    Log Name:      System
    Source:        Microsoft-Windows-DistributedCOM
    Date:          8/12/2014 9:31:43 AM
    Event ID:      10010
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      mdnfile.Auxiant.local
    Description:
    The server {E579AB5F-1CC4-44B4-BED9-DE0991FF0623} did not register with DCOM within the required timeout.
    9.
    Lots more errors about VSS...repeating Event ID's 11 and 8193...
    Log Name:      Application
    Source:        VSS
    Date:          8/12/2014 9:42:33 AM
    Event ID:      8193
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      mdnfile.Auxiant.local
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. 
    hr = 0x80080005, Server execution failed
    . Operation:
       Instantiating VSS server
    10.
    Then, finally stopping again...
    Log Name:      Application
    Source:        Microsoft-Windows-Backup
    Date:          8/12/2014 9:51:13 AM
    Event ID:      754
    Task Category: None
    Level:         Information
    Keywords:     
    User:          SYSTEM
    Computer:      mdnfile.Auxiant.local
    Description:
    The Block Level Backup Engine service has stopped.
    11.
    And still repeating 11 & 8193 at this point...as we write up this post.
    12.
    This was suggested by the Backup Assist - software vendor....
    A.)
    ...for 0x81080101:
    "ERROR - The shared restore point operation failed with error (0x81000101)
    The creation of a shadow copy has timed out. Try again this operation."
    If you receive the above error in your report, we have recently found a registry key which
    contains the timeout value set by Microsoft for VSS and found that you can edit this to extend it.
    To get to the registry key, open Regedit (Start > Run > Regedit) and browse to:
    "HKLM\Software\\Microsoft\\Windows NT\\CurrentVersion\\SPP\\CreateTimeout".
    Change value to 1200000 (2*10*60*1000 = 20 mins).
    The default for the timeout period is 10 mins so hopefully doubling this will give enough time to
    complete the snapshot.
    If this isn't present, you'll need to manually enter the registry key. It's a DWORD 32-bit key.
    --> NOTE: HAve not done this yet.
    B.)
    And for 0x80080005...
    http://support.microsoft.com/kb/870655/en-gb
    Our server does have high CPU load at times...
    13.
    Another post from technet mentions system volume size - here is our layout below:
    A.)
    OS/system Disk...
    DISKPART> list disk
      Disk ###  Status         Size     Free     Dyn  Gpt
      Disk 0    Online          278 GB      0 B    (System Vol = C: Drive - OS w/ Programs and batch jobs)
      Disk 1    Online         2791 GB      0 B        *    (Data drive - DFS, rsync,etc. run on D: Drive)
      Disk 2    Online         1863 GB      0 B    (USB 2/3.0 - Enclosure w/ SATA disk = 2GB formatted w/ NTFS.)
    DISKPART> detail disk
    DELL PERC H710P SCSI Disk Device
    Disk ID: CA0DEEA5
    Type   : RAID
    Status : Online
    Path   : 1
    Target : 0
    LUN ID : 0
    Location Path : PCIROOT(0)#PCI(0100)#PCI(0000)#RAID(P01T00L00)
    Current Read-only State : No
    Read-only  : No
    Boot Disk  : Yes
    Pagefile Disk  : Yes
    Hibernation File Disk  : No
    Crashdump Disk  : Yes
    Clustered Disk  : No
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      Volume 1         RECOVERY     NTFS   Partition   3072 MB  Healthy    System
      Volume 2     C   OS           NTFS   Partition    275 GB  Healthy    Boot
    B.)
    Backup disk...
    ST320006 41AS USB Device
    Disk ID: 801AF48C
    Type   : USB
    Status : Online
    Path   : 0
    Target : 0
    LUN ID : 0
    Location Path : UNAVAILABLE
    Current Read-only State : No
    Read-only  : No
    Boot Disk  : No
    Pagefile Disk  : No
    Hibernation File Disk  : No
    Crashdump Disk  : No
    Clustered Disk  : No
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      Volume 4     F   BACKUPS      NTFS   Partition   1863 GB  Healthy
    C.)
    NOTE:
    Also on disk 0(system Disk) - we have a small OEM partition = 39MB and a Recovery Partition = 3GB.
    D.)
    Issues with WBAdmin now...
    C:\>wbadmin get disks
    wbadmin 1.0 - Backup command-line tool
    (C) Copyright 2004 Microsoft Corp.
    ERROR - A Volume Shadow Copy Service operation error has
    occurred: (0x80042302)
    A Volume Shadow Copy Service component encountered an unexpected error.
    Check the Application event log for more information.
    14.
    Ran "Check-Disk" -no errors...
    C:\>chkdsk
    The type of the file system is NTFS.
    The volume is in use by another process. Chkdsk
    might report errors when no corruption is present.
    Volume label is OS.
    WARNING!  F parameter not specified.
    Running CHKDSK in read-only mode.
    CHKDSK is verifying files (stage 1 of 3)...
      116224 file records processed.
    File verification completed.
      654 large file records processed.
      0 bad file records processed.
      0 EA records processed.
      76 reparse records processed.
    CHKDSK is verifying indexes (stage 2 of 3)...
      156676 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered.
    CHKDSK is verifying security descriptors (stage 3 of 3)...
      116224 file SDs/SIDs processed.
    Security descriptor verification completed.
      20227 data files processed.
    CHKDSK is verifying Usn Journal...
      35628352 USN bytes processed.
    Usn Journal verification completed.
    Windows has checked the file system and found no problems.
     289233919 KB total disk space.
     100241492 KB in 85477 files.
         57380 KB in 20228 indexes.
             0 KB in bad sectors.
        226627 KB in use by the system.
         65536 KB occupied by the log file.
     188708420 KB available on disk.
          4096 bytes in each allocation unit.
      72308479 total allocation units on disk.
      47177105 allocation units available on disk.
    15.
    There are no backup error logs here - only .etl files...
    C:\Windows\Logs\WindowsServerBackup\
    Wbadmin.1.etl = 9:42AM on 8/12
    Wbadmin.2.etl = 4:51AM on 8/12
    Per windows Win troubleshooting:
    http://technet.microsoft.com/en-us/library/ee692290(WS.10).aspx
    http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx
    --> Related to Windows backup and not VSS?
    2155348001 - 0x80780021 - Windows Backup timed-out before the shared protection point was created.
    Should we run the "FIXVSS08.BAT" script - restarts services and re-registers DLL's - does this ever help?
    Will this server need a reboot since VSS is in a state and we can't even test backups?
    Is there a tool we can use to debug VSS or troubleshoot or OS backups further?
    MSReport/Diag, VSS debugging, or another way of helping fix our OS(SystemState/C: drive) backup issues?
    Any help is greatly appreciated - thx.
    -SP
    Scot Pichelman

    Hi Scot,
    Sometimes a third party backup application will change the default VSS provider adding VSS writers which causes Windows Server Backup using an incorrect component in doing backup, that's why I suggest to delete it for a test. Anyway you can reinstall it
    after testing.
    And as you said a high-load CPU could also be the cause of the issue so you may need to first rule hardware effective out.
    If issue still exists, please try the steps below as well:
    1. Please check DCOM Server Process Launcher service is started.
    2. If not, try to change RPC service to run as SYSTEM account. To do this please modify the following key:
    Note: Backup the key before edit incase it cause any issue.
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\RpcSs\
    Find "ObjectName" and change the value to LocalSystem.
    Reboot to see if DCOM back to work and if Windows Server Backup starts working. If not, please provide the result if there is any new error occurs.
    If DCOM still not work, please compare the content of the following key with a working server:
    HKEY_LOCAL_MACHINE\Software\Microsoft\OLE
    Edit if there is any difference and make sure you created a backup of the key before editing. 
    If you have any feedback on our support, please send to [email protected]

  • Why can't I boot from an external scsi drive?

    In a previous post, I mentioned that my hard drive died. While trying to find ways to work around it, I dug out an old 4 GB SCSI drive I used to use with my old Mac, and hooked it up. When I booted from the OS 10.3 install disk, I was aboe to install the OS on the external drive, and choose it as the startup drive before rebooting. When I rebooted, however, the Mac could not see the SCSI drive as a startup drive. I tried it several times, changed the SCSI ID, erased the drive and reloaded the OS, repaired the directory with Disk Warrior, all with the same results.
    What am I doing wrong?
    Dave

    What model SCSI card do you have installed? Some cards are driver-based, like the Adaptec 2906. Its driver is loaded from the boot drive, as the extensions are displayed across the screen during the startup process. As such, drives connected to that type of card can't be designated as the boot device. A newer SCSI card that's firmware-based, like the Adaptec 2930, can be used for booting the computer. If you have a card that's firmware-based, then you may need to update the firmware with a newer (Mac OS X) compatible version.

  • Quadra 800 and internal SCSI drive

    Could somebody advise me whether I can replace the second internal SCSI drive in Quadra 800 (MacOS 7.5) with something bigger and newer? I have a new Seagate Cheetah 73Gb internal SCSI drive (68-pin). Is there any way to use it in the Quadra? Is there any adapter that could be used for that?

    Yes, but.
    The largest Volume supported on that Mac, provided you are running 7.5 or later, is 4 GB. So you would have to create about 19 partitions (Volumes) to use all the 73 GB. The full story is in this article about Standard Format -- Extended Format requires OS 8.1 or later:
    8647- Macintosh: \[Standard] File System Specifications and Terms
    Volume
    A volume is either a full disk, or a section of a disk, partitioned into separate parts. If you partition a single drive then each partition is considered a volume.
    The maximum volume size under System 6 and System 7 is 2 GB. System 7.5 increased that limit to 4 GB and System 7.5.2 (and later) increases that limit to 2 TB on some computers, including:
    - any computer that came with System 7.5.2 or newer. \[your Quadra 800came with 7.1 and an enabler]
    - any Macintosh computer with PCI slots.
    That 68-pin drive likely could use wide transfers and much higher speeds, but can be made backward compatible through careful use of adapters. Alternatiively, you could install a NuBus card to connect to it directly.

  • OS 8.1 - Trying to partition an external scsi drive and backup data.

    Have an Apple PowerMac 6000 series minitower at work. It runs a program called 4D, that is a database we use to catalog images. Since I've been with the company, there has been no backup of the database, as an external scsi drive had died and never been replaced.
    Since the system is running OS 8.1, I wasn't sure how I could do any sort of network backup, and in the end I managed to get a new 50-pin scsi 50GB LaCie External Hard drive with the 25-pin cable to connect to the PowerMac. Connected it yesterday, and it did appear on the desktop as you'd expect.
    But when I went to point 4D to the drive, it didn't seem to recognize the file system. I tried erasing the drive, but it had the same probem. Norton Utilities is on the mac, so I tried replacing the partition. Specifically, I tried creating two partitions. One that's 40GB, that I could do 4D backups to. The other, the remaining space (about 7GB) so I could try to copy the entire drive to that partition and maybe even boot from it if the other drive failed.
    However, the drive was still mounted when I tried to repartition and it ended up causing an error. I tried rebooting, and the drive wasn't showing on the desktop, but it still wouldn't repartition. Not knowing was else to do, I low level formatted the drive, told it to write zeros to it, and then create the two partitions. Given I was doing all this on a Saturday and didn't know how long it would take, I left it running in the background to check on Monday.
    Anyone have any experience with OS 8.1? Is there a program like Carbon Copy Cloner that works with that OS? And any thoughts on what I'd need to do to get this drive working as indicated above? I started using Apple again with OS X, and it's quite a bit different than 9 and previous. Could sure use some help.

    Hi, merkman2001 -
    I would use the Apple utility Drive Setup (which comes with a normal OS 8.1 install) to initialize and partition the drive, rather than Norton or any other third-party utility.
    As far as the format type goes, select Mac OS Extended when asked.
    <hr>
    Is there a program like Carbon Copy Cloner that works with that OS?
    Generally such is not needed with OS 9 and earlier OS versions. All pre-OSX OS's and software can be copied using a Finder (drag and drop) copy process, and remain usable.
    This means that the System Folder on the internal drive can be dragged to the icon of the external drive and dropped into it. Ditto any/all additional folders, those containing the programs and documents.
    You should be able to successfully do a test boot using the freshly-copied OS on the external drive; this is the best way to verify the integrity of the copied OS.
    Can't recall if aliases were used in OS 8.1. If they were, it may be necessary to 'fix' any of them used, since the pathname contained in an alias is not corrected when it is copied to another drive - it continues to point to the original original.
    You can also copy the entire source drive to the external one in one action - drag the iccon of the internal drive to that of the external one and drop it in.
    After Finder gets done copying everything (this may take some time, so disable any sleep mode or screensaver), there will be a new folder on the external volume - this folder will be named the same as the internal drive. Inside that folder will be a copy of everything that was on the internal drive, including everything left lying around on the desktop and anything left unemptied in the Trash (these will be placed in new folders named "Desktop" and "Trash" respectively).
    In order to make that external volume bootable using the freshly copied OS, move the System Folder out of the folder it was copied into, so that it is at the root level of the drive, meaning visible in the window that appears when you first open the drive's icon.

  • How do you solve a DVD drive recognition conflict between Windows 7 and iTunes?

    After doing an iTunes reinstall to resolve another issue, I discovered that my PC running Windows 7 would not recognize my DVD burner, drive E:
    when attempting to do a backup to a DVD disk. Window 7 Device Manager indicated that there was a registry issue and assigned a code 19. I called Microsoft Support and they want into my Windows registry and made the required changes to correct the problem for $99 as the OS is out of support. I bring this issue to your attention in case you have a similar DVD recognition issue if you do an iTunes reinstall. The issue has been resolved. However, when I open iTunes now, I get a message as follows:
    "The registry used by the iTunes drivers for importing and burning CDs and DVDs are missing. This can happen as a result of installing other CD burning software". I did not install other CD burning software. Only iTunes was reinstalled. I can still import CDs into iTunes using my DVD drive so I ignore this annoying message every time I open iTunes. I am an iPad 2 user on iOS 6.
    Casey9

    Thanx b Noir for your recommendation. I did not see your recommended solution from my search. As a user with medium IT technical skills, I would only put this caveat out there that any time you change a system registry your risk is very high and the downside consequences can be severe due to any error e.g. A space or incorrect character, incorrect instruction, etc. So each user should decide based on their own experience and confidence level which remediation route they should take - third party remediation or do it yourself help.
    Casey9

  • Adding 2nd hard drive(IDE 40gig)  to B&W G3 w/ 9gig SCSI drive

    Recently got a 450 B&W G3 with a 9gig SCSI ultra something drive in it already and i would like to add a 40gig IDE drive as a second. the scsi drive is hooked through a scsi card and is the main drive. i want to just add the second drive for more storage. when i plug up the drive and start up, it does not see the drive. I know i'm missing something little to get this to work, but I don't know alot of the techincal terms and meanings to ask the right questions. any help or if someone can direct me to an older article that might help would be great!!! Thanks!!

    Hi, Papa -
    Welcome to Apple's Discussions.
    Make sure the drive is jumpered correctly. There is a block of exposed pins at the same end of the drive where the power cable and data cable are attached. On those exposed pins will be one or more little plastic-looking things bridging pin pairs - these are the jumpers.
    There should be a label affixed to the drive in the vicinity of the jumper pin block; this label depicts the various configurations of where jumpers should be placed for various settings.
    For your model Mac, you should use the jumper setting for "Master". Exception - if the drive is a Western Digital brand, it may have a setting named "Single" - if so, you should use that when the drive is the only device on the bus.
    If you have not yet initialized (formatted) the drive, do so. Most drives are not usable until they have been prepared for a Mac by initializing the drive; initializing a drive places Mac drivers on it, and structures the platter for use by the OS.
    You can use OSX's Disk Utility to initialize the drive. There should be sufficient info in OSX's Help section to use Disk Utility to do that. Some items of note -
    • If you want that drive to be accessible when the machine is booted to OS 9 at some time, be sure to select the option to install OS 9 drivers.
    • Select "Mac OS Extended" as the format for the drive.

  • Quicksilver scsi drive size limit ?

    Hello all.
    The original 37gig SCSI drive on my Quicksilver (NOT mirror door) is beginning to sing a sad song so I am looking into replacement.
    I know there is a 128gig size limit for ATA drives in this model but is there any size limit for internal SCSI ????
    I have already added a 120gig ATA with my original 80gig ATA so I think I'm pretty well maxed out (heat and power wise) on internal ATA drives.
    Due to the cost of SCSI drives I'm thinking what I may do is buy an external LARGE firewire dive, transfer the contents of my internal SCSI drive to that firewire drive and then just use the SCSI drive as a dedicated "video capture" drive until it finally dies.
    So, besides the original question about SCSI drive size limits does anyone have anythoughts on going external firewire vs. additional internal drives?
    Thanks.
    Gary
    933mhz PowerPC G4 Mac OS X (10.2.x)

    Hello! If speed is an issue get a sata Raptor drive (most 36 or 80 gigs). The access time is as fast as a 10,000 rpm scsi drive. Just add a sata card to use the sata drive. Tom

  • Adding SCSI drives to my 2001 G4 Quicksilver Dual 800?

    I'm thinking about adding additional SCSI drives to my Dual 800. I ordered my G4 Quicksilver with a 10,000rpm Seagate Cheeta and now want to add another Seagate SCSI. I'm choosing Seagate for no other reason than to stay using a product that has been successful for me. My questions are (enter drum roll here)..... how big of SCSI drive can I install??? What should I check out before doing so? What problems may I encounter?
    2001 QuickSilver G4   Mac OS X (10.4.8)   Dual 800/1.5gig memory
    QuickSilver G4   Mac OS X (10.3.9)  

    I expect it may be an Adaptec or Atto SCSI card. If you open the case and have a look there's probably a make and model stamped on the card itself. You may be able to find the information from the manufacturers web site:
    http://www.adaptec.com/en-US/support/mac/
    http://www.adaptec.com/en-US/support/scsi/
    http://www.attotech.com/software/manuals.html
    Alternatively I guess you could send them an email and hope you get a useful response.

  • Usb or Firewire adaptor that would fit a 25 pin scsi cord?

    I have an old Iomega 100 ZIP reader that was compatible with my G3, when my G3 died I had no way to access the zips with my new Macbook Pro, since there is no SCSI port.
    Is there an USB or Firewire adaptor I can purchase that will connect to the 25 pin SCSI cord so I can hook up my Zip reader?
    If there is not an adaptor, does anyone know how or where I can back up these files to cd's?
    Thanks.

    Welcome to Apple Discussions!
    There is a device here that converts UltraSCSI to FireWire, but the ZIP 100 is not Ultra. It's an expensive gadget.
    You could probably find a used external ZIP 100 USB fairly cheap. See:
    http://www.amazon.com/Iomega-Zip-100-Portable-Drive/dp/B00000J3Q7
    We have one and used it to move all the files we'd put on ZIPs from two old Macs with SCSI ZIP drives to our newer non-SCSI Macs.

  • SCSI Drive R.I.P.?

    Hi all,
    Well, I've been trying see if I can resuscitate my 4GB SCSI drive that has bad blocks, ("major error was found in the disk surface". Booted off the CD (OS9x), and started the Drive SetUp/Write Zeros process. Moved along normally at first, but then after about 3/4s of the way through, it stalled out. It's now been stuck in this same spot for about 3hrs now, (beach ball spinning, but progress bar is not moving).
    Even though the process hasn't completed, should I reboot off the CD and try again, or is there something else I should be doing (like holding a funeral)?
    TIA,
    ~ Kathleen

    Hi Allan,
    Your experience sounds similar to mine. My problem though started, (I believe), with a power surge to my system (and yup, I even had it hooked up to an APC battery/surge protector). Deceivingly so though, everything kept functioning pretty well. I ran the usual utilities:
    - Disk 1st Aid - nothing reported wrong
    - Disk Warrior - all went well here
    - Norton Disk Doctor - reported some bad blocks, but nothing out of the "norm".
    - Ran the Defrag. Everything o.k.
    All seemed well again, but not too much later, when I went to do another back up, all sorts of errors started showing up - could barely get the few new files that I needed copied onto CDs. Like you, I started having problems opening Apps, so I ran the utilities again. The last one I ran (Norton Disk Doctor) ended up stalling out during the check disk phase. I let it run (spin) for a day or so...finally got the major error/bad block message - that it couldn't fix. After that, the disk just seemed to keep deteriorating and I could never again get Norton to run through the whole disk.
    I'm aware of all those warnings about Norton, but I've been rather lucky with it myself for the last 7-8yrs. In this case, I don't think Norton was the culprit. I suspect rather that it was caused by a possessed transformer on the property that turned my computer into Frankenstein's laboratory.
    So, (as you may have seen in my other posts looking for advice re: SCSI & SATA drives, PCI cards, etc), I had a feeling this drive was toast, but Grant kindly gave me one last "glimmer of hope tip" to try. (Today's the 1st day that I've had a block of time available to do the whole erase & reinstall dance). I was figuring that if the damage wasn't going to be too severe, and if I could resuscitate the drive, I would probably only use it as a scratch disk - no data. (I'm guessing here now that that would be an ok use for it?)
    I did get a Seagate 160GB Ultra ATA drive that was on sale for about $40 - not bad!. Thought I would use it as an external back up. Considering another SCSI, but may go for the SATA WD Raptor instead for the primary internal drive.
    Thanks Allan for taking the time to write about your experience. I greatly appreciate everyones feedback and advice here.
    Best regards,
    ~ Katheen

  • SCSI drive on SCSI controller card wont mount using OSX leopard

    My SCSI drive on a SCSI controller PCI card wont mount using OSX Leopard. It mounts fine using OSX Tiger 10.4.11
    How can I make it mount on Leopard?

    I have PowerMacs G4 Quicksilvers with SCSI drives running 10.5.8. They boot and run OK without an added driver, faster with an added driver for their ATTO cards.
    What card are you using?

  • Caldera Graphics SCSI Driver - Removing

    I guess I'm basically stupid but I can't seem to figure out how the "Caldera Graphics SCSI Driver" gets attached/installed when booting Solaris8 on my Sun Blade 100.
    There is a startup script for Caldera Cameleo that I've disabled but that doesn't prevent this device driver from being attached/installed at boot time.
    I've checked /etc/system but find no reference to the Caldera device driver there.
    I've looked in /kernel/drv but, again, find no reference to it either in any sort of file name or as some sort of specification within any of the existing *.conf files.
    I'm having difficulty (as in, no success whatsoever) getting an HP "SureStore DAT40" (C5683A C908, according to probe-scsi-all) configured (connected to a newly-added Sun dual-channel single-ended ultra-wide SCSI adapter (X6540A)) and added to /dev/rmt but, it seems to be ignored regardless of how many "boot -r" attempts I make.
    Grasping at straws, here, I thought that this Caldera thing might be interfering so I'm trying to get rid of it. Even if it's not interfering I really don't want it now and I want to suppess it from attaching/ installing.
    Can some kind soul point me in the right direction for removing this thing?
    Thank you so much!
    Best Regards,
    Mark Dalton

    Hi,
    Your PC has on a on board video processor on the motherboard.  If you remove the failed video card, then the bios will switch to the on board video video processor when it no longer detects a presence of a video card in the PCI-E x16 slot.
    The ATI x1950 requires a 450 watt power supply and your PC only has a 250 watt power supply.
    HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
    HP Photosmart Premium C309G, HP Photosmart 6520
    HP Touchpad, HP Chromebook 11
    Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
    Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
    Windows 7/8 UEFI/Legacy mode, MBR/GPT

Maybe you are looking for