Jump to content

Dynaletik

Member
  • Posts

    668
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Posts posted by Dynaletik

  1. If you check the option to hide the additional buttons (Options, Config, Manual, About) when running from CD/DVD, only the upper buttons will be displayed when WPI detects, that it is not started from HDD.

    Where WPI gets started depends on how you call WPI.hta. If you start it via GUIRunOnce, it is started before the desktop loads completely. I start my WPI and in the background I continue loading the Vista desk etc. In chapter 2 of the manual you can find some archives for starting WPI when windows installation is done.

  2. Thank you for both projects XPero! XPize made my Win XP so beautiful and perfect, perhaps someone will get Vize to 64-bit state. ;)

    I wish you all the best for the future!!

  3. It should be UAC. I remove it with vLite and never had problems with WPI writing files on drive C:\ . But if UAC is enabled, it asks for every little file you delete and perhaps it also "protects" the systemdrive against saving files. :(

    Just enter msconfig -> Tools -> Disable UAC (this should be what it's called in Vista EN), reboot and check if the problem still exists.

  4. This is not a warez board, so will not get any help on your second question, only that license keys are often stored in the registry. I export my key of e.g. TuneUp 2008 (original ;) ) and integrate it via reg before ability in WPI.

    For finding switches, you have to determine which setup type is used by the program. Perhaps this can help you.

  5. For problem 2: As the manual says, you have to place all your images for the tooltips into the Graphics folder inside WPI, so they have to get different names. Then You simply put in the filename into the picture file box. (e.g. Cpuz.jpg)

  6. I translated the new WPI 6.5 manual into german! Just extract it into the Manual folder. :)

    Additionally I changed some strings to better fit the meanings of the options.

    Perhaps the manual and the updated lang file can be included in the next version of WPI. :P

    I know that I'm going on your nerves. :D

    EDIT: Both are included in WPI 6.5.1!

  7. Hey guys. I downloaded the actual WPI, and in fact, the Manual shows up. But always the english one is showing up. :P

    I played with your function in main.js and got it working I hope. First I changed the syntax at FileExists, file:// isn't necessary I think. And I added an else in there, because otherwise it gives an "undefined". :(

    function SetupManual()
    {
    position="main.js";
    whatfunc="SetupManual()";

    var tmpLang;

    if (!FileExists(""+wpipath+"/Manual/"+Language+"/index.html"))
    tmpLang="en";
    else
    tmpLang=Language;

    document.getElementById("layermanual").innerHTML='<a href="file://'+wpipath+'/Manual/'+tmpLang+'/index.html" target="_blank"><img id="OpenManualButton" src="./Themes/Windows/spaced.gif"></a>';
    }

    P.S.: I am a noob in programming, so it could be that there is a better way? :P

    EDIT: Another thing that I just saw: If you go to the config page and add a new entry (or edit an existing one) and select "Other" as category, there is no new text box to enter the new categories name. The manual (that I am translating atm) says, there would be such a box.

  8. Okay. :P

    If you select a language different to english and want to view the manual, WPI gives an error that the translated manual is not present (It replaces 'en' by your locale in the path). Okay, I understand it, but could it be done that WPI first searches if an translated manual is present, and if not, use the english one as default?

    If you go to the Windows Options page, the "Show Titlebar" Option (WindowShowTitleBar) setting is always disabled, even if you activated it before. It works, but if you save the options and do not remind to check the titlebar again it does not get used any more.

    But, WPI 6.5 rocks! :)

  9. I use Vista x64 and remove both, System Restore and Volume Shadow Copy. My SetPoint works like a charm.

    If I only use the normal SetPoint installer from Logitech, my keyboard and mouse do not show up in the software. But this has got nothing to do with vLite for me. Logitech did not manage to update their drivers for Service Pack 1. So if I try to install the Logitech drivers that ship with SetPoint 4.60, Vista says, that these are not compatible with x64. So I modified the .inf files (added x64 entries, quite simple) and tried it again.

    Now Vista gives signature warnings on installing the driver (because .cat files do not match the .inf files any longer), but it works! (I think that working drivers can also be applied by enabling auto update of SetPoint, but didn't test it myself.)

  10. Wow, thanks for the new release nuhi! Vista gets better and better ;)

    @ mattewre: All apps that need .NET FW will not work, installing it later is not possible yet, this is what the component description says. :)

×
×
  • Create New...