CLASYS

Been here before, but not recently. I develop a freeware package that has to run identically in XP and up, and I was adding a small feature while testing on a Vista64 system all the way up, but the bug presents on a clean install of Vista 64 SP2. I have a work-around but I am stymed I have to do so. I have to check this out in all the other supported systems, not sure if Win 7 is affected, but please help me out! I have a shortcut to a BATCH file meant to be stored with similar ones in an open window as a control center for a bunch of related activities. The idea is to have a shortcut on the desktop and users click on that to open this command-center window. Most of the icons/shortcuts in that window point to one of many .BAT files in another directory, etc. I happened to add another one and the icon winds up with the UAC elevation overlay on it. Worse still, making changes to the icon particulars can lead to the UAC actually being required! Here is the ONE change that makes it go away: If I change the name of the .BAT file and a corresponding change in the shortcut info the bug totally goes away! There seems to be a reserved keyword problem that you have to avoid the word SETUP in the file name. In particular If the name of the batch file is Setup Log File.BAT then the problem happens. However, if I change the fille name to Set Log File.BAT Then the entire problem goes away. I have isolated it down to merely what I am posting here, totally reproducible: The problem requires that you change to a different icon, any change will do, but predictably change the icon and the problem pops out! [The package has about two-dozen icons already, all with renamed labels on them to make sense to users, but the added frill is the only one that the BATCH FILE name pointed to starts with SETUP, and I happen to have a bunch of coherent icons, etc.] Not sure of other variations, but why can't the name of your own BATCH file not start with S-e-t-u-p? Any ideas. [The renamed shortcut still says Setup Log File so it cosmetically is fine, but I've never heard of seemingly ordinary reserved filenames in Windows! Any help? The BATCH does some mundane things to implement a new frill feature, and that always works, just this surreal-looking problem also shows up. Thanks in advance if anyone has ever encountered something like this. cjl

Hi folks! I haven't been here in quite awhile [because I got all my problems solved here!]. But of course there is always one more: I am attempting to install Win7 on a Lenovo W540 w/8GB and the 2.70 CPU. I can run 8.1 on it fine, and I have also installed Vista [although many driver problems, but I still got it up enough to have it proclaim "genuine software". I can install the product key [that matches the Windows version] fine. But I cannot install the cert file LENOVO_V2.1_Cert.XRM-MS and get the error code 0x00000BBA The spool file was not found. Is this somehow related to the fact that the Win8/8.1 key is built into the BIOS? Do I need a[n even] new[er] Cert file? All else is fine, but only got about 3 weeks more to activate. Any help appreciated.