826

(37 replies, posted in Windows 8 Discussion)

LSASS: http://en.wikipedia.org/wiki/Local_Secu … em_Service
I have a memory leak in my Win7 x64 system.  I've had it for over a year and I still don't know what causes it.
Does that memory use extend past a restart?  How long is your up-time? It's not 15-days is it?
Report it as a bug.

827

(37 replies, posted in Windows 8 Discussion)

Win8 works fine on my VB install.  It must be a problem with your settings.  Helmi's right.  The newer version does help though.

828

(60 replies, posted in Vista / 7 DriverPack Graphics A)

Thanks Samlab, I'll give that a try.
At the moment I have new DriverPack Graphics A, B, and Mobile ready to go with downgraded Nvidia drivers (270.61) which work fine using SAD2.

*Edit
The above folder/file structure does NOT solve the problem for the new drivers. sad
Samlab, if you can put together the new nvidia x86/x64 files together so that they work, upload them somewhere and I'll test them.  If they don't blow up, and if they work, I'll include them in the next release.
Otherwise, I'll be sticking with 270.61.

829

(52 replies, posted in Vista / 7 DriverPack Graphics A)

I'm working on releasing updated graphics DriverPacks.

830

(60 replies, posted in Vista / 7 DriverPack Graphics A)

atlesj wrote:

My fix was to unpack the nvidia 280.26 driver and place it alongside this driverpack in my "drivers path" used for auto-installation. Then it worked!

So it seems that upgrading the nvidia driver in the driverpack would fix the problem...

No.  I can't get the 280.26 driver to install.  Not even the manual method works.  Integrating 280.26 into the install.wim will cause a BSOD at first boot.  275.33 isn't any better.  (Code 28) error.
I'm reverting the packs back to 270.61 because those are stable.

Well, I'm not sure why you'd want to connect an optical drive to a RAID card in the first place...whatever.
Promise hasn't supported that card in nearly a decade.

TechDud wrote:

i sense mr_smartepants evacuating to a safe distance...:)

LOL, I'll be over here...behind this concrete wall. wink

TechDud wrote:

Please refrain from posting in Topics marked [SLVD] (Solved). smile

Well that's fine.  If d3w10n had bothered to actually read the above posts the solution to his problem is in this thread and his problem will also be marked "solved".

d3w10n wrote:

I have the same problem

You have the same solution:
Don't use nlite for drivers!

LOL, fail! big_smile
It's meant to say NT6 not NT5.

Version 11.10.08 in first post.

OverFlow wrote:

a combination of SAD and DriverPacks Finisher

That would be AWESOME!

836

(37 replies, posted in Windows 8 Discussion)

Well now this is interesting!  I was poking around in the new Intel drivers and found this:

[IntelGfx.NTamd64.6.2]
; no install on Win8

So the Win8 designator is NT 6.2.  Vista is 6.0, Win7 is 6.1 and now Win8 is 6.2.

OK, I'll remove them and add them to a Third Party DriverPack instead.

atlesj wrote:

I would think this could be fixed by including an updated driver from intel that better matches the intel HW, it that exists... (now it's using the RTM drivers from win7)

Well, the Intel drivers in 11.10 are the newest available and they're not RTM, they're final release.  From here:
http://downloadcenter.intel.com/Detail_ … p;lang=eng

838

(60 replies, posted in Vista / 7 DriverPack Graphics A)

Yes, I've already got those.  Once I striped out the control panel craplets I got the folder size down to around 6 MB so it's not too bad.
But I still maintain that nobody uses Matrox products.  Walk into any computer store ask for a Matrox product: "Who?" will be your response.

Moved topic to "other".
This is a DriverPacks support forum.  You didn't use DriverPacks.

840

(60 replies, posted in Vista / 7 DriverPack Graphics A)

Do you have a matrox card?  Does anybody?  DriverPack Graphics B is getting way too large to be adding drivers for cards nobody uses.

Yes, I added it back into DriverPack Chipset thinking everything would be fine with the new drivers.
The problem is that in my organization we have nothing but HP machines with AMD chipsets (Phenom CPU) and this driver is needed for our systems.  So while it may cause problems for some Intel-based systems, it's needed for newer AMD systems.
What's the solution? I don't want to remove the filter drivers because I (and others) need them.
Can you confirm that the problem is solved when the \AMD\1\Filter\ folder is removed?  If that's the case, then I'll just update the changelog with the notice that those folders should be removed if integrating on Intel hardware.

842

(26 replies, posted in Vista / 7 DriverPack Chipset)

Updated to 11.10 (used final version of Intel drivers.)

843

(85 replies, posted in Vista / 7 DriverPack Chipset)

Updated to 11.10 (used final version of Intel drivers.)

Baldwin wrote:

How's the testing results i wonder?

Still going...
I may have found a bug with the DriverPacks Finisher.  testing...

845

(85 replies, posted in Vista / 7 DriverPack Chipset)

Nope.  The latest Intel drivers solve the missing .cat errors in DISM.  All clean! smile

846

(37 replies, posted in Vista / 7 DriverPack LAN)

Updated to 11.09.

847

(67 replies, posted in Vista / 7 DriverPack LAN)

Updated to 11.09.

848

(26 replies, posted in Vista / 7 DriverPack Chipset)

Updated to 11.09.

849

(85 replies, posted in Vista / 7 DriverPack Chipset)

Updated to 11.09.

Ah, you had NOT mentioned you were using UBCD4win.  That changes everything.
I edited your topic title to reflect you are using UBCD4win.
The BartPE plugin will ONLY accept dpms, LAN & WLAN.  That's it.  All other DriverPacks will be grayed out.