Hi,
I got back from Spain.
What's the status on hyperion 5.18?

277

(1 replies, posted in DriverPack WLAN)

thanks,
I was abroad.
I checked the files I uploaded and put the correct values in the changelog file.

Torrero.
I downloaded the driver yesterday and hoped to get it in a release before I go on holiday.
I wrote that joke after I got the driver (the comma after html.. that got us to taiwnanese/chinese language page for it.)

If this is urgent, sorry, I won't be here  12th. to 21st.

BUT... there are other team members working on a testpack.

I do not know what OP is short for, but I most definately agree with Jeff.
He was//IS coding to get PE/UBCD4Winn support for a very difficult driverpack.

Yesterday I was looking at the HWIDs spotlight readout for the current LAN. (This was a scan of DriverPack LAN only) and I compared the findings to what I had described in the NVIDIA LAN topic downloadble files.

I put ALL  original NVIDIA LAN drivers in a package, and had hoped people would help us puzzle together the best combo for all.
Yesterday, I think I saw two wrong combo choices.
The file is still there, the txt about two matching or singulars is a guide.
BUT..
When I worked through 22 driver sets, I probably made mistakes.
There is ONE guy complaining about LAN, but I am not going to say he is a lone crusader.

Jeff would not like better than the LAN set for disc install be perfect before he can code the rules, and one of the problems he faces is that there is huge 'official' lan overlap in official nvidia lan drivers, and ' "not to be taken lightly" ' they usually use same same name in systemfiles.
WE, we dream of getting a rules based install so we don't have to care (much) about which driver we add.
An update would be an update.

I challenge you all to look at LAN NVIDIA official set of drivers, and please, DO help us figure out why they need so much attention from team.
Oh, you can be a gifted watson and not be in our team, but I can tell you that I was a watson before I learned to be Dr. watson.
I am not Holmes.

hehe.. we get unnofficial testers reporting on test versions, and they start helping us by helping those with same problem.

(And, by GOD, Krige had to be shown the lights, but he learns this quite fast..).
Compare the results like a scientist would.
If you can use same Same hardware, and if on this hardware there were NO problems with officially released DriverPacks, and there are issues with a new testpack testbuild we want to KNOW.

Of course we want to know about issues about officially released DriverPacks, and we want to know what you did to fix the issue (which driver you used to solve the issue, a link to it..)

I have often said I like to use the NOOB approach.
When I have to test a DriverPacks testpack, I run a live test on a testplank I know I had issues with.
It goes live with an autopartition, autoformat, and 22 minutes later I know about 'holes' or "whole".

