GrofLuigi

Because he'd like the computer to Serve(-r) him, not the other way around? GL

The registry entries would be: REGEDIT4 [HKEY_CURRENT_USER\Software\Microsoft\CTF] "Disable Thread Input Manager"=dword:1 [HKEY_CURRENT_USER\Software\Microsoft\CTF\MSUTB] "ShowDeskBand"=dword:0 [HKEY_CURRENT_USER\Software\Microsoft\CTF\Langbar] "ShowStatus"=dword:0 "ExtraIconsOnMinimized"=dword:0 Yeah, there's something fishy in that article (from Microsoft? Who would have thought? ) about the values ShowDeskBand and ShowStatus (notice the title of the article!) OK, this is the one that should get rid of the Langbar once and for all. You can't just remove ctfmon.exe from [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run], it will come back. Also, you can't just un-regsvr it. IIRC, there was a hack at the time with un-regsvr'ing another dll, but this is the 'clean' way of doing it. The same can be accomplished with the GUI in: control panel/regional & language options/languages tab/details button/advanced tab/turn off advanced text services (phew that was long ). And it's the same bar (Office/Windows). GL *Edit: to clarify, this will get rid of the button and the indicator only, you will still be able to switch languages with the keyboard.

For pre-Vista I use this. Don't know if it works on Vista, I don't have one. GL

Remove Language Bar once and for all. Use the registry entries for your unattended purposes. I can't believe no clear answer was given before. GL

Total Uninstall works quite OK for that, I use even the last free version without problems (for ANY installation). Only thing it doesn't monitor is permissions. Don't know about the new version(s) of the program. GL

Attempt to get back on topic: If you're running HDTach in compatibility mode, you're measuring compatibility mode, not your actual hard disk speed! And the biggest source of incompatibility: prohibition to write to %programfiles% for regular users - Microsoft promoted that until XP. Hell, they even promoted .INI files in Windows3X - you can't expect every time Microsoft changes their mind to blame it on others! GL

I remember this from looong time ago (nForce2). Something that made me bump my head into a wall (after I scratched it for days). Not so obvious and very weird. It has to do with the computer type (main one in device manager). Nvidia (S)ATA controllers didn't want to install if it was not Acpi Uniprocessor or Multiprocessor (I'm talking about already installed windows). Now this is not the new Acpi (S)ATA controller, it's the computer type (HAL?). Maybe it is not the exact same issue, but sure looks like it. Since you're doing unantended, I think there are two possibilities: 1. You had somehow chosen the 'wrong' HAL (computer type) that the drivers did not expect. Less likely. 2. You had chosen the wrong SATA driver package (or type of driver inside the package - one mistake you could make is Textmode vs. PNP and another is to choose wrong platform from inside a package - NVIDIA has multiple). GL

Just this one, not to bog the thread down... Although I have answer for all the other points raised, but let's not turn this into another bashing... Who said I liked XP? XP was also imposed onto me (by cutting off driver support and/or Adobe's insane requirements for photoshop/premiere). Now I didn't particularly like the 9X line either, because it was primitive - not really an OS, just a graphical shell over DOS. So what do I like? nLited 2000 or XP - that's close to perfection. Yeah, the old school - OS is an OS (Operating System), not everything including the kitchen sink. If I need a program for a speciffic task, I'll install it separately. All in one solutions can never be better than specialized programs - and I won't tolerate 'good enough'. But with Vi$ta (and partially with XP) I have no choice - I have to install everything (vLite isn't quite there yet i hear - I haven't tried it because, of course, I don't have Vi$ta). As for prefetching and indexing - what if all that work goes to waste? What if I never use that program Windows was prefetching for me or never open that document it was giving me on a platter? Or if I simply chose to reformat? That's so inneficient - that's BLOAT. I like my Windows to do what I tell it to do, not the other way around. OK, I got carried away again, let's not even touch phoning home and 'unbelievable restrictions'... Maybe open another topic (but I always say: why bother, who understands - understands.... And that's why Vi$ta lovers continue to amaze me - so much energy wasted trying to deny something that's so obvious...) GL

What you Vi$ta lovers forget is that it costs good money. For that money, a normal user would expect everything to work right out of the box, not to bring more restrictions and bloat. So when you try to push Vi$ta onto us, you'd better donate us a free copy, or else you're just Micro$oft's pimp$ (I say this out of general principle). Since this topic is about incompatibilities, just ask anyone who works with audio production what has Vi$ta brought to him (with moving the audio drivers out of kernel mode). Yeah, even the regular sound card drivers have enormous problems. It would be OK if this was justified by... what was the reason, you say? To satisfy Hollywood companies? Common... Every Windows NT version promised taking drivers out of user mode (and managed to do that, but not fully) with promises of stability, but brought only inconvenience. Another thing. If learning the user interface from start isn't an incompatibility, I don't know what is. Security? That was Micro$oft's fault in the first place, with every Window$ version full of holes like a Swiss cheese. And they try to remedy that how? By restricting user's access to everything? Viruses will find another way in, but the user will remain $crewed. And blaming incompatibilities on driver's manufacturers isn't helping either, because with that you're just blowing wind in Micro$oft's sails who want to extort money from signing every 64-bit driver. And if Nero has gone the bloat way, there's no reason others (Micro$oft) to follow it. I'll stop now, because this post has gone into the not-desired direction (and I have lots more to say), but it was intended as a response to the "Vi$ta-pushers" (I can understand when someone works for M$ and feels as his duty to defend his job and I respect that, but when someone wants to pursuade others to part with their good money for some not-so-obvious benefits, it's suspicious - at least for me, I can not see any benefits that Vi$ta brings that are worth the money). And I hope no harm will be done to this innocent post of mine 'cause I think it's valid response to the issues raised above. GL

