Welcome, Guest. Please login or register.

Author Topic: Os 3.1.4 - List of bug fixes and changes by component  (Read 85038 times)

Description:

0 Members and 2 Guests are viewing this topic.

Offline NinjaCyborg

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #104 from previous page: December 09, 2018, 12:49:12 PM »
But will that work if I unplug it, then change it for a different one? Or put two at the same time, in different USB sockets, both of which would therefore be "C" drive assuming one partition per stick?
 

guest11527

  • Guest
Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #105 on: December 09, 2018, 01:09:04 PM »
But will that work if I unplug it, then change it for a different one? Or put two at the same time, in different USB sockets, both of which would therefore be "C" drive assuming one partition per stick?

I do not know how your average USB stack maps devices to unit numbers, but I would believe that you can control with the unit number in the mount list which stick this is supposed to be. The geometry change does not matter, CrossDos gets this information from the partition and adjusts itself. That is, all the "LowCyl/HighCyl" numbers in the mount list are irrelevant and replaced by CrossDos anyhow.
 

guest11527

  • Guest
Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #106 on: December 09, 2018, 01:13:39 PM »
I see. Yes, guess I may have attempted using & in some temporary script, which then has been launched with "run >NIL: script" in the background, detaching it from any console capable of job control. Using & is more equivalent to "run >console:" I suppose.

No, & is not equivalent to "Run". "Run" starts a background shell, "&" does not. That means, the input of a program launched with "&" stays connected to the console, just a different console owner. Of course, the default Console-Handler of AmigaOs (aka Tripos) is too stupid to know, but ViNCed does. If you start a program with & and it requests input, the console will tell you and you can switch between the jobs with the "fg" and "bg" commands, and then enter information. "&" is much closer to the Linux/Unix "&" than "Run" ever was. If you start a program with "Run" and it expects input, it will receive nothing.

The name of the console will be "CONSOLE:xxxx" where "xxxx" is some unique string the shell generates with UniqueID() from the utility.library.
 

Offline kolla

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #107 on: December 09, 2018, 07:49:19 PM »
I see. Yes, guess I may have attempted using & in some temporary script, which then has been launched with "run >NIL: script" in the background, detaching it from any console capable of job control. Using & is more equivalent to "run >console:" I suppose.

No, & is not equivalent to "Run".
I wrote "more equivalent", not that it was equivalent.

Quote
"Run" starts a background shell, "&" does not. That means, the input of a program launched with "&" stays connected to the console, just a different console owner. Of course, the default Console-Handler of AmigaOs (aka Tripos) is too stupid to know, but ViNCed does. If you start a program with & and it requests input, the console will tell you and you can switch between the jobs with the "fg" and "bg" commands, and then enter information. "&" is much closer to the Linux/Unix "&" than "Run" ever was. If you start a program with "Run" and it expects input, it will receive nothing.

Well, what you describe is rather messy, with the console doing the job of the shell - again.

Code: [Select]
$> type ram:test
ping somewhere &
echo haha
$> protect ram:test +s
$> run >NIL: ram:test

.. and presto, requester pops up, asking me to insert CONSOLE:

In other words - "&" only really works "reliably" in ViNCed, where job control is a thing, and the fg and bg scripts are (somewhat) functional.

On plain OS 3.1.4 there is no ViNCEd, using the & becomes rather pointless, not to mention "dangerous".
« Last Edit: December 10, 2018, 06:42:59 AM by kolla »
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

guest11527

  • Guest
Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #108 on: December 09, 2018, 07:53:33 PM »
I am not sure which operating system you are using, but CONSOLE: is not a ViNCEd specific thing at all, not at all. It is a (pseudo)-device that is created and operated by the dos.library. If you see such a strange requester, it is surely not becaue you are not using ViNCEd. The only that that is different there is that my console supports job control whereas CON: does not.

Os 2.x supported CONSOLE: only incompletely, but this changed in 3.1.
 

Offline kolla

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #109 on: December 09, 2018, 07:59:47 PM »
I do not know how your average USB stack maps devices to unit numbers, but I would believe that you can control with the unit number in the mount list which stick this is supposed to be. The geometry change does not matter, CrossDos gets this information from the partition and adjusts itself. That is, all the "LowCyl/HighCyl" numbers in the mount list are irrelevant and replaced by CrossDos anyhow.

With FAT95, one can use DosType in a mountlist entry to tell what MBR partition on a device that will be mounted, for example by setting DosType=0x46415401 it will use the first FAT partition of a device (regardless), 0x46415402 is second primary... 05 is first logical if there is an extended partiion, 06 is second etc.

How do one do this with the new CrossDOS? I want to replace FAT95 with CrossDOS, but if it means dealing with geometry and cylinders on every individual device I may put into a system, it is simply not worth it.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline kolla

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #110 on: December 09, 2018, 08:03:41 PM »
I am not sure which operating system you are using, but CONSOLE: is not a ViNCEd specific thing at all, not at all. It is a (pseudo)-device that is created and operated by the dos.library. If you see such a strange requester, it is surely not becaue you are not using ViNCEd. The only that that is different there is that my console supports job control whereas CON: does not.

Os 2.x supported CONSOLE: only incompletely, but this changed in 3.1.

