Jump to content

sadicq

Member
  • Posts

    273
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Romania

Everything posted by sadicq

  1. Do you think you can wait two more days? 5.3 should be out these days. Let's hope that this error is related to the other bugs we were trying to fix. It's highly possible that the new version will fix it. So, I suggest you wait until tomorrow or the day after tomorrow. The code we see now will probably be modified and if there error persists, I'll look into it then.
  2. you should have made another post, because I barely saw a change in this thread. try applying the fixes located here . I'm sorry I can't say directly what the problem is, but I don't understand what the error message says. If you can find the fix in that thread, let us know.
  3. I'm not sure this is the easiest solution, but this is what I'm using: First, remove [GUIRunOnce] "%systemdrive%\temp\wpi-nl.cmd" from your winnt.sif. Then make sure you have OemPreinstall=Yes in your winnt.sif. Now in your OEM Distribution folders, create a file called cmdlines.txt. You can read more about it here. The content should be this: [Commands] "RunOnceEx.cmd" Now, in the same folder, create a file called RunOnceEx.cmd with the following content: for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\WIN51 set CDROM=%%i: REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\001 /V 1 /D "%CDROM%\WPI.cmd" /f EXIT That's assuming you have wpi.cmd at the root of your cd. If you don't correct it accordingly. Explanation: because RunOnce was not doing its job, we removed it from the winnt.sif. Instead we called cmlines.txt that gets called at the T-12 state. That file (cmdlines.txt) calls RunOnceEx which will do nothing more than adding your wpi.cmd to the RunOnceEx. So note that RunOnceEx executes before explorer.exe loads, while RunOnce executes after. So, to summarize: Winnt.sif -> cmdlines.txt -> RunOnceEx.cmd -> wpi.cmd .
  4. lol. just lol. Sorry guys but I'm really busy right now. I read the topic already but I didn't have the time to look at this. I'll try it tonight if I find some spare time. Hmm, one question though: how are you launching wpi (from runonceex or how?). Explorer.exe should not start whatever DoNotLoadDesktop is set to. That setting prevents the process from starting after WPI just finished installing programs. And it stops it by restarting the computer or by shutting it down right before explorer should load.
  5. mike_jrt, except for the restart feature, everything is already implemented. Take a closer look at the cond and gcond parameters. They allow you to check and disable certain items if they are already installed.
  6. Here's an idea: Once the install sequence is started, copy the config program by program into the registry and put the wpi in the runonce (not the installers, just wpi). once a program is run, delete it from registry. when all the programs are installed, delete wpi from the runonce (all the programs will have been deleted from the registry already). This would do it I guess. but I don't think Dje should waste his time on this problem. It's too much trouble for a small function.
  7. @lennierv What's the exact name of the melody you are trying to add? WPI has some problems with special chars.
  8. I doubt that would do it. And if it works, that's really strange. the problem was comnig from having '' in "" and \'\' ... anyway, i'll upload the whole archive I modified for you. I removed all the files you said you wanted plus the WPI inbuilt tips (you have your own). I also fixed some problems in wpi.hta. the problem was only boxes.js. If you don't want the other modifications, replace only that file. link
  9. It's very had to troubleshoot it once you modified it. So, if you want, you can archive it and upload it or email it to me.
  10. It is normal ... you see, %CDROM% won't work if you run it from hdd in most of the cases. But you can trick it if you layout your drive the same with your DVD (make sure all the folders relative paths to the drive are the same with the cd you want to put them on). So, when you edit your config, try moving your applications in DRIVE:\Applications\ and it should work. Edit: I'm writing from memory, so I'm not 100% sure.
  11. Way too dirty in my opinion. I just can't test a fix for this ... but anyone who uses cmds should show us some support... Read this and look for the cmd errors Pliek is talking about.
  12. 1. I really doubt it would 2. No. That's a really bad idea! What happens if one gets executed twice? You'll get some ugly errors.
  13. Ok ... that was not supposed to happen. About firefox I can say it behaves a little different from the others, but the one ... it is strange. I'll look into this when I have some time. Unfortunaly, I'm really busy these days, but you should also wait for the 5.3 version. I heard they are trying to fix a problem regarding batches, so stay tuned and read the other threads in this forum too.
  14. I don't think your problem is the batch file, but the installer. I know I once tried to install a plugin for Firefox right after it installed. You should adjust your batches so they wait for that link to be created then delete it.
  15. Some features that I would find useful: - disable or hide the Options, Config, Show Source and Manual buttons when WPI is run from a removable drive. Most of the times they are read-only and these options are useless. - disable screensaver while installer is running (I'm not sure if the screensaver may activate ... just an idea though). I'll edit this post later because I have to go right now ...
  16. 1024 x 768 - count this 10 times ... I have a lot of friends who use my WPI CD and they all use the same resolution.
  17. Already talked to mritter about that problem. Bugs reported so far 1. Progress bar wrong id. Link Fix [sidenote: you may also remove that line ...] 2. Uncommented line for theme update. Link Fix [sidenote: the file patcher should be modified because it generates those errors when it is run from a read-only media] 3. Not a bug, but an enhancement. Link & fix 4. Pause time issue. Link Fix 5. Command line parameters issue. Link Fix sent to mritter. 6. A bug ... Link No fix yet [i couldn't reproduce it yet]. 7. Installation slowed down. Link No fix yet [i couldn't reproduce it yet]. I hope these are all the bugs that were reported so far. Thanks Dynaletik and Pliek for the bug reports.
  18. As I already told mritter in an email I sent him yesterday, "show source" is not a big help in the form it is now. But if we add line numbers, a copy function and an "export to file" function, then it may be useful. Anyway, I never used either of them, although I just wanted to try the "show source" last night to trace a bug.
  19. Ok, here's the solution (the post before was just to determine the source of the problem, but I'm pretty sure that that was the problem). In installer.js, replace Pause(0,100); //wait for the new document to be fully loadedwith while (window.document.readyState != 'complete') Pause(0,100); //wait for the new document to be fully loadedAnd this will work every time.
  20. Open installer.js and look at this line: Pause(0,100); //wait for the new document to be fully loaded Try increasing that value and see if the error still appears.
  21. Ok... I know this sounds stupid, but I spent 2 hours on this bug ... Open patchFile.js in notepad and replace patchLine(wpipath + "Themes\\" + Theme + "\\wpi.htm", /class="txt"/ig, 'class="opText"');with //patchLine(wpipath + "Themes\\" + Theme + "\\wpi.htm", /class="txt"/ig, 'class="opText"');Somebody forgot to comment it out .... Attention: Apply this fix on a clear WPI as the line that is not commented has already modified your WPI if you ran it from hdd. The problem showed up only when you were running WPI from CD because it was read-only and the script could not modify the files .... Note that the line you are commenting is just an example and it is not needed by WPI. Actually it's doing just the opposite.
  22. Make sure the force checkbox is cheked in options.
  23. Open timers.js and replace the line 62 with this: document.getElementById("Timer_bar").style.width=0;
  24. I know that removing that code is not what a programmer would suggest, but if you look closer, the way the installer window is created permits you to skip the install close part. I don't know exactly what you guys are working on (we are working separately), but if the installer window will remain the same, you should skip the part with the installer window closing... or at least make the wpi not create the layout and check boxes again (for a large config that takes quite a while). That was the main reason why the installer stalled. I did not write these explanations together with the fix because I was not sure whether it will work.
×
×
  • Create New...