On my peg2 once i apply update, its just freeze peg2. Soft boot didn't works, nothing on serial. Hard reboot, validating of ffs (still use it for boot, sadly), and after that all back to normal.
The run amiupdate again, it ask me to convert all dates to new format, done well. I run then scan for updates again, it did, found nothing, i press then iconify one time and back from it, and then, when i press close gadget i have:
Dump of context at 0xEFE2ABA0
Trap type: DSI exception
Machine State (raw): 0x0200F030
Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on]
Instruction pointer: in module intuition.library.kmod+0x00013DD4 (0x01A7A074)
Crashed process: (0x65DFC1D0)
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a load operation
0: 00000000 65CCC300 2F970000 65CCC330 00000000 00000002 00000052 6FF95000
8: 65CCC330 00000000 65B22D60 65CCC330 0000079C 65EEE5F0 65D27A28 65EE0000
16: 65CCC3F0 85003009 65EE0000 20000000 08000000 40000000 04000000 65EE0000
24: 8003000E 65CCC3F4 6FF894D0 6FF894D0 65B7A0CC 00000005 00000000 65CCC330
CR: 39935055 XER: A0000068 CTR: 00000000 LR: 01A79FE0
DSISR: 40000000 DAR: 0000002E
The crash when quitting should be fixed for the next version, which is now available.
Simon
Edited by Rigo on 2013/8/5 13:07:07
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
Without more information, I couldn't even hazard a guess as to what might be wrong.
Simon
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
If you select the red text in column "Update to the AmigaOS4 SDK" the info button will be ghosted correctly because that area should not be clickable
And it's that when you select it with the mouse, but if you select this column with the keyboard the info button stay active and so if you click on it you will got a crash:
Quote:
Crash log for task "SYS:System/AmiUpdate/AmiUpdate" Generated by GrimReaper 53.5 Crash occured in module AmiUpdate at address 0x6FA333E0 Type of crash: DSI (Data Storage Interrupt) exception
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
What other parts do you use often enough to warrant the time expended?
Simon
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
Well, I've no idea what happened there, but neither the update, nor the date conversion routine touches the .restore scripts.
And as no-one else has reported such problems, I really don't know what to suggest.
The dates shown in the left column are derived from the directory names in the "Rollback" directory, and the components in the right hand list are derived from ".restore" scripts in those dated directories. I can only suggest you check to see whether these files are actually in their respective places.
But of course, you backed up the rollback directory prior to converting the dates like you was told to, right?
Simon
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
I found the date conversion process tripped up slightly.
After each start of AmiUpdate since the initial date conversion message, I got the conversion message but it didn't seem to do anything (apart from on the first time).
On checking the rollback directory I found I had an old drawer
5-8-2013
and a new drawer
2013-08-05
So the updater could not rename the former into the latter as the latter all ready existed.
I fixed this by copying the contents of 5-8-2013 into 2013-08-05 and deleteing the original.
I also noticed that some session.tmp files remained that hadn't been renamed to AmiUpdate.restore this seemed to be where AmiUpdate had needed to reboot as part of the self update process, although that might be a coincidence as I have not stuied every drawer and can not ofcourse remeber which versions rebooted further back in time.
[edit] Fixed an unfeasabily large number of typos (even for me!)[/edit]