Windows 95 says 'item added' but item isn't displayed.
if i run kix32 when the session W95 is open and not in the login script the item is added and displayed ...

Help needed , thanks .

Can you please be more specific in what task you are trying to accomplish. I'm sure someone can help you further once we know what your tyring to do.

Are you trying to create a shortcut in a specific folder or something like that?

The "ifmember" section works well, the shortcut works on NT but not on WIN95.

Creating Shortcuts

Did this answer your question or help you accomplish what you were wanting to do?

Please post an update when you get a chance.

I dont want to add another program to create a shortcut, i just want to make the addprogramitem command work with Win95 like it works fine with NT4 when opening the session.

Windows 9x and NT/2000 are completely different and there are things you can easily do on one that you can not easily do on the other.

Lets see your code please and we will try to help.

Works fine for NT2K , doesn't work for Win95 when opening the session, works on win95 after being logged and executing the script.

Or even that the update is taking place, but then is being overwritten by a roaming profile?

- overdiden by roaming profile : NO.

This is about the only way to get around the profile not being loaded for the user at that point in time on Win9x.

HTH... Please post again if you need a better explanation or further assistance.

If not, then yes Marcilly you will need to code it to only install and run that once, or run everytime, but only add the link the once... what ever your needs dictate.

Hopefully we are only giving you food for thought and I don't think we mean to tell you what or how you must do it.

Anything you stuff in RunOnce does just that, runs once and then what you stuffed removes itself.

Anything you stuff in Run, runs every time until you remove it. It does not remove itself.

So, if you need to do something that needs to run after the logon script, but you want to initiate it from the logon, you stuff RunOnce during every logon. If under changing circumstances, you no longer need the post-logon script, you simply stop stuffing RunOnce.

I would think this to be preferential to stuffing Run, as you have finer control over it. FE, if you stuffed Run with a call to a script that needed to access a network share, and the user ran islanded (laptop or whatever) the share would not be accessible and it would error out.

All this, however depends on individual circumstance.

Marcilly,
Hope this helps. Sorry for the long dissertation. If you already know all this, sorry X 2. Now, back to the exam!