Re: [MiNT] Potential bug on mouse wheel

[Peter Slegg <p.slegg@scubadivers.co.uk>]

On Sat, 19 Dec 2009 22:13:28 , Vincent Rivière <vincent.riviere@freesbee.fr> wrote:
> Helmut Karlowski wrote:
> > But I know only very few users that are bold enough to let my XaAES on
> > their computers, and even fewer that report bugs, so this can last ..
>
> The problem is really the setup process...
> As Atari users, we have been accustomed to unzip an archive somewhere our
>
> hard disk (or floppy), then run the software immediately.
> Running Linux software is a headache without a package manager.
> And for XaAES it is even worse: it must be compatible with the kernel, th
> ere
> is the risk to make the system unbootable, etc...
>
> If there is a detailed install procedure for the binaries (I mean
> documentation), as well as a recovery procedure if something goes wrong,
> everyone will try he binary, and I hope, give feedback.
>
> I believe it could be as simple as replacing xaaes.km if the versions are
>
> close enough...

I just installed it.

I have a c:\MINT\1-17-CUR folder that I do not use because of the bugs in
1.17 so I was happy to overwrite it.

bzip2 -d 20091216-freemint.tar.bz2
tar -xvf 20091216-freemint.tar

then used strip on the mint*.prg files as well as
strip * on the contents of the xaaes xif and xdd
folders.

Copied all the relevant xdd, xif and xaaes files into
the right places in C:\MINT\1-17-CUR

I didn't copy the filesystem xfs.

In the C:\1-16-CUR\AUTO folder I keep a copy of MINTMIL.PRG
so I can over-write the one in C:\AUTO and recover easily
from TOS if I have to.

I then put the new mintmil.prg into C:\AUTO and rebooted.
By over-writing the existing file, the boot order stays
the same.

It still has the floppy/syslogd bug and the modal dialogue
jamming bug.

Peter