Hi all,
I have put Lapwing 1.0 RC1 up at this address:
www.sourceforge.net/projects/liberta
It DOES have a number of issues. I would like to ask you all if when you use the application you run Regmon n the background and then post up the details of the last attempted write of that program, e.g. the attempt that failed. This should help me to pin down a munber of bug. Note file names with spaces are not supported at the moment.
I'll post some more information later of tomorrow as I'm in a bit of a rush.
Steve
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Google Talk fails to open with the error: Spy_dll: Can't load options from run.set.
Regmon says that it fails whenever it tries to open a RegKey And gives result, Not Found.
EDIT: Everything I run gives the "Can't load options from run.set" error.
If I create blank run.set files, the application runs but writes and reads the registry.
What should I put in my run.set file?
put that in, I'll re-upload tomorrow. Sorry
Yours
Steve Lamerton
In the readme it might help just to give a little explanation of things like going up one directory in relative paths, and things like that.
should be up now, you'll have to wait 5 or 10 minutes for it to seed though. As for the documentation, that'll be in the final release.
Yours
Steve Lamerton
Now Google Talk gives This Error and Regmon says that google talk did not attempt to write anything, but it did read stuff. How does Lapwing find initially decide what RegKeys to include in the ini file? (BTW: Lapwing created no registry ini file.)
I'm getting errors like that too, I was hoping it would only be me. I'll be putting out a new version later with some updated bits and pieces.
Yours
Steve Lamerton
I'll get the icons to you ASAP.
----
R McCue
PortaBlog Home and My Website
And before anyone complains about the grammar, I'm so jetlagged that my
hands aren't even in the same time zone...
"If you're not part of the solution, you're part of the precipitate."
*punches the air* *claps hands* *cheers*
RC2 coming up soon, no more of those errors. Give me a couple of hours.
Yours
Steve Lamerton
*Runs around the room screaming and cheering*
I'm afraid you'll have to wait till tomorrow, I've decided to delay a little, the extra time will allow me to keep the directory structure nice and neat.
Yours
Steve Lamerton
P.S. You should have seen the last of the memory exceptions and warnings
What's wrong with the directory structure?
What was funny about the memory stuff?
in RC11.1, but I fiddled around with it a bit for RC2 so that each app has there own INI and other such bits and pieces. Secondly nothings funny, I'm just happy that those bugs are gone.
Yours
Steve Lamerton
Thanks.