All this i would like in a hotfix rather then waiting for a update2.
1. Kingcon alike shell 2. Amidock scale of icons. Never liked amidock but use it now as amistart has problems with composition. Its like night and day these apps. 3. USB2 for speed which is very welcome 4.Fix corrupted filenames when copying to memstick. I dont know if and how many people have this. I tested everything without luck. I have 4 different memsticks.
EDIT: Make Opendrawer.rexx work even if partitions are "hidden" (hidden devices in workbench prefs). That would be great for the people that dont want to have partitions icons on workbench but rather in amidock/amistart and fire up from there. Saves space on wb :) At least i like it that way. Looks much cleaner.
Another good funktion of amistart is you can iconify(hide) a window without having an icon on the workbench. The icon on amistart bar for running apps just get shaded. Does this smell windows :)
and I would love a SLB which allows to select a linux partition to boot from..
edit: and a fix to the locale system, as it persists to use the second or third selected language for certain programs instead of the first one. Those apps are part of the OS (notepad, RAWBInfo, and some more) so I suppose there is a catalog for them.
@angelheart Some suggestions: * An option to "lock" AmiDock (and sub-dock) position, so I can't accidentally move it. (Too easyily move it at the moment, and then my sub-docks don't line-up.) * Sub-docks that automatically stay lined-up with the main dock (already implemented by Smart Docky, but it's transparency does not work). * ASL Requester with a volume list NEXT to the file/folder list. (This is one thing that MOS definitely gets right, and removes the need for the Volume button.) [* ASL Requester with alternating line colours, like Workbench's Name mode. EDIT: This was already an option!] * WBStartup Prefs should show priority of all icons, and allow directly changing that (without opening Icon Information window). Also fix it to actually order the items according to priority! * 3D OpenGL screen blankers (from OS4Depot) should be built-in to OS4.
and I would love a SLB which allows to select a linux partition to boot from..
The SLB supports this already, it just doesn't work on the SAM. The RDB filesystem IDs for Linux are different on the SAM Linux install to that needed on the old AmigaOne Linux install, so I suspect all that needs doing is an extra line of code to check another filesystem ID. If it helps the devs, the SAM Linux boot filesystem is EXT\03 (maybe it needs formatting as EXT2 as well, but on the AmigaOne the filesystem ID was something irrelevant like LNX\00)
ChrisH wrote: @angelheart Some suggestions: * An option to "lock" AmiDock (and sub-dock) position, so I can't accidentally move it. (Too easyily move it at the moment, and then my sub-docks don't line-up.) .
easy, just uncheck the autosave settings !
I am with you with subdocks being locked and with Kicko for hidden partitions drives that could be opened.
That's what I currently do, but it isn't very satisfactory, because I can make a change to AmiDock (e.g. drop an icon on it), and then wonder why it's lost next boot! Also, if I want to make any changes, I first need to remember to load "Last Saved" settings, or I will end-up saving AmiDock after it has been moved...
@angelheart Another suggestions: * Ability to specify a different filingsystem (e.g. FAT95) instead of CrossDos for USB memory sticks. * Add option to Prefs/PopupMenu to stop pop-up menus being "sticky".
I already tryed AutoDock but unfortunately it Hide the dock after x seconds ...I want to hide the dock whn the mouse left it... With auto dock time I have to do my things in some decided time and that's not nice... The Pop-Up time was also a bit too slow... And when AmiDock was hide it have the icon on Ws as iconified... ATM its no usefull to me sorry...
and I would love a SLB which allows to select a linux partition to boot from..
The SLB supports this already, it just doesn't work on the SAM. The RDB filesystem IDs for Linux are different on the SAM Linux install to that needed on the old AmigaOne Linux install, so I suspect all that needs doing is an extra line of code to check another filesystem ID. If it helps the devs, the SAM Linux boot filesystem is EXT\03 (maybe it needs formatting as EXT2 as well, but on the AmigaOne the filesystem ID was something irrelevant like LNX\00)
uhm..thanx for the info. AFAIR I used ext2 as filesystem for the SAM, would it help to change the filesystem in MediaToolBox to let's say SFS0? would it be recognized by the SLB then?
orgin wrote: Seems people are expecting Hyperion to basically create a new OS for the next 'update' rather than an update ;)
Yes, I'm sincerely glad Rogue has a tough skin and a useful arrogance when visiting the Amiga Boards of today...
No one seems to relish the moment anymore...
Ya know? the concept of enjoying using the best OS... everyone is tainted by a mass recognition of cpu idealism which in most cases I think is either overrated or misplaced... it is of course widely overused LOL
Keep it simple, keep it Amiga...
While all you lot have been moaning about this and that I've managed to compile all my favourite mud codebases and they function quite happily in the background with no freezes or grim reapers...
I don't know what alot of people do with there new Amigas but my machine rarely freezes and that only happens when I use IBrowse...
I'm seriously thinking of running my own Amiga Haven (on my spare SAM MB) but it'll be a mud with added zones of everything we'd like to kill for exp... heh I can think of quite a few Amiga Boards today I would like to turn into mobs and annihilate... laugh at yesterdays technology if you like but you can't beat timeless playability!
~Yes I am a Kiwi, No, I did not appear as an extra in 'Lord of the Rings'~ 1x AmigaOne X5000 2.0GHz 2gM RadeonR9280X AOS4.x 3x AmigaOne X1000 1.8GHz 2gM RadeonHD7970 AOS4.x
Good grief, why exactly would you want to disable APPDIR: it would have to be the single most usefull DOS feature since PROGDIR: and CURRDIR: were created.
orgin wrote: Seems people are expecting Hyperion to basically create a new OS for the next 'update' rather than an update ;)
Yes, I'm sincerely glad Rogue has a tough skin and a useful arrogance when visiting the Amiga Boards of today...
No one seems to relish the moment anymore...
Ya know? the concept of enjoying using the best OS... everyone is tainted by a mass recognition of cpu idealism which in most cases I think is either overrated or misplaced... it is of course widely overused LOL
Keep it simple, keep it Amiga...
While all you lot have been moaning about this and that I've managed to compile all my favourite mud codebases and they function quite happily in the background with no freezes or grim reapers...
I don't know what alot of people do with there new Amigas but my machine rarely freezes and that only happens when I use IBrowse...
I'm seriously thinking of running my own Amiga Haven (on my spare SAM MB) but it'll be a mud with added zones of everything we'd like to kill for exp... heh I can think of quite a few Amiga Boards today I would like to turn into mobs and annihilate... laugh at yesterdays technology if you like but you can't beat timeless playability!
yeah, sad isn't it?
As soon as I read the first moaning and complaining, the first thought that came to my mind was: now many developers will throw the towel!
Luckily many seem to be idealists or have still have fun or hope to get the Amiga back in the game and then get loads of money for this momentary path of thirst...
I'm not sure people get how hard programming stuff is, for some maybe it isn't, but for sure it isn't for all. And even if some still like to picture Hyperion, Ben Herman etc as bad guys, I wonder how they manage to finance all this. And I'm glad they do manage.
Good grief, why exactly would you want to disable APPDIR: it would have to be the single most usefull DOS feature since PROGDIR: and CURRDIR: were created.
Because to me its usefulness is very limited and doesn't justify its downsides (I gave more in-depth explanations here on AW.net).
I read it, it's rather pointed and uninformed, plus, I really can't believe you would be so reckless as to create scripts to manupilate the path cache and upload it to the public already, especially for purposes that are not even required, and for something you basically don't understand how it works.
Did you actually think that we would be stupid enough to create a bottomless pit of junk on your harddrive. ?
I will take a moment to mention a couple of things for what it's worth, I usually don't get involved on these forums, but this is an exception, whether it's of any use or not, I really don't care.
The APPDIR: server runs at a priority of -99 it does not affect normal operations, it operates asyncronously from the load process, so it does not cause any waits for the loader process, load events are sent as messages to the server for it to service when not much else is happening, besides, it only logs the path of applications when their data changes, not every time they are loadsegged.
The reason there are some extraneous files in the cache is because something other than ramlib LoadSeg()'ed them, this may be as simple as running the 'version' command over it, but whatever loaded it, it gets added to the cache when it's not loaded by ramlib.
The "hex" comment on the files in the cache are a quick 32 bit hashing value of the path string inside, the other number is the week number the last time it was used, this is so the APPDIR server can automatically flush dead entries after 6 months of no access, so dead entries won't build up.
I should take this opportunity to also mention that if the cache is disabled, you're going to need a large bucket of luck getting any of the pre-configured software to work.
None of the new URL: device settings will work, a bunch of extras on the CD won't either, nor will future automated update software work or anything that may use an installer script looking for the path of your application with; $(appdir/<application>)
Nevertheless, I understand it's your machine and you can cripple it anyway you see fit.
Well, of course it is uninformed: I'm not one of the AOS developers nor there is public documentation available.
Quote:
plus, I really can't believe you would be so reckless as to create scripts to manupilate the path cache and upload it to the public already,
If my script is unsafe, I have no problems removing it from OS4Depot. Just tell me.
Quote:
I will take a moment to mention a couple of things for what it's worth, I usually don't get involved on these forums, but this is an exception, whether it's of any use or not, I really don't care.
It *is* of use.
Quote:
The APPDIR: server runs at a priority of -99 it does not affect normal operations, it operates asyncronously from the load process, so it does not cause any waits for the loader process, load events are sent as messages to the server for it to service when not much else is happening,
Good implementation. Nice to know. Still, I'd be very happy if I was given the option of turning the server off
Quote:
besides, it only logs the path of applications when their data changes, not every time they are loadsegged.
Could you clarify this, please?
Quote:
The reason there are some extraneous files in the cache is because something other than ramlib LoadSeg()'ed them, this may be as simple as running the 'version' command over it, but whatever loaded it, it gets added to the cache when it's not loaded by ramlib.
OK, that's the what happens technically but... IMHO that's not what should happen since, as it seems, APPDIR: is just a user-oriented feature. Of course I understand that deciding what to take note of is hard, as understanding what the user specifically runs is not trivial.
Quote:
The "hex" comment on the files in the cache are a quick 32 bit hashing value of the path string inside, the other number is the week number the last time it was used, this is so the APPDIR server can automatically flush dead entries after 6 months of no access, so dead entries won't build up.
I wonder: why removing entries only because they're not used? They could be valid. On the other hand, since the server seems to already perform periodical checks, why doesn't it simply remove the invalid (i.e. containing wrong paths) entries as soon as it discovers them?
Quote:
I should take this opportunity to also mention that if the cache is disabled, you're going to need a large bucket of luck getting any of the pre-configured software to work.
None of the new URL: device settings will work, a bunch of extras on the CD won't either, nor will future automated update software work or anything that may use an installer script looking for the path of your application with; $(appdir/<application>)
Nevertheless, I understand it's your machine and you can cripple it anyway you see fit.
No problem: I do fine-tune and customize everything anyway.
Quote: Good implementation. Nice to know. Still, I'd be very happy if I was given the option of turning the server off.
Well, the mechanism is there, it's not that hard if you think about it, the server needs a -->DIRECTORY<-- called ENVAR:AppDir to be able to create the cache files inside it, if the server can't find a directory of that name on bootup then the server process simply exits politely.
You can see it with "Ranger" it's usually process #5.
Quote: Could you clarify this, please?
If the path changes or the week number it is run last changes, the cache entry is "refreshed".
Quote: I wonder: why removing entries only because they're not used? They could be valid. On the other hand, since the server seems to already perform periodical checks, why doesn't it simply remove the invalid (i.e. containing wrong paths) entries as soon as it discovers them?
If you havn't started a program even once in 6 months, it's probably safe to say that you don't use it anymore.
As far as entries with a bad path, they get flushed at every amiga day number that is a modulus of 31.