| Re: [hatari-devel] Re: RAM detection issue with VDI (was HDDriver issues with WinUAE CPU core) |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Re: RAM detection issue with VDI (was HDDriver issues with WinUAE CPU core)
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Wed, 14 Jan 2015 21:02:20 +0100
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1421265741; l=691; s=domk; d=seimet.de; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Subject:To:From:Date; bh=QpY0qOy1ikJbwu6X9fLk1ZoGhNk=; b=ThaRvmzI7BKg5UtteBeXVaRNTYWmJN3s86nm+JRg0IrLZzaCNYyhDBOC/IgiJtAgMLK UWtbsHkIcf0tKaaHKQnUSVLhDZIYlC3+j6UFLzu8eSRVk0Fy3mU6z2MO+yyJZ694lX/Km xBHJKtQjeKMLimpqgRUECTVhHb/NJpGBBIA=
Hi,
> On tiistai 13 tammikuu 2015, Uwe Seimet wrote:
> > > > > --vdi-width 800 --vdi-height 600 --vdi-planes 4
> > > > > --vdi-width 1920 --vdi-height 1080 --vdi-planes 1
> > > >
> > > > With the first resolution NVDI hangs after displaying its startup
> > > > message, with the second resolution it work.
>
> Was this with WinUAE CPU core or old UAE CPU core?
>
> If former, could you check also old UAE CPU core, just in case
> (before updating Hatari sources)?
This was with the WinUAE core. With the old core the behavior is the
same as with Hatari 1.8.0 and the new core: Pixel garbage with the first
resolution, the second resolution works fine.
Take care
Uwe