Skip to Content
author's profile photo Former Member
Former Member

WAS 6.30 Installation on IBM

Posted on Sep 16, 2003 at 10:01 AM 13 Views

Hi,

Has anyone attempted to install on an IBM thinkpad t21? (256MB, 796Mhz)Â Â What were your results? acceptable, too slow?

Please let me know.

Thanks,

SAP NetWeaver Application Server Java
Add comment
10|10000 characters needed characters exceeded

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Oct 04, 2003 at 04:19 PM

    IBM no, but on quite similar configuration - on my SONY Vaio SRX51P/A (256MB, 800Mhz). It was fine, actually run very smooth after some manual tuning.

    But this is w/o the IDE.

    Greetings,

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 17, 2003 at 06:40 PM

    Mike,

    I tried it on the equivalent machine but it was way to slow for me...

    I ended up installing it on my home desktop (the 90 days trial) with 1GHz and 512 MB.

    Using NW Development Studio this still performs acceptable.

    It is however for sure not a processor problem ....

    Regards

    Thorsten

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member
      Sep 17, 2003 at 08:49 PM

      I installed the CD on my IBM t22 and had several issues.  I put it on my home machine and it works great (1gz/1gbram).

      JW

  • author's profile photo Former Member
    Former Member
    Posted on Oct 05, 2003 at 08:03 PM

    Hi Michael,

    the most important point is the available memory. I'm afraid, 256 MB are not enough to work efficiently, at least if you want to run the server AND the Developer Studio locally at the same time.

    Regards

    Stefan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member
      Oct 05, 2003 at 08:34 PM

      I am running at home on a 256mb 700mHz Sony Vaio, using server and IDE.  Although it runs slowly (and the installation takes about 3 hours), for my purposes it suits just fine - it sure beats driving 80 miles to my workplace desktop system!