[hatari-devel] [hatari-tracking] [hatari - Help] Can't install Amberstar

[Eero Tamminen]

Hi,

I looked into an issue reported on the forums.

On Monday 27 September 2010, admin at berlios.de wrote:
> Read and respond to this message at:
> http://developer.berlios.de/forum/message.php?msg_id=52007
> By: paar
>
> Hi. I tried to install Amberstar (source:
> http://thalion.exotica.org.uk/games/amberstar/credits/credits.html), but
> had no luck.
> I can go to install screen, choose HDD install (through image you
> provided on your website)

I.e: http://hatari.berlios.de/hd80mb.image.gz

> but when first disk is finished, it keeps 
> asking for second disk, even it's at floppy drive.

This works fine for me with TOS 1.4.  But I can reproduce the issue
with EmuTOS.

Program just does fsfirst() GEMDOS call and then asks again for the original
disk A instead of B, the next disk.  I wonder whether EmuTOS fsfirst() is
returning a different file name than what it expected, or returning it in
different (lower?) case?

If somebody wants to debug it, you can catch the fsfirst() in debugger with:
	b GemdosOpcode = $4e


> I managed to install it once (with trouble), but couldn't play it, game
> said something is missing.
> GEMDOS install is not possible, appearently it cannot write to such HDD.

It does only GEMDOS dfree() (and wouldn't seem to be calling any other
extra OS bios/xbios/gemdos calls) and claims a read error.

I looked into Hatari GEMDOS emulation Dfree() implementation and it just
returns a hard coded file system size (10MB free on 50MB file system having
512 byte sectors with each cluster containing one sector).  I tried changing
this a little, but that didn't help anything.

On quick look into Atari docs, what gemdos.c does seemed fine.

Any idea what could be wrong?

(Dfree GEMDOS opcode is $36, in case somebody wants to catch it with
Hatari debugger :-))


> Disks with game are alright, at least it seems that way because install
> to other floppy disks works. Any advice? :(


	- Eero