What are Apple's rules on refunding price difference ?

Just bought a MacBook Air last Friday and didn't know that the price would drop less than a week later. Will I be able to get the difference back?

Since the processors in the new models are more energy efficient, it's definitely a worthwhile swap:
Power-efficient fourth generation Intel Core i5 and Core i7 processors work in conjunction with OS X® Mavericks to give the 13-inch MacBook Air up to 12 hours of battery life and the 11-inch MacBook Air up to 9 hours of battery life. iTunes® movie playback times increase to 12 hours on the 13-inch notebook and 9 hours on the 11-inch notebook, adding up to two hours of playback time to the updated MacBook Air.

Similar Messages

What are Apple doing to compensate for the damage caused by the iPhone 4 bumper?

I have noticed damage caused by the bumper.
It is NOT foreign object but caused by the hard plastic on the inside of the bumper
(plese do not come out with rubbish like steel is harder than plastic) I am not stupid and I know that the damage matches the pattern of the bumper skeleton.
What I want to know is when are Apple going to deal with this and replace my phone?
I dare not go to the so called Genius bar in Milton Keynes as they have adopted a Dixons style "fob off" attitude and I will become rather angry with them.

Re: What are Apple doing to compensate for the damage caused by the iPhone 4 bumper?
15-Jun-2011 15:15 (in response to sfrommilton keynes)
o Steel is harder than plastic, so the bumper has not caused the damage.
- You call it rubbish
- The world calls it physics
You are totally wrong. Please go back to School.
o You can deny physics
- but that will not change reality.
You can go to School but that wont change reality.
o Your description of your Genius bar is incomprehensible
- I recommend you go to the Genius bar leaving the chip on your shoulder at home and tactfully explain what you think is your issue.
I recomend you find a day job ans stop TROLLING peoples threads.
- I've never had them fail me or be the least bit confrontational.
- But if you act like a jerk then I couldn't predict what would happen
Yeah because you were there. Are you having some kind of relationship with the company? I think you sleep with an Apple under your pillow.
Finally I am a consumer who has paid for a product that is not living up to expectations. The plastic skelton is hard and abrasive (I know what that means as I went to School) Abrasion's are marking the product.
This is not the only time this has been reported and as such I have no issue with particles entering the bumber. This has happened from the start (when I used Apples stupid bumber case)
Please don't patronise or TROLL others threads.
<Edited by Host>

How to find what are all the rules and events are monitoring for specific server in SCOM 2007

how to find what are all the rules and events are monitoring for specific server in SCOM 2007.
I need to know what are all the events, services, and rules are monitored for the specific server.
Kindly help me friends.

how to find what are all the rules and events are monitoring for specific server in SCOM 2007.
I need to know what are all the events, services, and rules are monitored for the specific server.
Kindly help me friends.
Thanks for the question Sandoss. This is something that we all come across at sometime.
Thanks & regards, Sumit Agrawal
The lack of this feature is an inexcusable oversight for an enterprise management product. They have some serious lightweights making design decisions on the SCOM team. 5 thumbs down.
BTW the answer is probably LOTS of stuff. Literally 100's of workflows are running on any server.
The following OpsMgr DB query will list all running monitors on a server. Change the name of @srv. I think this works pretty well. I'd like some feedback if something is missing.
DECLARE @srv varchar(30)
SET @srv = 'your name here'
SELECT mon.displayName as monitor, bme.FullName,bme.DisplayName as object,
case
 when s.HealthState = 1 then 'healthy'
 when s.HealthState = 2 then 'Warning'
 when s.HealthState = 3 then 'Critical'
 else 'N/A'
end as Health
FROM state AS s WITH (NOLOCK)
left join BaseManagedEntity as bme WITH (NOLOCK) on s.basemanagedentityid = bme.basemanagedentityid
left join dbo.MonitorView Mon WITH (NOLOCK) on Mon.ID = s.monitorid
where
bme.FullName like '%' + @srv + '%'
and s.HealthState <> 0
and mon.IsInternalRollupMonitor = 0
and mon.IsExternalRollupMonitor = 0
order by bme.DisplayName, mon.displayName

