Search options (Page 22 of 58)

Nice rig!

Also, looks like a fair price to me.

Are you going with dual-boot or how were you planning on testing DriverPack Graphics A?

Anyway, bold move getting Vista now when SP1 is so close to public release...
Personally, I would have waited until they ship slipstreamed DVDs seeing as it's quite cumbersome doing that yourself (at least compared to XP - took me well over 3 hours to accomplish that!).
Whatever, if you want links to SP1, I can supply you with the info

Quality before quantity any day

Anyway, I sticky posts/threads that I deem useful for others.
I look at the contents, not so much the user who wrote them.

And seriously, we did have more than enough of these after-install update requests, now didn't we?
I'd put a link in my sig to cut them down but I am already at my max characters...

Anyway, if you feel like any other posts needs/deserves a sticky, just send me a note.
I know we're only a handful of Mods around here so we may miss a great post/thread here and there.
Really great stuff could also be copied to the FAQ forum.

Just because anyone's post did not get stickied doesn't mean we don't like/appreciate it - may just mean we didn't spot it or discover its true value yet

Where is the RC3 linked to?
I couldn't find any in the first posts of the linked threads (not going to crawl through all of it).

If you refer to it still being on the server, well, you don't have to dl and use it, now do you?

Anyway, Jaak, I think we should let them have RC2.
It contains support for XP SP3 (of which a new RC2 build 3311 has been released btw), so if anyone wants to try and fiddle with that, let them do.
Personally, RC2 has worked perfectly fine for me and I wouldn't want to go back to the last final any time soon
I would say it's stable enough not to cause us any great amount of support requests from regular users that are not testing it but rather using it for the real deal.

Yeah, I guess it's RC2, I've been using that lately.

There was a beta3 or so on the nightly server for a couple of days/hours but that was completely broken from what I can tell (didn't even start to slipstream) and was taken down quickly.
The previously (to that beta3...) released RC3 also was a no-go.

The model of the HDD is irrelevant to this, the only thing that matters is the SATA controller.
You will need the drivers for that.

If you use the DriverPacks, you'll have to include the dpms and also enable Texode support in BASE.

If you don't you need to use the driver of your MS controller - if it's on-board it will be supplied by your motherboard manufacturer.

NO double or cross posts! >8(

***CLOSED***

No, we don't "send out" drivers.
You'll have to contact your system's manufacturer (Sony support in your case) if you are unable to find the drivers on the website (have you even looked there already?).

Besides, what exactly is this "sound problem"?
Are you getting sound at all?

Also, have you already tried the DriverPacks and verified the required driver is not included?
In that case, please post your HWIDs (see the link in my sig).

As for camera drivers, you can try the 3rd party DriverPack, there's a cam pack.

The place is proper but your formalities aren't quite.

If you take a look at the other request posts, the subject line is to be started with a [REQ] tag so that it can easily be identified as a REQuest.

Other than that, your post is perfectly fine.
Direct link to driver file, taken from official manufacturer website as well as HW given that this applies to.
You may want to include HWIDs (see my sig) next time but it's not a necessity (I think).

Anyway, I do suspect your problem may be related to the missing KB888111 HDA hotfix rather than the driver missing, since, what I can see from the link given, it's Realtek and we already support a plethora of their devices.
Run a search on that KB term on he forum and you should find enough stuff on the matter.

Well, while you are right about the on-access scanning, I monitored the task manager closely (which is also where I discovered makecab.EXE not being SMP-capable).
My virus scanner (NOD32) wasn't grabbing any more CPU resources than in does on idle (hence not noticeable), and even if it did, I would still have had the other core for it to use
AT no time did my overall CPU usage come even close to 100%.

Anyway, I did enable QSC, as I always do with M2 (even if it's just for DPMS there), so I may give it another try once a pack has been updated

Now, that is very strange.
I guess there are hundreds of users on this forum that do the same as I, use all the available DriverPacks.
None has reported any error along what you have heared about.
I'm sure if this really was a problem, we, the team, would have been notified by some user.
Also, if it really was a problem, our members would do their best to fix it (ASAP no less!).

I would suggest you post a note in the Turkish forum pointing them to this thread (or this forum in general) so they can correct this "hoax".
It would be bad if it fooled other users into thinking they cannot use all DriverPacks together!

As OF already stated, this only means to use these tool for the ISO creation.
The reason for this is that BASE does not support making the ISO so you will have to do it manually or rely on the tools named above.

You should not do anything else but create the ISO after you have slipstreamed the DriverPacks using BASE.

If you want to use nLite or RVM to include update packs, hotfixes etc then do it before using BASE.

Personally, I use nLite for the task and when I get to the page to create the ISO, I leave nLite open, switch to BASE, slipstream the drivers, [alt]+[tab] back to nLite and make the ISO
Simple as that and rather convenient.

If you want to do this all in one go and only ever use one tool for it, I suggest you try RougeSpear's AutoImage which can be found here.

Does the DPInst also work with un-7ZIPped files as opposed to CABs?
Reason I'm asking is that because makecab.EXE is only using one core of my CPU (a P4 3GHz with HyperThreading) which results in a very slow performance (worse than 7zip because that actually uses both virtual cores) and I don't feel like disabling HT in the BIOS just for this (needs a reboot every time).
I started M1 when I edited the link in your other post and it is still working on compressing the CABs.
M2 would only take about 10min on this system, extracting all 7zip DriverPacks slightly longer.

Since I do test each and every nightly, this means I have to reapply M1 quite often in order to keep an up-to-date driver disc.

Not having to point the driver search wizzard manually to the drivers dir/disc definately does not make up for this long waiting time (I also include the 3rd party DriverPack).
I certainly wouldn't mind using a DVD for this and also can neglect the longer bruning time for more content because it pales in comparison to the wait M1 burdens on me!

Simple answer:
YES!
The DriverPacks are made so that they complement each other; no pack contains anything the others do.
There are also no compatibility issues between the packs (that would be rather stupid, wouldn't it?).
You can even use more packs if you include the 3rd party DriverPack or make your own packs (see my sig for links on hot to do that).

That is basically what I always do.
It may take some time to fine-tune it but yes, it will be very good (as in convenient) once it's done and polished

Where does it say that???
Sorry, but that is utter BS!
We always state that the BASE should be the last step before creating your ISO, so yes, what you read on RVM was absolutely correct!
Again, see my sig for a link to a HOWTO.

If you are using nLite, you can simply disable the Driver Signing Policy.
Or, you can do that yourself manually by editing the following lines in the winnt.SIF

[Unattended]
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore