The new addition of WBStartup Prefs, that replaced the old WBStartup drawer doesn't really work for me very well.

Can I change to the old style? I believe yes. What I have to do, just delete the WBStartUp Prefs program from the Prefs directory?

I suppose that I can't have both, can I?

Last edited by Phantom on 16-Jan-2010 at 02:08 PM.

_________________

@Phantom

What problems do you have with it? Works fine here. I suppose you can create a WBStartup drawer and something in user-startup to run everything in it, but... why?

@MickJT

Apart from Wet, that I get Gurus at the startup, some small scripts I have with FKey refuse to work.

Last edited by Phantom on 16-Jan-2010 at 02:13 PM.

_________________

@Phantom

For compatibility reasons, I would have expected a WBStartUp drawer to still work if it is present.

However, it doesn't. The drawer gets locked by some process, which suggests there is something resembling old WBStartUp code still present, but nothing executes.

_________________
"Miracles we do at once, the impossible takes a little longer" - AJS on Hyperion
Avatar is Tabitha by Eric W Schwartz

The code that launches startup items from the prefs is the exact same code that launched programs from the WBStartup drawer since 1988 so there should be no "compatibility" issues.

If you really want to go back to WBStartup, delete the wbstartup.library, and recreate the wbstartup directory.

Last edited by rigo on 16-Jan-2010 at 04:38 PM.

_________________
Simon

Comments made by me on any public fora are not representative of, or on behalf of, any company I may have, or assumed by the reader to have, any association with.

Any comments are a personal opinion, and should be accepted as such.

@rigo

I had a small issue with WBStartupPrefs myself. I couldn't launch LimpidClock from the Work: partion. Moved it over to Utilities/ and it worked fine.

_________________
This sig. intentionally left blank

Hi,

if I remember correctely, removing wbstartup.prefs from envarc (and reboot) should work already. New WBS-process needs wbstart.library and wbstart.prefs. If one of those is missing, then it will fall back.

BTW, you can still store your icons in the Drawer WBStartup, even if it is not processed the old way. ;)

WBStartup-Prefs also alows dropping a drawer on it and will then add all its content. So you could dror wbstartup-drawer onto it eg.... ;)

CU,
Mario

_________________
********** AMIGA - More Than Just Standard **********

@rigo
I guess there are a lot more important problems to fix first, but I was disappointed to find that Prefs/WbStartup does not allow editing or reordering of the items.

