Hi
@ Helmi, thanks.
I guess Graphics C will see an update.
G_C also has old NVidia TNT, so why not include these old ATI?

I will start work on this tonight

Hi

Can we ask that you again run it in the way you got that error, and then post the log? Please?

hi
there is a mass storage 706test1 version posted in testing forum, and that one attempts to fix the following

JMICRON JMB36X issues
folder \J\1 is gone, the HWIDs are put in J\2 which has a newer driver.

(Mass storage release 705 has an old AHCI for Gigabyte in there, and after the 705 release this was at first exchanged with an update by Gigabyte.. In this 706test1 testpack this is now gone, for people found two Jmicrons in hardware manager (yellow splats) when GBT driver-version 1.17.17 is used along with files in the existing pack.)

merged ATI-SiL-Image 3112r HWIDs in \S\5 (which is the newer)
\S\5\A gone (silly image clashes with silicate image)

Intel matrix storage drivers and the intel chipset were also looked at.
ICH9 was introduced, and intel dropped support for older than ICH6, and Intel in AHCI mode is an issue at times.
We want to fix that.


These are TEST versions, and we'd like to know wether this solves your issue.

test this on
INTEL, (INTEL in all its modes should be tested along with chipset 706test1.)
JMICRON 36x (test AHCI mode, and raid)
SIL3112r (test AHCI mode, and raid)


chipset706test1

storage706_TEST_3

A word of advice
Once a drive has been used in AHCI mode, and later on you want to use it in a RAID or in IDE mode, you may have to low level format it by using the drive manufactor disktool.

EDIT; mass storage test1 was updated to TEST2

your testversion for broadcom is uploading.
NOTE; for BartPE plugin optimizing, the dupe filenames were changed and file references in the INF file were changed.
The DELL driver for broadcom is renamed to 8221xxx (its version is used as part of the name)

http://users.pandora.be/jtdoom/DP_LAN_w … 1_TEST1.7z


EDIT, NOTE, dupe HWIDs were not edited out, but PnP ought to handle that fine.

hmmm
I think the fix will be a third folder, and an undo of the edit I did in 7.06.
I immediately saw a cartload of specific subs, and  looking at the registry entries I thought merging this old Dell with the newest broadcom is not going to be possible.

Another check reveals it will have to be a third folder, because the system file is different as well.
I will have to undo the edit in B\1, and add a B\3

if you need a solution pdq, put official broadcom in B\1 (I changed the INF, and the official has to be used)
put the DELL in B\3
undo your INI edit
then repack, and use your custom lanpack.

Hi
I had an extremely busy workload this week, and had not 'subscribed' to this topic.
(alas, that is an extra step, in this BBS.)

I meant the INF of the driver, not the driverpack's INI.
What you did was adding an exception to an NVidia LAN driver, which is not going to work for broadcom.

I just downloaded the DELL driver.
THANKS
I'll look into this one, and may find a solution. (I am subscribed to this thread now.)

Hi

the natively supported IDE drivers are not critically important during setup, but we have already included PnP IDE drivers in a test release for a particular driver, and I figure this will be a future trend.
PnP drivers like this just make life easier after setup. More responsive systems can be achieved that way.

Mind you, the chipset DriverPacks will have to be included in your slipstream, for these usually enable the enhanced features of the machine, and chipset drivers often have to be in place for other functions like specific SCI and IDE enhancements, and even for some graphics drivers.

hi
Saw this and did not want to comment.
I thought somebody would have replied by now, but since it did not happen, I will.

Well, the DriverPacks Mass storage plugin for BartPE is already released, and the work being done on LAN is making good progress.
We do not have an extensive tutorial about this feature yet.

Hi
yesterday, I downloaded these three ATI legacy packs, (and yours, to doublecheck), and scanned the existing releases for Graphics A, B and C against one of the supported HWIDs found in this rage-Pro driver, and I got nada, zip, zero.

This means that our packs do not have this driver. (actually, that the HWID I looked for was not supported)
I wanted to let you know I already did this.
I will hand this over to muiz, tho, for I still have to learn about ATI and CCC, and I do not want to mess this up.

FWIW, it looks like this old driver will have to be in a new folder, unless our newer driver can support the "unsupported" HWIDs.

1,835

(3 replies, posted in News)

Hi,
there was a typo in the filename.
Sorry.

Hi
Download should work now.
The file just had a wrong name. Sorry.
sad

1,837

(3 replies, posted in News)

Dear Gentlebeings,

OverFlow invented a neat way to make a listing in which we could find duplicates.
The list is just part of what we had to look at.
Just the same, it was really helpful, and the pack got smaller.
For instance; Via Rhine and Marvel Yukon updates in previous release made it possible to get rid of several outdated drivers. Jeff's list and a couple other tools made that possible.
In essence, this release has "More duplicates removed, more Folder and More Filename optimization for BartPE".
Updates are always prone to error, but we checked in more than one ways.
We see that during the last two updates we did, the LAN DriverPack got smaller yet supports more Hardware-IDs with fewer duplicates than before.
Fewer duplicates, should mean fewer possible causes for conflicts.
The optimization for BartPE is not detailed in the changelog, but essentially means that fewer drivers should have "missing" files because of wrong references in the INF files.

We've not yet touched Nvidia's Lan drivers, so far.
The neverending story can continue.
A warm Thanks to Jeff is in order, for his insights were educational..
DriverPacks LAN 7.06

Ok guys
Lan 7.06 is online, and we want feedback on this broadcom issue.

