Welcome, Guest. Please login or register.
Amiga Kit Amiga Store Hollywood MAL AMIStore App Store A600 Memory

AuthorTopic: Os 3.2 development preview  (Read 57222 times)

0 Members and 1 Guest are viewing this topic.

guest11527

  • Guest
Re: Os 3.2 development preview
« Reply #480 on: December 13, 2019, 10:44:03 AM »
The "problem" here is that you call this an "FPGA flag" - for sure it is not an "FPGA flag", it is an "Apollo Core flag" - one day that CPU may exist in ASIC, and the flag will still be there, and it will be very inaccurate to call it an "FPGA flag".
The name is "Apollo FPGA", if this makes you feel any better. Yes, it is reserved for the Apollo series of FPGA cores.

guest11527

  • Guest
Re: Os 3.2 development preview
« Reply #481 on: December 13, 2019, 10:46:21 AM »
What do you mean "other FPGA"?
You know that exactly.
 

Offline kolla

Re: Os 3.2 development preview
« Reply #482 on: December 13, 2019, 10:50:25 AM »

Here we go again. Just because you $favorite_feture is not supported, you bully around. Kolla, forget it.

No - it really is not a "$favourite_feature", I really couldn't care less about this feature, when it comes to icons, the tools provided by the operating system have been borderline useless/pointless since forever, so I have my ways around it.

But I see where the request comes from, and I find your argument against it very weak, for the reasons I mention - the WBInfo window is already an editor, a rather extensive one - the primary reason for a user to open an info window is to make changes - be it replace icons, edit tool types, set default tool, toggle filesystem flags etc. - because, you know...

Quote
an *information window*

that can not..
* display the version of a file
* does not show what filesystem is used on a device/volume (but hey, random information of a filesystem - blocksize - always what I look for!)
* the content size of a drawer (but hey, you can edit tooltypes of drawers - awesome!)

Quote
It is a job for an icon editor. We have one. Again a very basic one.

Then, for the sake of consistency, shouldn't also editing tooltypes, default tool, stack size, priority etc. also be left as a job to the icon editor?

The current icon editor is nothing but a very simple and extremely basic graphical editor, and not really so useful for editing icons as it doesn't grasp the "new" icon format properly (read only?), doesn't support more than the 8 basic pens, pasting brushes from programs like PPaint etc doesn't work as intended etc.

Its _only_ metadata editing capabilities IconEdit can do, is setting the "icon type".

Quote
Besides, Rawbinfo or swazinfo are not patches. They just implement the info hook of the workbench. If you want features implemented there, bug their authors. It's ok to have third party tools.

RAWBInfo (ReAction-WorkBench-Info) has all features one can wish for, only problem is that it is buggy and unmaintained, and it currently needs 020+, but that could just be a matter of ReAction classes not supporting 68000.
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
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM460 and Mac minis with MorphOS
 

Offline kolla

Re: Os 3.2 development preview
« Reply #483 on: December 13, 2019, 10:58:08 AM »
What do you mean "other FPGA"?
You know that exactly.
No, I don't know what kamelito - not you - means with "other FPGA". There is a whole range of FPGA based Amiga systems around, and more are coming, and the various 68k implementations have different goals. So, I wonder what projects specifically kamelito - not you - was thinking about when he wrote "other FPGA".

And again, does it make sense to call it "Apollo FPGA" the day Apollo Core is ASIC, or is implemented on something that is not regarded as FPGA, for example through software emulation? It should really be enough to say that C:CPU now recognise the Apollo Core 68080 CPU core, without dragging the term "FPGA" into it.
« Last Edit: December 13, 2019, 10:58:51 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
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM460 and Mac minis with MorphOS
 

guest11527

  • Guest
Re: Os 3.2 development preview
« Reply #484 on: December 13, 2019, 10:58:57 AM »
No - it really is not a "$favourite_feature", I really couldn't care less about this feature, when it comes to icons, the tools provided by the operating system have been borderline useless/pointless since forever, so I have my ways around it.
Then why all the rumble again? Oh, sorry, forgot, to make a rumble of course...

Offline kolla

Re: Os 3.2 development preview
« Reply #485 on: December 13, 2019, 12:52:01 PM »
Then why all the rumble again?

Because a very reasonable request was made, and your counter argument was very weak. WBInfo is much more of a metadata editor than IconEdit is.
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
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM460 and Mac minis with MorphOS
 

Offline Minuous

Re: Os 3.2 development preview
« Reply #486 on: December 13, 2019, 01:14:17 PM »

Offline ronniebeck

Re: Os 3.2 development preview
« Reply #487 on: December 13, 2019, 03:57:41 PM »
The "problem" here is that you call this an "FPGA flag" - for sure it is not an "FPGA flag"...............................

