Octopuss

That's dumb as hell. Sigh.

This is thread about 7Customizer, so why don't you take your Legolas and talk about it elsewhere?

Well I could go with specific command to be executed, too.

That's too bad, gotta have the right friends then ...or check torrents

no replies?...

Is it even possible to do REAL slipstream of SP into Office 2007 installation? Everything I googled up was this nonsense about putting all the files into updates folder. I don't want this, I want the real thing.

Best is to download the ISO from MSDN

I said it was junk. P.S. Font size reminder.

Does anyone know how do I set system TEMP variable in nLite? It looks like the available setting only affects the variable for users.

I am not defending Creative at all Their drivers are rubbish indeed and I only have firsthand experience with like two of their their producs. Oh I found an example of the sound

Well, this card was more or less a reply to Creative, because those cards sucked and this one didn't. At least in theory Those people who never had a problem with their X-Fi are pretty happy, loving this card with all their heart. Sadly, they seem to be a minority Anyway, this biggest problem with Auzen's card was never observed on Creative stuff, so naturally Auzentech is to be blamed for some sort of hadrware design screwup. Mixed with horrible customer support.. ew

This might be slightly offtopic and slightly ranty, but I simply want to warn people. Do not deal with Auzentech. Ever. I mean, don't even check their web. Don't be curious what kind of products they have. Stay the hell away. I bought X-Fi Forte about 1.5 years ago when it was still fairly new, but with decent amount of extremely positive reviews, kind of guaranteeing a good purchase. Well, that didn't turn not to be a good idea. Some people were not affected, but LOTS did experience horrible sound problems, like that cracking-popping random noise (just youtube it up) that would start randomly (I think there were a few other, less horrible issues with the card). Eventually Auzentech confirmed there was some sort of problem and people started to RMA the cards. Now here comes the reason why I am posting this: I saw some crap support in past, but nothing, I mean NOTHING comes even remotely close to what this company does (or rather doesn't do). Usually it takes at least a week before you get any reply to your ticket(s). Sometimes even longer. I RMAd my card in july last year. Initially it took them two weeks to answer the ticket, then for a week I tried to explain that their stupid PDF document was impossible to edit. The whole process (and it was agreed from start that I should simply receive a new card) took over a month, EXCLUDING the time spent waiting for an answer. The card I received had the same problems (in fact I believe it was the same piece). At that point I gave up for a few months. Recently I heard they produced a new revision (the card is allegedly physically different). I though it was worth giving it a shot. I have been waiting for a month already and despite a few reminders, I've been ignored. Well, kiss my a** Auzentech, the last thing I can do is warn anyone who is interested to listen to my little story. TL;DR for some, whining for others, maybe - but if just one person decides not to buy products from this fail company, the mission is a success. Lesson learned: even if you make awesome products, s***ty customer support will drag you to hell.

I am aware of that But I download and install the latest version anyway, because occasionally I get to PC with newer chipsets. This is not about compatibility but about performance. Allegedly the v9.6 has higher performance. I have no idea whether it is supposed to apply only to SandForce-based drives though. I have Intel 320.

I just read that for P55/ICH10R (or older) I should get Intel RST v9.6 and for P67 (or newer) RST v10.1. What's the deal here? I always thought newer (much newer in fact) drivers were always the better (as long as the hardware in question was still supported) considering possible new functionalities and bug fixes. Does anyone know anything about this subject?

RT7Lite is a junk. Don't use that. It's buggy and the development seems to be frozen in last months. And that indian english is just pain in the a**. Just download the iso with sp1 already integrated from MSDN (or ask someone to do so).

Long story short: 7Customizer does not have that functionality.

"I will use Google (or search) before asking stupid questions" Repeat this 100 times and you will come to enlightenment.

Oh btw. The removal function is not working properly. I didn't do anything but check all that is possible to check for removal (3 things or so), and after being finished with the process the folder actually grew by some 30MB. Considering those functions should take about 700MB, something is wrong. Btw. Please make presets save product key, updates and drivers too.

Oh btw you can draw upon inspiration from RT7 Lite's registry tweaker utility http://www.pub.rt7lite.com/rttweak-public/rt_registry_tweaker_2.1.msi I figured that in the end I don't care about components removal THAT much, but having the option to customize system settings is much more important to me. Slimming the image down is a very welcome bonus, but tweaks is the main thing.

Isn't that Gavotte thing a bit outdated btw? Last version from 2008.. I don't know.

The thing about version is that the source is SP3, which is which year? The updates in question are from say 2008 or much later. There is no way in hell those files would be older version than those on the cd. That is impossible.

I am using this list: http://www.vorck.com/windows/hotfixes_xp.html These updates told me the line about not being able to integrate directly (file not present in the ISO or what): 943729 969878 898461 941569 942288 955704 971513 979687 982316 2443685 2508272 2524375 And these babbled some nonsenses about file versions in iso being newer than those in the updates: 2360937 - sprv0405.dll in the ISO: 5.1.2600.6031, in the update: 5.1.2600.6022 2509553 - tcpip6.dll 5.1.2600.5935 vs .5625

On the subject of updates and problems: does anyone know what's the deal with nLite telling me that 1) certain update cannotbe integrated and whether I want to try the regular method (like I know what the non-regular one is) 2) a file in an update is older than the one present in the source? Like wtf, how can a file in the source data older than that in an update released several years after that? Something stinks about build numbers here, because there were at least 3-4 updates where the files to be integrated had build number like (random example) 2350 and the source is 2600 (which is the SP3 build number afaik). In such case I have no idea whether to keep the allegedly newer file...

Ok I nailed it down. The behavior is caused by RSS feeds. I have no idea why, because the news on the main web shouldn't be tied to the forums at all (but then again that's just my amateur opinion), but that's the way it is. xper, is there anything you can do about it?

I honestly have no idea. It must be Opera related, because xper stated it works well in IE. What I found out so far is that it's enough to just start Opera without even having MSFN in any tab at all. I will see about the RSS feeds, but that wouldn't make any sense as they aren't from the forums but rather the main web. But if it is the RSS's, then something is not coded the right way I'd say. Not using Speed dial (no idea what it does anyway).