Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country


About Denney

  • Birthday 01/12/1984

Contact Methods

  • Website URL

Denney's Achievements



  1. What's even more stupid is the Driver Signing option in GPEdit DOESN'T WORK after installing the 2 updates. The option is still there in GPEdit but doesn't actually work.
  2. I'm p***ed because I tested Office 2007 and we got NOTHING. I've been beta testing with Microsoft for A LONG time and I don't expect to get anything but when something this big gets given out to testers and the other, almost equally big, testers get nothing. Ah well, crap happens I guess.
  3. WOOHOO!! I've been waiting for this day! Time to crack open the beers and celebrate!! Looking forward to the slew of new features to appear in the next few versions...
  4. Ah ok. Thx Sonic. I only use my scripts on XP so the compatibility thing isn't an issue. So basically, the only difference is one is command line based registry editor and the other is a GUI based registry editor. Seems simple enough.
  5. @Avneet: That command currently won't work because the current code cannot find the "regedit" file. That's what we've been discussing.
  6. I agree. I'm one of those "has to stay updated" people. I would love to know how to make the micro installer myself. I could probably do it myself, just a guide would be a lot nicer (not even a guide, just some directions would be nice). Plz... Edit: Can anyone explain why, when I enter my LEGIT, RETAIL Premium edition serial number, it spits out this error: The serial number you have entered is a valid Nero serial, but is not valid for this application. I'm using the English Nero Micro package. Edit2: Nevermind. It seems, silently installing the micro package and then running the program won't accept my key. Adding the key straight into the registry on the other hand and it'll work like a charm... How strange. :S
  7. I agree with mritter that it will make it harder to keep our modifications but hey, if I'm making my own mod's, I know how to re-apply them if things still don't work... It's true though. Most people shouldn't edit the code to fix things... v5 isn't a final release after-all. The only reason I do it is to try and fix the already existing problems in the hope to make your life easier. Anyway, good luck with the fixes and I'll stop posting code now.
  8. I mean to add a new configuration option like "condition" but the passes the content to the FileExists() function. The end user would need to specify this path but maybe WPI could "attempt" to guess the correct path (that would require a fair bit of logic code though).
  9. @Dje: Yes you will and that is why I have a FileExists() condition for every one of my programs in WPI. Granted it uses up my "condition" statement but hey, it makes sure the programs are there (and I still have the greyed-condition to use). If we're gonna stick with the Shell.Run() command, I'd suggest having an option in the configuration file for an actual FileExists() condition that the user can specify. More work the end user but does prevent these errors. @mritter: Yes, thankyou heaps for your work. At least this is better than nothing and I'm greatfull. WPI has saved me HEAPS on time in making my business run smoothly. Thankyou both (mritter and Kel) for the excellent work!
  10. I have mine setup like this: ReturnCode = InstallShell.Run(cmdLine,1,true); if (ReturnCode) { WriteLogLine("Cmd1 Fail (returned code "+ReturnCode+"): '"+cmdLine+"'"); programs[i].fail=true; } else { WriteLogLine("Cmd1 Success (returned code "+ReturnCode+"): '"+cmdLine+"'"); programs[i].success=true; } Granted it doesn't always return the correct code but at least if gives you an idea. NOD32 and TortioseSVN are 2 programs that return non-0 return codes when they finish. I think this is better than the old way because at least the programs get executed rather than just bypassed.
  11. @Dje: What is the actual "rundll32" command you are using in WPI? Edit: The reason the command doesn't work is because WPI surrounds the entire command in double quotes. Comment out the "ExtractArgs" line and replace the InstallShell.Run line with: InstallShell.Run(cmdLine,1,true); and it should work.
  12. You're right. They are. The Shell.Run command returns the return code of the program it's executing and not of the Shell.Run command itself. Basically, it just passes the return code through. @Dynaletik: Your first problem, of the config file, are you using RC2 or RC1? RC2 fixes a problem of it not installing based on order number. Your second problem is the reason Dje and I are posting here. It has to do with the way WPI v5 handles command arguments (it only searches for -'s and /'s and XP-AntiSpy uses +'s). Personally, I've commented out the FileExists() code because I've added a FileExists() condition to ALL of my programs. Maybe make that another config file option? So the user can specify the file to look for before running the install? Or hell, make it optional. Edit: Better idea, make 2 config file options... 1 for the command to run and 1 for the arguments to run with it. Sure, it'd break the current configs but it would make the FileExists() calls work.
  13. @Dumpy Dooby: You just beat me to it. I was just about to post that suggestion. Makes things look a lot cleaner (removes a lot of disabled checkboxes...).
  14. The problem with that is that each program's return code is different. It's up to the program to return a return code so the actual return code would only be usefull if the user knew what the return codes meant. Would be a better idea than the current implementation though. Maybe checking for a "0" return code to indicate success (most programs return 0 on success)? Edit: Just an update on my post above (#16), I managed to fix this by changing line 227 in program.js from: progspercat.sort(SortByProg); to: progspercat.sort(SortByOrdr); I just loose the ability to sort programs by name when displaying them.
  15. @Dje: I agree. I have many "cmd" scripts that I call and I pass the path of WPI to them like so: "%wpipath%\software\someprog\someprog.cmd" "%wpipath%"

  • Create New...