|Re: [hatari-devel] HDDriver issues with WinUAE CPU core (and with EmuTOS)|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] HDDriver issues with WinUAE CPU core (and with EmuTOS)
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Mon, 12 Jan 2015 08:13:57 +0100
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1421046837; l=2991; s=domk; d=seimet.de; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Subject:To:From:Date; bh=Xn6FaSpeTy2gX6VZdPsNH2iHstg=; b=HOzk62OCKhK14t68pg0nAl3ts/6MTGHsgeJVpR/2rljGpXR+XJM6He43TsF9P5peQkM wVV07Fr10MQq0oOf2HgPJSNfmPtkWiaiEeBbylNnzShdyEO+yVNSwxIQaT8txDHJqbcUd YRvhGcfHWKr21l/J4bIXvWgG6sbYgseTC94=
Just start HDDRUTIL, then go to "Devices and Partitions", select the
HDDRIVER file you want to configure and switch on/off the devices you
are interested in.
Since SCSI/DMA is not supported by Hatari it might probably be better if
there was a bus error when accessing these addresses. At least Hatari
should behave like it behaves when you access these addresses in
> On lauantai 10 tammikuu 2015, Uwe Seimet wrote:
> > I will send you the full version 9.04 of HDDRIVER in a separate email,
> Btw. How do I disable SCSI scanning from HDDRIVER?
> It (still) takes ages with Hatari...
> > even though I don't think that it will behave differently from the demo
> > of 9.02. Maybe you can verify that there is a problem only when
> > *booting* from IDE, not when starting HDDRIVER later, e.g. from the AUTO
> > folder of a GEMDOS drive or manually.
> > I will check whether I also observe problems when booting from a disk
> > image later. But:
> > > With Old UAE CPU core it is recognized:
> > This means the actual problem is a Hatari regression, isn't it?
> Yes, ST one.
> (see my previous separate mail about WinUAE CPU core ST compatibility)
> > > That text is from ~5 years ago, from EmuTOS 0.8.x and
> > > older HD driver (and worse Hatari ACSI/IDE emulation).
> > > Unfortunately I don't anymore remember what problems
> > > there were.
> > >
> > > As to now... E.g. doing above IDE and ACSI tests results in:
> > > - HD DRIVER not being executed from ACSI image at boot
> > You mean IDE here, not ACSI, don't you?
> ACSI. EmuTOS doesn't execute the HD driver even from ACSI.
> Maybe because it is somewhat able to interpret the boot sector
> and partition table, so it thinks that it doesn't need the driver.
> I'll raise this on the EmuTOS mailing list.
> > > - EmuTOS seeing image contents regardless of that
> > > - double clicking on anything on the image, either immediately
> > >
> > > or after running hddriver.prg from floppy image,
> > > just giving error.
> > >
> > > > On first sight I did not find any problems, using EmuTOS 0.9.3.
> > >
> > > How did you use EmuTOS with HD driver?
> > I simply replaced my TOS 3.06 image file with the EmuTOS 0.9.3 image
> > file and enabled 24 bits addressing. (32 bit addressing does not seem to
> > work with EmuTOS.) The rest of my configuration remained unchanged. Then
> > I simply started Hatari and HDDRIVER correctly reports both IDE drives
> > and I can access them. HDDRUTIL also works, which means that HDDRIVER is
> > fully active as the SCSI Driver features are available.
> > Like before I started HDDRIVER.PRG from the AUTO folder of my GEMDOS boot
> > drive C.
> Ok, this works fine.
> I've commited a quick update to Hatari Manual:
> - Eero