600 meg too 10 gig?

hey, im doing a school project in iMovie on Jimi Hendrix.
so i downloaded a few of his videos, and im going to make something out of it. but when i import it into iMovie, the 600 meg file ends up being 10 gig. it takes about 50 minutes to import, and takes up obviously heaps of space. is there any way around this?
thanks.

welcome ty to the  board ...
iMovie and iDVD use the same codec as on miniDV tapes (what they are meant for....), which is "dv".
dv is ~13GB/hour...
no workaround - iApps use this codec.
your downloaded files use a much higher compression/different codec, which is mainly meant for playback, not editing… I keep my fingers crossed, you're able to create a watchable video with audio....
in case, these files use mpeg: start downloading this tool: Streamclip
... Jimi Hendrix... my parents hated it, when I played his records... he would be 62y old now... phewww, time......

Similar Messages

  • How does a 1.6-gig clip become an 11-gig clip when exported from FCP?

    I captured some video and had to do it in two sessions because my camera kept dropping frames. My first clip was 600 megs, my second was 1 gig. I put them into the timeline and synced them up at the break spot. I wanted to have just one file to work on in Shake, so I exported the two clips as a Quick Time movie -- no compression, self-contained -- a 720 X 480 NTSC file.
    Even with no compression, I expected to get a 1.6-gig movie out of the export, but it was 11 gigs. Where did the extra data come from? And what is the extra data? It cannot get any more resolution than there was to begin with in the original two clips, right?
    Any tips on a more efficient way to handle this situation much appreciated.
    JimBe

    The two segments were each about three and a half minutes long. The camera was a Sony Handycam DV. I did not have any special settings when I captured, I made one choice, to capture both video and audio. Yes, I did select uncompressed when I exported.
    So the camera is acquiring with a codec, it sounds like, but if I select uncompressed on export does that mean FCP will uncompress the compressed footage captured by the camera? I did not think that was possible. Isn't all the information thrown away by the camera when it acquires the footage with its codec?
    I was thinking that "uncompressed" export would just give me back what I put in, a 1.6-gig file. I did not want to compress a second time.
    Is there an export format choice that just gives you what you had without any manipulation of the original data?

  • Items on desktop and in windows appear too large

    I recently had to perform a System Restore to remove some malicious software, but when my computer restarted I found that everything seemed over-sized. Right now both the desktop and internet explorer look magnified, and to see a standard size web page I have to zoom out to 75%. It is extremely inconvenient, and I've been looking for an answer for quite some time.
    I have already verified that my resolution is at 800x600, which is the lowest setting, that my dpi is at 100%, and I've looked at my video card to see if I had to install any drivers. I think it is described as being a "standard vga graphics adapter."
    It is very important to me that I correct it back to the way it was prior to the restore, so any suggestions are appreciated.

    Hi,
    You need higher resolution, not lowest. What is the native resolution of your screen ? 800 x 600 is too low for a normal screen. To help us answer question quicker, please read this:
       http://h30434.www3.hp.com/t5/First-Time-Here-Learn-How-to/Welcome-Get-started-here/td-p/699035
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • Problem with Amanda

    Hi All, i have a problem with the Amanda under soalris 10, the planner is not able to get an estimate, se below:
    AMANDA bex> /usr/local/libexec/planner daily
    planner: pid 3833 executable /usr/local/libexec/planner version 2.5.1
    planner: build: VERSION="Amanda-2.5.1"
    planner:        BUILT_DATE="Thu Sep 14 22:40:36 CEST 2006"
    planner:        BUILT_MACH="SunOS bex 5.10 Generic_118855-14 i86pc i386 i86pc"
    planner:        CC="gcc"
    planner:        CONFIGURE_COMMAND="'./configure' '--with-group=amanda' '--with-user=amanda' '--datadir=/opt/local/share' '--sysconfdir=/opt/local/etc' '--sharedstatedir=/opt/local/com' '--localstatedir=/opt/local/var'"
    planner: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin"
    planner:        libexecdir="/usr/local/libexec" mandir="/usr/local/man"
    planner:        AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
    planner:        CONFIG_DIR="/opt/local/etc/amanda" DEV_PREFIX="/dev/dsk/"
    planner:        RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump"
    planner:        RESTORE="/usr/sbin/ufsrestore" VDUMP=UNDEF VRESTORE=UNDEF
    planner:        XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF
    planner:        SAMBA_CLIENT=UNDEF GNUTAR=UNDEF
    planner:        COMPRESS_PATH="/usr/bin/gzip"
    planner:        UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lp"
    planner:        MAILER="/usr/bin/mailx"
    planner:        listed_incr_dir="/opt/local/var/amanda/gnutar-lists"
    planner: defs:  DEFAULT_SERVER="bex" DEFAULT_CONFIG="DailySet1"
    planner:        DEFAULT_TAPE_SERVER="bex" HAVE_MMAP HAVE_SYSVSHM
    planner:        LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
    planner:        AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY USE_AMANDAHOSTS
    planner:        CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
    planner:        COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
    planner:        COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
    READING CONF FILES...
    DATE 20060919082701
    planner: timestamp 20060919082701
    planner: time 0.233: startup took 0.233 secs
    SENDING FLUSHES...
    ENDFLUSH
    ENDFLUSH
    SETTING UP FOR ESTIMATES...
    planner: time 0.234: setting up estimates for bex.martel-consulting.ch:d0
    bex.martel-consulting.ch:d0 overdue 13410 days for level 0
    setup_estimate: bex.martel-consulting.ch:d0: command 0, options: none    last_level -1 next_level0 -13410 level_days 0    getting estimates 0 (-2) -1 (-2) -1 (-2)
    planner: time 0.236: setting up estimates took 0.001 secs
    GETTING ESTIMATES...
    planner: time 0.420: got result for host bex.martel-consulting.ch disk d0: 0 -> -2K, -1 -> -2K, -1 -> -2K
    error result for host bex.martel-consulting.ch disk d0: missing estimate
    planner: time 0.421: getting estimates took 0.184 secs
    FAILED QUEUE:
      0: bex.martel-consulting.ch d0
    DONE QUEUE: empty
    ANALYZING ESTIMATES...
    planner: FAILED bex.martel-consulting.ch d0 20060919082701 0 [missing result for d0 in bex.martel-consulting.ch response]
    INITIAL SCHEDULE (size 2064):
    DELAYING DUMPS IF NEEDED, total_size 2064, tape length 30793728 mark 1000
      delay: Total size now 2064.
    PROMOTING DUMPS IF NEEDED, total_lev0 0, balanced_size 0...
    planner: time 0.421: analysis took 0.000 secs
    GENERATING SCHEDULE:
    I have a .amandahosts:
    AMANDA bex> ls -l .amandahosts
    -rw-------   1 amanda   amanda        11 Sep 16 22:25 .amandahosts
    AMANDA bex> more .amandahosts
    bex amanda
    the amanda service is defined
    bex> grep amanda /etc/services
    amanda          10080/udp
    amandaidx       10082/tcp
    bex> inetadm | grep amanda
    enabled   online         svc:/network/amandaidx/tcp:default
    enabled   online         svc:/network/amanda/udp:default
    bex> inetadm -l svc:/network/amanda/udp:default
    SCOPE    NAME=VALUE
             name="amanda"
             endpoint_type="dgram"
             proto="udp"
             isrpc=FALSE
             wait=TRUE
             exec="/usr/local/libexec/amandad"
             user="amanda"
    default  bind_addr=""
    default  bind_fail_max=-1
    default  bind_fail_interval=-1
    default  max_con_rate=-1
    default  max_copies=-1
    default  con_rate_offline=-1
    default  failrate_cnt=40
    default  failrate_interval=60
    default  inherit_env=TRUE
    default  tcp_trace=FALSE
    default  tcp_wrappers=FALSE
    bex>
    my config is
    bex> cat /opt/local/etc/amanda/daily/amanda.conf
    # amanda.conf - sample Amanda configuration file. See amanda.conf(5) for
    # details
    org      "BackupService"        # your organization name for reports
    mailto   "[email protected]"    # space separated list of operators at your site
    dumpuser "amanda"       # the user to run dumps under
    inparallel 4            # maximum dumpers that will run in parallel (max 63)
                            # this maximum can be increased at compile-time,
                            # modifying MAX_DUMPERS in server-src/driverio.h
    dumporder "sssS"        # specify the priority order of each dumper
                            #   s -> smallest size
                            #   S -> biggest size
                            #   t -> smallest time
                            #   T -> biggest time
                            #   b -> smallest bandwitdh
                            #   B -> biggest bandwitdh
                            # try "BTBTBTBTBTBT" if you are not holding
                            # disk constrained
    taperalgo first         # The algorithm used to choose which dump image to send
                            # to the taper.
                            # Possible values:
                            # [first|firstfit|largest|largestfit|smallest|last]
                            # Default: first.
                            # first         First in - first out.
                            # firstfit      The first dump image that will fit
                            #               on the current tape.
                            # largest       The largest dump image.
                            # largestfit    The largest dump image that will fit
                            #               on the current tape.
                            # smallest      The smallest dump image.
                            # last          Last in - first out.
    displayunit "k"         # Possible values: "k|m|g|t"
                            # Default: k.
                            # The unit used to print many numbers.
                            # k=kilo, m=mega, g=giga, t=tera
    netusage  600 Kbps      # maximum net bandwidth for Amanda, in KB per sec
    dumpcycle 4 weeks       # the number of days in the normal dump cycle
    runspercycle 20         # the number of amdump runs in dumpcycle days
                            # (4 weeks * 5 amdump runs per week -- just weekdays)
    #tapecycle 25 tapes     # the number of tapes in rotation
                            # 4 weeks (dumpcycle) times 5 tapes per week (just
                            # the weekdays) plus a few to handle errors that
                            # need amflush and so we do not overwrite the full
                            # backups performed at the beginning of the previous
                            # cycle
    #* vtapes
    define tapetype HARD-DISK {
    comment "Dump onto hard disk"
    length 30072 mbytes # specified in mbytes to get the exact size of 3GB
    tapecycle 20
    tapetype HARD-DISK
    tpchanger "chg-disk"
    changerfile "/opt/local/etc/amanda/daily/changer"
    tapedev "file:/backupdisk1/daily"
    bumpsize 20 Mb          # minimum savings (threshold) to bump level 1 -> 2
    bumppercent 20          # minimum savings (threshold) to bump level 1 -> 2
    bumpdays 1              # minimum days at each level
    bumpmult 4              # threshold = bumpsize * bumpmult^(level-1)
    etimeout 300            # number of seconds per filesystem for estimates.
    dtimeout 1800           # number of idle seconds before a dump is aborted.
    ctimeout 30             # maximum number of seconds that amcheck waits
                            # for each client host
    tapebufs 20             # A positive integer telling taper how many
                            # 32k buffers to allocate.  The default is 20 (640k).
    # By default, Amanda can only track at most one run per calendar day. When
    # the usetimestamps option is enabled, however, Amanda can track as many
    # runs as you care to make.
    # WARNING: This option is not backward-compatible. Do not enable it if you
    #          intend to downgrade your server installation to Amanda community
    #          edition 2.5
    usetimestamps yes
    # Specify tape device and/or tape changer.  If you don't have a tape
    # changer, and you don't want to use more than one tape per run of
    # amdump, just comment out the definition of tpchanger.
    # Some tape changers require tapedev to be defined; others will use
    # their own tape device selection mechanism.  Some use a separate tape
    # changer device (changerdev), others will simply ignore this
    # parameter.  Some rely on a configuration file (changerfile) to
    # obtain more information about tape devices, number of slots, etc;
    # others just need to store some data in files, whose names will start
    # with changerfile.
    # At most one changerfile entry must be defined; select the most
    # appropriate one for your configuration.  If you select man-changer,
    # keep the first one; if you decide not to use a tape changer, you may
    # comment them all out.
    runtapes 1                      # number of tapes to be used in a single run of amdump
    ##tpchanger "chg-manual"                # the tape-changer glue script
    ##tapedev ""    # the no-rewind tape device to be used
    rawtapedev "/dev/null"  # the raw device to be used (ftape only)
    #changerfile "/usr/local/etc/amanda/DailySet1/changer"
    #changerfile "/usr/local/etc/amanda/DailySet1/changer-status"
    ##changerfile "/usr/local/etc/amanda/DailySet1/changer.conf"
    changerdev "/dev/null"
    # If you want Amanda to automatically label any non-Amanda tapes it
    # encounters, uncomment the line below. Note that this will ERASE any
    # non-Amanda tapes you may have, and may also ERASE any near-failing tapes.
    # Use with caution.
    ## label_new_tapes "DailySet1-%%%"
    maxdumpsize -1          # Maximum number of bytes the planner will schedule
                            # for a run (default: runtapes * tape_length).
    ##tapetype HP-DAT               # what kind of tape it is (see tapetypes below)
    labelstr "^DailySet1-[0-9][0-9]*$"      # label constraint regex: all tapes must match
    amrecover_do_fsf yes            # amrecover will call amrestore with the
                                    # -f flag for faster positioning of the tape.
    amrecover_check_label yes       # amrecover will call amrestore with the
                                    # -l flag to check the label.
    amrecover_changer ""    # amrecover will use the changer if you restore
                                    # from this device.
                                    # It could be a string like 'changer' and
                                    # amrecover will use your changer if you
                                    # set your tape with 'settape changer'
    # Specify holding disks.  These are used as a temporary staging area for
    # dumps before they are written to tape and are recommended for most sites.
    # The advantages include: tape drive is more likely to operate in streaming
    # mode (which reduces tape and drive wear, reduces total dump time); multiple
    # dumps can be done in parallel (which can dramatically reduce total dump time.
    # The main disadvantage is that dumps on the holding disk need to be flushed
    # (with amflush) to tape after an operating system crash or a tape failure.
    # If no holding disks are specified then all dumps will be written directly
    # to tape.  If a dump is too big to fit on the holding disk than it will be
    # written directly to tape.  If more than one holding disk is specified then
    # they will all be used based on activity and available space.
    holdingdisk hd1 {
        comment "main holding disk"
        directory "/dumps/amanda"   # where the holding disk is
        use -100 Mb                 # how much space can we use on it
                                    # a non-positive value means:
                                    # use all space but that value
        chunksize 1Gb       # size of chunk if you want big dump to be
                            # dumped on multiple files on holding disks
                            #  N Kb/Mb/Gb split images in chunks of size N
                            #             The maximum value should be
                            #             (MAX_FILE_SIZE - 1Mb)
                            #  0          same as INT_MAX bytes
    #holdingdisk hd2 {
    #    directory "/dumps2/amanda"
    #    use 1000 Mb
    #holdingdisk hd3 {
    #    directory "/mnt/disk4"
    #    use 1000 Mb
    # If amanda cannot find a tape on which to store backups, it will run
    # as many backups as it can to the holding disks.  In order to save
    # space for unattended backups, by default, amanda will only perform
    # incremental backups in this case, i.e., it will reserve 100% of the
    # holding disk space for the so-called degraded mode backups.
    # However, if you specify a different value for the `reserve'
    # parameter, amanda will not degrade backups if they will fit in the
    # non-reserved portion of the holding disk.
    # reserve 30 # percent
    # This means save at least 30% of the holding disk space for degraded
    # mode backups.
    autoflush no #
    # if autoflush is set to yes, then amdump will schedule all dump on
    # holding disks to be flush to tape during the run.
    # The format for a ColumnSpec is a ',' seperated list of triples.
    # Each triple consists of
    #   + the name of the column (as in ColumnNameStrings)
    #   + prefix before the column
    #   + the width of the column, if set to -1 it will be recalculated
    #     to the maximum length of a line to print.
    # Example:
    #       "Disk=1:17,HostName=1:10,OutKB=1:7"
    # or
    #       "Disk=1:-1,HostName=1:10,OutKB=1:7"
    # You need only specify those colums that should be changed from
    # the default. If nothing is specified in the configfile, the
    # above compiled in values will be in effect, resulting in an
    # output as it was all the time.
    # The names of the colums are:
    # HostName, Disk, Level, OrigKB, OutKB, Compress, DumpTime, DumpRate,
    # TapeTime and TapeRate.
    #                                                       ElB, 1999-02-24.
    # columnspec "Disk=1:18,HostName=0:10,OutKB=1:7"
    # Amanda needs a few Mb of diskspace for the log and debug files,
    # as well as a database.  This stuff can grow large, so the conf directory
    # isn't usually appropriate.  Some sites use /usr/local/var and some /usr/adm.
    # Create an amanda directory under there.  You need a separate infofile and
    # logdir for each configuration, so create subdirectories for each conf and
    # put the files there.  Specify the locations below.
    # Note that, although the keyword below is infofile, it is only so for
    # historic reasons, since now it is supposed to be a directory (unless
    # you have selected some database format other than the `text' default)
    infofile "/opt/local/etc/amanda/daily/curinfo"  # database DIRECTORY
    logdir   "/opt/local/etc/amanda/daily"          # log directory
    indexdir "/opt/local/etc/amanda/daily/index"            # index directory
    #tapelist "/usr/local/etc/amanda/DailySet1/tapelist"    # list of used tapes
    # tapelist is stored, by default, in the directory that contains amanda.conf
    # tapetypes
    # Define the type of tape you use here, and use it in "tapetype"
    # above.  Some typical types of tapes are included here.  The tapetype
    # tells amanda how many MB will fit on the tape, how big the filemarks
    # are, and how fast the tape device is.
    # A filemark is the amount of wasted space every time a tape section
    # ends.  If you run `make tapetype' in tape-src, you'll get a program
    # that generates tapetype entries, but it is slow as hell, use it only
    # if you really must and, if you do, make sure you post the data to
    # the amanda mailing list, so that others can use what you found out
    # by searching the archives.
    # For completeness Amanda should calculate the inter-record gaps too,
    # but it doesn't.  For EXABYTE and DAT tapes this is ok.  Anyone using
    # 9 tracks for amanda and need IRG calculations?  Drop me a note if
    # so.
    # If you want amanda to print postscript paper tape labels
    # add a line after the comment in the tapetype of the form
    #    lbl-templ "/path/to/postscript/template/label.ps"
    # if you want the label to go to a printer other than the default
    # for your system, you can also add a line above for a different
    # printer. (i usually add that line after the dumpuser specification)
    # dumpuser "operator"     # the user to run dumps under
    # printer "mypostscript"  # printer to print paper label on
    # here is an example of my definition for an EXB-8500
    # define tapetype EXB-8500 {
    #     lbl-templ "/usr/local/etc/amanda/config/lbl.exabyte.ps"
    define tapetype QIC-60 {
        comment "Archive Viper"
        length 60 mbytes
        filemark 100 kbytes         # don't know a better value
        speed 100 kbytes            # dito
    define tapetype DEC-DLT2000 {
        comment "DEC Differential Digital Linear Tape 2000"
        length 15000 mbytes
        filemark 8 kbytes
        speed 1250 kbytes
    # [email protected]
    # in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
    define tapetype DLT {
        comment "DLT tape drives"
        length 20000 mbytes         # 20 Gig tapes
        filemark 2000 kbytes        # I don't know what this means
        speed 1536 kbytes           # 1.5 Mb/s
    define tapetype SURESTORE-1200E {
        comment "HP AutoLoader"
        length 3900 mbytes
        filemark 100 kbytes
        speed 500 kbytes
    define tapetype EXB-8500 {
        comment "Exabyte EXB-8500 drive on decent machine"
        length 4200 mbytes
        filemark 48 kbytes
        speed 474 kbytes
    define tapetype EXB-8200 {
        comment "Exabyte EXB-8200 drive on decent machine"
        length 2200 mbytes
        filemark 2130 kbytes
        speed 240 kbytes
    define tapetype HP-DAT {
        comment "DAT tape drives"
        # data provided by Rob Browning <[email protected]>
        length 1930 mbytes
        filemark 111 kbytes
        speed 468 kbytes
    define tapetype DAT {
        comment "DAT tape drives"
        length 1000 mbytes          # these numbers are not accurate
        filemark 100 kbytes         # but you get the idea
        speed 100 kbytes
    define tapetype MIMSY-MEGATAPE {
        comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
        length 2200 mbytes
        filemark 2130 kbytes
        speed 170 kbytes            # limited by the Emulex bus interface, ugh
    # dumptypes
    # These are referred to by the disklist file.  The dumptype specifies
    # certain parameters for dumping including:
    #   auth        - authentication scheme to use between server and client.
    #                 Valid values are "bsd", "krb4", "krb5" and "ssh".
    #                 Default: [auth bsd]
    #   comment     - just a comment string
    #   comprate    - set default compression rate.  Should be followed by one or
    #                 two numbers, optionally separated by a comma.  The 1st is
    #                 the full compression rate; the 2nd is the incremental rate.
    #                 If the second is omitted, it is assumed equal to the first.
    #                 The numbers represent the amount of the original file the
    #                 compressed file is expected to take up.
    #                 Default: [comprate 0.50, 0.50]
    #   compress    - specify compression of the backed up data.  Valid values are:
    #                 "none"        - don't compress the dump output.
    #                 "client best" - compress on the client using the best (and
    #                                 probably slowest) algorithm.
    #                 "client fast" - compress on the client using fast algorithm.
    #                 "client custom" - compress using your custom client compression program.
    #                                   use client_custom_compress "PROG" to specify
    #                                   the custom compression program.
    #                                   PROG must not contain white space.
    #                 "server best" - compress on the tape host using the best (and
    #                                 probably slowest) algorithm.
    #                 "server fast" - compress on the tape host using a fast
    #                                 algorithm.  This may be useful when a fast
    #                                 tape host is backing up slow clients.
    #                 "server custom" - compress using your server custom compression program.
    #                                   use server_custom_compress "PROG" to specify
    #                                   the custom compression program.
    #                                   PROG must not contain white space.
    #                 Default: [compress client fast]
    #   dumpcycle   - set the number of days in the dump cycle, ie, set how often a
    #                 full dump should be performed.  Default: from DUMPCYCLE above
    #   estimate      Determine the way AMANDA does it's estimate.
    #                 "client"      - Use the same program as the dumping program,
    #                               this is the most accurate way to do estimates,
    #                               but it can take a long time.
    #                 "calcsize"    - Use a faster program to do estimates, but the
    #                               result is less accurate.
    #                 "server"      - Use only statistics from the previous run to
    #                               give an estimate,
    #                               it takes only a few seconds but the result is not
    #                               accurate if your disk usage changes from day to day.
    #                 Default: [client]
    #   encrypt  - specify encryption of the backed up data. Valid values are:
    #                 "none"   - don't encrypt the dump output.
    #                 "client" - encrypt on the client using the program specified by
    #                            client_encrypt "PROG".
    #                            Use client_decrypt_option to specify the decrypt-
    #                            parameter, default is "-d".
    #                            PROG and decrypt-parameter must not contain white space.
    #                 "server" - encrypt on the server using the program specified by
    #                            server_encrypt "PROG".
    #                            Use server_decrypt_option to specify the decrypt-
    #                            parameter, default is "-d".
    #                            PROG and decrypt-parameter must not contain white space.
    #                 Default: [none]
    #   exclude     - specify files and directories to be excluded from the dump.
    #                 Useful with gnutar only; silently ignored by dump and samba.
    #                 Valid values are:
    #                 "pattern"       - a shell glob pattern defining which files
    #                                   to exclude.
    #                                   gnutar gets --exclude="pattern"
    #                 list "filename" - a file (on the client!) containing patterns
    #                                   re's (1 per line) defining which files to
    #                                   exclude.
    #                                   gnutar gets --exclude-from="filename"
    #                 Note that the `full pathname' of a file within its
    #                 filesystem starts with `./', because of the way amanda runs
    #                 gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note
    #                 the final dot!)  Thus, if you're backing up `/usr' with a
    #                 diskfile entry like ``host /usr gnutar-root', but you don't
    #                 want to backup /usr/tmp, your exclude list should contain
    #                 the pattern `./tmp', as this is relative to the `/usr' above.
    #                 Please refer to the man-page of gnutar for more information.
    #                 If a relative pathname is specified as the exclude list,
    #                 it is searched from within the directory that is
    #                 going to be backed up.
    #                 Default: include all files
    #   holdingdisk - should the holding disk be used for this dump.  Useful for
    #                 dumping the holding disk itself.  Default: [holdingdisk auto]
    #                 "never"    - Never use the holding disk.
    #                 "auto"     - Use the holding disk if possible.
    #                 "required" - Always use the holding disk.
    #   ignore      - do not back this filesystem up.  Useful for sharing a single
    #                 disklist in several configurations.
    #   index       - keep an index of the files backed up.  Default: [index no]
    #   kencrypt    - encrypt the data stream between the client and server.
    #                 Default: [kencrypt no]
    #   maxdumps    - max number of concurrent dumps to run on the client.
    #                 Default: [maxdumps 1]
    #   maxpromoteday - max number of day for a promotion, set it 0 if you don't
    #                 want promotion, set it to 1 or 2 if your disk get
    #                 overpromoted.
    #                 Default: [10000]
    #   priority    - priority level of the dump.  Valid levels are "low", "medium"
    #                 or "high".  These are really only used when Amanda has no
    #                 tape to write to because of some error.  In that "degraded
    #                 mode", as many incrementals as will fit on the holding disk
    #                 are done, higher priority first, to insure the important
    #                 disks are at least dumped.  Default: [priority medium]
    #   program     - specify the dump system to use.  Valid values are "DUMP",
    #                 or "GNUTAR".  Default: [program "DUMP"].
    #   record      - record the backup in the time-stamp-database of the backup
    #                 program (e.g. /etc/dumpdates for DUMP or
    #                 /usr/local/var/amanda/gnutar-lists for GNUTAR.).
    #                 Default: [record yes]
    #   skip-full   - skip the disk when a level 0 is due, to allow full backups
    #                 outside Amanda, eg when the machine is in single-user mode.
    #   skip-incr   - skip the disk when the level 0 is NOT due.  This is used in
    #                 archive configurations, where only full dumps are done and
    #                 the tapes saved.
    #   starttime   - delay the start of the dump?  Default: no delay
    #   strategy    - set the dump strategy.  Valid strategies are currently:
    #                 "standard" - the standard one.
    #                 "nofull"   - do level 1 dumps every time.  This can be used,
    #                              for example, for small root filesystems that
    #                              only change slightly relative to a site-wide
    #                              prototype.  Amanda then backs up just the
    #                              changes.
    #                 "noinc"    - do level 0 dumps every time.
    #                 "skip"     - skip all dumps.  Useful for sharing a single
    #                              disklist in several configurations.
    #                 "incronly" - do only incremental dumps. This is similar
    #                              to strategy 'nofull', but will increase
    #                              the dump level as usual. Full dumps will
    #                              only be performed when an 'amadmin force'
    #                              has been issued
    #                 Default: [strategy standard]
    # tape_splitsize - (optional) split dump file into pieces of a specified size.
    #                 This allows dumps to be spread across multiple tapes, and can
    #                 potentially make more efficient use of tape space.  Note that
    #                 if this value is too large (more than half the size of the
    #                 average dump being split), substantial tape space can be
    #                 wasted.  If too small, large dumps will be split into
    #                 innumerable tiny dumpfiles, adding to restoration complexity.
    #                 A good rule of thumb, usually, is 1/10 of the size of your
    #                 tape.  Default: [disabled]
    # split_diskbuffer - (optional) When dumping a split dump  in  PORT-WRITE
    #                 mode (usually meaning "no holding disk"), buffer the split
    #                 chunks to a file in the directory specified by this option.
    #                 Default: [none]
    # fallback_splitsize - (optional) When dumping a split dump  in  PORT-WRITE
    #                 mode, if no split_diskbuffer is specified (or if we somehow
    #                 fail to use our split_diskbuffer), we must buffer split
    #                 chunks in memory.  This specifies the maximum size split
    #                 chunks can be in this scenario, and thus the maximum amount
    #                 of memory consumed for in-memory splitting.  Default: [10m]
    # Note that you may specify previously defined dumptypes as a shorthand way of
    # defining parameters.
    define dumptype global {
        comment "Global definitions"
        # This is quite useful for setting global parameters, so you don't have
        # to type them everywhere.  All dumptype definitions in this sample file
        # do include these definitions, either directly or indirectly.
        # There's nothing special about the name `global'; if you create any
        # dumptype that does not contain the word `global' or the name of any
        # other dumptype that contains it, these definitions won't apply.
        # Note that these definitions may be overridden in other
        # dumptypes, if the redefinitions appear *after* the `global'
        # dumptype name.
        # You may want to use this for globally enabling or disabling
        # indexing, recording, etc.  Some examples:
        # index yes
        # record no
        # split_diskbuffer "/raid/amanda"
        # fallback_splitsize 64m
    define dumptype always-full {
        global
        comment "Full dump of this filesystem always"
        compress none
        priority high
        dumpcycle 0
    # Dumptypes for gnutar
    define dumptype root-tar {
        global
        program "GNUTAR"
        comment "                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          

    Auntbeee4 wrote:
    I just bought the LG ALLY and would love to have the Accuweather widget on the phone. My problem is while my phone shows the correct time, (I am on Eastern here, but about 15 miles away in Illinois they are on Central) the Accuweather Widget is off by an hour showing Central time. I tried to sync it, but I can't find it in my list of sync-able programs. If someone can help it would be greatly appreciated. It's frustrating both me and a co-worker with the same phone/problem.
    Thank you!
    Amanda
    I have the same issue, Amanda. The weather widget that comes with the Ally was poorly written. The time issue is bad enough, but it takes up more screen space than is visible. Try it, if you touch and hold on the space below the widget, it will select it. This also means you can't add widgets or icons directly below it, resulting in a great deal of wasted space. 

  • BIAR File Import from XI 3.0 Enterprise into new XI 3.0 Enterprise System

    HI there,
    I am encountering an error message when I attempt to import BIAR files from our old Enterprise XI 3.0 system into our new Enterprise XI 3.0 System. When I use the Import Wizard it asks me what source to copy from and I choose the location of our BIAR files. Next I choose our CMS name and logon to it using the Adminstrator credentials. When I click next the process begins to import the file but then stops at 23% and gives an error message that says:
    Failed to open the BIAR file. Reason: come.businessobjects.sdk.biar.om.internal.iw.ObjectManagerIWException:A runtime rxception has occured in the Object Manager. null
    This is a very concerning issue as we backed up our entire enterprise system with the BIAR files. In total there are 43 of them, each between 500 to 600 megs in size for a total of about 23 gigs. We had hoped to import these files to restore our system from a major crash but now has us very concerned. Any help in resolving this would be appreciated as we are now desperate to recover 4 years worth of work. Thank you.

    Hi i have used Import wizard for importing the biar file in to the system and that too using the administrator in to BOXi3.1SP3 machine.
    I am getting the following error
    Logon Error:Failed to open the BIAR file.  Reason:com.businessobjects.sdk.biar.om.internal.iw.ObjectManagerIWException: A runtime exception has occurred in the Object Manager, null
    Please let me know if solutions to resolve this. What could be the problem while importing.
    The same bair is working on my local machine but not on the client side
    Thanks in advance

  • Comments on my proposed build using the P965 Platinum

    My current PC is over three years old and I'm itching to upgrade.  I'm starting off with Windows XP but will move to Vista eventually.
    This is what I've come up with so far and I'd welcome any comments:
    MSI P965 Platinum
    Intel Core 2 Duo E6600 2.4GHz
    2 x  Corsair TWIN2X 6400 DDR2, 2048MB CL5 Kit w/two matched CM2X1024A-6400 (4GB in total)
    HIS Radeon X1950PRO 256MB GDDR3, IcQ3
    Hiper PSU ATX 580W Black, Type-M
    Samsung SpinPoint T166 500GB SATA2
    LG DVD±RW burner, GSA-H42NRBB
    I'm not a game player but want to be able to run all the Vista eye candy when I eventually upgrade.  I do thrash my machine a fair bit with downloaded stuff that needs parity checking, decompressing and converting if necessary.  I also tend to have loads of applications running at the same time.  I'm not interested in overclocking.
    I also have the following questions:
    1. I understand that Windows XP won't recognise the full 4 GB of RAM, will Vista? 
    2. Is it worth having 4GB RAM under Windows XP in preference to 2GB?
    3. Can I get by installing without a floppy drive as my DVD Drive isn't a SATA one and I'll need the additional drivers.  Can a windows install recognise drivers on other media such as a memory card in a card reader attached via USB or a USB pen drive?
    4. Will my power supply be adequate?  I will be adding hard drives as time goes on and possibly another optical drive. 
    5. What advantage is there to running the SATA drives under AHCI and if necessary will I be able to pull the drive out and access it in another PC with a different BIOS?
    I've not built a machine for ages, so I'm well out of practice and spending ages on research.  I'll be grateful for any help you can give me.
    Thanks
    Teresa

    I do development and such. Run one or two VM's at a time. A lot of apps running at same time.
    I went with the P6N Platinum.   The chipset seems pretty good.
    I went with the E6600 and same RAM, although I went with 4 gigs due to the VM's running.
    After reading some reviews and such, I would recommend going with the Saphire 512 version of the X1950 Pro, which I did.  I'm running Vista Business and the Aero interface is good and my index from Vista, for what its worth, is about 5.9 with the 3-D stuff.
    I'm not familiar with the PSU.   While I've worked with a couple other major PSU companies, I have NEVER been burned by PC Power & Cooling's products.  A little more expensive, but they have been rock solid.  I've been able to hang onto their PSU's over the years until the wattage becomes too much of an issue, to which I buy whatever covers it.   
    I tend to never use anything other than Pioneer or Plextor on the optical stuff.  For video work and my experience in the duplication area, both companies products have far exceeded the performance, longevity and fewest coasters for the small difference in price difference.
    XP X64 will see the full 4 gigs.   X32 editions will not.  I would suggest going to X64 Vista when you make that move, however you'll have to do a clean install.   Drivers can be a bit of a tough thing, but I need rock solid performance and that gives me that.
    2 Gigs is really pretty good.  With XP, it will see the extra space and take around 500-600 megs to improve performance. With Vista, its about double that.  Running a lot of apps or doing some memory intensive apps, such as graphic suites, etc, you will not regret 4 gigs. That will lighten the load on disk paging.
    I didn't install a floppy.  I had to dig around and found some utilities for format a USB key and boot to a DOS.  So I use that, setting the bootup on the board to use the memory key as the initial bootup device.  From there I've been able to do RAM testing as well as flash bios.
    I'm running around a 520W PSU.  But its a solid 520.  But with the high performance card and 4 SATA HD's and the optical, I will probably upgrade up to the 750W PC Power and Cooling.  That's what is recommended by their selector for the board anyways.  For now, I have not found any problems in the PSU end.
    Lance

  • Why don't AM or PM appear on my emails?

    I set my Mac to 24 hour clock. It works perfectly in my lists of emails sent and received, but the times displayed on actual emails are ludicrous. Examples:
    01:59 shows as 1:59:16
    16:22 shows as 4:22:00
    My desire is to have the emails showing 24 hour clock time. Logically, having set the system thus, I'd expect that to occur. Can anyone help me with a solution, or is it bad programming?
    Alternatively, I could live with the times shown on emails, provided that AM or PM showed too. I tried to achieve that, without success. Here's what I did:
    System Preferences>International>Formats>Customize. Then I made the following selections:
    * Short. (So why are seconds showing on emails?)
    * 01-24.
    * Before noon: AM.
    * After noon: PM. (I reinstated the AM & PM after I didn't get 24 hour times on my emails.)
    I should be very grateful if somebody could advise me how to get AM & PM back. As shown in the two examples early in this posting, 12 hour times without AM or PM are totally confusing. How to kill seconds would be a bonus, but I can live with seconds.
    Please, when replying to me, no "computer speak". I'm new and should be grateful for blow by blow instructions.
    20" iMac Intel Core 2 Duo   Mac OS X (10.4.10)  

    Thanks for your latest response, David. I'm going to reply to your queries, in the order in which they appeared in your posting.
    Q: Does the problem persist if you quit Mail and open it again?
    A. Yes. It has persisted for many days, with nightly computer shutdowns.
    "> surely the Short choice means no seconds?"
    Your first paragraph stated that having the Short option chosen "has absolutely no effect on whether applications will use it for displaying date & time information." That leads me to advise you how I achieved 24 hour time in Mail. I followed the advice of Michael Lafferty in the iCal forum, about how to achieve 24 hour time in iCal. It worked and, as a bonus, gave me 24 hour time in the Mail message list. Unfortunately, it gave the crazy, inconsistent times on emails, which are the topic of this thread. Michael was answering the topic "24 Hour times in iCal" and the posting was at 6:42 PM on Feb 18, 2006. Here it is:
    This is a goofy Mac OS X 10.4 thing.
    Launch System Preferences and open the International preference pane in the Personal panel. Press the Formats tab and then the Customize… button in the center, under the Times section.
    Under the Show: Short menu, you should see two values listed, the first representing hours, and the second representing minutes. If you click on that first value, you should see a downward-facing triangle. Press it to drop-down a menu on the right hand side of the value, and select the 01-24 format choice. Press the OK button, and quit.
    iCal should display 24 hour times from that point on, though some users—all or most using releases prior to version 2—indicating that existing event times don't shift to 24 hour representation. All of mine did.
    PowerBook G4 12 867 MHz 640 meg 40 gig SuperDrive Mac OS X (10.4.5) paired with a Treo 600 on the T-Mobile network
    End of quote.
    Knowing the above may help you to determine what happened. It may also make your third paragraph question redundant, but I shall answer it , in case it is still relevant. I dragged the Mail display so wide that it took up the complete width of the Mac's screen. The time display was unchanged. It continued to hug the right hand side of the display, but with lots of empty space between it and the previous column.
    Returning to my problem, I was concerned that recipients of my emails would get the ambiguous and confusing times shown in para. 2 of my original posting. However, today a friend sent me a reply including my original message. Instead of showing the ambiguous time that was on my version of the email, it had it nicely expressed as a PM time.
    While I'd prefer that unambiguous times appeared on my version of emails, ( that is, as shown on my screen, ) I could live with garbage times, if I were sure that recipients would receive 24 hour, or AM/PM style times.
    So, my acceptable solutions, starting with my favourite, are as follows:
    1. 24 hour clock on my version of emails and on the recipients'.
    2. AM/PM on mine and the recipients'.
    3. Ambiguous on mine, provided I could be sure that recipients would receive intelligible times. My message list would show the correct times.
    I do realise that I could revert to AM/PM in iCal and in my Mail message list, if none of 1 to 3 were possible.
    I suspect that you're like me: like to resolve a problem! I suspect that I've given you a juicy one here and I really appreciate your help.
    20" iMac Intel Core 2 Duo   Mac OS X (10.4.10)  

  • Garbage Collector pausing my Server for MINUTES at a time

    Garbage Collection pauses are really crippling my server. Here is a grep of Full GCs from the log file. (The lines following each Full GC have a timestamp, yymmdd:hhmmss.sss)
    [Full GC 876186K->169083K(222400K), 28.4152794 secs]
    011120:004809.413:
    [Full GC 883850K->214246K(259008K), 68.2294388 secs]
    011120:033449.558: *** RECLAIMED MemoryManager( Idle ) - Memory Usage: 209.2 MB/900.0 MB (Free: 43.7 MB, Allocated: 252.9 MB)
    [Full GC 881484K->300898K(347200K), 73.3787317 secs]
    011120:045927.680: *** RECLAIMED MemoryManager( Idle ) - Memory Usage: 293.8 MB/900.0 MB (Free: 45.2 MB, Allocated: 339.1 MB)
    [Full GC 886225K->269194K(317824K), 79.8212023 secs]
    011120:055800.166: *** RECLAIMED MemoryManager( Idle ) - Memory Usage: 262.9 MB/900.0 MB (Free: 47.5 MB, Allocated: 310.4 MB)
    [Full GC 890405K->261774K(338112K), 104.6192760 secs]
    011120:064350.312: *** RECLAIMED MemoryManager( Idle ) - Memory Usage: 255.6 MB/900.0 MB (Free: 74.5 MB, Allocated: 330.2 MB)
    [Full GC 893451K->306762K(361024K), 134.4052782 secs]
    011120:073523.335: *** RECLAIMED MemoryManager( Idle ) - Memory Usage: 299.6 MB/900.0 MB (Free: 53.0 MB, Allocated: 352.6 MB)
    [Full GC 896034K->286275K(350016K), 103.4689894 secs]
    011120:081636.710: *** RECLAIMED MemoryManager( Idle ) - Memory Usage: 279.6 MB/900.0 MB (Free: 62.2 MB, Allocated: 341.8 MB)
    [Full GC 882755K->260923K(310272K), 129.6787672 secs]
    011120:093812.612: *** RECLAIMED MemoryManager( Idle ) - Memory Usage: 254.8 MB/900.0 MB (Free: 48.2 MB, Allocated: 303.0 MB)
    You can see that between 12:48am and 9:38am, the Server is pausing for a combined total of TWELVE MINUTES! Often for 2 whole minutes at a time, during which the Server is completely unresponsive.
    I have read Sun's GC tuning guide at http://java.sun.com/docs/hotspot/gc/index.html but it is not much help:
    It says "Pauses can be minimized by using a small young generation and incremental collection, at the expense of throughput."
    Well, I AM using incremental collection, and the young generation is the default size, which is quite small I believe. (32 MB max?)
    It also says "Unless you have problems with pauses, try granting as much memory as possible to the JVM. The default size (64MB) is often too small."
    Well I DO have problems with pauses, but I HAVE to allocate a ton of memory. The Server must support hundreds of simultaneous users, each with hundreds of K's of personal, dynamic, temporary data.
    It also says "Unless you find problems with excessive major collection or pause times, grant plenty of memory to the young generation. The default MaxNewSize (32MB) is generally too small."
    I AM having problems with excessive major collections and pause times, so according to this I should NOT grant more memory to young generation (eden).
    What am I left with? Nothing! I am totally out to lunch here. The box this is running on is a dual P3-600 with a gig of RAM and Red Hat 6.2, with Sun JRE 1.3.1_02. My startup command line options are:
    java -server -Xincgc -verbose:gc -Xms256M -Xmx900M
    What should I do? The Tuning guide essentially says to screw around with generation sizes, but none of its specific tips seem to apply to me! This is a production server and I am worried about making things worse by playing around, so I was hoping someone out there might have some experience with this and concrete advice before I just start messing around with the memory map. Should I increase the young generation size? Decrease it? Something else altogether? HELP!

    With default settings, I am getting horrible performance, under peak load, 25%-50% of server time is being spent with GC, approx. 11,000 minor GCs per hour! And a Full GC every hour or two which takes up several minutes. On average, I am losing 13.09 minutes per hour due to minor GC, and 54.5 seconds to major GC.
    I tried your settings, Chuck, and they seemed to be working beautifully at first... minor GCs were now occuring once every few minutes for a couple seconds, instead of 3 times per second for a tenth of a second. Minor GC were now taking 1.06 minutes per hour instead of 13.09, more than a 1300% improvement!
    HOWEVER...
    After 7 hours, the Server started getting REALLY slow for no apparent reason. It seemed almost as if reading from sockets was suddenly becoming extremely time intensive. Then I got a HUGE minor GC that took 25.6 seconds. [GC 507410K->478034K(551296K), 25.6328459 secs], then a couple minutes later, the Server CRASHED with this output:
    An unexpected exception has been detected in native code outside the VM.
    Unexpected Signal : 11 occurred at PC=0x40573aa7
    Function name=malloc
    Library=/lib/libc.so.6
    Current Java thread:
    Dynamic libraries:
    011121:231738.194: Search ( pizzala, lzh ) returned 50 results (28 ms)
    08048000-0804c000 r-xp 00000000 08:06 376904 /usr/local/java/jre1.3.1_01/bin/i386/native_threads/java
    0804c000-0804d000 rw-p 00003000 08:06 376904 /usr/local/java/jre1.3.1_01/bin/i386/native_threads/java
    40000000-40013000 r-xp 00000000 08:06 311298 /lib/ld-2.1.3.so
    40013000-40014000 rw-p 00012000 08:06 311298 /lib/ld-2.1.3.so
    40015000-40016000 r--p 00000000 08:06 2424834 /usr/share/locale/en_US/LC_MESSAGES/SYS_LC_MESSAGES
    40016000-40017000 r--p 00000000 08:06 2408452 /usr/share/locale/en_US/LC_MONETARY
    40017000-40018000 r--p 00000000 08:06 2408454 /usr/share/locale/en_US/LC_TIME
    40018000-40023000 r-xp 00000000 08:06 311344 /lib/libpthread-0.8.so
    40023000-4002a000 rw-p 0000a000 08:06 311344 /lib/libpthread-0.8.so
    4002b000-40034000 r-xp 00000000 08:06 1081477 /usr/local/java/jre1.3.1_01/lib/i386/native_threads/libhpi.so
    40034000-40035000 rw-p 00008000 08:06 1081477 /usr/local/java/jre1.3.1_01/lib/i386/native_threads/libhpi.so
    40035000-403b0000 r-xp 00000000 08:06 2769091 /usr/local/java/jre1.3.1_01/lib/i386/server/libjvm.so
    403b0000-403b1000 ---p 0037b000 08:06 2769091 /usr/local/java/jre1.3.1_01/lib/i386/server/libjvm.so
    403b1000-404fd000 rw-p 0037b000 08:06 2769091 /usr/local/java/jre1.3.1_01/lib/i386/server/libjvm.so
    40515000-40517000 r-xp 00000000 08:06 311314 /lib/libdl-2.1.3.so
    40517000-40519000 rw-p 00001000 08:06 311314 /lib/libdl-2.1.3.so
    4051a000-40607000 r-xp 00000000 08:06 311305 /lib/libc-2.1.3.so
    40607000-4060b000 rw-p 000ec000 08:06 311305 /lib/libc-2.1.3.so
    4060f000-40621000 r-xp 00000000 08:06 311318 /lib/libnsl-2.1.3.so
    40621000-40623000 rw-p 00011000 08:06 311318 /lib/libnsl-2.1.3.so
    40625000-40641000 r-xp 00000000 08:06 311316 /lib/libm-2.1.3.so
    40641000-40642000 rw-p 0001b000 08:06 311316 /lib/libm-2.1.3.so
    40642000-40676000 r-xp 00000000 08:06 704575 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so
    40676000-40682000 rw-p 00033000 08:06 704575 /usr/lib/libstdc++-2-libc6.1-1-2.9.0.so
    40684000-40695000 r-xp 00000000 08:06 1081479 /usr/local/java/jre1.3.1_01/lib/i386/libverify.so
    40695000-40697000 rw-p 00010000 08:06 1081479 /usr/local/java/jre1.3.1_01/lib/i386/libverify.so
    40697000-406b8000 r-xp 00000000 08:06 1081480 /usr/local/java/jre1.3.1_01/lib/i386/libjava.so
    406b8000-406ba000 rw-p 00020000 08:06 1081480 /usr/local/java/jre1.3.1_01/lib/i386/libjava.so
    406bb000-406cf000 r-xp 00000000 08:06 1081481 /usr/local/java/jre1.3.1_01/lib/i386/libzip.so
    406cf000-406d2000 rw-p 00013000 08:06 1081481 /usr/local/java/jre1.3.1_01/lib/i386/libzip.so
    406d2000-41400000 r--s 00000000 08:06 1081510 /usr/local/java/jre1.3.1_01/lib/rt.jar
    4142d000-416d2000 r--s 00000000 08:06 1081511 /usr/local/java/jre1.3.1_01/lib/i18n.jar
    416d2000-416e8000 r--s 00000000 08:06 1081498 /usr/local/java/jre1.3.1_01/lib/sunrsasign.jar
    77a9f000-77ab5000 r--p 00000000 08:06 2408451 /usr/share/locale/en_US/LC_CTYPE
    77ab5000-77abd000 r--p 00000000 08:06 2408450 /usr/share/locale/en_US/LC_COLLATE
    77abd000-77abe000 r--p 00000000 08:06 2408453 /usr/share/locale/en_US/LC_NUMERIC
    77abe000-77abf000 r-xp 00000000 08:06 1622117 /usr/lib/gconv/ISO8859-1.so
    77abf000-77ac0000 rw-p 00000000 08:06 1622117 /usr/lib/gconv/ISO8859-1.so
    77ac1000-77ac9000 r-xp 00000000 08:06 311336 /lib/libnss_files-2.1.3.so
    77ac9000-77aca000 rw-p 00007000 08:06 311336 /lib/libnss_files-2.1.3.so
    77b37000-77b40000 r-xp 00000000 08:06 1081484 /usr/local/java/jre1.3.1_01/lib/i386/libnet.so
    77b40000-77b41000 rw-p 00008000 08:06 1081484 /usr/local/java/jre1.3.1_01/lib/i386/libnet.so
    77b41000-77b45000 r-xp 00000000 08:06 1081513 /usr/local/java/jre1.3.1_01/lib/i386/libNBIO.so
    77b45000-77b46000 rw-p 00003000 08:06 1081513 /usr/local/java/jre1.3.1_01/lib/i386/libNBIO.so
    77b46000-77b4f000 r-xp 00000000 08:06 311342 /lib/libnss_nisplus-2.1.3.so
    77b4f000-77b51000 rw-p 00008000 08:06 311342 /lib/libnss_nisplus-2.1.3.so
    77b51000-77b59000 r-xp 00000000 08:06 311340 /lib/libnss_nis-2.1.3.so
    77b59000-77b5b000 rw-p 00007000 08:06 311340 /lib/libnss_nis-2.1.3.so
    77b5b000-77b5e000 r-xp 00000000 08:06 311334 /lib/libnss_dns-2.1.3.so
    77b5e000-77b5f000 rw-p 00002000 08:06 311334 /lib/libnss_dns-2.1.3.so
    77b5f000-77b6b000 r-xp 00000000 08:06 311346 /lib/libresolv-2.1.3.so
    77b6b000-77b6c000 rw-p 0000b000 08:06 311346 /lib/libresolv-2.1.3.so
    Local Time = Wed Nov 21 23:17:38 2001
    Elapsed Time = 26581
    # The exception above was detected in native code outside the VM
    # Java VM: Java HotSpot(TM) Server VM (1.3.1_01 mixed mode)
    # An error report file has been saved as hs_err_pid20055.log.
    # Please refer to the file for further information.
    Yummy. Signal 11's really make my day fun :(. I tried restarting the Server, but it crashed again in the same way 15 minutes later. Then I switched back to default settings and it has run fine all weekend.
    The Sig11 makes me think either our C lib is buggy (our Linux distro is getting a bit old), or we have a physical memory problem. Odd that it only shows up when I tried your new settings though...

  • After reformatting hard drive, iPod syncs very slowly with iTunes

    A couple of months ago I had to reformat my computer's hard drive. I keep all my music files on an external hard drive. After reformatting, the man who did this for me reloaded iTunes for me and imported all my music back into my iTunes library.
    It seems that since that time, when I sync my iPod to the iTunes library, it takes many times longer than it used to. Maybe something else happened to my iPod or iTunes and the reformat is just a conincidence, but it really does seem to take three or four times longer to sync.
    I have iTunes 7.4.1.2 and my iPod is an older one, a 40G with dock connector
    Also, I recently bought some audiobooks to put on my iPod. I only had about 600megs available so the iPod would not sync. I then removed several Gigs from my iTunes library. When I click on the "music" icon under "library" it shows that I have only a little over 29G used which should leave well over 5 plus Gigs available for the new music. But when I try to sync the iPod, it gives me the message that I have only approx. 600 megs available. What's up. I never have had this problem before and I have had the iPod for several years.
    Any ideas or suggestions?
    Thanks,
    Dennis

    I actually learned yesterday that Apple didn't put USB 2.0 in their Macs until G5... something I was VERY irritated to find out. Turns out they were betting that Fire Wire would take off instead of USB 2.0, so they only equipped their machines with USB 1.1. So as a result, my iPod is unacceptably slow. Other nagging problems like this are convincing me that I'll have to get a new Mac Pro in the coming year, but for the meantime I think I'll be buying a USB 2.0 PCI card.
    Thanks for your response.

  • Huge increase over past few months on data usage.

    Huge increase in data traffic, even at times when systems are in sleep mode - like at 6am in the morning.  For months by usage levels varied between 10Gig and 12 Gig and I would adjust my plan as needed to prevent single Gigabyte overcharges.  However, in the past 4-6 months I have had to go to 15GB then 20GB, and what we actually do internet wise has not changed any where near that much.  Yesterday I had 600 meg of data transferred at about 6am when all systems were either off or in sleep mode.  The usage tool on verizon is no help in identifying what is driving this other than broad categories.
    Last night I turned off the MiFi device and there was no data recorded until I turned on at 8:30am then it recorded 800 megabytes only based on turning on the PC and not even using it.  And the hard file light was on solid for a long long time.
    I really need a tool that runs on the PC that shows what program or service is doing this much internet traffic.  I have seen disk I/O using Windows Task Manager that shows a number of Chrome services actively working I/O, as well as Google sync, but there is nothing new here that I have done over the past 6 months - my usage is very consistent. And that tool does not show who is driving the MiFi load.
    How can I get a handle on this?  This is getting very expensive and there is no obvious answer why.

    Personally, I use BitMeter OS for my PC. Any bandwidth from your computer (down/up) is logged & you can view certain days to see when it was used.
    https://codebox.org.uk/pages/bitmeteros
    Also, you may be able to view Mobile AND WiFi data usage (separate tabs) on your mobile devices, under Settings > Data Usage. Click the 3 dots for options.
    I had the same issue, but it was due to Verizon Cloud backing up... all 12gb (mostly pictures I don't even care about!).
    You may have that or another app that syncs data. It should tell you under Data Usage, though.
    I disabled Verizon Cloud through the App Manager.
    Hope that helps!

  • My data never works and voice hardly works.  Why do I have to pay so much?

    I currently pay roughly $180/month for 3 phones that get next to no use.  This is because the phone barely function, or I should say the network barely functions.  My "4G" data works maybe 10% of the time.  It usually flips to 3G after a couple seconds of use making it unusable.  I was so excited when Verizon gave me another gig of data to not be able to use!
    Voice is horrible.  I can't make or receive calls most of the time.  I always just let it go to voicemail so I can have Google Voice email me the message.  It works 20 times better than trying to actually have a conversation on my phone. 
    Verizon: please either cut my bill down dramatically or let me out of my contract.  2 of my lines only have a few months left anyways and I will not be renewing.  I can't continue paying so much for a service I can't use.  Please don't make me go to the BBB again.  I don't like doing that but it seems like that is the only way you will listen.

    The main zip code is 49512.  Its right near the Gerald R Ford Airport, so I don't see why there wouldn't be awesome coverage.
    The other 2 lines do have a ton of issues as well.  My son complains at least a couple times a week that his texts aren't working and my mother who uses the other line can hardly ever get through when she tries to make calls.
    I moved to this address about a year ago and I thought it would fix my service issues because I have had problems with service in the past.  Unfortunately the move did not help.  I am not sure what's wrong with the network but its frustrating.
    I checked my usage for the past few months and we have never used more than 600 megs of data and 700 minutes.  That's between 3 lines with no home phone.  Do you understand how frustrating it is every time I have to pay this bill?  I feel like the only reason I pay it is to avoid ETFs, not because I use the service.
    Please tell me what I need to do to get rid or this service or cut the price dramatically to make it reasonable for the level of service I am getting.

  • Deleting rows kills the process!

    Hi everybody
    I've installed Oracle XE 10.2.1.0 in my dev environment: Windows XP and 2 gig RAM.
    I've loaded about 600k rows in a table, which size is about 90 meg. When I try to delete these rows, the xe instance goes down, propably due to memory usage(?). This happens both in SQL Developer and in my Java application. In the web console the memory usage is 600 meg. (Seems a bit high compared to the amount of data I've put in)
    Unfortunately I'm a total newbie to tuning databases, so I'm hoping to get some hints in here:-)
    Some extracts from the logs, don't know if all is relevant or enough info for you people:
    bdump:
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2208K exceeds notification threshold (2048K)
    udump:
    Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
    Windows XP Version V5.1 Service Pack 2
    CPU : 2 - type 586
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:975M/2014M, Ph+PgF:2808M/3906M, VA:1371M/2047M
    Instance name: xe
    alert_xe.log
    Tue Dec 16 11:04:08 2008
    Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_psp0_4340.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    xe_psp0_4340.trc:
    *** 2008-12-16 11:04:08.364
    *** SERVICE NAME:(SYS$BACKGROUND) 2008-12-16 11:04:08.239
    *** SESSION ID:(48.1) 2008-12-16 11:04:08.239
    error 1242 detected in background process
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    Edited by: user506406 on Dec 16, 2008 2:36 AM

    "data file suffered media failure"
    One of your data files is buggered. You could try chkdsk and see if that fixes it (though I'd be inclined to back up anything important on the machine first).
    You could try dropping that data file and recreating it, but if there is an underlying problem on the disk, it may not solve the issue.

  • 10.5.6 Combo download; apparently nothing there

    I've tried unsuccessfully to download the Combo update from the Apple site twice now, and it stops short of the 600+ Meg transfer, and all that I can see in Safari's download manager is a message under the file name that says that the Disk Image could not be mounted. Any ideas why I can't seem to get the update onto my Mac? And has anyone else run into this?
    I've done my Time Machine backup and repaired permissions, but I just can't seem to get the file so I can finish (start?) the upgrade. Strange indeed.
    Tony

    Well, it may have been an ISP issue. It was too late for me to try to get ahold of my provider for tech support, so I figured what the heck, I'll give the download another shot. Looks like the third time "was the charm", since it fully downloaded and mounted, giving me the Installer dialogues that I was expecting.
    So now it's late, I'm going to bed, and I'll see how the upgrade goes tomorrow. Many thanks for the response.
    Tony

  • FlexBuilder 3 Memory Settings - FlexBuilder.ini

    I am wondering if anyone has found out an optimal configuration for FlexBuilder3 for utilizing RAM. Currently I have some flex apps that almost instantly take Flex to 600+ megs of ram after viewing one item in design mode. Any ideas for optimal tweaks to FlexBuilder.ini file?
    Here is the one I use below currently. Any ideas appreciated.
    -vmargs
    -Xms512m
    -Xmx1024m
    -XX:MaxPermSize=256m
    -XX:PermSize=64m
    -Djava.net.preferIPv4Stack=true
    My PC setup is XP SP3 32-Bit with 4 gigs of Ram

    So what does the Flex Forum think?

  • Turning to next page increasingly slower as page number higher

    I noticed that the time required for turning to the next page increases more or less linearly with the page number, i.e. moving from page 10 to 11 takes about ten times as long as moving from page 1 to 2. This is soon becoming very annoying!
    Anybody with a similar experience?
    Solution?

    Niel, thanks for the clarification.
    I the page turning was linear both in safari & TenFourFox.
    Safari page 4 - 8 seconds, 5-7, 7-9, 12-8, 13-10,18-10, &  24-10
    TenFourFox page 5 - 11 seconds, 6-11, 7-10, 9-13, 10-12, 11-11, 21-12, 22-13, & 23-12
    What does this mean?
    1) As a test, you should try this in a clean environment.  only one web browser running.  only one window with only one tab
    2) Run activity monitor.  See what may be interfering.
    Macintosh-HD -> Applications -> Utilities -> Activity Monitor
    3) a swag at the problem...
    You may want to run these "standard" fixes if the problem persists.
    Check the amount of free space on your harddrive.  You should have a several gigs free.
    You should run disk utility
    a) verify the disk
    b) update your permissions.
    Try a safe boot.
    Shutdown your machine.  Hold down the shift key.  Poweron.  Wait awhile Wait awhile while you harddrive is being checked.
    http://support.apple.com/kb/ht1455
    You may want to run applejack to clean up your machine.
       http://applejack.sourceforge.net/
    I am using Tiger 10.4.11 on an imac g3 600.
    Too bad I can't combing Safari & TenFourFox.  Safari seems to load pages faster than TenFourFox, but seems to slow down after the page is loaded ... Javascript?

Maybe you are looking for

  • Dynamic Receiver Determination [W/O using BPM] Sync interface

    I have been exploring options w.r.t. performance sensitive service interface. This has following issues : 1. Gets a org code looking up instance and route the msg. accordingly to an RFC and get response back. 2. Prominent answer would be Enhanced rec

  • Need help printing in classic to hp laserjet 3050

    when I try to print a classic document it can't find my printer. I look in chooser and it's not there. I have both the mac os X 10.3.9 and the mac 9.1. No problems with os X

  • When I backup my phone on iCloud the files in my Numbers app do not show in my back. Before backing up the Numbers

    When i backup my iPhone 5 on iCloud my files in Numbers app do not show in my PC when I log into my iCloud account. Before backup the switch for Numbers & Document & Data are both swithed on too, yet it does not show why ?

  • Need help adding links to carousel menu

    Here is the code I have now: var numOfItems:Number = 4; var radiusX:Number = 150; var radiusY:Number = 55; var centerX:Number = Stage.width/2; var centerY:Number = Stage.height/2 + 30; var speed:Number = 0.05; for(var i=1;i<numOfItems+1;i++) {       

  • IT 0045 issue

    Dear all I hired one employee and ran payroll for the month of April 2011. This employee have IT 0008, 0014, and 0045. From 01.05.2011 onwards this employee is on Deputation. so i had delimit 0014  and 0045. after that i ran payroll for May 2011. but