101

(107 replies, posted in 3rd Party DriverPacks)

And maybe thats the approach needed to support all bluetooth devices.  Install the Bluetooth stacks FIRST.

People don't complain that their network card drivers have to be loaded before a TCP/IP configuration can be set up.  Same thing with Bluetooth.

No sweat, everyone here is a volunteer with Real Jobs and Real Families........

My meager contribution is being able to test on about a half-dozen different laptops in the office IT lab (4 dells, two Lenovos) as well as my home machines (1 C2D, 1 C2Q and 1 ancient Athlon 3000).  You guys who have the skills and patience to code the packs and Base have my admiration and respect.

If the VirtualBox SATA controller is to be included in the MassStorage pack now, perhaps the VMware (v5 and v6) controllers should be as well.

Sam, no one wants to download drivers from any place other than the original mfgrs site.

Here is the direct download link at Intel:

http://downloadcenter.intel.com/downloa … p;lang=eng

only dumb if you ignore the build number.........

yawn, the packs have all those drivers on board and more....

dirvers for 'virtual' hardware should be contained in their own DP, IMHO....

108

(5 replies, posted in 3rd Party DriverPacks)

One thing to consider would be the relative sizes of an LCD-only pack vs an 'everything' Monitor pack and the on-going usefulness of integrating CRT support with LCD support and industry sales trends.

The most current rev of the LCD pack is about 10 Mb while the Monitor pack is nearly double that at 19.5 Mb.  I don't think that any attempt has been made to remove conflicting and/or duplicate HWIDs between the two so a size comparison of the current examples may only be marginally useful.

There was some discussion on this a while back.  I believe that the general consensus was that an official, frequently updated LCD pack was the way to go forward but that an intermittantly updated Monitor pack would be useful for legacy reasons.  The discussion kind of slacked off at that point without an official pronouncement.

109

(5 replies, posted in 3rd Party DriverPacks)

Did the 'philosophical' differences between the Monitor and LCD driverpacks ever get ironed out?

LCD; it's obvious. LCD drivers/.ini files.

Monitor; not so much.  Does the Monitor pack support glass tubes only or LCDs as well?  If LCDs, does it cover the same range as the LCD pack?  If LCDs, is there any deliberate effort to sync up support between the LCD and Monitor packs?

Hey, I hope that EVERYONE is having a great end-of-year holiday time.  So far I've attended respectfully formal and racously infomal celebrations with Hmong, Christian, Jewish, Arabic, and Chinese friends and I still have the 'official' New Years to get through.  It look like New Years will start with some local Russian friends and then move over to an Irish party.  If any Hmong friends invite you to a party, beware of the local LauLau, it often serves double duty as rocket fuel.......

Peace

considering they are all minor dot updates, we can probably wait a day or three for them to actually appear in Intels contrnt management system.

There is always a chance that these updates were emailed to some user by Intel support to try and fix some problem or another.

where did the files come from on your link?

112

(55 replies, posted in News)

Ninjas vs. the Green Goblin of NV?

I'd pay a dollar to see that!

113

(55 replies, posted in News)

As ATi and NV bring out new products, it's only natural that drivers for older products get 'rolled off' into the DP C pack.  Maybe set a benchmark of 24-30 months or 5 driver rev levels before things get rolled off.

It's even conceiveable that a D pack might be needed to keep the C pack at a manageable size.

You're bumping into a keyboard driver problem, not really a Bluetooth driver problem.

Lenove and a lot of Dells don't have full support for their keyboards in the BIOS.  This means that a driver (usually for function keys) needs to be loaded with Windows.

Complicating this (at least with Dells) is that there are multiple function key drivers, specific to different laptops.  It's a mess.

Nothing much to do for this except work out a way to get that driver loaded with your setup.

This one was released by Intel on Nov 16th......

have you checked your system error log/event viewer to see if there is anything there, such as disk errors or anti-virus alerts?

I've personally seen very long times on older hardware like yours.

What kind of disk drive do you have?

On my C2D E6850 (3gz), 4 GB ram, 7200 rpm SATA-2 drives, integrating all of the driverpacks as well as 3 or 4 third party packs, the process completes in about 100 seconds.

On my older Athlon MP (2.3 Gz), 2 Gb ram, 3600 rpm IDE drive, I would always go away for a drink of water and a little TV during driver pack integration.  Seriously, it would take that long.

Good news is that to upgrade to a new mobo, CPU, ram, and disk drive is in the neighborhood of $500-.

What is your time worth?

118

(88 replies, posted in DriverPack LAN)

You're slowing down fragbert, those drivers have been up for a week now............

119

(55 replies, posted in News)

Diti, you should take those down NOW.........

120

(17 replies, posted in Hardware)

LastXP is illegal warez and you'll probably not get any support for that here.

Is this a better/newer driver than the 'generic' Intel GMA driver (rev 5009) that was posted last week?

122

(5 replies, posted in Software)

got it, thanks

123

(5 replies, posted in Software)

well, I can't test consistantly, my available time and systems are separated by weeks sometimes.

But thanks.  Pointer to nightlies?

124

(5 replies, posted in Software)

I'm feeing a bit adventurous and will have some time over the next week so I thought I'd d/l the nightlies and give them a whirl on two laptops and one desktop.

But I seem to have misplaced the url for the nightlies.

Help?

(and thanks!)

125

(88 replies, posted in DriverPack LAN)

the link is in the top post in this topic