There must be a setting for this. I think it's in Acrobat. Dig into options, look for something like font embedding or font substitution. Sorry if I'm not of much help here, I don't have Acrobat. GL

SP2 or SP3. Don't integrate both. Throw one away. GL

Copy/paste: Take a look in Regedit where I left it - something isn't right there?: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AutoplayHandlers\EventHandlers\PlayMusicFilesOnArrival It seems you have removed Windows Media Player - he's responsible for creating initial music file type entries; Check if foobar2000 has an option for creating associations.; Foobar dosn't respond to checking/unchecking "set as default audiocd player"... In the past, when I used FooBar2000, there was a separate .exe responsible for setting associations - did they change that? Yeah now I'm sure - CD Audio Autoplay Handler isn't defined (by a program; it is only by Explorer). Reinstall foobar and have it take over AudioCD associaton (if it's capable, but it should be). Nice visiting you! GL

When? On a booted windows? Installing which program? NLited Windows is best installed when booted from the CD. Of course, you can run it from Windows (that's Manual Install/Upgrade) but there were some reported problems with that, especially with latest nLite (or XP SP3). Otherwise, what you're describing is Windows Autoplay function. You can restore it if you copy Autorun.inf from your original CD (and any files referenced in it, if not present in the new CD). GL

Create it. Don't be afraid. GL

Works fine with nLite. First slipstream SP4, then Update Rollup, then other hotfixes, if any. GL

Yes. Impossible any other way. GL

There are things in TweakUI that cannot be accomplished by scripts (now I forgot which ones, but... It's handy to make quick checks). Are you sure about that? 99.99% of what TweakUI does is making registry changes. And all registry changes can be made from a script - either using a .reg, reg.exe or through vbs. I'd be interested to know what can't be automated... That said, it's a lot easier to check some boxes than research what changes you have to make, unless you're trying to do it unattendedly. The bottom three nodes. And some settings are not translated directly to reg values (e.g. UserPreferencesMask). I'm not saying you're not right, just that it's like 90%. GL

The best would be to start with clean SP0 or SP1 (be careful about that hotfixes), but if that's all you have and works for you... oh well... You don't have to if you're satisfied with the result (if it works without problems). There were opposed oppinions on that, but I always do this: In first pass integrate all service packs/updates/hotfixes (and addons if I did them ) and in the second pass do all the removals/tweaks/services. It seems logical to me. GL

There are things in TweakUI that cannot be accomplished by scripts (now I forgot which ones, but... It's handy to make quick checks). Try some of the 'others' , you'd be surprised. Yeah, that's why I said 'very few' (I used them more in the past). GL

ExCtrlst, msicuu, TweakUI, everything from Nirsoft, very few from grc... GL

The preset looks fine, but the hotfixes/addons section is a mess. First, for troubleshooting purposes, try without any hotfix/addon (if you have time/desire, but I suspect it will be OK). Second, you must sort out that mess in there - check which hotfixes are for the service pack level you're working with - I see you start with XP SP1, then one approach would be to integrate SP2 (or SP3) + IE7 + WMP11 + net framework in one pass (without any other tweaks), then integrate hotfixes/addons for them in another. I don't have experience with integrating IE7, WMP11 or .NET, but I read there are many quirks with them. Try searching the forum for the right addon/method to integrate. I see you have even hotfixes for Windows2000 - double check if they apply to your scenario. (I'm too lazy to search every KBXXXXXX , sorry). Recently I integrate only SP3 + few hotfixes that came after that. GL *Edit* some obvious errors would be: you have WMP11 twice; the last two lines of xable-SP2-UpdatePack-June-v3.0.12a - double download? No wonder it doesn't work - you must clean up that mess.

That's what I meant with "corrupt download". I don't understand what this means. Maybe a screenshot? This again looks like the error(s) from the beginning of this thread, related to .net framework installation and/or some other program (antivirus, firewall) interffering, or maybe a missing .dll... It could be anything. The latest. You should be able to tell by looking at the date. The ones with "U" are not needed. Please remove your CD key, if present. And attach them, don't paste them in the thread. Attach that too, but as .txt file. No problem. GL

lnjr, About the hotfixes that failed: maybe the download was corrupt or they are not intended for the OS you are nLiting. Not expected type of hotfix: sometimes this is normal, depends whether the component was already present in the source. Or again, not intended for the source OS. If you integrate IE7, WMP... the order is important (the hotfix can't update something that is not there). You can find LastSession.ini in the folder you were working in (the source folder), inside the finished .iso file (you need to extract it from there) or in the directory where nLite is installed (usually program files\nlite\presets). GL

(And this goes to both of you) Temporarily disable antivirus (real-time scanning) while working with nLite. There were reports on this board that some of them interfere with nLite's operation. GL

Nlite brings it's own versions of msvcr90.dll with it. Might be a conflict with a version already installed on the system, if any. In this case, I would uninstall nLite (and wipe it's directory if something's left inside), then reinstall nLite. GL