I turned on the Amiga after a month of sleep and i run Amiupdate.
Amiupdate showed for new update: Amiarcadia, MUI and AISS (can't remember the fourth).
I installed AISS from the ram package.
I then rebooted the Amiga and the workbench fails to load.
I have a cli window with some lines of text:
Assign: file is not executable Assign: file is not executable Assign: file is not executable Assign: file is not executable Assign: file is not executable Assign: file is not executable
and a requester asking me for volume T process: 6 "AddDataTypes". After a while another requester appears: insert keymap disk and after a while a preference msgbox "cant load char map "i:iso-8859-15"
Seems that AISS overwrite all files in C directory. Since there are files with the same name of the C commands (like assign, version or list) all original commands are gone :(
Seems that AISS overwrite all files in C directory. Since there are files with the same name of the C commands (like assign, version or list) all original commands are gone :(
Why is your AISS installed in C:?
The default location for the tbimages: assign (set in S:user-startup) should be "SYS:Prefs/Presets/tbimages".
The default location for the tbimages: assign (set in S:user-startup) should be "SYS:Prefs/Presets/tbimages"."
Really don't know.
I executed the file unpacked in ram and it make everythings by his own.
I now fixed prefs. Still a gream reaper on reboot. Workbench starts in low res then try to set an higher resolution and the gream reaper appears. Default right-click context menu disappeared :(
@AmigaBlitter FWIW, AmiSystemRestore would have allowed you to undo all the damage. (Of course you would have needed it installed BEFORE your System partition got trashed.)
I mean, in *theory* AmiUpdate has a RollBack feature, but it's rather dependant upon the relevant authors writing their installers correctly.
Doing backup of most important directory, right now, but it's very slow. I will format the hard disk and reinstall everything. Almost two days trying to recovery....
Btw, there's a way to protect important part of the OS?
You can LOCK system volume (only read), but take care that some tools/programs will try to save prefs/config and will pop up a requester everytime then.