GrofLuigi

As per the title, after installation of XPSP2 and MANY hotfixes, there are many files scattered in C:\Windows\Driver Cache\i386\ directory. Can I compress them all into driver.cab (like Nlite does) or they are 'protected' somehow by SFC or catalog files? In this case, are there any additional steps I could do? Is WinRar suitable for the job (only adding/deleting files to the .cab)? GL

I'm not sure if we're talking about the same thing, but try this: Open RegEdit Navigate to HKEY_CLASSES_ROOT\CLSID Press Ctrl-F Enter "fade task" It will find a key with numbers and letters on the left hand side, and on the right will be: (Default)-REG_SZ_"Fade Text" (It will look like that exactly. If not, it isn't what you need, keep searching) Delete the key with letters and numbers on left side. Thiss kills the fading out of the screen when "Turn off computer" appears. Applied it to many computers in last 5 years, no adverse effect. Don't know about themes, never used one. Works on XP and 2000. I'd write a .reg file for you, but I dont have the key on any of my computers (killed a long time ago). Hence the reason for this long-wound explanation. PS: There is still some dimming going on, but much gentler to the eye. Another thing could be your laptop's EXTREME slowness (old? bad drivers? infected?). I've seen Pentium I 200's struggling with this. If it's not that old, things to check: graphic card drivers, AGP port driver (part of the chipset driver) (if the laptop is AGP based), antivirus/antispyware, event log. GL

This way you UNDO most of the things you've done with NLITE. Obviously, you removed too much before (something that's needed by your particular comfiguration). Maybe you're better off not touching HARDWARE SUPPORT, DRIVERS, LANGUAGE SUPPORT and KEYBOARDS? GL

Yes, I'm aware of this. Is that a problem? I've updated 1.4.1 to reinitialize the GUI when a new language is selected, so that it displays the correct language immediately after selection, but it's still not written to the INI file until after a file is selected and execution begins. Given that the whole purpose of UniExtract is to extract files, I don't see why you'd have any need to run it for any other reason. If you do have some issue with this, though, please let me know. It could have been an issue if you got stuck with history=0, then you could not change the setting because of the GUICtrlSetData bug. Of course, editing the INI helped. Guess it's solved with the new version. Downloading now. This is also a known issue. There are about 130 separate language items defined in the language INI files. It would be rather time-consuming, as well as increase ongoing maintenance time, to hardcode these items. Given that use of Universal Extract already requires a group of files in a particular order (all support binaries under bin\, for example), I don't think it's unreasonable to expect that users leave the lang\ directory intact. By the way, the ??? is hardocded so that I know if a particular language item is missing. It's a debugging item for me. Users (obviously) should never see it, assuming that all translation files are correct. You're the author, do what you have to do. I just thought I'd report it. This issue showed up because I copied the binaries while trying to leave out as many .txt files as I could (I always do that with new installs. If I want to read the Readme, I'll extract it from the archive.) So you could say I UniExtracted Uniextractor. Happy holiday(s) GL

Exactly the same here, together with usage method and thoughts... As if I wrote the post! Additionally, if you start UniExtract directly, it doesn't let you save options if you haven't selected a file. And an observation: without the Lang/English.ini file, it displays only question marks in the gui. I suggest it has some (English?) built in strings for fallback - who knows what could happen on a user's computer and you would get many unnecessary support questions. GL

Just some theoretical thoughts (contra prefetch): 1. What if some virus finds a way to insert itself in the prefetch cache? There isn't one yet, but who knows... 2. Do you want additional code between you and the hardware? Prefetch is monitoring what you execute and preloading it. Why not just load it when it's needed? It will never guess 100 %. 3. How can you be sure there isn't some bug in that extraneous code that's executing all the time? Do you think Microsoft writes perfect code? (In this case, code that's not absolutely necessary.) 4. Microsoft pushed prefetch with XP because people complained of slow boot times with Windows 2000. It is no magical pill that will speed up your computer 200 % nor does it cooperate with other windows subsystems (except that it's embedded in Task Scheduler service). 5. Every monitoring takes cpu cycles and memory, however insignificant thay may be. IMHO this is ridiculous, slowing down your machine so that you have the impression of it operating faster. As I said, these are just MY thoughts from the real world, not something that's been quoted over and over a 1000 times. I tried to think up some PRO arguments, but honestly, could not think of even one. OK, maybe there's one: 1. Your computer will boot in 25 seconds instead of 40. GL

This is a great idea, and I'd love to implement it, but as far as I can tell this behavior requires a shell extension DLL. All of the programs you mentioned register a DLL with Windows Explorer to enable this options. Unfortunately, as I stated in response to DerekB's response above, this kind of programming is beyond me. I actually did look into modifying the source code for 7-Zip's DLL to do something similar, but I wasn't able to make that work either, as these DLLs apparently require the commercial version of Visual Studio (for MFC support). Given that I write free and open source software, I really don't have any intention of purchasing Visual Studio. I might have completely misunderstood the issue here, but if you put a shortcut of \bin\UniExtract.exe to the "%appdata%\send to" folder, you get a right click functionality. I always use it that way and it works beautifully. Please no shell extensions - the world is already polluted with them. And thank you for the tool, nitro322! GL