Author Topic: ARCAOS 5.1 install  (Read 907 times)

andreas

  • Jr. Member
  • **
  • Posts: 89
  • Karma: +5/-0
    • View Profile
ARCAOS 5.1 install
« on: February 03, 2025, 02:04:52 am »
I have a problem, finishing instalation of AOS5.1 in UEFI-mode. After several reboots, installation went find until suddeny another reboot was required, but the reboot-button had no effect - and autreboot also didn't work.
I rebooted the "normal way", but the problem remained the same. tried several times
Startup.cmd leaves me with "install.exe allcopy2-pg /LogsC:\var\log /Fonts=M".
Even after trying an update-installation i come to the same result...

I get the message: CALL NOCDBOOT.cmd R:   Sys1041: The name NOCDBoot.cmd is not recognized as an internal or external command, ioerable program or batch file. 6 *-* 'CALL NOCDBOOT.CMD R:'; +++ RC(1041)
then: the before mentioned startup-cmd appears.
then: just [C:sys\install\gui]

How can I finish the installation process?


« Last Edit: February 03, 2025, 02:16:02 am by andreas »

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5216
  • Karma: +120/-1
    • View Profile
Re: ARCAOS 5.1 install
« Reply #1 on: February 03, 2025, 03:17:38 am »
I think you should open a ticket as it seems a weird problem.

andreas

  • Jr. Member
  • **
  • Posts: 89
  • Karma: +5/-0
    • View Profile
Re: ARCAOS 5.1 install
« Reply #2 on: February 03, 2025, 03:48:23 am »
did so

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5216
  • Karma: +120/-1
    • View Profile
Re: ARCAOS 5.1 install
« Reply #3 on: February 03, 2025, 04:57:04 am »
You need to attach a testlog generic to the ticket from your system which I understand is somewhat usable. Also in C:\sys\install (change drive letter to your boot one if needed) there should be a file, install_2025_0202.zip or with a slightly different date that you should also attach to the ticket.

andreas

  • Jr. Member
  • **
  • Posts: 89
  • Karma: +5/-0
    • View Profile
Re: ARCAOS 5.1 install
« Reply #4 on: February 05, 2025, 05:45:36 pm »
i think u found out the reason by myself: it was the IBM File and Print Client. Since i left this option unmarked installation process went without any trouble.
(Anyway I was not sure, if that Client is useful for me or not...).

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5216
  • Karma: +120/-1
    • View Profile
Re: ARCAOS 5.1 install
« Reply #5 on: February 05, 2025, 06:13:19 pm »
i think u found out the reason by myself: it was the IBM File and Print Client. Since i left this option unmarked installation process went without any trouble.
(Anyway I was not sure, if that Client is useful for me or not...).

Generally Samba works well for doing the peer stuff unless you're trying to communicate with old operating systems. IBM File and Print is old and insecure.

Roderick Klein

  • Hero Member
  • *****
  • Posts: 717
  • Karma: +14/-0
    • View Profile
Re: ARCAOS 5.1 install
« Reply #6 on: February 05, 2025, 06:45:27 pm »
I have a problem, finishing instalation of AOS5.1 in UEFI-mode. After several reboots, installation went find until suddeny another reboot was required, but the reboot-button had no effect - and autreboot also didn't work.
I rebooted the "normal way", but the problem remained the same. tried several times
Startup.cmd leaves me with "install.exe allcopy2-pg /LogsC:\var\log /Fonts=M".
Even after trying an update-installation i come to the same result...

I get the message: CALL NOCDBOOT.cmd R:   Sys1041: The name NOCDBoot.cmd is not recognized as an internal or external command, ioerable program or batch file. 6 *-* 'CALL NOCDBOOT.CMD R:'; +++ RC(1041)
then: the before mentioned startup-cmd appears.
then: just [C:sys\install\gui]

How can I finish the installation process?

Basedon this error message this has nothing todo with the selection of the PEER installer.  The best I can read that error messages is that the second phase (booting from the hard drive the first time) de-rails when it tries to load the installer UI that shows the progress bar. The IBM PEER installer has then not even been loaded at that , that is done  by the CID backend way later in the installer process.

Best regards,

Roderick Klein