Hi guys i just updated my amiupdate to the last new version, as sson its installed and did a soft reboot, Amiupdate crashes.

the first time installed i got a requester for a assigns?

i did assign it to my amigaos partition, but when i launch it it crashes.

anyone else got this?

@klapdeur

I got a GrimReaper. It seems that Amiupdate is now launched from the Workbench Startup. I deactivated it and now it works fine.

I don't know why, maybe a conflict with the latest AOS4 update.

Nic

_________________
RedOneX (SAM 460ex) and an A1 which now rests quite.
Amiga OS 4.1.6 and CinemaWare games.
Classic and NG softwares.

@unimon
how did you diable it?

ive rolled back to the earlier version now.

I seem to remember someone having this problem and fixing it by changing the way AmiUpdate starts. It was something like he'd set it to start iconified on the Workbench, and when he changed it to start as a docky it worked.

Something like that.

@klapdeur

The crash is with the new version 2.25 of AmiUpdate. I've submitted a bug report to the AmiUpdate bug tracker along with a crash log so hopefully it will be looked into and fixed.

@klapdeur

The fastest way is using the context menu. Click with RMB somewhere on the workbench. In "Prefs" you will find "Workbench Startup". Chose it and a window will open with all launched tools/softs. Click on "Amiupdate" (probably the last one) and on the right of the window, chose "disable". I'm not sure about the text because I use WB in French.

Nic

_________________
RedOneX (SAM 460ex) and an A1 which now rests quite.
Amiga OS 4.1.6 and CinemaWare games.
Classic and NG softwares.

@salass00

Quote:

The crash is with the new version 2.25 of AmiUpdate.

Yes, there have already been a couple of updates to AmiUpdate itself since OS 4.1 update 6 was released. First I got AmiUpdate 2.24, then a couple days later AmiUpdate 2.25. Also, I notice there have been a couple of updates to workbench components as well for my micro A1.
I guess from now on it is important to regularly schedule checking AmiUpdate to run to see what new OS4.x components become availble.

Scott

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@unimon

Quote:

I got a GrimReaper. It seems that Amiupdate is now launched from the Workbench Startup. I deactivated it and now it works fine.

If it was set to start from WBStartup then you must have done it yourself. Since AmiUpdate requires a working network connection on startup it is better to add it to Network-Startup IMO.

Just add "WBRun APPDIR:AmiUpdate" to the end of the S:Network-Startup script to make AmiUpdate start automatically after the network connection is started.

The crash on startup is because of the latest 2.25 version of AmiUpdate. If you have the rollback feature enabled in AmiUpdate you should use it to go back to the previous version you had installed.

@salass00

To make it even clearer for users - just run 'Updates' in the Preferences drawer and go back to a previous date.

Last edited by djrikki on 13-Dec-2012 at 06:18 PM.

_________________

@djrikki

I rolled back so now i just wait for 2.26 :)

Good with such errors are you get to know amiupdate some more. Now i know how to rollback, manage ignores and actually looked whats up in the menus :)

Last edited by Kicko on 13-Dec-2012 at 07:16 PM.

@djrikki & salass00

Thanks for the heads up. I'll roll back and wait for a newer fixed version.

_________________
Moxee
AmigaOne X1000
AmigaOne XE G4
I'd agree with you, but then we'd both be wrong.

@thread

I did not need to rollback. I still had AmiUpdate v2.21 installed and when the updater asked to install v2.25 I refused. I'll wait until v2.26 bugfix is offered.

Last edited by Moxee on 14-Dec-2012 at 12:53 AM.

_________________
Moxee
AmigaOne X1000
AmigaOne XE G4
I'd agree with you, but then we'd both be wrong.

@Moxee

Which means update 6 was not installed properly on your machine.
Amiupdate 2.22 is the version installed by update 6 .

Quote:

Moxee wrote: @thread I did not need to rollback. I still had AmiUpdate v2.21 installed and when the updater asked to install v2.25 I refused. I'll wait until v2.26 bugfix is offered.

_________________
Sam460ex : Radeon Rx550 Single slot Video Card : SIL3112 SATA card

@Spectre660

Quote:

Spectre660 wrote: @Moxee Which means update 6 was not installed properly on your machine. Amiupdate 2.22 is the version installed by update 6 .

