BIOS SUPPORT FOR NEW CPUS!!!!

hello
new post , i just got this board (6547 v1.0) board with a celeron 1.7 (clocked at 125mhz ) 2.14ghz and is total stable.
v1.8 bios support up to a 1.8 cel, are they going to make a update to support a 2hz cel, OR have they droped support for it.
and where can you get beta bios for this and other board (msi-development site).... ?( ;(
MAKE A VOTE (HOW OLD IS YOU BOARD AND HAVE THEY DROPED SUPPORT FOR NEW CPU,S FOR YOU BOARD-POST?

assuming its a 645 ultra by the bios numberlink

Similar Messages

Support for new Nvidia Quadro gpu?

When support for new Nvidia Quadro gpu? For example Nvida Quadro K2200 and K4200
Thk

What do you mean when you say "support"? All of After Effects OpenGL features already work on those cards.
The only thing that isn't supported on those cards is GPU acceleration of the ray-traced 3D renderer, which is an obsolete and almost entirely irrelevant feature. No more GPUs will ever be added to the list of cards supported for that feature.
Details:
GPU (CUDA, OpenGL) features in After Effects

How to add support for new file type.

Using the ESDK, I would like to add support for new file type ( a new extension). this new extension will function like any other non visual code editor but will have specific syntax highlighting, code folding and explorer.
I am trying ot figure out if I need to create a new editor or use existing JDeveloper code editor and add support for new file type. Does anyone have a high level outline on how to do this using the ESDK that is specifically targeted at adding new file type support for a text based code editor?
I have looked at the Samples and keep going in multipe directions. It would be cool if there was an example that was how add syntax higlighting for new file type.
Thank you

Brian, thank you. I looked at this extension and it answered a lot of questions for me. I was going in the right direction but needed a little help and bost of confidence, this is just what I needed. I created the LanguageSupport, LanguageModel, Addin, Node and TextDocument that are specific to the new file type. I was getting hung up on how to hook this into the JDevelpoer editor. I keep thinking I have to create a custom editor but it looks like I don't have to and it looks like I can associate this file support with the editor framwork, for version 10.1.3.2, with the following in the Addin Initilize() method.
Recognizer.mapExtensionToClass(MY_EXTENSION, MyNode.class);
CodeEditor.registerNodeType(MyNode.class, MY_EXTENSION);
LanguageModule.registerModuleForFileType(new MyLanguageModule(), MY_EXTENSION);
I have done this but still not able to recognize the new file type.
At this point, I just want to be able to recognize the new file and display it's associated icon or display a messare to the message log. I put a System.out.println("test") in the Initilize() method of my addin. then I registered MyAddin in the extension.xml. JDeveloper sees this new extension and it is loaded but I have not been able to show the test message or display the new icon when I open the new file type.
extension.xml
<?xml version="1.0" encoding="windows-1252" ?>
<extension xmlns="http://jcp.org/jsr/198/extension-manifest"
           id="teisaacs.jdev.myext.MyAddin" version="1.0.0" esdk-version="1.0"
           rsbundle-class="teisaacs.jdev.myext.resources.MyResBundle">
    <name rskey="EXTENSION_NAME">My Code Editor</name>
    <owner rskey="EXTENSION_OWNER">Me</owner>
    <dependencies>
        <import version="10.1.3">oracle.jdeveloper</import>
    </dependencies>
    <hooks>
        <jdeveloper-hook>
            <addins>
                <addin>teisaacs.jdev.myext.MyEditorAddin</addin>
            </addins>
        </jdeveloper-hook>
        <feature-hook>
            <description>My Code Editor</description>
            <optional>true</optional>
        </feature-hook>
        <document-hook>
            <documents>
                <by-suffix document-class="teisaacs.jdev.myext.model.MySourceDocument">
                    <suffix>my</suffix>
                    <suffix>MY</suffix>
                </by-suffix>
            </documents>
        </document-hook>
        <editor-hook>
            <editors>
                <editor editor-class="teisaacs.jdev.myext.editor.MyEditor">
                    <name rskey="EXTENSION_NAME">My Editor</name>
                </editor>
                <mappings>
                    <mapping document-class='teisaacs.jdev.myext.model.MySourceDocument">
                        <open-with editor-class="teisaacs.jdev.myrext.editor.MyEditor"
                                   preferred="true"/>
                        <open-with editor-class="javax.ide.editor.CodeEditor"/>
                    </mapping>
                </mappings>
            </editors>
        </editor-hook>
    </hooks>
</extension>
public class MyAddin implements Addin {
    public static final String MY_EXTENSION = "my";
    public void initialize() {
        System.out.println("MyEditor Constructor");
        new MyLanguageModule();
        Recognizer.mapExtensionToClass(MY_EXTENSION, MyNode.class);
        CodeEditor.registerNodeType(MyNode.class, MY_EXTENSION);
        LanguageModule.registerModuleForFileType(new MyLanguageModule(), MY_EXTENSION);
}I have added and removed the editor hook along with many other modificaitons to the extension.xml but still not recognizing the new file extension.
Todd

BIOS support for CPU upgrade

Hello...we have a ca. 5 year-old dv6-1253cl notebook that I've upgraded to 8GB memory, new SDD, new USB 3.0 card...what I'd like to do next is replace stock Intel P7550 processor with either the Intel T9xxx or an Intel P9xxx series. From the service manual, the system board/chipset will support up to the T9900 @ TDP = 35W, and up to the P8800 @ TDP = 25W. My question is: can I go beyond the P8xxx to P9xxx (e.g., P9700) even though that series isn't specifically called out in manual? Others have successfully swapped out P7xxx for T9xxx CPUs on this particular model, but I'm inclined to maintain close to the stock TDP specs, and keep to P-series. Is this possible? Thanks in advance for any advice given.
This question was solved.
View Solution.

the_hamster wrote:
Hello...we have a ca. 5 year-old dv6-1253cl notebook that I've upgraded to 8GB memory, new SDD, new USB 3.0 card...what I'd like to do next is replace stock Intel P7550 processor with either the Intel T9xxx or an Intel P9xxx series. From the service manual, the system board/chipset will support up to the T9900 @ TDP = 35W, and up to the P8800 @ TDP = 25W. My question is: can I go beyond the P8xxx to P9xxx (e.g., P9700) even though that series isn't specifically called out in manual? Others have successfully swapped out P7xxx for T9xxx CPUs on this particular model, but I'm inclined to maintain close to the stock TDP specs, and keep to P-series. Is this possible? Thanks in advance for any advice given.
I think I have the same family line as yours and I did upgrade it to a T9900 and it works great. I think I got like 4gig in it right now and formatted it to Windows 7x64 Ultra Sp1.
I am a Volunteer to help others on here-not a HP employee.
Replies aren't online 24/7 because of Time Zone differences.
Remember in this Day and Age of Computing the Internet is Knowledge at your fingertips if you choose understand it. -2015-

Why no firewire support for new iPods?

If firewire is so much better and faster why did the geniuses at Apple decide to discontinue support for it? It took me over 30 minutes to upload music & videos to my new iPod w/ USB, which would have taken 5-10 minutes with Firewire. I don't get it!

They did it because they obviously didn't see the need for it.
Either you have a usb 1.1 port, or have about 500mb of music. The speeds aren't that different between USB2.0 and FW. In fact, i think USB is faster. Stop complaining here, this is only a user-user support forum.

Is it possible to add support for new database type in Data Modeler?

Hi,
I see that Data Modeler v.4 supports different versions of Oracle, DB2 and MS SQL. Is it possible to add support for a new database family,
PostgreSQL for example? I hoped that RDBMS Site editor can do it, but so far I don't see any possibility to add XML files with metadata for a new RDBMS.
I did it previously for PowerDesigner were it is possible to add and modify definitions for new relational databases.
Thank you,
Sergei

There is discussion option as an out of the box feature. Check this: BI launch pad 4.0: Participate in a discussion about a document

CS5.1 support for new DSLR cameras (D600)

I would like to understand the business decission (if there is any) why Adobe decided that for new DSLR cameras support they will update only the Camera Raw version for the current release CS6 and not respecting the legacy for the n-1 release (updating the Camera raw for CS5.1). This is a serious concern and disapointment. Does it means that each time Adrobe has a new release , if i chnage the DLSR i am FORCED to upgrade and pay 190$ eventhus I do not need the new release features?

Ah, thanks guys - I am very very happy to eat crow on that one!
The actual point of my post was to make me feel better, and boy did it work! I did not expect any actual relief, so actually now the post is twice is good as I thought - I was actually wrong!
Anyway, I might mention (I didn't get into all the details) that I actually canceled the order for the d800e (the "e" version was backordered until just recently), as the d600 was just announced as my order was about to process.
So actually I am in the same bad situation as the previous poster, but maybe now I will go back to the d800 - saving a $450 upgrade to CS6 actually saves half the difference in price between the cameras.
And sorry for the rant on the 2 analogies. It was not a troll. I vaguely remember in my research that Lightbox comes with ACR, is that true? Lightbox doesn't come with CS5.5 MC, but I wonder if i were to buy it ($99??) that'll give me the latest ACR that supports the d600, and problem solved. I assume once i have the latest ACR it'll let me open straight into PS and not make me go through Lightbox and then PS?
Anyway, if that is correct, that would be a much better answer to the original poster (and it saves him $100). Other good answers (if this Lightbox hack won't work), might be:
"It's an incredible amount of work to support nearly every camera and lens ever made in ACR, so even though it comes free with your software, you don't get free updates once your software moves to a new version."
or
"The d600 began shipping nearly immediately upon announcement, and it takes a while to update the software." (perhaps the responder didn't realize it, but this was the situation with the d600.)
But the car-story and "if you can afford a new camera, you can afford to pay adobe" were pretty tragic answers - someone needed to call you on it, or you would have only served to upset the original poster.
Ha, PEBKAC, that is pretty good. Not very easy to pronounce, though.
I must say my last dozen interactions with adobe have all been negative, except this one, so maybe things are turning a new leaf. You're lucky I didn't get into the story of when my HD crashed, and I had to call Adobe to re-activate my old CS4 PS. It's awesome getting literally laughed at by the activation help desk person. (I had owned the software for 3 years at that point, and had only ever activated it once.) ...who just assumed I was lying. "here now let me tell you how to deactivate the old version" "the HD is dead, it ain't going to happen" "well let me show you again, because you need to do that..."
Oops, I did get into that story, didn't I?
Best,
Inline

Camera Raw support for new Nikon D810

Hi, could you please advise when we can expect to see camera raw support for the new nikon D810.
Thanks

Adriana – I installed the download from the link in the 7/27 post and was able to convert my NEF files to DNG format from my new D810 camera, but could not view/edit the NEF-smalls. When I saw your latest post I used your link to go to that download and noticed that in the description it mentioned that the issues with the D810 NEF-small have been resolved. I deleted/emptied trash of the 7/27 download and re-installed the one mentioned from your link – although they were both identical in file size and version: 8.6 – hmm? I tried the converter – but nothing new was converted (I presume because all had already been converted before?). However, CS6 is still not able to open/edit neither the NEF-small file formats, nor the DNG created from it. I am thinking maybe I am missing a step, because when I select properties for Camera Raw in CS6, the version is 8.5.0.236 – is that ok (my CS6 version is 13.0.6 – and no other updates appear available)? I only downloaded the DNGConverter_8_6.dmg; installed the .pkg – did I forget a step? Thanks for your help!

How to extend interMedia to support for new Image Format

Does anyone here has experience to extend interMedia to provide support for a new image format.
I have read the related chapter in Oracle Intermedia User Guide, I'm not very clear about it. Hope a step-by-step tutorial for this topic is available.
Thanks in advance for any idea

Can you send the details of your application to [email protected] and explain the reasons extensibility is needed by your application?
At this time, the only way to extend formats is to write your own procedures (ususally java stored procedures) to populate the image object... This does not extend the image processesing functionality to the new image format. Internally, this requires a translation to and from an intermediate format.
Larry

DNG Converter support for New Camera

What is the approximate usual time from the release date of a new camera
(specifically the Sony DSC RX100) and support for the camera by ACR or
DNG Converter ?

ACR and the Adobe DNG Converter are updated in an orderly fashion from three to four times a year. So you'll see a new version every three to four months.
The release of any new camera model has no bearing on this.

Needed Raw-Support for new Samsung SLRs like NX1000

Hopefully Apple is updating his support for these new cameras (they are still a few month on the market).

You better tell Apple directly: Apple - Aperture - Feedback
Here Apple probably will not hear you.

No RAW support for new Nikon P7000

Just received the new, compact, "pro-sumer" Nikon P7000 camera today. It's a beauty. High-end, finessed pictures in those situations where you don't want to lug a DSLR around. It's going head-to-head with the legendary Canon G11/G12.
One major "gotcha'" that I didn't know about until I started using the camera, is that the Nikon P7000 uses a proprietary RAW format. It's predecessor, the p6000, did too. However, while Aperture supports the older p6000 NRW "raw" format, it does NOT currently support the enhanced NRW+ format used by the p7000. f#$% !!!
This is truly annoying!! There is no reason that I can think of for the p7000 not to use the NEF raw format used by most other (Nikon) cameras. Thanks, Nikon!! /sarcasm
So this means that currently, RAW photos from the Nikon P7000 cannot be imported into Aperture. You have to set the camera to create "Fine" JPEG photos; which, granted, are pretty good. However, to get the advantage of RAW photos, you have to use the "ViewNX2" editing software that came with the camera. Blah!
Hopefully, Apple will step up, and the Raw Camera Support for Aperture will soon include the NRW+ format. Or even better yet, hopefully Nikon will see the error of their ways an migrate their Powershot cameras to the "standard" raw format, NEF, in an upcoming firmware release.
j0hnw
P.S. For info about the Nikon P7000, see: http://imaging.nikon.com/products/imaging/lineup/digitalcamera/coolpix/performan ce/p7000/index.htm

SierraDragon wrote:
Yes, it is a problem. Apple loses lots of market share through slow response time in supporting new cameras. Adobe is usually faster, so a workaround may be to use Adobe's DNG Converter to convert the Nikon P7000 NRW files to DNGs that Aperture can digest.
Thanks for the pointer to the free Adobe DNG Converter. Even though it doesn't yet support the P7000, you're right in that Adobe may beat Apple to the punch. Plus, I just like the idea of the DNG format. The Converter looks like a handy tool to have in the tool chest. I've got my fingers crossed that it's AppleScriptable
The P7000 does look like the pocket camera many of us have been whining to Nikon about for years. I lacks swivel display but the huge size of the LCD makes up for it. I want one!
Despite my whining about RAW support, my initial impression after one day of shooting is that it's as great a camera as it looks on paper. Lots of control over the shot. Good, solid feel. Can get great shots in adverse (eg. low light) conditions. The only major annoyance I've noticed is slow RAW write times (several seconds using Class 6 card). I've heard some grumbling about AutoFocus issues, but I having had any problems with it yet. The swivel monitor isn't a big deal -- for me anyway -- because the 3" display is easy to see at any angle. Plus, I wanted rugged, and would worry about the swivel joint becoming a weak spot. BTW, you'll need some big pockets to call it a "pocket camera"; it dwarfs my Canon S90 (which I consider my pocket camera)
Thanks again,
j0hnw

Ssd NCQ support for new iMac

Will there ever be firmware with NCQ support for 256 ssd shipped with new iMacs? My ssd ("TS" marked, most likely Toshiba) does not have one, and that's a bit outdated don't you think.

Kappy wrote:
Although with a separate SSD and HDD you have to perform the work yourself you do gain some flexibility in your set up. However, should the urge arise there are numerous tutorial around that explain how to turn the SSD and HDD into a Fusion Drive using the same mechanism that Apple uses.
And the converse is also possible and easy: you can turn the fusion drive back into two separate drives.
If possible, I think you should put up the extra $250 for the Fusion Drive - especially considering this is not an option later on. With such a new machine, the internal hard drive will be the slowest part.
Still, even with a Fusion Drive, an external is strongly recommended. You should install FCP X in your regular system drive (fusion or not), and have your projects and events in an external.
Your proposed solution is adequate, depending only on available space. You only need your working projects and events to fit in the ssd. As long as you move them elsewhere when finished, to make room for the new ones, you'll be more than fine even with a smallish usb3 ssd.

BIOS support for DTR Cpu's

Just wondering if anyone knew if MSI was working on better support for DTR and mobile Cpu's with it's next bios revision?
It's neat that I can get my CPU to run 1.5v and 10x multi through clockgen, but It'd be really nice if I could just set it and forget it in bios...

I realy hope so, as i can only run it at proper mutlipliers with 1 memory stick in slot 1, not sure if this is because of the corsair memory, or the boards support for dtr's (i think it is the later).

When will new Lightroom update be available with support for new cameras

Just purchased a fugi XT1. Any idea when new Lightroom update will be available for support for the raw RAF files?
Thanks,
Matthew Kraus

dj_paige wrote:
Right here, on the front page of this very forum, Adobe provides the answer
Well, not really - that FAQ doesn't explains policy on pre-announcing support, which is what's actually being asked about.
This gets closer, but even this is unspecific as to the policy...
Matthew, the short answer is: nobody who knows is allowed to say.

BIOS SUPPORT FOR NEW CPUS!!!!

Similar Messages

Maybe you are looking for