From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Dibse-00086S-QU
	for qemu-devel@nongnu.org; Wed, 15 Jun 2005 13:40:49 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DibsU-0007za-UZ
	for qemu-devel@nongnu.org; Wed, 15 Jun 2005 13:40:40 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DibsT-0007xs-Vu
	for qemu-devel@nongnu.org; Wed, 15 Jun 2005 13:40:38 -0400
Received: from [194.251.242.244] (helo=fep19.inet.fi)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1DibpZ-00050n-VE
	for qemu-devel@nongnu.org; Wed, 15 Jun 2005 13:37:38 -0400
Received: from co.inet.fi ([80.220.124.133]) by fep19.inet.fi with ESMTP
	id <20050615173600.YGST1914.fep19.inet.fi@co.inet.fi>
	for <qemu-devel@nongnu.org>; Wed, 15 Jun 2005 20:36:00 +0300
Message-ID: <42B06701.1080603@co.inet.fi>
Date: Wed, 15 Jun 2005 20:36:01 +0300
From: Tero Kaarlela <turo.kaarlela@co.inet.fi>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] OS/2 Bootloader Some weird behaviour of
	branch	instruct
References: <20050615163620.29335.qmail@web90204.mail.scd.yahoo.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

ecs user wrote:

>>Tero Kaarlela wrote:
>>Could this be because OS/2 can't handle this much
>>ram(128mb).
>>    
>>
> 
>eComStation can do at least 2GB and with updates 4GB
>OS/2 Warp4 should be able to handle 256MB
>

  Well I was talking about OS/2 PowerPC edition (Released december 1995)
   During that time Warp V3 could handle 64mb maximum. This was 
mentioned somewhere in my earlier post.

>  
>
>>OS/2 has always been very specific about maximum
>>memory(ie. versions 1.x can't boot on machines
>>that report more than 16mb ram. this is one of the
>>reasons 1.x versions dont boot under Qemu and
>>thats why many BIOSES have option "boot to OS/2). 
>>    
>>
> 
>Don't use those motherboard BIOS settings with
>eComStation or OS/2 Warp4. Leave the BIOS setting at
>default - "OS/2 use greater than 64MB = No"
>
>  
>
Yes I knew this already(This option is for 1.x OS/2)


Tero