Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Homes32

Pages: [1] 2 3 ... 6
PEBakery / Re: Request: PEBakery Help Document
« on: Today at 12:19:45 PM »
Something we miss for years now:
(current help files around have lots of missing and wrong info but still useful for now ... )
As one of the primary authors of WinbuilderN.chm I would be interested in knowing what info you believe is missing/wrong. Taking into consideration that the API Commands section refers to the old CAPI and not it can be added/corrected.

I hope you can start same way with PEBakery.

Check out the github repository:

once the documentation is more mature the markdown files can easily be converted to html for publishing to the web or compiling to a chm.

I feel It will be nice to get cmd applications have Echo on log  :thumbsup:
Maybe as default PEBakery can detect cmd application and follow output with something like Echo lines.
This will give us more ideas .....
This is already possible with c#
something like this
Code: [Select]
proc.StartInfo.UseShellExecute = false;
proc.StartInfo.Verb = "Open";
proc.StartInfo.WindowStyle = ProcessWindowStyle.Hidden;
proc.StartInfo.CreateNoWindow = true;

//  redirect stdout/err to buffer
proc.StartInfo.RedirectStandardError = true;
proc.StartInfo.RedirectStandardOutput = true;

   // read the streams and do something with them
while (!$proc.HasExited)
so not a question of "can we do it?" more of a "what is the most useful way to present the information for view/logging with minimal to no impact on performance?"

ps: The only reason I did not implement to Macro Library with tee.exe was to avoid another False Positive AntiVirus or Firewall .....
you hit another reasoning right on the head!  :thumbsup:
Anytime you add an homemade or external program to the mix you have the very likely possibility for sloppy/lazy/stupid antivirus vendors to flag your exe as a false positive.

PEBakery / Re: Request: ShellExecute - Process Priority
« on: Today at 11:18:42 AM »
IMHO I don't believe this would be a good idea. unless your still running Windows 9x its unlikely a script/plugin author knows better then the OS process scheduler what is the best use of resources. couple this with the possibility for ignorant users seeing the option and deciding they need to run their process in real-time priority, because hey! it should be the fastest right!?!?!

and again unless your on a really old system < P4, CPU resources when building generally isn't going to be an issue unless you routinely edit/render/encode video, are into heavy graphic design rendering, or feel the need to run prime95 wide open on all your cores while you are building your PE. If your running into slowness then its more likely related to paging/RAM/slow hard-drive/etc and adjusting the processes CPU priority isn't going to help you there.

PEBakery / Feature Request: StdErr & Stdout when using ShellExecute
« on: December 13, 2017, 03:28:26 PM »
On my wish-list since "forever" has been a way to redirect stdout/stderr into the builder, or at least log the output without using tricks like running from .cmd/.bat using redirection or using an external app to pipe them off and tee the output to another file for programs that don't write their own logs.

I hate with the fury of a thousand suns when applications/console windows/etc popup during a build, steal focus, annoy me while I'm trying to work on something else, etc. My brain likes to be busy, so I usually run the builder in the background and work on something else in the meantime. However some applications do display useful information while running (makeiso is a good example), so developers feel the need to run them "unhidden".

I see several possible options:

