ACR backward compatibility - why not?
I currently use Adobe CS3 (ACR 4.6) and the latest LR (3.4.1/ACR 6.4.1). I've been using a Kodak DCS SLR/n and LR/ACR to process my RAW files. I recently bought a Nikon D3s and have found that I can't open the NEF files in Bridge or PS, primarily because my PS ACR 4.6 can't read them, and PS informs me that the file is of the wrong kind. I don't even have the "Open in Camera Raw..." option in the context menu in Bridge for NEF.
My question is, then, is there an insurmountable technical reason that ACR can't be built so that it can 'degrade gracefully' for earlier versions of PS? I understand that new features and capabilities are added to ACR peirodically, but why can't the interface be designed such that an older version of PS can use the latest ACR (which, most importantly in this case, contains capabilities for newer cameras). PS doesn't care once the file is processed by ACR. It seems ACR could be easily written to determine what version of PS it should process for and, more importantly, why is it even tied to a specific version of PS anyway (other than perhaps 'smart objects').
Luckily, I have LR and can work around this newfound lack of capability with my upgraded camera. However, what I come away with from this experience is that this is a well-designed force-fed upgrade requirement for Adobe PS customers that don't appear to be truly necessary. If there is a valid techinical reason that this is not possible I will understand, but as a career SW architect/engineer, personally, I just don't see it. It appears that if Adobe has taken the path that if it can't create upgrades that stimulate mass upgrades (which haven't happened with CS4 or CS5, and shareholders know it), then they rely on HW updates to make their products obsolete. Not a good business practice. (Just ask Microsoft and the millions of people still using Windows XP Pro).
I would appreciate any input anyone might have on why ACR is designed in this way.
I can't find the official documentation, but 10 minute's googling found this in a forum ...
Command Line Support in the Adobe DNG Converter
Introduction
Previous versions of the Adobe DNG Converter always displayed a UI, which required human interaction to convert propriety raw files into DNG format. This made DNG conversion difficult to include as part of automated raw processing workflows.
Adobe DNG Converter 3.2 has added command line parameter support, which allows it to be run by automation systems without displaying a UI. This allows DNG converter to be included in automated raw processing workflows.
Running the Adobe DNG Converter from the Command Line
Under Windows, you can run the DNG converter from the command line by just typing the path to the executable file, followed by the parameters. For example, assuming the DNG Converter is installed at the standard location, type:
“C:\Program Files\Adobe DNG Converter.exe”
followed by the parameter list.
Note: Under Windows, you need to include at least one option in the parameter list to prevent the DNG Converter from displaying its UI. If you don’t have any non-default options to specify, just in use the “-c” option, which is a default option.
Under Mac OS X, you need to type to entire path to executable file, which is inside the Application bundle. For example, assuming the DNG Converter is installed at the standard location, type:
“/Applications/Adobe DNG Converter.app/Contents/MacOS/Adobe DNG Converter”
followed by the parameter list.
Parameter List
The parameters list consist of options followed by the names of raw files to convert. Options must precede the names of any raw files that they apply to, and apply to all the remaining raw files on the command line.
Command Line Options
The Adobe DNG Converter supports the following command line options:
-c Output compressed DNG files (default).
-u Output uncompressed DNG files.
-l Output linear DNG files.
-e Embed original raw file inside DNG files.
-p0 Set JPEG preview size to none.
-p1 Set JPEG preview size to medium size (default).
-p2 Set JPEG preview size to full size.
-d <directory> Output converted files to the specified directory.
Default is the same directory as the input file.
-o <filename> Specify the name of the output DNG file.
Default is the name of the input file with the extension
changed to “.dng”.
Similar Messages
-
While Updating to Fire Fox 4. It said Adobe Acrobat -Create PDF 1.0 is not supported.How come 3.6 supports but not 4. I believe you people have never heard of the term "Backward Compatibility" .U people will loose your customer/support base if every new version doesn't support some existing stuff.
'''Problem Solved FINALLY !'''
Solution:
I just updated my '''Adobe Acrobat X Pro''' to '''Version 10.1.0'''.By the way, I have to complain, Adobe is really slow in solving this problem...
Here is the official link for the Adobe Acrobat update.[http://www.adobe.com/support/downloads/detail.jsp?ftpID=5135 <click me!>http://www.adobe.com/support/downloads/detail.jsp?ftpID=5135<click me!>]
After update, the extention changed from "Adobe Acrobat -Create PDF 1.0" into "Adobe Acrobat - Create PDF 1.1". And the '''"Adobe Acrobat - Create PDF 1.1" is compatiable with the firefox 4.0.1'''. A screenshot is attached as a proof. -
Backwards Compatibility mapper module was not able to start
Hi ,
We have an issue with our SCOM 2012 agents not getting discovered because the Backwards Compatibility mapper module was not able to start.
I checked few blogs and could see the remediation for SCOM 2007 SP1.
http://blogs.msdn.com/b/mariussutara/archive/2008/03/11/backwards-compatibility-mapper-fails-to-start-event-on-opsmgr-2007-sp1.aspx
These are in the DMZ zone and are manually installed. i have bounced the health service folder as remediation but still looks the same.
For test i have set the mssing NetBios name for the server and restarted the service. Still the server is not getting discovered and shows the below error.
Log Name: Operations Manager
Source: HealthService
Date: 12/8/2014 6:13:23 PM
Event ID: 1103
Task Category: Health Service
Level: Warning
Keywords: Classic
User: N/A
Computer: Server.cc.domain
Description:
Summary: 1 rule(s)/monitor(s) failed and got unloaded, 1 of them reached the failure limit that prevents automatic reload. Management group "MG Group name". This is summary only event, please see other events with descriptions of unloaded rule(s)/monitor(s).
Log Name: Operations Manager
Source: Health Service Modules
Date: 12/8/2014 6:13:23 PM
Event ID: 10720
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Server.cc.domain
Description:
The Backwards Compatibility mapper module was not able to start because discovery has not fully completed for this Health Service. This is a transient issue, the affected rule(s) will be unloaded and the Health Service will restart them when initialization
is complete.
One or more workflows were affected by this.
Workflow name: System.Mom.BackwardCompatibility.ServiceStateMonitoring
Instance name: Server.cc.domain
Instance ID: {E0B732FD-3908-E52B-2EAD-813F42F0C48E}
Management group: MG Group name
Jesty SamHi Jesty,
Based on the Article it seems to be for SCOM 2007 SP1.
And as you mentioned you are using SCOM 2007 R2. I see that Microsoft has fixed this issue about the article you have mentioned above.
Below is the article from MS for that.
951380 Some
computer properties for a cluster node may not be collected by the discovery process in System Center Operations Manager 2007 Service Pack 1
Check the below link where MS has mentioned it has fixed this issue in SCOM 2007 R2.
http://support.microsoft.com/kb/971410
So i dont think it is necessary for
you to install this Hotfix
Gautam.75801 -
5.0 not backwards compatable???
I just compiled some 1.4.2 code in 1.5, and I got a compiler error. It's not a huge deal, and easily fixable, but I just found it odd that it wasn't backwards compatable. It's suppsoed to be, isn't it?
It's code that implements Comparable
public int compareTo(Object o) {
return toString().compareTo(o);
}compareTo(java.lang.String) in java.lang.String cannot be applied to (java.lang.Object) at line 92, column 25
Just incase this was already fixed, I tried compiling this in the latest 1.6.0_01 and I get the same error. The code looked like it was meant to compare the string versions of the objects if the objects were not of the right type. I suppose this case is no longer even valid using generics in Comparable, but like I said, it should still compile if it worked in 1.4.2.I just compiled some 1.4.2 code in 1.5, and I got a
compiler error. It's not a huge deal, and easily
fixable, but I just found it odd that it wasn't
backwards compatable. It's suppsoed to be, isn't
it?No, it's not. Nobody ever said that all code that was compilable with javac 1.4 would be compilable with javac 1.5. Only binary compatibility was guaranteed. That means that you may compile the code you're showing with a 1.4 compiler or with the latest javac if you set the option "-source 1.4".
After compilation, the generated class file will then be usable by all Java programs, even those compiled with Java 5 or 6.
BTW, with or without generics, the code looks so highly suspicious that you should be very glad the compiler finally rejects it. To make any sense, it should look like this, which is fine with every Java version:
public int compareTo(Object o) {
return toString().compareTo(o.toString()); -
It is very frustrating when you purchase a VERY expensive software package that is the latest version only to start receiving "You can't open this because there's a newer version out" error messages less than a year later.
I know you're going to defend yourselves with some stock BS such as "Newer versions have capabilities that older version don't have", but I know this isn't the case. Illustrator could just open the newer versions and you know what, if there's some effect that isn't supported, just let it display it incorrectly. I'm almost positive that you've purposefully programmed your software to detect if a file is a newer version and then force illustrator to display the error and not open it.
I believe you are using dishonest and shady tactics to increase revenue, and I am very displeased.@ joshmakar:
To a large extent, you are preaching to the choir here. Many long-time helpers in these fora have left in recent years, often over disillusion re: Adobe and it's current course in many areas.
While it is little consolation regarding the question/ problem in your initial post; if the newer AI file was saved with PDF compatibility ON (the default, I believe), you MAY be able to PLACE the file into an open Illustrator document. Exactly how editable it will remain is questionable, and depends on the file and what tools and effects may have been used. It is not backward compatibility, but it is (like so much in Adobe software any more) a workaround.
And, of course, one can always ask whoever supplied the file to save as an older format, but see my note above re: workarounds.
Who, Me? Cynical? NAH!
--OB -
InDesign Backwards Compatibility in CS5 an MAJOR issue
I am a print designer who works in InDesign. I bought CS3 Design Premium in late summer of 2008. Shortly thereafter CS4 came out, but after just having forked out a big chunk of change, I decided against upgrading to CS4 right away. Recently I considered upgrading but then heard CS5 was coming out so I decided to postpone the upgrade and wait for the new software. I've just checked out the trial version of CS5 InDesign and after speaking with Adobe Support have come to the conclusion that I can't upgrade to CS5. Why? BACKWARDS compatibility to CS3. The previously offered export features that supplied a path for backwards compatibility via an .inx file are gone.
I design freelance for a lot of different customers and once the design is complete, I have to deliver the InDesign file along with all associated fonts ad images to my clients. Most of my clients are still on CS3. If I upgrade to CS5 I will instantly not be able to work for 2/3 of my clients, as I will have no means by which to save a file backwards to CS3. I was informed by Adobe support that I would need to buy CS4 and CS5, as I could save my CS5 file in the IDML format and open it in CS4 and then I could save the file from CS4 as an INX file and open that is CS3. ARE THEY INSANE??? First off that requires keeping 3 version of InDesign up and running on my machine all of the time and secondly, why should I have to buy CS4 when I'm paying an additional fee to upgrade to CS5 because I didn't upgrade from CS4? This is so screwed up that it has to be an oversight---please tell me there is a patch in the works!!!
PS- I've never posted to a forum before, so if I have broken any rules of forum etiquette or offended in any way, I offer my apologies now and if I (and the Adobe Support staff I spoke to) have overlooked something, please enlighten me!Cynthia Ryan Graphic wrote:
I am all for working with better workflow practices and I understand that saving files backwards is less than ideal but Adobe needs to look at the real world uses of their software as well. I have to work with firms that aren't upgrading now--especially with the economy we are now in--and most of the items I design for them are ads-- one page- nothing too complex--really nothing fancy. I obviously wouldn't save a book or a very complex document backwards in this way, but simple things have translated just fine in the past. In the real world we hit situations like this.
I bought my software 21 months ago and in this time Adobe has expected me to upgrade twice--I haven't even finished expensing the initial cost of the software on my books yet. Upgrading that often just can't happen in a small firm--it's prohibitively expensive for a one man shop.
So now from what I understand, to do this properly, I am supposed to buy the upgrade and keep both versions running on my machine and track with every client which version of the software I need to be working in. What happens when I have to add an employee? I will have to buy the CS3 version of the software in addition to the CS5 Suite because otherwise we can't work on the same files. I'm finding this frustrating.
Your suggestion of buying CS4 from Amazon is a good one. I will look into that further.
DISCLAIMER: I'm an Adobe stockholder. REALITY: My holdings are probably in the same proportion as the number of bits it takes to store a period character (".") on an Internet server is to the entire Internet's storage capacity. So, while I may have some self-interest here, it's not driving me to encourage you - or even all the participants on this forum - to buy more software than you want to or need to.
If you're simply interested in test-driving a new release, you can do that with the free 30-day trials. If you run out time, you can probably figure out a way to trick out your system to get another 30-day shot.
However, if you use the software commercially - either to train others, or to create new material or revise old material for clients or employers - you need to decide if you can continue to do this with the software versions you own, or if the commercial needs will require you to license new versions.
Regarding "expensing the initial cost of the software on my books" If I understand the US income-tax policies, purchases under a rather modest amount can usually be expensed in the year of purchase. If, because of your accounting method or preference, you're using a longer expensing time period, you might want to reevaluate your approach. If you attribute a portion of the software cost to each project you use it on, and, in this case, in 21 months your work hasn't let you recapture the investment, they you may want to use that information to decide how to pursue more paying for the software, or decline that stream of work and forgo upgrading.
An alternate way to evaluate the software, especially as an employer of users, is to compare the product cost vs. how many more billable hours you and your workers can complete in a given time with it and without it, and, how competitively you can bid projects, due to the product's efficiency.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices -
Project Spartan policy on backwards compatability
I originally posted this to another Microsoft forum (but the system won't let me link it, so just google a random sentence below if you want to find it). I guess it can only really be addressed by someone on the Spartan team or up their line of supervisors
and a Microsoft Support Engineer suggested I post here instead. So:
Hi. I'd like to know if Project Spartan's backwards compatability policy will be different from Internet Explorer's.
Microsoft's general policy seems to be to go to great lengths to preserve backwards compatibility. (Raymond Chen's blog The Old New Thing has some great war stories about this.) For example, an IE 3 (Aug 1996) JavaScript quirk was that an array with a trailing
comma was longer than one without. [1].length != [1,].length Changing this behavior to match other browsers and the ECMAScript standard would possibly break JavaScript that had been written to depend on it, so it still exists in in-use versions of IE.
I understand why this policy exists and has been such a valuable business policy for Microsoft for decades. The situation is a bit different with a web browser, though, because the majority of third-party authors have to be compatible with browsers from
multiple vendors rather than a single Microsoft platform like embedded browsers or locked-down corporate intranets (not that those groups are tiny!). The other browsers have a different policy and will break backwards compatibility to better match the specs
(whether explicit or de facto). So the code I write to create websites quickly turns into “this works everywhere, except where you need this IE workaround”. I regularly encounter IE-only behaviors and bugs that I expect never to change, like recently finding
that only IE is case-insensitive when scrolling an HTML5 page to an in-page identifier or anchor from the URL fragid.
I've read a lot about the quality improvements planned for Spartan and I look forward to seeing a lot of these hairy old cross-browser differences get reconciled. But as a longtime developer I know no software is perfect and there will always be bugs. So
my question is: will this be a one-time fix or will there be a new policy towards backwards compatibility? If it's the former, Spartan is the new IE, and I know this tune very well. If the latter, there's a little room for hope that it will be pleasant to
work with.
Thanks for your consideration, and good luck with your code.PU
You can replace Http:// with Hxxp:// to put a link in until your account is verified.
Your thread on Answers is here http://answers.microsoft.com/en-us/insider/forum/insider_internet-insider_spartan/project-spartan-policy-on-backwards-compatability/d25ff33b-aeed-40fb-802b-af25fb9d157c
If you are being told you cant post a link, or embed a picture (or any other restriction) you just need to post to this thread saying your account has not been validated
Look for the verify your account thread that is stuck to the top of the page.
http://social.technet.microsoft.com/Forums/en-US/home?forum=reportabug
Read more here http://social.technet.microsoft.com/Forums/windows/en-US/9fe32cfb-ed1c-4b9d-93d9-7ff32b0106a3/verify-your-account-16?forum=reportabug
Wanikiya and Dyami--Team Zigzag -
Transient addition breaks backward compatibility
Hi folks. I have the following problem. I made some changes to a class and I have serialised objects created before the changes. I hoped that the changes I made would still be backwards compatable and that I would still be able to deserialise legacy objects.
I made the following changes...
added
private transient int _hashcode = 0;and
private void readObject(ObjectInputStream ois) throws ClassNotFoundException, IOException {
ois.defaultReadObject();
_hashcode = calcHashCode();
}The changes were motivated by some profiling using JIP which indicated that the hashCode method of my class was being called very repetitively outside of my control, and instead I decided to cache the hashcode instead of recalculating it.
Unfortunately however, now I get a java.io.StreamCorruptedException when I try to deserialise a Hashtable containing old objects of this class. Now, I know I can hack a fix into the code; however, I would love if someone could point out my stupidity and tell me why the class is no longer backwards compatable. Is the transient element an issue, or am I doing something stupid with the readObject method? The calcHashCode() method simply reinitialises the _hashcode field by calculating it's values from other fields.
Thanks.
B.T.W. I use
public static final long serialVersionUID = 1l;I don't suppose anyone is waiting with baited breath on this one, but I finally got back to the problem today and realised that my equals method which I also changed was the problem.
I wanted to speed up the equals method by ONLY checking that the hashcodes (which I cached) were equal and was being naive assuming the hashcodes would be unique for the input string. However, had a look at the birthday problem and figured that after hashing ~77,163 entries over the 2^32 Integer range that you are 50% likely to get a hash collision. Didn't realise the number was so small.
Now I initially check the hashcodes in the equals methods and if they are the same, then I check the data. This should at least speed up common non-equals comparisons. Apparently there was a collision in the hashtable I had previously serialised, so the integrity of the serialised hashtable must've been screwed with; hence the exception. When there is a collision in the hashtable, it reverts to the equals method.
Things I learnt:
#1 - Hash collisions are more likely than I thought
#2 - Keep to the equals, hashCode and compareTo regulations
#3 - Changing such methods can screw with backwards compatability of serilialised objects, not only adding removing fields
New equals:
public boolean equals(Object o) {
if (o==this)
return true;
else if (o instanceof Blah){
Blah b = (Blah)o;
return b._hashcode==_hashcode
&& (b._data==_data || b._data.equals(_data));
else return false;
} -
My iPad 1 is very unstable. Many Apps simply crash after opening. There is ample storage available.I have restored the iPad twice now and still it is unstable.
Is this a lack of backwards compatibility because no-one writes apps for IOS 51.1. and the original iPad anymore? not even Apple, as the documents and sheets I create on my Mac are incompatible with my iPad now.
My naievete tells me that this is simply Apple expecting us to upgrade to later levels of hardware. If so, very disappointing for an Apple fan. Seems your App developer approvals (even your own apps) do no require compatibility with anything but IOS 6 or later.There are various things to make your iPad more stable. You can try deleting all apps from the multitasking bar; do a reset ie hold the power and home buttons simultaneously until the Apple logo appears; Settings > General > Reset all Settings.
If you had the previous version of iPages (version 09) on your Mac before upgrading to Pages 5.2, your Mac should still have that version in Applications, which is still compatible with your version of Pages on your iPad.
If you don't have that version, you can 'Export to Pages 09' which is still compatible with iOS 5.1.1. -
We've been getting the following error for some time now.
An error occurred on line 105 while executing script 'MOM Backward Compatibility Service State Monitoring Script'
Source: Microsoft VBScript runtime error
Description: The remote server machine does not exist or is unavailable: 'GetObject'
One or more workflows were affected by this.
Workflow name: System.Mom.BackwardCompatibility.ServiceStateMonitoring
Instance name: server.domain.local
Instance ID: {INSTANCE}
Management group: GROUP
Unfortunately the instance in question has since been decommissioned and simply does not exist any more.
We're currently on a repeat count of over 350,000 and I would REALLY like to get it stopped. I've had a look at adding an override but that points to the management server rather than the instance itself.
Does anyone have any suggestions?
thanks in advance!Hi Steven,
There are for option for us to override a monitor ot rule:
For all objects of class:
Class
When you select this option for your override, the override settings apply to all objects in the class at which the rule or monitor is targeted.
For a group
When you select this option for your override, the override settings apply only to members of the group. The rule or monitor without the override settings continues to apply to all objects in the targeted class except for those objects that are also members
of the group used for the override.
When you create a group, you save it to an unsealed management pack. However, an element in an unsealed management pack, such as an override, cannot reference an element in a different unsealed management pack, such as a group. If you are going to use a group
to limit the application of an override, you must either save the group to the same unsealed management pack as the override, or you must seal the management pack that contains the group.
For a specific object of class:
Class
When you select this option for your override, the override settings apply only to the specified object. The rule or monitor without the override settings continues to apply to all other objects in the targeted class.
For all objects of another class
When you select this option for your override, the override settings apply only to objects of a class other than the targeted class. The rule or monitor without the override settings continues to apply to all objects in the targeted class.
Did you try to override it for a specific object of class?
Regards,
Yan Li
Regards, Yan Li -
Hi
Our application is composed of few data layers. The layers comunicate through interfaces.
My manager thinks that we should maintain backward compatibility between the layers.
So:
There is a defined functional interface "I".
There is a layer component "L" which provides the functionality of I.
There is a layer component "UL" which Uses L via I.
A new layer component "L2" is created which has greater functionality than L and which it exposes via a new interface "I2".
All the functions of I are also provided by I2. In other words, I is a subset of I2.
"UL" will provide to a "layer factory" a version number, and the factory will return "L" or "L2" etc.
This means that we cannot override methods, and difficult maintaining of code as well as code duplication.
The bennefit of this is that all the components that worked fine with the previous "L" and were not changed, are guarantied to continue working, and needn't any QA.
What do you think? Does it worth the trouble?
Thanks,
Libbhylibbysharf wrote:
The bennefit of this is that all the components that worked fine with the previous "L" and were not changed, are guarantied to continue working, and needn't any QA.Based on what you have stated here, this is not necessarily the case. Just having the same method signatures doesn't not mean that it will work exactly the same way. Even if the methods from L are implemented in the exact same way in L2, you could have situations where the new L2 methods change the behavior of the old L methods.
What do you think? Does it worth the trouble?Personally, I think it seems a little over-engineered. If you just add to a class, it will not break binary compatibility with existing clients. You'd be much better off spending time creating unit tests and regression test scripts and try to verify that the behaviors from the previous verison are maintained. -
Backward Compatibility Question
Our ADS system is running with Basis 7.0 SAPKB70005
Can we develop forms on systems with a lower Basis version e.g. 6.4?
Are there backward compatibility issues?
Regards,
LavaughnHi Lavaughn
it depends a bit on what you want to do.
If you want to develop the form on the 6.40 box and then render it with the 7.0 Application Server, the answer is No, as the solution always needs to be on the same NW level (i.e. either '04 or 2004s). SAP development always coordinates changes between Designer, ADS, Reader, and the SAP development environment - and there are a few incompatible changes between '04 and 2004s.
If you want to develop and render the forms on the 7.0 box and integrate data from a lower-release backend (e.g. R/3 Enterprise), you can do that for interactive scenarios using RFC connections to transfer the data and/or the PDF form from system to system.
Do not attempt to do this for print forms. The amount of data that may have to be transferred will heavily impact the form generation time.
Kind regards,
Markus Meisl
SAP NetWeaver Product Management -
I am considering CS6. I worry about
"backwards compatability." I am in a windows-only environment. Some files were antiquated mac computer. Files are: psd doc eps tif indd otf ai jpg
RW2 xmp pm7 bmp fh9 fh10 dng pm6 and ps. RickBackward compatibility FROM what TO what?
CS6 to older, or newer to CS6?
For specific answers, you most likely need to check in the forums for specific programs
The Cloud forum is not about using individual programs
The Cloud forum is about the Cloud as a delivery & install process
If you will start at the Forums Index https://forums.adobe.com/welcome
You will be able to select a forum for the specific Adobe product(s) you use
Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll -
Known backwards compatibility issues between Robohelp 9 and Robohelp 8?
Hi Group,
In addition to avoiding the tasks in the Review menu, does anyone know of any other backwards compatibility issues encountered while opening and using files generated in RoboHelp 9 from within Robohelp 8? Thanks, gailWelcome to the forum.
Simply the fact that RoboHelp 8 will not open a project that has been run in RoboHelp 9. Sure you might well open a project by deleting the CPD and perhaps the XPJ and using the HHP, however I would not recommend that except in an emergency.
What I am not clear on is how you link that to "avoiding the tasks in the Review menu." What has that got to do with the question?
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge -
Instalation of SQL server 2005 Backward compatibility components in Windows Seven
Anyone can help me to install de SQL Server 2005 Backward Compatibility componentes in Windows 7 home, Intel Core Duo
It say that is not compatible.
Thanks in advance.Hi,
We can see this feature pack was issued in Nov 2005 from the site, which may not be updated
to add Windows Vista/7 to supported operating systems. However, I can download and install X64 (64-bit)
Microsoft SQL Server 2005 Backward Compatibility Components on Windows 7 Enterprise 64-bit successfully.
If you get any error while installing, please let me know.
Thanks,
Chunsong
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Maybe you are looking for
-
PO- Contract release Qty not matching with minimum delivery qty
Hi expert, I have a requirement , there is a business process where my client need to replenish the fuel tank every two days . The tank capacity is 100,000 gallon and supplier supply the fuel of tank 11500 gallon every time. To map this
-
Inactive InfoObject after Transport
We modified an InfoObject and transported the change; however, our BWQ system still does not recognize the InfoObject has active. And the InfoObject is active in BWD. Our BWD system has the automatic transport connection active; then we went back a
-
I have a 2nd iPhone, the same problem of missing Data in Notes Apps again. Please advise.
I have a 2nd iPhone, the same problem of missing Data in Notes Apps again. Please advise.
-
Unparsable date "yyyy-MM-dd" in Windows Arabic OS
Hi Guys, I have one problem. Plese help me regarding in this. I am not able to parse the date format like "yyyy-MM-dd" in Windows XP Arabic OS environment. But the same thing is working fine in Windows XP English OS. I am using jdk version is j2sdk1.
-
HELP! Itunes can not find my speaker
It used to work well. After I upgrade my itunes to version 8, it always turns out that an "erro" when I try to stream my itunes music to speaker connected to Airport Express... Does anybody here know what the problem is? It's that because my AE is a