What are schemas and rules in HR?How it will use in HR?

Hi HR Proff,
What are schemas and rules in HR?How it will use in HR?
Give some documentation on this?
Early reply is highely appriciable.
Regards,
Chow.

Refer this link -
http://www.sd-solutions.com/documents/SDS_Payroll_Schemas.html
Regards,
Amit

What are the conversion rules

what are the conversion rules?can anybody give information on that?points wil be rewarded?

hI..
From sap help....
Conversion Rules for Elementary Data Types
There are ten predefined ABAP data types. There are 100 possible type combinations between these elementary data types. ABAP supports automatic type conversion and length adjustment for all of them except type D (date) and type T (time) fields which cannot be converted into each other.
The following conversion tables define the rules for converting elementary data types for all possible combinations of source and target fields.
C D F I N P STRING T X XSTRING
Source Type Character

Conversion table for source type C
Target
Conversion
C
The target field is filled from left to right. If it is too long, it is filled with blanks from the right. If it is too short, the contents are truncated from the right.
D
The character field must contain an 8-character date in the format YYYYMMDD .
F
The contents of the source field must be a valid representation of a type F field as described in Literals.
N
Only the digits in the source field are copied. The field is right-justified and filled with trailing zeros.
I, P
The source field must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The occupied length of the source field is copied. All trailing spaces are truncated.
T
The character field must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for fields of type X, except that the target field is not filled with zeros.
Source Type Date
Conversion table for source type D
Target
Conversion
C
The date is transported left-justified without conversion.
D
Transport without conversion.
F
The date is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
I, P
The date is converted to the number of days since 01.01.0001.
STRING
The date is converted to a character field, which is then converted to a character string.
T
Not supported. Results in an error message during the syntax check or in a runtime error.
X
The date is converted to the number of days since 01.01.0001 in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Floating Point Number
Conversion table for source type F
Target
Conversion
C
The floating point number is converted to the <mantissa>E<exponent> format and transported to the character field. The value of the mantissa lies between 1 and 10 unless the number is zero. The exponent is always signed. If the target field is too short, the mantissa is rounded. The length of the character field must be at least 6 bytes.
D
The source field is converted into a packed number. The packed number is then converted into a date field (see corresponding table).
F
Transport without conversion.
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The floating point number is converted to an integer or fixed point value and, if necessary, rounded.
STRING
As for fields of type C, except that the maximum number of places is used for the mantissa (maximum precision). Despite this, different signs or exponents can lead to different string lengths.
T
The source field is converted into a packed number. The packed number is then converted into a time field (see corresponding table).
X
The source field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Integer
Type I is always treated in the same way as type P without decimal places. Wherever type P is mentioned, the same applies to type I fields.
Source Type Numeric Text
Conversion table for source type N
Target
Conversion
C
The numeric field is treated like a character field. Leading zeros are retained.
D
The numeric field is converted into a character field. The character field is then converted into a date field (see corresponding table).
F
The numeric field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The numeric field is transported right-justified and filled with zeros or truncated on the left.
I, P
The numeric field is interpreted as a number, and transferred to the target field, where it is right-justified, and adopts a plus sign. If the target field is too short, the program may be terminated.
STRING
As for fields of type C. The length of the character string matches the length of the numeric text.
T
The numeric field is converted into a character field. The character field is then converted into a time field (see corresponding table).
X
The numeric field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Packed Number
If the program attribute Fixed point arithmetic is set, the system rounds type P fields according to the number of decimal places or fills them out with zeros.
Conversion table for source type P
Target
Conversion

