PureBasic Forums - English

Updates:

Veo 1.0.8 Merged Wan & Lan modes
Increased Max speeds up to ~60 FPS
Link Accelerator (persistent cache)
note you can't record screen with cache active

Veo 1.0.7 Single click mode added for Wan connections

Veo 1.0.6 Auto IP discovery over LAN
Improved LAN Mode up to 25 FPS

Veo 1.0.5 added Event driven update

Veo 1.0.4 Bug Fix release fixing issues with system keys

Veo 1.0.3 added Folder Transfer

Vere 1.0.2 removed start as admin as was blocking file transfer

Veo 1.0.2 added 256 AES encryption

Veré 1.0.1b fixed window key bug

Veo 1.0.0 Added file transfer:

Veo 0.9.52 fixed mouse cursor:

Veo Remote suite 2000,XP,Vista

"veré verás, vio"!
Veré - (I will see) - Remote desktop viewer / server
Verás - (You will see) - Remote Desktop Client
Vio - (It saw) - Session player

Why Veo Remote.

Better Visual Acuity, See more for less

Higher Compression, the veo encoder is specifically designed for desktop capture taking full advantage of the inherent redundancy of the typical desktop. Veo encoder compresses up to three times more on average over standard lossless compression methods. Meaning you see more for less, making it ideal for remote help and screen recordings.

Records Sessions for playback.

Verás simultaneously records sessions, so your client can play it back to
see what you did. It's also handy to make a quick demo.

No hacks It doesn't employ any evil system hacks. No mirror Drivers, No global hooks, No installation or Registry entries and poses no undue risks to your clients security.

Slim Veo remote suite is only 420kb

Written in PB C fasm

OS

2000, XP , Vista, Windows 7

Feedback

If you would like to give me feedback to help improve Veo Remote please either pm me or send my an email .

Cheers Idle

credits:

Thanks to all who have helped, directly and indirectly.

Demivec (porting)
Henrik (testing)
Helle (asm)
Kcc (for good laughs)
Netmaestro (8 bit image, useful code snippets )
Pdwyer (discussions, testing)
Rook (banter)
Sparkie (Cursor code, useful code snippets )
Srod( A lot )
sfxsOI & Trond (Arguing over BSOD but at least both finding the time to tell me it wasn't my fault)
Rings (for looking like Moss, and timely answers to questions)

And a real big thanks to the whole PB team for making a great compiler and supportive programing community.

Idle,

Thanks for posting. I work in an environment with 2000 and XP and will try out your veo.

Kcc (for good laughs)

Thanks thanks it's really too much honor
The little name of KCC in the middle of all this great name of god like you and them
Thanks very sincerelly to your kindness, i'm very proud of that.

Cooooollll !!!
I go to try your splendid soft

He works very good.
Best fluidity

I have try this, in local network only for the moment.

If i can say several first comment.
The advantage to let's try soft by KCC, it's he so null, that if KCC can use, all the world and even all the planet can use it

First point
Well, i have a little bit difficulty to understand if i must install véré or vera in the client.
I know, you explain that in your site, and also in the titleBar, but i believe it's better if you add a picture to explain in one second, if is the client or the server.
Or again better, because even client and server don't talk really to me

A picture like an eye, or a camera (for example) to say what is the soft to put on the computer who watch the other computer.
I have no idea for the picture to the computer to be watched :roll:

Or all other picture
A remote of TV for the soft who watched
And a TV for the soft who be watched

Or another idea again ....
The first it's that in one look, we know who do what

It's true several programmer forget that his client is mule and don't know clic on a shortcut
With picture, it's an universal language, because you go laugh, but my friend GOOGLE translate nearly the same sentence between "I will see" and "you will see"

Second point
Other in the computer who is watched, the desktop background picture disappears when your soft works.
When i stop your soft, the desktop come back like before
It's perhaps normal, it's just for info

Third point
If i don't touch anything and i click connect with 127.0.0.1, the program loop hitself.
I believe that a protection must be created

Other, again congratulation, this soft be surrely usually for me, because i don't count the several times, who i help another person, who is again less strong that me (Yes yes this person exist ) , i promise you
Install VNC, is too long, and i don't know how to do, with the internal command of XP [/u]

Thanks Kcc

First point

I will make a video tutorial

Second point

I assume that clients don't really want to share their desktop background over the internet, it's often personal information plus it's slow to transfer.

what if a clients desktop background was the Hoff do you really want to see an exposed Hoff! No!

it saves bandwidth!

Third point
If i don't touch anything and i click connect with 127.0.0.1, the program
loop hitself.

That's normal, it enables you to "Record" your own screen but you do need to ensure that "Input" is unchecked before looping back.

I'm going to try this thing in Windows 7 later today or tommorw.

I tested it on Windows 7 but only on 32 bit.

I'm using 32 bit Windows 7 also.

Veré 1.0.1b fixed window key bug

Pressing the window key would activating the short cuts but not release them, leading to unexpected behavior and an inability to type text.

Pressing the window key should now pop up the start menu.

Tried it out last night in windows 7 - worked just fine.

Veo 1.0.2 Added 256 bit AES Encryption

I'll only be impressed when an app like this can work through a corporate
firewall. So I can remote control my PC at home, from work. But I doubt
such a thing will EVER exist.

PB, it already does if its allowed thru.

I obviously mean when your workplace DOESN'T allow it through.

Probably my ignorance, but I have not been able to transfer a file. A step by step instruction might help.

Is it limited to IP Address access? Not possible ot enter a URL?

The listening viewer "invites" the remote end to access it. The listening viewer has no way to reject access? What if a second access is attempted? Will the viewer accept it too?

This seems reversed to me. The listening viewer should wait for an invitation to view the remote, have the ability to accept or reject the invitation. The session then controlled and initiated by the user willing to allow his system to be viewed/controlled.

There are some great ideas here, and I hope to see it grow.