Comments for Remote Internet Connect

09 Oct 2002 14:18 fastrack

Nice Program
I LIKE IT, it's a nice program.....

Easy for your family to use,
that's most likely the problem at
our place ;-),

Greetingz,

FasTrack

16 Sep 2002 06:20 hotten

New maintainer
Hello!

I'm the new maintainer of RIC, I use it a lot and I want more features wich I will try to make.
Soon I will release a couple of updates for RIC.
A friend of my will open a form soon so if you want to discuss about new feature it should have, or something else just do so.

Regards,

Harry

30 Apr 2002 10:15 leroy152

The future of RIC
I'm really happy with how RIC has turned out, it started out as a quick hack to make life easier for the other people in my house, and turned into a tutorial for me to deal with things like *nix programming and *shudder* VB =).

This latest version (0.5), will probably be the last, unless bugs appear. All of it (to my knowledge) works, and works well, and I don't think there's much else I can do to improve or add to it.

So yeah, have fun with it, add to it to suit your needs, write new clients, delete it, whatever =).

Cheers,

leroy.

12 Mar 2002 05:24 leroy152

Whoops slight mistake there...
I forgot to update the link to the 0.4 tarball for the release. Hopefully it'll be updated soon, 0.4 has some minor changes but it's worth upgrading to.

16 Feb 2002 22:18 leroy152

Re: win client error

> Correction - I should have phrased my
> statement better... performing the
> MSWINSCK.OCX procedure did succeed in
> registering the file. I did get the
> "file successfully registered" message.
> However, even with that being
> successful, I still received the "Failed
> to load control 'winsock' from
> MSWINSCK.OCX..." error (yes, I rebooted
> the PC to be sure). So, the web page fix
> itself was good, but RIC still didn't
> work for me. However, after a Google
> search I found another MSWINSCK.OCX on
> this web page -
> http://lettermanstationery.tripod.com/vbruntimes.htm
> - I registered that and tada! Now RIC
> works!
>
> Thank you!
> Tony


The daemon is pretty much complete, I think only bugfixes will be applied to it now (unless a feature smacks me around the head =), so my priority for the next release is to replace the VB client, with either a MSVC version or even a Java version.

Cheers,

leroy.

16 Feb 2002 11:33 tgroff

Re: win client error
Correction - I should have phrased my statement better... performing the MSWINSCK.OCX procedure did succeed in registering the file. I did get the "file successfully registered" message. However, even with that being successful, I still received the "Failed to load control 'winsock' from MSWINSCK.OCX..." error (yes, I rebooted the PC to be sure). So, the web page fix itself was good, but RIC still didn't work for me. However, after a Google search I found another MSWINSCK.OCX on this web page - http://lettermanstationery.tripod.com/vbruntimes.htm - I registered that and tada! Now RIC works!

Thank you!
Tony

16 Feb 2002 01:41 tgroff

Re: win client error
Yes, I got the same error too. I am very interested in trying this program. Running the client on Win 98, I have no knowledge of the "VB Winsock control" thing. I tried the fix on the web page above, it didn't work for me, still get the error. I'll keep an eye out for the web page with instructions, thanks!

14 Feb 2002 23:12 leroy152

Re: win client error

> When launching the windows client I get
> this: Component 'MSWINSCK.OCX' or one
> of its dependencies not correctly
> registered; a file is missing or
> invalid
>
> Using WinXP pro.

Hrm, yeah, I should've added that it requires the VB Winsock control, MSWINSCK.OCX. I was tossing up whether to include it in the tarball, and decided that it shouldn't be included. I then forgot to mention that in the README.

I'll put up a proper webpage for RIC soon enough.

Cheers,

leroy.

14 Feb 2002 14:18 hotten

Re: win client error

> When launching the windows client I get
> this: Component 'MSWINSCK.OCX' or one
> of its dependencies not correctly
> registered; a file is missing or
> invalid
>
> Using WinXP pro.


I got the same messages with win 2000 pro.
This page has the file that fixed for me

http://www.ascentive.com/cgi-bin/click/MA105/support/2126DownloadList.html

goodluck


14 Feb 2002 11:22 derge

win client error
When launching the windows client I get this: Component 'MSWINSCK.OCX' or one of its dependencies not correctly registered; a file is missing or invalid

Using WinXP pro.

Screenshot

Project Spotlight

ReciJournal

An open, cross-platform journaling program.

Screenshot

Project Spotlight

Veusz

A scientific plotting package.