C
The packed field is transported right-justified to the character field, if required with a decimal point. The last position is reserved for the sign. Leading zeros appear as blanks. If the target field is too short, the sign is omitted for positive numbers. If this is still not sufficient, the field is truncated on the left. ABAP indicates the truncation with an asterisk (*). If you want the leading zeros to appear in the character field, use UNPACK instead of MOVE.
D
The packed field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The packed field is accepted and transported as a floating point number.
N
The packed field is rounded if necessary, unpacked, and then transported right-justified. The sign is omitted. If required, the target field is filled with zeros on the left.
I, P
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified. If the target field is too short, an overflow occurs. If the target field is longer, it is filled with zeros on the left.
STRING
As for fields of type C, except that leading zeros are not generated.
T
The packed field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified and in big-endian format. If the target field is too short, it is truncated from the left. If the target field is longer than 4, it is filled with zeros on the left. Negative numbers are represented by the two's complement (= bit complement +1).
XSTRING
As for fields of type X, except that leading zeros are not generated.
Source Type String
Conversion table for source type STRING
Target
Conversion
C
The target field is filled from left to right. If it is longer than the string, it is filled with trailing spaces. If it is too short, the contents are truncated from the right.
D
The string must contain an 8-character date in the format YYYYMMDD .
F
The contents of the string must be a valid representation of a type F field as described in Literals.
N
Only digits in the string are copied. The field is right-justified and filled with trailing zeros. If the target field is too short, it is truncated from the left.
I, P
The string must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The source string is copied to the target string unconverted.
T
The string must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal-character string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This character string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for target fields of type X, except that the field is not filled with zeros.

Source Type Time
Conversion table for source type T
Target
Conversion
C
The source field is transported left-justified without conversion.
D
Not supported. Results in an error message during the syntax check or in a runtime error.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is converted into a character field. The character field is then converted into a numeric text field (see corresponding table).
I, P
The date is converted to the number of seconds since midnight.
STRING
The time is converted to a character field, which is then converted to a character string.
T
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
X
The date is converted to the number of seconds since midnight in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Hexadecimal Field
Conversion table for source type X
Target
Conversion
C
The value in the hexadecimal field is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The source field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The value of the source field is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the hexadecimal field is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the hexadecimal field.
T
The source field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The value is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The hexadecimal field is copied completely that is, trailing zeros are not truncated.
Source Type Byte Sequence
Conversion table for source type XSTRING
Target
Conversion
C
The value in the byte sequence is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The byte sequence value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The content of the byte sequence is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The content of the byte sequence is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The content of the byte sequence is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the byte sequence is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the byte sequence.
T
The byte sequence value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The byte sequence is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The source byte sequence is copied to the target byte sequence unconverted.
Conversion Rules for Internal Tables
Internal tables can only be converted into other internal tables. You cannot convert them into structures or elementary fields.
Internal tables are convertible if their line types are convertible. The convertibility of internal tables does not depend on the number of lines.
Conversion rules for internal tables:
Internal tables which have internal tables as their line type are convertible if the internal tables which define the line types are convertible.
Internal tables which have line types that are structures with internal tables as components are convertible according to the conversion rules for structures if the structures are compatible.
Conversion Rules for Structures
ABAP has one rule for converting structures that do not contain internal tables as components. There are no conversion rules for structures that contain internal tables. You can only make assignments between structures that are compatible.
You can combine convertible structures in the following combinations:
Converting a structure into a non-compatible structure
Converting elementary fields into structures
Converting structures into elementary fields
In each case, the system first converts all the structures concerned to type C fields and then performs the conversion between the two resulting elementary fields. The length of the type C fields is the sum of the lengths of the structure components. This rule applies to all operations using structures that do not contain internal tables.
If a structure is aligned, the filler fields are also added to the length of the type C field.
A non-aligned structure without filler fields:
If you convert a structure into a shorter structure, the original structure is truncated. If you convert a structure into a longer one, the parts at the end are not initialized according to their type, but filled with blanks.
It can make sense to assign a structure to another, incompatible, structure if, for example, the target structure is shorter than the source, and both structures have the same construction over the length of the shorter structure. However, numeric components of structures that are filled in incompatible assignments may contain nonsensical or invalid values that may cause runtime errors.
DATA: BEGIN OF FS1,
INT TYPE I VALUE 5,
PACK TYPE P DECIMALS 2 VALUE 2.26,
TEXT(10) TYPE C VALUE Fine text,
FLOAT TYPE F VALUE 1.234e+05,
DATA TYPE D VALUE 19950916,
END OF FS1.
DATA: BEGIN OF FS2,
INT TYPE I VALUE 3,
PACK TYPE P DECIMALS 2 VALUE 72.34,
TEXT(5) TYPE C VALUE Hello,
END OF FS2.
WRITE: / FS1-INT, FS1-PACK; FS1-TEXT, FS1-FLOAT, FS1-DATE.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
MOVE FS1 TO FS2.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
Message was edited by:
Rammohan Nagam

Dead-code elimination--what are all the rules?

This article http://www-128.ibm.com/developerworks/library/j-jtp12214/ has an entire section on dead-code elimination (DCE).
Does anyone know what all the criteria are by which the hotspot JIT compiler can determine that code is "dead"?
One obvious criteria is if the code will never get executed. I think that the canonical example is code like this:
       static final boolean debug = false;
       static void someMethod() {
               if (debug) {
       }Here, the compiler (javac as well as hotspot's JIT) can determine that someMethod has nothing inside it that could ever get executed, so it can be turned into an empty method.
If you look at that developerworks link above, he gives an even more interesting example for how hotspot's JIT can make sophisticated DCE based on inlining.
What I want to know is what are all the criteria that hotspot can use to decide that code is dead. Code that is never executed is always correct. But can it make more liberal decisions as to what counts as dead code?
Consider this code:
     int[] foo = new int[1000];
     int bar = foo.length;
     // don't use foo again, but do use barA smart compiler could recognize that the array declaration and allocation is actually useless, and simply do
     int bar = 1000;(Thank you Brian for this example.)

What are the rules? Naturally, the only definitive answer can be given can be given by the HotSpot JIT.
That's not a very satifying answer, but it's true. The server JIT, like most compilers, has been taught hundreds and hundreds simplifying transformations that, in part, enable dead code elimination. Enumerating the criteria is a nearly impossible task.
But, your specific example is an interesting case.
int[] foo = new int[1000];
int bar = foo.length;For simplicity, I assume foo and bar are locals to a method, and in this case, the 6.0 HotSpot Server JIT will recognize that foo is unchanged before the initialization of bar, and effectively change it to:
int[] foo = new int[1000];
int bar = 1000;The JIT can't get rid of the allocation of the new array without a more advanced optimization called Escape Analysis, which attempts to determine the dynamic scope of objects. Of course, if these two lines comprise the whole method, then the analysis is fairly trivial.
Any intervening code will make the analysis more complex:
int[] foo = new int[1000];
baz(foo);
int bar = foo.length;
qux(foo);The calls sites will preclude your desired optimization, unless the called methods baz and qux can be inlined and analyzed. The code in baz can neither modify foo nor allow it to escape, and qux can not allow it to escape.
HotSpot's implementation of escape analysis is not quite yet complete, but should be available relatively soon.

Can i know what are the thumb rules of sap r/3

hi,
sap gurus,
good afternoon to all,
can i know what are the list of thumb rules of sap r/3.
plz
regards,
balaji.t
09990019711

Hi,
Please Follow link
http://www.dbis.ethz.ch/research/publications/19.pdf
Thanks,
Raja

What are Apple's Default Fan vs Temp Settings?

Where are Apple's published "Fan Speed and MPB Temp" settings?

Not only don't they publish them, they sometimes change the values in various updates so at one point you MBP may be running hot, you apply a patch and the now it runs cooler (or vice versa) as the fans kick in at a different temperature point.
Just get yourself smcfancontrol and you can set the fan speed to what ever you want. I keep my fans at 4,000rpms and that's usually enough to really keep the temps down. We're in a bit of a heat wave here in Boston and so my home office (not air conditioned) has been in the 90s so I've bumped up the speed to 6,000 because the ambiant temps have been so hight.

Remind me again.. What are the iTunes rules?

I have more than one iMac. Can I mirror my entire iTunes media onto both iMac's? I have more than one iPad. I can ONLY sync one iPad up with one iMac/iTunes system? Just what are those rules? And why?

Yes you can copy the entire iTunes Library to another iMac and Authorise that Computer. Then Use Home Sharing to keep them in sync.
You can sync upto 10 devices on an itunes. However it does not let you just switch from one computer to another.

My iphone is suddenly populated by random songs I've downloaded in the past. Why does this happen, and what are apple doing about fixing this?

Why does this happen?
What do other people do? (I can't go to sleep knowing there's a rogue album or song in my music. It's 2am now)
What do we tell apple so that they actually fix it. None of us want to pay £25 to have our own music.

I am on the monthly payment plan because nobody at BT has told me there is any alternative!
Each year there I have a long, in-depth conversation with the person who sets up the contract for the next year but the gist of the thing is 'I'm not going to be paying more than [x amount] per month, am I? Because I can't afford any more'' and each year the person says that no, in fact I should be paying less... and then without notice and even with the bill saying 'We will continue to take....' a totally different - and higher - sum disappears from my bank account.
Then I go through the painful process of writing to complain about this, get some sort of sum refunded and then the payments go through at the level they should, with me paying any additional (usually small) amounts for usage over the allowance. Until contract end when we start all over again...
Even if the amount they seem to randomly decide on is based on some sort of forecast, this should not be happening as I am doing what they instruct me to do on the bill to keep my payments the same.
So something is going wrong, on many levels.
At no point have I been offered the sort of 'monthly billing' described here; maybe there is some reason I am not allowed it. Unfortunately 'whole bill' direct debit payment is beyond me. I really need to know what I will be paying each month and I need BT to correctly take that amount, as agreed, each month, from the get-go.
It shouldn't be that hard really! Does anyone from BT read these forums? Can somebody take this on and finally get this straight, please?

What are apple's specifications for acceptable performance

I sent my ipod in for service because it's freezing up on me; on a daily basis... and all i get back is a letter telling me that my ipod is within apple's specifications for acceptable performance. In addition to telling me they've done everthing I've already done to try to resolve my problem. But for some stange reason they never stated what apple's specifications for acceptable performance are. Not to mention you can't find any information on thier website. Anybody know where I can find this information..

Welcome to Apple Discussions!
If the iPod is doing as you say, then it is not fine and Apple should repair it.
However, Apple may not have found something in the hardware that is wrong with the iPod.
Have you tried updating and restoring the iPod before?
iTunes
iPod Updater
Updating iPod's Software
To Restore...
Restore the iPod
If none of the above works, you may want to call Apple and explain what is wrong and what you have tried. Ask why it was not repaired...
Apple Phone Numbers
btabz

The podcats app is a huge backwards step, what are apple doing about it?

I made an account here specifically to bring up the problem that the new podcats app is unbelievably awful.
Just take a quick look at the constant stream of 1 star reviews on the app store and it should become obvious that something is badly wrong.
I spent quite some time yesterday browsing hundreds of reviews of the app and the overwhelming response is not only negative but there are countless requests insisting that it just goes back to the old itunes integrated method and that the idea of a seperate podcats app seems like a step backwards.
Do apple in any way aknowledge this app is a problem? Surely they look at what their customers are saying about it, but so far noting but minor fixes to the most serious of flaws have been addressed (eating through a month of data in 1 day etc) .
In my opinion this is a much bigger issue than the whole apple maps thing, or at least it would have been if I did not discover an excelent third party (paid) podcats app.
I am not going to list every problem here as I am sure most are well documented, but on an OS that prides its self on its intuitive design and ease of use, just how in the world did it ever seem like a good idea to require people to use 2 seperate apps in order to download a piece of audio... and don't even get me started on the desgn...
The maps issue to me was no big deal as I rarely used it but this whole mess of an app has lost my confidence in apple software.
Does anybody else here feel let down by this sorry piece of software?
Am I overdoing it? It just seems such a shoddy piece of work and way below my expectations.

Submit your feedback to Apple - http://www.apple.com/feedback/
This is just a user to user technical support forum, so a complaint post here is really falling on deaf ears (well, at least on ears that cannot do a thing about your issue).

Extending Cairngorm - What are the ground rules?

I was wondering what the rules are as far as extending your application's Cairngorm classes, or creating new design patterns between Caingorm pieces.
What is the recommended practice for addressing custom requirements with Cairngorm? What if I wanted to add an injector between the Model and the View, so that the view does not contain a singleton reference? What if I wanted to add listeners to the FrontController for logging, precondition testing, and other cross-cutting concerns?
At what point does it become "not recommended practice" for me to tinker with the framework of my Cairngorm application?
I've been trying to construct a list of definite no-no's in Cairngorm. This way, if we have to extend Cairngorm, we can do so while treading lightly, and embracing the principles of the framework, even when we can't follow the paved path exactly.
The following link is my work in progress. I'd like to hear suggestions and thoughts.
http://cairngorm.jottit.com/what_not_to_do

Hey Harry,
Although this question may be better suited for someone from AC to respond I will try to provide some direction.
I think the ground rules for adding extensions to Cairngorm are pretty simple in that anyone is free to add extensions to accommodate specific implementations of the Framework. However only those which gain wide spread community support and adoption, and more importantly, are general enough to support typical project architectures would/should be considered to get rolled into future releases.
IMHO the power of Cairngorm is in it's simplicity and lack of unnecessary complexity. It is tempting to add additional functionality and patterns such as IoC/DI and so forth however these types of implementations may not be general enough to be considered for widespread adoption.
Hope that helps.
Best,
Eric

The horrible looking iOS 7.0.2 look. What are apple playing at here?

What a nasty looking cheap skin apple has given us. I'm really disappointed in this. I really feel let down by apple now. I paid lots of money for my apples and end up with a cheap looking phone. Get rid of this nasty looking look. Darren

I, however, prefer the new look and would disagree with any attempts by Apple to change it back to the old skeuomorphic hash. Different strokes for different folks, and nothing pleases everyone.
Regards.

What are Apple up to Airport Utility 5.5

My April 1TB TC died and Apple kindly sent me a new one. It came in a brown box without any disk/powercord etc as it is a replacement part. It is a new type of TC (the dual band type). However to install it, it requires Airport Utility 5.5 which Apple does not have on its website. This was released in Oct 2009 and still there is no sign of it on the Apple site. Why would they do something like this?

I feel your pain. I've had the same issue. This is apparently an issue with Time Capsule replacements of new generation models for old gens. (you're right - no power cable, no box, no install software, just sent in a padded shipping container). They replaced my first generation (single band) with a new dual-band Time Capsule. I called them over two weeks ago. They don't offer AU 5.5 online, I can't pick it up from an Apple store. The best they said they could do is snail-mail a copy to me - they can't even expedite the shipping. They can FedEx the hardware to me and the new box got to me in 2 days but I'm dumbfounded that they can't do the same if they forgot to include the software. I still don't have it - called tonight and they said it could be another week. Mega-lame.
They explained that the reason they don't offer the download online is that 5.5 isn't compatible with older TC's and are worried that posting it would cause chaos. Shouldn't Airport Utility be universal across the spectrum of their wireless networking devices?

What are Apple's rules on refunding price difference ?

Similar Messages

Maybe you are looking for