Data drive

We have a HP 500 208-aWe bought it because it had a 3 TB hard drive. It is broken up into 3 partitions Windows (C) (1.99GB), a DATA dive (D) 2.51 TB, and a recovery partition, (E) 14.9 GB. The C drive is where the files/folders are stored by default and keeps getting filled up quickly so my wife has transferred them to an external drive. The D drive is completley free. The recovery E is nearl;y full. I would have thought that files pictures documents folder etc should go to the DATA drive (D) by default, but my wife insists that it is somehow used for recovery and shouldn't be written on. Thanks, Valour Am I correct that the files should be getting stored ontp the data drive and how do we make the computer do that by default?

Lets make some sense of that hard drive:"We have a HP 500 208-a. We bought it because of the 3 TB hard drive. However, the partition is broken up into Windows drive (c) which has 199 GB, a data drive (D), which is 2.51 TB, and a recovery image (E) which is 14.0GB".The C partition is where everything happens, it's the default. It has the Windows Operating System, all user accounts, and all the data files.  The Recovery partition is supposed to be that small, as it's sole purpose is Recovery of the Operatimg System (only the Operating system) in case of a failure with the OS.What you have is an large 2.5TB (D) partition. You can manually move data files to this area. Store a few 4-6 GB movies, store that large music collection, or whatever.