I believe U6 doesn't remove previous AU versions, at least it didn't for me, so i had to remove the older version by hand. I think this might depend on the fact that i didn't have it installed on the default location (which i suppose is somwhere on SYS:) but i had it on WORK:

_________________
Proud Amigan since 1987
Owner of various Commodore and a SAM440ep\OS4.1FE
See them on http://retro.furinkan.org/

@Spectre660

Quote:

Which means update 6 was not installed properly on your machine. Amiupdate 2.22 is the version installed by update 6 .

Sorry, I made a mistake. I have AmiUpdate v2.23 installed.

I am a little annoyed with Update 6 though because Update 6 reinstalled old versions of NList and all those other MUI libraries. When I started Yam it notified me of MUI library updates which I had already installed weeks ago. I just figured that Update 6 contained some old libraries.

_________________
Moxee
AmigaOne X1000
AmigaOne XE G4
I'd agree with you, but then we'd both be wrong.

@Moxee

Update 6 did not contain any Mui libraries .

_________________
Sam460ex : Radeon Rx550 Single slot Video Card : SIL3112 SATA card

@Spectre660

Oh, then the old MUI libraries must have come installed already in my X1000 by AmigaKit.

And what I remember as installing the newer MUI libraries must have been in my XE. I keep a tablet listing what I install, but not in what machine. I guess I'll have to keep track of that now. Or get rid of the XE.

_________________
Moxee
AmigaOne X1000
AmigaOne XE G4
I'd agree with you, but then we'd both be wrong.

@Moxee

Update 6 installs a new AmiUpdate, but an env variable still points to the old AmiUpdate install & starts that from the new menu. I hit that wall testing it, only solution is to delete the old install so the new install is found. The update 6 text says to do this. Just be aware that any rollback files need to be saved from the old install, if you need them, RollBack directory.

Last edited by sundown on 14-Dec-2012 at 11:18 PM.

_________________
Hate tends to make you look stupid...

[Local time: 2012-12-14 19:30]
@sundown

I am starting to appreciate the Solaris package programs more and more.

I never took the occasion to make any such in 15 years of being an application programmer. But starting about 2 months ago I was misled about how eeeeasy it was. The demo was the equivalent of "Hello world" with no real world smarts. Needless to layout the details, but THAT is where the devil really is.

Like many such things: 1) unaware; 2) seems trivial; 3) the dawn comes and the learning curve ascends; 4) a plateau; 5) familiarity; 6) "This ain't so hard."

I'm at 3.3.

_________________
..effects of civilization upon...nature, the growing gap between what education was supposed to accomplish and what it consisted of, the national debt and...high taxes, the problem of the excess cost of medical care -- Philip Wylie, 1951

@sundown

Quote:

Update 6 installs a new AmiUpdate, but an env variable still points to the old AmiUpdate install & starts that from the new menu.

I only have one AmiUpdate. It is v2.23 located in SYS:System/AmiUpdate.

ENV: is ENV:AppDir/AmiUpdate. Which states: DH0:System/AmiUpdate.

Looks to me like all is well and it is working fine without problems.

Quote:

I hit that wall testing it, only solution is to delete the old install so the new install is found. The update 6 text says to do this.

I don't remember deleting anything, but I followed the directions. Either I already had deleted it or perhaps the new version installed over the old one. I don't know. My retention is getting faulty. Remember our discussion at AmiWest 2011? AmiUpdate appears to be working fine though.

Quote:

Just be aware that any rollback files need to be saved from the old install, if you need them, RollBack directory.

I didn't really need them in the X1000, but I may when I install Update 6 in my XE.

Just for information, I was not complaining about AmiUpdate. I was wondering why those old MUI Libraries were installed when I had updated them. I thought Update 6 installed the old MUI libs, but I was wrong. Apparently those old MUI Libraries were there in my X1000 as delivered. I just never got around to updating them in my X1000 when Yam advised of new MUI libs.

The MUI libs that I had updated were in my XE. Then, of course, my brain transposed that information to my X1000. I will be keeping 2 update logs from now on so I don't get the XE and X1000 updates confused again.

It is hell growing old. I don't recommend it.

_________________
Moxee
AmigaOne X1000
AmigaOne XE G4
I'd agree with you, but then we'd both be wrong.