Kolla is right.  Labeling it with "FPGA" is misleading and not helpful to anyone. 

Quote from: Thomas Richter link=topic=74270.msg847053#msg847053
I don't know, I don't care. We cannot give every version of the Apollo core another flag because we don't have many flags left..............

Rather a surprising answer to hear:  I don't know and I don't care.
I hope your attitude changes.

Offline rxxic

Re: Os 3.2 development preview
« Reply #488 on: December 13, 2019, 04:15:27 PM »

Quote
an *information window*

that can not..
* display the version of a file
* does not show what filesystem is used on a device/volume (but hey, random information of a filesystem - blocksize - always what I look for!)
* the content size of a drawer (but hey, you can edit tooltypes of drawers - awesome!)

One has to admit, these are all very valid points. I do fully agree with Kolla here.
Quote
Quote
It is a job for an icon editor. We have one. Again a very basic one.

Then, for the sake of consistency, shouldn't also editing tooltypes, default tool, stack size, priority etc. also be left as a job to the icon editor?

The current icon editor is nothing but a very simple and extremely basic graphical editor, and not really so useful for editing icons as it doesn't grasp the "new" icon format properly (read only?), doesn't support more than the 8 basic pens, pasting brushes from programs like PPaint etc doesn't work as intended etc.

Its _only_ metadata editing capabilities IconEdit can do, is setting the "icon type".

And I also see the logic here.
Quote
Quote
Besides, Rawbinfo or swazinfo are not patches. They just implement the info hook of the workbench. If you want features implemented there, bug their authors. It's ok to have third party tools.

RAWBInfo (ReAction-WorkBench-Info) has all features one can wish for, only problem is that it is buggy and unmaintained, and it currently needs 020+, but that could just be a matter of ReAction classes not supporting 68000.
If it's true it's unmaintained, then it's unfortunate.
 

Offline rxxic

Re: Os 3.2 development preview
« Reply #489 on: December 13, 2019, 04:22:13 PM »
Some other changes of C: components:

- SetDate gets a new keyword "FROM" that copies the date over from another file.


Will SetDate and Date be able to use the date format set in locale too, or will it--for consistency reason--force everybody using the shell to use a foreign format?
 

guest11527

  • Guest
Re: Os 3.2 development preview
« Reply #490 on: December 13, 2019, 05:10:09 PM »
Will SetDate and Date be able to use the date format set in locale too, or will it--for consistency reason--force everybody using the shell to use a foreign format?
Why "will"? Date and Setdate use StrToDate from the dos.library, and this function is patched over by the locale.library since a long time. It accepts input in the current locale since WB 2.1, I would say.


guest11527

  • Guest
Re: Os 3.2 development preview
« Reply #491 on: December 14, 2019, 09:07:01 AM »
For those of you who want to contribute to a little test, here is a resident module that is supposed to enable 4-way adapters on the internal IDE interface of the A1200 and A4000.

Note well, this is *not* an executable program. It cannot be run from the startup-sequence. Instead, you have to load it with LoadModule. Place the module into LIBS:Modules/AtapiMagic, then either edit or extend the startup-sequence by the following line:

LoadModule LIBS:modules/AtapiMagic <other LoadModule options go here>

The mechanism that is triggered by this module is available since Os 3.9 (scsi.device v43), and extends throughout Os 3.1.4 (and later, of course).
 
The following users thanked this post: Orphan264, Tygre

Offline kolla

Re: Os 3.2 development preview
« Reply #492 on: December 14, 2019, 11:21:18 AM »
For those of you who want to contribute to a little test, here is a resident module that is supposed to enable 4-way adapters on the internal IDE interface of the A1200 and A4000.

So much fuss about this... it works, of course.
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
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM460 and Mac minis with MorphOS
 

guest11527

  • Guest
Re: Os 3.2 development preview
« Reply #493 on: December 14, 2019, 12:00:24 PM »
So much fuss about this... it works, of course.
No, at this point, we know that it works for you, in your configuration. What we do not know what happens if you do not have the adapter installed, or one end not connected, with gates floating.

Offline CBH

Re: Os 3.2 development preview
« Reply #494 on: December 14, 2019, 01:54:07 PM »
No, at this point, we know that it works for you, in your configuration. What we do not know what happens if you do not have the adapter installed, or one end not connected, with gates floating.

Your whole big argument was that you won't release what you don't have the hardware to test. Now that problem is solved - it works.

Now your problem is that you don't not have the hardware, so you can't test what the module does when the splitter isn't installed?

Do I have to send you an envelope with a nothing in it, so you can use the nothing for testing purposes?

A normal human being would just try it on a bare motherboard with one drive and see. I'm sure you have that.
« Last Edit: December 14, 2019, 01:55:10 PM by CBH »