Jump to content

lurk&jerk

Member
  • Posts

    130
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by lurk&jerk

  1. Got the new version. Am I the only one still having problems with registry dependencies, not graying out installed apps? The file, folder and architecutre dependencies work great (I haven't tried the others). But registry keys are a no-go. I've tried this feature on all sorts of PCs. I've got admin rights. I've run WPI from a CD and a harddrive. There must be some reason this feature isn't working. I've got 64-bit Windows Ultimate. As a test, I tried: RegKeyExists("HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folder") this is how the code looks in the config.js file: prog[pn]=['Shell Folders']; uid[pn]=['SHELLFOLDERS']; dflt[pn]=['no']; forc[pn]=['no']; bit64[pn]=['yes']; cat[pn]=['Customizer']; pfro[pn]=['no']; cmds[pn]=['{REGEDIT} "%wpipath%\\Install\\Regs\\ShellFolders.reg"']; gcond[pn]=['RegKeyExists("HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Shell Folder")']; desc[pn]=['Shell Folders']; pn++; The entry is not greyed out even though the key exists in my registry.
  2. I'm still perplexed about my inability to get WPI to recognize registry keys that have been installed by apps. I had one other thought: I copy WPI from my install CD to my hard drive, and then run it. Would that make a difference? I'm running WPI version 8.1.0
  3. I have experienced same problem and was never able to ID the cause. As a bandage, I made a context menu entry to start and stop the printer spooler by right-clicking on the desktop. Autoscript code: RunWait(@ComSpec & ' /c net stop spooler') RunWait(@ComSpec & ' /c net start spooler') And here's the registry code to launch the script from the desktop right-click menu REGEDIT4 [HKEY_CLASSES_ROOT\DesktopBackground\Shell\Spooler] "Icon"="c:\\PATH2ICON\\Printer.ico" "Position"="Top" [HKEY_CLASSES_ROOT\DesktopBackground\Shell\Spooler\command] @="C:\\PATH2AUTOIT SCRIPT\\PrintSpooler.au3"
  4. I finally figured out the issue. In the config file WPI was putting an extra space between the last double slash and "Red.cur" as shown below. I've also noticed this occasionally happening on other entries but usually when I close WPI and reopen it, there will be an error message pointing to the line error. Anyway, thanks for the help. prog[pn]=['Cursors']; uid[pn]=['CURSORS']; dflt[pn]=['no']; forc[pn]=['no']; bit64[pn]=['yes']; cat[pn]=['Customizer']; cmds[pn]=['{REGEDIT} "%wpipath%\\Install\\MySetup\\Cursors.reg"']; gcond[pn]=['RegKeyValue("HKEY_CURRENT_USER\\Control Panel\\Cursors\\Arrow")=="F:\\1SYSTEM\\1cons\\Cursors\\ Red.cur"']; desc[pn]=['Cursors']; pn++;
  5. Am I to understand from this thread, that you can set a PC's IP and DNS settings for individual users? If so, can you set different grayed out or check box settings on the install menu for each user? That is, when you launch WPI and choose a user created from the Network settings tab, does that not only set IP, DNS and computer name but also show an install menu unique for that user?
  6. Thanks for catching the mistake, mritter. But I corrected it and my cursor registry entry is still not greyed out on the main menu even though it's been installed. Consider this thread closed. It's a bug I can't quash.
  7. Nope. Doesn't work when putting registry entries in either the "conditions" or "greyed conditions" field. If that's what you mean by opposite effect. Also, I assume registry condition will accept keys other than HKCU, like HKLM? Again, my issue is that when I put any entry other than registry in greyed out condition, the application install is indeed greyed out. With registry entries, nothing changes, like the entry, below: [HKEY_CURRENT_USER\Control Panel\Cursors] @="" "Scheme Source"=dword:00000000 "Arrow"="F:\\1SYSTEM\\1cons\\Cursors\\Red.cur" This is what I have tried under both "conditions" and "greyed condition." RegKeyValue("HKEY_CURRENT_USER\Control Panel\Cursors")=="F:\1SYSTEM\1cons\Cursors\Red.cur"
  8. Both "Registry Key" and "Registry Value" don't grey out installed applications with the registry keys I want recognized. Most of the other dependency stuff I've tried (File, Folder, Version, bits, etc.) works but not the registry. Is this a bug? And yes, I searched this topic but didn't find any discussion of it. Thanks.
  9. OK I love WPI, but it's more than 20mb now!!! How can I slim it down? FYI I don't need audio, ussf, only the livesstrong theme, no help, only default resolution and only English language. Thanks.
  10. After I issue the command.. C:\Windows\System32\cmd.exe /k %windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f ..is there anyway to avoid rebooting to disable user account controls and starting WPI without UAC interferring?
  11. Anybody know which registry keys to save to transfer custom library entries? I've tried the ones below and they don't seem to work when I apply them to a new machine: LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\CrawlScopeManager\Windows\SystemIndex\WorkingSetRules\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\Gather\Windows\SystemIndex\Sites\LocalHost\Paths\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\Gather\Windows\SystemIndex\StartPages\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\Shell Icons Also, I can't seem to move the desktop and a handful of other user folder from their default locations by changing the path in their registry entries.
  12. Just to weigh in one last time, overwriting the drives with 1s & 0s works, no question about it--it just takes all day on today's gigabyte drives. I am also not suggesting that after wiping a disk with any tool, Windows 7 is trying to boot. Rather, during a clean install process using Windows own format utility or 3rd party tools like Acronis or Partition Commander, Windows 7 recognizes that a previous installation has been attempted and preserves what data it can before proceeding with installation. So after I have installed Windows 7 a second time it either has: (1) a directory named Window.old that usually contains io.sys and/or autoexec.bat, or it flashes a message about looking for a previous Windows registry or says the copy is not genuine, when it absolutely is and confirms as much with I go on line and register.. Cluberti may have identified an issue that I did not consider. I do usually install Windows 7 on dual drive systems, with the OS on one drive and non-OS data on the other. I still don't understand why that would be a factor though. The OS is not on the second drive and neither is the pagefile, bootmgr, io.sys or any other boot file. Weird. Anyway, thanks to everyone for their suggestions. (EDIT) Nope same problem with a single drive that dual boots WIN& & XP. Weird.
  13. I have tried all of the suggestions submitted. I am an experienced computer user and the problem I have is not an issue of not using the right tool. Darik's nuke disk as well as commercial apps such as Killdisk work, but they take all day to wipe a 300gb harddrive with 1s&0s and even after that you have to use mbrwork.exe to really eliminate all traces of windows 7. However, I have found that faster tools that purport to delete the partition and/or master boot record don't do a complete job with Windows 7. Somehow the OS recognizes that a previous install has been made and attempts to recover the record of it, either looking for the registry or creating the directory windows.old that restores whatever files it can find from the previous installation. The only way to nuke Windows 7 is to wipe the drive and that takes all day. HDDerase.exe, when it works, is a lot faster. But it doesn't work consistently. As I said, these problems may be because of my particular hardware and or software combination but I posted mostly to see if anyone else has had a similar problem and found a solution. Apparently that is not the case, so I will consider this thread closed.
  14. In the good old days of Windows up to XP, you could delete the windows partition and reformat and be back in business with no adverse affect on your hard drive or the performance of your OS. But I've gone through more than a half dozen partition programs and disk wiping programs in an effort to cleanly upgrade from the evaluation version of Windows 7 to an OEM version, and each time Windows 7 resists being fully erased from the drive. Microsoft seems to be implementing some boot encryption or or hardware bios routine that leaves traces even after the Windows 7 OS file and partition is gone that slows down performance and sometimes preserves remnants of the old installation. Since I can't find much about this issue on the Net it may also be my particular software configuration, particularly the firewall that I use, Agnitum Outpost. You can see the effects when you install Windows 7 on a clean hard drive compared to one one that had Windows 7 previously installed but erased. In the latter case, you will sometimes see a message "checking registry" during the initial re-install of Windows 7 after the previous version was erased and/or get error messages after you think the OS has been cleanly install. This is not a boot virus issue. My PCs are clean. This problem is cropping up on at least a dozen computers I manage at home and at work. Like I said, with Windows 7, you seem to get one opportunity to get an install right on a virgin hard drive, and then the OS seems to try to preserve some remnants of itself no matter what you do to reformat or wipe the disk. The only tool I've found that actually gives me a clean hard drive for a re-install is the HDDerase.exe, driving wiping utility. But it doesn't work consistently. I was wondering if any other members had any ideas or recommendations or had experienced this problem at all.
  15. Since I use WPI for both 32-bit and 64-bit OSs, I was wondering if there is there are way so specify one color for 32-bit programs and another for 64-bit. Obviously, one way to do this is through default selections, instead of dual colors. But my pc configurations are so different I really can't specify a default selection for 32-bit or 64-bit, so I'd like to use different colors, if possible. Also I'd like to know if the program selection category listings are still changeable, that is, can you put drivers before applications, etc. There also appear to be some slight formatting issues as some categories look like they are a single line below the preceeding category while others are double-spaced.
  16. Will enabling this selection in the tools tab prevent WPI from running on 32-bit windows? In other words, do I need to make two WPI's, one for win7 32-bit and another for win7 64-bit? Also, is there a script to disable the win7 security features so WPI can run seamlessly.
  17. I want to use vlite to change the Windows 7 directory from the default "Windows" to something else and also specify the serial number for an unattended install. Won't change anything else. Can that be done without error on the release candidate? I'm seeing conflicting posts. Thanks.
  18. Than my current version 7.1.1. Are others having this issue or am I doing something wrong. (It's slower both with and without my old WPIScripts configuration files).
  19. Where are the menu bar settings saved in Outlook 2003? Also, how do you get custom created templates to "preview" in the New Office document dialog. Got second part answered on Google. Still no clue on how to save a customized menu bar.
×
×
  • Create New...