Problems with X-FI on central spea

Hi. I'm italian and it's the first time I write on this forum. I have?problems with X-Fi Extreme Gamer Fatalty on Windows XP SP2. My central speaker doesn't work, only scratches. I have removed?X-Fi and reinstalled, but nothing is changed. I read on this forum about many problems with this card. With coaxial?on THX mode central speaker sounds but not very good as the other speakers, music and games have bad sound. The driver is updated. CMSS is on. I've changed the speaker and made all the proves, without results. Please, can you help me. Thank you all.

So, have you tried to adjust it already, through ASIO panel?
Is the ASIO driver you're using there the Creative one, or one of those bundled w/ Cubase?
If you try w/ Asio4All, is the situation still the same?
- http://www.asio4all.com (not sure if Asio4All is working in Vista at all)
jutapa

Similar Messages

Problem with movies in Media Central

I've converted several movies to MP4. When I go to play them in Media Central they are very choppy, however, when playing through Front Row they are fine.
Anyone have any idea what might be causing this?
Thanks.

Since front row is playing fine - I would suspect the mac and the movie are working correctly.
You might report what the memory usage is when trying to play the movies with media central. Then I would contact the authors of that program and see if your system meets their recommended specifications for playing back a movie.
Just curious - what sort of data rate is your movie? What codec is used for the video and audio? At some point - any movie will cause even the fastest computer to choke when the numbers of bits being pushed is too great for the system to keep up. Perhaps media central isn't coded as efficiently as front row and needs movie files with less bits to play on your hardware.
If you haven't bought a 2G chip for your mini - I'd recommend that as the first thing you splurge on - RAM makes almost everything faster and if you are swapping anything - it will make playback more smooth if you can keep the programs in RAM and only have the data come from disk.

A few problems with my site I'd be grateful for help with...

Hi, I'm encountering some strange problems with my website, and I'd be really appreciative if anyone could help me. The site's live so I've included links to help anyone kind enough to respond. Thanks in advance.
1. On many of the pages, a scrollbar appears at the width of the container as opposed to the browser window. The 'clear' property doesn't seem to work, (although I am quite new to it so could have made some sort of basic error).
http://austinlindsay.com/suretowin.html
2. I'm having difficulty with the 'screenshots' on the left hand side of the page. First, the larger images should only appear when hovering over the thumbnails, but they seem to appear when hovering over the space where they appear.
The second problem is trying to make the background of the larger images consistent with their individual images in the foreground. Problem is the background always have a fixed width across the page. You can see what I mean when hovering over the final screenshot (called 'Scoreboard')
http://austinlindsay.com/virtuoso.html
Two problems with the 'Featured' section. The central link jilts slightly when hovered over. It's really strange. I've tested it by changing the order and putting a different link in the centre, and found it's not a problem with a link, it's a problem with it being positioned centrally. I couldn't find a solution for it, though. The final problem with this is that a horizontal scrollbar appear when hovering over any of the links (apart from the final one, Logos, for some reason).
http://austinlindsay.com/
I know there's a lot of problems here, but thanks in advance to anyone who can help!

No, there is definitely no height property on the container (or the content which is causing the problem). But to be fair, it may be because the content that gets hidden is, until hovered over, not visible. I've posted the code for that below, along with the container if anyone could help?
/*main container*/
#content {
    position: relative;
    left: 0px; right: 0px;
    width: 960px;
    background-color: #333;
    padding-bottom: 3em;
    border-top: 0.1em solid #FFF;
    border-bottom: 0.1em solid #FFF;
    overflow:hidden;