IF the 10.24.0.0.D version for broadcom57xx is bad for you, we want to know.
We sure would like to know when Broadcom puts up a new version, because I get the feeling we had less reports about failures with the older one. Broadcom will get feedback as well, and can remedy the way they post their driver.
(If you noticed, they do not include system files for 2K in Xp driver, yet reference the 2k system file in it. In our pack, both 2k and XP system files are present, and the driver folder is still incomplete because its INF has a reference to x64.)

One wonders how much bandwidth costs, and how beancounters work.

1,839

(4 replies, posted in Hardware)

Day before yesterday I had to kill an XP bootloader in a machine that got really bust up.
Both Hard disk drives were stamped active and system after the user had attempted format on his systemdrive(s), and traces of wrong letters and where memory dump had to go, or where where "hibernate file" was, and the swapfile had had some letter too.
This had to be cleaned.
A boot floppy could do it.
(my custom 98se Boot CD can do this too.)
It was actually more than 2 ys since I last used the tool. (I used it almost weekly way back.)

wipe two Mbr/Embr in a linux/Xp/98se boot machine what had two HDD and five "drives".
Data loss was not an issue.

knoppix GRUB can do this, but that little tool did it in no time flat.
boot, wipeout C:
then wipeout D:
and then a DriverPacks unattended with hotfixes. smile
56 minutes

hi
Your cellphone can be a carrier. (there are wild bluetooth viri around)
Your thumbstick can be a carrier. (they are known to install rootkit infections)
Yesterday I saw a request for a critical Dell update, for WLAN.
I was told (by experts) most home routers have a DMZ which is not really a DMZ.

I Wish the Antivirus makers never threw false positives as much as anybody else, but there will be a false from time to time.
Too bad this affects the tools we use here.

As an aside, are you scanning files during windows SETUP? HUH?

...but as the driverpacks finisher runs unattended-ly as Windows installs itself unattended-ly, there's no chance to setup this ignore rule before Symantec's Auto-Protect flags and deletes them before they ever have a chance to execute....

1,841

(4 replies, posted in DriverPack LAN)

hi
hmmm, why did you not just link to this?

anyway, this has already been done.
from current changelog
Fixed
- AC\1\2k removed since AC\1\xp supported this with newer driver (jtdoom and OverFlow)
- AC\1\xp moved to AC\1 for folder optimisation (jtdoom and OverFlow)
- C\4 removed, device is supported by O\7 (jtdoom and OverFlow)
- MI folder reference changed for BartPE (Muiz, jtdoom and OverFlow)
- N\3 folder reference changed for BartPE (jtdoom and OverFlow)
- SB\2 folder reference changed for BartPE (jtdoom and OverFlow)
- SM\3 folder reference changed for BartPE (jtdoom and OverFlow)
- SM\7 folder reference changed for BartPE (jtdoom and OverFlow)
- TR\2 removed, duplicate of T\1 (OverFlow)

----------------
when I check above;
SU\7 currently has ne2000.sys in it (because that was the internal name of this file)
So, most, if not all fixing was done already.

I will send an Excell file to Muiz, so he knows what was done during the last two days..
yes, 7.06 is almost ready for publication.
OverFlow is probably looking at the work, and doublechecking it.
GRIN, despite that, NO, it is not going to be a loooooong changelog. smile

hi

I think it was not online when I updated INTEL, and latest work was focused on BartPE optimization.
Anyway, it gets in now.

1,843

(2 replies, posted in DriverPack Mass Storage)

hi,

What model 'blades' is this?
Can you link to these drivers for these server 'blades', please?

you're ON... we know this is likely because catalyst 7.5 had bugs of its own.
I say four days and six minutes, tho.

Hi

This was part of the problem with Graphics_A 7.05 and 7.05.1.
The 7.05.2 is actually 7.04 since the update was pulled back.
The New Catalyst driver installer used a very different method than previous released Catalyst drivers, and while local tests worked for those working on it, a live rollout did not.
Tests on the new catalyst installer are showing real progress, though.

hi
can you provide a link to this DELL driver for this mobile variant?
(this string PCI\VEN_14E4&DEV_1677&CC [even with no numbers] has no hits at all here)
a moment ago I added this line in two sections of the driver's INF

%BCM5750A1DMOBILE%  =  BCM5750A1DMOBILE.Inst,  PCI\VEN_14e4&DEV_1677&SUBSYS_01AD1028&REV_01

YOU can do so as well.
paste this "REV_01" line under the followin lines, and it should work. smile
%BCM5750A1DMOBILE%  =  BCM5750A1DMOBILE.Inst,  PCI\VEN_14e4&DEV_1677&SUBSYS_01AD1028

then repack with 7zip, and give this a higher version number (7052 would be good)

I'd still like to have a look at DELL's driver.

Have you kept a copy of LAN 7.04?
Remember to keep copies of packs that work..

Hi
This info is useful.

6.05 had 119 files for XP in intel chipset, and later versions of Intel drivers dropped support for old stuff.

This is a TEST version, built on May30th.
http://users.pandora.be/jtdoom/DP_Chips … 59test1.7z

If this works, let us know, please?

Hi
Thanks for the report.

Bâshrat the Sneaky wrote:

So my suspicion was right smile

Kurt_Aust, could you please tell us which ones you disabled? So we can make the same changes - or changes with the same driver size. Then you won't have to bother doing this next time.

Since Kurt says he did not know which would be best candidat for disabling in Windows 2000, I guess we'll have to find infrequently used with same footstamp.

Highpoint was frequently used, and probably still is... and Kurt disabled them all?

Thanks,
Back to the drawing board..

I am deleting links to the testversions.
we had test versions linked to here, and the mass storage updates do not work.