Abandoned Support for X40 ?

Lenovo/Thinkvantage updates for Windows 7 have begun to exclude support for X40. Has Lenovo abandoned support for X40 ? My X40/2372 with SSD runs just fine under Windows 7. I trusted Lenovo's "cost of ownership" promise. It seems Lenovo has abandoned support for X40s running Windows 7. Is this so? If Lenovo has not abandoned support for X40s under Windows 7, which version of System Update and Access Connections supports X40 under Windows 7?
Solved!
Go to Solution.

Welcome to the forum!
As per MS's own guidelines, X40 is not deemed powerful enough to run Vista or W7, due to its outdated graphics chipset.
All of these machines are over five years old now and expecting support for an OS that is two releases behind the newest one that they were originally shipped with is rather optimistic - I know of no laptop manufacturer that provides that kind of support.
All of that said, trial and error is the only way to go, and find out what works and what doesn't. I do it with my older ThinkPads all the time.
Good luck.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

Similar Messages

  • Add support for SCXI-1600 in 64-bit Windows

    Hello,
    I recently discovered that the SCXI-1600 is not supported in 64-bit Windows.  From what NI has told me, it is possible for the hardware to be supported, but NI has chosen not to create a device driver for it.
    I'm a bit perplexed by this position, since I have become accustomed to my NI hardware just working.  It's not like NI to just abandon support for a piece of hardware like this -- especially one that is still for sale on their website.
    Please vote if you have an SCXI-1600 and might want to use it in a 64-bit OS at some time in the future.
    Thanks,
    Doug
     

    Hi All. Just reading about the lack of support for the
    SCXI-1600 and Windows 7 (64bit) It sounds like I am in the same boat as the
    rest of you. I have 4 SCXI systems and IT head office is rolling out Windows 7
    (64) across the board. (Worldwide). so now I have the choice of either
    purchasing 4 new systems ($160K USD), Trying to just get the Windows 7 (32)
    operating system (if possible) or start buying new hardware. Then I need to
    justify why I am spending this money. Like you all, it has been just so easy to
    use the NI stuff but when you are forced to upgrade and there is no support for
    one party it does make our job so much harder. Yes I would like 64bit support
    for the SCXI-1600 module.

  • Photos does not support external editing like iPhoto. Is there likely to be an upgrade to change this or will I abandon Photos for software that does support editing in Photoshop?

    Photos does not support external editing like iPhoto. Is there likely to be an upgrade to change this or will I abandon Photos for software that does support editing in Photoshop?

    iPhoto does work and there is an upgrade:
    Go to the App Store and check out the Purchases List. If iPhoto is there then it will be v9.6.1
    If it is there, then drag your existing iPhoto app (not the library, just the app) to the trash
    Install the App from the App Store.
    Sometimes iPhoto is not visible on the Purchases List. it may be hidden. See this article for details on how to unhide it.
    http://support.apple.com/kb/HT4928
    One question often asked: Will I lose my Photos if I reinstall?
    iPhoto the application and the iPhoto Library are two different parts of the iPhoto programme. So, reinstalling the app should not affect the Library. BUT you should always have a back up before doing this kind of work. Always.

  • HT201178 With the coming of OSX Mountain Lion, will there be support for a late 2006 iMac  (currently running OSX Lion

    With the coming of OSX Mountain Lion, will apple be supporting a late 2006 I mac currently running OSX Lion?

    Ahhhh. Well, now you have earned a "Slap Kappy" coupon good for one slap. Expires in 30 days.
    The 64-bit kernel thing will leave a lot of use behind. My main machine is a 2006 Mac Pro on which I've spent some money putting in two 4-core CPUs and an ATI 5770 GPU in the past year. If I want to run ML I can't do so. The only options I have for a desktop Mac is either a newer Mac Pro model - post 2007 - used or refurbed or a recent or new iMac. This assumes the Mac Pro line may be dropped. Apple has been very mum on that.
    Clearly, Apple wants to get users of older hardware to buy new machines in order to run ML now and in the future. Because it is possible to boot the older models with the 64-bit kernel via some hacking, Apple might have been able to install ML on them by adding some code and retaining 32-bit drivers where needed, but they've chosen not to take that route. I think it's a bit of a marketing ploy to help drive up sales of new Macs, but I appreciate that Apple has chosen to abandon legacy support in the past in order to avoid having an OS like Windows - bloated by support for older and older hardware.

  • Technical support for Designer?

    Open question for Adobe employees (I know you guys/gals read this - you are posting in other threads...): Who is providing technical support for Livecycle Designer?
    After moving from the Flex community to the Livecycle community I get the sense that a few of the supporting applications for Livecycle are suffering "abandonment" issues. The UI's feel very "last gen" and basic features just are missing or just dont work properly. Getting any sort of technical support or product development roadmap just seems to not exist. Integration with many aspects are just plain clunky (ever tried creating custom guides with Flex for Livecycle?)
    Is there any official response from Adobe on where this product is headed?  Developer Blogs? Anything?

    Who is providing technical support for Livecycle Designer?
    The official technical support for organizations paying for support is Adobe Customer Support. If your organization has a support contract with Adobe and you encounter product failures or bugs, contact support http://www.adobe.com/support/livecycle/ and open a service request.
    This forum and other user forums like it are the unofficial support vehicles for the user community to share their problems and solutions. Many Adobe employees and partners voluntarily monitor the forum and provide as much assistance as they can. Adobe employees are not required to contribute to the forum. They do so out of interest for the community and to enable those with less experience and knowledge to utilize the technology as it was intended. The same is true for many non-employees who actively support the forum.
    Is there any official response from Adobe on where this product is headed?
    If you have specific product concerns you should contact your Adobe sales representative or partner.
    Developer Blogs? Anything?
    Here is partial list of pertinent URLs:
    Adobe Blogs - http://blogs.adobe.com/adobe-com-blogs
    FormFeed (John Brinkman on form design) - http://blogs.adobe.com/formfeed/
    LiveCycle Product Blog - http://blogs.adobe.com/livecycle/
    Adobe Solution Partner Program - http://blogs.adobe.com/solutionpartners/
    LiveCycle Developer Center - http://www.adobe.com/devnet/livecycle.html
    Adobe Enterprise Café - http://www.adobe.com/devnet/enterprise/cafe.html
    Adobe Enterprise Developer Program - http://www.adobe.com/devnet/aedp.html
    Steve

  • Applescript support for future CS

    Hi,
    I was asked by a customer if Applescript is going to be still supported in the next CS versions (starting from CS5).
    As Adobe is focusing more and more on Flex/AS3 for extensions, the question has made sense to me. So I ask here.
    Do you have any infos on that topic ? Will Applescript be supported for ever, is it planned to be abandoned ?
    Loic

    I would love to see Applescript support within Bridge, as I need to integrate Bridge, Filemaker, BBEdit, and OmniPlan into a start to finish workflow system. Javascript just doesn't cut it as it relates to file handling/manipulation.
    Kurt Jones
    [email protected]

  • [svn] 3203: Add support for inline two-way data binding (syntax is @{expr}) .

    Revision: 3203<br />Author:   [email protected]<br />Date:     2008-09-14 05:11:47 -0700 (Sun, 14 Sep 2008)<br /><br />Log Message:<br />-----------<br />Add support for inline two-way data binding (syntax is @{expr}).  Also add support for two-way data binding via the <mx:Binding> tag and the new property twoWay=boolean (default is false).<br /><br />Code Reviewer: Paul<br />QA: tests for this feature need to be added to the regression test suite<br />Doc: new feature which needs to be documented<br /><br />Modified Paths:<br />--------------<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/InterfaceCompiler.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/analyzer/SyntaxAnalyzer.java <br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AbstractBuilder.java <br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AnonymousObjectGraph Builder.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/DocumentBuilder.java <br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ModelBuilder.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ServiceRequestBuilde r.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/XMLBuilder.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/XMLListBuilder.java< br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/dom/BindingNode.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/TextParser.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/BindingExpression.java<b r />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/MxmlDocument.java<br />    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler_en.properties

    EvilDave UK wrote:
    Surely there's a more practical way around this without having to reboot?
    Before you go to the trouble of going through all those steps, be warned that attempting to use Dreamweaver CS4 with SVN could even cause Dreamweaver to crash after updating to SVN 1.6.2. I, too, have abandoned SVN integration with Dreamweaver until the problems are sorted out. I reported this problem to Adobe a couple of weeks ago, and spent a long time working with an Adobe engineer, who was able to reproduce the problem, but not offer a solution. Hopefully, the next version of Dreamweaver will have more robust support for Subversion.

  • DAQmx support for LabVIEW 2010

    FYI to those downloading LabVIEW 2010 from NI web site:
    After Installing LabVIEW 2010 (download from web site), I noticed that there is no support for DAQmx (i.e.. VI libraries) in NI_DeviceDrivers-February2010 DVD (my latest copy).  Your have to download and install DAQmx 9.2 drivers (the first to include LabVIEW 2010 support).
    Additionally, If you were using Traditional NI-DAQ (Legacy) 7.4.4 VIs in a prior version of LabVIEW, you must do one of the following:
          1. Uninstall current Traditional NI-DAQ (Legacy) 7.4.4 installation and re-install after completing LabVIEW 2010 installation.
              Reason: Traditional NI-DAQ (Legacy) installs support only for the latest version of LabVIEW found on the system.
    Or
          2. Copy the the "<previous LabVIEW>\vi.lib\Daq" directory and all it contents to a new "<LabVIEW 2010\vi.lib\Daq directory.  This way you can use Traditional NI-DAQ in both versions of LabVIEW.

    I didn't have DVDs, I had to download.
    Yes it was a mess.  The device driver download took forever (NI can't help that).  The installation took beyond forever (what else can be done?). 
    I was disappointed that I had to do all of this backing up of legacy folders and restoring them after installing the device drivers.  Why does NI always have device drivers and toolkits install to the latest version of Labview only?  Why couldn't they leave the legacy stuff alone??  I still use LV2009 and wanted to try LV2010.  This involved a whole lot of trouble and time. 
    NI needs to provide a much easier way to upgrade, while still allowing previous versions to work without modification.  Most people who upgrade will not completely abandon the older versions.
    - tbob
    Inventor of the WORM Global

  • Still no LR support for 5D Mk 1 tethered shooting

    Adobe's apparent decision to abandon further OS X support for tethered shooting in LR for the 5D Mk1 is one that is deeply contemptuous of its user base.So far, the company strategy in responding to complaints is to shrug and blame the situation on Canon and or Apple. But since both Capture One and Aperture seem to have successfully transitioned their support into Lion, this rings false and is particularly galling. Adobe needs to reinvest some of its huge profits into serving  those of us who have invested much of our time, money, and expertise in Adobe's integrated software solutions, only to have our loyalty betrayed by the company's cheeseparing attitude.
    As someone who uses a 5D for professional studio photography, shooting tethered has become a virtual necessity in my workflow. To continue using LR for this, my options are very limited: dial my MacBook Pro back to Snow Leopard, where Canon's own utilities still provide support, or tether via Lion's Image Capture, a barebones workaround.
    C'mon, Adobe, and do right by the undoubtedly thousands of your customers who shoot with the original 5D and depend on your software.

    Tetherering in Lr is dependent on the camera vendors SDK, which at time of release wasn't avaialble for either of the two cameras you mention. Fortunately, Canon and Nikon have recently made their SDKs available, therefore, I suspect we'll see tethering for SDMk3 and D800 sometime in the coming few months.

  • No iMovie Support for MPEG 1 Muxed Video?

    When I installed the new iMovie as a part of iLife 08, my iPhoto video's were imported into iMovie...I thought. However, only six of my 400 video clips came across. I called Apple Care and was informed that MPEG 1 Muxed video - the format used by virtually every high end Sony compact digital camera I've owned - is not supported. I was told that, using QuickTime Pro, I could individually convert each video clip in my iPhoto database to MPEG 2 or 4, 4 being the most robust format. That's a major hassle, to say the least. It doesn't seem that Apple would intentionally exclude the video taken by a vast number of iPhoto/iMovie users - Sony camera owners - but it looks like I may be mistaken. Thoughts? ideas? workarounds?

    Apple is meant to be about plug it in and work with it, not spend 2 weeks of ** trying to find information on how to do stuff.
    What you say is essentially true. However, IMHO there is a reasonable expectation that the item "plugged in" will be of the same form of technology as that into which it is plugged. For instance, I would never expect to "plug" a V2 rocket engine into a 1969 XKE Jaguar in place of the standard 6.2 liter gasoline engine and expect it to simply "work out of the box." Not all video is equal. MPEG-1 and MPEG-2 muxed compression was not invented by Apple, the exclusive right to its use does not belong to Apple, and the spatial synchronization technology involved is different than Apple's own temporal synchronization technology.
    How about apple just buy streamclip MPEG and integrate it into imovie 08 so that it is possible for it go say "this is a video I can't work with, please wait a moment whilst I reconvert it for you"... **, why not add it to iPhoto as well, so that it would do it when u add these videos from your camera and avoid the nasty iMovie issues.
    Not a bad idea, but who pays for it? First of all, the QT structure does not reside within the applications themselves. They are now a fully integrated part of the operating system. (Ever wonder why you can't "downgrade" a QT update that is causing problems on your system or why people advise that you "wait and see" before installing?) So essentially, the operating system itself, as well as, all sub-systems and applications will have to rewritten, or at least modified, to properly interface with this new "hybrid" engine that you propose that Apple create. And if Apple is to integrate 2-decade old MPEG technology that pre-dates Apple's own technology and which has never been fully supported previously, should they not also include support for similarly aged interleaved compression formats (yet another synchronization technology) which are no longer supported even by their own creators? What about support for other current but proprietary codecs like VidX or WMP? While you may not want all of these different things supported, the man standing next to you probably does.
    How much are you willing to pay? Surely Apple is going to pass the cost of research, development, and software maintenance on to the users. Will you spend an extra $225 to $250 to have muxed MPEG, DivX, WMV support "built in?" I'm not. Nor am I willing to foot the bill for outdated/abandoned AVI technology which I don't even use. I personally prefer to embrace the current modular approach and purchase/add only those components which I need on a daily basis but the person down the street doesn't use at all. Call it "freedom of choice" or call me a "cheapskate," but it is the way I feel about the matter. To me, it seems to boil down to a matter of "dollar$ & $ense." (Frankly, I would much prefer that Apple fix the current problems with its own supposedly "fully" supported compression formats before "mucking" about in the back yards of other manufacturers'. Of course, that is only my own personal opinion and I'm sure every reader out there as his or her own agenda here.)
    This is not a technical issue. This is a usability issue. i refuse to trawl through my photo collection, re-encode them (even by batch process) and save back to their original locations.
    Oh, I can agree that this is a usability issue, but only if "usability" includes the choice of hardware, choice to use/not use it, as well as, the choice to use/not use a workflow that avoids/gets around the problem.
    1) If viewing and sharing of files is your only concern, then the choice of camera employing MPEG-1 compression is fine. However, the limited support for this format is well documented and of long standing (although I agree that Apple is not particularly "forthcoming" with that fact that is only "playback" supported).
    2) I personally would never use any "still" camera to shoot video clips nor use a video camcorder to shoot "still photos. I.e., you should always use the best tool available for any given job. (E.g., I would not normally us a .22 to go rabbit or dove hunting nor a shotgun to go deer hunting or fishing either.) But, if your MPEG-1 still camera is the only "tool available," then the user must accept the problems that have always accompanied use of partially supported compression formats. (I.e., nothing has changed here.)
    3) Am a bit more concerned about those who did their research, picked a camera that supposedly takes "fully" compatible QT video clips, and now find that iMovie '08 will not accept such clips. (E.g., Kodak cameras which take MPEG4/µ-Law clips and even places them in an MOV file container.) Makes me feel almost as if they were somehow cheated. However, at least these individuals can still use iMovie '06 in this case.
    4) If you have a viable option that corrects the problem or gets around it and you choose not to use it, then that is a matter of personal choice and one should accept the consequences. Since these files were never audio supported in any iMovie version, I don't really understand why this incompatibility issue is suddenly such a big problem.

  • IPod Reset Utility is not supported for use with Windows Vista??????

    is there anyway to get pass this?
    i need to use the ipod resetutility to reset my shuffle
    but the only problem is that i have Vista and the program isnt
    supported for vista. can someone help me out here?

    well the only problem with that is that
    everyone i know use vista -.-

  • Lack of support for Canon G7 and G9. Alternatives?

    I am really disappointed about the lack of support for the Canon G9, and looking at the list of compatible cameras (http://docs.info.apple.com/article.html?artnum=306835) I notice that Canon G7 - even if it does not have a RAW format, is not supported either.
    I am thinking that the purchase of the G9 may have been premature and that I may need to sell it and get another cam that is supported by Apple/Aperture.
    What would you guys do? Is there a cam out there similar to the G9 at the moment that has a Apple-supported RAW format?
    Best regards,
    Kjell Are Refsvik

    I think the camera closest to the G9 that has RAW support from Apple are the Panasonic DMC-LX2/Leica D-Lux 3 twins. Don't know where you are, but in the US, the Panasonic costs about $400. 10MP, 28-112mm (35mm equivalent) Leica lens, very compact body, and RAW output. The Leica costs $599, and has that classic look.
    I don't know much about that cameras, but you may want to investigate.
    Message was edited by: rkkwan
    Message was edited by: rkkwan

  • Why no SyncML-support for Harmattan??

    I've used SyncML on my N95 with memotoo.com for years. Worked very well. I took it for granted that SyncML would be supported on the N9. But alas, it isn't. I find that really incomprehensible. Worse yet, CalDAV syncing with memotoo doesn't work - I don't know who's to blame for this, but on the desktop it works flawelessly so I do have a suspicion. Even worse: there is no way to sync contacts using CardDAV.
    MeeGo (the true MeeGo) has SyncML-support out-of-the-box. And the N9/N950 does have SyncML-support for bluetooth.
    Yes, contacts syncing is supported for Ovi. And Google. And Facebook. But I do NOT want to use those services, because of grave privacy risks and because they use yet again some proprietary protocols.
    I wonder, what where they thinking at Nokia for NOT supporting some well-known open standards??
    (While I'm ranting: why is there ^%@$ Facebook and GTalk-support over XMPP, but no self-defined XMPP account?? Yes, you can add such accounts from the terminal, using mc-tool, but really that's just a kick in the teeth. And where's UPnP/DLNA-support?)

    Hey Guys, Did you figure out any way to do PIM sync via SyncML on N9?
    I am struggling to get things moving as I come from N8.
    N9 just doesnt have any way to sync calendar, tasks with Ovi. Same with Notes.
    Best Regards,
    Suyog

  • ISE 1.2.1 support for Yosemite?

    Hello all, just curious. I see in the release notes for ISE 1.2.X that support for Mac OS 10.10 (Yosemite) was available via patch 12 on the ISE1.2.0 train of code. That said, I see nothing in the release notes stating any support for Yosemite for any of the patches for ISE1.2.1, the latest being patch 3 released 1 week after ISE 1.2.0 patch 12. Can anyone please advise if Yosemite is in fact supported on 1.2.1 with patch 3??
    Thank you very much in advance for your help
    Jeff

    Jeff,
    OS X 10.10 is supported in ISE 1.2 p11, 1.2.1 p2 and 1.3.
    Patch 12 for 1.2 and Patch 3 for 1.2.1 fix other issues for OS X 10.10, and I recommend updating to the latest patches for these fixes.
    Here is the entry in the Release Notes detailing the fix for 10.10 in 1.2 p 12:
    MacOsXAgent versrion 4.9.5.3 should be used and MacOsXSPWizard 1.0.0.30
    Note that the description for these files denote ISE 1.2 Patch 11/12, ISE 1.3 release and above.  ISE 1.2.1 is not mentioned, but follows the bug fix/release schedule for 1.2, with an adjustment.
    1.2 patch 10 = 1.2.1 patch 1
    Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question.  Otherwise, feel free to post follow-up questions.
    Charles Moreton

  • HT204266 My iPad (version 1, IOS 5.1) has quit connecting with the store. I am unable to update or buy any app. I did a reboot and a reset with deleting the data. I can not find anything in support for this problem. Any help will be appreciated.

    My iPad (version 1, IOS 5.1) has quit connecting with the store. I am unable to update or buy any app. I did a reboot and a reset with deleting the data. I can not find anything in support for this problem. Any help will be appreciated.

    My iPad (version 1, IOS 5.1) has quit connecting with the store. I am unable to update or buy any app. I did a reboot and a reset with deleting the data. I can not find anything in support for this problem. Any help will be appreciated.

Maybe you are looking for