Chris Wiles was puzzled by a bug report..
> > Ouch! It does this not when you first select the file, but when you OK
> > the 'Edit Icon' window. As well as 'WB', 'DOS Script' also destroys the
> > file. I didn't try any more after that one.
>
> This is totally bizarre, and we simply cannot find the problem in the code,
> umpf. Still looking, but I have all my settings set to 'CLI', which I guess
> is why it never happened to me.
>
> Chris.
In the hope of helping you find the error, I've been looking into this
a bit more. The details of this are: (on my setup, at least)
You can change the program, its icon, etc etc and it will be fine.
Various read-locks are attempted throughout this which are ok.
When you select "OK" or "Cancel" to the "Edit Icon" window, OR close
it, there will be a successful *write*-lock to the program to be
executed,,leaving a filesize of zero. The ONLY instance in which this
doesn't happen is when the type of execute was "CLI" and *remains as*
"CLI". _Changing_ to or from "CLI" will still cause the error.
Keeping the execute type the same when its anything other than CLI
will still cause the error.
ie: In every case except the "Documentation" icon the user can safely
select a different file from the default config, provided he does not
change the execute type. As soon as you try to edit the Documentation
icon from the default config you are guaranteed to lose it.. :-(
You can safely create new entries provided you don't touch the default
"CLI" setting.
Hoping this will help get us all a *quick* bugfix,
Regards,
Ian
===
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