So? Not sure why you keep misreading me...

My point was that... JOB CONTROL ... and hence, using & to run commands in background,  is only useful with ViNCEd. Using "&" with the out-of-the-box console of OS 3.1.4 can easily bring the user to unfriendly places. Especially if he/she makes the mistake of putting it in scripts.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

guest11527

  • Guest
Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #111 on: December 09, 2018, 08:14:16 PM »
How do one do this with the new CrossDOS? I want to replace FAT95 with CrossDOS, but if it means dealing with geometry and cylinders on every individual device I may put into a system, it is simply not worth it.
You find out by reading my post. Yes, really. I just found out it's really not worth answering.
 
The following users thanked this post: Tygre

guest11527

  • Guest
Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #112 on: December 09, 2018, 08:18:36 PM »
So? Not sure why you keep misreading me...

My point was that... JOB CONTROL ... and hence, using & to run commands in background,  is only useful with ViNCEd. Using "&" with the out-of-the-box console of OS 3.1.4 can easily bring the user to unfriendly places. Especially if he/she makes the mistake of putting it in scripts.

CON: does not have job control. Or rather, it does not distinguish between multiple programs that opened the console, which is about the only difference.

Thus, whatever command was operating in background will instead "steal" input from the console. Instead of not getting any input at all. Now, is that any better at all? If you don't want input, you can still use an input redirection <NIL:



 
The following users thanked this post: Tygre

Offline NinjaCyborg

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #113 on: December 09, 2018, 09:27:48 PM »
Jesus christ Kolla eff off please. Go find another platform to harass people about, preferably Atari ST users.
 
The following users thanked this post: Tygre, klx300r

Offline kolla

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #114 on: December 09, 2018, 09:47:41 PM »
You find out by reading my post. Yes, really. I just found out it's really not worth answering.

It is vague, it appears to not let user specify where to actually look for a FAT file system.
You write "Change the name of the icon such that the last letter indicates the right partition".
So what is it for second logical partition? Does it depend on whether there is FAT filesystems on the other partitions? Does partition ordering matter?

Also...
Quote
Now, consider the same for FAT95: Instead, you could have as many as 255 entries in the FileSystem resource for that: One for FAT\0, the first partition, one for FAT\1, the second partition and so on, up to FAT\255, the 256th partition.
So how do one do many partitions with CrossDOS now anyways? You quickly run out of letters in the alphabet.
« Last Edit: December 10, 2018, 07:03:08 AM by kolla »
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline 10MARC

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #115 on: December 10, 2018, 05:45:41 AM »
If I can interrupt Kolla's persistent whining for just a moment - I put up a video last week all about the new features and updates in AmigaOS 3.1.4 - I tried to research this thread and the docs as much as I could, but I am sure I missed a few things. I would really appreciate if the developers of this awesome new update could take a peek when they have a chance, and correct me where I am off base. Thanks! And keep things civil!
https://youtu.be/BDAgjf6IlMA
 
The following users thanked this post: Tygre

guest11527

  • Guest
Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #116 on: December 10, 2018, 06:59:34 AM »
It is vague, it appears to not let user specify where to actually look for a FAT file system.
No, it's not at all vague. You just have to read the whole thing from start to end, all the information you need is there, including how to specify which partition to pick. Kolla, I'm not feeling responsible for spoon feeding you.
 

Offline kolla

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #117 on: December 10, 2018, 07:17:38 AM »
@Thomas Richter

No, you only say that dos device name must end with a letter that corresponds to a partition, whatever that is may very well depend on the partition layout, there is no exact answer, right? The MBR partition table may not list partitions in "correct" order, the extended partition may or may not exist on either of the four possible primary partitions, and the order of logical partitions is also not necessarily fixed. Does CrossDOS care about partition ordering? No answer. Does it get confused if there are primary partitions "behind" an extended partition? Who knows. Is there a specific letter associated with exactly the second logical partition of an extended partition? I suppose answer is - not really.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline trekiej

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #118 on: December 11, 2018, 01:54:34 AM »
Would there be any problem using this with an A1000 if I got an accelerator or rom board?
Amiga 2000 Forever :)
Welcome to the Planar System.
 

Offline Tygre

Re: Os 3.1.4 - List of bug fixes and changes by component
« Reply #119 on: December 11, 2018, 02:21:40 AM »
@Thomas Richter

No, you only say that dos device name must end with a letter that corresponds to a partition, whatever that is may very well depend on the partition layout, there is no exact answer, right? The MBR partition table may not list partitions in "correct" order, the extended partition may or may not exist on either of the four possible primary partitions, and the order of logical partitions is also not necessarily fixed. Does CrossDOS care about partition ordering? No answer. Does it get confused if there are primary partitions "behind" an extended partition? Who knows. Is there a specific letter associated with exactly the second logical partition of an extended partition? I suppose answer is - not really.

Why don't you try and report in this thread? (Or create a dedicated thread about your questions?) That would be useful to everyone and Thomas could go back to listing and explaining "bug fixes and changes by component", which is the reason for this tread. (Not to serve as an in-depth, developers' manual for AmigaOS v3.1.4.)
« Last Edit: December 11, 2018, 02:24:28 AM by Tygre »
 
The following users thanked this post: klx300r