MagicAndre1981

integrate the SP1 and you do not need the old updates

yes, but you can request about 40 Post SP1 Fixes from the MS support.

already posted here: http://www.msfn.org/board/Vista-Update-Int...a3-t114365.html

yeah Integration works fine with an RTM XP, but if you want to install the Sp3 on a running system you must have at least Sp1 installed

you need the Swedish Sp1 LP which is not available at the moment. The LPs from Vista RTM are not 100% compatible with the Sp1

I've tested it on my Vista 32 Bit and it works. The tool is a bit buggy when ypu try to integrate the Sp1 into the 64Bit version of Vista.

wow, thx for the news

yes that's right. After removing some parts with vLite the SP1 fails to install

I also have this but I have no idea why this happens

what was the problem?

Hi,the tag (vLite) indicates that you are using a DVD with was already edited with vLite. So try a clean DVD!

Vista Sp1 includes the .net 2 and .net 3 sp1

which edition of Vista do you use? Not all fixes apply to all editions of Vista

please write in English!

I know I also tried this. But now I got the matching LP DVDs for Vista Sp1

disable the service and remove the Defender GUI from automatic startup. You can use AutoRuns for doing this.

no it's only 1.1 GB and include both installers (x86 and x64) of the SP1. You can use MagicDisc or such a tool to mount the ISO.

I tried it and the tool runs fine for me. But I removed Defender. Try to disable Defender.

the LPs form the Vista RTM do not work for Vista Sp1. ou have to wait for the compatible ones.

sign up at oem.microsoft.com with a live account and you can DL the wave0 installer since 22th February.

why don't you integrate the LPs first?

this happens when you have UAC enabled and you put a program to the startup folder with requires elevated rights to run. UAC blocks those tool by default. The workaround is to create a new task inside the tasksheduler to start the tool elevated when you login.

but he mixed up the ID with the brand string. The ID is fixed and the BIOS sets up the string according to the ID and the CPU Speed. Because the speed was lowered the BIOS couldn't recognize the cpu and that's why the BIOS programs the CPU Brandstring "AMD Athlon" with the current clock speed.

no, the BIOS sets up the BrandString inside the MSRs of the CPU.

no, you need Jet for Access!