J2SE 1.4 assertion facility

I'm trying to test drive the new assertion facility in J2SE 1.4 but can't get even a simple example to work:
public class Foo
     public void m1( int value )
          assert 0 <= value;
          System.out.println( "OK" );
     public static void main( String[] args )
          Foo foo = new Foo();
          System.out.print( "foo.m1( 1 ): " );
          foo.m1( 1 );
          System.out.print( "foo.m1( -1 ): " );
          foo.m1( -1 );
Code fails with the following error:
Foo.java:5: Invalid expression statement.
assert 0 <= value;
The compiler fails to recognize the 'assert' keyword - when I change code to:
boolean b = true;
assert b;
the error is:
Foo.java:7: Class assert not found.
assert b;
So, it thinks I'm defining a variable b of type assert rather than recognizing the keyword 'assert'!
I've doing all this in the new J2SE 1.4 - I do have other versions of the JDK on my machine, but am pretty sure I'm compiling against the right one - when I type 'java -version' on command line I get:
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
Anyone any ideas?
Thanks,
Alan

what bs. post-condition type assertions typically
"validate the internal state of the receiver".
pre-condition type assertains are typically used to
validate the state of arguments passed in.
Pre-condition type asserts define the "contract" a
caller must agree to prior to calling. It's very
simple, and very effective.No, you shouldn't use assertions to test pre-conditions. The pre-conditions should always be checked, not just in debug mode. Otherwise, the program could behave differently in debug and release modes, and that would be very undesirable!

Similar Messages

  • J2SE 1.4 Logging facility

    Hi,
    Can anyone provide me with links to examples of using J2SE 1.4's Logging API?
    Thanks,
    Amit
    [email protected]

    Hi,
    Here's a couple of classes:
    The first is simple logging facility I've written using the logging API (not a complete class - just the relevant method), the second is a generic error class to capture some consistent data across my application.
    Drop me an e-mail if you're still stuck.
    Regards
    Peter.
    public void logError(ClientError error)
    FileHandler fh = null;
    try
    String logDirectoryPath = System.getProperty("user.home")
    + "/Pisces/Log/";
    String filePath = logDirectoryPath + "Error_log.xml";
    File logDirectory = new File(logDirectoryPath);
    if (logDirectory.exists())
    File logFile = new File(filePath);
    else
    logDirectory.mkdir();
    fh = new FileHandler(filePath,true);
    errorLog.addHandler(fh);
    errorLog.logp(Level.SEVERE,
    error.getClassName(),
    error.getMethodName(),
    error.getStackTrace());
    catch (IOException e) { e.printStackTrace(System.out);}
    finally { fh.close(); }
    public class ClientError {
    private String className;
    private String methodName;
    private Date errorTime;
    private String errorMessage;
    private String stackTrace;
    public ClientError() { }
    public void setClassName(String className)
    this.className = className;
    public String getClassName()
    return className;
    public void setMethodName(String methodName)
    this.methodName = methodName;
    public String getMethodName()
    return methodName;
    /* In case we want to set the time where the error occurred. */
    public void setErrorTime(Date errorTime)
    this.errorTime = errorTime;
    /* Sets the date to the current time */
    public void setErrorTime()
    errorTime = new Date();
    public Date getErrorTime()
    return errorTime;
    public void setErrorMessage(String errorMessage)
    this.errorMessage = errorMessage;
    public String getErrorMessage()
    return errorMessage;
    public void setStackTrace(String stackTrace)
    this.stackTrace = stackTrace;
    public String getStackTrace()
    return stackTrace;

  • How to use assert with wireless toolkit?

    Hi,
    I am trying to find out how to use assert with wireless toolkit. I have found that I need to pass "-source 1.4" to the java compiler. But I can't find any documentation on how to do it.
    I'm using J2ME Wireless Toolkit 2.2.
    thanks
    Ludde

    Here's a quote from an article on Java World at http://www.javaworld.com/javaworld/jw-11-2001/jw-1109-assert.html
    "To support the new assertion facility in J2SE 1.4, the Java platform adds the keyword assert to the language, an AssertionError class, and a few additional methods to java.lang.ClassLoader."
    So I really think it's part of 1.4.

  • JUnit vs. assert

    I haven't used JUnit before, but I have been reading up on it. My question is why would I want to use JUnit instead of just using the assert facility available in 1.4?

    I haven't used JUnit before, but I have been reading
    up on it. My question is why would I want to use
    JUnit instead of just using the assert facility
    available in 1.4?You are comparing apples and oranges - they are not the same thing.
    Consider these three methods:
    void initResult()
    void computeResult()
    int getResult()
    How are you going to use the assertion facility to test that getResult() returns the correct result after initResult() and computeResult() are called?
    Consider this method:
    void setName(String name)
    How are you going to use JUnit in your final application to make sure that a null is not passed to setName()?

  • UIX and asserts

    Does anybody know about the interaction of asserts in the ViewController layer and UIX with JDev 10.1.2?
    I've coded an assert in a class and enabled the J2SE 1.4 Assertions option under project->project-properties->profiles->compiler. However when the assertion is violated, while the following code is correctly not executed, the UIX page doesn't report anything. Should it? At a broad guess I would have thought I'd see something reported in the UIX-page to say an assertion has failed.
    Even running with the -Djbo.debugoutput=console option on, no assertion is logged in the console.
    Regards,
    CM.

    UIX by default swallows exceptions and errors that may occur, for graceful handling. However when such situation occurs, the page rendered might be incomplete. If you want the application errors/exceptions to be propogated to the rendered output as an error message, you should use the <try> and <catch> elements wrapping such potential UIX code area.

  • Is there assert facilities in JAVA?

    I know there are assert facilities in c++ which are very useful for testing and debuging programms. Does Java has the similar things? If not, anyone has developed something like this?
    Thank you
    Shaomin

    Yes and no....
    There is a language built-in assert facility in JDK 1.4, but it's still in beta.
    If you need pre-1.4 java, you may use 3rd party classes, as pointed by mriffe.

  • Command line parameters to print to a file

    Hello
    is there a command line parameter for acrord32.exe to specify a filename to print to - just as if i ticked the box in the print dialog to print to a physical file?
    If not does anyone know how i can do that?
    Thanks
    Sean

    Asserts are disabled by default. Use the -ea switch to enable asserts or -da to explicitly disable them.
    You can find documentation about the assertion facility at http://java.sun.com/j2se/1.4/docs/guide/lang/assert.html
    Remember, the Java Docs http://java.sun.com/sun/ are your friend!

  • Special directives for javac

    Hi. Lately I been coding back in C/C++ and there is a little thing i miss in java. Directives like #error or #warning. I use them to mark code I know it's working and a little descriptive message.
    Also things like #ifdef, etc. Is there anything similar in java?

    Since 1.4 there is the assertion facility.
    http://java.sun.com/j2se/1.4.2/docs/guide/lang/assert.html
    You can use your favourite precompiler to preprocess Java source too.
    posman@linux:~/ivan> cat xx.c
    public class xx {
            private final static String when = __DATE__ ;
            public static void main(String args[]) {
                    System.out.println(when);

    posman@linux:~/ivan> gcc -E -P xx.c >xx.java
    posman@linux:~/ivan> javac xx.java
    posman@linux:~/ivan> java xx
    Jun  7 2005

  • Where is the "Profile" section in Project Property window?

    Hi, first time use this Oracle JDeveloper. From the tutorial it seems that inside the Project Property window, the left pane, you have the "Common" section and "Profile" section. Inside "Profile" section it's the "Development", then under Development you have "Paths" "CodeCoach" "Compiler", etc.
    My problem is, in that left pane, I only see a "Common" section, I don't even have something called "Profile". This makes it impossible for me to set the class path, because according to the tutorial, I need to change something under "Development" which is under the "Profile".
    Any advice welcomed! Thanks!

    Hello all,
    I'm trying to use ADF Faces. According to the document, http://www.oracle.com/technology/products/jdev/htdocs/partners/addins/exchange/jsf/doc/faq.html, section 3.5:
    "You need to enable J2SE 1.4 Assertions. In jdev this can be done in project properties (Select Tools -> Project Properties -> Profiles -> Development -> Compiler -> Enable J2SE 1.4 Assertions.)"
    I'm using JDeveloper 10.1.3.34.12 on Mac OS X, java version 1.5.0_02-56. How do I enable J2SE1.4 Assertions?
    Thanks,
    -Anthony

  • Error on compile but no errors in source code code??

    Error(284,33): illegal forward reference in the CharacterDataLatin1.java which is not part of my project.

    I had the same error and caught it out. The cause is not into the code.
    Application: Oracle JDeveloper 10g on Fedora Core Linux 4
    Versions: 10.1.2, build 1811 (Jan 2005) and the new 10.1.2.1, build 1913 (Aug 2005)
    ERROR DESCRIPTION (BOTH BUILDS 1811 AND 1913):
    Compiler Messages:
    /usr/java/j2sdk1.4.2_04ojvm/src.zip!/java/lang/CharacterDataLatin1.java
    Error(284,33): illegal forward reference
    /usr/java/j2sdk1.4.2_04ojvm/src.zip!/java/lang/CharacterData.java
    Error(956,33): illegal forward reference
    /usr/java/j2sdk1.4.2_04ojvm/src.zip!/javax/swing/JFrame.java
    Warning(406,23): method setMenuBar(javax.swing.JMenuBar) in class javax.swing.JRootPane has been deprecated
    Warning(416,30): method getMenuBar() in class javax.swing.JRootPane has been deprecated
    /usr/java/j2sdk1.4.2_04ojvm/src.zip!/java/util/Locale.java
    Warning(25,1): import java.io.* partially used, should be replaced by
    import java.io.ObjectOutputStream;
    import java.io.IOException;
    import java.io.ObjectInputStream;
    import java.io.Serializable;
    etc.
    Compilation complete: 2 errors, 372 warnings.
    ERROR DURING THE FIRST START OF THE BUILD 1913:
    An error ocurred while opening jar:file: /usr/java/j2sdk1.4.2_04ojvm/src.zip!/org/apache/xpath/objects/XString.java
    Details:
    Exception Stack Trace:
    sun.io.MalformedInputException
    at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:149)
    at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:247)
    at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:297)
    at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:182)
    at java.io.InputStreamReader.read(InputStreamReader.java:167)
    at oracle.javatools.buffer.UnsynchronizedReader.fillBuffer(UnsynchronizedReader.java:162)
    at oracle.javatools.buffer.UnsynchronizedReader.read(UnsynchronizedReader.java:85)
    at oracle.javatools.buffer.AbstractTextBuffer.normalizeEOL(AbstractTextBuffer.java:1477)
    at oracle.javatools.buffer.AbstractTextBuffer.read(AbstractTextBuffer.java:1301)
    at oracle.ide.model.TextNode$TextBufferWrapper.read(TextNode.java:1111)
    at oracle.ide.model.TextNode.loadURLContentIntoBuffer(TextNode.java:923)
    at oracle.ide.model.TextNode.reloadTextBuffer(TextNode.java:393)
    at oracle.ide.model.TextNode.reloadNode(TextNode.java:377)
    at oracle.ide.model.TextNode.open(TextNode.java:223)
    at oracle.jdevimpl.jotimpl.src.SrcFile.getNode(SrcFile.java:1756)
    at oracle.jdevimpl.jotimpl.src.SrcFile.init(SrcFile.java:170)
    at oracle.jdevimpl.jotimpl.src.SrcFile.<init>(SrcFile.java:150)
    at oracle.jdevimpl.jotimpl.src.SrcFile.createFile(SrcFile.java:127)
    at oracle.jdevimpl.jotimpl.internal.database.DatabaseFragment.createFile(DatabaseFragment.java:526)
    at oracle.jdevimpl.jotimpl.internal.database.ClassDatabase.getFile(ClassDatabase.java:724)
    at oracle.jdevimpl.jotimpl.JotWorkAreaImpl.getFile(JotWorkAreaImpl.java:738)
    at oracle.jdevimpl.jotimpl.addin.CacheFactory.buildData(CacheFactory.java:336)
    at oracle.jdevimpl.jotimpl.addin.CacheFactory.buildParseData(CacheFactory.java:378)
    at oracle.jdevimpl.jotimpl.addin.CacheFactory.create(CacheFactory.java:108)
    at oracle.jdevimpl.jotimpl.addin.JotRunnable.buildLibrary(JotRunnable.java:608)
    at oracle.jdevimpl.jotimpl.addin.JotRunnable.loadLibrary(JotRunnable.java:124)
    at oracle.jdevimpl.jotimpl.addin.JotRunnable.run(JotRunnable.java:64)
    at oracle.jdevimpl.jotimpl.addin.JotCacheThread.run(JotCacheThread.java:57)
    CAUSE:
    The Project Properties. Menu: Tools >> Project Properties >> Profiles >> Development >> Compiler.
    Uncheck "Update Imports" and that's all. Character Encoding: UTF8. For the target JDK 1.4 it's necessary to "Enable J2SE 1.4 Assertions". The "Self-Deprecation Warnings" produces an excessive amount of deprecation warnings. The OJVM' Patch is recommended (see <jdeveloper_install_directory>/jdev/install.html and readme.html).
    Of course, if this is the case.
    null

  • Encrypt / Decrypt in J2SE 1.3.1

    Hi,
    I need to encrypt / decrypt a string.
    For this, i use JCE (J2SE 1.4) (Cipher class)
    The problem it's, i have to use J2SE 1.3.1.
    I am looking for some class i can use for encrypt and decrypt a string.
    Do you know what class can i use for my goal ???
    Thanks so much ...
    Omar

    J2SE is Java 2 Standard Edition
    JRE is Java Runtime Environment (that is what the client has)
    JDK is Java Development Environment (it includes JRE plus the development tools)
    If you have J2SE 1.4 and need to make sure that your
    program will run with J2SE 1.3.1, you need to add the
    option "-target 1.3" to the compile command on the
    command line:
    #javac -target 1.3 MyClass.java
    This makes sure that the class file is compatible with
    J2SE 1.3. If your program uses the JCE, you need to
    make sure that the end user has the JCE installed,
    because it is not automatically included with J2SE
    1.3. This is not correct. "-target" option tells compiller to use features specific for the concrete targets. And the default target for javac from 1.4 actually "1.2" (it was "1.1" in 1.3 and befofe). This is from javac changes documentation from JSDK 1.4
    The javac byte-code compiler has a new -source option that enables support for compiling source code containing assertions. Also, default compilation is for -target 1.2. Previously, the default was 1.1. The compiler now correctly detects unreachable empty statements, as discussed in bug 4083890. Javac also recognizes the new -Xswitchcheck option that checks switch blocks for fall-through cases and provides a warning message for any that are found.
    So, to make shure if your app going to work on 1.3 you no need to recompile it but you have to run it in 1.3 JRE and see if it work or not. Because JCE (Java Cryptography Extention) wasn't included into JRE 1.3 you have to install it in there. I recommend to use BouncyCastle or Sun's reference implementation.
    Use the Cipher class, if your end user has the JCE
    installed, it will work all fine.
    If you wanted to you could also use BouncyCastle
    instead of JCE, but it is not necessary.BouncyCastle is cleanroom JCE implementation and JCE provider! It have much more algorithms implemented and they are faster comparing with Sun's JCE provider.

  • Assert error!! how to solve that problem?

    Hi,
    when i use an assert after the compilation , the error is:
    C:\CLASSES>javac Assertion.java
    Assertion.java:11: as of release 1.4, 'assert' is a keyword, and may not be used as an identifier
    (try -source 1.3 or lower to use 'assert' as an identifier)
    public static void assert(boolean expression, String why) {
    ^
    1 error
    The tutorial says: In order for Code Sample 1(Doesn't matter) to compile, use -source 1.3 because assert is a keyword as of J2SE 1.4.
    what is the source 1.3 ?? where and what the hell is that?? LOL =))
    thanks!

    i understand and i don't understand.
    lol
    thats possible for someone who is using xemacs but someone who is using Eclipse or JCreator how do i do that?
    if u don't want to answer that question could u put an assertion in this code, for example : asser -> if the num < = 0 !
    here is the code:
    import java.io.*;
    public class Capicua {
         public static void main (String[] args) throws Exception {
              int digit, num;
              int inverted = 0;
              int x;     
                   BufferedReader br = new BufferedReader(new InputStreamReader(System.in));
                   System.out.print(" Insert number: ");
                   num=Integer.parseInt(br.readLine().trim());
                   Assertion.assert(num <= 0, "Number can't be shorter or equals to zero!"); <--- how do i put an assert here? ( with the "do - while" its easy, but and with the asserts?
                   x=num;
                   while(num > 0) {
                   digit = num % 10;
                   num = num /10;
                   inverted = inverted * 10 + digit;
                   System.out.println("inverted = " + inverted);
                        if(inverted == x) {
                             System.out.println("Capicua");
                        }else{
                             System.out.println("not a capicau");
    }

  • Using assert or exception?

    I have been struggling with the methodology of using assertions for some time
    now and would like to have an objective viewpoint. It primarily has to
    do with the use of assertions for pre-conditions.
    Let's say we have some class, for demonstration purpose only, as this one:
    public class MyClass {
        private final String str;
        public MyClass(String str)
            this.str = str;
        private int getLength(String x, String y)
            return x.length() + y.length();
        public int getTotalLength(String x)
            return  getLength(str, x);
    }Let's say I want to make sure that the classes methods and constructor is not
    called with any null parameter. Of course I will get a NullPointerException
    eventually automatically anyway, but let's say I want to know as soon
    as possible to something is wrong. Or maybe I am dealing with a complicated
    class in which it is not so clear yet.
    Anyway the Sun Java documentation says the following:
    http://java.sun.com/j2se/1.4.2/docs/guide/lang/assert.html#preconditions
    "Do not use assertions to check the parameters of a public method."
    Instead it should throw some particular exception. In this case a
    NullPointerException in the MyClass constructor if the str parameter is
    null. Conventation say that assertion can be used for private methods
    however, such as the getLength method.
    I always try to keep my classes relatively small. So often I feel no desire
    to include assertions in private methods to check parameters if I can
    already see that the parameters are checked in the public methods.
    So in this case why add assertions in getLength if I can already clearly
    see that the parameters have been checked in the MyClass constructor and
    the getTotalLength method?
    Maybe I am wrong, but I am afraid that using such rigurous parameter testing
    in every public method might influence performance too much, because in
    contrary of assertions these normal checks are done always. I cannot
    remove these normal checks, because that would mean it could trigger
    an assertion in one of the private methods, and I could as well move
    the assertions from the private to the public methods.
    What I don't feel comfortable about is this big distinction between
    assertions and run-time exceptions. Why not use assertions in
    public methods for parameter testing? They are just exceptions
    too anyway. And they have the benefit of not impacting performance
    for production environments.
    There is an article about challenging the Sun Assert convention here.
    http://www.javaworld.com/javaworld/jw-12-2001/jw-1214-assert-p2.html
    I would like you to read it and give your objective opinion. Weighing
    the positive and negative implications of it and tell me what you
    think and why.

    I don't have the time to read that article. IMO
    assertions are to be used to validate the state of
    your instance and its internal works.So you do not think that assertions should be used for any pre-conditions of parameters?
    They are not
    exceptions, by the way. Failure will result in an
    AssertionError.Yes, I should have said errors or throwables.
    It's quite overkill IMO to use those for the
    validation of parameters provided by someone else.Why? Isn't it overkill to impact the performance by
    using run-time exceptions instead of assertions?
    If
    your API declares the legit value range of an
    argument, a NullPointerException for null and an
    IllegalArgumentException for values outside bounds,
    that gives me more flexibility to react and handle
    error states (it could be user input - null would
    mean there's a bug, out of bounds would mean I have
    to ask the user again) than merely firing of a "big"
    assertion error.But the whole idea of pre-conditions is that the method never must be called with invalid values. Your example might make sense for some class close to the front-end, but most classes are deep inside everything and have no idea what to do with a NullPointerException or IllegalArgumentException at that point. I would let a facade near the front-end deal with invalid user input and explicitly prevent the invalid input progress deeper inside my code.
    The article I linked goed deeper in about why it is a good idea to give a "big" assertion error at that point.
    There's probably no hard or objective rule when you
    should use what anyway, otherwise, there wouldn't be
    different opinions in this matter. If you're looking
    for one, you'll most likely not find it.I have certain ideas about assertions and I would like to know if these ideas are reasonable. Especially because they go against the Sun convention and I usually am a follower of standards.

  • How to use assert about jdk1.4

    I write a Test java file to test the assert statement but fail to compile.
    public class Test{
    public static void main(String args[]){
    int i = new Integer(args[0]).intValue();
    assert true;
    if(i%3==0){
    System.out.println("good");
    }else if(i%3==1){
    System.out.println("better");
    }else{
    System.out.println("best");
    What's the problem, and how to fix it?
    Thanks!

    you need to tell pass the compiler the -source 1.4 flag to get it
    compile a class with assert.
    see here
    http://java.sun.com/j2se/1.4.1/docs/guide/lang/assert.html#compiling

  • CJS-00081  Assertion failed: in function InstallationScript_212()

    Hi,
    I am trying to install WAS6.4 Sneak-Preview on win2k sp4 (Terminal), J2SE1.4.2_05 and every fresh installation is failing in the "MaxDB Database Installtion" phase with the following error message.
    ERROR 2005-06-13 19:45:56
    CJS-00081  Assertion failed: in function InstallationScript_212() {    var installer = new Installer();    var kdb = new KeyDB();    var context = new Context();    var gui = new Gui();
    Any pointers related to this type of failures would be of GREAT!! Help..
    Thanks in Advance
    Atul

    Thanks for the response sai..
    i managed to resolved this particular issue (it was because one of the NT service was not running)
    However now the Installtion is hanging at one particular point "MaxDB Database Installation" (phase 5) the last few lines in the "sapinst.log" file are as follows:
    installation of MaxDB Webtools finished successfully We, Jun 15, 2005 at 201841
    INFO 2005-06-15 201844
    The service 'XServer' started successfully on host 'Local'.
    INFO 2005-06-15 201852
    The service 'SAPDBWWW' started successfully on host 'Local'.
    INFO 2005-06-15 201859
    Working directory changed to Csapdbprogramspgm.
    INFO 2005-06-15 201859
    Working directory changed to CProgram Filessapinst_instdirNW04SR1WEBAS_JAVACENTRALONE_HOST.
    INFO 2005-06-15 201902
    Working directory changed to Csapdbprogramspgm.
    INFO 2005-06-15 201902
    Working directory changed to CProgram Filessapinst_instdirNW04SR1WEBAS_JAVACENTRALONE_HOST.
    installation of MaxDB Webtools finished successfully We, Jun 15, 2005 at 20:18:41
    INFO 2005-06-15 20:18:44
    The service 'XServer' started successfully on host 'Local'.
    INFO 2005-06-15 20:18:52
    The service 'SAPDBWWW' started successfully on host 'Local'.
    INFO 2005-06-15 20:18:59
    Working directory changed to C:/sapdb/programs/pgm.
    INFO 2005-06-15 20:18:59
    Working directory changed to C:/Program Files/sapinst_instdir/NW04SR1/WEBAS_JAVA/CENTRAL/ONE_HOST.
    INFO 2005-06-15 20:19:02
    Working directory changed to C:/sapdb/programs/pgm.
    INFO 2005-06-15 20:19:02
    Working directory changed to C:/Program Files/sapinst_instdir/NW04SR1/WEBAS_JAVA/CENTRAL/ONE_HOST.
    My current System Configuration is as follows:
    - MS Windows Server 2003 (Enterprise Edition)
    - RAM 1 GB
    - Pentium 4 2.4 Ghz processor
    - 1.4.2_05 J2SE
    And i have used both the Installation currently available on SDN site viz.
    a)SAPinst_SP_WAS640.exe
    b)WebAS640SP9.zip
    I have also tried on m/c having Windows 2000 SP4 OS with 2GB of RAM without any success.
    I even tried options such as "cancelling" the Installation and resuming it later without any success.
    Though the installtion is hanging for MaxDB however it was succefull when tried with MS SQL-Server2000.
    Can somebody provide any pointers in resolving this issue?
    Thanks in advance..
    Atul

Maybe you are looking for

  • Exchange rate expression Direct and Indirect qutation

    Hello, Please can you explain whether there are any issues or risks in switching the Exchange Rate Types used in SAP to allow inverted rates to be used - or any reasons why it was designed not to have inverted rates switched on. I think to reduce the

  • Cover flow all wrong

    Hi there, I've just bought an ipod Classic 120gb and everything's fine aside from having 40 odd albums at the end of the cover flow completely out of alphabetical order. Some are compilations but most aren't and nothing that I've read on this problem

  • Error in importing technology in topology by local agent

    Hi , I am trying to import technology using following command Startcmd OdiImportObject -WORK_REP_NAME=<<Work repo name>> -IMPORT_MODE=SYNONYM_INSERT -FILE_NAME=<<TECH_Informix.xml>> Note: localAgent is in running mode. But i am getting error like : [

  • Safari 4 Won't Start At All

    Help! I was having the same problem as many others with Safari randomly shutting down. I thought I'd remedy the problem by downloading the Safari 4 beta. Now it's worse. Instead of randomly stopping, Safari won't open at all. I got one message that s

  • Internal Error from CyberTan in LR4

    Hi, just out of the blue I opened LR and got this message.  I have to shutdown or Force Quit LR on my mac to shut down LR.  This is horrible!  I have SM plugin and used it yesterday.  Don't remember if I quit LR and restarted yesterday, but the probl