/* container for the screenshots content below this*/
#main_content {
position: relative;
margin: 0 40px;
top: -160px;
/* screenshots - content that seems hides itself*/
#screenshot_list {
position: relative;
left: 72px;
#screenshot_list a {
border:none;
text-decoration:none;
padding: 5px 0px;
display:block; /**space between icons**/
position: relative;
width:150px;
#screenshot_list a span {
visibility:hidden;
display:block;
position: absolute;
/**adjust positioning of full size images in px or %**/
left: 130px;
top: 0px;
/**optional image captions**/
font-size: 13px;
line-height: 1.2;
color: #FFFFFF;
text-align: left;
background-color: #455c5a;
background-repeat: no-repeat;
/**optional image borders & padding**/
border: 2px solid#455c5a;
padding: 15px;
z-index: 100;
#screenshot_list a:hover span, #screenshot_list a:active span, #screenshot_list a:focus span {visibility:visible; z-index: 100;
padding: 15px;
#screenshot_list a:hover, #screenshot_list a:focus
{visibility:visible;
border: none;
z-index: 100;
padding-left:2px;

Problem with LSMW - G/L Account Centrally for 2 or more Company Codes.

Hi,
I have a problem with an LSMW G/L Account Centrally Master Data.
I used the Object: 0010 GL A/C Master Record, and the Method: 0001 Hier. structure.
I can create massives Accounts but I can't create Same Accounts with differents Company Codes.
Please, somebody can explain me, how create Same Accounts with differents Company Code in masive form with LSMW?
Thanks and Regards!

Try this report RFBISA10: "Copy General Ledger Account Master Data: Send"
or RFBISA20: "Copy G/L Account Master Data in Target Company Code: Receive"
Bye.

N79 - problem with central navigation key

I've got a problem with my N79. The central navigation key refuses to work after I play a N-gage game (hooked on, to be specific). Rebooting helps but it's so irritating.
Anyone knows how to solve this?
N71 ---> N79

Update:
I tried a couple of other N-gage games - the central key didn't freeze.
A strange thought vame to me - those games were trial, Hooked on is paid by activation number. And i don't remember having problems when I played Hooked on in trial mode. 0_0
Aha, I just found another way to unfreeze the central key - the keylock slider. It's much better than rebooting, but not less irritating.
N71 ---> N79

I have been having problems with my FaceTime for the last few weeks. Up to then I was able to use it daily and then it suddenly stopped functioning. I have 4 friends in the same situation. Is there a problem centrally with Apple? Anyone else with problems

I have been using FaceTime regularly over the past year or so and suddenly it has stopped working. It seems to dial up and says its connecting and then just switches off. I have a number of other friends who are also having problems with this and also on their iPhones. Does anyone have an answer to this problem?

Make sure all parties are running IOS 7.1.1
http://support.apple.com/kb/TS5419

Problem with non central adapter engine

Hi All,
I have a peculiar issue with adapters on non central AE. We are able to get messages through the sender soap adapter on non central AE to the IE. But messages going to the receiver soap adapters on non central AE are failing in IE with 401 Unauthorized.
Please suggest how to check this.
Thanks,
Kiran

hi,check the below link
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/webinars/configuring%20a%20local%20adapter%20engine%20to%20work%20with%20a%20central%20instance%20-%20webinar%20powerpoint.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c50cddbb-0601-0010-92a7-f2a40ca68e6d
note:reward points if solution found helpfull.....
regards
chandrakanth.k

I have problem with adobe bridge cs6. Every time I open it Bridge tells me to Purge Cache. I have CS

I have problem with adobe bridge cs6. Every time I open it Bridge tells me to Purge Cache. I have CS6 on two computers and it works fine on one of them. I have tried to reinstall it without succeeding to fix the problem. Does anyone have the same problem and a solution to it?
"Bridge encountered a problem and is unable to read the cache. Please try purging the central cache in Cache Preferences to correct the situation."

You must have a Mac. Try this.
Quit Bridge, from user library (NOT system and root library) preferences folder find and delete the com.adobe.bridge5.plist file manual. Do this also in same user library caches folder (Caches/Adobe/Bridge CS6) and inhere find and the folder called 'cache' and drag it to the trash.
restart Bridge holding down option key and choose reset preferences, then try again.

Problem with RFC connection - tp program not registered

Hello everyone
recently there has appeared a problem with the RFC connection on our system - we received the following set of messages:
Trace file opened at 20101221 130738 Central European Standard Time, SAP-RE
======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Tp program is not registered.
ABAP Programm: RSRFCPIN (Transaction: SM59)
User: xxx(Client: 100)
Destination: SIDRFC_IFSAPHRCZPKCP (handle: 2, , )
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Program transakcji nie jest zarejestrowany
DEST =SIDRFC_IFSAPHRCZPKCP
HOST =%%RFCSERVER%%
PROG =IFCZPKCP
GWHOST =ssapprod
GWSERV =sapgw21
I tried to register program with a command:
rfcexec -aIFCZPKCP -gssapprod -xsapgw21
but with no success - the program didn't appear on the list of logged clients on the system in gateway monitor. Frankly speaking we do not know now what else we can do - please help!
We have ECC 6.0 (SAP_BASIS 700 SP18) on Windows Server 2003 R2 x64.
Thanks in advance for any help.
Regards
Peter

Hi Salim
thanks for your reply.
./rfcexec -a(PROG_ID) -gssapprod -xsapgw21 &
The syntax you're providing refers to UNIX systems, but I did similar thing on our Windows system - I tried all of the following methods (unfortunatelly without success):
rfcexec -a(PROG_ID) -gssapprod -xsapgw21
full_path_to_rfcexec.exe -a(PROG_ID) -gssapprod -xsapgw21
rfcexec -a(PROG_ID) -gssapprod.domain -xsapgw21
full_path_to_rfcexec.exe -a(PROG_ID) -gssapprod.domain -xsapgw21
Can you advise me what to do now?
Thanks
Piotr

Problem with comma and point

Hello,
I have a problem with comma and point in a double-digit.
I use a english driver for HM8142. When I get the values then I only get
int-digits. How can I change "Use comma as separator" . I tried to change
the option in LabVIEW.
I changed it, then I got the window. "To change, restart the programm". I
have done this. But when I have a look at the option, it is not changed.
What can I do?
I am not the admin on the computer.
Martin

Hi Martin,
you do not have to change any system settings neither in LabVIEW nor in your windows.
All instrument drivers should use a point as decimal separator. You can overwrite the decimal point handling in the string functions "Scan from string" and "Format into string".
Make a right click on the function and use "Edit Scan String". In the dialog open the ring under "Selected operation", the last entry allows you to set the character for the decimal separator. This separator will be used for all the following floating point numbers.
From your name and problem I think you are located in central europe. I do not have a german version of LV so I cannot tell you how the elements are named in german.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Problem with MSI Board and MSI Geforce 4 with Windows XP

I have a MSI 845E Max(MS-6566E)
MSI Geforce 4 - 420
Celeron 1.7 gig
Soundblaster Live
2 Network Cards
and the usual stuff.
I have loaded Windows 98 on my system and it works fine. But then I load Windows XP on and the system starts rebooting. After it reboots my video resets itself and I have to load it back in. I will then reboot and sometimes it will work, sometimes it will not. I try playing a game or even searching the net for awhile, but out of the blue the system will give a very quick blue screen and reboot. And of course when it boots up the video is reset. I loaded all the drivers I could find on MSI's website and used every video driver made by Nvidia and MSI. If I do a Windows XP update to my system the computer will not even boot up. it will just keep rebooting when it is trying to bring up the login screen. Anyone else run into this with Windows XP?

My system sometime freezes. Why ???
P4 1.8A GHz Notrtwood, 256MB PC2700, MSI Geforce 4 TI4400, SB Live 1024
Check my logs:
1)
// Watchdog Event Log File
LogType: Watchdog
Created: 2002-07-23 20:03:27
TimeZone: -60 - Central Europe Standard Time
WindowsVersion: XP
EventType: 0xEA - Thread Stuck in Device Driver
// The driver for the display device got stuck in an infinite loop. This
// usually indicates a problem with the device itself or with the device
// driver programming the hardware incorrectly. Please check with your
// display device vendor for any driver updates.
ShutdownCount: 108
Shutdown: 0
EventFlag: 1
EventCount: 1
BreakCount: 1
BugcheckTriggered: 1
DebuggerNotPresent: 1
DriverName: nv4_disp
DeviceClass: Display
DeviceDescription: NVIDIA GeForce4 Ti 4400
HardwareID: PCIVEN_10DE&DEV_0251&SUBSYS_87111462&REV_A3
Manufacturer: NVIDIA
DriverFixedFileInfo: FEEF04BD 00010000 0006000D 000A0BD6 0006000D 000A0BD6 0000003F 00000008 00040004 00000003 00000004 00000000 00000000
DriverCompanyName: NVIDIA Corporation
DriverFileDescription: NVIDIA Compatible Windows 2000 Display driver, Version 30.30
DriverFileVersion: 6.13.10.3030
DriverInternalName: nv_disp.dll
DriverLegalCopyright: (c) NVIDIA Corporation. All rights reserved.
DriverOriginalFilename: nv_disp.dll
DriverProductName: NVIDIA Compatible Windows 2000 Display driver, Version 30.30
DriverProductVersion: 6.13.10.3030
2)
// Watchdog Event Log File
LogType: Watchdog
Created: 2002-08-12 18:53:23
TimeZone: -60 - Central Europe Standard Time
WindowsVersion: XP
EventType: 0xEA - Thread Stuck in Device Driver
// The driver for the display device got stuck in an infinite loop. This
// usually indicates a problem with the device itself or with the device
// driver programming the hardware incorrectly. Please check with your
// display device vendor for any driver updates.
ShutdownCount: 235
Shutdown: 0
EventCount: 8
BreakCount: 8
BugcheckTriggered: 1
DebuggerNotPresent: 1
DriverName: nv4_disp
EventFlag: 1
DeviceClass: Display
DeviceDescription: NVIDIA GeForce4 Ti 4400
HardwareID: PCIVEN_10DE&DEV_0251&SUBSYS_87111462&REV_A3
Manufacturer: NVIDIA
DriverFixedFileInfo: FEEF04BD 00010000 0006000D 000A0C0A 0006000D 000A0C0A 0000003F 00000008 00040004 00000003 00000004 00000000 00000000
DriverCompanyName: NVIDIA Corporation
DriverFileDescription: NVIDIA Compatible Windows 2000 Display driver, Version 30.82
DriverFileVersion: 6.13.10.3082
DriverInternalName: nv_disp.dll
DriverLegalCopyright: (c) NVIDIA Corporation. All rights reserved.
DriverOriginalFilename: nv_disp.dll
DriverProductName: NVIDIA Compatible Windows 2000 Display driver, Version 30.82
DriverProductVersion: 6.13.10.3082
3)
// Watchdog Event Log File
LogType: Watchdog
Created: 2002-09-07 22:22:41
TimeZone: -60 - Central Europe Standard Time
WindowsVersion: XP
EventType: 0xEA - Thread Stuck in Device Driver
// The driver for the display device got stuck in an infinite loop. This
// usually indicates a problem with the device itself or with the device
// driver programming the hardware incorrectly. Please check with your
// display device vendor for any driver updates.
ShutdownCount: 408
Shutdown: 0
EventCount: 14
BreakCount: 14
BugcheckTriggered: 1
DebuggerNotPresent: 1
DriverName: nv4_disp
EventFlag: 1
DeviceClass: Display
DeviceDescription: NVIDIA GeForce4 Ti 4400
HardwareID: PCIVEN_10DE&DEV_0251&SUBSYS_87111462&REV_A3
Manufacturer: NVIDIA
DriverFixedFileInfo: FEEF04BD 00010000 0006000D 000A0FC9 0006000D 000A0FC9 0000003F 00000008 00040004 00000003 00000004 00000000 00000000
DriverCompanyName: NVIDIA Corporation
DriverFileDescription: NVIDIA Compatible Windows 2000 Display driver, Version 40.41
DriverFileVersion: 6.13.10.4041
DriverInternalName: nv_disp.dll
DriverLegalCopyright: (C) NVIDIA Corporation. All rights reserved.
DriverOriginalFilename: nv_disp.dll
DriverProductName: NVIDIA Compatible Windows 2000 Display driver, Version 40.41
DriverProductVersion: 6.13.10.4041

