4 replies to this topic

[marinomarini111]

Hey there,

just found your site some days ago,
and while these days I experimentated a little with Winbuilder an LiveXP.

My aim is to autostart in a fullscreen rdp session.
The problem is, that the PENetwork takes some time to engage,
more time than the rdp client is going to retry, so it stops with connection failure.

I watched around and found that maybe the easiest way to delay a programstart
is to make a .bat(ch) and take a workaround with a ping for some seconds.

My problem now is, that I just dont get it working to implement the .bat in the build,
and so I dont know how to autostart it, because I cant find out if it is implemented,
and if it is, where it is located. (to give the Add_Shortcut,AutoStart a correct foldername)


I would appreciate if you could help me,
I think its a tiny thing, but I am not so connected to scripting,
maybe you can tell me how the "abstract" foldernaming works!

Thx a lot and best wishes!

[homes32]

This topic should give you a couple places to start.

You basically have the following options:


1.
If you use PENetwork.exe exculusivly then the eaiseest is to add the following info to your PENetwork.ini profile to have PENetwork autostart your program when it has finished networking.

[PENetwork]

...

[ProfileXYZ]

...

CMDStart.CMD1=YourRemoteDesktop.exe /Your parameters

CMDStart.Start1=hidden

CMDStart.Wait1=No

2.
use a batch file or autoit script to wait until network is detected and then run your program. This method is more complex but more flexible if your script needs to be compatible with projects not using PENetwork.exe (typically only advanced users with special needs will use this method. its much easier to use PENetwork profiles.)

welcome to the community!

-Homes32

[RoyM]

Hey there,
just found your site some days ago,
and while these days I experimentated a little with Winbuilder an LiveXP.

Welcome to the forums marinomarini111

My aim is to autostart in a fullscreen rdp session.
The problem is, that the PENetwork takes some time to engage,
more time than the rdp client is going to retry, so it stops with connection failure.
I watched around and found that maybe the easiest way to delay a programstart
is to make a .bat(ch) and take a workaround with a ping for some seconds.
My problem now is, that I just dont get it working to implement the .bat in the build,
and so I dont know how to autostart it, because I cant find out if it is implemented,
and if it is, where it is located. (to give the Add_Shortcut,AutoStart a correct foldername)

Try a look here how to autostart:
http://reboot.pro/14319/

I would appreciate if you could help me,
I think its a tiny thing, but I am not so connected to scripting,
maybe you can tell me how the "abstract" foldernaming works!
Thx a lot and best wishes!

Are you asking about the foldernaming / Directories and sub-Directories
withing the WinBuilder Directory.
If you have questions you can always post back

RoyM

[marinomarini111]

This topic should give you a couple places to start.

You basically have the following options:


1.
If you use PENetwork.exe exculusivly then the eaiseest is to add the following info to your PENetwork.ini profile to have PENetwork autostart your program when it has finished networking.

[PENetwork]

...

[ProfileXYZ]

...

CMDStart.CMD1=YourRemoteDesktop.exe /Your parameters

CMDStart.Start1=hidden

CMDStart.Wait1=No

Thanks a lot,
this worked perfect and fits all of my needs! I dont think that I will need anymore options, cause I am just looking for an boot up a slow machine and connect to a strong machine OS.

Are you asking about the foldernaming / Directories and sub-Directories
withing the WinBuilder Directory.
If you have questions you can always post back

RoyM

Yes Roy, I also would like to know how the abstract / variable folder naming works, especially when I try to start / work with system files. So is the systemroot called "#$pSystemRoot#$p" but sometimes it seems (for example in the PENetwork.ini) that you have to take "%SystemRoot%".
This is a little strange (for me, of course ).

Also do I not know exactly where files will be located after I added them with a script. I think in Programs under the folder which is named like the project?


Thx anyway so far! U are great!

Edited by marinomarini111, 30 April 2012 - 01:15 PM.

[homes32]

#$pSystemRoot#$p
and
%SystemRoot%

both point to the same location...but #$pSystemRoot#$p will only work in a winbuilder script as #$p is a special escape character translating to % and is unique to the winbuilder script engine. you should always use %SystemRoot% unless you have a scripting issue that requires you to use the escaped version.

ps. glad you got your autostart working as you required!