Xgenconfig basic explanation - JVM 1.2.2

Hello !
I need to tune GC in Solaris 1.2 JVM, and cannot find the answer for the one basic question:
Where is explicitely Xgenconfig option described in Sun'docs ?I can find some tuning tips on iPlanet or WebLogic sites but where is some basic source of that knowledge ? I can see that Xgenconfig option is accepted by JVM 1.2.2_09 on Solaris but cannot find it anywhere in 1.2 docs.
I have seen some HotSpot tips (generaly for 1.3 and 1.4 JVMs but not 1.2) but where is some basic and first hand explantion from Sun ?
I need to know what "semiscpes" and "markcompact" algorithms are. What are general guidelines for settings ? Are there any other algorithm enties ?
sincerely Olek

You can find the information you are looking for here: http://wireless.java.sun.com/midp/articles/garbage/

Similar Messages

  • Nice basic explanation of curves vs. levels

    http://www.photographlondon.co.uk/curves.htm

    Hello Barbara I have purchased your Missing Manual and found it one of the best.. thank you
    Some people are suggesting that when using curves add-on with PE3 that it is best to use more than one curves adjustment. Making small adjustments on each curves until you reach your target. That way if you need to change later on you do not have to start completely over because you cannot edit in Elements. Also they suggest that multiple small adjustments will change fewer levels that are ok to begin with.
    Do you think this is necessary?
    Butch

  • Very basic, explanation about data fields

    Hi everyone,
    I am new here and I need to undertand the difference between static and nonstatic data fields. In my tutorial it says:
    "To help you determine wether a data field should be static or not, you can ask your self how many many times it occurs. If it occurs once per class, it is static. but if it occurs once per object, it is not static".
    can anyone explain what that means?

    [http://xahlee.org/java-a-day/instance_vs_class_members.html]

  • Basic Producer/Consumer loops for a newbie

    Labview neewbie here.
    I was looking at Producer Consumer loops.
    Can anybody give me a very basic explanation of how to set one up.
    I want to take readings from a HP 53131A counter and store them in an excel spreadsheet.
    I understand the part about labview slowing down as it opens the Excel file, and a seperate loop will help solve this.
    But I dont understad how to set up the Que function.
    Thanks.

    Multithreading will not make excell open faster but using concurrency you can have more than one operation operate ate different speeds.  The nice thing about the produce consumer model is that the if the consumer is slow or unreliable (freeses up) the producer doesnt care and will continue.  To use a queue is very simple, 1. create the queue, name it(optional) and give it a data type (ie int, array of floats ...)  in the produce loop use the enqueue vi to add items as needed to the queue, in the consumer dequeue these items (using a timeout = -1 the loop will wait for a new item and not consume resources)  the consumer can process the data acquired in the producer loop.
    Paul Falkenstein
    Coleman Technologies Inc.
    CLA, CPI, AIA-Vision
    Labview 4.0- 2013, RT, Vision, FPGA

  • EBCC confusion (basic)

    I'm a bit confused by an aspect of the EBCC.
    When I open go to open an application there is a directory structure. There
    are directories that are mirrored in both the EBCC directory and the WLPortal
    direcotry.
    For example the following directories both exist:
    ebcc4.0\applications\portal
    wlportal4.0\applications\portal
    Initially I thought that you opened the EBCC application, made changes & then
    'synchronized' it...which would copy the metadata over to the wlportal version
    of it.
    However I'm now getting weird (to me) behavior when something is saved in one
    particular location and then doesn't seem accessible from another location.
    I'm not trying to do anything very complicated...just work on a portlet that
    can exist within the StockPortal demo application.
    What is the appropriate area to change/create metadata for this portlet within
    the EBCC?
    Thanks a lot for any basic explanation of the appropriate way to deal with this.
    Any pointer to accurate docs would be cool too. I've found that most of the
    documentation isn't so clear about defining the appropriate workspace for different
    situations.
    -James

    James,
    First, sorry for any confusion. BOTH the WLP server and the EBCC ship with
    the example application data. The reason for this is that technically you
    could have either one of these products installed depending on your
    development role. You should just pick one of these application data
    directories and make all your changes to that (probably the EBCC one). When
    you run a sync from the EBCC it sends your changes up to a running server
    (never onto another file system).
    Sincerely,
    Daniel Selman
    "James" <[email protected]> wrote in message
    news:3c696dd9$[email protected]..
    >
    I'm a bit confused by an aspect of the EBCC.
    When I open go to open an application there is a directory structure.There
    are directories that are mirrored in both the EBCC directory and theWLPortal
    direcotry.
    For example the following directories both exist:
    ebcc4.0\applications\portal
    wlportal4.0\applications\portal
    Initially I thought that you opened the EBCC application, made changes &then
    'synchronized' it...which would copy the metadata over to the wlportalversion
    of it.
    However I'm now getting weird (to me) behavior when something is savedin one
    particular location and then doesn't seem accessible from anotherlocation.
    >
    I'm not trying to do anything very complicated...just work on a portletthat
    can exist within the StockPortal demo application.
    What is the appropriate area to change/create metadata for this portletwithin
    the EBCC?
    Thanks a lot for any basic explanation of the appropriate way to dealwith this.
    >
    Any pointer to accurate docs would be cool too. I've found that most ofthe
    documentation isn't so clear about defining the appropriate workspace fordifferent
    situations.
    -James

  • Basic help needed .

    Hi guys could you please explain me the meaning of shares and configuring acl (i.e.Access control list ) on shares.
    I m totally new to this environment as i just shifted from windows to solaris environment.
    Please explain the concept behind the shares and acl.
    I m using sun 7410 storage system.

    Hello,
    A basic explanation of these concepts is in the documentation on your array.
    ACLs are a windows feature, not specific to Solaris.
    http://ARRAY-IP/wiki/index.php/Shares:Shares:Access#Root_Directory_ACL
    The information on shares is at:
    http://ARRAY-IP/wiki/index.php/Shares:Shares
    -Jay

  • 16 Bit and 32 bit program

    What is the difference between a 16 bit program and a 32 bit program?
    Plus, is there a 64 bit program.
    Thanks

    It basically refers to the address space of a computer. To address a memory location the processor loads an address into a register. If the width of this register is 16 bit the computer is often called 16 bit, and the programs written for it 16 bit programs. This is the BASIC explanation. There are lots of modifications, for example the JVM. It can be seen as a software computer with a 32 bit address space. So Java programs are always 32 bit regardless of what computer they run.
    Most computers today are 32 bits, but the general tendency is towards wider address spaces so 64 bit's in the pipeline.

  • MSI K8N Diamond Plus - Guide to my first week

    OK, not a newb here, but been around the block quite a bit.   MSI K8N Diamond Plus is my 5th A64 mobo (ECS K8M800, my daily undestroyed computer, K8T800, my 12 year olds gamer, Asus A8V Deluxe, first 939 system, Abit AN8 SLI, first SLI gamer, and now the MSI Diamond Plus).   Had the KDP (K8N Diamond Plus) for more than a week now, and here's what I've learned.
    This is state of the art again, and we have no one to blame but ourselves for the pain this causes us when we upgrade like lunatics 
    And as usual, the drivers and BIOS are al Dente (i.e. not cooked enought yet, a little raw)
    MSI is also oddly silent on this system, which is wierd, as they are a large company, and specifically cater to enthusiasts.  But their BIOS guys are MIA.  Hopefully this will not be forever.  Asus, ABIT, DFI, Epox are always fast with fixes
    The board is a nice design, with everything basically accessible, as much as any other board.   Lots of purposeful components, not too many dumb frills.  No tooty fruity colors, but rather practical parts.
    The new 2 piece NForce chipset is fine, and the MSI guys gave us a decent, but funky cooler.  It gets a little warm to the touch when you pound on it with Prime95, or Quake4, but other than that it is fine
    The manual has a zillion typos, and fortunately for us in this forum, we have shared what we've learned.  The translation from Chinese to English leaves quite a bit to be desired, and hopefully, MSI will learn from Asus and Abit and get a better translation service.  In 2006 this is just plain stupid, especially with a $225 board   
    As usual, the mobo supplied tweaker utilities are just aweful.  They look like a hallucination from a Hunter S Thompson book, and they work about as well.  Core center is a sad state of affairs, and the rest of them just burrow their way into your otherwise stable system and cause it to have poor behavior.  And therefore as usual, the BIOS is the best way, if slowest, to tweak this bundle of parts
    Which brings us to the BIOS.  IMHO, the worst one I've seen on a high end board.  ZERO explanation for half the settings (this is not strange in and of itself, BIOS is still a black art, but in a tweakers board, we should have some basic explanation  )
    There seem to be adequate settings in the BIOS for all sorts of doodads and gizmos, but who the heck knows what half of them are.  Roger points out rightfully, that we now need to "Tune" across all these different intermediary bus structures and test.  But with the lack of info from either NVidia, MSI or anyone else for that matter, its kinda hard to know where to start.
    The board is clearly sensitive, which is a result of it being high strung.  This is no different than any "first out" product I've ever bought.  Most take 2 or 3 turns of the crank to get totally stable and forgiving.  This one hated my OCZ platinum EL 2Gb kit memory, and it brought out the worst in one of the SLI based EVGA 7800 GT COs.   These components worked in the Abit AN8 SLI (although not always great), but the MSI has ZERO tolerance for even the slightest pertubation from the memory.  It was BSOD city until I removed both of these components by process of elimination that took probably 100 hours
    Once I removed the bad components, and replaced the memory with Geil Ultra X 2x512 2-2-2-5, it worked great, ran Prime95 for 10 hours with no errors, and seems reasonably stable.  I've RMA-d the bad 7800GT CO back to EVGA, and will report back on how SLI behaves when I get the new one (cross shipped of course, I haveno patience )
    I also now need to replace the 2Gb RAM kit with something that the board will tolerate.  I may RMA the 2Gb kit back to OCZ and try another one, but I dunno.   I love OCZ but I have a bad feeling about this, even though they have great!!! support.  I may try OCZ PC4000 or the RAM that Roger successfully used.
    I did upgrade to the 1.16 BIOS, and found that some new things were added, as well as voltage control in Cell was a little better, but registration of changes in voltage is still a disaster.   I adjusted a bunch of times, it didn't register, and I ended up smoking a new A64 3700+ Diego with 1.95 volts, even though the BIOS claimed it was 1.53.  I had to rebot to see what was going on.   The Thermalright XP-90 kept the proc from melting down through the earth
    Finally, I hope this board attracts more people, and therefore more tweakers that can figure out all these gadgets and settings.  Everyone flocked to the Asus X16 SLI product, which is too bad, as this one needs lots o' folks to hack it up for us to figure out what is going on.
    The on board Creative audio sounds lousy to my ears, and I will replace it with an Audigy 2ZS gamer that I had in the Abit.  It just sounds better, but hopefully the drivers will not trash my newly stable system.   Creative scares me, they scare me alot.
    I've been able to get the CPU up to 2.4Ghz, with a .5 volt bump to the CPU and 2.9 volts into the Geil memory.  So far, so stable, no smoke coming out yet 
    I hope this info is somewhat valuable to someone on this board.  I will post details of all changes that I make, as others are doing, so we can at least take care of ourselves with this thing.

    Quote from: nanohead on 15-February-06, 01:17:10
    Which brings us to the BIOS.  IMHO, the worst one I've seen on a high end board.  ZERO explanation for half the settings (this is not strange in and of itself, BIOS is still a black art, but in a tweakers board, we should have some basic explanation  )
    There seem to be adequate settings in the BIOS for all sorts of doodads and gizmos, but who the heck knows what half of them are.  Roger points out rightfully, that we now need to "Tune" across all these different intermediary bus structures and test.  But with the lack of info from either NVidia, MSI or anyone else for that matter, its kinda hard to know where to start.
    first of all, i do think that all the settings in the BIOS have an explanation in the manual, even if it's a basic one. if that explanation doesn't tell you everything in detail, is because if you do need a detailed explanation of the settings, you probably shouldn't be messing around with those settings.
    Quote from: nanohead on 15-February-06, 01:17:10
    I did upgrade to the 1.16 BIOS, and found that some new things were added, as well as voltage control in Cell was a little better, but registration of changes in voltage is still a disaster.   I adjusted a bunch of times, it didn't register, and I ended up smoking a new A64 3700+ Diego with 1.95 volts, even though the BIOS claimed it was 1.53.  I had to rebot to see what was going on.   The Thermalright XP-90 kept the proc from melting down through the earth.
    wanna tell me how did you get 1.95V on that mobo?
    Quote from: nanohead on 15-February-06, 01:17:10
    I've been able to get the CPU up to 2.4Ghz, with a .5 volt bump to the CPU and 2.9 volts into the Geil memory.  So far, so stable, no smoke coming out yet 
    a 0.5V  bump? again, you must be joking. maybe 0.05V.

  • NEED HELP GETTING NEW SOFTWARE AND ITUNES

    Hello. I recently updated my iphone 4s to the most recent update. I don't know what it's called, sorry. Anyways, once I did this, my iphone was no longer recognized by itunes. It was recognized by my computer, however. Because of this I tried to download the newest itunes. It told me that I couldn't without 10.8.6 software. I did the "software update" on my computer and it did nothing. I then went onto the internet (apple) and tried to download 10.8.6. It said that I could not without 10.6. software? Anyways, I have been doing all that I can to get any sort of update but I'm not allowed to get anything since I lack 10.8.6 software. I trashed my old itunes as it was apart of the process of getting (what would be the new itunes) to recognize my phone. Now, I can't get itunes or any sort of software and I'm incredibly frustrated. I'm stuck and have no idea what to do or where to start. MY laptop is a macbook pro from 2009. (I am not tech savy and thus need basic explanations) I don't even know the software that I am currently running but please help. I am extremely frustrated as my music (which is one of the few things I use this computer for) is completely gone. HELP. Thank you so much
    -Andrew

    iot is Not 10.8.6... But... 10.6.8 = Snow Leopard.. This is not a Download...
    First Check that your Mac meets the System Requirements for SL...
    Snow Leopard Tech Specs
    http://support.apple.com/kb/SP575
    If so Contact Apple in your Country to Purchase a Snow Leopard Disc...
    http://support.apple.com/kb/HE57

  • BT Vision missold - disgraceful!

    On 24/08/11 I called BT on the recommendation of a friend who lives elsewhere in the country to ask about their TV, phone and broadband packages. We previously used a similar package from Virgin Media.  Virgin Media could not match the price of BT's package (once Sky Sports had been added), so having spoken to BT, I decided to switch and signed up to the BT Vision, BT Infinity Broadband and Unlimited Calls package with Sky Sports 1.
    I was on the phone to the BT employee for over an hour while he sorted this out and referred to it as a 'complex order'.  I couldn't see what was so complex about it, but he sounded new to the job so I remained patient as he went through the process.  At no stage during the conversation did the BT employee tell me that being able to use BT Vision was reliant on having an aerial at my house with which to receive Freeview channnels.  I told him that we were previously with Virgin but at no point did he explain the difference between cable and BT Vision as an aerial/freeview based service.  We do not have an aerial at our house.   I recall specifically asking him whether our house was likely to already have everything we need in order to use the service and that his reply was yes, and that if it didn't, the engineer who visits would install a BT line or a socket, as this was the only thing likely to pose a problem.  He told me that the engineer would install everything, show me how it works and make sure I was completely happy before he left.  I believed that everything would be fine because why would BT sell you a new service that they weren't sure you could use - right?!
    On 31/08 the hardware arrived: Vision box, Hub, remote etc.  On 02/09 I took the day off work to be home for the engineer. The engineer arrived and drilled a hole, installed a wire to move an old socket that the previous people in our house had used in another room and set up the broadband and phone line.  He said that he does not get involved with the BT Vision part though, that if I wanted help with that, I'd have to arrange for a separate engineer to come out.
    I set about installing the BT Vision myself. Following the instructions and obviously stumbling at the first because I had no aerial cable to attach to the Vision box as per the diagrams.  Without the aerial, I can watch iPlayer and some pay perview programmes/films and not a lot else - hardly value for money.  The Sky Sports card also does not seem to work, but I'm unsure as to whether this is down to the lack of aerial problem.  I spent all day yesterday fiddling with this and by the time I was finished, customer services was shut (and I was furious, so just as well I couldn't call then!).  
    I have to say that the BT Infinity part of the package is wonderful and I would like to keep this and the phone line.
    I have been quoted nearly £200 for the installation of an aerial on my roof and £45 for the addition of a socket for the wiring to enter the house in the right place.  That's an additional £250 to use BT Vision.  I hadn't bargained for this, wasn't informed of this at the point of sale and I certainly cannot afford it!  On closer inspection on the website/ help pages, BT have a preferred partner for installations of aerials - I bet they do - what a nice little earner!
    Today, 03/09, I called BT. They were very helpful and said that if the young man I spoke to when I was signing up didn't do a freeview check with me, i.e. talk about the channels we'd get and mention the aerial, then we have been missold and that this is serious, especially considering that this is one of BT's premium products.  BT are handing it on to an offline team who will listen to the call I made on 24/08 and check.  If they find that he hasn't done what he should have done, then they will cancel the Vision service, take back the box and not charge us for any of it, while keeping the BT Infinity and phone line intact. BT have said that they will contact me within 5 working days and let me know.  
    I am SURE that the salesaman did NOT make it CLEAR that I would need an aerial to access the service.  If he had mentioned the aerial, I would have gone away to check before signing up, as we have never used an aerial since we have been in this property.  The salesman made me feel that the engineer would solve any problems but when he arrived he wouldn't even touch the Vision box!  Until yesterday I didn't even understand that BT Vision is basically just Freeview with iPlayer and pay per view movies.  BT obviously need to make sure this is crystal clear in all conversations and advertising. 
    Before I knew that all this would be such a headache I cancelled my Virgin Media services and they have already been round to take back their set top box etc. - I'll also have the problems of restarting a cancelled service with them if BT manage to resolve the above!  I wish I'd never even heard of BT!
    I will let you know how it goes....

    Homework includes listening to the people who are selling the service!  We're not talking about some 'fly by the night' cowboy outfit here, and BT have a (moral) responsibility to ensure that they're not selling a service that the consumer can't access. 
    I can remember my own call when I signed up to Vision, and they asked about my reception for Freeview, so BT's own procedures were followed, and I have no complaints despite not being able to receive all 6 mux's.
    You only have to read this forum to understand that there are many questions about what Vision does and doesn't provide (HD content is a perfect example), the least you can expect from BT's own employee's is a basic explanation.
    Not everyone is this world is technically savvy and what seems obvious to you and me may not be obvious to others. It seems to me from the original post that BT's own procedures weren't followed and so the OP (who's happy to keep the BB and phone - so isn't on some sort of anti BT crusade) should be allowed to drop Vision at no charge to themselves.
    For the avoidance of doubt I have no complaints about the level of service I have had from BT
    ......but I'm not an 'expert'....yet!

  • Dwh's current take on SCP (Snap-Crackle-P

    I think that many people could solve their SCP problems mainly by looking at the problem differently. The main reason for this post is to try to help that happen. In a sense, of course, this will tend to validate my position or not, depending whether significantly more people start reporting getting rid of SCP or not. It is <i>not</i> my intent to defend my position - I think there's been plenty of that in other threads - and I intend to ignore any replies which are simply argumentati've, because experience has shown that responding makes the thread length explode, which would just bury my intended message underneath that kind of traffic. In fact, I've decided I will give all such argumentati've posts in this thread a "" rating as further encouragement to argue with me in some other thread.
    OK, you've got SCP. How do I suggest you approach it's
    First, do not assume your SCP has the same cause as everybody else's. I'm going to talk about the bus latency cause, because that's the one I think is behind the bulk of the complaints, but yours might be something else: you might be one of the unlucky people whose card is defecti've, for example (that's going to happen to some people, and it could be you).
    Second, think of your soundcard symptoms as possibly <i>revealing</i> a problem in your system, much as canaries were used in coal mines because they are more sensiti've to toxic gases and would die before it was too late for the miners to get out. This suggests that the soundcard may be telling you to look elsewhere, and I suggest that for this particular problem, that's actually a good way to go. So, for this particular problem, ask yourself what <i>other</i> devices seem to be acti've when you hear SCP. For example, if you hear SCP when you see the disk activity LED flash, that's a big clue. Pay attention to stuff like that.
    I'll get into why's later on, but for now, the kind of device most likely to be behind SCP is a relati'vely smart device geared for high performance, particularly video cards and busmastering disk controllers (especially RAID controllers), although network cards and TV cards are examples which don't seem to me to fit that mold, but sometimes seem to be behind SCP.
    I think the first thing to try is to do simple things which may evoke SCP or make it worse. I suggest rapidly scrolling a large window up and down while playing audio is a good basic test for the video card. Similarly, copying a large file (or better, running a disk benchmark) while playing audio is a good basic test for disk controllers.
    The next thing to try is to temporarily change settings which affect driver behavior. Examples are lowering the video acceleration and disk read ahead settings. These are things easily changed and changed back. If they stop SCP, this casts strong suspicion toward the device associated with them.
    Progressing to steps which require some more effort, I am convinced these problems are fundamentally due to some design weaknesses in the PCI and PCIe buses themselves. However, there's really nothing that you can do about that. The only available true fix is having drivers for vulnerable devices take steps which avoid the situation which sets off the problem. So, this means it's a good idea to make sure all your drivers are current, including the drivers for any devices which are integrated into your motherboard. Then, if that doesn't help, see if you can find some non-current drivers to try for those devices which were already current, and try those. Sometimes you can revert to generic drivers which are built into the operating system. For example, if you remove your video card drivers, this will happen. The idea is to try a completely different driver to see if it affects the symptoms. I don't suggest running anything other than the current drivers supplied by the device manufacturer as a real solution, but it can be a very effecti've diagnostic tactic, and it can be useful information when trying to get the official driver fixed (i.e. if you can tell your video card maker that your soundcard noises stopped when you removed their video card driver...). Falling back to generic drivers may mean advanced hardware features won't be used, so if you're only experiencing SCP when there is high-intensity game action on your two-card SLI graphics rig, it may not be diagnostic; but if you get SCP when playing WMV-HD video files, it could well be enlightening.
    If you're not focused on a specific non-soundcard device at this point, my next suggestion is to rule out as much as possible. This probably means opening the computer's case and removing any hardware that is not essential for your testing. You won't be able to remove integrated devices, so for those this means disabling them in the BIOS. (If you have more than one disk controller, you might be able to temporarily rearrange your system to only use one of them at a time for your tests.) Of course, you can take a slower approach like trying disabling devices in Device Manager first, but ultimately this step is to help rule out things you're not suspecting, and there's nothing like removal to make sure something isn't influencing your symptoms. If this approach proves fruitful, putting things back together piece by piece until the problems recur should cast suspicion on the last device you put back or enabled. Unfortunately, simplifying your system can make SCP go away simply by slightly improving bus latency performance without actually fixing it. So, this isolation process can only suggest which device is really behind your system's bus latency problems, and which driver you really need fixed (or device with bad drivers you might consider replacing).
    If you still get SCP with your system stripped down with only essential devices left, you will at least have a smaller number of prime suspects, unless you are in a position to try substituting other devices. That's often not really practical, but if you own a computer store, or have very generous and helpful friends, it may be an option.
    Ultimately, if you can figure out which device to focus on, and can find drivers for it that address the bus retry problem, you should be able to make just that one substitution, and really solve bus-latency-caused SCP, not just keep it at bay.
    In some cases it may be useful to record the SCP via What-U-Hear and/or Wave, at the right sample rates, and look at it in a suitable wav editor. This can give clues as to whether the SCP is due to bus latency or something else. Within reason, I'm quite willing to try to help out in individual cases in this thread if you're trying to follow my advice. Feel free to ask questions, etc.
    Now, to explain where I'm coming from a little.
    There's a bottom line here. If you're talking about bus latency, which is how long a device has to wait to get the bus after making a request for it, in terms of 00's of microseconds (more than 3,000 bus-cycle times), or more, for something that operates at the speed of the PCI bus, that's all you need to know that something is seriously out of whack. It's also all you need to know to rule out the device that is waiting as being the cause of the delay. The point here is that we're not talking about sub-optimal bus latency, nor even poor bus latency, but "insanely awful" bus latency.
    Any analogy is going to be a stretch here, but imagine a traffic signal in a city that does not permit a right turn on a red light. We can consider the latency a car experiences to be the time from when it arri'ves at the intersection controlled by the light to when that car gets a green light. Now, considering the normal speed of cars, etc., suppose I start talking to you about timing the light for a two-hour cycle, i.e. about one hour green, a few seconds of yellow, and about one hour red. That would be more than completely nuts, right? Well, the kinds of bus latency CL has measured is that kind of nuts. It really is.
    (While I understand the arguments that if CL makes a sound card at all they should go to whatever lengths to make sure it works irregardless, there must be some point where those arguments just get unfair if the infrastructure upon which CL relies, but does not control, is sufficiently insane. That's why I personally can't bring myself to blame CL, and instead look to the design of the infrastructure first, and whatever is able to avoid causing the "insanely awful" bus latency second.)
    While bus latency as high as has been reported is sufficient to explain a reasonably-designed soundcard producing the kinds of symptoms that are being observed, and that the device experiencing that kind of bus latency isn't that cause of it, it's not enough information to determine the cause. I've said there are really only two plausible things that can explain it. Either the controls to limit the length of an individual bus transaction (after the bus has been requested) fail to do so under some conditions, or after a master requests the bus, others are being given multiple turns before the bus is finally granted (i.e. you ask for the bus, but your "turn" keeps getting skipped). (The only other possibilities are either essentially even more insane bus behavior, unless your position is that CL's engineers and others are so dumb they can't use equipment like bus analyzers to measure the latency their device is exposed to, or that they are just plain lying.)
    Initially my instincts had me leaning toward the first of the two cases: something wrong with the transaction latency controls. Currently, it looks like it's really the second case: one device is getting more than one transaction when others are waiting. This is after I've been able to look at the PCI specs. (Because my access is through a pcisig.org member company, I don't feel comfortable quoting from the specs., nor saying more than a minimum about their contents that is relevant.)
    "Bus retry" is when a transfer is stopped by the addressed device before any data transfer has occurred. It carries a special implication that the same transaction is to be retried. It seems to be designed as a way for a slow device to delay things (a little) until it can get ready.
    The failure mode I have seen described is that the host bridge (essentially the processor connection to the bus), addresses a device and then does bus retry transactions for an insanely long time. The device has some kind of small queue of things to do, which has become full, and the device signals bus retry until the full condition ends. The host bridge seems to dedicate itself to this one task, so this may block other processor I/O operations. Since the bus retry transactions do finish, albeit early, it would seem that other bus masters, like the CL soundcards at issue, should be able get the bus while this is going on, but that doesn't seem to happen. In looking over the PCI 3.0 spec, I only find 2 things which seem relevant.
    There is a 0 microsecond limit on bus retry looping of a specific kind, but there is no hardware enforcement; the spec explicitly permits proper avoidance to be implemented in device drivers. If this is overlooked, failure lurks for spec-conformant hardware, and I think it's easy to overlook this.
    Secondly, there are ways some masters can get an exclusi've lock of the bus, and some situations where the lock semantics can result in data overruns for video/audio/communications devices, to the extent that the 3.0 spec discourages the use of the LOCK# signal and hopes to remove completely it in the future.
    I also tend to think that having 2 basic causes for such grotesque, long-standing problems is pretty unlikely, though not impossible. So far I don't see a need to speculate to the contrary, which is to say I am inclined to apply Occam's razor to this, so long as the symptoms and hard evidence seem to be covered by one basic explanation.
    My current take on all this is that it's likely been standard practice for host bridges to control bus deadlocks and operation sequencing problems by some combination of bus locking and transaction ordering, with the net effect that the bus gets dedicated to bus retry loops when they occur. It's likely that these practices have been carried to the PCIe bus (because they control potentially serious problems). In PCIe-bus machines, the PCI bus hangs off the PCIe bus by means of a PCIe/PCI bridge. That means that if there is a locked bus-retry pathology on the PCIe bus, I'd expect PCI devices to see the PCI bus appear to go idle for the duration even though there are requests for the PCI bus. That seems to me to be consistent with the CL NF4 statement that it was "...the first motherboard on which these extremely long PCI service holdoffs have been observed by Creative, where another PCI device in the system was not causing the holdoff."
    This suggests that chipsets might be able to do something about this. If the host bridge released the lock on the bus, at least when ending a "bus retry" transaction, it seems this would help busmastering soundcards, like the X-Fi, by letting them break in during a bus-retry loop. That should eliminate the huge bus latency measurements. However, the bridge would have to be doing something pretty complex to let other driver tasks past an unlocked bus-retry loop, so I think this could still be a big bottleneck. For this not to be a problem area, I think extended bus-retry loops have to be prevented.
    Right now, extended bus-retry loops can be prevented by driver-avoidance, which IMO is a workaround, not a true solution. If you can hunt down and deal with the culprit drivers, however, at least it does fix things; it's just that that can be darn hard to accomplish. From a bus protocol standpoint, this kind of thing needs an enforced limit. A device which simply has slow circuitry doesn't need very many retry cycles, and that's what this is useful for. A device which (ab)uses it because its work queue is full leads to these problems, because the right thing to happen is do other things with the bus until the device work queue has room. In other words, this isn't a "wait for me" situation, it's a "come back later" one. Exceeding some generous "wait for me" limit should have been a reject reflected back to the driver. There is more than one reasonable way to do something like that, so I'm not going suggest how the PCI bus might have been different to help with that; the small hard limit is sufficient: the driver can look at a status bit, and request an interrupt from the device when the bit clears, as the PCI bus stands now.
    -Dave
    [email protected]

    . Perhaps NVidia simply makes their 6x PCIe slots ultra high priority so their video cards can squeeze out every last frame per second in SLI mode as possible, without regard to being "nice" to other add-in cards by allowing them proper bus time?
    While that's certainly not something I can rule out, I think it's much more likely the bus-retry pathology has simply spread to PCIe, having not been dealt with in PCI. But, you say, PCIe is based on serial point-to-point technology and can be doing more than one thing at at time. It's also based on the PCI programming model and I think it likely there are bottleneck points around the setting up of transfers. What that means is that the arbiter does one grant at a time, but can continue onto others unless they would conflict or it runs out of some needed resource, so when that process is locked by the PCIe Host Bridge while it tries to start up a transfer to a device that keeps responding to each attempt with bus retry, it's entirely possible the same thing happens as for the PCI bus, even though normally the PCIe bus <i>can indeed</i> do some numbers of multiple transfers in parallel.
    2. Perhaps PCIe won't have this problem, once motherboards are 00% PCIe without any old PCI slots? I think this may happen, because PCIe is based on serial point-to-point technology as opposed to the older PCI based on parallel shared-bus technology.
    If there was a Soundblaster X-Fi card with PCIe for connectivity (even though it doesn't need the bandwidth), then perhaps it wouldn't have any of these ongoing problems any more at all.
    Hopefully, some day very soon, Creative Labs will make a sound card for PCIe. There sure is a high demand for it now, which I'm sure will only increase -- especially when PCI gets phased out completely just like ISA was a few years ago!
    My current take is that this problem really appears to have spread to PCIe. Furthermore, CL has stated that PCIe has tested to be <i>even worse</i> than PCI for audio. It's better for moving more data faster, but seems to be even worse at moving small amounts of data promptly. (This is what can happen if only throughput is your God.) I'm very inclined to believe the reason for this is really that the bus-retry pathology gets worse as the bus gets faster, and I take it as some of the evidence for the problem having spread to PCIe.
    -Dave
    [email protected]

  • G4 Flat Panel power problem

    Hi
    We recently had a power cut and since then I have been unable to start up our imac flat panel.  We have tried the fuse, plugged it in somewhere else and checked all the leads etc, but hold the power button on and nothing.  I changed the PRAM batery about 3-4 years ago and have not had this problem before this occasion.  Does anyone know if there is an internal fuse or a reset button etc

    The reset often tried after a power outage or other interrupt, requires one to follow instructions in the maintenance support article regarding a reset of the Power Management Unit (PMU) as follows.
    •Resetting the iMac (flat panel G4) Power Management Unit (PMU)
    http://support.apple.com/kb/HT1712
    This article has a few helpful images of the computer and basic explanations on how to do the procedure.
    Other more in-depth items may require more take-apart know-how and techniques which will be more tedious and would follow instructions such as those outlined in an official iMac G4 Apple repair manual in PDF. These may be hard to get. While I have three iMac G4 17" 1.25GHz desktop computers, none of them are up and running at this time; my original one has a power issue and I believe it may be a failed power supply. Of the other two, one was acquired as non-running parts computer, but it has a good power supply, optical drive, display, and a few other parts. The third iMac in my instance, needs a replacement optical drive; so while I have three of these, all of them would require disassembly to remedy their various issues.
    When you take apart one of these, be sure to have some new Thermal Paste, a new/fresh clock Battery, a means of re-torquing the internal chassis to required specification, and remember to remove all the old thermal paste from the heat transfer conduits before re-assembly. If you can get the correct Service Manual for this iMac G4 (several in series) which was an official Apple document, in PDF, it would be of great help in troubleshooting the issues. Some of the suggested repair procedures require access to known-good parts; in part to swap out and help find out what is not wrong with it.
    Online sources of information vary, as do their worthiness and value as problem solving tools, depending on depth of the troubles involved. Even a site with info such as this iFixit may offer tips for some situations: http://www.ifixit.com/Device/iMac_G4 -- And the xlr8yourmac article on how to Take-apart iMac G4 for Drive and Ram upgrades has a few others: http://www.xlr8yourmac.com/systems/imac_g4/imacg4_takeapart.html
    There are test ports or holes under the first bottom plate cover on the iMac G4 where one could use a multimeter and small tipped probes to check for correct voltage outputs from the computer power supply. There is a chance one of the power supply transformer voltage outputs may have failed.
    Sometimes, a power failure may coincide with other parts failures; in example, a hard disk drive on its last legs may be affected by a power surge or outage timed upset, and that contains startup disk OS files.
    To find a qualified and trained technician who can and will help repair these older models, can be a problem in and of itself; several shops also sell new hardware and their answer for an old unique computer, is to get a new not-so unique model from them. With the correct Service Manuals, you could eventually repair one of these, if you can get good quality replacement parts at low cost and do the work yourself.
    Hopefully this helps somewhat.
    Good luck & happy computing!
    {edited to add info + url}

  • I have a dvr and I want to monitor from my phone.  this worked when I had a Belkin router that let me open ports.  I use "canyouseeme" and it can't see 80, 9000 or 1025. How do I make them available?

    I have a Lorex DVR that I want to monitor from my IPhone and IPad.  I used to be able to do this when I had a Belkin router (easy to open ports) but I bought the AirPort Extreme router and no longer have that capability.  When I use "canyouseeme" they can NOT see 80, 9000 or 1025.  Lorex says I need them all available in order to access.  Help!  And all the help I see refers to a earlier version of the AirPort Utility so I cant use those to look at anything, I cant find the same screens, I have version 6.1 (610.31).  I also don't really understand how ports work, so I need a pretty basic explanation.

    Well...I went to the modem (Westell, WireSpeed), found the NAT settings, once again, I'm WAY over my head, I am assuming this is a TCP connection (as opposed to a UDP) and per Lorex my mobile devices will use port 1025.  So I gave it a "global port range" of 1-10 and I indicated that the "base host port" was 80, 1025, & 9000 (ports 1,2,3).  When I selected the 'enable' it asked for a "host devise" my choices are my IPhone, IMac and the IP address for the dvr, so I choose the dvr.  I still cannot connect and canyouseeme still can NOT find these open ports.  This is taking up my whole day! I don't know how people figure this stuff out.

  • I bougth the sf2 program change for garagaband, but what is it exactly and how do I make it work?

    I couldn't find out what exactly the sf2 program change is, but it seemed nice, so I bought it, hoping that it would explain itself when installed. It hasn't. I did hope that it would give me some more midi instruments, and it seems like it should, but how to get them into garaband (10.0.2)?
    This thread seems to explain it: How to do use Soundfonts (.sf2 files) in GarageBand 10?
    It says I can add "audio unit plugins" to a track. Now I don't know what an audio unit plugin is, but I assume that it is a confusing word for a sound, and that it refers specifically to the sf2 sounds. I got as far as the smart control inspector but then "Click an empty part of the Audio Units area, choose Audio Units, then choose a plug-in from the submenu." What is the audion units area? I have clicked the empty part of whatever I could find here, but there is no submenu anywhere.
    Is there anybody out there who could give a really basic explanation of what it is that I have purchased and how I can make it work? I would really apreciate it.
    Ahston

    I got a bit further. I found the submenu and I am able to load a default instrument. But I cannot change that instrument to any other.

  • What is a PDF Portfolio? | Learn Acrobat X | Adobe TV

    This video explains how to create a PDF Portfolio in Acrobat X Pro.
    http://adobe.ly/yLb9tW

    This video has the title "What is a PDF portfolio?", but instead of starting with a brief explanation of what is a PDF portfolio, it goes right into describing actions which I assume go to making such a portfolio.
    This problem of skipping initial basic explanations permeates the computer world.  People who makes these videos jump over the explanations that people who want to learn don't know.

Maybe you are looking for