1. Always log stdout/stderr to the log
2. Publish the current contents of stderr/stdout to a small text area on the progressUI possibly under the messages section. This would be useful for programs like makeiso, 7z, etc that show progress that may be useful or entertaining. Also output to log. [See attached screen mockup for a crude example.]
3. Global builder setting to toggle logging of stdout/stderr
4. Add an optional argument to shellexecute telling PeBakery what to do with stdout/stderr
5. Return the streams in a variable for the developer to deal with. (I don't see much value in this. double yuck if the program has a large output this could cause unwanted slowdowns/hangs)

I prefer option #2  :smile:

This could possible cause a small amount of overhead reading the stream and flushing it to the log (as with any logging action), but I would much rather have everything in one spot if possible.
real-time reading of the streams would be preferred to just collecting them in a buffer and dumping them the log at the end of the process, to avoid having the builder to hang if the called program has a large amount of output.

Discussion is welcome. If something solid can be agreed on I will submit a ticket to the tracker for future development.

PEBakery / Re: GetParam, PackParam
« on: December 12, 2017, 08:29:53 PM »
I think the main reason why the PackParam command was introduced because there was no way of knowing how many parameters had been supplied. This command allowed for (a) a check within the supplied parameters for a certain string (used in Gena for registry injection at boot); and (b) a way to determine the total number of parameters (but this wasn't used and in reality may not be practically useful).

It had more to do with the Run command not accepting more then 9 parameters. I remember it because pedro was having issues with that when he wrote the CAPI. the whole Get/Pack was buggy as hell in ver 80 :( I woulden't cry if it went away.  :wink:

PEBakery / Re: PEBakery Test Build
« on: December 10, 2017, 09:12:45 PM »
2. UI Controls to be deprecated
I cannot find usage of CheckList in Win10PESE.
If there is no demand for this, can this be deprecated?

Ideas about new UI control is also good.
CheckList very rarely used,
here is last time I see:
Downloads\AppYGS\HD Tasks\Runtime Software ALL

Aside from that Runtime Software implementation I have never seen checklist used outside my personal test cases (mostly back in 2009) The feature was undocumented (even psc didn't know how it worked) and apparently Runtime and I were the only ones to ever figure it out. Even then its rather clumsy to use as you have to IniRead itself to get the values so I could never actually come up with a use case that made sense. In less time you could create a handful of standalone checkboxes to do the same job without all the work to setup the loops and inireads. Less code = faster and cleaner scripts.

You can do some really cool things with it though like dynamically switch the list contents based on the value of another control. see example below:
Code: [Select]
Title=Checklist Example
Description=Shows how a checklist can be used

Message,"Is cat selected: "%isSelected%, INFORMATION






because this behavior has potential to be useful I don't know that I would say get rid of it forever, but I would definitely back-burner it while more important things are worked on.

PS thanks for the quick work fixing the combobox run actions :)

Other World / Re: All good things must come to an end
« on: December 09, 2017, 05:07:11 PM »
It's been a pleasure working with you all these years ChrisR. Best of luck with the new endeavor!
No doubt our paths will cross again. We never truly leave, Even with a new baby I still poke in here and other places to lurk a bit now and then.  :cool: Family is always the priority though and I truly do wish you the best of luck and happiness.


Win10 / Re: ShutdownPE
« on: March 09, 2017, 04:22:22 PM »
Pecmd hooks in automatically. It uses the normal restart and shutdown options on the start menu.

So does ShutdownPE. Whats your point?

This thread is about a user wanting the additional features of ShutdownPE.

PEcmd does not:
  • give the option to eject cd/media on shutdown/reboot. Something the OP desires
  • allow you to lock the screen
  • perform a safe shutdown after flushing all buffers to disk
  • allow you to run a user defined program or script before shutdown/restart
All things ShutdowPE does.

Forum Support / Attachment Error
« on: February 27, 2017, 02:20:12 PM »
When trying to attach a file to a PM I get the following error when sending the message

The attachments upload directory is not writable. Your attachment or avatar cannot be saved.

The send fails and I get the message regardless of whether I have checked "Save a copy in my inbox"

LiveSystem pro / Getting started questions
« on: February 20, 2017, 01:40:28 PM »
Please excuse me if these questions have already been answered somewhere. I'm a native English speaker so the German forums are hard to follow sometimes.

A few questions as I'm experimenting with LSP.

  • Is there planned support for attachments/embedded files?
  • Are feature requests/fixes/but submission welcome and if so where should they be posted
  • What is the dev process for LSP? is it just kare in his freetime or is it a collaborative effort?
  • Projects have both a and Project.cfg - The 2 files are nearly identical but the editor only opens what is the purpose of Project.cfg?

Thanks :)


LiveSystem pro / Re: English Tutorial with Syntax of LiveSystem pro
« on: February 07, 2017, 02:25:57 PM »

As far as I remember this command does not exist anymore, as the progress bar is always shown.

ok that would make sense then. I saw it in a few scripts when I was poking around and wondered if it had anything to do with redirecting progress from an external application.
can you tell me why the progress bar changes colors from green to yellow?

LiveSystem pro / Re: English Tutorial with Syntax of LiveSystem pro
« on: February 07, 2017, 01:27:50 PM »
Code: [Select]
appears to be undocumented. Its missing from the English pdf in the 1st post and also from the LSP help file.

Win10 / Re: ShutdownPE
« on: February 02, 2017, 10:40:14 AM »
found it. pretty sure this was the GA release. let me know if something is borked. I dusted off the code and have been tinkering with getting kb controls (tab/enter) working for v1.6. something I have wanted since forever but MS has made difficult with icon controls.

Development and code snippets / Re: USB7ice
« on: January 28, 2017, 02:15:55 PM »
looks neat. interesting that you chose purebasic.

can you please dial back on the transparency a bit? its quite distracting on my "busy" (n. see messy :) ) desktop.

Win10 / Re: ShutdownPE
« on: January 28, 2017, 12:02:19 PM »
its good to be back! :)
I changed jobs a few years ago so it cut into my developing time considerably lol and I was married this last Feb so my wife demands my time as well!