Problem with users accessing sharepoint 2013 site collection

I have an unbeliveable problem..
I have a sp site with several site collections..
I have around 15 users.. Everybody have access to the root site. Two users do not have access to site collections even though they are in EXACTLY same permission groups like other users who can access those site collections!
I tried to delete them from all user groups in SP, then delete their user profiles in Central Administration, and delete them from Active Directory. After that I recreated their profiles in Active directory, readded them to Central Administration, and again
added them to coresponding groups in SharePoint site collections. They again CAN NOT ACCESS site collections.
What should I do.. This is incredible that 5 users with the same user privileges can access site collections, and 2 can not, even though they are all created in the same way..
Regards,
Srdjan

Hello,
Have you found a solution for this problem? I have the exact same problem with 2 users accessing a site collection (access denied). I found also this row on uls log:
Access Denied. Exception: Attempted to perform an unauthorized operation., StackTrace:   at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(Exception ex)     at Microsoft.Office.Project.PWA.PJBaseWebPartPage.OnPreInit(EventArgs
e)     at System.Web.UI.Page.PerformPreInit()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()     at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionSt... 6955b79c-c42c-50fc-84f8-2b68f97002ea

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.

Problem with users in portal - login conflict with LDAP.

Hi.
Let me describe our problem:
We've a EP5 portal with LDAP conected to a central LDAP server, users access with the same user and password to all the different systems.
The problem happens to users who have theyr passwords expired. We already set to 0 the password expiration days to avoid future problems but that didn't applied to the already expired ones.
This affected users cannot change the password due to problems with the connection rights to LDAP server.
We're trying to find the place there it's set that the user is in some kind of "password expired" status, directly in a database table if neccesary, to change the status manually, as system does not allow os to set it by user administration in portal.
Any suggestions would be appreciated.

