different KS, different startup-sequence running

[kremiso]

i remember in past the trouble in some releases to close correctly the Workbench, running them with Kickstart 2.0 or 3.1, compared to the KS1.x

but today i am testing something different
a 3 disks ADOS game (Moonstone), emulated with 3 floppies enabled, with the df0: startup-sequence changed;
just a single command "df2:boot" into, with a boot executable file added in the third disk

now, using KS1.x the startup-sequence runs ok, when instead nothing happen using KS2.0 ;
no errors on screen, seems completely skipped
i have alredy tried to add a "wait" command before that line, still nothing

i miss something noob thing here?

[AMIGASYSTEM]

Hi, I didn't understand well, if you can add the problem also in Italian probably I can help you to solve it.

--- Italiano ---

Ciao, non ho capito bene, se puoi aggiungere il problema anche in Italiano probabilmente potrò aiutarti a risolvere.

[kremiso]

Originally Posted by AMIGASYSTEM

Hi, I didn't understand well, if you can add the problem also in Italian probably I can help you to solve it.

--- Italiano ---

Ciao, non ho capito bene, se puoi aggiungere il problema anche in Italiano probabilmente potrò aiutarti a risolvere.

ciao
sto cercando di far leggere un file aggiunto nel terzo disco di gioco (e inserito in df2: ), tramite la normale startup-sequence (in df0: )

usando il solo comando "df2:boot" (dove 'boot' è il nome del file aggiunto),
la startup-sequence parte normalmente con una configurazione A500 KS1.x + 3 drives

ed invece non funziona con A500+ KS2.0 e 3 drives

non riesco a capire se cambia qualcosa nella procedura di riconoscimento dei drives che fa saltare completamente la startup-sequence, usando la seconda configurazione...
spero sia chiaro

EDIT english translation :

I'm trying to read a file added in the third game disk (and inserted in df2: ), through the normal startup-sequence (in df0: )

using only the command "df2:boot" (where 'boot' is the name of the added file),
the startup-sequence starts normally with an A500 KS1.x + 3 drives configuration

but it does not work with A500+ KS2.0 and 3 drives.

I cannot understand if something changes in the drives recognition procedure that makes the startup-sequence skip completely, using the second configuration...

[AMIGASYSTEM]

True I confirm, it seems that with OS2.x/OS3.x you can't execute anything automatically from DF2, if the command is given by DF0, if you type from the prompt instead it works fine, strange, we must see if it is a choice or there is a remedy, tonight I do some tests.


---- Italiano ----


Vero confermo, sembra che con OS2.x/OS3.x non si possa eseguire nulla automaticamente da DF2, se il comado è dato da DF0, se digiti dal prompt invece funziona bene, strano, bisogna vedere se è una scelta o esiste un rimedio, stasera faccio qualche test.

[AMIGASYSTEM]

@kremiso

Found the mystery, the problem is not really with OS 2.x or 3.x but with the names of the floppies, in practice the three floppies have the same name, that is "one" space. Probably OS 1.x can distinguish the three floppies while OS2 and OS3 don't know where to look for them

Solve the problem by renaming the floppies "Moonstone1", "Moonstone2" "Moonstone3".
In the startup-sequence of "floppy one" you will put the command:

Moonstone3:Boot

--- Italiano ---

Scovato l'arcano, il problema non è proprio di OS 2.x o 3.x ma i nomi dei floppy, in pratica i tre floppy hanno lo stesso nome, ovvero "uno" spazio. Probabilmente OS 1.x riesce a distinsione i tre floppy mentre OS2 e OS3 non sanno dove cercare

Risolvi il problema rinominando i floppy "Moonstone1", "Moonstone2" "Moonstone3"
Nella startup-sequence del "floppy uno" metterai il comando:

Moonstone3:Boot

[kremiso]

Amazing find, thank you
btw, quite bizarre thing, let me say another point for the old 1.x

i'll do some play tests after the diskname change, just to check if all is still ok with the game itself

[AMIGASYSTEM]

I don't know why they used a space as the volume name, let me know if the game works fine even with the changed volume names !

[kremiso]

Originally Posted by AMIGASYSTEM

I don't know why they used a space as the volume name, let me know if the game works fine even with the changed volume names !

confirmed working changing all the three disks volume names

---
quite funny, just changing only the third disk name (ie 'Moonstone3')
and using 'Moonstone3:boot' or the same 'df2:boot' in the startup-sequence,
lead to the same buggy effect on os2.x and 3.x;

seems that they go in confusion just having two disks with the same volume name ?!

wondering

first - if this happens on real hardware too (i'm testing in emulation)
second - if could be considered an os bug, due the fact that it does not happen on 1.x

[malko]

If you put a "dir df2:" in your Strartup-Sequence does it work (with the original disks labels) ?

[kremiso]

Originally Posted by malko

If you put a "dir df2:" in your Strartup-Sequence does it work (with the original disks labels) ?

tested atm : nope

i had already tried also with a 'cd df2:' before launching the file, but still nothing

indeed quite bizarre, all fine instead through standard prompt

seems the df2: is completely ghosted from the other two disks

[AMIGASYSTEM]

Originally Posted by kremiso

first - if this happens on real hardware too (i'm testing in emulation)
second - if could be considered an os bug, due the fact that it does not happen on 1.x

I don't think so since this happens with all OS 2.x and 3.x. even if you use DF1 you will have the same problem.
My guess is that OS2.x and O3.x look for the Floppy name while OS 1.3 looks for the Volume name.

I remember that Amiga recognizes a path from the Volume Name as well as from the Disk or Partition name.

I add that on Amiga you can give names to Volumes but also to Directories or Files with spaces that can be as many as normal characters, this will make Volumes, Directories and Files invisible.


---- Italiano ----


Non credo visto che questo accade con tutti gli OS 2.x e 3.x. anche se utilizzi DF1 avrai lo stesso problema

Secondo me OS2.x e O3.x cercano il nome del Floppy mentre OS 1.3 cerca il nome del Volume.

Ricordo che Amiga riconosce un percorso sia dal Nome Volume che dal nome Disco o Partizione.

Aggiungo che su Amiga si possono dare nomi a Volumi ma anche a Directoy o File con degli spazi che posono essere tanti quanto quelli dei caratteri normali, questo renderà invisibili Volumi Directory e File.

[AMIGASYSTEM]

Originally Posted by malko

If you put a "dir df2:" in your Strartup-Sequence does it work (with the original disks labels) ?

No, it won't work even if you make a CD DF2:, or other strategies, everything will be ignored until you name the floppy.

[kremiso]

Originally Posted by AMIGASYSTEM

...even if you use DF1 you will have the same problem.
My guess is that OS2.x and O3.x look for the Floppy name while OS 1.3 looks for the Volume name.

i'm doing some tests atm, just for fun (os2.x)

-with 2 floppydrives and original named disks into ('space' character both)
the startup-sequence does not work

-with 2 floppydrives, first original named disk into df0: ('space' character), and renamed disk into df1:
the startup-sequence works

what i consider bizarre is the fact that i'm using a volume direct command (df1: or df2: ) that shouldn't generate issues; so i presume the os goes in confusion even before reading the startup-sequence, during the boot?

EDIT
and look this, seems that just renaming the disk in df0: 'fix' everything also
in this way it's possible to leave the other two disks with the 'space' name