Similar Messages

  • Crystal Reports XI String [255] limit with the File System Data driver...

    I was trying to create a Crystal Reports XI report to return security permissions of files and folders.  I have been able to successfully connect and return data using the File System Data driver as the Data Source; however the String limit on the ACL NT Security Field is 255 characters.  The full string of data to be returned can be much longer than the 255 limit and I cannot find how to manipulate that parameter. 
    I am currently on Crystals XI and Crystal XI R2 and have applied the latest service packs but still see the issue.  My Crystal Reports Database DLL for File System data ( crdb_FileSystem.dll ) is at Product Version 11.5.10.1263.
    Is it possible to change string limits when using the File System Data driver as the Data Source?  If so, how can that be accomplished.  If not, is there another method to retrieve information with the Windows File System Data being the Data Source?  Meaning, could I reach my end game objective of reporting on the Windows ACL's with Crystal through another method?

    Hello,
    This is a known issue. Early versions you could not create folder structures longer than 255 characters. With the updates to the various OS's this is now possible but CR did not allocate the same space required.
    It's been tracked as an enhancement - ADAPT01174519 but set for a future release.
    There are likely other ways of getting the info and then putting it into an Excel file format and using that as the data source.
    I did a Google search and found this option: http://www.tomshardware.com/forum/16772-45-display-explorer-folders-tree-structure-export-excel
    There are tools out there to do this kind of thing....
    Thank you
    Don
    Note the reference to msls.exe appears to be a trojan: http://www.greatis.com/appdata/d/m/msls.exe.htm so don't install it.
    Edited by: Don Williams on Mar 19, 2010 8:45 AM

  • DAT Drive not registering on sunfire V240

    Hi,
    I have 9 SUN v240 with which i connected the same DAT drive HP 72GB DDS DAT (PART NUMBER C7439). In six servers
    did devfsadm and it registered the DAT. It worked fine but in three of the SUN v240, this command doesnt seem to
    do anything. /dev/rmt is not created. I cannot restart the server because they are live/production servers. Is there
    any other solution to get this DAT recognised in solaris with out a reboot. Also, i cannot go to OBP (OK prompt) because
    ofcourse it needs a reboot.
    I checked the st.conf file and the entries of these file are the same in all 9 v240. So i think its not a problem of
    st.conf.
    Eargerly waiting for a solution.
    Here are some of the command outputs from 1 of the 3 servers which donot see the DAT:
    [root@vbsmf /kernel/drv] $strings /kernel/drv/st.conf | grep st
    # Copyright (c) 1995-2000 by Sun Microsystems, Inc.
    "@(#)st.conf
    # devices of Sun Microsystems and many 3rd party devices.
    # 1 Drive is configured automatically - no entry is needed in st.conf.
    # The 3rd party devices do apparently work with the configurations listed.
    # the past, but have not been tested by Sun Microsystems. Use these entries
    # as your starting point for generating your configuration entries.
    #tape-config-list=
    name="st" class="scsi"
    name="st" class="scsi"
    name="st" class="scsi"
    name="st" class="scsi"
    name="st" class="scsi"
    name="st" class="scsi"
    name="st" class="scsi"
    #name="st" class="scsi"
    #name="st" class="scsi"
    #name="st" class="scsi"
    #name="st" class="scsi"
    #name="st" class="scsi"
    #name="st" class="scsi"
    #name="st" class="scsi"
    #name="st" class="scsi"
    name="st" parent="fp" target=0;
    [root@vbsmf /kernel/drv] $cfgadm configure
    Ap_Id Type Receptacle Occupant Condition
    configure: No matching library found
    [root@vbsmf /kernel/drv] $cfgadm -al
    Ap_Id Type Receptacle Occupant Condition
    c0 scsi-bus connected configured unknown
    c0::dsk/c0t0d0 CD-ROM connected configured unknown
    c1 scsi-bus connected configured unknown
    c1::dsk/c1t0d0 disk connected configured unknown
    c1::dsk/c1t1d0 disk connected configured unknown
    c2 scsi-bus connected unconfigured unknown
    [root@vbsmf /kernel/drv] $cfgadm configure c2
    Ap_Id Type Receptacle Occupant Condition
    c2 scsi-bus connected unconfigured unknown
    configure: No matching library found
    [root@vbsmf /kernel/drv] $cfgadm -val
    Ap_Id Receptacle Occupant Condition Information
    When Type Busy Phys_Id
    c0 connected configured unknown
    Jan 1 1970 scsi-bus n /devices/pci@1e,600000/ide@d:scsi
    c0::dsk/c0t0d0 connected configured unknown unavailable
    Jan 1 1970 CD-ROM y /devices/pci@1e,600000/ide@d:scsi::dsk/c0t0d0
    c1 connected configured unknown
    Jan 1 1970 scsi-bus n /devices/pci@1c,600000/scsi@2:scsi
    c1::dsk/c1t0d0 connected configured unknown FUJITSU MAT3073N SUN72G
    Jan 1 1970 disk n /devices/pci@1c,600000/scsi@2:scsi::dsk/c1t0d0
    c1::dsk/c1t1d0 connected configured unknown FUJITSU MAT3073N SUN72G
    Jan 1 1970 disk n /devices/pci@1c,600000/scsi@2:scsi::dsk/c1t1d0
    c2 connected unconfigured unknown
    Jan 1 1970 scsi-bus n /devices/pci@1c,600000/scsi@2,1:scsi
    [root@vbsmf /kernel/drv] $ls /dev/rmt/0
    /dev/rmt/0: No such file or directory
    [root@vbsmf /kernel/drv] $ls /dev/rmt
    [root@vbsmf /kernel/drv] $devfsadm -v
    [root@vbsmf /kernel/drv] $ls /dev/rmt
    [root@vbsmf /kernel/drv] $ls /dev/rmt/0
    /dev/rmt/0: No such file or directory
    [root@vbsmf /] $modinfo
    Id Loadaddr Size Info Rev Module Name
    6 10158000 445b 1 1 specfs (filesystem for specfs)
    8 1015dd40 333c 1 1 TS (time sharing sched class)
    9 10160938 8d4 - 1 TS_DPTBL (Time sharing dispatch table)
    10 101609c0 291e3 2 1 ufs (filesystem for ufs)
    11 10187b33 1f7 - 1 fssnap_if (File System Snapshot Interface)
    12 10187c83 10900 226 1 rpcmod (RPC syscall)
    12 10187c83 10900 226 1 rpcmod (32-bit RPC syscall)
    12 10187c83 10900 1 1 rpcmod (rpc interface str mod)
    13 10195cc3 66f08 0 1 ip (IP Streams module)
    13 10195cc3 66f08 3 1 ip (IP Streams device)
    14 101f30bb 1982 1 1 rootnex (sun4u root nexus 1.91)
    15 101f4648 210 57 1 options (options driver)
    17 101f4d3c 18d8 12 1 sad (Streams Administrative driver's)
    18 101f639c 67b 2 1 pseudo (nexus driver for 'pseudo')
    19 101f68a5 1c228 85 1 md (Meta disk base module)
    24 1023362d 5234 - 1 md_stripe (Meta disk stripes module)
    25 1023847d a760 - 1 md_mirror (Meta disk mirrors module)
    26 10242765 10338 109 1 pcisch (PCI Bus nexus driver 1.201)
    27 1025111d 1023b 50 1 glm (GLM SCSI HBA Driver 1.166.)
    28 1025f310 8ac0 - 1 scsi (SCSI Bus Utility Routines)
    29 10264fe4 18008 32 1 sd (SCSI Disk Driver 1.356)
    33 1029bf1e a52d 135 1 uata (ATA controller Driver 1.89)
    34 102a5713 151f - 1 dada ( ATA Bus Utility Routines)
    37 102a7141 93c - 1 todm5819p_rmc (tod module for ALI M5819P)
    38 102a7a0b 344f 196 1 rmc_comm (rmc_comm driver, v1.2)
    39 102aaa92 508 199 1 pmugpio (Pmugpio Driver 1.1)
    40 780b8000 72bf - 1 ufs_log (Logging UFS Module)
    41 1027bd5c 1b04a 5 1 procfs (filesystem for proc)
    42 102962ba fab 126 1 ebus (ebus nexus driver)
    43 10296efd 2fcd 194 1 mc-us3i (Memory-controller: v1.1)
    44 10299bba d98 134 1 power (power button driver v1.9)
    45 1029a7aa 1016 159 1 pmubus (pmubus nexus driver)
    46 10211abd 5cb6 197 1 rmclomv (rmclomv control driver v1.4)
    47 1021684b 256a 9 1 pcf8584 (I2C Nexus Driver 1.13)
    48 102a689a 464 - 1 i2c_svc (I2C module ver 1.2)
    50 102aae3a 10628 8 1 sockfs (filesystem for sockfs)
    52 102a6c7b 6be 11 1 clone (Clone Pseudodriver 'clone')
    53 1029b5f0 304 2 1 ip6 (IP Streams module)
    53 1029b5f0 304 143 1 ip6 (IP Streams device)
    54 102bafd2 25e40 3 1 tcp (TCP Streams module)
    54 102bafd2 25e40 42 1 tcp (TCP Streams device)
    55 10219963 1059 - 1 md5 (MD5 Message-Digest Algorithm)
    56 1029b734 365 4 1 tcp6 (TCP Streams module)
    56 1029b734 365 146 1 tcp6 (TCP Streams device)
    57 1021a907 9b50 5 1 udp (UDP Streams module)
    57 1021a907 9b50 41 1 udp (UDP Streams device)
    58 1029b8d9 365 6 1 udp6 (UDP Streams module)
    58 1029b8d9 365 145 1 udp6 (UDP Streams device)
    59 1022292f 7f10 7 1 icmp (ICMP Streams module)
    59 1022292f 7f10 5 1 icmp (ICMP Streams device)
    60 1029ba7e 30e 8 1 icmp6 (ICMP Streams module)
    60 1029ba7e 30e 144 1 icmp6 (ICMP Streams device)
    61 10228ea7 651b 9 1 arp (ARP Streams module)
    61 10228ea7 651b 44 1 arp (ARP Streams driver)
    62 1022e16a 4b93 10 1 timod (transport interface str mod)
    64 102d9d66 c83 16 1 conskbd (Console kbd Multiplexer driver )
    65 102da65d 1ffa 15 1 wc (Workstation multiplexer Driver )
    66 102dba4f 4885 37 1 su (su driver 1.47)
    67 102dff2c 3f2e 1 1 elfexec (exec module for elf)
    67 102dff2c 3f2e 0 1 elfexec (32-bit exec module for elf)
    68 102e3d57 3400 3 1 fifofs (filesystem for fifo)
    69 102e6ebf adea 11 1 ldterm (terminal line discipline)
    70 102f13b6 246d 12 1 ttcompat (alt ioctl calls)
    71 102f365a 9223 29 1 zs (Z8530 serial driver V4.125)
    72 102fc375 1568 26 1 ptsl (tty pseudo driver slave 'ptsl')
    73 102fd645 211f 25 1 ptc (tty pseudo driver control 'ptc')
    77 10318d3b 116a9 - 1 usba (USBA: USB Architecture 1.25)
    78 10313719 498c - 1 usbser (USB generic serial module 1.1)
    80 1032d854 15ac5 - 1 usba10 (USBA10: USB 1.0 Architecture 1.)
    81 781b6000 4012 - 1 usba10_usbser (USBA10 Generic Serial Modul
    82 10344153 1c30 13 1 rts (Routing Socket Streams module)
    82 10344153 1c30 43 1 rts (Routing Socket Streams device)
    83 781e8000 f487 15 1 ipsecesp (IP Encapsulating Security Paylo)
    83 781e8000 f487 141 1 ipsecesp (IP Encapsulating Security Paylo)
    84 7814e000 ff46 14 1 ipsecah (IP Authentication Header Stream)
    84 7814e000 ff46 140 1 ipsecah (IP Authentication Header Stream)
    85 7803c000 4af3 105 1 tl (TPI Local Transport Driver - tl)
    86 78042000 44ab 16 1 keysock (keysock module)
    86 78042000 44ab 139 1 keysock (PF_KEY Key Management Socket ST)
    87 78040743 16ea 97 1 sysmsg (System message redirection (fan)
    88 780416bd 82c 0 1 cn (Console redirection driver)
    89 780e3c1a 475 2 1 intpexec (exec mod for interp)
    90 78041d59 2c3 42 1 pipe (pipe(2) syscall)
    90 78041d59 2c3 42 1 pipe (32-bit pipe(2) syscall)
    91 10354c78 f9d 13 1 mm (memory driver)
    92 78046000 8a90 195 1 bge (BCM570x driver v0.22)
    93 7804e000 e868 - 1 gld (Generic LAN Driver (v2))
    94 7805e000 4eac6 217 1 ce (CE Ethernet Driver v1.135)
    95 780b0000 2bd7 - 1 vlan (Ethernet VLAN module (v1) 1.18)
    97 780b4000 322b 115 1 pci_pci (Standard PCI to PCI bridge nexu)
    98 780b7ad5 5ac 19 1 dump (crash dump driver)
    99 780c0000 4421 201 1 doorfs (doors)
    99 780c0000 4421 201 1 doorfs (32-bit door syscalls)
    100 780c6000 2d06 88 1 devinfo (DEVINFO Driver 1.33)
    103 780ca000 ebf8 66 1 ohci (USB OpenHCI Driver 1.23)
    104 781579c6 c03 176 1 inst_sync (instance binding syscall)
    104 781579c6 c03 176 1 inst_sync (32-bit instance binding syscall
    105 780d4c38 1538 4 1 namefs (filesystem for namefs)
    106 7814c6d0 1a98 4 1 logindmux ( LOGIND MUX Driver)
    110 780bf047 d70 14 1 iwscn (Workstation Redirection driver )
    111 7804d698 a4f 17 1 consms (Mouse Driver for Sun 'consms' 5)
    113 780b6bbb 9f7 21 1 log (streams log driver)
    114 780b734a 8f3 22 1 sy (Indirect driver for tty 'sy')
    115 780c8b56 cc4 23 1 ptm (Master streams driver 'ptm')
    116 10342e11 dc6 24 1 pts (Slave Stream Pseudo Terminal dr)
    117 780c5670 a8c 31 1 seeprom (I2C serial EEPROM device driver)
    120 1030a1c5 6a30 - 1 fctl (Sun FC Transport Library v1.12)
    123 780c411c 17ec 34 1 smbus (SMBUS nexus Driver 1.6)
    124 10308a8f 1dea 35 1 random (random number device v1.1)
    125 780e0000 2290 17 1 authsha1 (SHA1-HMAC algorithm)
    127 780b2637 1f01 38 1 openeepr (OPENPROM/NVRAM Driver v1.7)
    131 78188000 30bc0 - 1 s1394 (IEEE 1394 Services Library 1.0)
    143 10355a75 2e1f - 1 hidparser (HID PARSER 1.5)
    146 103256b4 2d2e 60 1 fssnap (snapshot driver)
    153 781af8c7 820 72 1 ksyms (kernel symbols driver)
    156 10345623 2d73 - 1 usba10_hidparser (USBA10 HID PARSER 1.1)
    161 780e2467 1a23 81 1 winlock (Winlock Driver v1.43)
    162 10317889 14ed - 1 seg_drv (Segment Device Driver v1.1)
    165 1030f375 2268 - 1 diaudio (Generic Audio)
    167 1032811a 19cc 89 1 lockstat (Lock Statistics)
    168 78215406 d1e 90 1 kstat (kernel statistics driver)
    169 780e6000 5d08 91 1 vol (Volume Management Driver, 1.87)
    170 780de000 1664 95 1 cpc (cpc sampling driver v1.8)
    170 780de000 1664 179 1 cpc (cpc sampling system call)
    170 780de000 1664 179 1 cpc (32-bit cpc sampling system call)
    172 78259747 ba0 103 1 qec (QEC driver v1.32)
    175 10347bee 4197 107 1 llc1 (LLC Class 1 Driver)
    177 780ec000 4c5e - 1 amsrc1 (Audio Sample Rate Conv. #1 1.2)
    178 780f2000 23ee - 1 audiosup (Audio Device Support 1.9)
    179 780f6000 14f6e - 1 mixer (Audio Mixer 1.41)
    182 1030331b 4edc 114 1 tnf (kernel probes driver 1.48)
    184 7816a000 b3ec 150 1 fcp (Sun FCP Pseudo Driver v1.11)
    185 1034b93d 4cd6 127 1 pm (power management driver v1.95)
    186 780598aa 846 128 1 tod (tod driver 1.0)
    189 780f0baf 1420 138 1 poll (Dev Poll driver)
    190 780f4176 1ecf 147 1 lofi (loopback file driver (1.2))
    193 78142000 499d - 1 pcihp (PCI nexus hotplug support v1.31)
    194 78146605 1ae7 - 1 busra (Bus Resource Allocator (BUSRA) )
    195 780df02c c4c - 1 hpcsvc (hot-plug controller services v1)
    196 78148000 4fe8 - 1 pcicfg (PCI configurator v1.38)
    203 781567ae bb1f - 1 amsrc2 (Audio Sample Rate Conv. #2 1.1)
    214 1034f79b 4805 187 1 sppp (PPP 4.0 mux v1.3)
    215 780da000 3ae0 18 1 sppptun (PPP 4.0 tunnel module v1.2)
    215 780da000 3ae0 188 1 sppptun (PPP 4.0 tunnel driver v1.2)
    218 781f0000 b5c0 191 1 rsm (Remote Shared Memory Driver 1.6)
    219 7804dd6f 2e8 - 1 ipc (common ipc code)
    220 780c95b2 aac - 1 rsmops (RSMOPS module 1.1)
    221 781fb0b0 b33 198 1 rmcadm (rmcadm control driver v1.1)
    222 78174f30 fec 200 1 pca9556 (pca9556 device driver v1.2)
    231 10329430 1069 214 1 fcode (FCode driver 1.8)
    232 1032a2c1 29ec - 1 fcodem (FCode framework 1.13)
    245 78104000 4819 242 1 kb_ps2 (PS/2 Keyboard 1.31, 01/05/09)
    250 781ba000 267e7 250 1 llc2 (SUN LLC2 Class II Streams Drive)
    253 78108000 1bcaa - 1 pcmcia (PCMCIA Nexus Support)
    264 781b2000 304c 263 1 ipdcm (IP/Dialup v1.9)
    265 7814dd68 40a 264 1 ipdptp (IP/Dialup ptp interface v1.9)
    266 7825bd1b 407 265 1 ipd (IP/Dialup mtp interface v1.9)
    268 7826a000 165b8 268 1 wrsmd (RSMPI DLPI 1.4 03/01/08)
    269 7827c000 295e6 19 1 nca (NCA Streams module)
    269 7827c000 295e6 269 1 nca (NCA Streams device 1.2)
    270 1032c3f5 15cc 15 1 mntfs (mount information file system)
    271 78210000 159d2 11 1 tmpfs (filesystem for tmpfs)
    272 78228000 2aa20 106 1 nfs (NFS syscall, client, and common)
    272 78228000 2aa20 106 1 nfs (NFS syscall, client, and common)
    272 78228000 2aa20 16 1 nfs (network filesystem)
    272 78228000 2aa20 7 1 nfs (network filesystem version 2)
    272 78228000 2aa20 17 1 nfs (network filesystem version 3)
    273 78254000 4d9b - 1 rpcsec (kernel RPC security module.)
    274 7825a000 1dc1 - 1 tlimod (KTLI misc module)
    275 7825c000 860f - 1 klmmod (lock mgr common module)
    276 78264000 65e3 18 1 autofs (filesystem for autofs)
    277 10357fa4 109 2 1 IA (interactive scheduling class)
    278 78258a03 f40 3 1 RT (realtime scheduling class)
    279 102a70e1 28c - 1 RT_DPTBL (realtime dispatch table)
    280 103406c9 2878 53 1 semsys (System V semaphore facility)
    280 103406c9 2878 53 1 semsys (32-bit System V semaphore facil)
    281 103064bf 26f8 52 1 shmsys (System V shared memory)
    281 103064bf 26f8 52 1 shmsys (32-bit System V shared memory)
    282 102186fd cf0 207 1 pset (processor sets)
    282 102186fd cf0 207 1 pset (32-bit pset(2) syscall)
    283 102ff5cc 3d82 178 1 kaio (kernel Async I/O)
    283 102ff5cc 3d82 178 1 kaio (kernel Async I/O for 32 bit com)
    284 780a8a5e 1687 20 1 ptem (pty hardware emulator)
    285 781b482c 19d2 21 1 telmod (telnet module)
    [root@vbsmf /kernel/drv] $vi st.conf
    # Copyright (c) 1995-2000 by Sun Microsystems, Inc.
    # All rights reserved.
    #pragma ident "@(#)st.conf 1.27 00/08/29 SMI"
    # This file contains configuration entries for both officially supported
    # devices of Sun Microsystems and many 3rd party devices.
    # The officially supported devices are :
    # "ARCHIVE Python 28388"
    # "ARCHIVE Python 28454"
    # "ARCHIVE Python 29279"
    # "ARCHIVE VIPER 150"
    # "EXABYTE EXB-8200"
    # "EXABYTE EXB-8500"
    # "EXABYTE EXB-8505"
    # "EXABYTE EXB-8900"
    # "HP 88780"
    # "HP C5683A" Note 1
    # "HP C5713A" Note 1
    # "Quantum DLT4000"
    # "Quantum DLT7000"
    # "Quantum DLT8000" Note 1
    # "STK 9840" Note 1
    # "SUN DLT4000"
    # "SUN DLT4700"
    # "SUN DLT7000"
    # "TANDBERG SLR5"
    # "TANDBERG TDC 4200"
    # "TANDBERGMLR1"
    # "TANDBERGMLR3"
    # Notes
    # 1 Drive is configured automatically - no entry is needed in st.conf.
    # The 3rd party devices do apparently work with the configurations listed.
    # All the entries have been taken from the net and probably have worked in
    # the past, but have not been tested by Sun Microsystems. Use these entries
    # as your starting point for generating your configuration entries.
    #tape-config-list=
    # "Emulex MTO2", "Emulex MT02 QIC-11/QIC-24", "MT02",
    # "ANRITSU DMT2120", "Unisys 1/2\" Reel", "ANRITSU",
    # "ARCHIVE Python 28454","Archive Python 4mm Helical Scan","ARCH_Python",
    # "ARCHIVE Python 29279", "Archive Python 4mm DAT Stacker","ARCH_Python",
    # "ARCHIVE Python 28388", "Archive/Conner CTDX004 4mm DAT", "Conner2-DAT",
    # "ARCHIVE VIPER 150", "Archive QIC-150", "QIC150",
    # "ARCHIVE VIPER 255", "Archive QIC-525", "QIC150",
    # "DEC DLT2", "DEC DLT", "DLT2",
    # "DEC TZ87", "DEC DLT", "DLT2",
    # "EXABYTE EXB-2501", "Exabyte EXB-2501 QIC", "EXB-2501",
    # "EXABYTE EXB-4200c", "Exabyte 4mm Helical Scan","Exa4200c",
    # "EXABYTE EXB-8200", "Exabyte EXB-8200 8mm Helical Scan","EXB-8200",
    # "EXABYTE EXB-8500", "Exabyte EXB-8500 8mm Helical Scan","EXB-850X",
    # "EXABYTE EXB-8505", "Exabyte EXB-8505 8mm Helical Scan","EXB-850X",
    # "EXABYTE EXB8500C", "Exabyte 8500C 8mm Helical Scan", "EXB-850X",
    # "EXABYTE EXB-8900", "Mammoth EXB-8900 8mm Helical Scan","EXB-8900",
    # "FUJITSU M1016B M2483B","Fujitsu 1/2\" Cartridge", "Fujitsu_comp",
    # "FUJITSU M248", "Fujitsu 1/2\" Cartridge", "Fujitsu_m248x",
    # "HP 88780", "HP-88780 1/2\" Reel", "HP_half",
    # "HP C1533A", "HP DDS2 4mm DAT loader", "HP_DAT",
    # "HP C1553A ", "HP C1553A 4mm DAT", "HP_DAT",
    # "HP C1537A", "HP DDS-3 4mm DAT ", "HP_DAT_3",
    # "HP C1557A", "HP DDS-3 4mm DAT loader", "HP_DAT_3",
    # "HP HP35470A", "HP 35470A 4mm DAT", "HP_DAT",
    # "HP HP35480A", "HP 35480A 4mm DAT", "HP_DAT",
    # "IBM 03490", "IBM 3490E 1/2\" Cartridge", "CLASS_3490",
    # "IBM 9348", "STK 4220 1/2\" Cartridge", "C3490",
    # "KENNEDY", "Kennedy 1/2\" Reel", "KENNEDY",
    # "LMS", "CDC 1/2\" Cartridge", "LMS",
    # "M4 DATA 123107 SCSI", "M4-Data 1/2\" Reel", "M4_DATA",
    # "Metrum", "Metrum VHS Cartridge", "MetD",
    # "QUANTUM DLT7000", "Quantum DLT7000", "DLT7k-data",
    # "SUN DLT7000", "Sun DLT7000", "DLT7k-data",
    # "Quantum DLT4000", "Quantum DLT4000", "DLT-data",
    # "SUN DLT4000", "DLT4000", "DLT-data",
    # "SUN DLT4700", "DLT4700 Library", "DLT-data",
    # "R-BYTE RB100", "R-Byte Whozits", "DAT",
    # "SONY SDT-5000", "SONY 4mm DAT", "DAT",
    # "SONY SDT-5200", "SONY 4mm DAT", "DAT",
    # "STK 9490", "STK 9490 1/2\" Cartridge", "CLASS_3490",
    # "STK 4280", "STK 4280 1/2\" Cartridge", "C3490",
    # "STK", "STK 1/2\" Cartridge", "CLASS_3490",
    # "TANDBERG 4100", "Tandberg 4100 QIC", "TAND_4100_QIC",
    # "TANDBERG 4200", "Tandberg 4200 QIC", "TAND_4200_QIC",
    # "TANDBERG TDC 4200", "Tandberg QIC 2.5 Gig Tape Drive", "TANDB-2_5G",
    # "TANDBERG SLR5", "Tandberg 8 Gig QIC", "TAND-8G-VAR",
    # "TANDBERGMLR1", "Tandberg MLR1 QIC", "TANDBERG_MLR1",
    # "TANDBERGMLR3", "Tandberg 50 Gig QIC", "TAND-50G-VAR",
    # "TELEX", "STK 4220 1/2\" Cartridge", "C3490",
    # "WANGTEK 51000 SCSI", "Wangtek 1.2GB QIC", "WtQIC",
    # "WANGTEK 5150ES", "Wangtek QIC-150", "WANGTEK_QC150",
    # "WANGTEK 5525ES SCSI", "Wangtek 525MB QIC", "WtQIC",
    # "WANGTEK 6130-HS", "Wangtek 4mm Helical Scan", "WANGTEK_6130",
    # "WangDAT Model 2600", "WangDAT 4mm DAT", "WangDAT",
    # "WangDAT Model 3400", "WangDAT 4mm DAT", "WangDAT",
    # "WangDAT", "Wang DAT 3.81 Helical Scan", "WangDAT",
    # "\076\000", "Fujitsu 1/2\" Cartridge", "Fujitsu_half";
    #ANRITSU = 1,0x25,0,0x41d,4,0x00,0x02,0x03,0x03,1;
    #ARCH_Python= 1,0x2c,0,0xde39,4,0x00,0x8c,0x8c,0x8c,3;
    #CLASS_3490 = 1,0x24,0,0x1c43d,1,0x00,0;
    #C3490 = 1,0x24,0,0x1c43d,4,0x00,0x00,0x00,0x01,2;
    #Conner2-DAT= 1,0x2c,0,0xde39,1,0x00,0;
    #DAT = 1,0x34,0,0x0439,1,0x00,0;
    #DLT2 = 1,0x38,0,0xd639,4,0x17,0x18,0x80,0x81,2;
    #DLT-data = 1,0x38,0,0xD639,4,0x80,0x81,0x82,0x83,2;
    #DLT7k-data = 1,0x38,0,0xD639,4,0x82,0x83,0x84,0x85,2;
    #EXB-2501 = 1,0x28,1024,0x442,1,0x00,0;
    #EXB-8200 = 1,0x28,0,0x8c79,1,0x00,0;
    #EXB-850X = 1,0x29,0,0xce39,4,0x14,0x15,0x8c,0x8c,1;
    #EXB-8900 = 1,0x29,0,0x19E39,4,0x27,0x27,0x27,0x27,3;
    #Exa4200c = 1,0x34,0,0x1639,2,0x63,0x0,1;
    #Fujitsu_comp = 1,0x21,0,0x18639,4,0x00,0x00,0x00,0x09,1;
    #Fujitsu_half = 1,0x21,0,0x63b,1,0x00,0;
    #Fujitsu_m248x = 1,0x21,0,0xc639,1,0x00,0;
    #HP_DAT = 1,0x34,0,0x19679,1,0x0,0;
    #HP_DAT_3 = 1,0x34,0,0x9639,4,0x00,0x8c,0x8c,0x8c,1;
    #HP_half = 1,0x23,0,0x41d,4,0x01,0x02,0x03,0xc3,1;
    #KENNEDY = 1,0x22,0,0x41d,4,0x01,0x02,0x03,0x03,1;
    #LMS = 1,0x20,0,0x66b,1,0x00,0;
    #M4_DATA = 1,0x27,0,0x49d,4,0x01,0x02,0x06,0x06,1;
    #MT02 = 1,0x14,512,0x202,4,0x84,0x05,0x05,0x05,1;
    #MetD = 1,0x36,0,0x1639,1,0x00,0;
    #QIC150 = 1,0x15,512,0x642,1,0x00,0;
    #TANDB-2_5G = 1,0x32,0,0xD67b,1,0x0,0;
    #TAND-8G-VAR = 1,0x37,0,0x963b,4,0xA0,0xD0,0xD0,0xD0,3;
    #TANDBERG_MLR1 = 1,0x32,512,0x463a,1,0x00,0;
    #TAND-50G-VAR = 1,0x37,0,0x963b,4,0xA0,0xD0,0xD0,0xD0,3;
    #TAND_4100_QIC = 1,0x32,512,0x463a,1,0x00,0;
    #TAND_4200_QIC = 1,0x32,512,0x463a,1,0x00,0;
    #WANGTEK_6130 = 1,0x2a,0,0x659,1,0x00,0;
    #WANGTEK_QC150 = 1,0x16,512,0x642,1,0x00,0;
    #WangDAT = 1,0x2b,0,0x659,1,0x00,0;
    #WangDAT = 1,0x34,0,0x0679,1,0x00,0;
    #WtQIC = 1,0x32,512,0x467a,1,0x00,0;
    name="st" class="scsi"
    target=0 lun=0;
    name="st" class="scsi"
    target=1 lun=0;
    name="st" class="scsi"
    target=2 lun=0;
    name="st" class="scsi"
    target=3 lun=0;
    name="st" class="scsi"
    target=4 lun=0;
    name="st" class="scsi"
    target=5 lun=0;
    name="st" class="scsi"
    target=6 lun=0;
    # as your starting point for generating your configuration entries.
    #tape-config-list=
    # "Emulex MTO2", "Emulex MT02 QIC-11/QIC-24", "MT02",
    # "ANRITSU DMT2120", "Unisys 1/2\" Reel", "ANRITSU",
    # "ARCHIVE Python 28454","Archive Python 4mm Helical Scan","ARCH_Python",
    # "ARCHIVE Python 29279", "Archive Python 4mm DAT Stacker","ARCH_Python",
    # "ARCHIVE Python 28388", "Archive/Conner CTDX004 4mm DAT", "Conner2-DAT",
    # "ARCHIVE VIPER 150", "Archive QIC-150", "QIC150",
    # "ARCHIVE VIPER 255", "Archive QIC-525", "QIC150",
    # "DEC DLT2", "DEC DLT", "DLT2",
    # "DEC TZ87", "DEC DLT", "DLT2",
    # "EXABYTE EXB-2501", "Exabyte EXB-2501 QIC", "EXB-2501",
    # "EXABYTE EXB-4200c", "Exabyte 4mm Helical Scan","Exa4200c",
    # "EXABYTE EXB-8200", "Exabyte EXB-8200 8mm Helical Scan","EXB-8200",
    # "EXABYTE EXB-8500", "Exabyte EXB-8500 8mm Helical Scan","EXB-850X",
    # "EXABYTE EXB-8505", "Exabyte EXB-8505 8mm Helical Scan","EXB-850X",
    # "EXABYTE EXB8500C", "Exabyte 8500C 8mm Helical Scan", "EXB-850X",
    # "EXABYTE EXB-8900", "Mammoth EXB-8900 8mm Helical Scan","EXB-8900",
    # "FUJITSU M1016B M2483B","Fujitsu 1/2\" Cartridge", "Fujitsu_comp",
    # "FUJITSU M248", "Fujitsu 1/2\" Cartridge", "Fujitsu_m248x",
    # "HP 88780", "HP-88780 1/2\" Reel", "HP_half",
    # "HP C1533A", "HP DDS2 4mm DAT loader", "HP_DAT",
    # "HP C1553A ", "HP C1553A 4mm DAT", "HP_DAT",
    # "HP C1537A", "HP DDS-3 4mm DAT ", "HP_DAT_3",
    # "HP C1557A", "HP DDS-3 4mm DAT loader", "HP_DAT_3",
    # "HP HP35470A", "HP 35470A 4mm DAT", "HP_DAT",
    # "HP HP35480A", "HP 35480A 4mm DAT", "HP_DAT",
    # "IBM 03490", "IBM 3490E 1/2\" Cartridge", "CLASS_3490",
    # "IBM 9348", "STK 4220 1/2\" Cartridge", "C3490",
    # "KENNEDY", "Kennedy 1/2\" Reel", "KENNEDY",
    # "LMS", "CDC 1/2\" Cartridge", "LMS",
    # "M4 DATA 123107 SCSI", "M4-Data 1/2\" Reel", "M4_DATA",
    # "Metrum", "Metrum VHS Cartridge", "MetD",
    # "QUANTUM DLT7000", "Quantum DLT7000", "DLT7k-data",
    # "SUN DLT7000", "Sun DLT7000", "DLT7k-data",
    # "Quantum DLT4000", "Quantum DLT4000", "DLT-data",
    # "SUN DLT4000", "DLT4000", "DLT-data",
    # "SUN DLT4700", "DLT4700 Library", "DLT-data",
    # "R-BYTE RB100", "R-Byte Whozits", "DAT",
    # "SONY SDT-5000", "SONY 4mm DAT", "DAT",
    # "SONY SDT-5200", "SONY 4mm DAT", "DAT",
    # "STK 9490", "STK 9490 1/2\" Cartridge", "CLASS_3490",
    # "STK 4280", "STK 4280 1/2\" Cartridge", "C3490",
    # "STK", "STK 1/2\" Cartridge", "CLASS_3490",
    # "TANDBERG 4100", "Tandberg 4100 QIC", "TAND_4100_QIC",
    # "TANDBERG 4200", "Tandberg 4200 QIC", "TAND_4200_QIC",
    # "TANDBERG TDC 4200", "Tandberg QIC 2.5 Gig Tape Drive", "TANDB-2_5G",
    # "TANDBERG SLR5", "Tandberg 8 Gig QIC", "TAND-8G-VAR",
    # "TANDBERGMLR1", "Tandberg MLR1 QIC", "TANDBERG_MLR1",
    # "TANDBERGMLR3", "Tandberg 50 Gig QIC", "TAND-50G-VAR",
    # "TELEX", "STK 4220 1/2\" Cartridge", "C3490",
    # "WANGTEK 51000 SCSI", "Wangtek 1.2GB QIC", "WtQIC",
    # "WANGTEK 5150ES", "Wangtek QIC-150", "WANGTEK_QC150",
    # "WANGTEK 5525ES SCSI", "Wangtek 525MB QIC", "WtQIC",
    # "WANGTEK 6130-HS", "Wangtek 4mm Helical Scan", "WANGTEK_6130",
    # "WangDAT Model 2600", "WangDAT 4mm DAT", "WangDAT",
    # "WangDAT Model 3400", "WangDAT 4mm DAT", "WangDAT",
    # "WangDAT", "Wang DAT 3.81 Helical Scan", "WangDAT",
    # "\076\000", "Fujitsu 1/2\" Cartridge", "Fujitsu_half";
    #ANRITSU = 1,0x25,0,0x41d,4,0x00,0x02,0x03,0x03,1;
    #ARCH_Python= 1,0x2c,0,0xde39,4,0x00,0x8c,0x8c,0x8c,3;
    #CLASS_3490 = 1,0x24,0,0x1c43d,1,0x00,0;
    #C3490 = 1,0x24,0,0x1c43d,4,0x00,0x00,0x00,0x01,2;
    #Conner2-DAT= 1,0x2c,0,0xde39,1,0x00,0;
    #DAT = 1,0x34,0,0x0439,1,0x00,0;
    #DLT2 = 1,0x38,0,0xd639,4,0x17,0x18,0x80,0x81,2;
    #DLT-data = 1,0x38,0,0xD639,4,0x80,0x81,0x82,0x83,2;
    #DLT7k-data = 1,0x38,0,0xD639,4,0x82,0x83,0x84,0x85,2;
    #EXB-2501 = 1,0x28,1024,0x442,1,0x00,0;
    #EXB-8200 = 1,0x28,0,0x8c79,1,0x00,0;
    #EXB-850X = 1,0x29,0,0xce39,4,0x14,0x15,0x8c,0x8c,1;
    #EXB-8900 = 1,0x29,0,0x19E39,4,0x27,0x27,0x27,0x27,3;
    #Exa4200c = 1,0x34,0,0x1639,2,0x63,0x0,1;
    #Fujitsu_comp = 1,0x21,0,0x18639,4,0x00,0x00,0x00,0x09,1;
    #Fujitsu_half = 1,0x21,0,0x63b,1,0x00,0;
    #Fujitsu_m248x = 1,0x21,0,0xc639,1,0x00,0;
    #HP_DAT = 1,0x34,0,0x19679,1,0x0,0;
    #HP_DAT_3 = 1,0x34,0,0x9639,4,0x00,0x8c,0x8c,0x8c,1;
    #HP_half = 1,0x23,0,0x41d,4,0x01,0x02,0x03,0xc3,1;
    #KENNEDY = 1,0x22,0,0x41d,4,0x01,0x02,0x03,0x03,1;
    #LMS = 1,0x20,0,0x66b,1,0x00,0;
    #M4_DATA = 1,0x27,0,0x49d,4,0x01,0x02,0x06,0x06,1;
    #MT02 = 1,0x14,512,0x202,4,0x84,0x05,0x05,0x05,1;
    #MetD = 1,0x36,0,0x1639,1,0x00,0;
    #QIC150 = 1,0x15,512,0x642,1,0x00,0;
    #TANDB-2_5G = 1,0x32,0,0xD67b,1,0x0,0;
    #TAND-8G-VAR = 1,0x37,0,0x963b,4,0xA0,0xD0,0xD0,0xD0,3;
    #TANDBERG_MLR1 = 1,0x32,512,0x463a,1,0x00,0;
    #TAND-50G-VAR = 1,0x37,0,0x963b,4,0xA0,0xD0,0xD0,0xD0,3;
    #TAND_4100_QIC = 1,0x32,512,0x463a,1,0x00,0;
    #TAND_4200_QIC = 1,0x32,512,0x463a,1,0x00,0;
    #WANGTEK_6130 = 1,0x2a,0,0x659,1,0x00,0;
    #WANGTEK_QC150 = 1,0x16,512,0x642,1,0x00,0;
    #WangDAT = 1,0x2b,0,0x659,1,0x00,0;
    #WangDAT = 1,0x34,0,0x0679,1,0x00,0;
    #WtQIC = 1,0x32,512,0x467a,1,0x00,0;
    name="st" class="scsi"
    target=0 lun=0;
    name="st" class="scsi"
    target=1 lun=0;
    name="st" class="scsi"
    target=2 lun=0;
    name="st" class="scsi"
    target=3 lun=0;
    name="st" class="scsi"
    target=4 lun=0;
    name="st" class="scsi"
    target=5 lun=0;
    nam

    Sorry Simon, but I had to jump in on that.
    You are correct that they'll need to probe from OBP, however...
    jumping down from an active OS will leave much in various bus registers and they'll lock up the entire system when a probe is done that way. They'll have to power-cycle the chassis to recover.
    Vassilios,
    When you have the chance for testing this system, bring the chassis down to the OBP level. ( init 0 is acceptable ) then do:
    OK setenv auto-boot? false <enter>
    OK reset-all <enter>
    The chassis will cycle and automatically stop at the OK prompt, with empty bus registers, and you can probe all you wish.
    The peripheral MUST be seen at the hardware level before an OS can dream of manipulating it.
    But, if I may ask...
    You attached the tape peripheral to where?
    (the integrated onboard SCSI connector or to an add-on card?)
    Is it a Single-Ended SCSI device, a HVD SCSI device, or a LVD SCSI device?
    If your cable is attached to an appropriate add-on card, do you need to install any packages for that card?

  • Creating a Boot drive and a data drives

    I have just installed a new 750 GB hard drive into a PowerMac G5, it had a 160 GB drive already, and I left that in there. I would like to use the older smaller drive as the boot drive, and the newer bigger one as the user data drive.
    How do I go about doing it to minimize problems? I can clone the older drive onto the newer one, using disk utility. Once I do that, then what? Please give me some detailed steps.
    Where do I divide things up, put system and applications on the boot drive, and users on the data drive? What about Library? What about things like etc, tmp, and var? Will I have problems cloning users? Please help

    You do not need to clone to the new drive, unless you want to be able to startup from it.
    Just use Disk Utility. Select the new drive in the Disk Utility sidebar. If you just want one partition on the drive, you can use the Erase tab to format it. Select Mac OS Extended (Journaled) as the format type. If you want to partition it and format it, use the Partition tab. One possibility is to create two partition, with one partition being about the size of the 160GB startup drive. You can then periodically clone your regular startup drive to that smaller partition to have a bootable backup (very useful for trouble-shooting). The second partition can be the rest of the space. How you partition the drive is up to you...
    You should keep your system and library files on the startup drive. You should generally keep your application files on your startup drive, in the Application folder. You may also want to keep all of default first level folders in your Home (user) folder on the startup drive. These are the folders like Documents, Music, Movies, etc. that are created during the OS installation.
    Inside these user folders, I have moved my large folders (such as +iTunes Music+ at <home>/Music/iTunes/) to my second drive. Then I create an alias named exactly like the moved folder, and put it back in the original location. When iTunes is started, it should act like the folder was still on startup drive in the default location. Alternately, you can move the folder and tell iTunes where the new location is in its preferences, but I like using the default settings when possible.
    You should be able to take similar actions to put your iPhoto library folder and others on your second drive. If you have sub-folders in your documents folder, you can also alias them to folders on your second drive. Essentially, most of your user-created data can be on the second drive, but it will look like a default setup in Finder and to the system.
    There are more technical things you can do, such as move your entire user folder to the second drive. You can look at those possibilities as well...

  • Altering program files from SAP Data drive to C drive

    Dear Forum,
    I am trying to alter the 'program files' in SAP Data drive folder that was created during installation to free up some space. In this case the SAP Data drive is the 'E' drive and the 'program files' folder is altered to 'C' drive.
    Here are the steps:
    1.     stopped SAP, then all SQL services
    2.     regedit to look for registry entries pointing to the E:\ drive:
    3.     Copied over from E:\ to C:\ drive all non-duplicate folders contained in E:\Program Files\Common Files\Microsoft Shared\DW
    4.     renamed the registry entries to reflect their new location.
    So, for example in the registry 'My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders' the entry 'E:\Program Files\Common Files\Microsoft Shared\DW\' is altered to 'C:\Program Files\Common Files\Microsoft Shared\DW\'. All entries are altered one by one.
    So far the first trial works. Is it secure to do it in this way. Will it be a problem when the SQL needs to be patched, for example?
    Please kindly advice.
    Regards,
    Agoes

    With DATA files it´s VERY different. They are pretty isolated seen from an operating system perspective, you can put them anywhere and just point the database to the right path.
    However, everything on "C:" must reside there, especially %SYSTEMROOT% and %PROGRAM FILES%. On Unix system you could copy them somwhere, create a soft link and you were done, on Windows, this is possible because depending on the installed software (SAPGUI, Backup software etc.) you will have LOTS of registry entries pointing to "c:program files", including the COM and ActiveX objects (e. g. a SAPGUI registers > 2000 ActiveX objects in the registry).
    Since almost no vendor has documentation about which piece of software is installed where and what is put where in the registry the only way of safely relocating something from C: (if C: is your system drive) is to reinstall the OS and do a homogeneous system copy.
    Welcome to the world of Windows
    Markus

  • Is VHDX for data drive considered good practice on a client PC?

    Hi!
    I don't like putting user's data files (documents, etc.) inside the user's Documents directory on C:. Instead I prefer having them on a D: disk, separate from the OS. On the other hand I don't want to create a fixed size partition as I consider it a waste
    of space, especially when everything is on a rather small SSD.
    Therefore, I consider creating a virtual hard disk (VHDX) on my C: drive and making it dynamically expanding. This would allow me to store data on that "separate" disk which is actually an expanding VHDX file on C:. One problem is that for some
    unknown reason Windows 8.1 is not able to auto-attach such disks on startup, but I have seen some workarounds to auto-mount them through tasks.
    My question is the following: Is it considered good practice to put all data files on such a dynamic VHDX instead on a separate partition? Reading the VHDX explanations it looks like this file format is very stable (even in case of power loss) and is widely
    used in virtual servers. Performance should be also very good. Therefore I don't see any reason to not use it for my data drive. Or are there any drawbacks?
    Thanks in advance for any help.
    Best regards,
    Anguel

    Hi,
    Since the VHDX is created on C which should be the system partition, I don’t think it is more safety than separate partition.
    Please consider that once the system corrupted and we have to format the C to reinstall the System, it may be difficult for us to recovery the date. But the separated partition will be easily stayed without changes.
    You can try to shrink the C volume in Disk management to create a new partition.
    Just my thought.  
    Kate Li
    TechNet Community Support

  • How can I install Itunes in the data drive and not in OS partition?

    My PC has a 3 partitions and I hace installed Itunes in the OS partition, very small. How can I install Itunes in the data drive?

    See Williams Lloyd's post > https://discussions.apple.com/message/15670671#15670671

  • User did not specify local data drive, MSATA drive

    SCCM 2007 R2 SP2 windows 7 x64.
    Hi,
       I am trying to image Dell M6800 with MSATA drive, but imaging is failing to
    User did not specify local data drive
    Volume C:\ is not a fixed hard drive
    Volume D:\ is not a fixed hard drive
    Volume X:\ is not a fixed hard drive
    TSM root drive =
    We do not find an available volume to store the local data path
    Winpe is not finding Msata drive. i have injected new "WinPE3.0-Drivers-A15-47R7V" from dell. no luck. Dispart find disk on 0 fine.
    Here is the log file http://1drv.ms/1L7Cw6b
    do you i need to install sata driver?
    thanks
    orion

    got it fixed.
    1.diskpart
    2.list disk
    3.select disk #
    4.clean
    5.create partition primary
    6.select partition 1
    7.active
    8.format quick fs=NTFS
    9.assign
    10.exit
    works great
    orion

  • Garbage folders remain in user data drive

    Patch management generated some working folers(ex. 3d1cd6ffb3eb95d299573bf8bd31) & files in my d: (user data drive). Some of these folder remain in the drive after patching and these folders could not be deleted by Win7 user without admin rights. Is there any way to change the working folder to Windows system drive (c? How to house keep these folders??

    Ird,
    I bet those are the folders created by MS patches, you get them even if
    you use Windows Update
    Shaun Pond

  • MB BIOS 2.2TB MBR limitation: Can add-on drive controller BIOS enable UEFI/GPS on a non-bootable data drive?

    I am working on older hardware that is not UEFI enabled so it is subject to the 2.2TB volume limitation under Windows Server 2012 R2 resulting in 11.6TB of unusable drive space. I installed an Adaptec Series 7 2274500-R 71605E controller card and created
    a striped RAID 10 totalling 13.6 TB of drive space. During boot, the Adaptec BIOS is installed on the system, which prompts the following question:
    Since the boot utilizes the motherboard BIOS, clearly the boot partition cannot exceed the 2.2TB limit. But what about a separate logical data drive? If I shrink the boot partition to 1TB, create a second volume at RAID level of 12.6TB formatted with GPT
    NTFS, would the Adaptec BIOS enable UEFI/GPT (since the MB BIOS would not boot to the second logical drive) and Windows Server see the full 12.6TB second drive volume?
    Yes, I am aware that I can create multiple 2.2TB partitions, but that would be an inefficient option for this installation.
    Any thoughts or suggestions will be greatly appreciated.
    Thanks!

    Hi,
    According to your description, my understanding is that you want to use add-on drive controller to enable UEFI/GPS on a non-bootable drive.
    In order for an operating system to fully support storage devices that have capacities that exceed 2 TB, the device must be initialized by using the GUID partition table (GPT) partitioning scheme. If the user intends to start the computer from one of these
    large disks, the system’s base firmware interface must use the Unified Extensible Firmware Interface (UEFI) and not BIOS. Windows support for hard disks that are larger than 2 TB, and there are some prerequisites are needed.
    Detailed information reference link:
    https://support.microsoft.com/en-us/kb/2581408
    Best Regards,
    Eve Wang
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Don't have permissions to data drives after replacing system drive

    In my 10.4 Mac Pro, the hard drive with the OS died.  I have two more hard drives in there that I store all my data on, those are fine.  I bought a new drive, reloaded OSX, created a administrator account during setup, but now I don't appear to have access to my data drives.  I did a command+i and tried to reset it to my administrator account and group having read & write, and everyone else having read & write (as other people use this computer too, we all share the data drives so the permissions need to be wide open for everyone) but it says I dont have permissions to do it.
    Anyone know how i can blow open the permissions on those two data drives?

    Thanks - I did go there but couldn't find my specific issue addressed.
    In any event - I've since discovered that the two HD in question (although I use them on a daily basis with no problem) both had "Ignore ownership on this volume" checked in the Info window. The two I COULD access (via Time Machine) did not.
    So I unchecked that box on the 2 problem drives and, when I went back into TM, was able at least to select each hard drive with no error messages.
    Unfortunately, execept for the "Today" state, TM would NOT go back in time to show files on either of the two  previously-locked drives for all of the yesterdays that it backed them up.
    Unless I can figure out how to access Time Machine as "System" I think all those archived files are lost to me on the two drives.

  • Collections are empty after upgrading to a bigger data drive

    Last summer I upgraded the size of my data drive (I have a multi-bayed old Mac Pro) and all seems to be well. I recently reviewed my Collections (in LR5) which I upgraded from 4 at the same time) which I use to group images and noticed that images were missing. All my folders on the hard drive seem fine, they all recognise that the images are on the new larger hard drive. However many of the collections (though interestingly not all) seem to think the images are still on the old discontinued drive which i no longer have. When I select an image to 'reconnect it' it tells me its on another drive (the old drive) and will not reassign the file name to the same image which is now on the newer larger drive. I could understand this if the Folder structure was incorrect, but its not, and Ive synced it. Does anyone have a solution for me? Much appreciated

    Yes, that's exactly what you would expect, and that's exactly the catalog you want to use.
    You will need to reconnect the photos in that old catalog using these instructions: http://www.computer-darkroom.com/lr2_find_folder/find-folder.htm
    Do NOT synchronize anything. Do NOT import anything. If you open this backup catalog and perform the fix described at that link, you now have a catalog where all the photos are "not missing" and the collections are intact.
    If there are new photos added to your existing catalog after you performed this move, we can deal with those next. Let me know how it goes.

  • Trouble with color labels not synching between different machines sharing same data drive

    Hi
    I am having a problem that seems to have come up when I started using a mix of PS/Bridge CS4 and CS3, in which color labels I apply in Bridge--primarily to folders--do not retain the color label when I look at the same set of folders on the same external hard drive using multiple, different Macintosh machines, running a mix of CS3 and CS4.  The color labels will appear on one machine and then not appear at all on another.  Note: they don't appear as white labels without a color.  It's as if they were never labeled at all!
    I use multiple Macs to connect to one primary external data drive.  I consistently configure Bridge to export caches to the external drive, and with CS3 any color labels I applied to folders were consistently displayed in the same way on multiple machines.
    Every since I upgraded a couple of my Macs to CS4, I now notice that color labels applied on one machine aren't showing up when I attach my external drive to other machines. I've even noticed a problem connecting to the external drive from two different user profiles on the same Mac laptop (running CS4).
    I have tried resetting the preferences and the cache on all of these machines.  I also then re-toggled the export caches checkboxes on all these machines.  Per some earlier troubleshooting, I have also made sure that the naming convention for the labels is the same on all the machines: "Approved" versus "Green," etc.
    There just seems to be no rhyme or reason for why the color labels are not synching.
    HELP!?
    Thanks in advance.

    I have no clue at all, labels should stay visible after having applied them
    to a file and used purge cache. And they do so on my system.
    Normally there will not be many reasons to use the purge cache option unless
    you have trouble, every time you alter a file it should be auto update the
    preview and thumb, is this not in your workflow?
    Are you still working with same files that were also present on your other
    system and using CS3?
    Have you considered to start from scratch?
    Quit Bridge, from the user library preference folder delete the plist file
    for Bridge to the trash and in the same library from the caches folder /
    Adobe/BridgeCS4 move the cache file outside the user library if you want to
    backup this file (or to the trash if you don't want it anymore)
    Both files will replace itself with fresh ones but the cache needs to start
    all over again building previews.
    Again hold option when starting Bridge first time and again choose refresh
    preferences.
    Set the preferences for Bridge to your wishes and try again.
      However, if I go to "Tools-Cache-Purge Cache For Folder" and purge the cache
    for the folder I'm working in, the color labels disappear.  Is this expected
    behavior?  Shouldn't the color labels be recreated?? Again, I have repeatedly
    purge the cache in this way, have reset Bridge CS4 settings, and have
    re-selected the option to "Export Caches To Folders When Possible."  What's
    going on!?!?!?  Thanks.

  • "Additional DSD Data:Driver Data" filed not found

    Hi,
    we have activeted Direct store delivery in our system.But when we are trying to create Driver we are unable to fine the field /button "Additional DSD Data:Driver Data".
    Please help to resolve the issue.
    Thanks in advance for your help.
    regards
    Sandip

    Hi,
    Can you post the relevant <jdbc-resource> element in server.xml? Also, your res-ref in ejb xml?
    Thanks.
    -Tuan.

  • Encrypting data drive in Mavericks

    In Mountain Lion it was possible to right-click on an external data drive and select an option from the popup menu to encrypt the data drive. (Presuming it is properly formatted at a GUID partition HFS+ drive.)
    However the same option is not available in the Finder in Mavericks. It is possible similarly encrypt specifically a Time Machine drive by opening Time Machine preferences and ticking a box to encrypt the Time Machine backup volume but I am asking about encrypting a general purpose data drive which will not be used as a Time Machine backup.
    Last time I needed to do this I had to specifically find a Mac still running Mountain Lion to do it. Surely there must be an easy way to still do it in Mavericks.
    Thanks for any help.

    That option is still there. Perhaps the drive your are trying to encrypt is not a Journaled HFS volume.

Maybe you are looking for