Jump to content

AlBundy33

Member
  • Posts

    216
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Posts posted by AlBundy33

  1. Maybe your network is not setup correctly?

    you can try this:


    REM reg add "HKLM\System\CurrentControlSet\Control\Network\NetworkLocationWizard" /v HideWizard /t REG_DWORD /d 00000001 /f

    REM create automatically a networkdrive (works only if the share is not password-protected)
    PUSHD \\192.168.x.xxx\DEPLOY

    REM Start WPI and wait until it was closed
    Start "running WPI..." /Wait WPI\wpi.exe

    REM removes the networkdrive
    POPD

    Attention: If WPI restarts your PC the network-drive is lost.

    Al

  2. Maybe you should try to install a "normal" XP (without nLite) and try WPI again.

    You should also remove the "start"-commands in your install commands.

    Instead of

    start %systemdrive%\wpi\install\imgburn\imgburn.exe

    you should use

    %systemdrive%\wpi\install\imgburn\imgburn.exe

    Al

  3. These are the three that come back as having a script error

    I can use your files without any problem (tried with WPI 8.0.2).

    AFAIK WPI has some problems if Nero 7 is installed.

    Do you have a "normal" XP (e.g. not modified with nlite)?

    You can also try to run WPI in another account.

    Al

  4. I am receiving this script error as seen in the screen capture and a few more saying the same thing. The WPI scripts having this error are windowoptions.js,configwizard.js, and useroptions.js. I am running XP Pro (SP3) x86. Any ideas as how to fix this or is it even a big problem? Thanks

    You should also post the corrupt files.

    Al

  5. I think it's better to NOT include empty config-files.

    Without these empty config-files I can download a new archive and extract it over my current WPI-installation and all it's fine.

    With these empty config-files download the archive and have to extract it manually if I don't want to override my config-files.

    In my opinion there is no need to change the current behavior.

    But I some people don't like this it would be better to initialize the config internaly with default-values and after that try to load the config files - if they exist override the default-values.

    Al

  6. AlBundy33's issue is fixed. Waiting for schnedwui to reply.

    Thanx to mritter and Kelsenellenelvian - really good work.

    I think schnedwui's error was the same as mine - because I had exactly the same message.

    I my case it was the problem of IE6 (or its settings) - because my XP Home was a clean install without updates.

    After update to SP3 (and all later hotfixes) the problem was also gone without the fix.

    Al

  7. @xure: Are you sure? The paths get saved correctly for me.

    @ricktendo64: Fixed.

    @AlBundy33: Fixed.

    Note: For a new line press Shift+Enter. For a new paragraph, just Enter.

    If the archive is updated the fix doesn't work.

    Just a hint: The image on wpiw.net shows 7.7.0 as current version.

    Al

  8. There are problems with linebreaks in ToolTips - if you just press return a new-line-character will be inserted after the div in config.js


    prog[pn]=['Test'];
    shortdesc[pn]=['1.0'];
    uid[pn]=['TEST'];
    dflt[pn]=['yes'];
    forc[pn]=['no'];
    bit64[pn]=['no'];
    cat[pn]=['Applications'];
    cmds[pn]=[];
    desc[pn]=['<P>Test</P>
    <P>1</P>
    <P>2</P>
    <P>3</P>'];
    pn++;

    Al

  9. Some days ago I started WPI from my pen-drive to install some apps for my parents - unfortunately they have Windows Vista with the UAC-Problem.

    So before each application a window poped up and asked for the rights...

    Now I created a vb-script and modified my run_wpi.cmd to run wpi with admin-rights (so hopefully the uac-dialog will only be shown at the start of wpi).

    Because I'm working with XP I could try the skripts only on my machine and on a virtual Windows 7 machine.

    On XP the script will start normally and on windows 7 the uac-dialog is shown at startup.

    Maybe someone can test it on vista.

    Simply put the script in the same folder where you've extracted WPI - your structure should look like this:

    - WPI
    - ...
    - Themes
    - Tools
    - ...
    - run_wpi.cmd
    - sudo.vbs

    Of course you can also edit the variables in run_wpi.cmd.

    Hint: If you path to wpi.hta is WPI\wpi.hta you have to change the following line in run_wpi.cmd:

    SET WPI_HTA=Common\wpi.hta

    to

    SET WPI_HTA=wpi.hta

    Al

    scripts.zip

×
×
  • Create New...