AROS World Exec
Distros => AROS One => Topic started by: ntromans on May 07, 2023, 01:07:30 PM
-
I finally found a some time over the bank holiday weekend heew in the UK to ugrade to ArosOne v2.0 on my Samsung netbook (was running on 1.8). Mosly absolutely fine, and thanks again for all the effort in putting it together, but I did notice a problem with the installer.
I was trying to install from USB on an existing partition (overwriting the existing sys: after booting from USB) but on the last panel the device box was empty. I manually added the device (ata.device) and correct unit but the installer absolutely refused to write the bootloaded to the partition resulting on a Grib error on boot. I only finally fixed if by using the istaller from the 1.8 distro, which correctly filled in device box and installed. Anyway, thought I should mention it.
Cheers,
Nigel.
-
I don't quite understand the problem, the correct procedure to install a new version of AROS One on an old one is this:
- Start Pendrive with AROS One v2.0
- From Wanderer format the AROS volume
- Restart Pendrive with AROS One v2.0
- Run InstallAROS
This will give you a clean installation, if you install on the old version instead, you will pull duplicate or obsolete files (on AROS One 2.0 there have been changes and folder moves)
-
I don't quite understand the problem, the correct procedure to install a new version of AROS One on an old one is this:
- Start Pendrive with AROS One v2.0
- From Wanderer format the AROS volume
- Restart Pendrive with AROS One v2.0
- Run InstallAROS
This will give you a clean installation, if you install on the old version instead, you will pull duplicate or obsolete files (on AROS One 2.0 there have been changes and folder moves)
I have several partitions - sys:, work:, documents:, content: and test: I have to use the installer for sys: so Grub is installed but work: I want to install by hand and the others left untouched. So, boot from the USB, reformat the sys: partition and in installer select 'Use existing AROS partitons (on any drive)' but on reaching th last panel the device (in this case ata.device) is not selected - see attached..Even if you type the device in manually Grub is not installed on the device/unit. As noted, a copy of the installer from 1.8 works fine, with the device being correctly selected.
Cheers,
Nigel.
-
With which tool did you create the other partitions ?
I did the same operation on my PC, but there was only one partition and everything worked, now I don't know if with the new "core" something has changed, I should ask deadwood
-
With which tool did you create the other partitions ?
I did the same operation on my PC, but there was only one partition and everything worked, now I don't know if with the new "core" something has changed, I should ask deadwood
The other partitons were using made using HDToolbox.
Cheers,
Nigel.
-
Tried with HDToolbox to fix SYS.
-
However it may be that HDToolbox has modified something.
I tried to upgrade a PC of mine with DualBoot AROS/Win10, formatted the "AROS" volume and installed AROS One 2.0 without any problem.
-
One thing tht may be affecting the outcome - I don't use the standard device names (dh0::, dh1: etc.), but set each of my machines wirth a sightly different set of names (e.g. dso:, ds1: for the Samsung, dc0:. dc1: for the Compaq etc.). This is so if a machine 'dies' and I need to extract data from its hard drive by connecting to another computer AROS does not get confused with the same device name appearing twice. However, as mentioned I've never seen this cause a problem with the installer before.
Cheers,
Ngel.
P.S. I also give each device its own unique volume name, e.g. AROS_S, Work_S, and for each machine assign the standard names (AROS, Work etc.) in the first few lines of its startup-sequence).
-
However, if you say that with AROS One 1.8 the problem does not exist, then the partition name or volume name cannot be