Jump to content

Geej

Member
  • Posts

    635
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Singapore

Posts posted by Geej

  1. If you use HFslip, you can made use of HFEXPERT\PROGRAMFILES folder to put your own programs in it. (w/o knowing SFX)

    You can also include additional command line executable in the HFEXPERT\WIN (or HFEXPERT\WIN\system32) if you want to add some more functionality in your cmd script

  2. I'm using IZArc and made an addon/post here

    here<--repost link

    to get around file association problem.

    Maybe u like to try it. (Use the mediafire download link)

    For RyanVM intergrator user, you must rename the file IZArc381.cab to IZArc381_addon.cab

    The svcpack addon is unattended but not silent as it is an autoit script. Internet explorer is assumed as default browser.

    Eng lng only (Rest of language files are deleted)

    Pls remove any cmd or reg files for file association to avoid any possible conflict.

  3. Next...

    I assume you are trying to Disable DCOM by default & you are using HFslip. So to install & disabled automatically, you

    1) put DCOMbob.exe into the path: ....\HFEXPERT\PROGRAMFILES\DCOMbob\DCOMbob.exe

    2) Create a script DCOMbobscript.au3 within HFExpert\autoit folder

    with the code

    Runwait (@ProgramFilesDir&"\DCOMbob"&"\DCOMbob.exe disable","",@SW_HIDE)

    Hope this is what you want

    (BTW, I did not test the script. But believe should work)

  4. you can try this code to see if you can get around the menu...

    run ("DCOMbob.exe")
    winwaitactive (" DCOMbobulator -- Say no to DCOM to improve your security.","The GRC DCOMbobulator")
    sleep (200)
    send ("!{V}");Select Am I Vulnerable? Tab
    send ("!{R}"); Activate Remote Port 135 Test


    sleep (1000)
    send ("!{M}"); Select DCOMBobulate Me! Tab
    send ("!{E}"); Enable DCOM

  5. I use it when everything else fails, why use autoit when it can be done with swiches etc.

    And your valid reasons being?

    I have a question for you. What is the difference between using a cmd file to run a file with switches and using a au3 file to run a file with switches?

    My answer is none, so long as you have both interpreters. AutoIt IMO gives you many more options to achieve your goal. So saying AutoIt is a last resort seems very illogical. AutoIt is far more then just an automation language and people who know this make very good use of AutoIt.

    To Dislocated Time:

    This is my personal experience: Learn Autoit the manual way first. This way, you understand autoit function better. The program help file (AutoIt3.chm) is very useful. I use it a lot for quick reference. Read the WINZip installation found in the help file. (Learn a few functions to get started such as Run, runwait, WinwaitActive, send, sleep , processclose, controlsend, controlclick, ShellExecute, ShellExecuteWait, MouseClick. Oh yes, marcos such as @ProgramFilesDir are important too. This is the equivalent for environment path %programfiles% use in cmd file)

  6. I tried your scripts and see what you mean now. You provided an HFSLIP.CMD file that wasn't made by HFSLIP 1.7.5. That's why I was confused.

    This problem should be fixed in the next version, but you can already try HFSLIP 1.7.6rc7 from the test releases thread at the top.

    Ok. Thanks :rolleyes:

  7. Well... I can't say much beyond this because I'm not familiar with AutoIt scripts myself. I just followed someone's instructions to implement functionality into HFSLIP.

    Are the scripts compatible with SVCPACK?

    Is anything else failing?

    Ok, thanks for answering my query. Also thanks for bringing Autoit functionality into HFslip. Without it, I wouldn't benefit from learining a useful scripting language. I am sure HFslip is the only slipstreaming utility that support Autoit. I will stick to v161 as I have no problem with that. Hope future release will still include Autoit functionality.

    For compatible with SVCPACK issue, it should be compatible if I repack my file into SVCPACK method.

    Nope, nothing else failing. Once again, thanks for helping :rolleyes:

    Meanwhile, I will still try new release on virtual machine.

    I compared v161 & v175 HFSLIP.cmd and discover there are some codes missing in v175, preventing AUTOit script from executing. The missing parts are:

    :PART2
    %HFSLIPSVC%AutoIt3.exe %HFSLIPSVC%xplorer2script.au3
    rundll32.exe advpack.dll,LaunchINFSection %SYSTEMROOT%\HFSLPGUI\HFSLPGUI.INF,HFSLIPGUI
    IF EXIST %SYSTEMROOT%\*.TMP (
    ATTRIB -R %SYSTEMROOT%\*.TMP
    DEL/Q/F %SYSTEMROOT%\*.TMP
    )
    GOTO :EOF
    :EOF

    I have also attached 3 files for testing the AUTOIT folder. The program is xplorer² Lite v1.7.0.5

    http://www.mediafire.com/?kj3bg4zereq

    I have no idea how to rectify this, could you kindly update it in the next release?

  8. Well... I can't say much beyond this because I'm not familiar with AutoIt scripts myself. I just followed someone's instructions to implement functionality into HFSLIP.

    Are the scripts compatible with SVCPACK?

    Is anything else failing?

    Ok, thanks for answering my query. Also thanks for bringing Autoit functionality into HFslip. Without it, I wouldn't benefit from learining a useful scripting language. I am sure HFslip is the only slipstreaming utility that support Autoit. I will stick to v161 as I have no problem with that. Hope future release will still include Autoit functionality.

    For compatible with SVCPACK issue, it should be compatible if I repack my file into SVCPACK method.

    Nope, nothing else failing. Once again, thanks for helping :rolleyes:

    Meanwhile, I will still try new release on virtual machine.

  9. Hi Geej

    HFEXPERT/AUTOIT...

    Are the files present in SOURCESS\I386\SVCPACK after HFSLIP has run?

    Are you creating a multiboot CD?

    Are you doing a network-based installation of Windows instead of a CD-based installation?

    REPLACE...

    The purpose of the REPLACE folder is to replace files and folders in the entire SOURCESS folder.

    I suppose you want those files to replace the same files in SOURCESS\I386. If so, you need to put them in REPLACE\I386 and not in REPLACE.

    Hi Tomcat76

    Thanks for the fast reply.

    1) Yes, SOURCESS\I386\SVCPACK files are present.

    2) Not creating multiboot CD

    3) Not doing network-based installation. Just CD-based installation

    REPLACE...

    I guess I put it wrongly. Will put it in REPLACE\I386 instead

×
×
  • Create New...