my old wb subdomain and download  is acting up so give me a bit to dig up the last published script (plugin for lancelot :) or compile a new one.

nice to see you still around :)

Win10 / Re: ShutdownPE
« on: January 28, 2017, 11:41:18 AM »
ShutdownPE was never updated to work with Windows 8/10, so I would not recommend using it.
Not true. ShutdownPE was updated for Win 8.1. the latest release is 1.5.x and was posted back in Jan of 2015 script version is .17
I do not know why chrisR continued to use the old 1.4.x version. He never reported any issues on the 1.5 beta. as far as I am aware there are no outstanding issues with 1.5.x

as far as I remember ShutdownPE was created to be sure hd was first flush than shutdown. And a nice menu for shutdown.
( Later more integrated ...)

ShutdownPE was originally written for and was the fist GUI for Win7PE. Before shutdownPE the only way to shutdown/reboot was to create shortcuts directly to winpeutil.exe and there was no way to eject CD's
ShutdownPE fulfilled this need and added the additional safety of flushing file-buffers and the option to run additional programs before shutdown (ie unmount, save logs, etc)
a bit later if added integration into the start menu shutdown/reboot options (which were previously non-functional) so the start menu was usable and had the benefit of flushing buffers, running scripts, ejecting cd's etc.

Win7PE SE HomePage / Re: Script has no certification
« on: January 28, 2017, 10:40:48 AM »
And Homes32 , we change name to plugins it is much more accurate name than script
 and also it splits very old than new, old script not supported by us, we use and develop plugins on projects

So Homes32 , use plugins terminology around here.  :cool:

well I may have to respectfully disagree on the "more accurate name" point. espically when the builder itself consistently refers to them as script (even in file extension). if that was the case we should call them "instruction-sets-that-sometims-included-encoded-binary-executables"  :tongue: :w00t:
in any case it really doesn't matter what you call them, the function is the same and I'm getting off topic lol.

As far as I read, it was also used to avoid anyone use winbuilder ! nice for a "free" project,
 Good to see AutoIT development did not do such thing....  :wink:
afraid i'm not sure what your talking about here. nothing stops anyone from removing the certification and wb certainly doesn't refuse to process a script that isn't "certified"

my point with the certification not fully realized was mainly the fact that it was so easy to disregard. I still have my copy of my signature file and the certify.exe and used to certify all my scripts only to see the signature stripped out *EVERY TIME* someone added my script to their project. Since I developed mainly core scripts and applications (such as VisualC++/ShutdownPE/etc)  it made the process pretty worthless. The only thing it was really good for was if a user wanted to "feel good" that they had the original released version or if a project developer wanted to say "I refuse to help you unless all your scripts are certified in the original form"

Its good to see you again old friend.

Win7PE SE HomePage / Re: Script has no certification
« on: January 27, 2017, 09:49:44 AM »
the message can be safely ignored and as lancelot said, if you don't turn on certain debug options they won't show in the log.

The original idea behind the certification process was to give project developers a way to digitally sign (the actual implementation is actually just a salted checksum of the contents of the script file excluding certain sections) their scripts so it was easy for them to tell if someone modified them and ease support. (a large portion on the time the issues were caused by either the user modifying the script code and having trouble or another project adopting the script, modifying it and the user thinking it was the original authors problem)
the certification was never really finished to completion although the checksum did work and was not widely adopted due to disagreements on how/who to distribute "keys" to among other issues. That coupled with the fact that due to the open nature of the script files a user could just delete the 2 lines that contained the certification verification data and invalidate anyways the only real use was for the developer to say "not signed by me I'm not supporting it" which wasn't in any of our blood.


Win8.1 SE HomePage / Re: Odd Clearlock Issue
« on: August 26, 2014, 09:51:08 AM »
I'll see if I can find anything out. It may take me a little while because my time is limited at the moment with projects at work and the code needs a fair amount of updating to compile with the latest autoit with official Win8.1 support.


Great tool.

I am sitting behind a proxy and i want to know if there is any parameter to use a proxy with the waik tools ?

Regards Silvia

Hi Silvia,

this tool uses the WinHTTP library for the download functions if you have not configured it to use CURL.
as such if you are running Win Vista/7/8 you can use the following built-in command to configure a proxy.

enter the windows command prompt (Win+R > cmd.exe [enter]) and use the following command substituting "myproxy" with the FQDN or IP address of your proxy. see for more examples and additional syntax.

Code: [Select]
netsh winhttp set proxy myproxy

cheers!  :great:

Pages: [1] 2 3 ... 6
Powered by EzPortal