AmiUpdate?

@tldaley

What are your tooltypes? I was having the same problem until I changed mine.

i update to the latest version on pegasos and it runs fine. i will try it on sam tommorow.

@tldaley

Same DSI here, only where scanning for new updates ...

@samo79

Check the main icon, 1.119 had an erronous icon in the archive which overwrote your normal one.

Simon

@Rigo

Ok l'll look into it when I turn in front of my Amiga, but how about releasing also 1.120 as "standard" .lha ?

Thanks

@Rigo

Quote:

Hi,

Ok that seems to be the problem. (thanks everyone for the icon suggestions)

My icon tooltypes don?t exsist.

Now I have been trying to make life easy and find the AmiUpdate archive (which I haven?t found) and cut-n-past the tool types across. Can someone point out what tooltypes I need and I?ll have to do it the hard way.

Many thanks,
Trev Daley.

@tldaley

For you sir, everything

Quote:

@Raziel

Quote:

Many thanks, that did the job. Why is it always the simplist things that are always the hardest to find. I would never had thought of checking the tooltypes!

Back to having a stress free day.

Ciao,
Trev Daley.

@Rigo

Since some days i get the same update notification about Ranger

I have 1.44 installed, problem is the version in the package says it's from 2009, the package information itself (AmiUpdate) says it's from 2010.

Maybe i'm at the wrong address, but what can i do to turn it off?

@Raziel

OK, the problem lies with the application owner. There is two reasons for this, especially in this situation:

Firstly, the application owner is the one that submits the data to the AmiUpdate database, and it is these details you see when you hit "scan". At this point, AmiUpdate has had nothing to do with this update apart from authorising its addition into the database, which in the case of known apps, is virtually automatic.

Secondly, the application owner, in this instance, made a mistake with the version string, and didn't bump the year section. Because the owner submitted a date of 15-2-2010 into the database but left the version string in the binary of 15-2-2009, AmiUpdate believes an update is always applicable.

In future, I suggest you mail the application owner directly as it is them that submits the data. Posting on forums is likely to get missed, you was lucky it was spotted this time, as not everyone reads the forums, and those that do, some are getting fed up with the constant BS in some of them.

Simon

@Raziel

Mr Raziel, Steven puts his email address in the Ranger documentation for a very good reason, to report bugs.

/me clubs Raxiel for ssolie...

Well , he knows now, but the point about emailing him bugs stands.

Version 1.45 uploaded.

@Rigo

Sorry about that.
There were two possible destinations to send this report to and i hit the wrong one

@sundown

Understood.
I will read and act more carefully in future

@Raziel

Was mean't to be a light hearted post, but you can see how fast Steve fixes bugs when reported to him, he doesn't search the forums for bugs in his programs. He's too busy coding OS5 on the X1000

@Rigo

Would it be possible to avoid that DSI in AmiUpdate completely with a check that if no tooltypes are found it defaults to some presets?

I know the tooltypes are "amiga-way" of doing small settings but I usually use xml-files.

@flow

Yes, of course, and as far as I was aware it was all working fine. The problem only surfaced when the tooltypes were destroyed. That particular section of code is as old as it gets, and was working fine when it was written, and never presented problems before.

Such is life...

Simon

@tonyw

Quote:

The problem with that is that the updates are not released as nice small easy to download updates but usually as an entire OS install CD.

For those of us that have slow connections updating as and when you need via AmiUpdate is far better than having to download some huge behemoth taking over an hour each time - especially if it is like the OS4.1 update 1 and you find the file is corrupted.

The more that can be done in small stages using something liek AmiUpdate the better.

I do hope the SDK can be done that way. Last time I had to download a huge file taking ages and most of the files in it were identical to the ones I already had.

We have a good update system here and it could be used a lot more.