Restoring expired Portal passwords
Solved

Problem with Crystal Report Job Server Destinations

I am using Crystal Reports XI Server and I am having problems with scheduling. I believe that the problem is that I have not enabled any destinations under the Crystal Reports Job Server. The following is an observation list:
-Enabled and set up all destinations for other servers, such as the Destination Server.
-Have been able to use Infoview to directly email, inbox, and file save reports in different formats (I believe the Destination Server controls this, right?)
-All servers are enabled in the Central Configuration Manager
-Have been able to go into the Crystal Reports Job Server within the CMC, but I DO NOT FIND ANY destinations to enable (why is this?)
-Have not been able to schedule an instance of any report (neither email, nor inbox, nor file, ...nothing)
Could somebody please help me with this? Is this a limitation to the Crystal Reports XI Server vs the Enterprise edition? Is there something else I am missing? I have never been able to successfully schedule a report.

Thank you for the input, but I have not yet solved my problem. Please allow me to provide some additional information which may give more hints:
I have Crystal Reports XI Server R2 installed as 5 named user license (version that comes with developer)
The following servers are enabled in CMC (which is all of them)
-Input.DomainNameSQL
-DomainNameSQL.cacheserver
-DomainNameSQL.cms
-DomainNameSQL.destinationjobserver (has all destinations enabled)
-DomainNameSQL.eventserver
-DomainNameSQL.ListofValuesJobServer (no destination tab)
-DomainNameSQL.pageserver
-DomainNameSQL.programjobserver (has all destinations enabled)
-DomainNameSQL.RAS
-DomainNameSQL.reportjobserver (has destinations tab, but there are no destination entries to enable! Object type is: CrystalEnterprise.Report and detail: IDL:omg.org/CORBA/UserException:1.0
. Details: %2.'
These are the ONLY two event IDs that appear after I schedule the report instance. No other events occur.
Are there any other logs that I can check? How do I look up what event ID 45387 and 45385 are?
Thanks!

Problems with X-FI on central spea

Similar Messages

Maybe you are looking for