I want to logically group items together, so Up/Down buttons would be very helpful here. (Drag N Drop even better, but I guess that'd be tricky.) At the moment it feels way too restrictive.

Since wbstartup.prefs is a binary file (yuck), you really need to allow editing of the added items. If I change the volume name of a partition, I don't want to have to delete & re-add all the relevant items. Directly editing their path would be so much ease. (An ASCII or XML prefs file would be a good alternative.)

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...

@rigo

Quote:

The code that launches startup items from the prefs is the exact same code that launched programs from the WBStartup drawer since 1988 so there should be no "compatibility" issues.

Well, AmigaDOS scripts don't get executed, though.

_________________
RETREAM - retro dreams for Amiga, Commodore 64 and PC

@ChrisH

Quote:

I guess there are a lot more important problems to fix first, but I was disappointed to find that Prefs/WbStartup does not allow editing or reordering of the items.

So how about if you open up the icon info and edit the boot priority, doesn't that reorder the list?

Quote:

Since wbstartup.prefs is a binary file (yuck), you really need to allow editing of the added items.

The whole idea of having graphical editors is to remove the need to hack away at scripts, this isn't Linux you know.

_________________
Simon

Comments made by me on any public fora are not representative of, or on behalf of, any company I may have, or assumed by the reader to have, any association with.

Any comments are a personal opinion, and should be accepted as such.

@saimo

Try an AmigaDOS script in WBStartup then, I doubt it will work there either. Why there was ever an option to "run from shell" when objects are in WBStartup is beyond me.

The launching of programns from WB relies on the workbench startup message, which is never sent when launching programs from a shell, hence the idea is broken by design.

The WBStartup stuff is balancing on the edge of a crumbling cliff, and I had to work very hard to improve the situation to where we are now. In future versions be prepared that shell programs won't run at all from WBStartup simply because they are two completely different mechanisms.

_________________
Simon

Comments made by me on any public fora are not representative of, or on behalf of, any company I may have, or assumed by the reader to have, any association with.

Any comments are a personal opinion, and should be accepted as such.

@rigo Quote:

So how about if you open up the icon info and edit the boot priority, doesn't that reorder the list?

Didn't work when I briefly tried it, before making that post. Will try again... (I guess it would make sense to SHOW the priority in the list, if that is what is supposed to be used to determine the order.)

edit: Tried it again, and still no joy.

Quote:

The whole idea of having graphical editors is to remove the need to hack away at scripts, this isn't Linux you know.

I didn't say an ascii prefs file was required, but it is an alternative if you don't want to add direct editing of item paths to the GUI (and I could understand why you might not). Maybe a better solution would be to allow opening of a file requester with the current item loaded, and let you edit/rechoose it using that? That would make most sense, and very easy to do I think.


But, actually I thought that was a great thing about the AmigaOS: Power of Linux, with simplicity of Windows. i.e. GUI for beginners, but easily editable/fixable for power users.

Why did someone go to all the trouple of implementing an XML library for OS4 prefs files (see AmiDock, ScreenBlanker, application_lib, etc), if not to allow editing them manually when required? A binary prefs file would be far more efficient...

And here's an *example* of WHY you'd want an ASCII prefs file:

When switching from OS3 to OS4, I wanted to transfer all my programs without reinstalling (since it shouldn't be necessary & I have far too many programs to reinstall even if I could find the original media & all the updates). Part of that required transferring my assignments...

...On AmigaOS3 I used to use MCP for my *vast* number of assignments (which are stored in ascii format), and since I had copied all my OS3 files over to identically named OS4 partitions, I also wanted the same assignments on OS4. I looked for some Assign Prefs type program that worked on OS4. I found two, one which used a binary prefs file, and the other used an ascii text file. So I picked the ascii prefs one, and with simple simply search/replace was able to get my MCP Assigns into the format it expected. This saved me manually re-entering 120+ assignments!!!

Last edited by ChrisH on 16-Jan-2010 at 05:37 PM.
Last edited by ChrisH on 16-Jan-2010 at 05:35 PM.

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...

@rigo

My biggest problems whit deficons system, is when you have made a tool to open file type X, and need to update or chanage deficons.prefs, there most be some tool or API one can use to add items.

I'm guessing we are going to have the same problem whit new startup system.

we need some thing like this:

update-startup FILE work:progs/icq/icq NAME icq TO end
update-Startup REMOVE NAME icq

update-deficons FILETYPE archive/lha FILE sys:utilities/UnArc
update-deficons FILETYPE acrhive/lha ADD MATCH LZX OFFSET 0 CASE TRUE

Last edited by NutsAboutAmiga on 16-Jan-2010 at 06:14 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@rigo

I discovered the problem precisely because I had a script (with the appropriate icon) which was correctly launched from WBStartup. However, sorry, it was an *AREXX* script.

Anyway, just to be clear: this is not a big issue at all - luckily scripts can be moved to / executed from the startup-sequence and the user-startup

_________________
RETREAM - retro dreams for Amiga, Commodore 64 and PC

@rigo

Quote:

Why there was ever an option to "run from shell" when objects are in WBStartup is beyond me.

Yes but the file has icon, and icon has tooltype.
the command wbrun handles it all.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@rigo

Quote:

The launching of programns from WB relies on the workbench startup message, which is never sent when launching programs from a shell, hence the idea is broken by design.

Just because they are launched differently, doesn't mean that it's invalid to want to run a script when starting Workbench.

For instance, I have a few ARexx scripts that modify Workbench's behaviour that I've been using since they added the port in OS3.5.

_________________
Doing stupid things for fun...

Why use a old fetures? Wait until devs release a new version of their support. Use you time to point these problems to the authors, not to restore the old method... which is old.

_________________
ikir

@ikir

Quote:

Why use a old fetures?

why use amiga and not win or linux?

_________________
A3040 AmigaOS3.9
A1200 060/BPPC AmigaOS3.9/4.0
Sam440ep AmigaOS4.1.2
Pegasos2/G3 AmigaOS4.1.2/Morphos2.7/Debian6.0/OpenSuse11.1
MacMini/G4 1.5 MorphOS 2.7/OSX 10.5.8

Long Live Amiga

@ChrisH

Nothing wrong with it being a binary file. There is something wrong with it being an undefined format though (it isn't even IFF PREF). Maybe it will be defined in the SDK when it materialises.

As for starting up scripts, just make them a project of IconX. That's always been more reliable than setting an icon to "start from Shell" anyway.

Chris

_________________
"Miracles we do at once, the impossible takes a little longer" - AJS on Hyperion
Avatar is Tabitha by Eric W Schwartz

@NutsAboutAmiga

You might want to check C: for WBS#?...
Might be a start.

CU,
Mario

Last edited by padrino on 17-Jan-2010 at 01:15 AM.
Last edited by padrino on 17-Jan-2010 at 01:15 AM.

_________________
********** AMIGA - More Than Just Standard **********