Yeah its vb.net but I have no problem with it ! Thank you very much :rose:

yeah, thank you :D! But 1 Problem remain... How could I draw under it without set the focus to the Form? :confused:

Hey guys, is it possible to load a .jpg on a form and make it transparently to sketch it in paint or somewhere else? The picture should always stay in the foreground, but I want interact to the window under it. any suggestions? :doh:

Yeah I know! I already tried this, without success! :)

Yeah I already tried this, but doesn't work.. I tried "any cpu" / "x86" / "x64" to build.

Thanks for your replies, it seems that the .exe need the manifest. Now it works =) /closed

sry I don't know what you mean. :doh:

Hi, I made a tool to read a .mdb File, everything works fine except on a 64Bit Machine... To connect to the database I use OLEDB 4.0, but it seems that 64x does not provide this. How could I compile this compatible?? :doh:

OleDbConnection con = new OleDbConnection(
@"Provider=Microsoft.Jet.OLEDB.4.0;
Data Source=" + lblDATABASE.Text);
con.Open();

Hey guys, is there a possibility to create .pdf files with the command line? (User shouldn't see what happen) the reason: I create a Word file from a .dot pattern and paste many rich text files to it (.rtf) after the .doc have been created, it should be converted to a .pdf... :( (that happen in a software)

"play" means the user is on the server with remote software.

Yes I know... But I solved this otherwise! easier :laugh:

Nobody try to hack into it... its just ja medium that both (Laptop & desktop) can reach... But would you give an user the chance to "play" on a server? :confused:

Well... ... thanks a lot but you don't know what I mean :laugh: I solved this otherwise 3 *.exe 1. starter.exe *new* 2. RemoteStarter.exe (some Telnet function to start Software on other systems) 3. WOL.exe There is no other solution... or how would you solve something like this when a user is not allowed to use VNC to view the server. And they know nothing about wake on LAN ;P

It doesn't work... I try to describe like you :P 1. Laptop: run starter.exe 2. Laptop: starter.exe start wol.exe with ip adress of the desktop 3. Laptop: starter.exe terminates now the problem begin 4. Because starter.exe runs wol.exe the wol.exe will run on the laptop... what should do: 4. Server: runs wol.exe 5. Desktop: boots 6. Laptop: connect to desktop and is ready for action --- for example sitting in school your neighbour looks bored then you start a program like media player and this program should pop up on HIS screen not yours! If I start media player (installed on his desktop pc) it will pop up on my screen, this I wouldn't have...

just nickname :P real name is different ;P oh no, what you must think about germany :doh:

wuah :doh: again: I sit with my laptop in the sun, enjoy the sun :laugh: connect to network with vpn. Now I have a connectivity to the Server. I want to work Remote on my desktop pc from work. But the desktop pc is turned off. Now I want to start my desktop pc to connect to it! I start "starter.exe" and my desktop pc turns on. ----- Now how I realize this: I have 2 .exe 1. starter.exe is on my laptop 2. WOL.exe is on the server ----- Now how my tool works: starter.exe start the WOL.exe on the server with IP or MAC adress from my desktop pc as a parameter. WOL.exe sends a magic packet to desktop and this turns on! ----- Problem: starter.exe starts on my laptop starter.exe starts wol.exe which lay on the server but if starter.exe start wol.exe, wol.exe will be started on my laptop instead of the server. And cause my laptop is in an another subnet my laptop can not root packets directly. I hope this would help ;P

starter.exe send parameter to the wol.exe on the server and start it. But if I start the starter.exe local on my laptop, the WOL.exe will run there, too.

Well... 1. If the Laptop start the WOL_starter.exe the WOL_starter runs WakeonLAN.exe (from server) local on the laptop and this laptop can't communicate to the desktop PC! ;) so some error occurs. The User (Laptop) just should start my starter.exe and his desktop should turn on. They have no permission to connect to server via remote. The server should start his program on his system not on the Laptop :laugh:

heey!!! xD which coincidence you excactly mean :laugh:

1. Laptop: runs WOL_starter.exe 2. Server runs WakeonLAN.exe 3. Desktop boot 4. Laptop use remote-desktop on the Desktop pc There are 2 *.exe -- 1. WOL_starter.exe -> *.exe on the Laptop -> communicate to the server and start "WakeonLAN.exe" with parameter IP. 2. WakeonLAN.exe -> *.exe on the server -> send WOL message to the Desktop PC