after I see 'whole", do not think I don't look further. I run the testplank through tests (but I don't always use hibernation.. I don't buy laptops for testing. I test on the hardware I have available and I kept quite a few difficult 'crapola' motherboards to test on.
((which means I am in breach of an agreement. We asked the testers they do NOT personally invest in testing materials..))

281

(88 replies, posted in DriverPack LAN)

Hi
e1e6032.INF is for Vista and server 2008 32 bit versions.
It sure looks like we can drop the i3\folder into the bitbin.

282

(23 replies, posted in Software)

Hi
we'll need the HWID for that sound chip
(you can run the HWID tool in one of these laptops, and copy the relevant txt to an USB stick.)

Thanks for the test report.

Can you use the 'older' but official release and tell us if that one works correct or not?
I know you are still quite new to this, but we appreciate the reports.
Updating DriverPacks is often not as easy as people think.

it was actually called A\8 and content got merged to a same version variant.
((merged A\8 into AC\21 (abdou had asked about what to do with it.))

Thanks.
I am looking at the LAN pack again. (did a new HWIDs readout and looking at requests.)

Hi

we knew it, We really knew it.
In Russia some excavation was going on, and 50 yards deep they come across copper wires.
They sent people to look at this and concluded that over 600 years ago they had copper based networks.
You just said that in taiwan they had LAN some 2005 years ago.
Tthe americans dug too, and in one of the deep digs they find glass fibres. They now clain they had fibre optic networks about 4000 years ago.

Over here.. we have really deep digs and mines, and when the russians and americans boasted about the finds we started looking too.

We found NOTHING.. no copper, no glass fiber, and the experts now say that we had wireless networks at least 8000 years ago.

287

(10 replies, posted in DriverPack WLAN)

Hi
spotlight05... on the WLAN pack. Look closely and see it misses a few broadcoms.

prove it to yourself, download a couple recent broadcom drivers, and then scan them.
(by the way, I use a dragdrop version of the cmd script. As a fallback I also used a SED script (which is what we developed first.))

http://users.telenet.be/jtdoom/spotligh … scanner.7z

288

(63 replies, posted in DriverPack Mass Storage)

There is a testpack for mass and chipset.

http://forum.driverpacks.net/viewtopic. … 495#p21495

and http://forum.driverpacks.net/viewtopic. … 457#p21457

289

(10 replies, posted in DriverPack WLAN)

This is like a wishlist with super generics in reference drivers.
We've seen that generics and super generics can cause trouble, and we may never find out what we could use for real reference driver.

What did you use to collect the HWIDS?
We have two tools, and neither are perfect.

19,1 MB (20.124.331 bytes)
MD5 hash 564abf9881fbbbb2de4fac91e727501c
DP_Modem_wnt5_x86-32_806.7z


V8.06,
Made corrections in supported hardware list.
Device list had reference to empty AC\2 folder. (AC\2 was covered by AC\4 (same version))

removed A4\ (covered by AC\49)

removed AC\22 (covered by more recent driver in AC\4)

removed AC\35 (covered by same version in AC\36)

removed AC\47 (covered by newer in AC\21)

removed AC\54 (covered by more recent in AC\21)

merged A\8 into AC\21 (abdou had asked about what to do with it.)

removed files from C\5\ (files in C\6 were duplicated in C\5\)

disabled PCI\VEN_8086&DEV_24C6 generic in M\2

ADDED
C\19\ CXT HDAUDIO Soft Data Fax Modem with SmartCP, 10/16/2006, 7.57.00.51
C\20\ CXT HDAUDIO Soft Data Fax Modem with SmartCP, 03/16/2006, 7.33.00.51

C\21 (Windows Update) conexant AC97 SoftV92 SmartSpeakerphone Modem, 11/11/2003, 7.04.01.00
C\22 (windows update) conexant AC97 SoftV92 Data Fax Modem with SmartCP, 12/08/2004,7.14.00.50

A\5 added an INF file for toshiba laptop.

==================================
previous version;

805; by abdou
A\8 - Agere HDA Modem for Acer aspire 5315, 03/09/2007,2.1.77.9
C\18 - Conexant Soft Data Fax Modem with SmartCP for sony vaio VGN-FZ18E, 10/24/2006, 7.58.00.50

Hi abdou.
When you first posted about the ACER driver you mentioned that you was not sure about how to deal with it.

A\08 can indeed be dropped into AC\21
---------
I am still working on modem, (have a few REQUESTS I want to look at too) but have a temporary list with changes.
Today I built a new worksheet.. did a new spotlight scan, and used that in excell 2007.. (works easier than excell 2000.)

EDIT, The result is below

& JsE

http://forum.driverpacks.net/viewtopic.php?pid=21425

if you are looking for a 'link to latest testpack', there is a sticky in forum which has a link to the relevant topic..
http://forum.driverpacks.net/viewtopic.php?pid=21496
The title sometimes changes, the sticky gets updated when new work warrants it.

8.06C (06 June 2008)

driverpacks_nightlies/DP_MassStorage_wnt5_x86-32_806C.7z

MD5 hash 86516c2970912b1b0a4a0589f48fdf11



Changed
'[I3] Intel Maxtrix Storage 09/29/2007,7.8.0.1012, keep support for hardware not covered by new intel driver.'.

'|[AD2] removed'.
'|[IB4] removed'.
'|[IB5] removed',

Fixed
'',

New
'[ADC] Adaptec SAS/SATA-II RAID for server 2003, 02/08/2008,5.2.0.15728'.

'|[H3K] Highpoint RocketRaid RR182x/181x for windows 2000'.
'|[H3S] Highpoint RocketRaid RR182x/181x for windows 2003'.
'|[I4] Intel Matrix Storage 04/20/2008, 8.2.0.1001',


Updated
'[ADB] Adaptec SAS/SATA-II RAID for XP, from 09/15/2007, 5.2.0.15317 to 02/08/2008, 5.2.0.15728',


notes
JsE did the real work on adaptec and IBM. http://forum.driverpacks.net/viewtopic.php?id=2363

I must have forgotten to hit the subscribe link because I see I was not subscribed to this topic..

I am sorry.
I am working on this again.
I wish all posters were as thorough as that.
Why are you not in one of the DriverPacks teams? I see the CSV file and other research you did on this, and I see you know more than most here..
Are you interested?

Hi
I think soporific wrote a warmsnow with more gui.
btw, the name rings a bell.. I think he is a gifted member. (and not just a word I read in a dictionary.. smile )

Projects like this don't start if there was no percieved need.
We had many requests for a ""post-install-minisetup-plus-finisher" (in which Finisher is our "exception ruled CPL installer and cleanup tool"") and once the WAIK provided the tool we needed to do a "post install mini setup" people like Jeff, warm snow, nuno brito and soporific (and others whom we have perhaps never heard of) started coding.

I'd like to see the works.
GhostE, where is the url of that project?

Samlab?
what did you change for HWID read tool?

previous posts with output was most often not consistent to what we normally see.

or an english vista.. for Host Os.  (The txt we write can be adapted to what we see in screenies.. as long as the screenies are showing what we have to show.)
1, not all packs,
2, at least one outdated pack.
3, 3rd DriverPacks if you really want.. we used none (it was a basics tut..), but we could show them selected.. and have extra screens on  how the folder was populated.
4, extra screenies on DPinst tool.

5, for daredevils: multiboot disc (separate tut)

Hi guys.
You probably read I think it would be a good idea to split the laptop graphics out of DriverPack Graphics A and have a DriverPack Graphics A MOBILE.

desktop IGP and mobility drivers probably have different default refresh settings.
I have an LCD screen that will do 60 and 75 Hz but not 70.
When the driver forces a default of 70, I am greeted with a black screen too.

mr_smartepants has put a wonderful sticky up, in which you can read about changing default resolution for laptops.
I think we see issues because we have desktop GPU add-in cards (and desktop IGP) and laptop in graphics DriverPacks, and if we really must do this, we could perhaps change a default.

link to public testpack for chipset is here

http://forum.driverpacks.net/viewtopic.php?id=2698

hi,

if they want to use it, they can test the version we had before we added INI for PE.

DP_Chipset_wnt5_x86-32_806A_PUBLIC.7z